Signaling of link preference order and maximum allowed links for multi-link operation

Abstract

Signaling of link preference order and maximum allowed links for multi-link operation can be provided. First, an access point (AP) multi-link device (MLD) can receive an indication that a non-AP MLD supports preference ordering. Then, the AP MLD can indicate that it supports preference ordering. Next, the AP MLD can receive a desired preference order from the non-AP MLD. The AP MLD can then consider the desired preference order.

Description

[0001] Related application technical fields The applicant claims a right to U.S. Provisional Application No. 63 / 596,086, filed November 3, 2023, which is incorporated herein by reference. Technical Field

[0002] This disclosure generally relates to providing signaling for link preference ordering and maximum allowed links for multi-link operation. Background Technology

[0003] In computer networks, a wireless access point (AP) is a network hardware device that allows Wi-Fi-compatible client devices to connect to a wired network as well as other client devices. APs are typically connected to a router as standalone devices (directly or indirectly via a wired network), but they can also be integrated into the router itself. Several APs can also collaborate via direct wired or wireless connections, or through a central system commonly referred to as a Wireless Local Area Network (WLAN) controller. APs are distinct from hotspots, which are physical locations where Wi-Fi access to a WLAN is available.

[0004] Before the advent of wireless networks, establishing a computer network in a business, home, or school typically required laying numerous cables through walls and ceilings to provide network access to all network-enabled devices in the building. With the advent of wireless access points (APs), network users can add devices that can access the network with little or no cable. An AP connects to a wired network and then provides a radio frequency link to that wired network for other wireless devices. Most APs support connections from multiple wireless devices. APs are built to support standards used to transmit and receive data using these radio frequencies. Attached Figure Description

[0005] The accompanying drawings, which are incorporated in and constitute a part of this disclosure, illustrate various embodiments of the present disclosure. In the drawings: Figure 1 It is a block diagram of the operating environment used to provide signaling for link preference ordering and maximum allowed links for multi-link operations; Figure 2 It is a flowchart of a method for providing signaling for link preference ordering and maximum allowed links for multi-link operations; Figure 3 The basic ML elements are shown; Figure 4 The basic ML elements are shown; Figure 5 The basic ML elements are shown; and Figure 6It is a block diagram of a computing device. Detailed Implementation

[0006] Overview Signaling for link preference ordering and maximum allowed links can be provided for multi-link operation. First, the Access Point (AP) Multilink Device (MLD) can receive an indication that the non-AP MLD supports preference ordering for the requested links (indicated in the per-STA profile sub-element). Then, the AP MLD can indicate that it supports preference ordering for the requested links (indicated in the per-STA profile sub-element). Next, the AP MLD can receive the desired preference ordering for the requested links from the non-AP MLD. The AP MLD can then consider this desired preference ordering.

[0007] The foregoing overview and the following example embodiments are merely exemplary and illustrative, and should not be construed as limiting the scope of this disclosure as described and claimed. Furthermore, other features and / or variations may be provided in addition to the described features and / or variations. For example, embodiments of this disclosure may be adapted to various combinations and sub-combinations of features described in the example embodiments.

[0008] Example Implementation The following detailed description refers to the accompanying drawings. Where possible, the same reference numerals are used in the drawings and the following description to refer to the same or similar elements. While embodiments of this disclosure may be described, modifications, adaptations, and other implementations are possible. For example, elements shown in the drawings may be substituted, added, or modified, and the methods described herein may be modified by replacing, reordering, or adding stages to the disclosed methods. Therefore, the following detailed description does not limit this disclosure. Rather, the appropriate scope of this disclosure is defined by the appended claims.

[0009] In IEEE 802.11be standard multilink (ML) operation, a non-AP multilink device (MLD) can provide a set of one or more links it wishes to associate with an AP MLD in a (re)association request. The AP MLD can accept a subset of these links based on criteria such as inter-link load balancing, channel load conditions, and priority of links for certain service / device types. The AP MLD can then provide the accepted set of links to the non-AP MLD in a (re)association response frame.

[0010] From the perspective of a non-AP MLD, the desired outcome is the ability to indicate its preferred order of links among a set of multiple links requested for a (re)association or link addition operation. This allows the AP MLD to consider the preferred order of links provided by the AP MLD when selecting accepted links (and other criteria) for (re)association or link addition. This is desirable so that the most preferred links can be considered and prioritized in the selection. Current IEEE 802.11be standards may not provide a process for non-AP MLDs to indicate their link preferences for (re)association or link addition operations.

