Secure and fast multicast

Abstract

The present disclosure generally relates to secure and fast multicast. An electronic device is described. The electronic device may include an antenna node communicatively coupled to an antenna; and an interface circuit communicatively coupled to the antenna node, the interface circuit in communication with a second electronic device. During operation, the interface circuit is addressable to at least the second electronic device to provide a multicast (GCR) block acknowledgement request (BAR) with a retry, where the GCR BAR indicates that the GCR BAR is protected. Note that the GCR BAR may include a GCR multi-user BAR (MU-BAR). In addition, an indication may be included in a reserved bit in the GCR BAR. For example, the reserved bit may include bit 0, or at least one of bits 5 to 11 in the BAR control field. Moreover, the GCR BAR may use the reserved bit to indicate a key identifier.

Description

TECHNICAL FIELD

[0001] The described implementations relate generally to wireless communications between electronic devices, including secure and fast groupcasting. BACKGROUND

[0002] Many electronic devices communicate with each other using wireless local area networks (WLANs), such as those based on communication protocols compliant with the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (sometimes referred to as "Wi-Fi").

[0003] To secure Wi-Fi communications, control frames and medium access control (MAC) headers of unicast data and management frames are added protection. However, group addressed frames, such as those associated with groupcasting with retries (GCR), a service for robust audio / video streaming, are not protected.

[0004] In an attack, an attacker can move the block acknowledgement window, causing data loss at one or more receivers. For example, a fake GCR multi-user block acknowledgement request (MU-BAR) or data can be injected with an invalid sequence number (SN), which can pollute or otherwise corrupt the scoreboard and / or can corrupt the reordering buffer. This can prevent improper ordering of frames and / or can hinder recovery of associated content. SUMMARY

[0005] In a first set of implementations, an electronic device is described. The electronic device includes an antenna node communicatively coupled to an antenna, and an interface circuit communicatively coupled to the antenna node, the interface circuit to communicate with a second electronic device. During operation, the interface circuit provides a groupcasting with retries (GCR) block acknowledgement request (BAR) addressed to at least the second electronic device, where the GCR BAR indicates that the GCR BAR is protected.

[0006] Note that the GCR BAR can include a GCR multi-user BAR (MU-BAR).

[0007] Further, the indication can be included in a reserved bit in the GCR BAR. For example, the reserved bit can include bit 0, or at least one of bits 5-11 in a BAR control field. Also, the GCR BAR can use the reserved bit to indicate a key identifier.

[0008] Additionally, the GCR BAR can include a packet number (PN) and a message integrity check (MIC). For example, the PN and MIC can be included in or after a BAR information field following the GCR group address. Note that the BAR information field can include padding after the MIC.

[0009] In some embodiments, the interface circuit receives a multi-station block acknowledgement (M-BA) in association with the second electronic device. The M-BA can be protected. Note that the M-BA can include a per-association identifier (AID) traffic identifier (TID) information field identified by a reserved value in an AID TID information subfield, and each AID TID information subfield can include information associated with a GCR. The information can include a GCR group address and / or TID information.

[0010] Further, the second electronic device can be a member of a GCR group.

[0011] Also, the interface circuit can address at least the second electronic device and provide an initial control frame (ICF) prior to the GCR BAR. The ICF can include information about one or more MAC headers of one or more subsequent GCR data frames. For example, the information can include a valid sequence number (SN) range of the one or more MAC headers, a power management bit, a more data bit, an end of service period (EOSP) bit, or a high throughput (HT) control field. Additionally, the interface circuit can receive an initial control response (ICR) or ICR frame in association with the second electronic device and in response to the ICF. The ICR can be protected. Note that the ICF can include a multi-user request to send frame, a buffer status report poll (BSRP), a trigger frame, a BAR frame, a block acknowledgement frame, or another control frame. In some embodiments, the ICF can be included in an aggregated MAC protocol data unit (A-MPDU). The ICF can be unicast and can be protected using a key for a GCR group that includes the second electronic device. Further, a receiver address (RA) for the ICF or a user information field in the ICF can include a group address of the GCR group.

[0012] The GCR BAR can include information about one or more MAC headers of one or more subsequent GCR data frames, and the information can include a valid SN range of the one or more MAC headers, a power management bit, a more data bit, an EOSP bit, or an HT control field.

[0013] Other embodiments provide a second electronic device that performs operations corresponding to at least some of the operations performed by the electronic device. For example, the second electronic device can include: an antenna node communicatively coupled to an antenna; and an interface circuit communicatively coupled to the antenna node, the interface circuit in communication with the electronic device. During operation, the interface circuit receives a GCR BAR in association with the electronic device, where the GCR BAR indicates that the GCR BAR is protected.

[0014] Further, the interface circuit can provide an M-BA addressed to the electronic device. The M-BA can be protected.

[0015] Also, the interface circuit can verify one or more GCR data frames based at least in part on the information. For example, the verification can be based at least in part on a MIC of the ICF.

[0016] Other embodiments provide an integrated circuit (such as an interface circuit) for use with the electronic device or the second electronic device. The integrated circuit can perform at least some of the aforementioned operations.

[0017] Other embodiments provide a computer-readable storage medium for use with the electronic device or the second electronic device. When program instructions stored in the computer-readable storage medium are executed by the electronic device or the second electronic device, the program instructions can cause the electronic device or the second electronic device to perform at least some of the aforementioned operations of the electronic device or the second electronic device.

[0018] Other embodiments provide a method. The method includes at least some of the aforementioned operations performed by the electronic device or the second electronic device.

[0019] In a second set of embodiments, an electronic device is described. The electronic device includes: an antenna node communicatively coupled to an antenna; and an interface circuit communicatively coupled to the antenna node, the interface circuit in communication with a second electronic device. During operation, the interface circuit provides information addressed to the second electronic device, the information indicating that the second electronic device remains on an enhanced multi-link single radio (eMLSR) link.

[0020] Note that the information can include: a duration during which the second electronic device remains on the eMLSR link; an end of a physical layer protocol data unit (PPDU) used for coordinated transmission; an end of a current transmission opportunity (TXOP); or an indication that the second electronic device needs to wait until at least another frame addressed to the second electronic device before an end of the current TXOP. For example, the indication can include a flag in the ICF. In some embodiments, the information can be included in: a trigger frame; or an aggregate control (A-Control) field of a data or management frame.

[0021] Other embodiments provide integrated circuits (such as interface circuits) for use with electronic devices or second electronic devices. These integrated circuits can perform at least some of the operations described above.

[0022] Other embodiments provide a second electronic device that performs operations corresponding to at least some of the operations performed by the electronic device. For example, the second electronic device may include: an antenna node communicatively coupled to the antenna; and an interface circuit communicatively coupled to the antenna node, the interface circuit communicating with the electronic device. During operation, the interface circuit receives information in association with the electronic device instructing the second electronic device to remain on the eMLSR link.

[0023] It should be noted that the second electronic device can remain on the eMLSR link for a predefined threshold time. When no indication of an incoming PPDU addressing the second electronic device is detected at the end of the predefined threshold time, the interface circuitry can switch to listen operation.

[0024] Other embodiments provide a computer-readable storage medium for use with an electronic device or a second electronic device. When the electronic device or the second electronic device executes program instructions stored in the computer-readable storage medium, the program instructions cause the electronic device or the second electronic device to perform at least some of the aforementioned operations of the electronic device or the second electronic device.

[0025] Other implementations provide methods. These methods include at least some of the foregoing operations performed by an electronic device or a second electronic device.

[0026] In the third set of embodiments, an electronic device is described. This electronic device includes: an antenna node communicatively coupled to an antenna; and an interface circuit communicatively coupled to the antenna node, the interface circuit communicating with a second electronic device. During operation, the interface circuit determines that the second electronic device is busy on a first eMLSR link (using peer-to-peer communication). Then, when the second electronic device is busy on the first eMLSR link, the interface circuit prevents the use of the second eMLSR link to transmit to or receive from the second electronic device.

[0027] It should be noted that before transmitting a data frame on a given eMLSR link, including the first eMLSR link or the second eMLSR link, the interface circuitry can address a second electronic device to provide an ICF.

[0028] Other embodiments provide integrated circuits (such as interface circuits) for use with electronic devices or second electronic devices. These integrated circuits can perform at least some of the operations described above.

[0029] Other implementations provide a second electronic device. For example, the second electronic device may include: an antenna node communicatively coupled to the antenna; and an interface circuit communicatively coupled to the antenna node, the interface circuit communicating with the electronic device. During operation, the interface circuit determines that the electronic device is busy on the first eMLSR link (using peer-to-peer communication). Then, when the electronic device is busy on the first eMLSR link, the interface circuit prevents the use of the second eMLSR link to send to or receive data from the electronic device.

[0030] It should be noted that before receiving a data frame on a given eMLSR link, including the first eMLSR link or the second eMLSR link, the interface circuitry can receive an ICF in association with the electronic device and can respond with an ICR.

[0031] Other embodiments provide a computer-readable storage medium for use with an electronic device or a second electronic device. When the electronic device or the second electronic device executes program instructions stored in the computer-readable storage medium, the program instructions cause the electronic device or the second electronic device to perform at least some of the aforementioned operations of the electronic device or the second electronic device.

[0032] Other implementations provide methods. These methods include at least some of the foregoing operations performed by an electronic device or a second electronic device.

[0033] The purpose of providing this invention is to illustrate some exemplary embodiments in order to provide a basic understanding of some aspects of the subject matter described herein. Therefore, it should be understood that the features described above are merely examples and should not be construed as narrowing the scope or essence of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description

