Wireless fidelity devices with dynamic capability allocation and related capability allocation methods

Abstract

A capability allocation method for a Wi-Fi device includes: during association between the Wi-Fi device and another Wi-Fi device, setting a first capability allocation for a first non-AP (Access Point) STA, wherein each Wi-Fi device includes multiple stations, each station belonging to the other Wi-Fi device is an AP, each station belonging to the Wi-Fi device is a non-AP STA, the first AP belongs to the other Wi-Fi device, and the first non-AP STA belongs to the Wi-Fi device; and after the first non-AP STA is associated with the first AP, changing the first capability allocation of the first non-AP STA without re-associating it. Using this scheme, the capability allocation of AP STAs can be dynamically changed.

Description

Technical Field

[0001] This invention relates to the field of wireless communication, and more particularly to a wireless fidelity (Wi-Fi) device with dynamic capability allocation and a related capability allocation method. Background Technology

[0002] In Wi-Fi multi-link operation (MLO), multiple links may exist between two multi-link devices (MLDs), which include an access point (AP) MLD and a non-AP MLD. These links can operate independently to increase overall throughput and / or improve connection stability. An AP MLD can be considered to have multiple APs belonging to the same MLD. A non-AP MLD can be considered to have multiple non-AP sites (STAs) belonging to the same MLD. More specifically, each of the AP MLD and non-AP MLDs can include multiple sites, where each site belonging to the same AP MLD is an AP, and each site belonging to the same non-AP MLD is a non-AP STA. APs or non-AP STAs within the same MLD can share resources such as memory, antennas, and / or radios. Furthermore, the MLD can manage the allocation of these resources. The capability allocation set for a non-AP MLD is not necessarily the same as the capability allocation set for an AP MLD. After the capability allocation of the non-AP MLD and the AP MLD are set, the number of enabled links between a non-AP MLD and an AP MLD may change.

[0003] In a dual-band dual concurrent (DBDC) or triple-band triple concurrent (TBTC) host, multiple devices (sites) can operate independently. For an APDBDC / TBTC host, each subordinate device (site) is an AP. For a STADBDC / TBTC host, each subordinate device (site) is a non-AP STA. APs or non-STAs within the same DBDC / TBTC host can share resources such as memory, antennas, and / or radios. Furthermore, the DBDC / TBTC host can manage the allocation of these resources. The capacity allocation configured for a STADBDC / TBTC host is not necessarily the same as that configured for an AP DBDC / TBTC host. After the capacity allocations for STADBDC / TBTC and AP DBDC / TBTC hosts are configured, the number of links between a STA DBDC / TBTC host and an AP DBDC / TBTC host may change.

[0004] Therefore, an innovative dynamic capability allocation scheme is needed to update capability allocation settings for affiliated non-AP STAs within a Wi-Fi device (e.g., a non-AP MLD or STA DBDC / TBTC host). Summary of the Invention

[0005] One of the objectives of this invention is to provide a Wi-Fi device with dynamic capability allocation and a related capability allocation method.

[0006] According to a first aspect of the present invention, an exemplary capability allocation method employed by a Wi-Fi device is disclosed. The exemplary capability allocation method includes: setting a first capability allocation for a first non-AP STA during association between the Wi-Fi device and another Wi-Fi device; and changing the first capability allocation for the first non-AP STA without re-association after the first non-AP STA is associated with a first AP. Each of the Wi-Fi device and the other Wi-Fi device includes multiple sites. Each site belonging to the other Wi-Fi device is an AP, each site belonging to the Wi-Fi device is a non-AP STA, the first AP belongs to the other Wi-Fi device, and the first non-AP STA belongs to the Wi-Fi device.

[0007] According to a second aspect of the present invention, an exemplary Wi-Fi device is disclosed. The exemplary Wi-Fi device includes a plurality of affiliated sites, including a first affiliated site. During association between the Wi-Fi device and another Wi-Fi device, the Wi-Fi device sets a first capability allocation for the first affiliated site. Each site affiliated with the other Wi-Fi device is an access point (AP). Each site affiliated with the Wi-Fi device is a non-AP STA. After the first affiliated site is associated with a second affiliated site included in the plurality of affiliated sites of the other Wi-Fi device, the Wi-Fi device changes the first capability allocation of the first affiliated site without re-association.

[0008] Using the above-described technical solution of the present invention, the capability allocation of AP STA can be changed without re-association.

[0009] These and other objects of the invention will undoubtedly become apparent to those skilled in the art after reading the following detailed description of the preferred embodiments shown in the various accompanying drawings. Attached Figure Description

[0010] Figure 1 This is a schematic diagram illustrating a wireless fidelity (Wi-Fi) system according to an embodiment of the present invention.

[0011] Figure 2 This is a schematic diagram illustrating a first DBDC scenario according to an embodiment of the present invention.

[0012] Figure 3 This is a schematic diagram illustrating a second DBDC scenario according to an embodiment of the present invention.

[0013] Figure 4 This is a schematic diagram illustrating a first multi-link operation (MLO) scenario according to an embodiment of the present invention.

[0014] Figure 5 This is a schematic diagram illustrating a variation of a first MLO scenario according to an embodiment of the present invention.

[0015] Figure 6 This is a schematic diagram illustrating a second MLO scenario according to an embodiment of the present invention.

[0016] Figure 7 This is a schematic diagram illustrating a variation of a second MLO scenario according to an embodiment of the present invention.

[0017] Figure 8 This is a schematic diagram illustrating a third MLO scenario according to an embodiment of the present invention.

[0018] Figure 9This is a schematic diagram illustrating a fourth MLO scenario according to an embodiment of the present invention.

[0019] Figure 10 This is a schematic diagram illustrating an MLO scenario with cross-link signaling according to an embodiment of the present invention. Detailed Implementation

[0020] Certain terms are used in the following description and claims to refer to specific components. As those skilled in the art will understand, electronic device manufacturers may use different names to refer to a component. This document is not intended to distinguish between components with different names but the same function. In the following description and claims, the terms "comprising" and "including" are used in an open-ended manner and should therefore be interpreted as meaning "including but not limited to...". Furthermore, the term "coupled" is intended to indicate an indirect or direct electrical connection. Thus, if one device is coupled to another device, the connection can be a direct electrical connection or an indirect electrical connection via other devices and connections.

