Multicast with Retry (GCR) in Multi-link WLAN Systems

Abstract

The present disclosure relates to multicast with retry (GCR) in a multi-link WLAN system. Embodiments of a multicast with retry (GCR) in a multi-link wireless communication system are disclosed. In some embodiments, an access point (AP) multilink device (MLD) can exchange information with a non-AP MLD to establish a GCR multilink operation (MLO) protocol corresponding to a group address, wherein the information includes, but is not limited to: a GCR primary link or a set of GCR primary links of the AP MLD, and an association identifier (AID) corresponding to the group address. In some embodiments, the AP MLD can send a GCR frame that complies with the GCR-MLO protocol, wherein the GCR frame includes a sequence number assigned from a sequence number space (SNS)_GCR_MLO defined at the MLD level, and a group transient key (GTK) GCR_ML is generated at the MLD level, wherein the GTK_GCR_ML enables encryption and decryption of the GCR frame.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 224,797, filed on July 22, 2021, which is incorporated herein by reference in its entirety. Technical Field

[0003] Embodiments generally relate to a wireless device for sending a multicast with retry (GCR) in a wireless communication system. Background Art

[0004] Multicast with Retry (GCR) is defined in IEEE P802.11REVme_D0.0, Draft Standard for Information Technology—Telecommunications and Information Exchange between Local and Metropolitan Area Networks—Specific Requirements: Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specification for Single Link Operation (SLO) to improve the reliability and / or reduce the delay of delivering group-addressed frames. Summary of the Invention

[0005] Some embodiments include apparatus, methods, and computer program products for multicast with retry (GCR) for multilink operation (MLO) in a multilink system, such as a wireless LAN (WLAN) system. Some embodiments include an access point (AP) multilink device (MLD) that obtains membership in a multicast group (e.g., obtains membership in a group address). The GCR service enables the transmission or retransmission of a medium access control (MAC) service data unit (MSDU) or aggregated MSDU (A-MSDU) to a destination that is a group address. The GCR service improves reliability by enabling retransmissions, wherein the retransmitted group address is hidden from stations that do not support GCR (e.g., legacy stations that do not support GCR). GCR-MLO enables AP MLDs and non-AP MLDs to utilize the MLD's multiple links for retransmitting group-addressed frames while maintaining backward compatibility with legacy devices (e.g., legacy stations that do not support GCR) and single-link devices (SLDs) that support GCR.

[0006] The AP MLD can establish a multicast with retry (GCR) protocol at the MLD level (e.g., modifying the Direct Multicast Service (DMS) request / response frame exchange used by GCR Single Link Operation (SLO) to set up the GCR-MLO protocol; or exchanging GCR-MLO parameters through other signaling methods). The AP MLD can operate in at least two modes: Mode 1, in which all members of the GCR-MLO group are available on a common link (GCR primary link) during the GCR frame delivery time; and Mode 2, in which all members of the GCR-MLO group are unavailable on the common link during the GCR frame delivery time. Therefore, Mode 2 includes a GCR primary link set that includes two or more primary links through which GCR frames can be delivered to members of the GCR-MLO group.

[0007] In some embodiments, the AP MLD schedules a GCR-Service Period (SP) for low-latency services, where the SP is link-specific. For example, the AP MLD may initiate a GCR-SP on a link and terminate the GCR-SP on the link before the scheduled duration of the GCR-SP expires. Additionally, an SP (e.g., a target wake time (TWT) SP) may overlap with a GCR-SP. The AP MLD may transmit instructions to members of a GCR-MLD group and / or stations corresponding to overlapping TWT SPs to terminate the corresponding SPs individually or in conjunction with other SPs.

[0008] In some embodiments, the AP MLD can define a sequence number space (SNS) for GCR frames at the MLD level to assign sequence numbers to GCR frames subject to the GCR-MLO Unsolicited Retry policy or the GCR-MLO Block Ack retry policy. The AP MLD can perform duplicate GCR frame detection at the MLD level and can also discard duplicate GCR frames at the MLD level. The AP MLD can generate a group transient key (GTK) for GCR-MLO at the MLD level to encrypt / decrypt GCR frames. In addition, the AP MLD can perform GCR-MLO functionality while achieving backward compatibility with: legacy STAs that support GCR-MLO; non-AP MLDs that support GCR-MLO; and / or legacy STAs that do not support GCR. When all members of a group address support GCR-MLO, the AP MLD can map a group address to one or more GCR subgroups.

[0009] Some implementations of GCR-MLO improve link-specific performance by means including, but not limited to: assigning an association identifier (AID) for GCR frame transmission; implementing a multi-service identifier (TID) A-MAC protocol data unit (A-MPDU) aggregate payload; and managing early termination of link-specific GCR-SPs, including GCR-SPs that overlap with other SPs (e.g., TWT SPs). BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the disclosed disclosure and, together with the description, further serve to explain the principles of the disclosure and enable one skilled in the relevant art to make and use the disclosure.

[0011] Figure 1 An exemplary system for multicast with retry (GCR) for multilink operation (MLO) is shown in accordance with some embodiments of the present disclosure.

[0012] Figure 2 A block diagram of an exemplary wireless system supporting GCR-MLO according to some embodiments of the present disclosure is shown.

[0013] Figure 3A An exemplary system supporting GCR-MLO including a GCR main link (Mode 1) according to some embodiments of the present disclosure is shown.

[0014] Figure 3B An exemplary system supporting GCR-MLO including a GCR primary link set (Mode 2) according to some embodiments of the present disclosure is shown.

[0015] Figure 4A An example of GCR-MLO non-GCR-Service Period (SP) delivery time is shown according to some embodiments of the present disclosure.

[0016] Figure 4B Shown are examples of GCR-MLO GCR-SP delivery times according to some embodiments of the present disclosure.

[0017] Figure 5 An example of association identifier (AID) assignment for GCR-MLO is shown according to some embodiments of the present disclosure.

[0018] Figure 6 An exemplary method for setting up and updating the GCR-MLO protocol according to some embodiments of the present disclosure is shown.

[0019] Figure 7AAn example of a GCR multi-user (MU) block acknowledgement request (BAR) for early termination of a SP according to some embodiments of the present disclosure is shown.

[0020] Figure 7B Another example of a GCR MU BAR for early termination of an SP according to some embodiments of the present disclosure is shown.

[0021] Figure 8 An example of GCR-SP management for GCR-MLO with overlapping SPs is shown according to some embodiments of the present disclosure.

[0022] Figure 9A An example of GCR frame transmission for GCR-MLO according to some embodiments of the present disclosure is shown.

[0023] Figure 9B An example of a non-GCR frame format according to some embodiments of the present disclosure is shown.

[0024] Figure 10A An example of GCR-MLO unsolicited retry - Mode 1 with legacy non-GCR members is shown, according to some embodiments of the present disclosure.

[0025] Figure 10B An example of GCR-MLO unsolicited retry - Mode 2 with legacy non-GCR members is shown, according to some embodiments of the present disclosure.

[0026] Figure 11A An example of GCR-MLO Block Acknowledgement - Mode 1 with legacy Single Link Device (SLD) GCR members is shown, according to some embodiments of the present disclosure.

[0027] Figure 11B An example of GCR-MLO block confirmation with legacy SLD GCR members—Mode 2 is shown, according to some embodiments of the present disclosure.

[0028] Figure 12 An example of frame exchange with GCR Multi-User (MU) Block Acknowledgement Request (BAR) for GCR-MLO is shown, according to some embodiments of the present disclosure.

[0029] Figure 13 An example of creating multiple GCR subgroups corresponding to a single group address is shown according to some embodiments of the present disclosure.

[0030] Figure 14 An exemplary method of an access point (AP) multi-link device (MLD) for GCR-MLO according to some embodiments of the present disclosure is shown.

[0031] Figure 15 Another exemplary method for AP MLD of GCR-MLO according to some embodiments of the present disclosure is shown.

[0032] Figure 16 An exemplary method for non-AP MLD of GCR-MLO according to some embodiments of the present disclosure is shown.

[0033] Figure 17 Another exemplary method for non-AP MLD of GCR-MLO according to some embodiments of the present disclosure is shown.

[0034] Figure 18 is an exemplary computer system for implementing some embodiments or portions thereof.

[0035] The present disclosure is described with reference to the accompanying drawings. In the drawings, generally, like reference numerals represent identical or functionally similar elements. Additionally, generally, the leftmost digit of a reference numeral identifies the drawing in which the reference numeral first appears. DETAILED DESCRIPTION

[0036] Some multi-link devices (MLDs), such as access point (AP) MLDs, can communicate with non-AP MLD stations (e.g., extremely high throughput (EHT) stations (STAs)) using one or more radios over multiple links. The multiple links can be multiple channels in the same frequency band or multiple channels in different frequency bands. Furthermore, the AP MLD can communicate with legacy stations over links in the multiple links using one or more of the radios.

[0037] Figure 1An exemplary system 100 for multicast with retry (GCR) for multilink operation (MLO) according to some embodiments of the present disclosure is shown. System 100 includes an AP MLD 110 that provides access to a network 150 for non-AP MLDs 120a, 120b, 120c, legacy single-link device (SLD) stations 130, and legacy non-GCR-capable stations 140 (e.g., not multilink devices). Non-AP MLDs 120a-120c, legacy SLD stations 130, and legacy non-GCR-capable stations 140 may be electronic devices that may include, but are not limited to, cellular phones, smartphones, tablets, personal digital assistants (PDAs), or laptops. Network 150 may include, but is not limited to, any one of a local area network (LAN), a metropolitan area network (MAN), a wireless local area network (WLAN), and / or the Internet, or any combination thereof. Non-AP MLDs 120a-120c, legacy SLD stations 130, and legacy non-GCR-capable stations 140 in proximity to AP MLD 110 can associate with AP MLD 110. In some embodiments, AP MLD 110 obtains membership in a multicast group corresponding to a group address. The GCR service enables the transmission or retransmission of a Media Access Control (MAC) Service Data Unit (MSDU) or Aggregate MSDU (A-MSDU) to a destination that is the group address. The GCR service improves reliability by enabling retransmissions, where the retransmitted group address is hidden from stations that do not support GCR (e.g., legacy non-GCR-capable station 140). In some embodiments, AP MLD 110 and non-AP MLD stations 120a-120c can perform GCR-MLO to utilize multiple links of the MLD to retransmit the group address while maintaining backward compatibility with legacy devices (e.g., legacy non-GCR-capable station 140) and GCR-capable SLD stations (e.g., legacy SLD station 130).

[0038] Figure 2 A block diagram of an exemplary wireless system 200 supporting GCR-MLO according to some embodiments of the present disclosure is shown. For purposes of illustration and not limitation, reference may be made to Figure 1 Elements to describe Figure 2. For example, the system 200 can be any of the electronic devices of the system 100 (e.g., the AP MLD 110, the non-AP MLDs 120a, 120b, 120c, the legacy SLD station 130, and the legacy non-GCR-enabled station 140). The system 200 includes one or more processors 265, a transceiver 270, a communication interface 275, a communication infrastructure 280, a memory 285, and an antenna 290. The memory 285 may include random access memory (RAM) and / or cache, and may include control logic (e.g., computer instructions) and / or data. The one or more processors 265 may execute instructions stored in the memory 285 to perform operations that enable the wireless system 200 to send and receive wireless communications, including operations for performing the GCR-MLO functionality herein. In some embodiments, the one or more processors 265 may be "hard-coded" to perform these functions herein. According to some embodiments, transceiver 270 transmits and receives wireless communication signals, including wireless communication supporting GCR-MLO, and can be coupled to one or more antennas 290 (e.g., 290a, 290b). In some embodiments, transceiver 270a (not shown) can be coupled to antenna 290a, and a different transceiver 270b (not shown) can be coupled to antenna 290b. Communication interface 275 allows system 200 to communicate with other devices, which can be wired and / or wireless. Communication infrastructure 280 can be a bus. Antenna 290 can include one or more antennas that can be the same or different types.

[0039] Figure 3A An exemplary system 300 supporting GCR-MLO including GCR primary link (Mode 1) according to some embodiments of the present disclosure is shown. For purposes of illustration and not limitation, reference may be made to Figure 1 and Figure 2 3. For example, AP MLD 310 may correspond to Figure 1 AP MLD 110, and non-AP MLD A 320a, non-AP MLD B 320b, and non-AP MLD C 320c may correspond to Figure 1 non-AP MLDs 120a, 120b, and 120c.

[0040] AP MLD 310 may include multiple APs, each identified by a specific link. For example, AP1 313 may communicate via 2.4 GHz, identified by link 1 391; AP2 315 may communicate via 5 GHz, identified by link 2 395; and AP3 317 may communicate via 6 GHz, identified by link 3 397. In system 300, AP1 313, AP2 315, and AP3 317 may each have a radio transceiver that operates independently of the other radio transceivers. AP MLD 310 may utilize one or more radio components (e.g., three transceivers) to communicate with non-AP MLD A 320a via multiple links (e.g., across one or more frequency bands). For example, AP MLD 310 may communicate with non-AP MLD A 320a via link 1 391, link 2 395, and / or link 3 397 using the transceivers of AP1 313, AP2 315, and / or AP3 317. AP MLD 310 may communicate with non-AP MLD B 320b via link 1 391 and / or link 2 395 using the transceivers of AP1 313 and / or AP2 315. AP MLD 310 may communicate with non-AP MLD C 320c via link 1 391 using the transceiver of AP1 313.

[0041] Non-AP MLD A 320a can scan across all three links and identify AP MLD 310. After associating with AP MLD 310, non-AP MLD A 320a can communicate via any of these links (link 1 391, link 2 395, and / or link 3 397), which are available, for example, in three different frequency bands (e.g., 2.4 GHz, 5 GHz, and 6 GHz). If one link is busy, non-AP MLD A 320a or AP MLD 310 selects another link that is available first.

[0042] AP MLD 310 may operate in GCR-MLO with at least the following retransmission policies: unsolicited retries and block acknowledgements (BAs). GCR frames sent in GCR-MLO utilize sequence numbers from a sequence number space (SNS) determined at the MLD level, including, but not limited to, SNS_GCR-MLO unsolicited retries 360 and SNS_GCR-MLO block acknowledgements 365. When implementing SNS_GCR-MLO unsolicited retries 360, sequence numbers generated at the MLD level and other parameters in the GCR frame (e.g., group address (e.g., corresponding to the GCR-MLO protocol and / or GCR-MLO group), hidden address) may be used to detect duplicate GCR frames. This detection may be performed at the MLD level, and any duplicate GCR frames detected may be discarded at the MLD level. In some embodiments, SNS_GCR-MLO unsolicited retries may be the same as the general SNS used to deliver group-addressed frames that are not subject to the GCR protocol. When implementing SNS_GCR-MLO block acknowledgement 365, the sequence number generated at the MLD level and other parameters in the GCR frame (e.g., group address, hidden address, and / or traffic identifier (TID)) can be used to detect duplicate GCR frames. This detection can be performed at the MLD level, and any duplicate GCR frames detected are discarded at the MLD level.