[0034] The accompanying drawings are for illustrative purposes and are intended only to provide examples of possible structures and arrangements of the disclosed systems and technologies for intelligently and efficiently managing communication among multiple associated user devices. These drawings are in no way intended to limit any changes in form and detail that may be made to the embodiments by those skilled in the art without departing from the spirit and scope of the embodiments. The embodiments will be readily understood from the following detailed description taken in conjunction with the accompanying drawings, wherein similar reference numerals denote similar structural elements.

[0035] Figure 1 This is a block diagram illustrating an example of communication between electronic devices.

[0036] Figure 2 This is a block diagram illustrating an example of communication between electronic devices.

[0037] Figure 3 This is an example used for... Figure 1 or Figure 2 The flowchart shows an example method for providing GCR BAR in electronic devices.

[0038] Figure 4 This is an example used for... Figure 1 or Figure 2 A flowchart of an example method for an electronic device to receive a GCR BAR.

[0039] Figure 5 This is an example Figure 1 or Figure 2 An illustration of an example of communication between electronic devices.

[0040] Figure 6 This is an example used for... Figure 1 or Figure 2 A flowchart illustrating an example method for providing information to electronic devices.

[0041] Figure 7 This is an example used for... Figure 1 or Figure 2 A flowchart illustrating an example method for an electronic device to receive information.

[0042] Figure 8 This is an example Figure 1 or Figure 2 An illustration of an example of communication between electronic devices.

[0043] Figure 9 This is an example used for... Figure 1 or Figure 2 A flowchart illustrating an example method whereby an electronic device selectively blocks sending to or receiving from a second electronic device.

[0044] Figure 10 This is an example Figure 1 or Figure 2 An illustration of an example of communication between electronic devices.

[0045] Figure 11 This is a diagram illustrating existing communication between electronic devices.

[0046] Figure 12 This is an example Figure 1 or Figure 2 An illustration of an example of communication between electronic devices.

[0047] Figure 13 This is an illustration of an example of a protected GCR BAR or GCR MU-BAR.

[0048] Figure 14This is an illustration of an example of a protected GCR BAR or GCR MU-BAR.

[0049] Figures 15 to 18 This is a diagram illustrating an example of communication between electronic devices.

[0050] Figure 19 This is a diagram illustrating existing communication between electronic devices.

[0051] Figures 20 to 22 This is a diagram illustrating an example of communication between electronic devices.

[0052] Figure 23 Examples of some embodiments according to this disclosure are illustrated. Figure 1 Examples of electronic devices.

[0053] It should be noted that similar reference numerals throughout the accompanying drawings refer to the corresponding components. Furthermore, multiple instances of the same component are identified by a common prefix, which is separated from the instance number by a hyphen. Detailed Implementation

[0054] In a first set of embodiments, an electronic device is described. This electronic device may include: an antenna node communicatively coupled to an antenna; and an interface circuit communicatively coupled to the antenna node, the interface circuit communicating with a second electronic device. During operation, the interface circuit can address at least the second electronic device providing a GCR BAR, wherein the GCR BAR indicates that the GCR BAR is protected. Note that the GCR BAR may include a GCR MU-BAR.

[0055] These communication technologies enhance the security of group-addressed frames by protecting GCR BAR frames. These capabilities prevent attackers from injecting data with invalid serial numbers and / or corrupting the scoreboard or reordering buffer. Therefore, the communication technologies prevent incorrect frame reordering and / or aid in the recovery of associated content. In these ways, these communication technologies improve the user experience when using the electronic device and / or a secondary electronic device.

[0056] Furthermore, in a second set of embodiments, an electronic device is described. This electronic device may include: an antenna node communicatively coupled to an antenna; and an interface circuit communicatively coupled to the antenna node, the interface circuit communicating with a second electronic device. During operation, the interface circuit may address information provided by the second electronic device instructing the second electronic device to remain on the eMLSR link. It should be noted that this information may include: the duration for which the second electronic device remains on the eMLSR link during its operation; the end of a PPDU for coordinated transmission; the end of the current TXOP; or an indication that the second electronic device needs to wait for at least another frame addressed to the second electronic device before the end of the current TXOP.

[0057] By conveying information, these communication technologies ensure that the second electronic device can take advantage of the low latency benefits of eMLSR operation. Notably, the communication technologies ensure that the second electronic device remains on the eMLSR link for a predefined time. Therefore, the communication technologies can help ensure predictable operation and performance of the eMLSR link, for example, by preventing the second electronic device from prematurely switching back to listening operation. In these ways, these communication technologies can improve the user experience when using the electronic device and / or the second electronic device.

[0058] In the third set of embodiments, an electronic device is described. This electronic device may include: an antenna node communicatively coupled to an antenna; and an interface circuit communicatively coupled to the antenna node, the interface circuit communicating with a second electronic device. During operation, the interface circuit may determine that the second electronic device is busy on a first eMLSR link (using peer-to-peer communication). Then, when the second electronic device is busy on the first eMLSR link, the interface circuit may prevent transmission to or reception from the second electronic device using the second eMLSR link. It should be noted that the interface circuit may address the second electronic device to provide an ICF before transmitting a data frame on a given eMLSR link including either the first or second eMLSR link.

[0059] By determining that the second electronic device is busy, these communication technologies ensure that communication with the second electronic device (e.g., via an eMLSR link) is robust and reliable. Therefore, the communication technologies help ensure predictable operation and performance of communication with the second electronic device. In these ways, these communication technologies can improve the user experience when using the electronic device and / or the second electronic device.

[0060] In the following discussion, users may include: individuals, organizations, companies, government agencies, for-profit business entities, non-profit entities, or groups of one or more individuals.

[0061] It should be noted that communication technologies can be used during wired or wireless communication between electronic devices, depending on the communication protocol, such as a communication protocol compatible with the IEEE 802.11 standard (which is sometimes referred to as Wi-Fi). However, these communication technologies can also be used with a wide variety of other communication protocols and can also be used in electronic devices (such as portable electronic devices or mobile devices) that can combine a variety of different radio access technologies (RATs) to provide connectivity through different wireless networks that offer different services and / or capabilities.

[0062] The electronic device and / or the second electronic device may include hardware and software to support WPAN according to Wireless Personal Area Network (WPAN) communication protocols, such as those standardized by the Bluetooth Special Interest Group and / or those developed by Apple (Cupertino, California) and known as Apple Wireless Direct Link (AWDL). Furthermore, the electronic device and / or the second electronic device may communicate via: Wireless Wide Area Network (WWAN), Wireless Metropolitan Area Network (WMAN), WLAN, Near Field Communication (NFC), cellular phone or data network (such as using third-generation (3G) communication protocols, fourth-generation (4G) communication protocols (e.g., LTE, LTE-A Advanced, or LTE-5), fifth-generation (5G) communication protocols, or other currently or future advanced cellular communication protocols) and / or another communication protocol. In some embodiments, the communication protocol includes peer-to-peer communication technologies.

[0063] In some embodiments, the electronic device and / or the second electronic device may also operate as part of a wireless communication system, which may include a set of client devices, also referred to as site or client electronic devices, interconnected to an access point, for example, as part of a WLAN, and / or interconnected with each other, for example, as part of a WPAN and / or a “self-organizing” wireless network such as Wi-Fi Direct. In some embodiments, the client devices may be any electronic device capable of communicating via WLAN technology (e.g., according to a WLAN communication protocol). Furthermore, in some implementations, the WLAN technology may include a Wi-Fi (or more generally, WLAN) wireless communication subsystem or radio component, and the Wi-Fi radio component may implement IEEE 802.11 technology, such as one or more of the following: IEEE 802.11a; IEEE 802.11b; IEEE 802.11g; IEEE 802.11-2007; IEEE 802.11n; IEEE 802.11-2012; IEEE 802.11-2016; IEEE 802.11ac; IEEE 802.11ax, IEEE 802.11ba, IEEE 802.11be, IEEE 802.11me, IEEE 802.11bn, IEEE 802.11bx, IEEE 802.11mf, or other currently or future IEEE 802.11 technologies.

[0064] It should be noted that the electronic device and / or the second electronic device may use multi-user transmission (such as OFDMA) and / or multiple-input multiple-output (MIMO).

[0065] In some implementations, the electronic device and / or the second electronic device may act as a communication hub, providing access to WLAN and / or WWAN, and thus access to a wide variety of services supported by various applications running on the electronic device and / or the second electronic device. Therefore, the electronic device and / or the second electronic device may include an "access point" that wirelessly communicates with other electronic devices (such as using Wi-Fi) and provides access to another network (such as the Internet) via IEEE 802.3 (sometimes referred to as "Ethernet"). It should be noted that the access point may be a physical access point implemented on a computer or electronic device, or a virtual or "software" access point. However, in other implementations, the electronic device and / or the second electronic device may not be an access point.

[0066] Additionally, it should be understood that the electronic devices described herein can be configured as multimode wireless communication devices capable of communicating via different 3G and / or second-generation (2G) RATs. In these scenarios, the multimode electronic devices or UEs can be configured to preferentially attach to LTE networks, which offer faster data rate throughput, compared to other 3G legacy networks that offer lower data rate throughput. For example, in some specific implementations, the multimode electronic devices are configured to fall back to 3G legacy networks, such as Evolved High-Speed ​​Packet Access (HSPA+) networks or Code Division Multiple Access (CDMA) 2000 Evolved Data Only (EV-DO) networks, when LTE and LTE-A networks are otherwise unavailable. More generally, the electronic devices described herein are capable of communicating with other currently or future cellular telephone technologies.