[0021] Figure 1 This is a schematic diagram illustrating a wireless fidelity (Wi-Fi) system according to an embodiment of the present invention. The Wi-Fi system 100 has multiple Wi-Fi devices 102 and 104. By way of example and not limitation, the Wi-Fi devices 102 and 104 may conform to the IEEE 802.11ax standard or the IEEE 802.11be standard. For the sake of brevity, Figure 1 Only two Wi-Fi devices are shown in the diagram. In practice, Wi-Fi system 100 is allowed to have more than two Wi-Fi devices. As shown in Figure 1, Wi-Fi device 102 includes multiple stations 112_1-112_N, where N is a positive integer not less than 2. Like Wi-Fi device 102, Wi-Fi device 104 includes multiple stations 122_1-122_N. Wi-Fi device 102 can connect to multiple links L1-L1. N Communicates with Wi-Fi device 104. For example, link L1-L. N It can be a channel in different radio frequency (RF) bands, such as the 2.4 GHz band, the 5 GHz band, and the 6 GHz band. Furthermore, the Wi-Fi device 102's site 112_i can be connected via a link L established through the association process. iThe site communicates with station 122_i of Wi-Fi device 104, where i = {1, ..., N}. Depending on the actual role played by Wi-Fi device 102, each of stations 112_1-112_N can be an access point (AP) or a non-AP station (STA). Similarly, each of stations 122_1-122_N can be an AP or a non-AP STA, depending on the actual role played by Wi-Fi device 104.

[0022] In one exemplary embodiment, both Wi-Fi devices 102 and 104 can be dual-band dual concurrent (DBDC) hosts or triple-band triple concurrent (TBTC) hosts. When Wi-Fi device 102 is an AP DBDC / TBTC host and Wi-Fi device 104 is a STA DBDC / TBTC host, sites 112_1-112_N belonging to the same Wi-Fi device 102 are all APs, and sites 122_1-122_N belonging to the same Wi-Fi device 104 are all non-AP STAs. In another scenario where Wi-Fi device 102 is a STA DBDC / TBTC host and Wi-Fi device 104 is an AP DBDC / TBTC host, sites 112_1-112_N belonging to the same Wi-Fi device 102 are all non-AP STAs, and sites 122_1-122_N belonging to the same Wi-Fi device 104 are all APs. Perform a separate association between site 112_1 of Wi-Fi device 102 and site 122_1 of Wi-Fi device 104, perform another separate association between site 112_2 of Wi-Fi device 102 and site 122_2 of Wi-Fi device 104, and so on.

[0023] In another exemplary embodiment, both Wi-Fi devices 102 and 104 can be multi-link devices (MLDs). When Wi-Fi device 102 is an AP MLD and Wi-Fi device 104 is a non-AP MLD, stations 112_1-112_N belonging to the same Wi-Fi device 102 are all APs, and stations 122_1-122_N belonging to the same Wi-Fi device 104 are all non-AP STAs. When Wi-Fi device 102 is a non-AP MLD and Wi-Fi device 104 is an AP MLD, stations 112_1-112_N belonging to the same Wi-Fi device 102 are all non-AP STAs, and stations 122_1-122_N belonging to the same Wi-Fi device 104 are all APs. An MLD-level association (i.e., MLO association) is performed between Wi-Fi devices 102 and 104.

[0024] One of the Wi-Fi devices 102 and 104 (e.g., a non-AP MLD or STA DBDC / TBTC host) can employ the proposed dynamic capability allocation scheme to update the capability allocation of affiliated devices (e.g., non-AP STAs) within the Wi-Fi device. According to the proposed dynamic capability allocation scheme, after a non-AP STA is associated with the AP of another Wi-Fi device (e.g., an AP MLD or APDBDC / TBTC host) through an association process, a change in the capability allocation of the non-AP STA within the Wi-Fi device (e.g., a non-AP MLD or STADBDC / TBTC host) is performed. Furthermore, this change in the capability allocation of the non-AP STA within the Wi-Fi device (e.g., a non-AP MLD or STA DBDC / TBTC host) is achieved without re-association (e.g., re-association between MLDs or re-association between the AP of the AP DBDC / TBTC host and the non-AP STA of the STADBDC / TBTC host). Since reassociation may disrupt current traffic and the reassociation period can be lengthy, the proposed dynamic capability allocation scheme sends frames to carry information about different capability allocations used to update the capability allocations of non-AP STAs in the Wi-Fi device. Further details of the proposed dynamic capability allocation scheme are described below with reference to the accompanying drawings.

[0025] Multiple links can share the hardware resources of the same Wi-Fi device 102 / 104. Taking memory as a shared resource as an example, there is a maximum memory limit to support frame switching. However, due to cost reasons, it is not always possible to allocate a memory size that matches the maximum memory limit for each link. Furthermore, for some use cases, it is not always necessary to enable all frequency bands or all links. For example, some links may be disabled when the load is low. Therefore, dynamically allocating these resources owned by the Wi-Fi device is crucial for adapting to different use cases to maximize efficiency or throughput. To better understand the technical features of this invention, it is assumed that the capability allocation set for non-AP STAs in a Wi-Fi device (e.g., a non-AP MLD or STADBDC / TBTC host) may include memory resource allocation. For example, the memory resource allocation for a non-AP STA may include the maximum Media Access Control Protocol Data Unit (MPDU) length. The maximum MPDU length in the very high throughput (VHT) / high efficiency (HE) capability element defines three possible values. Specifically, for 3895 (4K) octets, the value of the 2-bit maximum MPDU length subfield is set to 0; for 7991 (8K) octets, the value of the 2-bit maximum MPDU length subfield is set to 1; and for 11454 (11K) octets, the value of the 2-bit maximum MPDU length subfield is set to 2.