[0043] In some embodiments, when the GCR-MLO retry policy type switches between unsolicited retry and block ACK, the AP MLD 310 sends the non-AP MLD (e.g., non-AP MLD A 320a) the last sequence number of the MPDU corresponding to the GCR service flow being updated, which was delivered before the GCR-MLO retry policy switch, to facilitate detection of any duplicate GCR frames caused by the GCR-MLO retry policy switch.

[0044] In some embodiments, the SNS_GCR_MLO unsolicited retry 360 allows multiplicity and is indexed by <address 1>. In some embodiments, the SNS_GCR-MLO block ACK allows multiplicity and is indexed by <address 1, TID>. For example, when implementing the SNS_GCR-MLO block ACK, the block ACK may be specific to the GCR address and TID. In some embodiments, the block ACK may be TID-agnostic. In some embodiments, the SNS_GCR_MLO block ACK may be merged with the SNS2 currently defined in IEEE P802.11 REVme. For example, the modified SNS2 of IEEE P802.11 REVme may be used by both unicast QoS (data) and GCR block ACK frames, and the modified SNS2 may allow multiplicity and be indexed by <address 1, TID>.

[0045] In addition, the AP MLD 310 can generate a group transient key (GTK) (e.g., GTK_GCR-Multilink (ML) 370) at the MLD level to encrypt and decrypt GCR frames at the MLD level, as described in Table 1: GCR-MLO Security. Corresponding replay attack detection / PN (packet number) checks can also be performed at the MLD level. To deliver group-addressed data frames that are not compliant with the GCR protocol, GTK_link_i can be used to communicate on link_i, where i is an integer greater than zero.

[0046] Table 1: GCR-MLO safety

[0047]

[0048] In Examples 1, 2, and 3 of the table above, GTK_LINK i is the group key used to deliver group-addressed data frames not subject to the GCR protocol (e.g., non-GCR group-addressed frames) on link i. GTK_GCR-ML is the group key used to deliver group-addressed frames subject to the GCR protocol on all links.

[0049] Example 1 in the table above shows that GTK-Multilink (ML) is generated at the MLD level, and the GTK for each link i is equal to the GTK-ML for all links i. For example, the GTK-ML generated at the MLD level is shown as GTK_GCR-ML 370 in system 300. The GTK_link_1 (e.g., link 1 391) used by AP1 313 can be GTK_GCR-ML 373 (which is the same as GTK_GCR-ML 370). Therefore, GTK_GCR-ML 370 can be used to encrypt and decrypt GCR frames being sent and received. AP2 315 can use GTK_GCR-ML 375 (which is the same as GTK_GCR-ML 370) to encrypt and decrypt GCR frames being sent and received. AP3 317 may use GTK_GCR-ML 377 (which may be the same as GTK_GCR-ML 370) to encrypt and decrypt transmitted and received GCR frames.

[0050] Example 2 shows that GTK-ML is generated at the MLD level, and the GTK for each link i is equal to the GTK-ML for all links i or a truncated version of GTK-ML. For example, for all i, each GTK_linki is the same as GTK-ML or the same as a truncated version of GTK-ML. The GTK-ML generated at the MLD level is shown as GTK_GCR-ML 370 in system 300. GTK_link_1 (e.g., link1 391) used by AP1 313 can be the same as GTK_GCR-ML 373 (which is the same as GTK_GCR-ML 370) or the same as a truncated version of GTK_GCR-ML 373. Therefore, GTK_GCR-ML 370 or a truncated version of GTK_GCR-ML 370 can be used to encrypt and decrypt group-addressed frames that are not subject to the GCR protocol and are sent and received on link1 391. Similarly, GTK_LINK_2 (e.g., link2 395) used by AP2 315 may be the same as GTK_GCR-ML 375 (which is the same as GTK_GCR-ML 370) or a truncated version of GTK_GCR-ML 375. Thus, GTK_GCR-ML 370 or a truncated version of GTK_GCR-ML 370 may be used to encrypt and decrypt GCR group addressed frames that are not compliant with the GCR protocol and are sent and received on link2 395. GTK_LINK_3 (e.g., link3 397) used by AP3 317 may be the same as GTK_GCR-ML 375 (which is the same as GTK_GCR-ML 370) or a truncated version of GTK_GCR-ML 375. Thus, GTK_GCR-ML 370 or a truncated version of GTK_GCR-ML 370 may be used to encrypt and decrypt GCR group-addressed frames that are not compliant with the GCR protocol and that are sent and received on link 3 397. AP1 313 may use GTK_GCR-ML 373 (which is the same as GTK_GCR-ML 370) to encrypt and decrypt GCR frames sent and received on link 1 391. AP2 315 may use GTK_GCR-ML 375 (which is the same as GTK_GCR-ML 370) to encrypt and decrypt GCR frames sent and received on link 2 395. AP3 317 may use GTK_GCR-ML 377 (which may be the same as GTK_GCR-ML 370) to encrypt and decrypt GCR frames sent and received on link 3 397.

[0051] Example 3 shows that the GTK for link i is independent and is generated at each AP level rather than at the MLD level. For group-addressed frames that are not compliant with the GCR-MLO protocol (e.g., non-GCR group-addressed frames), AP1 313 can use a link-specific GTK (e.g., GTK_1 383) that is independent of GTK_GCR-ML 370 generated at the MLD level to encrypt and decrypt group-addressed frames that are not compliant with the GCR protocol and are sent and received on link 1 391. AP2 315 can use a link-specific GTK (e.g., GTK_2 385) that is independent of GTK_GCR-ML 370 generated at the MLD level to encrypt and decrypt group-addressed frames that are not compliant with the GCR protocol and are sent and received on link 2 395. AP3 317 may encrypt and decrypt group-addressed frames that are not subject to the GCR protocol and are sent and received on Link 3 397 using a link-specific GTK (eg, GTK_3 387 ) that is independent of GTK_GCR-ML 370 generated at the MLD level.

[0052] AP MLD 310 can operate in at least two modes: Mode 1 with a GCR primary link and Mode 2 with a GCR primary link set, where the GCR primary link or GCR primary link set is where the initial GCR frame transmission occurs. GCR frame retransmissions can occur on the GCR primary link, the GCR primary link set, or a non-primary link. Assume that a GCR-MLO group includes non-AP MLD A 320a, non-AP MLD B 320b, and non-AP MLD C 320c, and each of them complies with the GCR-MLO protocol with AP MLD 310. When all members of the GCR-MLO group are available on a common link (e.g., Link 1 391) during the GCR frame delivery time, AP MLD 310 can designate Link 1 391 as the GCR primary link. Therefore, non-AP MLD B 320b and non-AP MLD C 320c can receive the initial GCR frame sent via link 1 391 (GCR primary link) during the GCR frame delivery time, and receive the GCR frame retransmitted via primary link 1 391 or non-primary link 2 395 or non-primary link 3 397. Non-AP MLD A 320a, non-AP MLD B 320b, and non-AP MLD C 320c can all detect and discard duplicate GCR frames received on any link or on all links at the MLD level.

[0053] Figure 3B An exemplary system 350 supporting GCR-MLO including GCR primary link set (Mode 2) according to some embodiments of the present disclosure is shown. For purposes of illustration and not limitation, reference may be made to Figure 1 、 Figure 2 and Figure 3A 3. For example, AP MLD 310 may correspond to Figure 1 The AP MLD 110 of the system 300 is not described again here. Non-AP MLD A 322, non-AP MLD B 324, and non-AP MLD C 326 may correspond to Figure 1 The non-AP MLDs 120a, 120b, and 120c are configured.

[0054] Assume that the GCR-MLO group includes non-AP MLD A 322, non-AP MLD B 324, and non-AP MLD C 326, and each of them complies with the GCR-MLO protocol with AP MLD 310. In system 350, for example, members of the GCR-MLO group are unavailable on a common link. For example, only non-AP MLD A 322 can communicate via link 1 393. Since all members of the GCR-MLO group are unavailable on the common link during the GCR frame delivery time, AP MLD 310 can designate one or more links (e.g., link 2 395 and link 3 397) as master links in the GCR master link set 390. Therefore, during the GCR frame delivery time, non-AP MLD A 322 and / or non-AP MLD B 324 may receive the initial GCR frame transmitted from AP MLD 310 via link 2 395, and non-AP MLD C 326 and / or non-AP MLD B 324 may receive the initial GCR frame transmitted from AP MLD 310 via link 3 397. Non-AP MLD A 322 may receive the GCR frame retransmitted on link 1 393 or link 2 395, non-AP MLD B 324 may receive the GCR frame retransmitted on link 2 395 or link 3 397, and non-AP MLD C 326 may receive the GCR frame retransmitted on link 3 397. Non-AP MLD A 322, non-AP MLD B 324, and non-AP MLD C 326 may detect and discard duplicate GCR frames at the MLD level.

[0055] Return Reference Figure 1, AP MLD 110 may obtain membership of the multicast group corresponding to the group address. For example, AP MLD 110 may send a group membership request frame according to an IEEE 802.11 method or using another method other than IEEE 802.11 to request the contents of the dot11GroupAddressTable of the associated station. AP MLD 110 may establish a GCR-MLO protocol at the MLD level. Non-AP MLDs (e.g., non-AP MLD 120a) may send or receive frames to obtain membership of the multicast group corresponding to the group address. For example, AP MLD 110 may send a group membership request frame according to an IEEE 802.11 method or using another method other than IEEE 802.11 to request the contents of the dot11GroupAddressTable of the associated station. Figure 3A and Figure 3B The GCR-MLO protocol is established or updated on link 2 395 or link 3 397 of the GCR-MLO protocol. After the GCR-MLO protocol is established, GCR frames can be delivered on links (e.g., link 1 391), which may not be the same as the links used to establish the GCR-MLO protocol. If the members included in the GCR-MLO group are pre-EHT legacy devices that support single-link operation (e.g., legacy SLD stations 130), then the GCR primary link (e.g., in mode 1) or one of the links in the GCR primary link set (e.g., in mode 2) needs to be the same link as the link on which the pre-EHT legacy device that supports single-link operation operates.

[0056] AP MLD 110 can exchange information with each member of a multicast group that supports GCR-MLO to set up and / or update the GCR-MLO protocol. A multicast group that includes one or more non-AP MLD members (e.g., non-AP MLDs 120a-120c) that have established a GCR-MLO protocol with an AP MLD (e.g., AP MLD 110) can be referred to as a GCR-MLO group, and the corresponding group address can be referred to as a GCR group address. The GCR-MLO group can include legacy stations that do not support GCR (e.g., legacy non-GCR station 140). For example, legacy non-GCR station 140 can receive group-addressed frames that are not retransmitted (e.g., no acknowledgment / no retry transmission of these group-addressed frames), but does not support GCR (e.g., group rebroadcast with retries). When retransmitting these group-addressed frames according to the GCR-MLO protocol, APMLD 110 may hide the group address from legacy stations (e.g., by assigning a hidden address and including it in an Aggregation-Media Access Control (MAC) Service Data Unit (A-MSDU) frame). Figure 9A .

[0057] Figure 6 An exemplary method 600 for setting up and updating the GCR-MLO protocol according to some embodiments of the present disclosure is shown. For purposes of illustration and not limitation, reference may be made to elements of other figures within the present disclosure. Figure 6 For example, AP MLD 610 may correspond to Figure 1AP MLD 110, and non-AP MLD 620 may correspond to Figure 1 The information exchanged between the AP MLD 610 and the non-AP MLD 620 is shown in Table 2: Setting and updating the GCR-MLO protocol.

[0058] Table 2: Setting and updating the GCR-MLO protocol

[0059]

[0060] At 630, AP MLD 610 sends a GCR notification that is received by non-AP MLD 620. The GCR notification announces the availability of GCR service for the group address. The GCR notification may include, but is not limited to, the group address, delivery time (e.g., non-GCR service (SP) or GCR-SP information), retry method (e.g., unsolicited retry or block acknowledgement (BA)), GCR primary link (mode 1), or GCR primary link set (mode 2).

[0061] At 635, non-AP MLD 620 sends a GCR request that can be received by AP MLD 110. The GCR request requests GCR-MLO service for the group address. The GCR request may include, but is not limited to, the group address, a requested delivery time (e.g., non-GCR-SP or GCR-SP), a retry method (e.g., unsolicited retry or BA), and / or a GCR primary link or a set of GCR primary links.

[0062] At 640, the AP MLD 610 sends a GCR response that can be received by the non-AP MLD 620. The GCR response informs the non-AP MLD 620 of the GCR-MLO operating parameters that the AP MLD 610 has selected. These GCR-MLO operating parameters may be different from the information included by the non-AP MLD 620 in the GCR request. The GCR response may include, but is not limited to: a group address, a hidden address, an assigned delivery time (e.g., non-GCR-SP or GCR-SP), a retry method (e.g., unsolicited retry or BA), SP details (if a GCR-SP exists), a GCR primary link or a set of GCR primary links, and / or an association indicator (AID) for the GCR (AID_ GCR ).

[0063] The AP MLD may use one or more of the currently reserved AID values ​​to assign an AID to be used for GCR frame transmission in a DL MUPPDU. The AID assignment types are described in Table 3 below: AID assignment types.

[0064] Table 3: AID assignment types

[0065]

[0066] In option 1, AID_ GCR For example, the AP MLD 610 may assign an AID to a specific GCR-MLO group corresponding to a group address. The AP MLD 610 may send the AID in the GCR response 640 during the method 600 for setting up and updating the GCR-MLO protocol. GCR These AIDs are used to assign resource units (RUs) to recipients in RU allocations. They correspond to specific AIDs in the downlink (DL) multi-user (MU) physical layer convergence protocol (PLCP) protocol data unit (PPDU). GCR The RU allocation corresponds to the corresponding group address (the corresponding group address corresponds to the specific AID_ GCR ). Therefore, corresponding to a specific AID_ GCR The RUs are allocated only for sending GCR frames corresponding to the corresponding group addresses. When there are a large number of group-addressed frames in the network, the designated RUs for a specific GCR group (option 1) facilitate the delivery of GCR frames corresponding to the GCR group.

[0067] Figure 5 An example 500 of AID assignment for GCR-MLO according to some embodiments of the present disclosure is shown. For purposes of illustration and not limitation, reference may be made to elements of other figures within the present disclosure to describe the present disclosure. Figure 5 For example, the AP MLD 610 may assign a first AID_ for the first GCR-MLO group corresponding to GCR group address #1. GCR , assigning a second AID_ for the second GCR-MLO group corresponding to GCR group address #2 GCR GCR Group Address #1 may be a first group address subject to a first GCR-MLO protocol, and GCR Group Address #2 may be a second group address subject to a second GCR-MLO protocol.