[0067] According to the various embodiments described herein, the terms "wireless communication device," "electronic device," "mobile device," "mobile station," "wireless station," "wireless access point," "site," "access point," and "user equipment (UE)" may be used herein to describe one or more consumer electronic devices that can perform processes associated with the various embodiments of this disclosure.

[0068] Figure 1A block diagram illustrating an example of an electronic device for wireless communication is presented. It is noteworthy that one or more electronic devices 110 (such as a smartphone, laptop computer, notebook computer, tablet computer, or other such electronic device) and access point 112 can wirelessly communicate in a WLAN using the IEEE 802.11 communication protocol. Therefore, electronic device 110 may be associated with or have one or more connections to access point 112. For example, electronic device 110 and access point 112 can wirelessly communicate by: detecting each other by scanning a wireless channel, sending and receiving beacons or (equivalently) beacon frames on a wireless channel, establishing a connection (e.g., by sending a connection request), and / or sending and receiving packets or frames (packets or frames may include requests and / or additional information such as data as a payload). It should be noted that access point 112 may provide access to a network such as the Internet via the Ethernet protocol and may be a physical access point implemented on a computer or electronic device or a virtual or “software” access point. In the following discussion, electronic device 110 is sometimes referred to as a “client,” “site,” or “receiving electronic device.”

[0069] See below for reference Figure 23 Furthermore, electronic device 110 and access point 112 may include subsystems such as a networking subsystem, a memory subsystem, and a processor subsystem. Additionally, electronic device 110 and access point 112 may include a radio component 114 within the networking subsystem. More generally, electronic device 110 and access point 112 may include any electronic device with a networking subsystem (or may be included within any electronic device with a networking subsystem) that enables electronic device 110 and access point 112 to communicate wirelessly with another electronic device. This may include transmitting beacon frames on a wireless channel to enable the electronic devices to make initial contact with or detect each other, followed by exchanging subsequent data / management frames (such as connection requests) to establish a connection, configure security options (e.g., IPSec), and send and receive packets or frames via the connection.

[0070] like Figure 1 As can be seen, wireless signals 116 (represented by sawtooth lines) are transmitted by one or more radio components 114-1 and 114-2 in electronic device 110-1 and access point 112, respectively. For example, as previously mentioned, electronic device 110-1 and access point 112 can exchange packets or frames using the Wi-Fi communication protocol in a WLAN. See below for reference. Figures 2 to 22As further illustrated, one or more radio components 114-1 may receive radio signals 116 transmitted by one or more radio components 114-2 via one or more links between electronic device 110-1 and access point 112. Alternatively, one or more radio components 114-1 may transmit radio signals 116 received by one or more radio components 114-2.

[0071] In some implementations, the wireless signal 116 is transmitted by one or more radio components 114 in electronic device 110 and access point 112, respectively. For example, one or more radio components 114-1 and 114-3 may receive the wireless signal 116 transmitted by one or more radio components 114-2 via one or more links between electronic device 110-1 and 110-2 and access point 112.

[0072] It should be noted that the one or more radio components 114-1 may consume additional power in a higher power mode. If the one or more radio components 114-1 remain in a higher power mode even when not transmitting or receiving packets or frames, the power consumption of electronic device 110-1 may increase unnecessarily. Therefore, electronic device 110 may include a wake-up radio component (WUR) 118 that listens for and / or receives wake-up frames (and / or other wake-up communications) from, for example, access point 112. When a particular electronic device (such as electronic device 110-1) receives a wake-up frame, WUR 118-1 may selectively wake up radio component 114-1, for example, by providing a wake-up signal that selectively transitions at least one of the one or more radio components 114-1 from a low-power mode to a high-power mode.

[0073] IEEE 802.11be has proposed the use of multiple concurrent links between electronic devices, such as access point 112 and one or more electronic devices 110. For example, as Figure 2As shown, this figure presents a block diagram illustrating an example of an electronic device for wireless communication. Access point 112 may be an Access Point Multilink Device (MLD) comprising multiple access points 210, which are co-hosted or co-located within access point 112. In this discussion, "co-hosted" or "co-located" means that access points 210 are physically or virtually implemented in the same access point MLD, or attached to the same access point MLD. It should be noted that this meaning of "co-hosted" does not imply that access points 210 have the same primary 20MHz channel. Access point 210 may have an associated Basic Service Set Identifier (BSSID) 212 and Media Access Control (MAC) and Physical (PHY) layers (including separate radio components that may be included in the same or different integrated circuits). It should be noted that access point 112 may have an ML entity 214, which has an MLD MAC address, an ML identifier, a Service Set Identifier (SSID), and provides security for access point 210.

[0074] Furthermore, access point 210 may have concurrent links 216 in different frequency bands than station 218 in at least electronic device 110-1 (which is a non-access point MLD) (such as link 216-1 in the 2.4 GHz band with link identifier 1, link 216-2 in the 5 GHz band with link identifier 2, and link 216-3 in the 6 GHz band with link identifier 3). These stations may have associated lower MAC and PHY layers (including separate radio components that may be included in the same or different integrated circuits). Additionally, electronic device 110-1 may have an ML entity 220 that possesses an MLD MAC address.

[0075] For example, an access point MLD may have three radio components. One radio component may operate on the 2.4 GHz band, and the other radio components may operate on the 5 / 6 GHz band. The access point MLD may form three access points 210, which operate on the 2.4 GHz channel, the 5 GHz channel, and the 6 GHz channel, respectively. The three access points 210 may operate independently, each access point having at least one BSS, and these BSSs having different BSSIDs 212. (Although...) Figure 2An access point MLD with three access points 210 is illustrated, but more generally, an access point MLD may include up to 15 access points, one or more of which are located in a given frequency band. Furthermore, each access point 210 may be adapted to a conventional non-access point site as well as a non-access point MLD site 218. Moreover, each access point 210 may use its own BSSID to transmit its own beacon frames. Additionally, an access point MLD may have an ML entity 214 identified by an MLD address (such as an MLD MAC address). This MAC address can be used to pair with the ML entity 220 of the associated non-access point MLD site 218.

[0076] Furthermore, a non-access point MLD site (e.g., electronic device 110-1) may have two or three radio components. One radio component may operate in the 2.4 GHz band, and the other radio components may operate in the 5 / 6 GHz band. When a non-access point MLD establishes an ML association with an access point MLD, it may create up to three sites 218, each associated with one access point 210 within the access point MLD. Each site 218 may have a different air interface MAC address 222. The non-access point MLD may also have an ML entity 220 identified by another MLD address (such as another MLD MAC address). This MLD MAC address can be used to pair with an ML entity 214 of the associated access point MLD.

[0077] Return to reference Figure 1 As previously mentioned, existing communication technologies may not protect GCR BAR frames. To address these issues, please refer to the following references. Figures 3 to 22 As further described, in the communication technology, access point 112 and / or electronic device 110-1 can perform the communication technology.

[0078] It is worth noting that access point 112 can address at least electronic device 110-1 providing a GCR BAR, where the GCRBAR indicates that the GCR BAR is protected. For example, the GCR BAR may include a GCR MU-BAR. Note that electronic device 110-1 may be a member of a GCR group.

[0079] The GCR BAR can be received by electronic device 110-1. Electronic device 110-1 can then address access point 112 to provide an M-BA. This M-BA can be protected. Access point 112 can then receive the M-BA. Note that the M-BA may include a per-AID TID information field identified by a reserved value in the AID TID information subfield, and each AID TID information subfield may include information associated with the GCR. This information may include the GCR group address and / or TID information.

[0080] In some implementations, access point 112 may address at least electronic device 110-1 and provide an ICF prior to the GCR BAR. The ICF may include information about one or more MAC headers for one or more subsequent GCR data frames. For example, this information may include: a valid SN range, power management bits, additional data bits, EOSP bits, or HT control fields for one or more MAC headers. Additionally, access point 112 may receive an ICR in association with electronic device 110-1 and in response to the ICF. The ICR may be protected. Note that the ICF may include: a multi-user request to send frame, BSRP, trigger frame, BAR frame, block acknowledgment frame, or another control frame. In some implementations, the ICF may be included in an A-MPDU. The ICF may be unicast and may be protected using a key for the GCR group including electronic device 110-1. Furthermore, the RA for the ICF or the user information field in the ICF may include the group address of the GCR group.

[0081] In addition, the GCR BAR may include information about one or more MAC headers of one or more subsequent GCR data frames, and this information may include: the valid SN range of one or more MAC headers, power management bits, additional data bits, EOSP bits, or HT control fields.

[0082] In some implementations, electronic device 110-1 may verify one or more GCR data frames, at least in part, based on this information. For example, verification may be at least in part based on the ICF's MIC.

[0083] Alternatively or additionally, access point 112 may address electronic device 110-1 to provide information instructing a second electronic device to remain on the eMLSR link. This information may be received by electronic device 110-1.

[0084] It should be noted that this information may include: the duration during which the second electronic device remains on the eMLSR link; the end of the PPDU used for coordinated transmission; the end of the current TXOP; or an indication that electronic device 110-1 needs to wait for at least another frame addressed to electronic device 110-1 before the end of the current TXOP. For example, this indication may include a flag in the ICF. In some embodiments, the information may be included in: a trigger frame; or the A control field of a data or management frame.

[0085] In some implementations, electronic device 110-1 may remain on the eMLSR link for a predefined threshold time. When no indication of an incoming PPDU addressed to electronic device 110-1 is detected at the end of the predefined threshold time, electronic device 110-1 may switch to listening operation.

[0086] Alternatively or additionally, access point 112 determines that electronic device 110-1 is busy on the first eMLSR link (using peer-to-peer communication). Then, when electronic device 110-1 is busy on the first eMLSR link, access point 112 may prevent transmission to or reception from electronic device 110-1 via the second eMLSR link.