[0026] Figure 2This is a schematic diagram illustrating a first DBDC scenario according to an embodiment of the present invention. Assume that Wi-Fi device 102 is an AP DBDC host with two sites 112_1 and 112_N (N=2) acting as APs (labeled AP1 and AP2), and Wi-Fi device 104 is a STA DBDC host with a 16K storage area 202 and two sites 122_1 and 122_N (N=2) acting as non-AP STAs (labeled STA1 and STA2), and links L1 and L2 are in different frequency bands (e.g., 2.4GHz and 5GHz). Initially, only the non-AP site STA1 is associated with access point AP1, and the capability allocation (e.g., maximum MPDU length) set for the non-AP site STA1 in Wi-Fi device 104 is 11454 (11K) octets. Based on the signal notification capability from Wi-Fi device 104, access point AP1 can send packets to non-AP station STA1 via link L1, and the packets have an MPDU length constrained by a maximum MPDU length of 11454 (11K) octets (i.e., if AP MLD104 sends packets, the MPDU length of the packets is equal to or less than the maximum MPDU length of 11454 (11K) octets).

[0027] In this example, the association between non-AP site STA2 and access point AP2 is initiated after non-AP site STA1 has already associated with access point AP1. Therefore, in response to the association between non-AP site STA2 and access point AP2, non-AP site STA1 sends frame FR to access point AP1 to notify non-AP site STA1 of the capability allocation update. For example, frame FR can be sent after non-AP site STA2 has successfully associated with access point AP2. Alternatively, frame FR can be sent before non-AP site STA2 initiates its association with access point AP2.

[0028] To balance the load and maximize potential throughput, a Wi-Fi device (e.g., a STADBDC host) 104 with 16K storage area 202 can evenly divide the storage area resources and allocate the same capacity (e.g., maximum MPDU length = 7991 (8K) octets) to both non-AP sites STA1 and STA2. Therefore, during the association between non-AP site STA2 and access point AP2, non-AP site STA2 sets its capacity allocation of 7991 (8K) octets (e.g., maximum MPDU length) and announces its capacity allocation. Frame FR sent from non-AP site STA1 carries information for updating the current capacity allocation of non-AP site STA1 (e.g., maximum MPDU length = 11454 (11K) octets) and the different capacity allocation (e.g., maximum MPDU length = 7991 (8K) octets). It should be noted that non-AP site STA1 does not need to re-associate with access point AP1 to change / update the current capacity allocation of non-AP site STA1.

[0029] like Figure 2 As shown, after non-AP site STA2 is associated with access point AP2, the 16K storage area 202 is shared by non-AP sites STA1 and STA2. Based on the signal notification capability from Wi-Fi device 104, access point AP1 can send packets with an MPDU length constrained by a maximum MPDU length of 7991 (8K) octets to non-AP site STA1 via link L1, and access point AP2 can send packets with an MPDU length constrained by a maximum MPDU length of 7991 (8K) octets to non-AP site STA2 via link L2.

[0030] Figure 3This is a schematic diagram illustrating a second DBDC scenario according to an embodiment of the present invention. Assume that Wi-Fi device 102 is an AP DBDC host with two sites 112_1 and 112_N (N=2) acting as APs (labeled AP1 and AP2), and Wi-Fi device 104 is a STA DBDC host with a 16K storage area 202 and two sites 122_1 and 122_N (N=2) acting as non-AP STAs (labeled STA1 and STA2), and links L1 and L2 are in different frequency bands (e.g., the 2.4GHz band and the 5GHz band). Initially, non-AP site STA1 is associated with access point AP1, and non-AP site STA2 is associated with access point AP2. To balance the load and maximize possible throughput, a Wi-Fi device (e.g., a STA DBDC host) 104 with 16K storage area 202 can allocate storage area resources evenly and assign the same capacity (e.g., maximum MPDU length = 7991 (8K) octets) to both non-AP sites STA1 and STA2 during one association between non-AP site STA1 and access point AP1 and another association between non-AP site STA2 and access point AP2.

[0031] In this embodiment, the deassociation between non-AP site STA2 and access point AP2 is initiated after non-AP site STA1 has associated with access point AP1 and non-AP site STA2 has associated with access point AP2. Therefore, in response to the deassociation between non-AP site STA2 and access point AP2, non-AP site STA1 sends a frame FR′ to access point AP1 to notify non-AP site STA1 of the capability allocation update. For example, the frame FR′ can be sent after non-AP site STA2 has successfully deassociated with access point AP2. Alternatively, the frame FR′ can be sent before non-AP site STA2 initiates the deassociation with access point AP2. The frame FR′ sent from non-AP site STA1 carries information about a different capability allocation (e.g., maximum MPDU length = 7991 (8K) octets) used to update the current capability allocation of non-AP site STA1 (e.g., maximum MPDU length = 7991 (8K) octets). It should be noted that non-AP site STA1 does not need to reassociate with access point AP1 to change / update the current capability allocation of non-AP site STA1. Figure 3 As shown, after the non-AP site STA2 is de-associated with the access point AP2, the 16K storage area 202 is shared only by the non-AP site STA1. Based on the signaling capability from the Wi-Fi device 104, the access point AP1 can send packets with an MPDU length constrained by a maximum MPDU length of 11454 (11K) octets to the non-AP site STA1 via link L1.

[0032] Figure 4 This is a schematic diagram illustrating a first multi-link operation (MLO) scenario according to an embodiment of the present invention. Assume that Wi-Fi device 102 is an AP MLD with three sites 112_1-112_N (N=3) acting as APs (labeled AP1, AP2, and AP3), and Wi-Fi device 104 is a non-AP MLD with a 26K memory area 402 and three sites 122_1-122_N (N=3) acting as non-AP STAs (labeled STA1, STA2, and STA3). Initially, all three links L1, L2, and L3 (e.g., links in the 2.4GHz, 5GHz, and 6GHz bands) are enabled. Furthermore, during the MLO association between Wi-Fi device 102 and Wi-Fi device 104, a capacity allocation (e.g., maximum MPDU length) of 7991 (8K) octets is set for each non-AP site STA1-STA3. The 26K storage area 402 at Wi-Fi device (e.g., non-AP MLD) 104 is shared by non-AP sites STA1-STA3.