[0011] Additionally, to better manage its resources, an AP MLD operating on multiple links may want to limit the maximum number of links that a non-AP MLD is allowed to establish. To support this scenario, the AP MLD can advertise the maximum allowed link establishment limit.

[0012] Therefore, embodiments of this disclosure can provide signaling to indicate the preferred order of links in a set of links requested for multi-link (re)association or in a set of links requested for a link addition operation, which enables a non-AP MLD to perform ML establishment on the most preferred link. Embodiments can also provide signaling to indicate the maximum number of links allowed to be established by a non-AP MLD.

[0013] Figure 1 An operating environment 100 is shown for providing signaling for link preference ordering and maximum allowed links for multi-link operations. For example... Figure 1As shown, the operating environment 100 may include a controller 105 and a coverage environment 110. The coverage environment 110 may include, but is not limited to, a wireless local area network (WLAN) comprising multiple access points (APs) that can provide wireless network access (e.g., providing access to the WLAN to client devices). The multiple APs (e.g., AP sites (STAs)) may include a first AP 115, a second AP 120, and a third AP 125. When multiple client devices move within the coverage environment 110, the multiple APs can provide wireless network access to those client devices. The multiple client devices (e.g., non-AP sites) may include, but are not limited to, a first client device 130, a second client device 135, and a third client device 140. Each of the multiple client devices may include, but is not limited to, smartphones, personal computers, tablets, mobile devices, telephones, remote control devices, set-top boxes, digital video recorders, Internet of Things (IoT) devices, network computers, routers, virtual reality (VR) / augmented reality (AR) devices, or other similar microcomputer-based devices. Each of the multiple APs can be compatible with standard specifications, such as, but not limited to, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard.

[0014] Multiple access points (APs) and multiple client devices can use multi-link operation (MLO), where they simultaneously transmit and receive on different frequency bands and channels by establishing two or more links to two or more AP radio devices. These frequency bands may include, but are not limited to, the 2 GHz band, the 5 GHz band, the 6 GHz band, and the 60 GHz band. Any two or more links on any given client device can be established with any one of the APs or with any combination of APs.

[0015] Controller 105 may include a Wireless Local Area Network (WLC) controller and may configure and control coverage environment 110 (e.g., WLAN). Controller 105 may allow a first client device 130, a second client device 135, and a third client device 140 to join coverage environment 110. In some embodiments of this disclosure, controller 105 may be implemented by a Digital Network Architecture Center (DNAC) controller (i.e., a Software-Defined Networking (SDN) controller) that can configure information for coverage environment 110 to provide link preference ordering and signaling for the maximum allowed links for multi-link operation.

[0016] The aforementioned components of the operating environment 100 (e.g., controller 105, first AP 115, second AP 120, third AP 125, first client device 130, second client device 135, or third client device 140) can be implemented in hardware and / or software (including firmware, resident software, microcode, etc.) or in any other circuit or system. The components of the operating environment 100 can be implemented in circuits including discrete electronic components, in packages or integrated electronic chips containing logic gates, in circuits utilizing microprocessors, or on a single chip containing electronic components or a microprocessor. Furthermore, the components of the operating environment 100 can also be implemented using other technologies capable of performing logical operations (e.g., AND, OR, and NOT), including but not limited to mechanical, optical, fluid, and quantum technologies. As described below regarding… Figure 6 In more detail, the components of the operating environment 100 can be implemented in the computing device 600.

[0017] Figure 2 This is a flowchart illustrating the general stages involved in a method 200 for providing signaling for multi-link operation with a link preference order and a maximum allowed link, consistent with embodiments of this disclosure. Method 200 may use the following regarding... Figure 6 The computing device 600 is implemented in a more detailed manner. The computing device 600 may be embodied by the first AP 115. The manner in which each stage of the implementation method 200 is carried out will be described in more detail below.

[0018] One way a non-AP MLD can indicate its preference ordering for a requested link is by explicitly sorting the per-STA profile sub-elements of the requested link in descending preference order within the base ML elements of the (re)association request frame. Method 200 can begin at start box 205 and proceed to stage 210, in which the first AP 115 can receive an indication that a non-AP MLD (e.g., the first client device 130) supports preference ordering. For example, the non-AP MLD can declare its ability to support preference ordering for each STA profile in the (re)association request frame.