[0087] It should be noted that before transmitting a data frame on a given eMLSR link, including the first eMLSR link or the second eMLSR link, access point 112 can address electronic device 110-1 to provide ICF.

[0088] In some implementations, electronic device 110-1 can determine that access point 112 is busy on the first eMLSR link (using peer-to-peer communication), rather than access point 112 determining that electronic device 110-1 is busy. Then, when access point 112 is busy on the first eMLSR link, electronic device 110-1 prevents sending to or receiving from access point 112 via the second eMLSR link.

[0089] It should be noted that before receiving a data frame on a given eMLSR link, including the first eMLSR link or the second eMLSR link, the electronic device 110-1 may receive an ICF associated with the access point 112 and may respond with an ICR.

[0090] In summary, the disclosed communication technology facilitates improved communication between access point 112 and electronic device 110-1. For example, the communication technology can improve the security of group addressing frames (such as GCR BARs). Furthermore, the communication technology can ensure that electronic device 110-1 remains on the eMLSR link for a predefined time. Moreover, the communication technology can ensure that communication with electronic device 110-1 (e.g., via the eMLSR link) is robust and reliable. Therefore, the communication technology helps ensure predictable operation and performance of communication with access point 112 and electronic device 110-1. In these ways, the communication technology can improve user experience and customer satisfaction when using access point 112 and / or electronic device 110-1.

[0091] While the foregoing discussion illustrates communication between access point 112 and electronic device 110-1, in other embodiments, the roles of access point 112 and electronic device 110-1 may be reversed in the communication technology. For example, electronic device 110-1 may include a second access point, and access point 112 may be a second electronic device, which is a station or client associated with the second access point. Alternatively, in some embodiments, communication technology is performed between electronic device 110-1 and electronic device 110-2.

[0092] It should be noted that access point 112 and one or more electronic devices (such as electronic devices 110-1 and / or 110-2) may be compatible with the IEEE 802.11 standard, which includes trigger-based channel access (such as IEEE 802.11ax). However, access point 112 and one or more electronic devices may communicate with one or more legacy electronic devices that are not compatible with the IEEE 802.11 standard (i.e., do not use multi-user trigger-based channel access). In some embodiments, access point 112 and one or more electronic devices use multi-user transmission (such as OFDMA). For example, the one or more radio components 114-2 may provide one or more trigger frames to the one or more electronic devices. Furthermore, in response to receiving the one or more trigger frames, the one or more radio components 114-1 may provide one or more group or block acknowledgments to the one or more radio components 114-2. For example, the one or more radio components 114-1 may provide one or more group acknowledgments during an associated allocation time slot and / or in an allocation channel within one or more group acknowledgments. However, in some embodiments, one or more electronic devices in electronic device 110 may individually provide acknowledgments to the one or more radio components 114-2. Therefore, the one or more radio components 114-1 (and more generally, radio components 114 in electronic devices 110-1 and / or 110-2) can provide one or more acknowledgments to the one or more radio components 114-2.

[0093] In the described implementation, processing packets or frames in one of the electronic devices 110 and access point 112 includes: receiving a wireless signal 116 that encodes the packets or frames; decoding / extracting packets or frames from the received wireless signal 116 to obtain packets or frames; and processing packets or frames to determine information contained in the packets or frames (such as data in a payload).

[0094] Generally speaking, communication via WLAN in communication technology can be characterized by a variety of communication performance metrics. For example, communication performance metrics may include one or more of the following: RSSI, data rate, data rate of successful communication (sometimes called "throughput"), latency, error rate (such as retry rate or retransmission rate), mean square error of the equalized signal relative to the equalization target, inter-symbol interference, multipath interference, signal-to-noise ratio (SNR), eye diagram width, the ratio of the number of bytes successfully transmitted during a predetermined or predefined time interval (such as, for example, a time interval between 1 second and 10 seconds) to the estimated maximum number of bytes that can be transmitted during that predetermined or predefined time interval (where the latter is sometimes referred to as the "capacity" of the communication channel or link), and / or the ratio of the actual data rate to the estimated data rate (sometimes called "utilization").

[0095] Although we Figure 1The network environment illustrated is described using an example, but in alternative embodiments, different numbers and / or types of electronic devices may be present. For instance, some embodiments may include more or fewer electronic devices. In other embodiments, different electronic devices may send and / or receive packets or frames. In some embodiments, multiple links may be used during communication between electronic devices 110. Therefore, one electronic device among electronic devices 110 may perform operations in the communication technology.

[0096] Figure 3 A flowchart illustrating an example method 300 for providing a GCR BAR is presented. This method can be provided by an electronic device (such as...) Figure 1 The method is executed at access point 112. For example, method 300 can be executed by... Figure 1 This is achieved through the interface circuit in access point 112. Note that this electronic device interacts with a second electronic device (such as...). Figure 1 Communication between electronic devices 110-1 (which can be a site or client associated with access point 112) and the IEEE 802.11 communication protocol is compatible.

[0097] During operation, the electronic device can address at least a second electronic device providing a GCR BAR (operation 310), wherein the GCR BAR indicates that the GCR BAR is protected.

[0098] Then, the electronic device can receive the M-BA in association with the second electronic device (operation 312).

[0099] It should be noted that GCR BAR may include GCR MU-BAR.

[0100] Furthermore, the indication may be included in a reserved bit in the GCR BAR. For example, the reserved bit may include bit 0, or at least one of bits 5 to 11 in the BAR control field. Moreover, the GCR BAR may use the reserved bit to indicate a key identifier.

[0101] Additionally, the GCR BAR may include PN and MIC. For example, PN and MIC may be included in or after the BAR information field following the GCR group address. Note that the BAR information field may include padding after MIC.

[0102] In some implementations, the M-BA may be protected. It should be noted that the M-BA may include a per-AID TID information field identified by a reserved value in the AID TID information subfield, and each AID TID information subfield may include information associated with the GCR. This information may include the GCR group address and / or TID information.

[0103] In addition, the second electronic device can be a member of the GCR group.

[0104] Furthermore, the GCR BAR may include information about one or more MAC headers for one or more subsequent GCR data frames, and this information may include: the valid SN range of one or more MAC headers, power management bits, additional data bits, EOSP bits, or HT control fields.

[0105] In some implementations, the second electronic device may optionally perform one or more additional operations (operation 314). For example, the interface circuitry may address at least the second electronic device and provide an ICF prior to the GCR BAR. The ICF may include information about one or more MAC headers for one or more subsequent GCR data frames. For example, this information may include: the valid SN range, power management bits, additional data bits, EOSP bits, or HT control fields of one or more MAC headers. Additionally, the interface circuitry may be associated with the second electronic device and receive an ICR in response to the ICF. The ICR may be protected. Note that the ICF may include: a multi-user request to send frame, a BSRP, a trigger frame, a BAR frame, a block acknowledgment frame, or another control frame. In some implementations, the ICF may be included in an A-MPDU. The ICF may be unicast and may be protected using a key for the GCR group that includes the second electronic device. Furthermore, the RA for the ICF or the user information field in the ICF may include the group address of the GCR group.

[0106] Figure 4 A flowchart illustrating an example method 400 for receiving a GCR BAR is presented. This method can be performed by a second electronic device (such as...) Figure 1 The electronic device 110-1 in the system (which can be a site or client associated with access point 112) performs the operation. For example, method 300 can be performed by... Figure 1 This is achieved through the interface circuit in electronic device 110-1. Note that the second electronic device and the electronic device (such as...) Figure 1 Communication between access points 112 in the system is compatible with the IEEE 802.11 communication protocol.

[0107] During operation, the second electronic device may receive the GCR BAR (operation 410) in association with the electronic device, wherein the GCR BAR indicates that the GCR BAR is protected.

[0108] The interface circuit can then address the electronic device to provide the M-BA (operation 412). The M-BA can be protected.

[0109] In some implementations, the second electronic device may optionally perform one or more additional operations (operation 414). For example, the interface circuitry may verify one or more GCR data frames, at least in part, based on this information. For example, the verification may be at least in part based on the ICF's MIC.

[0110] exist Figure 5 The diagram also illustrates a communication technique, presenting a flowchart illustrating an example of communication between electronic device 110-1 and access point 112. During operation, one or more interface circuits (or interface circuit systems) 510 in access point 112 can be addressed by electronic device 110-1 to provide GCR BAR 512, wherein GCR BAR 512 indicates that GCR BAR 512 is protected 514.

[0111] The GCR BAR512 can be received by one or more interface circuits (or interface circuit systems) 516 in electronic device 110-1. Then, one or more interface circuits 516 can address access point 112 to provide M-BA 518.

[0112] Figure 6 A flowchart illustrating an example method 600 for providing information is presented. This method can be provided by an electronic device (such as...) Figure 1 The method is executed at access point 112. For example, method 600 can be executed by... Figure 1 This is achieved through the interface circuit in access point 112. Note that this electronic device interacts with a second electronic device (such as...). Figure 1 Communication between electronic devices 110-1 (which can be a site or client associated with access point 112) and the IEEE 802.11 communication protocol is compatible.

[0113] During operation, the electronic device can address information provided by the second electronic device (operation 610) that instructs the second electronic device to remain on the enhanced multilink single radio (eMLSR) link.

[0114] Then, the electronic device can receive the confirmation in association with the second electronic device (operation 612).

[0115] It should be noted that this information may include: the duration during which the second electronic device remains on the eMLSR link; the end of the PPDU used for coordinating transmission; the end of the current TXOP; or an indication that the second electronic device needs to wait for at least another frame addressed to the second electronic device before the end of the current TXOP. For example, this indication may include a flag in the ICF. In some implementations, the information may be included in: a trigger frame; or the A control field of a data or management frame.