[0033] In this example, link L3 is disabled after the MLO association between Wi-Fi device 102 and Wi-Fi device 104 is completed. That is, link L3 is disabled after links L1-L3 have all been enabled. Therefore, in response to the disabling of link L3, non-AP site STA1 sends frame FR1 to access point AP1 to notify non-AP site STA1 of the capability allocation update, and non-AP site STA2 sends frame FR2 to access point AP2 to notify non-AP site STA2 of the capability allocation update. For example, frame FR1 sent from non-AP site STA1 carries information for updating the current capability allocation of non-AP site STA1 (e.g., maximum MPDU length = 7991 (8K) octets) with a different capability allocation (e.g., maximum MPDU length = 11454 (11K) octets), and frame FR2 sent from non-AP site STA2 carries information for updating the current capability allocation of non-AP site STA2 (e.g., maximum MPDU length = 7991 (8K) octets) with a different capability allocation (e.g., maximum MPDU length = 11454 (11K) octets). It is important to note that there is no need for reassociation (especially reassociation between APMLD and non-AP MLD) between non-AP sites STA1 / STA2 and access points AP1 / AP2 to change / update the current capability allocation of non-AP sites STA1 / STA2.

[0034] Reference Figure 4After link L3 is disabled, the 26K storage area 202 is shared by two non-AP sites STA1 and STA2. Based on the signaling capability from Wi-Fi device 104, access point AP1 can send packets with an MPDU length constrained by a maximum MPDU length of 11454 (11K) octets to non-AP site STA1 via link L1, and access point AP2 can send packets with an MPDU length constrained by a maximum MPDU length of 11454 (11K) octets to non-AP site STA2 via link L2.

[0035] After Link L3 is disabled, it can be re-enabled. In this example, when Link L3 is re-enabled, the Wi-Fi device (e.g., non-AP MLD) 104 does not change the storage area allocation for non-AP sites STA1 and STA2. Since the available free storage space in 26K storage area 402 is 3895 (4K) octets, and the existing capability allocation of non-AP site STA3 (i.e., the capability allocation assigned to non-AP site STA3 before Link L3 was disabled) is set by a maximum MPDU length of 7991 (8K) bytes, non-AP site STA3 sends frame FR3 to access point AP3 to notify non-AP site STA3 of the capability allocation update. Frame FR3 carries information about the different capability allocation (e.g., maximum MPDU length of 3895 (4K) octets) used to update the current capability allocation (e.g., maximum MPDU length of 7991 (8K) octets) of non-AP site STA3.

[0036] Figure 5 This is a schematic diagram illustrating a variation of a first MLO scenario according to an embodiment of the present invention. Figure 4 and Figure 5 The main difference between the MLO scenarios shown is that when link L3 is re-enabled, Figure 5The Wi-Fi device (e.g., a non-AP MLD) 104 determines that all non-AP sites STA1-STA3 should share the same capabilities (e.g., the same maximum MPDU length = 7991 (8K) octets). Since the current capability allocation for non-AP site STA1 is set by the maximum MPDU length = 11454 (11K) octets, the current capability allocation for non-AP site STA2 is set by the maximum MPDU length = 11454 (11K) octets, and the existing capability allocation for non-AP site STA3 (i.e., the capability allocation assigned to non-AP site STA3 before link L3 was disabled) is set by the maximum MPDU length = 7991 (8K) octets, non-AP site STA1 sends frame FR1' to access point AP1 to notify of the capability allocation update, and non-AP site STA2 sends frame FR1' to access point AP1 to notify of the update. Point AP2 sends frame FR2′ to notify non-AP site STA2 of capability allocation updates. Frame FR1′ carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) for updating the current capability allocation (e.g., maximum MPDU length = 11454 (11K) octets) of non-AP site STA1, and frame FR2′ carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) for updating the current capability allocation (e.g., maximum MPDU length = 11454 (11K) octets) of non-AP site STA2.

[0037] Figure 6This is a schematic diagram illustrating a second MLO scenario according to an embodiment of the present invention. Assume that Wi-Fi device 102 is an AP MLD with three sites 112_1-112_N (N=3) acting as APs (labeled AP1, AP2, and AP3), and Wi-Fi device 104 is a non-AP MLD with a 26K memory area 402 and three sites 122_1-122_N (N=3) acting as non-AP STAs (labeled STA1, STA2, and STA3). Initially, only two links L1 and L2 are enabled (e.g., two links in the 2.4GHz band, 5GHz band, and 6GHz band). Therefore, the 26K memory area 402 at Wi-Fi device (e.g., non-AP MLD) 104 is shared by the two non-AP sites STA1 and STA2. Furthermore, during the MLO association between Wi-Fi device 102 and Wi-Fi device 104, a capability allocation (e.g., maximum MPDU length) of 11454 (11K) octets is set for each non-AP site STA1 and STA2. It should be noted that even though link L3 is initially disabled, the MLO association between Wi-Fi device 102 and Wi-Fi device 104 can still set a capability allocation (e.g., maximum MPDU length) for non-AP site STA3. In other words, non-AP site STA3 can have a specified capability allocation (e.g., maximum MPDU length) before link L3 is disabled.

[0038] Link L3 can be enabled after the MLO association between Wi-Fi device 102 and Wi-Fi device 104 is completed. That is, link L3 is enabled after links L1 and L2 are enabled. In this embodiment, when link L3 is enabled, Wi-Fi device (e.g., non-AP MLD) 104 determines that all non-AP sites STA1-STA3 share the same capabilities (e.g., the same maximum MPDU length = 7991 (8K) octets), and the existing capability allocation of non-AP site STA3 (capability allocation assigned to non-AP site STA3 before link L3 is disabled or during MLO association) is set by the maximum MPDU length = 7991 (8K) octets. Therefore, in response to the activation of Link L3, non-AP site STA1 sends frame FR1 to access point AP1 to notify non-AP site STA1 of capability allocation update, and non-AP site STA2 sends frame FR2 to access point AP2 to notify non-AP site STA2 of capability allocation update. Frame FR1 sent from non-AP site STA1 carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) for updating the current capability allocation of non-AP site STA1 (e.g., maximum MPDU length = 11454 (11K) octets), and frame FR2 sent from non-AP site STA2 carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) for updating the current capability allocation of non-AP site STA2 (e.g., maximum MPDU length = 11454 (11K) octets). It is important to note that non-AP sites STA1 / STA2 and access points AP1 / AP2 do not need to be re-associated (especially between AP MLD and non-AP MLD) to change / update the current capability allocation of non-AP sites STA1 / STA2.