[0019] From stage 210 (where the first AP 115 receives an indication that a non-AP MLD (e.g., the first client device 130) supports preferred ordering), method 200 can proceed to stage 220, in which the first AP 115 can indicate that it supports preferred ordering. For example, the AP MLD could also declare that it supports per-STA profile ordering when selecting an accepted link establishment. This can be achieved by, for example, in... Figure 3The capability bit 310 in the extended MLD capability and operation subfield of the basic ML element 300 shown is used to implement both phases 210 and 220 simultaneously. The capability field can be defined as shown in Table 1 below. When both the non-AP MLD and AP MLD declare their ability to support preference sorting for per-STA profiles of the requested link in the (re)association request, the following rules can be followed as shown in phases 230 and 240.

[0020] Table 1 When the first AP 115 indicates its supported preference ordering in stage 220, method 200 can proceed to stage 230, in which the first AP 115 can receive the desired preference ordering from a non-AP MLD (e.g., the first client device 130). For example, a non-AP MLD that sets the ordered perSTA profile support subfield to 1 in its basic ML elements and includes multiple perSTA profile sub-elements in its (re)association request frame, when associated with an AP MLD that also sets the ordered perSTA profile support subfield to 1 in its transmitted basic ML elements, sorts the perSTA profiles according to the desired preference ordering of the requested link. For example, if a non-AP MLD request is associated on Link 1 (2.4 GHz), Link 2 (5 GHz), and Link 3 (6 GHz), and the preferred link order is (1, 3, and 2), then when an association request is sent on Link 1 (2.4 GHz), it can indicate the per-STA profile in the basic ML element in the following order: i) the per-STA profile of Link 3 (6 GHz) (first); and ii) the per-STA profile of Link 2 (5 GHz) (second).

[0021] After the first AP 115 receives the desired preference order from a non-AP MLD (e.g., the first client device 130) in phase 230, method 200 can proceed to phase 240, where the first AP 115 can consider the desired preference order. For example, when selecting an accept link for a non-AP MLD with the ordered perSTA profile support subfield set to 1, the link preference order indicated by the ordering of the perSTA profiles in the (re)association request frame is considered. When the first AP 115 has considered the desired preference order in phase 240, method 200 can then end in phase 250.

[0022] Add link operation In other embodiments, the per-STA profile sorting used to indicate the preferred order of requested links can also be applied to multiple add-link operations requested in a link reconfiguration request frame. Non-AP MLDs can explicitly sort the per-STA profile sub-elements included in the reconfiguration ML elements for multiple add-link operations in descending order of preference for adding links.

[0023] like Figure 3 The same capability field "Ordered perSTA profile support" shown in the above ML setup can also be used in the link reconfiguration request frame to indicate support for perSTA profile preference ordering for adding a link. For perSTA profile preference ordering in link reconfiguration add link operations, the following rules can be followed: i) In the basic ML element, the ordered per-STA profile support subfield is set to 1 and multiple non-AP MLDs that include link addition requests are included in the link reconfiguration request frame. When a request is sent to an AP MLD that also has the ordered per-STA profile support subfield set to 1 in the basic ML element, the per-STA profiles for adding links can be sorted according to the desired preference order of the requested links.

[0024] ii) When selecting an AP MLD that sets the Ordered PerSTA Profile Support subfield to 1 and includes multiple add link requests in the Link Reconfiguration Request Frame, the preferred order of add links indicated by the order of the perSTA profiles in the Link Reconfiguration Request Frame shall be taken into account when selecting an accept add link for a non-APMLD that sets the Ordered PerSTA Profile Support subfield to 1 and includes multiple add link requests in the Link Reconfiguration Request Frame.

[0025] Replace perSTA configuration file sorting In another embodiment, instead of sorting each STA profile sub-elements in descending preference order, they can be sorted in ascending preference order. In yet another embodiment, instead of indicating preference by "sorting" each STA profile sub-elements, the non-AP MLD can include a new link preference field (e.g., 2-bit, 4-bit, or 8-bit) in each STA profile to indicate its relative link preference. The link preference field can be included in the STA control field or STA information field of each STA profile sub-element. This embodiment can be helpful when the link used to transmit the sub-element is not the most preferred link.

[0026] In another embodiment, instead of the per-STA profile for establishing and adding links for ML including a link preference field, the non-AP MLD may include a “non-preference” or “undesired” field for the link.

[0027] In another embodiment, a non-AP MLD can sort its per-STA profiles for its links in a basic ML element (for ML establishment) or a reconfigured ML element (for adding links) without explicitly declaring a capability field for sorting per-STA profiles. An AP MLD can assume that the non-AP MLD is sorting its per-STA profiles and take into account the order in which they are received when selecting to accept links for ML establishment or link addition operations.