[0116] Figure 7A flowchart illustrating an example method 700 for receiving information is presented. This method can be implemented by a second electronic device (such as...) Figure 1 The electronic device 110-1 in the process (which can be a site or client associated with access point 112) performs the operation. For example, method 700 can be performed by... Figure 1 This is achieved through the interface circuit in electronic device 110-1. Note that the second electronic device and the electronic device (such as...) Figure 1 Communication between access points 112 in the system is compatible with the IEEE 802.11 communication protocol.

[0117] During operation, the second electronic device may receive information in association with the electronic device instructing the second electronic device to remain on the eMLSR link (operation 710).

[0118] Then, the second electronic device can address the electronic device to provide confirmation (operation 712).

[0119] In some implementations, the second electronic device may optionally perform one or more additional operations (operation 714). For example, the second electronic device may remain on the eMLSR link for a predefined threshold time. When no indication of an incoming PPDU addressed to the second electronic device is detected at the end of the predefined threshold time, the second electronic device may switch to listening operation.

[0120] exist Figure 8 The diagram also illustrates a communication technology, presenting a flowchart illustrating an example of communication between electronic device 110-1 and access point 112. During operation, one or more interface circuits (or interface circuit systems) 810 in access point 112 can be addressed by electronic device 110-1 providing information 812 instructing a second electronic device to remain on eMLSR link 814.

[0121] Information 812 may be received by one or more interface circuits (or interface circuit systems) 816 in electronic device 110-1. Then, one or more interface circuits 816 may address access point 112 to provide acknowledgment (ACK) 818.

[0122] Figure 9 A flowchart illustrating an example method 900 for selectively blocking transmission or reception is presented. This method can be implemented by an electronic device (such as...) Figure 1 The method is executed at access point 112. For example, method 900 can be executed by... Figure 1 This is achieved through the interface circuitry at access point 112. Alternatively, method 900 can be implemented by... Figure 1 This is achieved through the interface circuit in electronic device 110-1. Note that this electronic device interacts with a second electronic device (such as...). Figure 1The electronic device 110-1 in the device, which may be a site or client associated with access point 112, can communicate with access point 112 in a manner compatible with the IEEE 802.11 communication protocol.

[0123] During operation, the electronic device can determine that the second electronic device is busy on the first eMLSR link (using peer-to-peer communication) (Operation 910). Then, when the second electronic device is busy on the first eMLSR link, the electronic device can prevent sending to or receiving from the second electronic device using the second eMLSR link (Operation 912).

[0124] In some implementations, the second electronic device may optionally perform one or more additional operations (operation 914). For example, before transmitting a data frame on a given eMLSR link that includes the first eMLSR link or the second eMLSR link, the electronic device may address the second electronic device to provide an ICF.

[0125] Furthermore, before receiving a data frame on a given eMLSR link, including either the first or second eMLSR link, the second electronic device may receive an ICF associated with the electronic device. After receiving the ICF, the second electronic device may respond with an ICR.