[0039] like Figure 6 As shown, after link L3 is enabled, the 26K storage area 202 is shared by three non-AP sites STA1-STA3. Based on the signal notification capability from Wi-Fi device 104, access point AP1 can send packets with an MPDU length constrained by a maximum MPDU length of 7991 (8K) octets to non-AP site STA1 via link L1, access point AP2 can send packets with an MPDU length constrained by a maximum MPDU length of 7991 (8K) octets to non-AP site STA2 via link L2, and access point AP3 can send packets with an MPDU length constrained by a maximum MPDU length of 7991 (8K) octets to non-AP site STA3 via link L3.

[0040] Figure 7This is a schematic diagram illustrating a variation of a second MLO scenario according to an embodiment of the present invention. Figure 6 and Figure 7 The key difference between the MLO scenarios shown is that the capability allocation assigned to non-AP site STA3 before link Lx is disabled or during MLO association is set by a different maximum MPDU length (e.g., 3895 (4K) octets) than 7991 (8K) octets. In this example, when link L3 is enabled, the Wi-Fi device (e.g., non-AP MLD) 104 determines that all non-AP sites STA1-STA3 share the same capabilities (e.g., the same maximum MPDU length = 7991 (8K) octets). Therefore, non-AP site STA1 sends frame FR1 to access point AP1 to notify non-AP site STA1 of a capability allocation update; non-AP site STA2 sends frame FR2 to access point AP2 to notify non-AP site STA2 of a capability allocation update; and non-AP site STA3 sends frame FR3 to access point AP3 to notify non-AP site STA3 of a capability allocation update. Frame FR1 carries information about the different capability allocations (e.g., maximum MPDU length = 11454 (11K) octets) used to update the current capability allocation of non-AP site STA1. Frame FR2 carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) for updating the current capability allocation (e.g., maximum MPDU length = 11454 (11K) octets) for non-AP site STA2, and frame FR3 carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) for updating the current capability allocation (e.g., maximum MPDU length = 3895 (4K) octets) for non-AP site STA3.

[0041] Figure 8This is a schematic diagram illustrating a third MLO scenario according to an embodiment of the present invention. In the aforementioned MLO scenario, a change in the capability allocation of a non-AP site (which is using an enabled link for wireless communication) is performed in response to enabling / disabling another link. For the third MLO scenario, a more aggressive update method is used to change the capability allocation of a non-AP site (which is using an enabled link for wireless communication) in response to a state transition of another enabled link in power-saving mode, wherein the state transition can be a transition from an active state to a doze state or from a doze state to an active state. The capability reallocation operation performed in the third MLO scenario in response to an enabled link entering an active state is similar to the capability reallocation operation performed in the first / second MLO scenario in response to a link being enabled, and the capability reallocation operation performed in the third MLO scenario in response to an enabled link entering a doze state is similar to the capability reallocation operation performed in the first / second MLO scenario in response to a link being disabled.

[0042] Assume Wi-Fi device 102 is an AP MLD with three sites 112_1-112_N (N=3) acting as APs (labeled AP1, AP2, and AP3), and Wi-Fi device 104 is a non-AP MLD with a 26K storage area 402 and three sites 122_1-122_N (N=3) acting as non-AP STAs (labeled STA1, STA2, and STA3). Initially, all three links L1, L2, and L3 (e.g., links in the 2.4GHz, 5GHz, and 6GHz bands) are enabled. Furthermore, during MLO association between Wi-Fi device 102 and Wi-Fi device 104, a capacity allocation (e.g., maximum MPDU length) of 7991 (8K) octets is set for each non-AP site STA1-STA3. Therefore, the 26K storage area 402 is shared by the non-AP sites STA1-STA3.

[0043] In this example, non-AP site STA3 operates in power-saving mode. Initially, non-AP site STA3 enters an active state to receive or transmit frames. When non-AP site STA3 leaves the active state and enters a sleep state in power-saving mode, Wi-Fi device (e.g., non-AP MLD) 104 initiates capability reallocation for other non-AP sites STA1 and STA2. Therefore, in response to the enabled link L3 switching from the active state to the sleep state, non-AP site STA1 sends frame FR1 to access point AP1 to notify non-AP site STA1 of the capability allocation update, and non-AP site STA2 sends frame FR2 to access point AP2 to notify non-AP site STA2 of the capability allocation update. For example, frame FR1 sent from non-AP site STA1 carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) used to update the current capability allocation of non-AP site STA1 (e.g., maximum MPDU length = 7991 (8K) octets), and frame FR2 sent from non-AP site STA2 carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) used to update the current capability allocation of non-AP site STA2 (e.g., maximum MPDU length = 11454 (11K) octets). It is important to note that there is no need for reassociation (especially reassociation between AP MLD and non-AP MLD) between non-AP sites STA1 / STA2 and access points AP1 / AP2 to change / update the current capability allocation of non-AP sites STA1 / STA2.

[0044] like Figure 8 As shown, after non-AP site STA3 enters sleep mode, the 26K storage area 402 is shared by the two non-AP sites STA1 and STA2. Based on the signal notification capability from Wi-Fi device 104, access point AP1 can send packets with an MPDU length constrained by a maximum MPDU length of 11454 (11K) octets to non-AP site STA1 via link L1, and access point AP2 can send packets with an MPDU length constrained by a maximum MPDU length of 11454 (11K) octets to non-AP site STA2 via link L2.