[0068] AP MLD 610 may transmit a MU PPDU that is received by a non-AP MLD (e.g., non-AP MLD 620). For example, non-AP MLD 620 may receive the following items in a MU PPDU: i) AID corresponding to GCR 2 RUs assigned: For example, for GCR_ AID1 RU#1 530 and for GCR_ AID2 RU#2 535; ii) corresponds to an AID_ GCR One RU assigned and one RU for individually addressed data frames: for example, for GCR_AID2 or iii) 2 RUs of an individually addressed data frame: for example, RU#4 545 and RU#3 540.

[0069] In option 2, the AID is common to all GCR groups. Therefore, AID_ GCR Can be common to any GCR group and to all GCR groups.

[0070] return Figure 6 At 645, non-AP MLD 620 may send a GCR update request that may be received by AP MLD 610. The GCR update request may request a change in GCR operating parameters. The GCR update request may include, but is not limited to, a group address, a delivery time for the requested update (e.g., non-GCR-SP or GCR-SP information), a retry method (e.g., unsolicited retry or BA), and / or a GCR primary link or GCR primary link set.

[0071] At 650, the AP MLD 610 may send a GCR update / announcement, which may be solicited (e.g., in response to the received GCR update request 645) or unsolicited (e.g., based on a change in AP MLD 610 resources). The GCR update / announcement may be received by the non-AP MLD 620 and may include, but is not limited to: a group address, a hidden address, a designated delivery time for the update (e.g., non-GCR-SP or GCR-SP information), a retry method (e.g., unsolicited retry or BA), SP details (if a GCR-SP exists), a GCR primary link (Mode 1) or a GCR primary link set (Mode 2), and / or an AID_ GCR .

[0072] In some embodiments, method 600 can be performed by reusing and modifying the Direct Multicast Service (DMS) request / response frames exchanged by GCR Single Link Operation (SLO) to set up the GCR-MLD protocol. For example, some embodiments include modifying Table 9-230 of IEEE P802.11 REVme_D0.0 for the DMS descriptor. AP MLD 610 can use one of the reserved sub-element IDs defined as "GCR-MLO Request" (e.g., a reserved value of "2") to include GCR operational parameters applicable only to multi-link operation in GCR Request 635. Additionally, some embodiments include using the existing "Sub-element ID = 1" to carry operational parameters related to both single-link and multi-link operations.

[0073] Some embodiments include modifying Table 9-234 of IEEE P802.11 REVme_DO.0 for the DMS state. AP MLD 610 may use one of the reserved sub-element IDs defined as "GCR-MLO Response" (e.g., a reserved value of "2") to include GCR operational parameters applicable only to multi-link operation in GCR Response 640. Some embodiments include using the existing "sub-element ID=1" to carry operational parameters related to both single-link and multi-link operations, including the SP description in the "Scheduling Element" field of the "GCR Response" sub-element (as shown in Figure 9-480 of IEEE P802.11 REVme_DO.0).

[0074] The GCR-MLO protocol established between the AP MLD 610 and the non-AP MLD may include a combination of delivery methods and retransmission (ReTx) policies, as shown in the following Table 4: GCR-MLO Protocol Type.

[0075] Table 4: GCR-MLO protocol types

[0076]

[0077] For frames subject to a group address, only one of the four GCR-MLO protocol types is active at a time. Two types of retransmission policies include GCR-MLO unsolicited retry and GCR-MLO block acknowledgment (BA). When implementing GCR-MLO unsolicited retry, AP MLD 610 can determine the number of retries for the GCR frame. When implementing GCR-MLO BA, AP MLD 610 can send a BA request (BAR) to non-AP MLD 620 to obtain a BA from non-AP MLD 620. AP MLD 610 can determine whether to retransmit the GCR frame based on the received BA.

[0078] Figure 4A An example 400 of GCR-MLO non-GCR-service period (SP) delivery time according to some embodiments of the present disclosure is shown. For purposes of illustration and not limitation, reference may be made to elements of other figures in the present disclosure. Figure 4A For example, the AP MLD 310 of FIG. 3 may send a Delivery Traffic Indication Message (DTIM) beacon 1 412 immediately before the non-GCR-SP delivery time 414. Additionally, link 1 410 and link 2 may correspond to Figure 3B Link 2 395 and Link 3 397 in the GCR main link set 390.

[0079] Example 400 illustrates a non-GCR-SP delivery method. AP MLD 310 may transmit DTIM Beacon 1 412 on Link 1 410, followed by (e.g., immediately thereafter) a non-GCR-SP delivery time 414. During the non-GCR-SP delivery time 414, a no-acknowledgement / no-retry group-addressed frame is transmitted, followed by any GCR frame transmission. After DTIM Beacon 2 416 is transmitted, a non-GCR-SP delivery time 418 begins. Any no-acknowledgement / no-retry group-addressed frame is delivered, followed by any GCR frame transmission. Note that these GCR frames and the number of retries for the corresponding GCR frames may be different in each of the non-GCR-SP delivery times 414 and 418. A similar process occurs on Link 2 of Example 400. In some embodiments, for protocol type 2 (non-GCR-SP with GCR-MLO BA) in Table 4: GCR-MLO protocol types above, if all members in the GCR BA are awake (e.g., not in sleep or power save mode) at any particular time, the AP MLD 310 may send the GCR frame immediately without waiting for the DTIM beacon.

[0080] Figure 4B An example 450 of GCR-MLO GCR-SP delivery time according to some embodiments of the present disclosure is shown. For purposes of illustration and not limitation, elements of other figures in this disclosure may be used to describe Figure 4B For example, the AP MLD 310 of FIG. 3 may transmit Beacon 1 472 and use scheduled GCR-SPs 474a-474e. Additionally, Link 1 470 and Link 2 may correspond to Figure 3B Link 2 395 and Link 3 397 in the GCR primary link set 390. Example 450 illustrates a GCR-SP delivery method where the AP MLD 310 may deliver GCR frames within a scheduled service period (SP).

[0081] For example, AP MLD 310 may transmit Beacon 1 472 on Link 1 470 and transmit GCR frames within scheduled GCR-SPs 474a-474e. Similarly, AP MLD 310 may transmit Beacon 2 476 and subsequently transmit one or more GCR frames within scheduled GCR-SP 478a, and so on. These GCR frames may be different in each of GCR SPs 474a-474e and 478a. A similar process occurs on Link 2 of Example 450.