[0126] In method 300 ( Figure 3 Method 400 Figure 4 Method 600 Figure 6 Method 700 Figure 7 In some embodiments of method 900, additional or fewer operations may be present. Additionally, one or more distinct operations may be included. Furthermore, the order of operations may be changed, and / or two or more operations may be combined into a single operation or performed at least partially in parallel.

[0127] exist Figure 10 The diagram further illustrates a communication technique, presenting a flowchart illustrating an example of communication between electronic device 110-1 and access point 112. During operation, one or more interface circuits (or interface circuit systems) 1010 in access point 112 can determine that electronic device 110-1 is busy (using peer-to-peer communication) 1012 on the first eMLSR link. Then, when electronic device 110-1 is busy 1012 on the first eMLSR link, access point 112 can prevent 1014 from transmitting to or receiving from electronic device 110-1 on or using the second eMLSR link.

[0128] Furthermore, before transmitting data frame 1022 on a given eMLSR link (such as the first eMLSR link), access point 112 can address electronic device 110-1 to provide ICF 1016. This ICF can be received by one or more interface circuits (or interface circuit systems) 1018 in electronic device 110-1. Then, one or more interface circuits 1018 can address access point 112 to provide ICR 1020. Next, after receiving ICR 1020, one or more interface circuits 1010 can address electronic device 110-1 to provide data frame 1022, which can be received by one or more interface circuits 1018.

[0129] Although Figure 5 , Figure 8 and Figure 10 Communication between components is illustrated as unidirectional or bidirectional communication (e.g., lines with single or double arrows), but generally a given communication operation can be either unidirectional or bidirectional. Furthermore, although Figure 5 , Figure 8 and Figure 10 The operations in the example are illustrated as sequential, but in some implementations, at least some of these operations may be performed in parallel.

[0130] The implementation of the disclosed communication technology will now be described further. As previously discussed, in an attack, an attacker can move the block confirmation window to cause data loss at one or more receivers. For example, a forged GCR MU-BAR or data can be injected with an invalid SN, which may contaminate or otherwise corrupt the scoreboard and / or may corrupt the reordering buffer, which prevents incorrect frame reordering and / or may aid in the recovery of associated content. To address these vulnerabilities, the disclosed communication technology can protect group-addressed data and / or management frames and enables secure and fast GCR. Although the GCR service is used as an example in this disclosure, the disclosed communication technology can also be used to protect group-addressed data and / or management frames not associated with the GCR service.

[0131] In addition, such as Figure 11 As shown, this diagram illustrates an existing communication between electronic devices. In an existing or traditional unicast GCR BAR, different members of the GCR group can be polled for a Block Acknowledgment (BA) after data transmission. To protect this communication, a protected GCR BAR can be defined that requests a protected M-BA. This prevents attackers from manipulating the scoreboard with forged data.

[0132] Moreover, such as Figure 12 As shown in the figure, this illustrates an example. Figure 1 or Figure 2This illustration illustrates an example of communication between electronic devices. In some versions of IEEE 802.11 (e.g., IEEE 8021ax, IEEE 8021be, and / or IEEE 8021bn), a GCR MU-BAR trigger frame can be used to request simultaneous block acknowledgments from multiple members of a GCR group (such as GCR group member 1 and GCR group member 2, or GCR group member 3 and GCR group member 4) after data transmission. Alternatively, the GCR BAR can be used to request block acknowledgments from a less efficient site that is a member of a GCR group (such as GCR group member 5). To protect this communication, a protected GCR MU-BAR requesting the protected M-BA can be defined. This prevents attackers from manipulating the scoreboard with forged data.

[0133] This is Figure 13 The diagram illustrates an example of a protected GCR BAR or GCR MU-BAR. It is worth noting that... Figure 13 An implementation scheme for protecting a unicast GCR BAR is illustrated. For example, the GCR MU-BAR may be overridden by one or more protected trigger frames. The protected GCR BAR may include: a frame control field (which may be, for example, 2 octets), a duration field (which may be, for example, 2 octets), a receive address field (which may be, for example, 6 octets), a send address field (which may be, for example, 6 octets), a BAR control field (which may be, for example, 2 octets), a BAR information field (which may be, for example, variable in size), and / or a frame control sequence (FCS) field (receive address (which may be, for example, 4 octets)). Furthermore, one or more reserved bits in the BAR control field may be used to indicate whether the frame is a protected GCR BAR and / or to indicate a key identifier. For example, reserved bit 0 (B0) and / or reserved bits 5 to 11 (B5 to B11 or up to seven bits) may be used. In other specific implementations, one or more other bits may be used. Note that the BAR type (e.g., four bits) can be used to indicate: reserved (BAR type "0"), extended compression (BAR type "1"), compressed (BAR type "2"), multi-service identifier or TID (BAR type "3"), reserved (BAR type "4" or "5"), or GCR (BAR type "6").

[0134] Figure 14 Illustrations illustrating examples of protected GCR BARs or GCR MU-BARs are provided. It is worth noting that... Figure 14Examples illustrate the placement of protection information (such as the group number (PN), message integrity check (MIC), and / or optional padding) within or after the BAR information field of a GCR BAR frame. It is noteworthy that the PN, MIC (which can function as a checksum and can be enabled during association), and / or optional padding can be included after the GCR group address. Reserved bits in the BAR control field can be used to indicate the protected GCR BAR frame, and / or reserved bits can indicate the key identifier used to generate the MIC. It should be noted that a protected unicast GCR BAR or a protected group-addressed (broadcast) GCR MU-BAR may request a protected M-BA (instead of a block acknowledgment or GCR block acknowledgment), which can be sent to the access point. For example, the protected M-BA may include a special per-association identifier (AID) TID information field. Furthermore, the AID TID can be identified by, for example, a reserved value in the AID TID information subfield to carry GCR-related information, such as the GCR group address and / or TID information (which can be defined for traditional GCR block acknowledgments). Note that bits 0 to 15 (or 16 bits) can be used for block acknowledgment start sequence control, and bits 16 to 63 (or 48 bits) can be used for GCR group address.

[0135] Additionally, Figure 15 The illustration presents examples of communication between electronic devices. Figure 15 As shown, one or more implementations can be used to prevent attacks on the MAC header of data in the GCR. It is worth noting that because a legacy site (such as Group Member 1) may need to receive GCR data, the GCR data itself cannot be modified to protect the MAC header. Therefore, an attacker could, for example, insert a forged MAC header into the data to cause data loss by scrambling or disrupting the block acknowledgment window with a forged packet SN.

[0136] To address these vulnerabilities, an optional protected Initial Control Frame (ICF) can indicate information about the MAC header regarding subsequent GCR data. For example, it can indicate a valid SN range, power management bits (which may indicate a power-saving mode in the access point), additional data bits, the number of additional data frames, and / or an End of Service Period (EOSP) bit, such as in the High Throughput (HT) control field of the MAC header, allowing the receiver to verify this information using the ICF's MIC. It should be noted that the ICF can be a Multi-User Request to Transmit (MU-RTS), Buffer Status Report Polling (BSRP), trigger frame, BAR frame, block acknowledgment frame, or any protected control frame, such as those defined in IEEE 802.11bn or subsequent IEEE 802.11 standards. When protection is enabled by a site that is a member of the GCR group (e.g., using a protected ICF): the protected GCR BAR or protected GCR MU-BAR can be used to request a response from the site, and this response can be transmitted in the protected M-BA; and the site can discard GCR data with a SN outside the valid SN range indicated by the protected ICF. The same verification can also be used to discard forged GCR data with invalid values ​​(such as invalid power management bits, more data bits, EOSP bits, or HT control fields). Note that the site can optionally respond to the protected ICF with an optional Initial Control Response (ICR) frame, which can optionally be the protected ICR. In some implementations, an optional MIC can be used to protect the protected ICF. Furthermore, note that when more than a threshold number of errors are reported to the access point in the optional ICR, the access point can update its key so that an attacker can no longer generate a valid MIC. Note that group member 2 can be an ultra-high reliability (UHR) site.

[0137] Figure 16 and Figure 17 The illustrations present examples of communication between electronic devices. For example, such as... Figure 16 As shown, adjacent frames in a data sequence can be separated by a short inter-frame interval (SIFS) (e.g., a separation time (such as an SIFS burst)). Furthermore, as previously mentioned, the optional ICR can be protected or not (e.g., allowed-to-transmit (i.e., CTS) frames can be used). Alternatively, as... Figure 17As shown, an ICR may not be present. In these implementations, the ICF may be grouped with remaining frames: using SIFS bursts; or aggregated with Aggregated MAC Protocol Data Units (A-MPDUs). Within such an A-MPDU, the ICF may be repeated zero or more times anywhere within the A-MPDU, for example, for reliability. For example, multiple instances of the ICF may be included back-to-back (adjacent to each other) or may be distributed throughout the A-MPDU. In some implementations, the ICF may be located at the beginning of the A-MPDU. Figure 16 and Figure 17 Note that member 1 can be a traditional site, and member 2 can be a UHR site.

[0138] In addition, such as Figure 18 As shown, this diagram illustrates an example of communication between electronic devices. In an implementation where the ICF is included in the A-MPDU, the ICF can request an immediate response (such as a protected M-BA) from one or more addressing sites supporting the protected GCR service. This can be performed without a separate BAR. As previously mentioned, the ICF can be any protected control frame. When the control frame is a unicast frame or is included in a unicast frame (e.g., a GCR BAR frame), the key for the group-addressed frame can be used to protect the ICF to allow multiple sites to decode it. Furthermore, the resource allocation (RA) of the unicast frame can also be changed to a group address. Note that GCR group members can verify the ICF, at least in part, based on the key for the group-addressed frame. Note that to reduce overhead, the ICF can be implemented as a trigger frame for the M-BA, which can reduce overhead. Figure 18 Note that member 1 can be a traditional site, while members 2 and 3 can be UHR sites.

[0139] Figure 19Other implementations are illustrated in the figure, which presents an example of existing communication between electronic devices. It is worth noting that existing IEEE 802.11be rules have limitations on Enhanced Multilink Single Radio (eMLSR) operation and may not work well with eMLSR sites. (While IEEE 802.11be allows sites to operate simultaneously on multiple links using multiple radios in higher power mode, this can be expensive in terms of power consumption. Instead, a site can have one or more radios in eMLSR mode. This allows for lower power listening (or monitoring) until a higher power mode radio is needed.) For example, a non-access point MLD can be switched to listening operation on an eMLSR link. In some cases, the switch can occur after the eMLSR transition delay time most recently indicated by the non-access point MLD, for example, when the non-access point site does not detect a separately addressed frame in the PPDU corresponding to the Physical Start of Receive (PHY-RXSTART) indication, where RA is equal to the MAC address of the non-access point site attached to the non-access point MLD. This may prevent eMLSR sites from taking advantage of the low latency benefits of eMLSR operations from their link diversity. For example, GCR member 1 can provide block acknowledgment after a BAR is sent by the access point. However, GCR member 2 (which could be an IEEE 802.11be eMLSR site) can switch to listen mode when this happens. Therefore, GCR member 2 might miss subsequent BARs sent by the access point and thus might not provide block acknowledgment. In other words, the access point can transmit ICFs (such as BARs) to one or more sites. In response, a site can switch to a higher power mode. When a site receives a frame or packet not intended for use by that site, it can switch back to a lower power mode. However, in this process, a site (such as GCR member 2) might miss subsequent BAR frames intended for it.

[0140] Note that eMLSR enhancements can be implemented to address such scenarios. It is worth noting that the eMLSR used for data exchange with the access point may include one or more anomalies regarding when a transition (or switchback) to listening operation (e.g., low-power mode) is performed. Specifically, one or more anomalies may exist regarding when a non-access point MLD can switch back to listening operation on the EMLSR link. In some implementations, this reduces the chance of a site switching back prematurely. For example, the access point may command the site to remain on the link longer, for example, based at least in part on one or more of the following indications: duration information in the trigger frame (causing the non-access point station not to switch back to listening mode during the indicated duration); the More Trigger Frame (TF) field in the trigger frame (e.g., when set to "1," the non-access point station may wait for the next PPDU from the access point instead of immediately switching back to listening operation); the end of a PPDU for coordinated transmission (coordinated beamforming, i.e., C-BF, or coordinated spatial reuse, i.e., C-SR); or the aggregation of data frames or management frames. The end of the control (A control) field; the end of the current transmission opportunity (TXOP) (as indicated by or within the More Data subfield of the frame control field or the End of Service Period (EOSP) subfield of the Quality of Service (QoS) control field); when the medium or channel is idle (as indicated at least in part based on SIFS, Packet Inter-Frame Spacing (PIFS), or PHY-RXSTART); and / or a special user information field in the trigger frame (such as a user information field whose AID12 subfield is set to a currently reserved value (e.g., 2008-2044 or 2047-4094). Note that the special user information field may also set its AID12 subfield to 2046, thereby indicating an unallocated resource element (RU) in the baseline. Other values ​​may be used in other implementations. The content of this special user information field may command a single non-access point site (such as when the content includes its AID) or multiple non-access point sites (such as when the content includes a group address or a list of AIDs for the site). This content can also indicate the target SN that a non-access point site should receive before switching back to the eMLSR link for a listening operation.

[0141] In addition, it should be noted that after one or more of the above conditions are met, a non-access point site may switch back to listening operation, or it may switch back to listening mode if the site does not detect a PHY-RXSTART indication within a threshold time (such as the sum of aSIFSTime, aSlotTime, and aRxPHYStartDelay in IEEE 802.11be).

[0142] Figure 20 and Figure 21The illustration presents an example of communication between electronic devices. It is worth noting that... Figure 20 The illustration shows that one or more transmissions from the access point (such as a protected ICF, data, a GCR BAR, and / or a protected GCR BAR or MU-BAR) may include one or more of the disclosed indications. In response to a GCR-BAR, GCR group member 1 (which may be a legacy site) may provide a GCR block acknowledgment. GCR group member 2 (which may be a UHR site) may provide a protected ICR in response to a protected ICF. Furthermore, GCR group member 2 may, for example, wait on the link, at least in part, based on one or more of the disclosed indications, until it receives a protected GCR BAR or GCR MU-BAR. Additionally, GCR group member 2 may provide a protected M-BA, for example, in response.

[0143] Alternatively or additionally, access point 1 may provide a first ICF including one or more of the disclosed indications. Following the ICF may be a first C-BF PPDU. Similarly, access point 2 may provide a second ICF including one or more of the disclosed indications. Following the second ICF may be a second C-BF PPDU. It should be noted that in some cases, the first and second C-BF PPDUs may be simultaneously transmitted, for example, at least in part, based on coordinated beamforming or coordinated spatial reuse.

[0144] like Figure 21 As shown, site 1 associated with access point 1 may provide a first ICR, for example, in response to a first ICF from access point 1. Site 1 may remain on the link, for example, based at least in part on one or more indications of the first ICF (which has been previously discussed) or a second ICF from access point 2. After the first Coordinated Beamforming (C-BF) PPDU, site 1 may provide a first block acknowledgment. Site 2 associated with access point 2 may provide a second ICR, for example, in response to a second ICF from access point 2. Site 2 may remain on the link, for example, based at least in part on one or more indications of the ICF (which has been previously discussed). After the second C-BF PPDU, site 2 may provide a second block acknowledgment. It should be noted that in some specific implementations, the first block acknowledgment and the second block acknowledgment may be communicated concurrently.

[0145] like Figure 22As shown, this figure illustrates an example of communication between electronic devices. In some implementations, the communication technology can provide enhancements to the eMLSR used for data exchange on peer-to-peer (P2P) links. ICF / ICR can be used at the beginning of the TXOP for data exchange on peer-to-peer links. Data exchange can be permitted on any link between two eMLSR sites for low-latency data delivery (including GCR). When a transmitter determines that a receiver is busy on one eMLSR link used for peer-to-peer communication, the transmitter may not transmit to the receiver on another eMLSR link. For example, when the transmitter determines that the receiver is using eMLSR link 1, the transmitter may not use eMLSR link 2.

[0146] While the foregoing discussion exemplifies communication techniques using GCR services, more generally, these techniques can be used to protect information during wireless communication using group-addressed frames that employ one or more other communication protocols or services. For example, group-addressed frames may include: video streaming, audio streaming, group-addressed transmission without retries, etc.

[0147] Furthermore, while the foregoing embodiments illustrate a communication technique having a frame sequence including a GCR BAR or a GCR MU-BAR, in other embodiments of the communication technique, information in the communication technique (such as the valid SN of a GCR data frame) may be included in the initial control frame (such as in the MAC header) even if the sequence does not include a GCR BAR or a GCR MU-BAR.

[0148] In some implementations, the communication technology can be implemented at the physical layer and / or MAC layer.

[0149] It should be noted that the format of packets or frames transmitted during communication technology may include more or fewer bits, subfields, or fields. Alternatively or additionally, the position of information in these packets or frames may be changed. Therefore, the order of subfields or fields may be changed.

[0150] While the foregoing embodiments illustrate communication techniques using sub-bands, in other embodiments, the communication techniques may involve the simultaneous use of different time slots, and / or combinations of different sub-bands, different frequency bands, and / or different time slots. In some embodiments, these communication techniques may use OFDMA.

[0151] Furthermore, while the foregoing embodiments exemplify the use of Wi-Fi during communication technologies, in other embodiments of these communication technologies, Bluetooth or Bluetooth Low Energy is used to convey at least a portion of the information in these communication technologies. Moreover, the information conveyed in the communication technologies may be transmitted or appear in one or more frequency bands, including: 900MHz, 2.4GHz, 5GHz, 6GHz, 60GHz, Citizen Broadband Radio Component Service (CBRS) bands, bands used by LTE or other data communication protocols, etc.

[0152] As described herein, aspects of this technology may include the collection and use of data available from various sources, for example, to improve or enhance functionality. This disclosure contemplates that, in some instances, the collected data may include personal information data that uniquely identifies or can be used to contact or locate specific individuals. Such personal information data may include demographic data, location-based data, telephone numbers, email addresses, Twitter IDs, home addresses, data or records related to a user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying information or personal information. This disclosure recognizes that the use of such personal information data in the present invention's technology can be used to benefit users.

[0153] This disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage, or other use of such personal information data will comply with robust privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to privacy policies and measures recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy and security of personal information data. Such policies should be easily accessible to users and should be updated as the collection and / or use of data changes. Personal information from users should be collected for legitimate and reasonable entity purposes and should not be shared or sold outside of these legitimate purposes. Furthermore, such collection / sharing should only occur upon receipt of informed consent from the user. Additionally, such entities should consider taking any necessary steps to protect and safeguard the right to access such personal information data and ensure that other entities with access to personal information data comply with the privacy policies and procedures of those other entities. Furthermore, such entities may be subject to third-party assessments to demonstrate their compliance with widely accepted privacy policies and privacy practices. Additionally, policies and practices should be adapted to the specific types of personal information data collected and / or accessed, and to applicable laws and standards, including considerations of specific jurisdictions. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy measures should be advocated for different types of personal data in each country.

[0154] Regardless of the foregoing, this disclosure also anticipates implementation schemes for users to selectively block the use or access to personal information data. That is, this disclosure anticipates hardware and / or software components to prevent or block access to such personal information data. For example, the technology may be configured to allow users to selectively participate in the collection of personal information data at any time during or after service registration via an "opt-in" or "opt-out" option. In addition to providing "opt-in" and "opt-out" options, this disclosure also anticipates providing notifications related to access to or use of personal information. For example, users may be notified when downloading an application that their personal information data will be accessed, and then reminded again just before the application accesses the personal information data.

[0155] Furthermore, the intent of this disclosure is that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once data is no longer needed, this risk can be minimized by restricting data collection and deleting data. Additionally, and where applicable, including in certain health-related applications, data deidentification can be used to protect user privacy. Deidentification can be facilitated, where appropriate, by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of stored data (e.g., collecting location data at the city level rather than the address level), controlling how data is stored (e.g., aggregating data among users), and / or other methods.

[0156] Therefore, while this disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, it is also contemplated that various embodiments can be implemented without access to such personal information data. That is, various embodiments of the present invention will not become inoperable due to the absence of all or part of such personal information data.

[0157] The implementation scheme of the electronic device will now be described. Figure 23 A block diagram of an electronic device 2300 (which may be a cellular phone, smartwatch, access point, wireless speaker, IoT device, other electronic device, etc.) according to some embodiments is presented. The electronic device includes a processing subsystem 2310, a memory subsystem 2312, and a networking subsystem 2314. The processing subsystem 2310 includes one or more devices configured to perform computational operations. For example, the processing subsystem 2310 may include one or more microprocessors, application-specific integrated circuits (ASICs), microcontrollers, graphics processing units (GPUs), programmable logic devices, and / or one or more digital signal processors (DSPs).

[0158] The memory subsystem 2312 includes one or more devices for storing data and / or instructions for processing subsystem 2310 and / or networking subsystem 2314. For example, the memory subsystem 2312 may include dynamic random access memory (DRAM), static random access memory (SRAM), read-only memory (ROM), flash memory, and / or other types of memory. In some embodiments, instructions for processing subsystem 2310 within the memory subsystem 2312 include program instructions or instruction sets (such as program instructions 2322 or operating system 2324) executable by processing subsystem 2310. For example, ROM may store programs, utilities, or procedures to be executed in a non-volatile manner, while DRAM provides volatile data storage and may store instructions related to the operation of electronic device 2300. It should be noted that one or more computer programs may constitute a computer program mechanism, a computer-readable storage medium, or software. Furthermore, the instructions in the various modules of the memory subsystem 2312 may be implemented in languages ​​such as high-level programming languages, object-oriented programming languages, and / or assembly language or machine language. Furthermore, the programming language can be compiled or interpreted, for example, configured to be executed by the processing subsystem 2310 (these two are used interchangeably in this discussion). In some implementations, one or more computer programs are distributed across network-coupled computer systems, such that one or more computer programs are stored and executed in a distributed manner.

[0159] Furthermore, the memory subsystem 2312 may include mechanisms for controlling access to the memory. In some embodiments, the memory subsystem 2312 includes a memory hierarchy that includes one or more caches of the memory coupled to the electronic device 2300. In some of these embodiments, one or more of these caches are located within the processing subsystem 2310.

[0160] In some implementations, the memory subsystem 2312 is coupled to one or more high-capacity mass storage devices (not shown). For example, the memory subsystem 2312 may be coupled to a disk drive or optical disc drive, a solid-state drive, or another type of mass storage device. In these implementations, the memory subsystem 2312 may be used by the electronic device 2300 as a fast-access storage device for frequently used data, while the mass storage device is used to store less frequently used data.

[0161] The networking subsystem 2314 includes one or more devices configured to be coupled to and communicate (i.e., perform network operations) on wired and / or wireless networks, such as: control logic unit 2316, one or more interface circuits (or interface circuit systems) 2318, and an antenna set 2320 (or antenna element) in an adaptive array that can be selectively turned on and / or off by the control logic unit 2316 to generate a variety of optional antenna patterns or "beam patterns". Alternatively, instead of the antenna set, in some embodiments, the electronic device 2300 includes one or more nodes 2308, such as pads or connectors, that can be coupled to the antenna set 2320. Therefore, the electronic device 2300 may or may not include the antenna set 2320. For example, the networking subsystem 2314 may include Bluetooth. TM Networking systems, cellular networking systems (e.g., 3G / 4G / 5G networks, such as UMTS, LTE, etc.), Universal Serial Bus (USB) networking systems, and networking systems based on standards described in IEEE 802.12 (e.g., Networked systems), Ethernet networked systems and / or another networked system.

[0162] In some implementations, the networking subsystem 2314 includes one or more radio components, such as a wake-up radio component for receiving wake-up frames and wake-up beacons, and a main radio component for transmitting and / or receiving frames or packets during normal operating mode. The wake-up radio component and the main radio component may be implemented separately (e.g., using discrete components or separate integrated circuits) or may be implemented in a common integrated circuit.

[0163] The networking subsystem 2314 includes a processor, controller, radio components / antenna, jacks / plugs, and / or other devices for coupling to each supported networking system, communicating on each supported networking system, and processing data and events on each supported networking system. It should be noted that the mechanisms for coupling to the network of each networking system, communicating on the network of each networking system, and processing data and events on the network of each networking system are sometimes collectively referred to as the “network interface” for that networking system. Furthermore, in some embodiments, a “network” or “connection” between electronic devices does not yet exist. Therefore, electronic device 2300 can use the mechanisms in the networking subsystem 2314 to perform simple wireless communication between electronic devices, such as sending one or more announcement frames and / or scanning announcement frames sent by other electronic devices.

[0164] Within electronic device 2300, processing subsystem 2310, memory subsystem 2312, and networking subsystem 2314 are coupled together using bus 2328, which facilitates data transfer between these components. Bus 2328 may include electrical, optical, and / or optoelectronic connections that the subsystems can use to communicate commands and data to each other. Although only one bus 2328 is shown for clarity, different embodiments may include different numbers or configurations of electrical, optical, and / or optoelectronic connections between subsystems.

[0165] In some embodiments, electronic device 2300 includes a display subsystem 2326 for displaying information on a display. The display subsystem may include a display driver and a display, such as a liquid crystal display, a multi-touch screen, etc. The display subsystem 2326 may be controlled by processing subsystem 2310 to display information (e.g., information related to incoming, outgoing, or active communication sessions) to a user.

[0166] In addition, the electronic device 2300 may also include a user input subsystem 2330 that allows a user of the electronic device 2300 to interact with the electronic device 2300. For example, the user input subsystem 2330 may take various forms, such as: buttons, keypads, dial pads, touch screens, audio input interfaces, visual / image capture input interfaces, input in the form of sensor data, etc.

[0167] Electronic device 2300 may be any electronic device having at least one network interface (or may be included in any electronic device having at least one network interface). For example, electronic device 2300 may include: cellular phones or smartphones, tablet computers, laptop computers, notebook computers, personal or desktop computers, netbook computers, media player devices, wireless speakers, IoT devices, e-book devices, etc. Devices, smartwatches, wearable computing devices, portable computing devices, consumer electronics, vehicles, doors, windows, portals, access points, routers, switches, communication devices, testing devices, and any other type of electronic computing device having wireless communication capabilities that may include communication via one or more wireless communication protocols.

[0168] Although specific components are used to describe electronic device 2300, in alternative embodiments, different components and / or subsystems may be present in electronic device 2300. For example, electronic device 2300 may include one or more additional processing subsystems, memory subsystems, networking subsystems, and / or display subsystems. Additionally, one or more of the subsystems may not be present in electronic device 2300. Furthermore, in some embodiments, electronic device 2300 may include Figure 23One or more additional subsystems not shown. In some embodiments, the electronic device may include an analysis subsystem that performs at least some of the operations in the communication technology. Furthermore, although in Figure 23 Separate subsystems are shown, but in some embodiments, some or all of a given subsystem or component may be integrated into one or more other subsystems or components in electronic device 2300. For example, in some embodiments, program instructions 2322 are included in operating system 2324, and / or control logic unit 2316 is included in the one or more interface circuits 2318.

[0169] Furthermore, the circuits and components in the electronic device 2300 can be implemented using any combination of analog and / or digital circuit systems, including bipolar, PMOS, and / or NMOS gates or transistors. Moreover, the signals in these embodiments can include digital signals with approximately discrete values ​​and / or analog signals with continuous values. Additionally, the components and circuits can be single-ended or differential, and the power supply can be unipolar or bipolar.

[0170] The integrated circuit may implement some or all of the functions of the networking subsystem 2314. The integrated circuit may include hardware and / or software mechanisms for transmitting wireless signals from electronic device 2300 and receiving signals from other electronic devices at electronic device 2300. In addition to the mechanisms described herein, radio components are well known in the art and are therefore not described in detail. Generally, the networking subsystem 2314 and / or the integrated circuit may include any number of radio components. It should be noted that the radio components in multiple radio component embodiments function in a manner similar to the single radio component embodiment described herein.

[0171] In some embodiments, the networking subsystem 2314 and / or the integrated circuit include configuration mechanisms (such as one or more hardware and / or software mechanisms) for configuring the radio components to transmit and / or receive on a given communication channel (e.g., a given carrier frequency). For example, in some embodiments, this configuration mechanism can be used to switch the radio components from monitoring and / or transmitting on a given communication channel to monitoring and / or transmitting on a different communication channel. (Note that "monitoring" as used herein includes receiving signals from other electronic devices and possibly performing one or more processing operations on the received signals.)

[0172] In some implementations, the output of the process for designing an integrated circuit or a portion thereof that includes one or more of the circuits described herein may be a computer-readable medium, such as, for example, magnetic tape, optical disc, or magnetic disk. The computer-readable medium may be encoded with data structures or other information describing a circuit system that can be physically instantiated as an integrated circuit or a portion thereof. Although various formats are available for such encoding, these data structures are typically written in formats such as Caltech Intermediate Format (CIF), Calma GDS II Data Stream Format (GDSII), Electronic Design Exchange Format (EDIF), Open Access (OA), or Open Prototype Systems Exchange Standard (OASIS). Those skilled in the art of integrated circuit design can develop such data structures from the schematic diagrams and corresponding descriptions of the types detailed above and encode such data structures onto a computer-readable medium. Those skilled in the art of integrated circuit manufacturing can use such encoded data to manufacture integrated circuits that include one or more of the circuits described herein.

[0173] While the foregoing discussion uses the Wi-Fi communication protocol as an illustrative example, a wide variety of communication protocols can be used in other embodiments, and more generally, wireless communication technologies can be used. Therefore, communication technologies can be used in a variety of network interfaces. Furthermore, although some operations in the foregoing embodiments are implemented in hardware or software, in general, the operations in the foregoing embodiments can be implemented in a wide variety of configurations and architectures. Thus, some or all of the operations in the foregoing embodiments can be performed in hardware, software, or both. For example, at least some of the operations in the communication technology can be implemented using program instructions 2322, operating system 2324 (such as a driver for the interface circuitry in the networking subsystem 2314), or firmware in the interface circuitry in the networking subsystem 2314. Alternatively or additionally, at least some of the operations in the communication technology can be implemented at the physical layer (such as the interface circuitry in the networking subsystem 2314 or hardware in the interface circuitry system). In some embodiments, the communication technology is implemented at least partially in the MAC layer and / or physical layer of the interface circuitry in the networking subsystem 2314.

[0174] It should be noted that, in one or more embodiments, the use of the phrases “capable,” “operable as,” or “configured as” means that some device, logic component, hardware, and / or element is designed to enable the device, logic component, hardware, and / or element to be used in a specified manner.

[0175] While examples of numerical values ​​have been provided in the foregoing discussion, different values ​​are used in other implementations. Therefore, the provided values ​​are not intended to be limiting.

[0176] Furthermore, while the foregoing embodiments exemplify the use of wireless signals in one or more frequency bands, other embodiments of the communication technology utilize electromagnetic signals in one or more different frequency bands. For example, these signals may be transmitted in one or more frequency bands, including: microwave bands, radar bands, 900MHz, 2.4GHz, 5GHz, 6GHz, 60GHz, and / or the bands used by citizen broadband radio services or LTE.

[0177] The foregoing description mentioned "some implementation schemes." It should be noted that "some implementation schemes" describes a subset of all possible implementation schemes, but does not always specify the same subset of implementation schemes.

[0178] The foregoing description is intended to enable any person skilled in the art to implement and use this disclosure, and is provided in the context of a particular application and its requirements. Furthermore, the foregoing description of embodiments of this disclosure has been presented for illustrative and descriptive purposes only. They are not intended to be exhaustive or to limit this disclosure to the forms disclosed. Thus, many modifications and variations will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of this disclosure. Additionally, the discussion of the foregoing embodiments is not intended to limit this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown, but will be given the widest scope consistent with the principles and features disclosed herein.

Claims

1. An electronic device, the electronic device comprising: An antenna node configured to be communicatively coupled to an antenna; and An interface circuit, communicatively coupled to the antenna node and configured to communicate with a second electronic device, wherein the interface circuit is configured to: Addressing to at least the second electronic device provides a multicast (GCR) block acknowledgment request (BAR) with retry, wherein the GCR BAR indicates that the GCR BAR is protected.

2. The electronic device according to claim 1, wherein the GCR BAR includes a GCR multi-user BAR (MU-BAR).

3. The electronic device of claim 1, wherein the indication is included in a reserved bit in the GCR BAR.

4. The electronic device of claim 1, wherein the GCR BAR uses the reserved bit to indicate a key identifier.

5. The electronic device of claim 1, wherein the GCR BAR includes a group number (PN) and a message integrity check (MIC).

6. The electronic device of claim 5, wherein the PN and the MIC are included in or after the BAR information field following the GCR group address.

7. The electronic device of claim 5, wherein the BAR information field includes padding following the MIC.

8. The electronic device of claim 1, wherein the interface circuitry is configured to receive a multi-site block acknowledgment (M-BA) associated with the second electronic device.

9. The electronic device of claim 8, wherein the M-BA is protected.

10. The electronic device of claim 8, wherein the M-BA includes a per AIDTID information field identified by a reserved value in the associated identifier (AID) service identifier (TID) information subfield, and each AID TID information subfield includes information associated with the GCR.

11. The electronic device of claim 10, wherein the information includes a GCR group address, TID information, or both.

12. The electronic device of claim 1, wherein the second electronic device is a member of the GCR group.

13. The electronic device of claim 1, wherein the GCR BAR includes information about one or more Media Access Control (MAC) headers for one or more subsequent GCR data frames, and the information includes a valid sequence number (SN) range, power management bits, additional data bits, end of service period (EOSP) bits, or high throughput (HT) control fields of one or more Media Access Control (MAC) headers.

14. A method for providing a multicast (GCR) block acknowledgment request (BAR) with retry, the method comprising: From electronic devices: Addressing to at least a second electronic device provides the GCR BAR, wherein the GCRBAR indicates that the GCR BAR is protected; as well as The second electronic device receives a multi-site block acknowledgment (M-BA).

15. The method of claim 14, wherein the GCR BAR includes a GCR multi-user BAR (MU-BAR).

16. The method of claim 14, wherein the M-BA is protected.

17. A second electronic device, the second electronic device comprising: An antenna node configured to be communicatively coupled to an antenna; and An interface circuit, communicatively coupled to the antenna node and configured to communicate with an electronic device, wherein the interface circuit is configured to: The electronic device receives a multicast (GCR) block acknowledgment request (BAR) with retry capability, wherein the GCRBAR indicates that the GCR BAR is protected.

18. The second electronic device of claim 17, wherein the interface circuitry is configured to address the electronic device to provide multi-site block acknowledgment (M-BA).

19. The second electronic device according to claim 18, wherein the M-BA is protected.

20. The second electronic device of claim 17, wherein the interface circuitry is configured to verify one or more GCR data frames at least in part based on information.

Images