[0045] A non-AP site operating in power-saving mode may frequently switch between awake and sleep states. In this example, when non-AP site STA3 leaves the awake state and re-enters the awake state in power-saving mode, the Wi-Fi device (e.g., non-AP MLD) 104 initiates another capability reallocation for other non-AP sites STA1 and STA2. Therefore, in response to the enabled link L3 switching from sleep to awake state, non-AP site STA1 sends frame FR1′ to access point AP1 to notify non-AP site STA1 of the capability allocation update, and non-AP site STA2 sends frame FR2′ to access point AP2 to notify non-AP site STA2 of the capability allocation update. For example, frame FR1′ sent from non-AP site STA1 carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) used to update the current capability allocation of non-AP site STA1 (e.g., maximum MPDU length = 11454 (11K) octets), and frame FR2′ sent from non-AP site STA2 carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) used to update the current capability allocation of non-AP site STA2 (e.g., maximum MPDU length = 11454 (11K) octets). It should be noted that there is no need for reassociation (especially reassociation between AP MLD and non-AP MLD) between non-AP sites STA1 / STA2 and access points AP1 / AP2 to change / update the current capability allocation of non-AP sites STA1 / STA2.

[0046] Figure 9This is a schematic diagram illustrating a fourth MLO scenario according to an embodiment of the present invention. Assume that Wi-Fi device 102 is an AP MLD with three sites 112_1-112_N (N=3) acting as APs (labeled AP1, AP2, and AP3), and Wi-Fi device 104 is a non-AP MLD with a 26K storage area 402 and three sites 122_1-122_N (N=3) acting as non-AP STAs (labeled STA1, STA2, and STA3). During the MLO association between Wi-Fi device 102 and Wi-Fi device 104, Wi-Fi device (e.g., non-AP MLD) 104 sends an association request REQ to establish three links and corresponding capability allocations (e.g., the maximum MPDU length of non-AP sites STA1-STA3 = (8K, 8K, 8K)). However, the Wi-Fi device (e.g., AP MLD) 102 only allows a subset of the requested links and notifies the Wi-Fi device (e.g., non-AP MLD) 104 of two allowed links (e.g., L1 and L2) and one rejected link (e.g., L3) via a response frame RSP. In other words, requests to establish links L1 and L2 are allowed by the Wi-Fi device (e.g., AP MLD) 102, while requests to establish link L3 are rejected by the Wi-Fi device (e.g., AP MLD) 102.

[0047] After the MLO association between Wi-Fi device 102 and Wi-Fi device 104 is completed, only two links L1 and L2 (e.g., two links from the 2.4GHz band, 5GHz band, and 6GHz band) are enabled. For each non-AP site STA1 and STA2, the capacity allocation (e.g., maximum MPDU length) is set to 7991 (8K) octets. Furthermore, a 26K memory area 402 at Wi-Fi device (e.g., non-AP MLD) 104 is shared by non-AP sites STA1 and STA2.

[0048] Wi-Fi device (e.g., non-AP MLD) 104 can reallocate resources initially defined for the three non-AP sites to improve the efficiency or throughput of the two links actually allowed by Wi-Fi device (e.g., AP MLD) 102. Therefore, in response to a request to establish link L3 being rejected by Wi-Fi device (e.g., AP MLD) 102, non-AP site STA1 sends frame FR1 to access point AP1 to notify of the capability allocation update, and non-AP site STA2 sends frame FR2 to access point AP2 to notify of the capability allocation update. For example, frame FR1 sent from non-AP site STA1 carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) used to update the current capability allocation of non-AP site STA1 (e.g., maximum MPDU length = 7991 (8K) octets), and frame FR2 sent from non-AP site STA2 carries information about different capability allocations (e.g., maximum MPDU length = 7991 (8K) octets) used to update the current capability allocation of non-AP site STA2 (e.g., maximum MPDU length = 11454 (11K) octets). It is important to note that there is no need for reassociation (especially reassociation between AP MLD and non-AP MLD) between non-AP sites STA1 / STA2 and access points AP1 / AP2 to change / update the current capability allocation of non-AP sites STA1 / STA2.

[0049] In the example above, changing the capability allocation of a specific non-AP site requires sending frames carrying information indicating capability allocation updates for that specific link. If the Wi-Fi device can receive cross-link signaling, thus enabling it to receive signaling from one link and apply it to another, the number of frames sent for dynamic capability allocation can be reduced. For example, the MLO scenario described above can be modified to support cross-link signaling features, allowing a single frame sent by a non-AP site on one link to indicate capability updates on other non-AP sites.

[0050] Figure 10This is a schematic diagram illustrating an MLO scenario with cross-link signaling according to an embodiment of the present invention. Assume Wi-Fi device 102 is an AP MLD, Wi-Fi device 104 is a non-AP MLD, where sites 112_1-112_N include APs (labeled AP1 and AP2), and sites 122_1-122_N include non-AP STAs (labeled STA1 and STA2). Initially, non-AP site STA1 communicates with access point AP1 via enabled link L1, where non-AP site STA1 is assigned a capability allocation (e.g., maximum MPDU length = A1 octets) set during the MLO association between Wi-Fi device 102 and Wi-Fi device 104. Non-AP site STA2 communicates with access point AP2 via enabled link L2, where non-AP site STA2 is assigned a capability allocation (e.g., maximum MPDU length = A2 octets, where A1 may be equal to or different from A2) set during the same MLO association between Wi-Fi device 102 and Wi-Fi device 104. Therefore, the storage area 1002 at the Wi-Fi device (e.g., non-AP MLD) 104 is shared by two non-AP sites STA1 and STA2.

[0051] For various reasons, Wi-Fi device (e.g., non-AP MLD) 104 may need to reallocate resources for non-AP sites STA1 and STA2. In this example, non-AP site STA1 sends a frame FR to access point AP1. The frame FR, sent by non-AP site STA1 via link L1, carries information about a different capability allocation (e.g., maximum MPDU length = A1 octets) used to update the current capability allocation of non-AP site STA1 (e.g., maximum MPDU length = A2 octets). The same information carried in the frame FR sent by non-AP site STA1 via link L1 is further used to indicate a capability allocation update (e.g., maximum MPDU length = B octets) for the current capability allocation of non-AP site STA2, which is using another link L2 for wireless communication (e.g., maximum MPDU length = A2 octets). It is important to note that there is no need for reassociation (particularly reassociation between AP MLD and non-AP MLD) between non-AP sites STA1 / STA2 and access points AP1 / AP2 to change / update the current capability allocation of non-AP sites STA1 / STA2.