[0028] Maximum allowed associated links To better manage its resources, an AP MLD operating on multiple links may want to limit the maximum number of links that a non-AP MLD is allowed to establish. To support this scenario, the AP MLD can, for example... Figure 4 The maximum allowed link establishment field 405 in the basic ML element 400 shown indicates this restriction to non-AP MLDs.

[0029] The maximum allowed link field can be defined as shown in Table 2 below: Table 2 When the Maximum Allowed Link Establishment subfield is set to a non-zero value, the AP MLD may refuse to accept associations on links that are greater in number than the value indicated in the Maximum Allowed Link Establishment subfield.

[0030] When the Maximum Allowable Link Establishment subfield is set to a non-zero value, the AP MLD may reject link addition requests that could cause the number of established links to exceed the value indicated in the Maximum Allowable Link Establishment subfield. In another embodiment, non-AP MLDs and AP MLDs may support, for example... Figure 5 The basic ML element 500 shown includes both the per-STA profile sorting capability and the maximum allowed link establishment subfield.

[0031] Figure 6 A computing device 600 is shown. (For example...) Figure 6 As shown, computing device 600 may include a processing unit 610 and a memory unit 615. Memory unit 615 may include software module 620 and database 625. When executed on processing unit 610, software module 620 may perform, for example, the above-described... Figure 2The described procedure outlines the signaling process for link preference ordering and maximum allowed links for multi-link operation. Computing device 600 may provide an operating environment for, for example, controller 105, first AP 115, second AP 120, third AP 125, first client device 130, second client device 135, or third client device 140. Controller 105, first AP 115, second AP 120, third AP 125, first client device 130, second client device 135, or third client device 140 may operate in other environments and are not limited to computing device 600.

[0032] Computing device 600 can be implemented using Wi-Fi access points, tablet devices, mobile devices, smartphones, telephones, remote control devices, set-top boxes, digital video recorders, cable modems, personal computers, network computers, mainframes, routers, switches, server clusters, smart TV devices, network storage devices, network relay devices, or other similar microcomputer-based devices. Computing device 600 can include any computer operating environment, such as handheld devices, multiprocessor systems, microprocessor-based or programmable transmitter electronics, minicomputers, mainframes, etc. Computing device 600 can also be implemented in a distributed computing environment, where tasks are performed by remote processing devices. The systems and devices described above are examples, and computing device 600 can include other systems or devices.

[0033] Embodiments of this disclosure may be implemented, for example, as a computer process (method), computing system, or article of manufacture, such as a computer program product or a computer-readable medium. A computer program product may be a computer storage medium readable by a computer system and encoded with instructions for performing the computer process. A computer program product may also be a propagated signal on a carrier wave readable by a computing system and encoded with instructions for performing the computer process. Therefore, this disclosure may be embodied in hardware and / or software (including firmware, resident software, microcode, etc.). In other words, embodiments of this disclosure may take the form of a computer program product on a computer-usable or computer-readable storage medium embodying computer-usable or computer-readable program code for use by or in connection with an instruction execution system. A computer-usable or computer-readable medium may be any medium capable of containing, storing, communicating, propagating, or transmitting a program for use by or in connection with an instruction execution system, apparatus, or device.

[0034] Computer-usable or computer-readable media can be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, apparatuses, or propagation media. More specific examples of computer-readable media (not an exhaustive list) include: electrical connections having one or more wires, portable computer disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, and portable compact disc read-only memory (CD-ROM). Note that computer-usable or computer-readable media can even be paper or other suitable media on which programs are printed, because programs can be electronically captured, for example, by optical scanning of paper or other media, and then compiled, interpreted, or otherwise processed as appropriate, and then stored in computer memory.

[0035] While some embodiments of this disclosure have been described, other embodiments may exist. Furthermore, although embodiments of this disclosure have been described in association with data stored in memory and other storage media, data may also be stored in or retrieved from other types of computer-readable media, such as secondary storage devices like hard disks, floppy disks, or CD-ROMs, carrier waves from the Internet, or other forms of RAM or ROM. Moreover, the stages of the disclosed methods may be modified in any way, including by reordering stages and / or inserting or deleting stages, without departing from this disclosure.

[0036] Furthermore, embodiments of this disclosure can be implemented in circuits including discrete electronic components, in packages or integrated electronic chips containing logic gates, in circuits utilizing microprocessors, or on a single chip containing electronic components or a microprocessor. Embodiments of this disclosure can also be implemented using other technologies capable of performing logical operations (e.g., AND, OR, and NOT), including but not limited to mechanical, optical, fluid, and quantum technologies. Additionally, embodiments of this disclosure can be implemented in a general-purpose computer or in any other circuit or system.