[0082] Table 2: Setting and updating the GCR operating parameters described in the GCR-MLO protocol can be further described in Table 5: GCR operating parameters below. Contains a single GCR primary link information indicating that the operation is in mode 1, and contains a GCR primary link set indicating that the operation is in mode 2, as referenced Figure 3A and Figure 3B In some embodiments, the AP MLD 610 may send a response message in a GCR response / update / announcement frame (e.g., Figure 6 640, 650, 630) may be used in conjunction with the GCR operating parameters assigned by a particular station (e.g., Figure 6 AP MLD 610 selects operating parameters based at least on input received from members of the GCR-MLD group and resource constraints of AP MLD 610. For example, AP MLD 610 may receive a GCR request 635 from non-AP MLD 620 requesting a GCR-SP duration of 5 milliseconds. AP MLD 610 may also receive another GCR request (not shown) from another non-AP MLD requesting a GCR-SP duration of 3 milliseconds. Based on the received GCR request and the resources of AP MLD 610, AP MLD 610 may set the GCR-SP duration to 5 milliseconds.

[0083] Table 5: GCR operating parameters

[0084]

[0085] In some embodiments, other signaling / framing methods may be used to exchange Figure 6, Table 2: Setting and updating the GCR-MLO protocol and Table 5: GCR operating parameters. For example, broadcast or multicast frames (rather than individually addressed frames) can be used to establish a GCR-SP. If channel access protection for the SP is desired, a broadcast approach can be used (e.g., including a container of information (such as elements, sub-elements) in a beacon / probe response). In some embodiments, the broadcast TWT element can be modified to indicate that a specific broadcast TWT SP is used to send GCR frames that are subject to a specific GCR-MLO protocol by including a GCR-MLO protocol identifier (e.g., a hidden address or GCR group ID) in the container for information about the specific broadcast TWT SP. When the GCR-SP is used for low-latency service, the scheduling method used for low-latency service (e.g., restricting TWT) can be modified for the establishment of the GCR-SP. For example, a container including an rTWT schedule can include an indication (e.g., a field, subfield, sub-element, etc.) that such rTWT schedule is used for GCR transmission. In some embodiments, a multicast or unicast approach can be used. For example, the GCR-SP information may be sent to GCR group members in a group-addressed frame or an individually-addressed frame.

[0086] GCR-SP is required for low-latency service. GCR SP can be set using broadcast signaling, multicast signaling, or unicast signaling as described above. Service periods (SPs) are link-specific. Each SP can be initiated and terminated independently in its corresponding link. Different links can have SPs running simultaneously (e.g., overlapping in time). For mode 2 of both GCR-MLO unsolicited retries and GCR-MLO block acknowledgments, when GCR-SP is used for low-latency service (e.g., protocol types 3 and 4 in Table 4: GCR-MLO protocol types), the service periods on all links in the GCR primary link set (e.g., all primary links) should be synchronized or semi-synchronized to provide low-latency delivery of traffic, where semi-synchronized GCR-SP on different links enables timely shutdown of the delivery of delay-sensitive traffic on different links, thereby meeting low-latency requirements. For example, a GCR frame is delivered on one link at time 1 and on another link at time 2, and the time interval between time 1 and time 2 is small enough that reception on both links can meet low-latency requirements. In some embodiments, the AP MLD 110 schedules SPs based on input from the non-AP MLDs 120a-120c and / or the legacy SLD stations 130 (eg, service requirements delivered in their traffic specifications (TSPEC) or by other methods).

[0087] Figure 7A An example 700 of a GCR multi-user (MU) block acknowledgement request (BAR) for early termination of a SP is shown, according to some embodiments of the present disclosure. Figure 7B An example 750 of a GCRMU BAR for early termination of an SP according to some embodiments of the present disclosure is shown. For purposes of illustration and not limitation, reference may be made to elements of other figures in the present disclosure to describe the present disclosure. Figure 7A and Figure 7B For example, the AP may be the AP MLD 310 of FIG. 3 , which may transmit a beacon 1472 and may be present in, for example, Figure 4B The GCR frame is delivered within the GCR-SP 475a of the GCR-SP. In examples 700 and 750, the GCR-SP has a maximum SP duration length t1. In some embodiments, the STA includes stations that are members of the GCR-MLD group, such as non-AP MLD stations that have a BA agreement with the AP: STA1, STA2, STA3, STA4, and STA5. In some embodiments, some non-AP MLD STAs may return to power save mode at the end of the GCR-SP, or earlier if the non-AP MLD STA receives one or more of the following information or indications during the GCR-SP and / or target wake time (TWT) SP:

[0088] More Trigger Frames (TF) in Trigger Frame = 0: Member stations (STAs) of the GCR-MLO group that have no resource units (RUs) allocated in the Trigger Frame may enter the sleep state;

[0089] End of Service Period (EOSP) = 1 or More Data (MD) = 0 in GCR data (e.g., GCR frame) or QoS Null frame;

[0090] GCR-SP termination indication.

[0091] After receiving one or more of these indications, the receiving non-AP MLD STA may return to a dormant state (e.g., power save mode). Example 700 is further described below:

[0092] At 705 , during the longest SP duration length t1 of the GCR-SP, the AP may send a GCR data frame, an indication (MD=1, eosp=0), and a GCR address (eg, addressed to the GCR-MLO group).

[0093] At 710, after sending the data frame 705, the AP may send a GCR MU BAR trigger frame including resource unit (RU) allocations for STA1, STA2, STA3, STA4, and STA5. In addition, the AP indicates More TF=1.

[0094] STA4 and STA5 signal in their BAs that they have correctly received the GCR frame at 715. STA1, STA2, and STA3 indicate in their BAs that they have not yet correctly received their GCR frames.

[0095] At 720, the AP retransmits the lost data and indicates MD=1, eosp=0.

[0096] At 725, after sending data frame 720, the AP may send a GCR MU BAR trigger frame including the RU allocations for STA1, STA2, and STA3. In addition, the AP indicates More TF = 0. Since there are no RU allocations for STA4 and STA5, STA4 and STA5 can return to the sleep state. In other words, the GCR SP is terminated for STA4 and STA5.

[0097] At 730, STA1, STA2, and STA3 signal in their BAs that they have correctly received their GCR frames.

[0098] At 735, the AP may transmit a GCR frame or a QoS null frame indicating MD=0 and eosp=1, and the GCR frame or the QoS null frame may terminate the GCR-SP of all stations (e.g., STA1, STA2, and STA3). Therefore, the GCR-SP of these stations may end before the maximum SP duration t1.

[0099] Figure 7B Another example of a GCR MU BAR for early termination of an SP according to some embodiments of the present disclosure is shown. Example 750 is further described below:

[0100] At 755 , during the longest SP duration length t1 of the GCR-SP, the AP may send a GCR data frame, an indication (MD=1, eosp=0), and a GCR address (eg, addressed to the GCR-MLO group).

[0101] At 760, after sending data frame 755, the AP may send a GCR MU BAR trigger frame including resource unit (RU) allocations for STA1, STA2, STA3, STA4, and STA5. Additionally, the AP may indicate More TF = 0. The GCR MU BAR trigger frame may include the sequence number of the last transmitted GCR MPDU. If the STA receives all MPDUs from the sequence signaled in the last transmitted GCR data frame (e.g., at 755), the station may return to sleep. Otherwise, the STA remains awake.

[0102] At 765, STA4 and STA5 signal in their BAs that they have correctly received the GCR frame. Therefore, STA4 and STA5 can terminate their SPs and return to sleep. Because STA1, STA2, and STA3 indicate in their BAs that they have not yet correctly received their GCR frames, they remain awake.

[0103] At 770, the AP retransmits the lost data and indicates MD=1, eosp=0.

[0104] At 775 , after sending the data frame 770 , the AP may request a BA from STA1 , STA2 , and STA3 by sending a GCR MU BAR trigger frame including RU allocations for STA1 , STA2 , and STA3 .

[0105] At 780, STA1, STA2, and STA3 signal in their BAs that they have correctly received their GCR frames and can return to sleep. In some embodiments, more TF = 0 terminates SP. Any STA with RU allocation terminates SP after correctly receiving its GCR frame. Therefore, the GCR-SP for these stations can end before the maximum SP duration t1.

[0106] A summary of the reception address (RA) usage is shown below in Table 6: Reception address (RA) usage.

[0107] Table 6: Receive Address (RA) Usage

[0108]

[0109] Figure 8 An example 800 of GCR-SP management for GCR-MLO with overlapping SPs according to some embodiments of the present disclosure is shown. For purposes of illustration and not limitation, reference may be made to elements of other figures in this disclosure. Figure 8 For example, the AP MLD 310 of FIG. 3 may transmit frames within a target wake time (TWT) SP and a GCR-SP that overlap on Link 1 (eg, Link 2 395 in the GCR primary link set 390 of FIG. 3 ).

[0110] Example 800 shows a TWT#2 SP 840, where downlink (DL) individually addressed data is sent to a STA (not shown). The STA can receive multiple TWT streams (e.g., TWT#1 SP 850 and TWT#2 SP 840), and each TWT stream can have SPs with different schedules (e.g., different SP start time, SP end time, and SP interval). Therefore, two or more TWT SPs can overlap. At the TWT SP early termination 810, all overlapping TWT SPs can be terminated early using the same signaling indication shown in Example 800. GCR-SP carries GCR frames with the same group address in the destination address field. (See Figure 9A ). The group address can be associated with a GCR-MLO group, and the group address can be subject to the corresponding GCR-MLO protocol. Because the GCR#1 SP and the GCR#2 SP carry different data, each GCR-SP (e.g., GCR#1 SP and GCR#2 SP) is terminated separately (e.g., as shown at GCR#2 SP early termination 820 and GCR#1 SP early termination 830). In addition, GCR-SP termination does not terminate the TWT SP of the separate data.

[0111] In some embodiments, a STA may have a TWT SP that transmits an individually addressed frame simultaneously with a GCR SP. EOSP=1 or MD=0 in the MAC header of an MPDU sent to a group address terminates only that specific GCR-SP. EOSP=1 or MD=0 in the MAC header of an individually addressed frame terminates all TWT SPs. The end of a GCR-SP duration terminates only that GCR-SP. For example, after GCR#2, early termination 820 does not affect other GCR-SPs, such as subsequent GCR#2 SPs. A trigger frame with more TF=0 terminates both the GCR SP and the individual SPs of the STA that was not assigned an RU by that trigger frame.

[0112] Figure 9A An example 900 of GCR frame transmission for GCR-MLO according to some embodiments of the present disclosure is shown. Elements of other figures in this disclosure may be used to describe Figure 9A For example, AP MLD (e.g., Figure 1 An example 900 of a GCR frame transmission may be sent by a non-AP MLD (e.g., an AP MLD 110) that is a member of a GCR-MLO group. Figure 1The GCR frame is a group-addressed frame subject to the GCR-MLO protocol between the APMLD 110 and at least one non-AP MLD 120 (e.g., non-AP MLD 120a-120c) within an infrastructure basic service set (BSS) or between peer mesh stations in a mesh BSS.

[0113] The GCR frame transmission 900 uses an aggregated MAC A-MSDU frame format including a service data unit (A-MSDU) medium access control (MAC) header 910 and a subframe 920. The A-MSDU MAC header 910 may include: a retry field 912 set to "1" for GCR retransmission (ReTx); an address 1 field 914 may include a hidden address assigned by the AP MLD 110. The hidden address prevents the GCR frame from being processed by legacy non-GCR-capable stations (e.g., legacy non-GCR-capable stations 140); a sequence control field 916 may include a sequence number space (SNS) defined at the MLD level (e.g., Figure 3A The SNS_GCR-MLO unrequested retry 360 and SNS_GCR-MLO block acknowledgment 365 are shown. The subframe field 920 includes a GCR frame format including a destination address (DA) field 922. The DA field 922 includes a hidden group address. The group address may be subject to the GCR-MLO protocol.

[0114] GCR frames can be aggregated in an aggregated MAC protocol data unit (A-MPDU). An A-MPDU includes an aggregation of multiple MPDUs and results in a larger transmit payload. GCR frames (also referred to as GCR data) can be similarly aggregated into individually addressed data frames by adding an A-MPDU header. A-MPDU aggregation for GCR data may include a single traffic identifier (TID) A-MPDU aggregation. For example, the payload of a single TID A-MPDU aggregation includes aggregate frames corresponding to a single hidden address (corresponding to a single group address). All aggregate frames in these aggregate frames will belong to the same TID (e.g., share the same TID value). All extremely high throughput (EHT) stations that support GCR (e.g., non-AP MLDs 120a-120c) are mandatory to support such single TID aggregation.

[0115] Some embodiments include a multi-TID A-MPDU aggregate payload that includes aggregated frames from two or more hidden addresses (corresponding to two or more group addresses) within a transmitted PPDU. If multi-TID A-MPDU aggregation is used, all receivers (e.g., non-AP MLDs 120a-120c) can receive the multi-TID A-MPDU aggregate, and AP MLD 110 can transmit the multi-TID A-MPDU aggregate. In some embodiments, AP MLD 110 uses a single indication to indicate its support for both sending multi-TID A-MPDUs for individually addressed frames and multi-TID A-MPDUs for GCR frames. In some embodiments, AP MLD 110 separately indicates (e.g., using two separate indications) its support for sending multi-TID A-MPDUs for individually addressed frames and its support for sending multi-TID A-MPDUs for GCR frames. In some embodiments, AP MLD 110 can assign a hidden address to each group address that complies with the GCR-MLO protocol. All receivers of the multi-TID A-MPDU of the GCR frame (eg, non-AP MLDs 120a-120c) have established GCR protocols with AP MLD 110 (each protocol corresponding to one GCR hidden address subject to such A-MPDU).

[0116] Figure 9B An example 950 of a non-GCR (eg, no acknowledgement / no retry) group addressed frame format according to some embodiments of the present disclosure is shown. Elements of other figures in this disclosure may be used to describe Figure 9B For example, AP MLD (e.g., Figure 1 An example 950 of a no-acknowledgement / no-retry group-addressed frame format may be sent by a legacy non-GCR station (e.g., an AP MLD 110) that is also a member of a GCR-MLO group. Figure 1 The no-acknowledgement / no-retry group-addressed frame may be a group-addressed frame where the group address is subject to a GCR-MLO protocol between an AP MLD 110 and at least one non-AP MLD 120 (e.g., non-AP MLDs 120a-120c) within an infrastructure basic service set (BSS) or between peer mesh stations in a mesh BSS.

[0117] In some embodiments, if at least one group member does not implement GCR, a no-acknowledgement / no-retry group addressing frame format may also be used to send frames that comply with the GCR protocol. For example, a GCR-MLO group may include legacy stations that do not support GCR (e.g., Figure 1To accommodate the legacy non-GCR supporting stations 140). To accommodate the legacy non-GCR supporting stations, the AP MLD 110 may send the no-acknowledgement / no-retry group-addressed frame format shown in example 950 across each of the links of the AP MLD 110 to serve at least the legacy non-GCR supporting stations 140. Any subsequent GCR frames sent by the AP MLD 110 include a hidden address that is not recognized by the legacy non-GCR supporting stations 140 (e.g., not passed to the MAC Service Access Point (SAP) of the legacy non-GCR supporting stations 140). In example 950, the no-acknowledgement / no-retry group-addressed frame format may be referred to as a non-GCR group-addressed frame format and includes a MAC header 960. The MAC header 960 may include a retry field 962 set to "0" and an address 1 field 964 set to the group address, which may be Figure 9A The sequence control field 966 uses the group address of the DA 922 and is hidden from the legacy non-GCR supporting stations 140. The sequence control field 966 uses SNS1 as described in IEEE P802.11 REVme_D0.0.

[0118] Figure 10A An example 1000 of GCR-MLO unsolicited retry with legacy non-GCR members—Mode 1 is shown, according to some embodiments of the present disclosure. Figure 10A The description may refer to elements of other figures in the present disclosure. For example, the AP MLD 1010 may be Figure 1 3 or AP MLD 310 of FIG. 3. AP1 1013, AP3 1015, and AP3 1017 may correspond to AP1 313, AP3 315, and AP3 317. Non-AP MLD A 1020a, non-AP MLD B 1020b, and non-AP MLD C 1020c may correspond to Figure 1 Non-AP MLD 120a-120c or Figure 3A The traditional SLDGCR members 1030 and the traditional non-GCR members 1040 may correspond to the non-AP MLDs 320a-320c. Figure 1 The traditional SLD station 130 and the traditional non-GCR supporting station 140.

[0119] Systems implementing GCR-MLO unsolicited retry can support backward compatibility with legacy devices. GCR-MLO unsolicited retry operation is possible even when some members of a GCR-MLO group corresponding to a group address include GCR-capable group members and some group members that do not. If at least one group member does not implement GCR, frames subject to the GCR unsolicited retry protocol can also be sent using the no-acknowledgement / no-retry frame format. For example, when a GCR-MLO group (corresponding to a group address and a hidden address) includes (a) a GCR-MLD-capable non-AP MLD (e.g., non-AP MLD 120a, 120b, or 120c) and (b) a legacy non-GCR-capable station (e.g., legacy non-GCR-capable station 140), some embodiments utilize GCR-MLO unsolicited retry as the retransmission strategy. The GCR-MLO unsolicited retry group may also include (c) a legacy GCR-SLO-capable station (e.g., legacy SLD station 130). A copy of the group-addressed frame is first sent on each link of the AP MLD 110 using a no-acknowledgement / no-retry format (e.g., example 950 of a non-GCR frame format) that is intended to be received by legacy non-GCR-capable stations 140. Any GCR frame may be sent via a GCR primary link (e.g., link 1 391 of FIG. 3 ) or via a link in a GCR primary link set (e.g., GCR primary link set 390) (e.g., link 2 395, link 3 397 of FIG. 3 ).

[0120] For both GCR-MLO unrequested retries and GCR-MLO block ACKs, when the GCR group contains both (a) legacy GCR-SLO-capable stations (e.g., legacy SLD GCR member 1030) and (b) GCR-MLO-capable non-AP MLDs, the legacy GCR-SLO-capable stations operate on the GCR primary link (e.g., link 1 1091) or one link (e.g., link 2 1095 or link 3 1097) in the GCR primary link set (e.g., GCR primary link set 1090), and the following conditions need to be met to achieve backward compatibility with the legacy GCR-SLO-capable STAs: i) none of the options for GCR-SLO / MLOAID assignment described in Table 3: AID Assignment Type are used; ii) the GCR-MLO protocol setup / update signaling described in paragraphs

[0064] and

[0065] is used; and iii) option 1 described in Table 1: GCR-MLO Security is used.

[0121] For both GCR-MLO unsolicited retries and GCR-MLO block ACKs, all options described in this disclosure may be used when the GCR group contains only non-AP MLDs that support GCR-MLO.

[0122] exist Figure 10A In Mode 1, the GCR-MLO group includes the following members: non-AP MLD A 1020a, non-AP MLD B 1020b, non-AP MLD C 1020c, legacy SLD GCR member D 1030, and legacy non-GCR member 1040. A GCR-MLO protocol can be established between AP MLD 1010 and each of non-AP MLD A 1020a, non-AP MLD B 1020b, and non-AP MLD C 1020c. A GCR-SLO protocol can be established between AP MLD 1010 and legacy SLD GCR member D 1030, but no GCR protocol can be established with legacy non-GCR member 1040. For Mode 1, during GCRF (GCR frame) delivery time, GCR-MLO group members are committed to being available on the GCR primary link, Link 1 1091.

[0123] GCRF 1005 refers to a GCR frame that complies with the GCR protocol (e.g., GCR-MLO). Based on the GCR-MLO group membership, AP MLD 1010 implements GCR-MLO unrequested retry as the GCRF retransmission policy and determines the number of GCRF 1005 retries. In addition, AP MLD 1010 determines and assigns a hidden address corresponding to the group address. Since the legacy non-GCR members 1040 do not support GCR, the AP MLD 1010 sends GCRF data using a no-acknowledgement / no-retry group addressed frame format (e.g., example 950 of the non-GCR frame format) on all links of the AP MLD 1010, which is shown as GCRF_SN=n 1045a on link 1 1091, GCRF_SN=n 1045b on link 2 1095, and GCRF_SN=n 1045c on link 3 1097, where the Address 1 field 964 is equal to the group address, and the corresponding GTKs corresponding to these links are used: GTK_1 1083, GTK_2 1085, GTK_3 1087, and the sequence number assigned from the SNS_GCR-MLO unrequested retry 1060 in the sequence control field 916.

[0124] AP MLD 1010 may retransmit GCRF data Retry GCRF_SN=n 1007 on the GCR primary link (link 1 1091) to legacy SLD GCR members 1030, non-AP MLD A 1020a, non-AP MLD B 1020b, and non-AP MLD C 1020c using the GCR frame format (as shown in example 900). The GCR frame format of Retry GCRF_SN=n 1007 may include a hidden address in Address 1 field 914, a sequence number assigned from SNS_GCR-MLO Unrequested Retry 1060 in Sequence Control field 916, and a group address in DA field 922. Retry GCRF_SN=n 1007 may be retransmitted multiple times, where the number of retries is set by AP MLD 1010. The GCR frame is sent using GTK_GCR-ML 1070.

[0125] When the AP MLD 1010 obtains information that the non-AP MLD A 1020a, MLD B 1020b, or non-AP MLD C is temporarily unavailable on the primary link 11091 but is available on a non-primary link (e.g., link 2 1095 or link 3 1097), the AP MLD 1010 and the non-AP MLDs 1020a-1020c utilize their multiple links using unsolicited retry as the retransmission strategy of the GCRF 1005 by sending a Retry GCRF_SN=n 1007 in a GCR frame format (e.g., example 900 of GCR frame transmission for GCR-MLO) on the non-GCR primary link (link 2 1095 or link 3 1097), wherein GTK_GCR-ML 1073 is used.

[0126] Figure 10B An example 1050 of GCR-MLO unsolicited retry with legacy non-GCR members - Mode 2 is shown, according to some embodiments of the present disclosure. Figure 10B The description may refer to elements of other figures in the present disclosure. For example, the AP MLD 1010 may be Figure 1 3 or AP MLD 310 of FIG. 3. AP1 1013, AP3 1015, and AP3 1017 may correspond to AP1 313, AP3 315, and AP3 317. Non-AP MLD A 1022, non-AP MLD B 1024, and non-AP MLD C 1026 may correspond to Figure 1 Non-AP MLD 120a-120c or Figure 3A The traditional SLD GCR members 1030 and the traditional non-GCR members 1040 may correspond to the non-AP MLDs 320a-320c. Figure 1 The traditional SLD station 130 and the traditional non-GCR supporting station 140.

[0127] Example 1000 focuses on Mode 1; Example 1050 is similar but focuses on Mode 2. In Example 1050, the GCR-MLO group includes the following members: non-AP MLD A 1022, non-AP MLD B 1024, non-AP MLD C 1026, legacy SLD GCR member D 1030, and legacy non-GCR member 1040. A GCR-MLO agreement can be established between AP MLD 1010 and each of non-AP MLD A 1022, non-AP MLD B 1024, and non-AP MLD C 1026. A GCR-SLO agreement can be established between AP MLD 1010 and legacy SLD GCR member D 1030, without establishing a GCR agreement with legacy non-GCR member 1040.

[0128] In example 1050, GCRF 1002 refers to a GCR frame that complies with the GCR protocol (e.g., GCR-MLO). Based on the GCR-MLO group membership, AP MLD 1010 implements GCR-MLO unsolicited retry as the GCRF's retransmission policy and determines the number of GCRF 1002 retries. In addition, AP MLD 1010 determines and assigns a hidden address corresponding to the group address. For Mode 2, during GCRF (GCR frame) delivery time, GCR-MLO group members strive to be available on at least one link within the GCR primary link set 1090 (e.g., Link 2 1095 and / or Link 3 1097). In some embodiments, if the GCR-MLO group members converge to a single link of the GCR primary link set 1090, example 1050 transitions to Mode 1.

[0129] Since the legacy non-GCR members 1040 do not support GCR, the AP MLD 1010 uses a non-GCR frame format (e.g., example 950 of the non-GCR frame format) to send GCRF data on all links of the AP MLD 1010, which is shown as GCRF_SN=n 1045a on link 1 1093, GCRF_SN=n 1045b on link 2 1095, and GCRF_SN=n 1045c on link 3 1097, where the Address 1 field 964 is equal to the group address, and the corresponding GTKs corresponding to these links are used: GTK_1 1083, GTK_2 1085, and GTK_3 1087.

[0130] AP MLD 1010 may retransmit GCRF data (e.g., Retry GCRF_SN=n (GCR frame format) 1004 and 1006) on all links of GCR primary link set 1090 (e.g., Link 2 1095 and Link 3 1097) to legacy SLD GCR members 1030, non-AP MLD A 1022, non-AP MLD B 1024, and non-AP MLD C 1026 using the GCR frame format. This GCR frame format is similar to example 900 in that the Address 1 field will include a hidden address corresponding to the group address, and the DA field will include the group address. However, the GCR-SLO frame format sequence control field will use SNS1 (as defined in IEEE P802.11 REVme). GCRF data in the GCR-SLO frame format may be retransmitted multiple times, with the retry count set by AP MLD 1010. The GCR frame format of Retry GCRF_SN=n 1004 and Retry GCRF_SN=n 1006 may include a hidden address in Address 1 field 914, a sequence number assigned from SNS_GCR-MLO Unrequested Retry 1060 in Sequence Control field 916, and a group address in DA field 922. Retry GCRF_SN=n 1004 and Retry GCRF_SN=n 1006 may be retransmitted multiple times, where the number of retries is set by AP MLD 1010. GCR frames are sent using GTK_GCR-ML 1070.

[0131] When the AP MLD 1010 obtains information that the non-AP MLD A 1021a, MLD B 1024, or non-AP MLD C 1026 is temporarily unavailable on a link in the primary link set 1090 but is available on a link in the non-primary link set (e.g., link 1 1093), the AP MLD 1010 and the non-AP MLDs 1022, 1024, and 1026 utilize their multiple links using unsolicited retry as the retransmission strategy of the GCRF 1002, using GTK_GCR-ML 1070, by sending Retry GCRF_SN=n 1004 and Retry GCRF_SN=n 1006 in a GCR frame format (e.g., example 900 of GCR frame transmission for GCR-MLO) on a link that does not belong to the primary link set.

[0132] Table 7: GCR-MLO: Unsolicited Retry - Modes 1 and 2 summarize the above transmission types. If all members of the GCR-MLO group are non-AP MLDs (e.g., supporting EHT / 11be), and GCR-SLO / MLO AID assignment option 1 as described in Table 3: AID assignment types is used, the AID assigned to the GCR group isGCR Uniquely identifies the GCR group (corresponding to the group address). The hidden address of this GCR group may not be generated by the AP MLD and sent to group members during the GCR protocol setup. Instead, the frame format of the no-acknowledgement / no-retry transmission of the group address frame can be used for GCR transmission instead of the GCR frame format.

[0133] Table 7: GCR-MLO: Unsolicited Retry - Modes 1 and 2

[0134]

[0135] When all members of the group corresponding to the group address support GCR, GCR-MLO block confirmation can be established in modes 1 and 2. During the GCR protocol setup, the AP MLD establishes the GCR primary link (mode 1) or a link in the GCR primary link set (mode 2). During the GCRF delivery time, the GCR member STA is committed to being available on the GCR primary link or a link in the GCR primary link set. If the GCR-MLO group includes a legacy GCR-SLD member (e.g., legacy SLD GCR member 1130), the legacy GCR-SLD member operates on the GCR primary link (mode 1) or one link in the GCR primary link set (mode 2), and the following conditions are met to ensure backward compatibility with legacy STAs that support GCR-SLO.

[0136] Figure 11A An example 1100 of GCR-MLO Block Acknowledgement—Mode 1 with legacy Single Link Device (SLD) GCR members is shown, according to some embodiments of the present disclosure. Figure 11A Reference may be made to elements of other figures in this disclosure for description. For example, the AP MLD 1110 may be Figure 1 3 or AP MLD 310 of FIG. 3. AP1 1113, AP3 1115, and AP3 1117 may correspond to AP1 313, AP3 315, and AP3 317. Non-AP MLD A 1120a, non-AP MLD B 1120b, and non-AP MLD C 1120c may correspond to Figure 1 Non-AP MLD 120a-120c or Figure 3A The non-AP MLD 320a-320c. The legacy SLD GCR member D 1130 may correspond to Figure 1 130 of the traditional SLD GCR members.

[0137] Figure 11AAn example 1100 of GCR-MLO Block Acknowledgement (Block ACK) with legacy SLD GCR members—Mode 1, according to some embodiments of the present disclosure, is shown. Assume that a GCR-MLO group includes the following members: non-AP MLD A 1120a, non-AP MLD B 1120b, non-AP MLD C 1120c, and legacy SLD GCR member D 1130. A GCR-MLO protocol can be established between AP MLD 1110 and each of non-AP MLD A 1120a, non-AP MLD B 1120b, and non-AP MLD C 1120c. A GCR-SLO protocol can be established between AP MLD 1110 and legacy SLD GCR member D 1130. Furthermore, all GCR-MLO group members establish a GCR BA protocol with AP MLD 1110. For Mode 1, GCR-MLO group members are committed to being available on the GCR primary link, Link 1 1191, during GCRF (GCR frame) delivery time.

[0138] AP MLD 1110 may send an initial GCR frame GCRFs_SN=n, (n+1), ..., x, ..., m 1107 using the GCR frame format. Transmissions are nominally on a GCR primary link of Mode 1 (e.g., Link 1 1191) or a GCR primary link set of Mode 2 (e.g., Figure 11B 1195 or link 3 1197). The GCR frame format for the GCRF (GCRF_SN=n, (n+1), ..., x, ..., m 1107) may include a hidden address in the address 1 field 914, a sequence number assigned from the SNS_GCR-MLO block acknowledgment 1165 in the sequence control field 916, and a group address in the DA field 922.

[0139] In some embodiments, due to temporary unavailability of one or more non-AP MLDs on a GCR primary link or a link in a GCR primary link set, the AP MLD 1110 may be disconnected from the GCR primary link (e.g., link 2 1195 or link 3 1197) or a link in a non-GCR primary link set (e.g., Figure 11B The initial GCR transmission is performed on link 1 1193 of the AP MLD 1110. AP MLD 1110 and non-AP MLDs 1120a-1120c utilize their multiple links using Block Ack retry as a retransmission strategy. AP MLD 1110 may perform retransmissions on a link (GCR master link, a link in the GCR master link set, or other link) selected by AP MLD 1110 based on, but not limited to, the following: Block Ack bitmaps from each member; lost Block Ack frames; and / or member availability on various links.

[0140] Example 1100 shows that after initially sending a GCRF (GCRF_SN=n, (n+1), ..., x, ..., m 1107), AP MLD 1110 sends a BAR (Block Ack Request) frame to each of the member non-AP MLD A 1120a, non-AP MLD B 1120b, non-AP MLD C 1120c, and legacy SLDGCR member D 1130. Based on the acknowledgment frames received from these GCR group members, AP MLD 1110 knows that the GCR frame with a sequence number (SN) equal to x (e.g., Retry GCRF_SN=x (GCR frame format) 1107) needs to be retransmitted on link 1 1191. The GCR frame format of GCRF_SN=n, (n+1), ..., x, ..., m 1107 and GCRF RetryGCRF_SN=x 1107 may include an example 900 of GCR frame transmission for GCR-MLO using GTK_GCR-ML 1170, and may include a hidden address in the address 1 field 914, a sequence number assigned from the SNS_GCR-MLO block confirmation 1165 in the sequence control field 916, and a group address in the DA field 922.

[0141] If all members, including legacy SLD GCR member D 1130, support multi-user (MU)-Block Acknowledgement Request / Block Acknowledgement (BAR / BA) exchanges, AP MLD 1110 may send MU-BAR / A, B, C, D 1145 identifying non-AP MLD A 1120 a, non-AP MLD B 1120 b, non-AP MLD C 1120 c, and legacy SLD GCR member D 1130, and may receive a corresponding BA response, shown as MU-BA / A, B, C, D 1143. If legacy SLD GCR member D 1130 does not support MU-BAR / BA, AP MLD 1110 may send and receive separate BAR / BA exchanges, shown as: MU-BAR / A, B, C 1125; MU-BA / A, B, C 1123; and BAR / SLD D 1135 and BA / SLD D 1133. The other GCRF retransmission is shown as GCRF_SN 1107m.

[0142] Figure 11B An example 1150 of GCR-MLO block validation with legacy SLD GCR members—Mode 2 is shown, according to some embodiments of the present disclosure. Figure 11BFigure 2 shows an example of GCR-MLO block confirmation with legacy SLD GCR members - Mode 2 according to some embodiments of the present disclosure. Elements of other figures in this disclosure may be used to describe Figure 11B For example, AP MLD 1110 may be Figure 1 3 or AP MLD 310 of FIG. 3. AP1 1113, AP3 1115, and AP3 1117 may correspond to AP1 313, AP3 315, and AP3 317. Non-AP MLD A 1122, non-AP MLD B 1124, and non-AP MLDC 1126 may correspond to Figure 1 Non-AP MLD 120a-120c or Figure 3A The traditional SLDGCR member D 1130 may correspond to the non-AP MLD 320a-320c. Figure 1 130 of the traditional SLD GCR members.

[0143] Assume that the GCR-MLO group includes the following members: non-AP MLD A 1122, non-AP MLD B 1124, non-AP MLD C 1126, and legacy SLD GCR member 1130. A GCR-MLO protocol can be established between AP MLD 1110 and each of non-AP MLD A 1122, non-AP MLD B 1124, and non-AP MLD C 1126. A GCR-SLO protocol can be established between AP MLD 1110 and legacy SLD GCR member D 1130. In addition, all GCR-MLO group members establish a GCRBA protocol with AP MLD 1110. For Mode 2, during GCRF (GCR frame) delivery time, GCR-MLO group members strive to be available on at least one link in the GCR primary link set 1190 (e.g., link 2 1195 or link 3 1197).

[0144] Example 1150 shows that after an initial transmission of GCRF_SN=n,(n+1),...,x,...,m 1104 using the GCR frame format on link 2 1995 and an initial transmission 1106 on link 3, AP MLD 1110 sends a BAR (Block Ack Request) frame to each of the member non-AP MLD A 1122, non-AP MLD B 1124, non-AP MLD C 1126, and legacy SLD GCR member D 1130. Based on the acknowledgment frames received from these GCR group members, AP MLD 1110 knows that the GCR frame with sequence number x (e.g., Retry GCRF_SN=x (GCR frame format) 1104) needs to be retransmitted on link 2 1195, and the GCR frame with sequence number y (e.g., Retry GCRF_SN=x (GCR frame format) 1106) needs to be retransmitted on link 3 1197. The GCR frame format of GCRF_SN=n, (n+1), ..., x, ..., m 1104, GCRF Retry GCRF_SN=x 1104 and GCRF Retry GCRF_SN=y1106 may include an example 900 of GCR frame transmission for GCR-MLO using GTK_GCR-ML 1170, and may include a hidden address in the address 1 field 914, a sequence number assigned from the SNS_GCR-MLO block confirmation 1165 in the sequence control field 916, and a group address in the DA field 922.

[0145] If all members including legacy SLD GCR member D 1130 support multi-user (MU)-block acknowledgement request / block acknowledgement (BAR / BA) exchange, AP MLD 1110 may send MU-BAR / C, D 1144 identifying non-AP MLD C 1126 and legacy SLD GCR member D 1130 on link 3 1197 and may receive corresponding BA responses shown as MU-BA / C, D 1142.

[0146] If legacy SLD GCR member D 1130 does not support MU-BAR / BA, then AP MLD 1110 may send and receive separate BAR / BA exchanges on link 3 1197, shown as: BAR / SLD D 1134 and BA / SLD 1132; and single user (SU)-BAR / C 1138 and BA / C 1136. Other GCRF retransmissions are shown as GCRF_SN 1106m.

[0147] AP MLD 1110 may send MU-BAR / A, B 1148 identifying non-AP MLD A 1122 and non-AP MLD B 1124 on link 2 1195 and may receive corresponding BA responses shown as MU-BA / A, B 1146. Other GCRF retransmissions are shown as GCRF_SN 1104m.

[0148] Table 8: GCR-MLO: Block Ack—Modes 1 and 2 summarizes the above discussion. If all members of a GCR-MLO group are non-AP MLDs (e.g., supporting EHT / 11be) and GCR-SLO / MLO AID assignment option 1 described in Table 3: AID Assignment Types is used, then the AID_GCR assigned to the GCR group uniquely identifies the GCR group (corresponding to the group address), and the hidden address of this GCR group may not be generated by the AP MLD and sent to group members during GCR protocol setup. Instead, the frame format for no-acknowledgement / no-retry transmission of the group address frame may be used for GCR transmission instead of the GCR frame format.

[0149] Table 8: GCR-MLO: Block Acknowledgement - Modes 1 and 2

[0150]

[0151]

[0152] Figure 12 An example 1200 of a frame exchange with a GCR multi-user (MU) block acknowledgement request (BAR) for GCR-MLO is shown according to some embodiments of the present disclosure. For convenience and not limitation, reference may be made to elements of other figures in the present disclosure to describe Figure 12 For example, example 1200 may include Figure 11B Elements such as AP MLD A 1110 , non-AP MLD A 1122 , non-AP MLD B 1124 , non-AP MLD C 1126 and legacy SLD GCR member D 1130 .

[0153] When the GCR-MLO protocol is established, the AP MLD 1110 can immediately initiate block negotiation with the non-AP STAs in the group. For the GCR Block Acknowledgement Request variant, TID_INFO = 0, as described in IEEE P802.11 REVme. To unify block acknowledgement operations for unicast and multicast, some embodiments allow the GCR Block Acknowledgement Request to be TID-specific (e.g., TID_INFO is not always 0): Option 1: Modify the existing GCR Block Acknowledgement Request variant. Option 2: Create a new GCR Block Acknowledgement Request variant, exemplarily named "TID-Specific GCR Block Acknowledgement Request Variant." For both Options 1 and 2 above, the new GCR Block Acknowledgement Request variant can request block acknowledgements for multiple TIDs using a single Block Acknowledgement Request.

[0154] Example 1200 shows AP MLD 1110 sending data and then sending a GCR MU-BAR trigger 1148 corresponding to non-AP MLD A 1122 and non-AP MLD B 1124. Non-AP MLD A 1122 and non-AP MLD B 1124 respond with corresponding block acknowledgments 1223 and 1227. If legacy SLD GCR member D 1130 does not support GCR MU-BAR, AP MLD 1110 may send a GCR MU BAR trigger 1138 corresponding to non-AP MLD C 1126, where the GCR MU BAR trigger 1138 allocates RUs only to non-AP MLD C 1126. Non-AP MLD C 1126 may respond with a corresponding block acknowledgment 1243. AP MLD 1110 may send a single user (SU) block acknowledgment request 1134 corresponding to legacy SLD GCR member D 1130. Legacy SLD GCR member D 1130 may respond with a Block Ack 1265. Based on the received Block Ack, AP MLD 1110 determines whether additional retransmissions are needed.

[0155] Figure 13 An example 1300 of creating multiple GCR subgroups corresponding to a single group address according to some embodiments of the present disclosure is shown. For convenience and not limitation, reference may be made to elements of other figures in the present disclosure to describe the present disclosure. Figure 13 .For example, Figure 1 AP MLD 110 or Figure 2The processor 265 of the system 200 can perform the functions described in example 1300 by executing instructions stored in the memory 285. In some embodiments, all group members corresponding to the group address support GCR-MLO, and the AP MLD 110 can map a group address 1310 to one or more hidden addresses (hidden address 1 1320, hidden address 2 1322, ..., hidden address N 1340, where N is an integer greater than 1). The hidden address (e.g., hidden address 1 1320) can correspond to a GCR subgroup identified by a GCR group ID (e.g., GCR ID 1 1360, GCR ID 2 1362, ..., GCR ID N 1380). In addition, hidden address x can be used for duplicate detection (e.g., duplicate frames). Each GCR subgroup (e.g., GCR ID 2 1362) can use a corresponding separate GTK_GCR-ML (subgroup n).

[0156] Figure 14 An exemplary method 1400 of an access point (AP) multi-link device (MLD) for GCR-MLO service according to some embodiments of the present disclosure is shown. For convenience and not limitation, the method 1400 may be described with reference to elements of other figures in the present disclosure. For example, the method 1400 may be performed by Figure 1 AP MLD 110 or Figure 2 The system 200 is executed by the processor 265, which executes instructions stored in the memory 285.

[0157] At 1405, AP MLD 110 exchanges signals with a non-AP MLD (e.g., non-AP MLD station 120a) to set up and / or update the GCR-MLO protocol. In some embodiments, AP MLD 110 may send a signal announcing the availability of GCR-MLO service for a group address (e.g., a group address that may be subject to the GCR-MLO protocol) and the AP MLD's GCR primary link or GCR primary link set. AP MLD 110 may receive the signal including the group address and the GCR primary link or GCR primary link set. In response to receiving the signal, AP MLD 110 may send the GCR-MLO group address, the GCR primary link or GCR primary link set, and an association identifier (AID) corresponding to the group address to non-AP MLD 120a. Some functions of the exchanged signals are described in 1415, 1420, 1425, 1430, 1435, and 1440, and the order of the functions may vary.

[0158] At 1415, the AP MLD 110 may assign an AID as the AID corresponding to the GCR-MLO group. GCRThe AP MLD 110 receives the AID_ GCR To allocate resource units (RUs). In some embodiments, the AID is common among all GCR groups.

[0159] At 1420, the AP MLD 110 may receive parameter inputs (e.g., requests to set certain parameters to certain values) from one or more members in the GCR-MLO group and assign one or more GCR operating parameters based on the received parameter inputs and the resources of the AP MLD 110. For example, the AP MLD 110 may receive a first parameter in a GCR-MLO request signal (e.g., requesting a GCR-SP duration of 3 milliseconds) from a first member in the GCR-MLO group and, based on at least the first parameter and input from another member in the group address, assign a GCR operating parameter different from the first parameter (e.g., allocating a GCR-SP duration of 5 milliseconds). The AP MLD 110 may then send the GCR operating parameter to the first member in a GCR-MLO response signal.

[0160] At 1425, the AP MLD 110 may utilize a reserved value (e.g., sub-element ID=2) of the Direct Multicast Service (DMS) state of the GCR-MLO response frame. For example, the AP MLD 110 may include GCR-MLO parameters including the group address, the GCR primary link or the GCR primary link set, and the AID corresponding to the group address in a sub-element of the DMS state, where the sub-element ID uses a reserved value (e.g., sub-element ID=2) in REVme_D0.0.

[0161] At 1430, AP MLD 110 may establish a GCR-MLO protocol with the station using a broadcast, multicast, or unicast method. For example, AP MLD 110 may use a broadcast or multicast frame to send the SP scheduling information. As another example, AP MLD 110 may use a unicast frame to send the SP scheduling information. In some embodiments, the SP established using the broadcast frame includes a broadcast target wake time (TWT) element, which may include a group address corresponding to the GCR-MLO group, a corresponding hidden address, and / or an identifier of the GCR-MLO group corresponding to the GCR-MLO protocol (e.g., a GCR-MLO group ID). When the GCR-SP is used for low-latency services, AP MLD 110 may modify the restricted TWT (rTWT) SP establishment method to establish the GCR-MLO SP. In some embodiments, 1430 may occur at any time after 1425.

[0162] At 1435, AP MLD 110 may send synchronous or semi-synchronous SPs on links in the GCR primary link set (e.g., Mode 2). For example, when the group address corresponds to the GCR primary link set, AP MLD 110 may send synchronous or semi-synchronous SPs on links in the GCR primary link set.

[0163] At 1440, when the GCR-MLO group includes a legacy GCR single link operation (SLO) station member, the AP MLD 110 may utilize the DMS state to establish a GCR-MLO protocol corresponding to the group address. For example, the AP MLD 110 may include GCR-MLO parameters including the group address, the GCR primary link or the GCR primary link set, and the AID of the group address in a sub-element corresponding to the DMS state, where the sub-element ID is a reserved value in REVme_D0.0 (e.g., sub-element ID=2).

[0164] At 1445, AP MLD 110 may establish a GCR-MLO protocol with a first member in the GCR-MLO group at the MLD level, where reception and transmission may occur on different links of AP MLD 110. For example, the group address, GCR primary link, or GCR primary link set may be received from the first member via any link of AP MLD 110, and the group address, hidden address, GCR primary link, or GCR primary link set, and an AID corresponding to the group address may be sent to the first member via any link of AP MLD 110. Subsequently, AP MLD 110 may transmit a GCR frame corresponding to the group address via the GCR primary link or the GCR primary link set.

[0165] At 1450, the AP MLD 110 may send a requested or unsolicited GCR update signal including: an updated delivery time, an updated hidden address, an updated GCR primary link or updated GCR primary link set, and / or an updated AID_ GCR This update can occur at any time after the establishment of GCR protocol 1445.

[0166] At 1455, AP MLD 110 may start GCR frame delivery. Some functions of GCR frame delivery are described in 1460, 1465, 1470, 1480, 1485, and 1490.

[0167] At 1460, AP MLD 110 utilizes the GCR primary link or GCR primary link set to transmit GCR frames during the GCR frame delivery time. When the group address corresponds to a GCR-MLO group, where all members are available on a common link during the GCR frame delivery time, AP MLD 110 may utilize the common link as the GCR primary link during the GCR frame delivery time. The GCR frame delivery time may be based on at least: a non-GCR-SP or a GCR-SP. When the GCR frame delivery time is based on a non-GCR-SP, the GCR frame delivery time occurs after a Delivery Traffic Indication Message (DTIM) beacon and after a no-acknowledgement / no-retry group-addressed frame delivery.

[0168] When the group address corresponds to a GCR-MLO group, where the members are not all available on a common link during GCR frame delivery time, the AP MLD 110 may utilize a GCR primary link set, where each of the members is available on at least one link within the GCR primary link set during the GCR frame delivery time.

[0169] At 1465, the AP MLD 110 may transmit an aggregate-media access control (MAC) protocol data unit (A-MPDU) including an aggregate payload having an aggregate GCR frame sharing a common traffic identifier (TID). For example, the AP MLD 110 may determine that the members of the GCR-MLO group are stations that support GCR and then transmit an A-MPDU including an aggregate payload having an aggregate GCR frame sharing a common TID. In some embodiments, the AP MLD 110 may determine that the members of the GCR-MLO group are capable of receiving aggregate GCR frames and transmit an A-MPDU including an aggregate payload having aggregate GCR frames corresponding to two or more TIDs.

[0170] At 1470, AP MLD 110 may implement either an unsolicited retry GCR-MLO retransmission policy or a block acknowledgement (BA) GCR-MLO retransmission policy. For example, AP MLD 110 may determine a maximum number of retries for a GCR frame corresponding to the group address and transmit the GCR frame based on the maximum number of retries. In some embodiments, AP MLD 110 may implement a block acknowledgement (BA) GCR-MLO retransmission policy. Thus, AP MLD 110 may determine that the first non-AP MLD 110 operates on more than one link in the GCR primary link set, determine a nominal link in the GCR primary link set on which to receive a GCR BA request (BAR), and transmit the nominal link to the first non-AP MLD 110 via a transceiver.

[0171] At 1480, the AP MLD 110 may provide an indication to the non-AP MLD to end the GCR-SP earlier than the scheduled duration of the GCR-SP. Thus, the non-AP MLD may return to power save mode before the scheduled duration of the GCR-SP. For example, the AP MLD 110 may send a first GCR-SP corresponding to the group address on a link in the GCR primary link set and send an indication to end the first GCR-SP before the scheduled duration of the first GCR-SP ends. In some embodiments, the indication includes, but is not limited to: a concatenation indication in the first trigger frame = 0, or the first trigger frame is not targeted at a member of the GCR-MLO group; more trigger frames (TF) = 0 in the second trigger frame for stations that do not have resource units (RUs) allocated by the second trigger frame; a quality of service (QoS) null frame; an end of SP (EOSP) = 1; more data (MD) = 0 in the GCR frame; and / or a GCR-SP termination indication.

[0172] At 1485, the AP MLD 110 may manage the GCR-SP that overlaps with other SPs. For example, the AP MLD 110 may send a TWTSP of a separately addressed frame that overlaps with the first GCR-SP corresponding to the group address on one link in the GCR primary link set. Subsequently, the AP MLD 110 may send an indication that the first GCR-SP ends before its maximum duration without affecting the TWT SP.

[0173] In some examples, AP MLD 110 may send an indication to end one GCR-SP without ending another overlapping GCR-SP. For example, AP MLD 110 may send a TWT SP of a separately addressed frame that overlaps with a first GCR-SP corresponding to a group address, along with a second GCR-SP, on a link in the GCR primary link set. Subsequently, AP MLD 110 may send an indication to end the first GCR-SP before its maximum duration without affecting the second GCR-SP.

[0174] At 1490, the AP MLD 110 may terminate one or more GCR-SPs and one or more TWT SPs using a trigger frame (TF) with More TF = 0. For example, the AP MLD 110 may send a trigger frame including More TF = 0, terminating the first GCR-SP, the second GCR-SP, and the TWT SP for stations that do not have resource units (RUs) allocated by the trigger frame.

[0175] Figure 15Another exemplary method 1500 for AP MLD of GCR-MLO according to some embodiments of the present disclosure is shown. For convenience and not limitation, the method 1500 may be described with reference to elements of other figures in the present disclosure. For example, the method 1500 may be performed by Figure 1 AP MLD 110 or Figure 2 The system 200 is executed by the processor 265, which executes instructions stored in the memory 285.

[0176] At 1505, AP MLD 110 may generate a group transient key (GTK) at the MLD level for use in sending GCR frames for GCR-MLO. For example, AP MLD 110 may generate GTK_GCR_ML at the MLD level, where GTK_GCR_ML is used to encrypt and decrypt GCR frames. In some embodiments, to generate GTK_GCR_ML at the MLD level, AP MLD 110 is further configured to utilize the AP MLD's MAC address as the authenticator address (AA). In some embodiments, AP MLD 110 may use GTK_GCR_ML to encrypt and decrypt GCR frames for all links of AP MLD 110. In some embodiments, AP MLD 110 may use a truncated version of GTK_GCR_ML to encrypt and decrypt group-addressed frames that are not compliant with the GCR protocol for the AP MLD 110 link.

[0177] At 1510, the AP MLD 110 may transmit a GCR frame for GCR multilink operation (MLO), the GCR frame including a sequence number assigned from a sequence number space (SNS) defined at the MLD level. For example, the AP MLD 110 may transmit a GCR frame compliant with the GCR-MLO protocol, the GCR frame including a sequence number assigned from SNS_GCR_MLO, where SNS_GCR_MLO is defined at the MLD level. In some embodiments, SNS_GCR_MLO may correspond to: an SNS_GCR_MLO unsolicited retry, which allows multiplicity and is indexed by address; or an SNS_GCR_MLO block acknowledgement, which allows multiplicity and is indexed by address and traffic identifier (TID).

[0178] At 1513, some functionality regarding GCR MLO operation is described in 1515, 1520, 1525, 1535, 1540 and / or 1545, in any order.

[0179] At 1515, the AP MLD 110 may switch between an unsolicited retry strategy and a block acknowledgement (BA) strategy for the group address and perform duplicate detection using the sequence number assigned from the SNS_GCR_MLO. During the switch, the AP MLD 110 may send, via the transceiver, the last SNS_GCR_MLO sequence number corresponding to the group address, which was delivered before the switch.

[0180] At 1520, the AP MLD 110 may detect and discard duplicate GCR frames using the SNS_GCR_MLO sequence number, where the detection and discarding are performed at the MLD level.

[0181] At 1525, the AP MLD 110 supports backward compatibility where a GCR-MLO group includes legacy non-GCR capable station members. For example, when a GCR frame corresponds to a GCR-MLO group including legacy non-GCR capable station members, the AP MLD 110 may utilize SNS_GCR_MLO unrequested retries, use sequence numbers assigned from the SNS_GCR_MLO, and send a no-acknowledgement / no-retry group-addressed frame corresponding to the GCR-MLO group on all links of the AP MLD 110.

[0182] In some embodiments, AP MLD 110 can establish a GCR-MLO protocol that includes a GCR primary link, on which members of the GCR-MLO group commit to being available for receiving GCR frames, wherein the initial GCR frame is sent via the primary link. In addition, AP MLD 110 can assign a retry count for the GCR frame. In some embodiments, AP MLD 110 can establish a GCR-MLO protocol that includes a GCR primary link set, on which members of the GCR-MLO group commit to being available for receiving GCR frames on links in the GCR primary link set, wherein the initial GCR frame is sent via the links in the GCR primary link set. AP MLD 110 can assign a retry count for the GCR frame.

[0183] At 1535, the AP MLD 110 supports backward compatibility where the GCR-MLO group includes legacy GCR single link operation (SLO) station members (e.g., legacy GCR single link devices (SLDs)). In some embodiments, the AP MLD 110 may utilize SNS_GCR_MLO unrequested retries and perform duplicate detection using a sequence number assigned from the SNS_GCR_MLO where the initial GCR frame was sent via the GCR primary link or a link in the GCR primary link set. In some embodiments, the AP MLD 110 may utilize an SNS_GCR_MLO block acknowledgement corresponding to the SNS_GCR_MLO sequence number where the GCR frame was sent via the GCR primary link or a link in the GCR primary link set. In some embodiments, AP MLD 110 may retransmit GCR frames via the transceiver based at least on: block acknowledgments from members in the GCR-MLO group; lost block acknowledgment frames; or availability of members in the GCR-MLO group on the GCR primary link or links in the GCR primary link set.

[0184] At 1540, when the GCR-MLO group includes one or more non-AP MLDs supporting GCR-MLO (supporting multi-user (MU)-Block Acknowledgement Request (BAR) / Block Acknowledgement (BA)), the AP MLD 110 supports MU-BAR / BA. For example, the AP MLD 110 may initiate negotiation with the one or more non-AP MLDs supporting GCR-MLO (supporting MU-BAR / BA), and after sending a GCR frame, send a MU-BAR to request a BA for one or more (e.g., multiple) TIDs.

[0185] At 1545, AP MLD 110 includes backward compatibility when legacy SLO station members do not support MU-BAR. For example, AP MLD 110 may initiate block negotiation with legacy SLO station members. After sending a GCR frame, a BAR is sent to request a BA from the legacy SLO station members.

[0186] At 1550, AP MLD 110 may support the GCR-MLO extension, in which a group address may be mapped to one or more hidden addresses. For example, AP MLD 110 may determine that all members of a GCR-MLO group support GCR-MLO. Based at least on this determination, AP MLD 110 may map the group address of the GCR-MLO group to one or more hidden addresses corresponding to one or more GCR subgroups. In some embodiments, the one or more GCR subgroups are identified by corresponding GCR IDs, where the corresponding GCR IDs correspond to corresponding GTK_GCR-MLs that are different from GTK_GCR_MLs. In some embodiments, AP MLD 110 may detect and discard duplicate hidden addresses of the one or more hidden addresses, where the detection and discarding are performed at the MLD level.

[0187] Figure 16 FIG1 shows an exemplary method 1600 for non-AP MLD for GCR-MLO service according to some embodiments of the present disclosure. For convenience and not limitation, the method 1600 may be described with reference to elements of other figures in the present disclosure. For example, the method 1600 may be performed by Figure 1 Non-AP MLD 120 (e.g., 120a-120c) or Figure 2 The processor 265 of the system 200 executes instructions stored in the memory 285. Some functions of the exchanged signals are described in 1615, 1620, 1625, 1630, and 1640, and the order of these functions may vary. At 1605, a non-AP MLD station (e.g., non-AP MLD station 120a) exchanges signals with an AP MLD (e.g., AP MLD 110) to set up and / or update the GCR-MLO protocol.

[0188] At 1615, the non-AP MLD station 120a may receive the assigned AID as the AID corresponding to the GCR-MLD group. GCR The AP MLD 110 receives the AID_ GCR To allocate resource units (RUs). In some embodiments, the AID is common among all GCR groups.

[0189] At 1620, the non-AP MLD station 120a may send parameter inputs to the AP MLD 110 (e.g., requesting that certain parameters be set to certain values). The AP MLD 110 may then assign one or more GCR operating parameters based on the parameter inputs and other received parameter inputs and AP MLD 110 resources. For example, the AP MLD 110 may receive first parameters in a GCR-MLO request signal from the non-AP MLD station 120a, a first member of the GCR-MLO group, and based on at least the first parameters and input from another member of the GCR-MLO group corresponding to the group address, the AP MLD 110 may assign GCR operating parameters that are different from the first parameters. The non-AP MLD station 120a may then receive the GCR operating parameters in a GCR-MLO response signal from the AP MLD 110.

[0190] At 1625, the non-AP MLD station 120a may include GCR-MLO parameters, including the group address and preferred GCR primary link or GCR primary link set, in a sub-element of the DMS descriptor, where the sub-element ID uses a reserved value in REVme_D0 (eg, sub-element ID = 2).

[0191] At 1630, the non-AP MLD station 120a may establish a GCR-MLO protocol with the AP MLD 110 using a multicast or unicast method. For example, the non-AP MLD station 120a may receive a broadcast frame, a multicast frame, or a unicast frame used to establish an SP for delivering GCR frames compliant with the GCR-MLO protocol. In some embodiments, the broadcast SP includes a broadcast TWT SP that includes a group address corresponding to the GCR-MLO group, a hidden address, and / or an identifier of the GCR-MLO group corresponding to the GCR-MLO protocol (e.g., a GCR-MLO group ID). When the GCR-SP enables low-latency service, the restricted TWT SP may be modified by the AP MLD 110 for GCR-MLO SP establishment. In some embodiments, the SP established using the broadcast frame includes a broadcast target wake time (TWT) element, which may include a group address corresponding to the GCR-MLO group, a corresponding hidden address, and / or an identifier of the GCR-MLO group corresponding to the GCR-MLO protocol (e.g., a GCR-MLO group ID). When GCR-SP is used for low-latency services, non-AP MLDs may receive such modified broadcast target wake time (TWT) elements.

[0192] At 1640, the non-AP MLD station 120a may utilize the DMS descriptor to establish a GCR-MLO protocol corresponding to the group address. For example, the non-AP MLD 120a may include GCR-MLO parameters, including the group address and the preferred GCR primary link or GCR primary link set, in a sub-element of the DMS descriptor, where the sub-element ID uses a reserved value in REVme_D0.0 (e.g., sub-element ID = 2).

[0193] At 1645, the non-AP MLD station 120a may be the first member in the GCR-MLO group and may establish a GCR-MLO protocol with the AP MLD 110 at the MLD level. During the establishment of the GCR-MLO protocol, reception and transmission may occur on different links of the non-AP MLD station 120a. For example, the group address, GCR primary link, or GCR primary link set may be transmitted via any link of the non-AP MLD station 120a, and the group address, corresponding hidden address, GCR primary link, or GCR primary link set, and AID corresponding to the group address may be received by the non-AP MLD station 120a via any link of the non-AP MLD station 120a. Subsequently, the non-AP MLD station 120a may receive a GCR frame corresponding to the group address via the GCR primary link or GCR primary link set.

[0194] At 1650, the non-AP MLD station 120a may receive a requested or unsolicited GCR update signal including: an updated delivery time, an updated GCR primary link or updated GCR primary link set, and / or an updated AID_ GCR This update can occur at any time after the GCR protocol is established.

[0195] At 1655, the non-AP MLD station 120 may begin receiving GCR frames. Some functions of GCR frame reception are described in 1660, 1665, 1670, 1680, 1685, and 1690.

[0196] At 1660, the non-AP MLD station 120a receives a GCR frame via the GCR primary link or via a link in the GCR primary link set during a GCR frame delivery time. The GCR frame delivery time may be based on at least: a non-GCR-SP or a GCR-SP. When the GCR frame delivery time is based on a non-GCR-SP, the GCR frame delivery time occurs after the DTIM beacon and after the delivery of a no-acknowledgement / no-retry group addressed frame.

[0197] At 1665, the non-AP MLD station 120a may receive an A-MPDU including an aggregate payload with an aggregated GCR frame that shares a common traffic identifier (TID). In some embodiments, the non-AP MLD station 120a may receive an A-MPDU including an aggregate payload with an aggregated GCR frame corresponding to two or more TIDs.

[0198] At 1670, the non-AP MLD station 120a may implement an unsolicited retry GCR-MLO retransmission policy or a block acknowledgement (BA) GCR-MLO retransmission policy. For example, the AP MLD 110 may determine a maximum number of retries for a GCR frame corresponding to the group address; and the non-AP MLD station 120a may receive the GCR frame based on the maximum number of retries. In some embodiments, the non-AP MLD station 120a may implement a block acknowledgement (BA) GCR-MLO retransmission policy. Thus, the AP MLD 110 may determine that the first non-AP MLD 110 operates on more than one link in the GCR primary link set, determine a nominal link in the GCR primary link set on which to receive the GCR BA request (BAR), and the non-AP MLD station 120a may receive the BAR from the AP MLD 110 via the nominal link.

[0199] At 1680, the non-AP MLD station 120a may receive an indication from the AP MLD 110 that the GCR-SP is ending earlier than the scheduled duration of the GCR-SP. Thus, the non-AP MLD 120a may return to power save mode before the scheduled duration of the GCR-SP. For example, the non-AP MLD station 120a may receive a first GCR-SP corresponding to a group address on a link in the GCR primary link set and receive an indication that the first GCR-SP is ending before the scheduled duration of the first GCR-SP ends. In some embodiments, the received indications include, but are not limited to: a concatenation indication in the first trigger frame = 0, or the first trigger frame is not targeted at a member of the GCR-MLD group; more trigger frames (TF) = 0 in the second trigger frame, and the non-AP MLD station 120a does not have a station resource unit (RU) allocated by the second trigger frame; a quality of service (QoS) null frame; an end of SP (EOSP) = 1; more data (MD) = 0 in the GCR frame; and / or a GCR-SP termination indication.

[0200] At 1685, non-AP MLD station 120a may receive a GCR frame within a GCR-SP that overlaps with other SPs. For example, APMLD 110 may send a TWT SP of an individually addressed frame that overlaps with a first GCR-SP corresponding to a group address on one of the links in the GCR primary link set. AP MLD 110 may then send an indication that the first GCR-SP ends before its maximum duration without affecting the TWT SP.

[0201] In some examples, the non-AP MLD station 120a may receive an indication from the AP MLD 110 to end one GCR-SP without ending another overlapping GCR-SP. For example, the non-AP MLD station 120a may receive a TWT SP of an individually addressed frame that overlaps with a first GCR-SP corresponding to a group address, and a second GCR-SP from the AP MLD 110 on one link in the GCR primary link set. Subsequently, the non-AP MLD station 120a may receive an indication from the AP MLD 110 to end the first GCR-SP before its maximum duration without affecting the second GCR-SP.

[0202] At 1690, after the AP MLD 110 terminates one or more GCR-SPs and one or more TWT SPs corresponding to the non-AP MLD station 120a, the non-AP MLD station 120a may return to the power saving mode. For example, the AP MLD 110 may send a trigger frame (TF) with more TF=0, terminating the first GCR-SP, the second GCR-SP, and the TWT SP for the non-AP MLD station 120a that does not have resource units (RUs) allocated by the trigger frame.

[0203] Figure 17 Another exemplary method 1700 for a non-AP MLD station (e.g., non-AP MLD station 120a) for GCR-MLO according to some embodiments of the present disclosure is shown. For convenience and not limitation, the method 1700 may be described with reference to elements of other figures in the present disclosure. For example, the method 1700 may be performed by Figure 1 The non-AP MLD station 120a or Figure 2 The system 200 is executed by the processor 265, which executes instructions stored in the memory 285.

[0204] At 1705, the non-AP MLD station 120a may receive a GCR frame for GCR multilink operation (MLO), the GCR frame including a sequence number assigned by a sequence number space (SNS) defined at the MLD level. For example, the non-AP MLD station 120a may receive a GCR frame compliant with the GCR-MLO protocol, the GCR frame including an SNS_GCR_MLO sequence number assigned at the MLD level. In some embodiments, the SNS_GCR_MLO may correspond to: an SNS_GCR_MLO unsolicited retry, which allows multiplicity and is indexed by an address (e.g., a group address corresponding to a GCR-MLO group); or an SNS_GCR_MLO block acknowledgement, which allows multiplicity and is indexed by an address and a traffic identifier (TID).

[0205] At 1710, the non-AP MLD station 120a may utilize a group transient key (GTK) generated at the MLD level for receiving GCR frames. For example, the AP MLD 110 may generate a GTK_GCR_ML at the MLD level, where the GTK_GCR_ML is used to encrypt and decrypt GCR frames. In some embodiments, the non-AP MLD station 120a may use the GTK_GCR_ML to encrypt and decrypt group-addressed frames that are not subject to the GCR protocol for all links to the non-AP MLD station 120a. In some embodiments, the non-AP MLD station 120a may use a truncated version of the GTK_GCR_ML to encrypt and decrypt group-addressed frames that are not subject to the GCR protocol for links to the non-AP MLD station 120a.

[0206] At 1713, some functionality regarding GCR MLO operation is described in 1715, 1720, 1525 and / or 1740, in any order.

[0207] At 1715, the non-AP MLD station 120a may switch between an unsolicited retry policy and a block acknowledgement (BA) policy. For example, the AP MLD 110 may switch between an unsolicited retry policy and a BA policy for a group address. During the switch, the non-AP MLD station 120a may receive the last SNS_GCR_MLO sequence number corresponding to the group address from the AP MLD 110, which was delivered before the switch.

[0208] At 1720 , the non-AP MLD station 120 a may detect and discard duplicate GCR frames using the sequence numbers assigned by SNS_GCR_MLO defined at the MLD level, where the detection and discarding are performed at the MLD level.

[0209] At 1740, the non-AP MLD station 120a may support multi-user (MU)-block acknowledgement request (BAR) / block acknowledgement (BA). For example, the AP MLD 110 may initiate block negotiation with the non-AP MLD station 120a. After receiving the GCR frame from the AP MLD 110, the non-AP MLD station 120a may receive the MU-BAR to send a BA for one or more (e.g., multiple) TIDs.

[0210] At 1750, the non-AP MLD station 120a may support the GCR-MLO extension, in which a group address may be mapped to one or more hidden addresses. For example, the AP MLD 110 may determine that all members of the GCR-MLO group support GCR-MLO. Based at least on this determination, the AP MLD 110 may map the group address of the GCR-MLO group to one or more hidden addresses corresponding to one or more GCR subgroups. In some embodiments, the one or more GCR subgroups are identified by corresponding GCR IDs, where the corresponding GCR IDs correspond to corresponding GTK_GCR-MLs that are different from GTK_GCR_MLs. In some embodiments, the non-AP MLD station 120a may detect and discard duplicate hidden addresses of the one or more hidden addresses, where the detection and discarding are performed at the MLD level.

[0211] You can use, for example, Figure 18 Various embodiments may be implemented using one or more well-known computer systems, such as the computer system 1800 shown. The computer system 1800 may be any well-known computer capable of performing the functions described herein. For example, and without limitation, Figure 2 System 200, Figure 14 Method 1400, Figure 15 Method 1500, Figure 16 Method 1600, Figure 17 The method 1700 (and / or other devices and / or components shown in the figure) can be implemented using the computer system 1800 or a portion thereof.

[0212] Computer system 1800 includes one or more processors (also referred to as central processing units or CPUs) such as processor 1804. Processor 1804 is connected to a communication infrastructure 1806, which may be a bus. One or more processors 1804 may each be a graphics processing unit (GPU). In an embodiment, a GPU is a processor that is a specialized electronic circuit designed to process mathematically intensive applications. A GPU may have an efficient parallel architecture for processing large blocks of data in parallel, such as mathematically intensive data commonly used in computer graphics applications, images, videos, and the like.

[0213] The computer system 1800 also includes user input / output devices 1803, such as a monitor, keyboard, pointing device, etc., that communicate with the communication infrastructure 1806 through the user input / output interface 1802. The computer system 1800 also includes main memory or internal memory 1808, such as random access memory (RAM). The main memory 1808 may include one or more levels of cache. The main memory 1808 has control logic (e.g., computer software) and / or data stored therein.

[0214] The computer system 1800 may also include one or more secondary storage devices or memories 1810. For example, the secondary storage 1810 may include a hard drive 1812 and / or a removable storage device or drive 1814. The removable storage drive 1814 may be a floppy disk drive, a tape drive, an optical drive, an optical storage device, a tape backup device, and / or any other storage device / drive.

[0215] Removable storage drive 1814 can interact with removable storage unit 1818. Removable storage unit 1818 includes a computer-usable or readable storage device having computer software (control logic) and / or data stored therein. Removable storage unit 1818 can be a floppy disk, magnetic tape, compact disk, DVD, optical storage disk, and / or any other computer data storage device. Removable storage drive 1814 reads from and / or writes to removable storage unit 1818 in a well-known manner.

[0216] According to some embodiments, secondary storage 1810 may include other devices, means, or other methods for allowing computer system 1800 to access computer programs and / or other instructions and / or data. Such devices, means, or other methods may include, for example, a removable storage unit 1822 and an interface 1820. Examples of removable storage unit 1822 and interface 1820 may include a program cartridge and cartridge interface (such as that found in a video game device), a removable memory chip (such as an EPROM or PROM) and associated socket, a memory stick and USB port, a memory card and associated memory card slot, and / or any other removable storage unit and associated interface.

[0217] The computer system 1800 may also include a communication or network interface 1824. The communication interface 1824 enables the computer system 1800 to communicate and interact with any combination of remote devices, remote networks, remote entities, and the like (individually and collectively referenced by reference numeral 1828). For example, the communication interface 1824 may allow the computer system 1800 to communicate with the remote device 1828 via a communication path 1826, which may be wired and / or wireless and may include any combination of a LAN, a WAN, the Internet, and the like. Control logic and / or data may be sent to and from the computer system 1800 via the communication path 1826.

[0218] The operations in the foregoing embodiments can be implemented in a variety of configurations and architectures. Thus, some or all of the operations in the foregoing embodiments can be performed in hardware, software, or in both hardware and software. In some embodiments, a tangible, non-transient device or article includes a tangible, non-transient computer-usable or readable medium on which a control logic component (software) is stored, also referred to herein as a computer program product or program storage device. This includes, but is not limited to, computer system 1800, main memory 1808, auxiliary memory 1810, and removable storage units 1818 and 1822, as well as tangible articles embodying any combination of the foregoing. When executed by one or more data processing devices (such as computer system 1800), such control logic components cause such data processing devices to operate as described herein.

[0219] Based on the teachings contained in this disclosure, it will be apparent to those skilled in the relevant art how to use Figure 18 The embodiments of the present disclosure may be made and used with data processing devices, computer systems, and / or computer architectures other than those shown. In particular, the embodiments may operate with software, hardware, and / or operating system implementations other than those described herein.

[0220] It should be understood that the Detailed Description section, and not the Summary and Abstract sections, is intended to be used to interpret the claims. The Summary and Abstract sections may set forth one or more, but not all, exemplary embodiments of the present disclosure as contemplated by the inventors, and thus, are not intended to limit the present disclosure or the appended claims in any way.

[0221] Although the present disclosure has been described herein with reference to exemplary embodiments of exemplary fields and applications, it should be understood that the present disclosure is not limited thereto. Other embodiments and modifications are possible and are within the scope and spirit of the present disclosure. For example, and without limiting the generality of this paragraph, the embodiments are not limited to the software, hardware, firmware, and / or entities shown in the figures and / or described herein. In addition, the embodiments (whether or not explicitly described herein) have significant utility for fields and applications beyond the examples described herein.

[0222] Embodiments have been described herein with the aid of functional building blocks illustrating the implementation of specific functions and relationships thereof. For ease of description, the boundaries of these functional building blocks have been arbitrarily defined herein. Alternative boundaries may be defined so long as the specified functions and relationships (or their equivalents) are appropriately performed. Additionally, alternative embodiments may perform functional blocks, steps, operations, methods, etc., in an order different from that described herein.

[0223] References herein to "one embodiment," "an embodiment," "an exemplary embodiment," or similar phrases indicate that the described embodiment may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Furthermore, when particular features, structures, or characteristics are described in connection with an embodiment, it is within the knowledge of those skilled in the relevant art to incorporate those features, structures, or characteristics into other embodiments, whether or not explicitly mentioned or described herein.

[0224] The breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

[0225] This disclosure contemplates that entities responsible for collecting, analyzing, disclosing, transmitting, storing, or otherwise using such personal information will adhere to established privacy policies and / or practices. Specifically, such entities should implement and adhere to privacy policies and practices that are recognized as meeting or exceeding industry or government requirements for maintaining the privacy and security of personal information. Such policies should be easily accessible to users and updated as the collection and / or use of data changes. Personal information collected from users should be used for the entity's legitimate and reasonable purposes and not shared or sold beyond those legitimate uses. Furthermore, such collection / sharing should only be done with the user's informed consent. Furthermore, such entities should consider taking any necessary steps to safeguard and secure access to such personal information and ensure that others with access to the personal information adhere to their privacy policies and procedures. Furthermore, such entities may subject themselves to third-party assessments to demonstrate compliance with widely accepted privacy policies and practices. Furthermore, policies and practices should be tailored to the specific type of personal information collected and / or accessed, and to applicable laws and standards, including jurisdictional considerations. For example, in the United States, the collection or access of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); whereas health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy practices should be maintained for different types of personal data in each country.

Claims

1. An access point (AP) multi-link device (MLD), comprising: transceiver; and a processor communicatively coupled to the transceiver and configured to: sending, via the transceiver, an advertisement indicating availability of a multicast GCR-Multilink Operation (MLO) service with retry for a group address; receiving, via the transceiver, a GCR request including the group address associated with the GCR-MLO service, wherein the group address corresponds to a GCR-MLO group, at least one member of which is unavailable on a common link during a GCR frame delivery time; as well as A GCR response is sent via the transceiver, the GCR response including the group address, a GCR primary link set, and an association identifier AID corresponding to the group address, for which a plurality of GCR-MLO group members are available on at least one link within the GCR primary link set during the GCR frame delivery time. 2 . The AP MLD according to claim 1 , wherein the GCR frame delivery time is based on a non-GCR-service period (SP). 3 . The AP MLD according to claim 2 , wherein when the GCR frame delivery time is based on the non-GCR-SP, the GCR frame delivery time occurs after a delivery traffic indication message (DTIM) beacon.

4. The AP MLD according to claim 1, wherein the processor is further configured to: Assign the AID as the AID corresponding to the first GCR-MLO group GCR ;as well as Allocate resource units RU for sending group-addressed frames to the GCR Identify the first GCR-MLO group.

5. The AP MLD according to claim 1 , wherein the processor is further configured to: An aggregate-medium access control MAC protocol data unit (A-MPDU) is transmitted via the transceiver, the A-MPDU including an aggregate payload having an aggregate GCR frame corresponding to two or more traffic identifiers (TIDs), wherein the two or more TIDs correspond to two or more hidden addresses.

6. The AP MLD of claim 1, wherein the GCR request is received from a first member in the group address via any link of the AP MLD, and wherein the GCR response is sent to the first member via any link of the AP MLD.

7. The AP MLD according to claim 6, wherein the processor is further configured to: A GCR frame corresponding to the group address is transmitted via the transceiver over the GCR primary link set.

8. The AP MLD according to claim 1, wherein the processor is further configured to: sending, via the transceiver, a requested or unsolicited GCR update signal, the GCR update signal comprising: Updated delivery time, updated GCR primary link set, or updated AID_ GCR .

9. The AP MLD according to claim 1, wherein the AID is an AID corresponding to the first GCR-MLO group. GCR , and wherein the GCR-MLO retransmission strategy includes a block acknowledgement BA, the processor is further configured to: sending a group-addressed data frame to the first GCR-MLO group; After sending the group-addressed data frame, sending a GCR multi-user MU-BA request BAR trigger frame, the GCR multi-user MU-BA request BAR trigger frame including resource unit RU allocations for a first non-AP MLD GCR member and a second non-AP MLD GCR member of the first GCR-MLO group; and In response to the GCR MU-BAR trigger frame, a first BA frame is received from the first non-AP MLD GCR member, and a second BA frame is received from the second non-AP MLD GCR member.

10. The AP MLD according to claim 9, wherein the first GCR-MLO group includes legacy single-link device (SLD) GCR members that do not support GCR MU-BAR, and the processor is configured to: sending a single user SU BAR frame including RU allocations for the legacy SLD GCR members; and A third BA frame is received from the legacy SLD GCR member in response to the SU BAR frame.

11. A non-access point (AP) multi-link device (MLD) station, comprising: transceiver; and a processor communicatively coupled to the transceiver and configured to: receiving, via the transceiver, an advertisement indicating availability of a multicast GCR-Multilink Operation (MLO) service with retry for a group address of which the non-AP MLD station is a member; sending, via the transceiver, a GCR request including the group address associated with the GCR-MLO service, wherein the group address corresponds to a GCR-MLO group, at least one member of which is unavailable on a common link during a GCR frame delivery time; as well as A GCR response is received via the transceiver, the GCR response including the group address, a GCR primary link set, and an association identifier AID corresponding to the group address, for which a plurality of GCR-MLO group members are available on at least one link within the GCR primary link set during the GCR frame delivery time.

12. The non-AP MLD station of claim 11 , wherein the processor is further configured to: transmitting, via the transceiver, a first value of a GCR operating parameter in a GCR request; A second value of the GCR operating parameter is received in a GCR response via the transceiver, wherein the first value and the second value are different.

13. The non-AP MLD station of claim 11 , wherein the processor is further configured to: receiving, via the transceiver, a requested or unsolicited GCR update signal, the GCR update signal comprising: Updated delivery time, updated GCR primary link set, or updated AID_ GCR .

14. A non-transitory computer-readable medium storing instructions, wherein when executed by a processor of a first electronic device, the instructions cause the first electronic device to perform operations for an access point (AP) multi-link device (MLD), the operations comprising: sending a notification indicating availability of a multicast GCR-Multilink Operation (MLO) service with retry for a group address; receiving a GCR request including the group address associated with a GCR-MLO service, wherein the group address corresponds to a GCR-MLO group, at least one member of which is unavailable on a common link during a GCR frame delivery time; as well as A GCR response is sent, the GCR response including the group address, a GCR primary link set, and an association identifier AID corresponding to the group address, for which a plurality of GCR-MLO group members are available on at least one link within the GCR primary link set during the GCR frame delivery time.

15. The non-transitory computer-readable medium of claim 14, wherein when the GCR-MLO retransmission policy includes unsolicited retries, the operations further comprise: determining a maximum number of retries for a GCR frame corresponding to the group address; as well as Retransmissions of the GCR frame corresponding to the maximum number of retries are sent.

16. The non-transitory computer-readable medium of claim 14, wherein the GCR-MLO retransmission strategy includes a block acknowledgement (BA), the operations further comprising: determining that a first non-AP MLD operates on more than one link of the GCR primary link set; determining a nominal link of the GCR primary link set, and receiving a GCR BA request (BAR) on the nominal link; as well as The nominal link is sent to the first non-AP MLD.

17. The non-transitory computer-readable medium of claim 14, wherein the operations further comprise: receiving a first value of a GCR operating parameter in a GCR request from a first member of the group address; assigning a second value for the GCR operating parameter based at least on the first value and input from another member of the group address, the second value being different from the first value; and The second value of the GCR operating parameter in a GCR response is sent to the first member.

18. The non-transitory computer-readable medium of claim 14, wherein the operations further comprise: A GCR frame compliant with the GCR-MLO protocol corresponding to the group address is sent in a GCR-service period SP, wherein the GCR frame includes an indication enabling a receiving station to enter a sleep state before a maximum duration of the GCR-SP.

19. The non-transitory computer readable medium of claim 14, wherein the AID is an AID corresponding to a first GCR-MLO group. GCR , and wherein the GCR-MLO retransmission strategy includes a block acknowledgement BA, the operations further comprising: sending a group-addressed data frame to the first GCR-MLO group; After sending the group-addressed data frame, sending a GCR multi-user MU-BA request BAR trigger frame, the GCR multi-user MU-BA request BAR trigger frame including resource unit RU allocations for a first non-AP MLD GCR member and a second non-AP MLD GCR member of the first GCR-MLO group; as well as In response to the GCR MU-BAR trigger frame, a first BA frame is received from the first non-AP MLD GCR member, and a second BA frame is received from the second non-AP MLD GCR member.

20. The non-transitory computer-readable medium of claim 19, wherein the first GCR-MLO group includes legacy single-link device (SLD) GCR members that do not support GCR MU-BAR, the operations further comprising: sending a single user SU BAR frame including RU allocations for the legacy SLD GCR members; as well as A third BA frame is received from the legacy SLD GCR member in response to the SU BAR frame.

Images