[0052] In the above example, signaling a memory resource allocation from one Wi-Fi device 102 / 104 to another Wi-Fi device 104 / 102 may include the maximum MPDU length. However, this is for illustrative purposes only and does not imply limitation of the invention.

[0053] In some embodiments of the present invention, signaling from one Wi-Fi device 102 / 104 to another Wi-Fi device 104 / 102 regarding storage resource allocation may include a maximum aggregate MPDU (A-MPDU) length. The maximum A-MPDU length in the High Throughput (HT) capability element defines two possible values. Specifically, a 1-bit maximum A-MPDU length subfield is set to 0 for 3839 octets, and a 1-bit maximum A-MPDU length subfield is set to 1 for 7935 octets.

[0054] In some embodiments of the present invention, signaling from one Wi-Fi device 102 / 104 to another Wi-Fi device 104 / 102 regarding storage resource allocation may include a maximum A-MPDU length exponent. The maximum A-MPDU length exponent in the VHT / HE 6G capability element defines a maximum A-MPDU length of 2. (13+最大A-MPDU长度指数) -1 octet.

[0055] Capability allocation for non-AP sites can be dynamically changed without re-associating Wi-Fi device 102 and Wi-Fi device 104. In addition to storage resource allocation, capability allocation can be set by other capabilities or operating modes. For example, one capability allocation for a non-AP site may include the number of spatial streams (NSS) in receive (RX) mode. Another example is that the capability allocation for a non-AP site may include the number of spatial streams (NSS) in transmit (TX) mode.

[0056] As described above, changing the capability allocation for a specific site in a Wi-Fi device requires sending a frame carrying information necessary to notify peer Wi-Fi devices of the capability allocation update for that specific site. In some embodiments of the invention, the information can be recorded in the Aggregate Control (A-Control) field defined in 802.11ax, where a new operating mode (OM) control definition can be added for the MLO. In some embodiments of the invention, this frame can be a management frame that carries information using a new capability element. For example, the management frame can be a control frame.

[0057] Changing the capability allocation of a non-AP site can be achieved through a one-way notification from one Wi-Fi device 102 / 104 to another Wi-Fi device 104 / 102, or through bidirectional negotiation between the two devices. Regarding the one-way notification used to update capability allocation, there are no other frames or corresponding information (carrying information about the different capability allocation) besides the acknowledgment (ACK) frame. Capability updates will occur immediately on the peer device after the peer device sends an ACK frame and the requester (e.g., an AP or non-AP STA) receiving the ACK frame (which carries information about the different capability allocation). For example, a change in capability allocation can be achieved through a one-way notification when the A-Control field records information for updating capability allocation.

[0058] Regarding the bidirectional negotiation used to update capability allocation, the frame (carrying information about different capability allocations) is a request frame sent by the requester (e.g., a non-AP STA), and the peer device (e.g., an AP) receives the request frame containing the capability update. The peer device (e.g., the AP) needs some time to synchronize the capability update with other APs belonging to the same AP MLD. The peer device (e.g., the AP) sends a response frame corresponding to the request frame to announce the completion of information synchronization. Therefore, the requester (e.g., a non-AP STA) can update its capabilities after receiving the response frame from the peer device (e.g., the AP). For example, when the frame is a management frame, depending on the actual design considerations, changing the capability allocation of a non-AP site can be achieved through one-way notification or bidirectional negotiation. One use case for one-way notification to change capability allocation is when the management frame is a broadcast frame.

[0059] Those skilled in the art will readily observe that many modifications and changes can be made to the apparatus and method while retaining the teachings of the present invention. Therefore, the above disclosure should be construed as being limited only by the scope of the appended claims.

[0060] Although the invention has been described using practical and preferred embodiments, it should be understood that the invention is not necessarily limited to the disclosed embodiments. Rather, it is intended to cover various modifications and similar arrangements included within the spirit and scope of the appended claims, which are to be given the broadest interpretation to cover all such modifications and similar structures.

Claims

1. A capability allocation method for a Wi-Fi device, characterized in that, include: During the association between the Wi-Fi device and another Wi-Fi device, a first capability allocation is set for a first non-AP site STA, wherein each of the Wi-Fi device and the other Wi-Fi device includes multiple sites, each site belonging to the other Wi-Fi device is an AP, each site belonging to the Wi-Fi device is a non-AP STA, the first AP belongs to the other Wi-Fi device, and the first non-AP STA belongs to the Wi-Fi device; and After the first non-AP STA is associated with the first AP, the first capability allocation of the first non-AP STA is changed without reassignment. The Wi-Fi device is a multi-link device (MLD), and the association between the Wi-Fi device and the other Wi-Fi device is a multi-link operation (MLO) association.

2. The capacity allocation method as described in claim 1, characterized in that, Also includes: During the association between the Wi-Fi device and the other Wi-Fi device, a second capability assignment is set for a second non-AP STA, wherein the second AP belongs to the other Wi-Fi device, and the second non-AP STA belongs to the Wi-Fi device; Specifically, before changing the first capability allocation of the first non-AP STA, the first link between the first non-AP STA and the first AP, and the second link between the second non-AP STA and the second AP, are enabled links; changing the first capability allocation of the first non-AP STA includes: In response to the second link being disabled, a frame carrying information for updating a third capability allocation to the first capability allocation of the first non-AP STA is sent, wherein the third capability allocation is different from the first capability allocation.

3. The capacity allocation method as described in claim 2, characterized in that, Also includes: In response to the second link being disabled and then re-enabled, the third capability allocation of the first non-AP STA is maintained.

4. The capacity allocation method as described in claim 2, characterized in that, Also includes: In response to the second link being disabled and then re-enabled, a frame carrying information about the different capability allocation for updating the third capability allocation of the first non-AP STA is sent.