[0037] Embodiments of this disclosure can be implemented using a system-on-a-chip (SOC), wherein Figure 1 Each or many of the components shown can be integrated onto a single integrated circuit. Such a SoC device may include one or more processing units, graphics units, communication units, system virtualization units, and various application functions, all of which can be integrated (or “programmed”) onto a chip substrate as a single integrated circuit. When operating via the SoC, the functions described herein with respect to embodiments of this disclosure can be performed by dedicated logic integrated onto a single integrated circuit (chip) along with other components of the computing device 600.

[0038] Embodiments of this disclosure have been described above with reference to block diagrams and / or operational illustrations of methods, systems, and computer program products according to embodiments of this disclosure. Functions / actions marked in the blocks may not occur in the order shown in any flowchart. For example, two blocks shown successively may actually be executed substantially concurrently, or these blocks may sometimes be executed in reverse order, depending on the functions / actions involved.

[0039] While the specification includes examples, the scope of this disclosure is indicated by the appended claims. Furthermore, although the specification has been described in language specific to structural features and / or method actions, the claims are not limited to the features or actions described above. Rather, the specific features and actions described above are disclosed as examples of embodiments of this disclosure.

Claims

1. A method comprising: The Access Point (AP) Multilink Device (MLD) receives an indication of preferred ordering supported by the non-AP MLD; The AP MLD indicates its supported preference ranking; The AP MLD receives the desired preference order from the non-AP MLD; as well as The desired preference order is considered by the AP MLD.

2. The method according to claim 1, wherein, The desired preference order is used for requesting links.

3. The method according to claim 1 or 2, wherein, The desired preference order is used for adding links.

4. The method according to any of the preceding claims, wherein, The indication that the non-AP MLD supports preference ordering is received in the association request frame.

5. The method according to claim 4, wherein, The instruction is made in the support subfield of the ordered per-site (STA) configuration file.

6. The method according to any of the preceding claims, wherein, The indication that the non-AP MLD supports preference ordering is received in the reassociation request frame.

7. The method according to claim 6, wherein, The instruction is made in the support subfield of the ordered per-site (STA) configuration file.

8. The method according to any of the preceding claims, wherein, The indication that the non-AP MLD supports preference ordering is received in the link reconfiguration request frame.

9. The method according to claim 8, wherein, The instruction is made in the support subfield of the ordered per-site (STA) configuration file.

10. The method according to any of the preceding claims, wherein, The desired preference order is a decreasing preference order.

11. The method according to any of the preceding claims, wherein, The desired preference order is an increasing preference order.

12. The method according to any of the preceding claims, further comprising: The AP MLD announces the maximum number of links that can be established.

13. A system comprising: Memory storage device; as well as A processing unit, coupled to the memory storage device and disposed in an access point (AP) multilink device (MLD), wherein the processing unit is operable to: Receive instructions from non-AP MLDs that support preference ordering; The AP MLD indicates its supported preference ranking; The AP MLD receives the desired preference order from the non-AP MLD; and The desired preference order is considered by the AP MLD.

14. The system according to claim 13, wherein, The indication that the non-AP MLD supports preference ordering is received in the association request frame.

15. The system according to claim 14, wherein, The instruction is made in the support subfield of the ordered per-site (STA) configuration file.

16. The system according to any one of claims 13 to 15, wherein, The processing unit can also be operated to perform the method according to any one of claims 2 to 3 and / or 6 to 12.

17. A non-transitory computer-readable medium storing a set of instructions, said set of instructions, when executed, performing a method performed by said set of instructions, said method comprising: The Access Point (AP) Multilink Device (MLD) receives an indication of preferred ordering supported by the non-AP MLD; The AP MLD indicates its supported preference ranking; The AP MLD receives the desired preference order from the non-AP MLD; as well as The desired preference order is considered by the AP MLD.

18. The non-transitory computer-readable medium according to claim 17, wherein, The indication that the non-AP MLD supports preference ordering is received in the reassociation request frame.

19. The non-transitory computer-readable medium according to claim 18, wherein, The instruction is made in the support subfield of the ordered per-site (STA) configuration file.

20. The non-transitory computer-readable medium according to any one of claims 17 to 19, wherein, The indication that the non-AP MLD supports preference ordering is received in the link reconfiguration request frame.

21. The non-transitory computer-readable medium according to claim 20, wherein, The instruction is made in the support subfield of the ordered per-site (STA) configuration file.

22. The non-transitory computer-readable medium according to any one of claims 17 to 21, wherein, The method executed by the set of instructions further includes the method of any one of claims 2 to 5 and / or 10 to 12.

Images