5. The capacity allocation method as described in claim 1, characterized in that, Also includes: During the association between the Wi-Fi device and the other Wi-Fi device, a second capability assignment is set for a second non-AP STA, wherein the second AP belongs to the other Wi-Fi device, and the second non-AP STA belongs to the Wi-Fi device; Specifically, before changing the first capability allocation of the first non-AP STA, the first link between the first non-AP STA and the first AP is an enabled link, and the second link between the second non-AP STA and the second AP is a disabled link; changing the first capability allocation of the first non-AP STA includes: In response to the second link being enabled, a frame carrying information for updating a third capability allocation of the first capability allocation of the first non-AP STA is sent, wherein the third capability allocation is different from the first capability allocation.

6. The capacity allocation method as described in claim 5, characterized in that, Also includes: In response to the second link being enabled, another frame is sent, the other frame carrying information for updating the second capability allocation of the second non-APSTA; The fourth capability allocation is different from the second capability allocation.

7. The capacity allocation method as described in claim 1, characterized in that, Also includes: During the association between the Wi-Fi device and the other Wi-Fi device, a second capability assignment is set for the second non-AP STA, wherein the second AP belongs to the other Wi-Fi device, and the second non-AP STA belongs to the Wi-Fi device; Wherein, the first link between the first non-AP STA and the first AP, and the second link between the second non-AP STA and the second AP, are enabled links; the second non-AP STA operates in power-saving mode; changing the first capability allocation of the first non-AP STA includes: In response to the second non-AP STA switching from one of the waking state and the sleeping state to the other of the waking state and the sleeping state, a frame carrying information on different capability assignments for updating the first capability assignment of the first non-AP STA is sent.

8. The capacity allocation method as described in claim 1, characterized in that, Also includes: During the association between the Wi-Fi device and the other Wi-Fi device, a second capability assignment is set for the second non-AP STA, wherein the second AP belongs to the other Wi-Fi device, and the second non-AP STA belongs to the Wi-Fi device; During the association between the Wi-Fi device and the other Wi-Fi device, a request to establish a first link between the first non-AP STA and the first AP is allowed by the other Wi-Fi device, and a request to establish a second link between the second non-AP STA and the second AP is rejected by the other Wi-Fi device; changing the first capability allocation of the first non-AP STA includes: In response to the other Wi-Fi device refusing to establish the second link, a frame carrying information on different capability assignments for updating the first capability assignment of the first non-AP STA is sent.

9. The capacity allocation method as described in claim 1, characterized in that, The second non-AP STA belongs to the Wi-Fi device, and changing the first capability allocation of the first non-AP STA includes: A frame carrying information for updating a different capability allocation for a first capability allocation of the first non-AP STA is sent, wherein the information carried in the frame also indicates a capability allocation update for a second capability allocation of the second non-AP STA.

10. The capacity allocation method as described in claim 1, characterized in that, The first capacity allocation includes storage area resource allocation.

11. The capacity allocation method according to claim 10, characterized in that, The storage area resource allocation includes: maximum Media Access Control Protocol Data Unit (MPDU) length, maximum aggregated MPDU length, or maximum aggregated MPDU length index.

12. The capacity allocation method according to claim 1, characterized in that, The first capability allocation includes the number of spatial streams (NSS) received in RX mode.

13. The capacity allocation method according to claim 1, characterized in that, The first capability allocation includes the number of spatial streams (NSS) in the transmit TX mode.

14. The capacity allocation method according to claim 1, characterized in that, The change in the first capability allocation of the first non-AP STA is achieved through a one-way notification from the Wi-Fi device to the other Wi-Fi device.

15. The capacity allocation method as described in claim 1, characterized in that, The change in the first capability allocation of the first non-AP STA is achieved through bidirectional negotiation between the Wi-Fi device and the other Wi-Fi device.

16. The capacity allocation method according to claim 1, characterized in that, Changing the first capability allocation of the first non-AP STA includes sending a frame carrying information for updating the different capability allocation of the first capability allocation of the first non-AP STA, the information being recorded in the aggregation control A-Control field, or the frame being a management frame.

17. A capability allocation method used in a Wi-Fi device, characterized in that, include: During the association between the Wi-Fi device and another Wi-Fi device, a first capability allocation is set for a first non-AP site STA, wherein each of the Wi-Fi device and the other Wi-Fi device includes multiple sites, each site belonging to the other Wi-Fi device is an AP, each site belonging to the Wi-Fi device is a non-AP STA, the first AP belongs to the other Wi-Fi device, and the first non-AP STA belongs to the Wi-Fi device; and After the first non-AP STA is associated with the first AP, the first capability allocation of the first non-AP STA is changed without reassignment. The association between the Wi-Fi device and the other Wi-Fi device includes a separate association between the first non-AP STA and the first AP; Wherein, the second AP belongs to the other Wi-Fi device, and the second non-AP STA belongs to the Wi-Fi device. After the first non-AP STA is associated with the first AP, the deassociation between the second non-AP STA and the second AP is initiated. The change of the first capability allocation of the first non-AP STA includes: In response to the deassociation between the second non-AP STA and the second AP, a frame carrying information on different capability assignments for updating the first capability assignment of the first non-AP STA is sent.

18. The capacity allocation method as described in claim 17, characterized in that, The Wi-Fi device is a dual-band dual-concurrent DBDC host or a tri-band tri-concurrent TBTC host.

19. The capacity allocation method as described in claim 17, characterized in that, Also includes: After the first non-AP STA is associated with the first AP, the association between the second non-AP STA and the second AP is initiated; In response to the association between the second non-AP STA and the second AP, a frame carrying information on different capability assignments for updating the first capability assignment of the first non-AP STA is sent.

20. A wireless fidelity Wi-Fi device, characterized in that, include: Multiple subordinate sites, including the primary subordinate site; During the association between the Wi-Fi device and another Wi-Fi device, the Wi-Fi device sets a first capability allocation for the first affiliated site, where each site belonging to the other Wi-Fi device is an Access Point (AP), and each site belonging to the Wi-Fi device is a non-AP STA; and After the first subordinate site is associated with a second subordinate site included in a plurality of subordinate sites of the other Wi-Fi device, the Wi-Fi device changes the first capability allocation of the first subordinate site without reassignment. The Wi-Fi device is a multi-link device (MLD), and the association between the Wi-Fi device and the other Wi-Fi device is a multi-link operation (MLO) association.

Images