Multi-link procedure for link disabling identification in basic service set (bss) transition management frame

Abstract

A multi-link procedure to identify link disabling in a basic service set (BSS) transition management frame can be provided. First, a basic service set (BSS) transition management (BTM) request can be created. The BTM request can indicate that link disabling will occur in the future. The BTM request can then be transmitted.

Description

[0001] Cross-reference to related applications The applicant claims the benefit of U.S. Provisional Application No. 63 / 581,467, filed on September 8, 2023, which is incorporated herein by reference. Technical Field

[0002] This disclosure generally relates to providing a multi-link process for identifying link disablement in a Basic Service Set (BSS) transition management frame. Background Technology

[0003] In computer networks, a wireless access point (AP) is a networking hardware device that allows Wi-Fi-compatible client devices to connect to wired networks and other client devices. An AP typically connects to a router as a standalone device (directly or indirectly via a wired network), but it can also be an integrated part of the router itself. Several APs can also work together, via direct wired or wireless connections, or through a central system commonly known as a Wireless Local Area Network (WLAN) controller. An AP differs from a hotspot, which is a physical location where Wi-Fi access to a WLAN is available.

[0004] Before the advent of wireless networks, setting up computer networks in commercial settings, homes, or schools typically required laying numerous cables through walls and ceilings to provide network access to all networked 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 cabling. An AP connects to a wired network and then provides a radio frequency link for other wireless devices to access that network. Most APs support connections from multiple wireless devices. APs are built to support the standard of transmitting and receiving data using these radio frequencies. Attached Figure Description

[0005] Various embodiments of the present disclosure are illustrated in conjunction with the accompanying drawings, which are included in and constitute a part of this disclosure. In the drawings: Figure 1 It is a block diagram for providing an operational environment for identifying link disablement in a multi-link process within a Basic Service Set (BSS) transition management frame; Figure 2 This is a flowchart of a method for providing a process to identify a disabled link in a Basic Service Set (BSS) transition management frame; Figure 3 The format of the request pattern field is shown; and Figure 4 It is a block diagram of a computing device. Detailed Implementation

[0006] Overview A multi-link process for identifying link disablement within a Basic Service Set (BSS) Transition Management (BTM) frame can be provided. First, a BSS Transition Management (BTM) request can be created. This BTM request can indicate a link disablement that will occur in the future. Then, the BTM request can be sent.

[0007] The foregoing overview and the following example embodiments are merely illustrative and explanatory, and should not be considered as limiting the scope of the described and claimed disclosure. 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. Wherever 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 the IEEE 802.11be draft amendment, when an auxiliary AP is being removed from an AP multilink device (MLD), the auxiliary AP being removed can send a Basic Service Set (BSS) Transition Management (BTM) request frame to notify legacy client devices (i.e., stations (STAs)) (pre-11be STAs) that the BSS corresponding to that AP will be terminated. For Extremely High Throughput (EHT) non-AP MLDs, an Imminent Link Removal bit is added to the BTM request to signal that only that auxiliary AP is being shut down, and that AP MLDs with multiple auxiliary APs will continue to operate on the remaining auxiliary APs. If a broadcast BTM request is sent, the Imminent Link Removal bit is required for EHT non-AP MLDs to determine that the BTM is for removing a link / auxiliary AP, rather than for removing the entire AP MLD.

[0010] The IEEE 802.11be draft amendment can also define another mechanism to disable a link of a corresponding affiliated AP for a period of time using a traffic identifier (TID) to link mapping mechanism. When an affiliated AP / link is disabled, a BTM request (e.g., broadcast or unicast) can be issued to notify legacy client devices (e.g., pre-11be STAs) that the corresponding BSS is being terminated (e.g., for legacy devices). If the BTM request is sent as a broadcast, the non-AP MLD receiving the BTM request may need a way to identify that the link of the corresponding AP is being disabled for a period of time, to distinguish it from: i) the AP / link being removed (already handled by the link removal bit); or ii) the entire AP MLD being shut down (already handled by the original BTM request).

[0011] This may be because non-AP MLDs behave differently when a link is disabled and when an AP is removed. When a link is disabled, the non-AP MLD maintains a group key for the disabled link so that it can operate on that link when it is later re-enabled. Furthermore, if a link is being removed, a non-AP MLD with two established links may decide to re-associate with another AP MLD (to maintain multi-link (ML) operation), but if the link is disabled for a short period, it may decide to remain with the current AP MLD. Therefore, embodiments of this disclosure can provide a process for an AP MLD to indicate in a BTM request frame that a specific link is being disabled and distinguish it from a link being removed.

[0012] Figure 1 An operational environment 100 is shown for providing a multi-link process that identifies link disablement in a Basic Service Set (BSS) transition management frame. 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., WLAN access for client devices). The multiple APs 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 the multiple client devices. The multiple client devices may include, but are not limited to, a first client device 130, a second client device 135, and a third client device 140. The devices among the multiple client devices may include, but are 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 may be compatible with, for example, but not limited to, the Institute of Electrical and Electronics Engineers (IEEE) 802.11 specification.

[0013] Multiple access points (APs) and multiple client devices can use multi-link operation (MLO), where they simultaneously transmit and receive across different frequency bands and channels by establishing two or more links to two or more AP radios. 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. Two or more links on any given client device can be established with any one AP or with any combination of APs.

[0014] Controller 105 may include a Wireless Local Area Network (WLC) controller and may provision 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 about coverage environment 110 to provide a multi-link process for identifying link disablement in Basic Service Set (BSS) transition management frames.

[0015] The aforementioned components of 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 operating environment 100 can be implemented in circuits including discrete electronic components, packaged or integrated electronic chips containing logic gates, circuits utilizing microprocessors, or on a single chip containing electronic components or a microprocessor. Furthermore, the components of operating environment 100 can also be implemented using other technologies capable of performing logical operations such as AND, OR, and NOT, including but not limited to mechanical, optical, fluid, and quantum technologies. As described below regarding… Figure 4 In more detail, the components of the operating environment 100 can be implemented in the computing device 400.

[0016] Figure 2 This is a flowchart illustrating the general stages involved in a method 200 for providing a multi-link process for identifying a disabled link in a Basic Service Set (BSS) transition management frame, consistent with embodiments of this disclosure. Method 200 can be implemented using a computing device 400, as described below. Figure 4 More detailed description. The computing device 400 can be embodied by the first AP 115. The implementation of the various stages of method 200 will be described in more detail below.

[0017] Method 200 may begin at start block 205 and proceed to stage 210, in which the first AP 115 may receive a Basic Service Set (BSS) Transformation Management (BTM) query. The first client device 130 may send a BTM query to the first AP 115, potentially requesting a BTM request. For example, if the Received Signal Strength Indicator (RSSI) of the currently associated AP is too low or the first client device 130 finds a better AP, the first client device 130 may send a BTM query to the associated AP (e.g., the first AP 115). Upon receiving the query, the AP may respond with a BTM request as described below. In other embodiments, the BTM request may be unsolicited. For example, if the first AP 115 detects that the RSSI of the first client device 130 is below an RSSI threshold, it may send a BTM request to the first client device 130 unsolicited.

[0018] Upon receiving a BTM query from the first AP 115 in stage 210, method 200 can proceed to stage 220, where the first AP 115 can create a BTM request. This BTM request can indicate a link disablement that will occur in the future. For example, Figure 3The request mode field format 300 is illustrated. Embodiments of this disclosure may provide a bit in the BSS Transition Management (BTM) request frame to indicate to the non-AP MLD that the BTM request sent by the affiliated AP is for future link disabling. The request mode field format 300 in the BTM request frame can be modified by adding, for example... Figure 3 The LinkDisablementImminent subfield 305 shown is enhanced.

[0019] When a link of a subordinate AP to a corresponding AP MLD is being disabled, the subordinate AP can set the Link Removal Imminent subfield 305 to 1 in the BTM request frame sent by the AP. In one embodiment, to minimize interference with EHT client devices deployed before this protocol definition, the subordinate AP can also set the Link Removal Imminent subfield 310 to 1 in the BTM request, as these devices may not understand the Link Removal Imminent subfield 305. In another embodiment, the Link Removal Imminent subfield 310 may not be set to 1 for a link being disabled (e.g., deployment of the Link Removal Imminent subfield 305 is understood by all devices). In another embodiment, the AP MLD can ensure that the advertised Traffic Identifier (TID) to Link Mapping (T2LM) is performed before the AP MLD sends this BTM request, so that most associated non-AP MLDs should no longer listen for the soon-to-be-disabled subordinate AP, and most may then miss the BTM request. However, there may be non-AP MLDs that are still actively using the link even after the advertised T2LM until the link is disabled, and these non-AP MLDs may receive the BTM request.

[0020] In a BTM request, the affiliated AP (e.g., the first AP 115) can indicate the duration for which the link can be disabled in the Duration subfield of the BSS termination duration sub-element included in the BTM request frame (used by legacy devices to determine how long the BSS will be gone). The Duration subfield can be set based on the Expected Duration field of the T2LM for the announcement of the link's disabling.

[0021] Non-MLD clients may only see regular IEEE 802.11v BTM requests and proceed as usual. A "Wi-Fi7R1" non-AP MLD (i.e., a non-AP MLD deployed prior to this protocol definition), according to the embodiments followed above, may miss a BTM request, or may detect a BTM request and use the "Link Remove Now" subfield 310, but not the "Link Disable Now" subfield 305 (e.g., because it might be reserved for that generation of clients), and may eventually gracefully remove the link. A "Wi-Fi7R1" non-AP MLD (i.e., a non-AP MLD deployed after this protocol definition), when receiving a BTM request frame from an AP with the "Link Disable Now" subfield 305 set to 1, can determine that the BTM request is for disabling the link corresponding to that AP. Note that a non-AP MLD can retrieve detailed information about the link disabling (e.g., the handover time when the link is disabled and the expected duration of the link disabling) from the TID-to-link mapping element of the announcement received from a Beacon or Probe Response frame.

[0022] AP MLDs can suggest BSS transition candidates for non-AP MLDs in BTM request frames sent for link-disabled scenarios, for example, in the following cases: i) for non-AP MLDs that have only established a single link with the AP MLD, enabling these non-AP MLDs to (re)associate with another preferred AP MLD, or possibly associate with the current AP MLD but on a different link; and ii) for non-AP MLDs that have established a dual-link setup with the AP MLD, including the link that is about to be disabled, enabling these non-AP MLDs to (re)associate with another preferred AP MLD to maintain multi-link operation, or possibly associate with the current AP MLD but on a different dual-link group. Having an explicit link-disabled indication in the BTM request frame ensures that Wi-Fi 7R1 non-AP MLDs do not misinterpret the BTM request in a link-disabled scenario as meaning link removal, or worse, as the shutdown of the entire AP MLD.

[0023] Once the first AP 115 has created a BTM request in phase 220, method 200 can continue to phase 230, where the first AP 115 can send the BTM request. For example, the first client device 130 can receive the BTM request sent by the first AP 115. As mentioned above, the request can be requested or unrequested.

[0024] After the first AP 115 sends a BTM request in phase 230, method 200 can proceed to phase 240, where the first AP 115 can receive a BTM response. For example, upon receiving the BTM request, the first client device 130 can determine whether to disconnect from the first AP 115 and roam to a recommended AP. If the first client device 130 determines to roam, it can send a BTM response to the first AP 115. If the first client device 130 fails to leave the current BSS before the disassociation timer expires, the first AP 115 can send a disassociation request to the first client device 130 and can deregister the first client device 130. Once the first AP 115 receives the BTM response in phase 240, method 200 can then terminate at phase 250.

[0025] Figure 4 A computing device 400 is shown. (For example...) Figure 4 As shown, computing device 400 may include a processing unit 410 and a memory unit 415. Memory unit 415 may include software module 420 and database 425. When executed on processing unit 410, software module 420 may perform, for example, the above-described... Figure 2 The described process is for providing a multi-link procedure to identify disabled links in a Basic Service Set (BSS) transition management frame. Computing device 400 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 400.

[0026] Computing device 400 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 TVs, network storage devices, network relay devices, or other similar microcomputer-based devices. Computing device 400 can include any computer operating environment, such as handheld devices, multiprocessor systems, microprocessor-based or programmable transmitter-based electronic devices, minicomputers, mainframes, etc. Computing device 400 can also be implemented in a distributed computing environment where tasks are performed by remote processing devices. The above systems and devices are examples; computing device 400 can include other systems or devices.

[0027] Embodiments of this disclosure may be implemented as a computer process (method), a computing system, or as an 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 a computer process. A computer program product may also be a propagated signal on a carrier wave of a computer program readable by a computing system and encoded with instructions for performing a 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 having computer-usable or computer-readable program code embodied in that medium for use by or in conjunction 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 conjunction with an instruction execution system, apparatus, or device.

[0028] 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), fiber optics, and portable optical disc read-only memory (CD-ROM). Note that computer-usable or computer-readable media can even be paper or another suitable medium on which a program is printed, as the program 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.

[0029] 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 on or read 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.

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

[0031] Embodiments of this disclosure can be implemented via 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 via dedicated logic integrated onto a single integrated circuit (chip) along with other components of the computing device 400.

[0032] For example, embodiments of this disclosure are described above with reference to block diagrams and / or operating instructions of methods, systems, and computer program products according to embodiments of this disclosure. The functions / actions described in the blocks may occur in a different order than that shown in any flowchart. For example, two blocks shown successively may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order, depending on the functions / actions involved.

[0033] Although the specification includes examples, the scope of this disclosure is indicated by the following claims. Furthermore, while 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: Create a Basic Service Set (BSS) Transformation Management (BTM) request, wherein the BTM request indicates a future link disablement that will occur; and Send the BTM request.

2. The method according to claim 1, wherein, The BTM request indicates the future link disablement that will occur in the request mode field of the BTM request frame.

3. The method according to claim 1, wherein, The BTM request indicates the upcoming link disablement in the upcoming link disable subfield of the request mode field in the BTM request frame.

4. The method according to claim 1, wherein, Creating the BTM request also includes setting the value of the soon-to-be-deassociated subfield to 1 in the BTM request frame.

5. The method according to claim 1, wherein, Creating the BTM request also includes setting the BSS termination subfield in the BTM request frame to a value of 0 or 1.

6. The method according to claim 1, wherein, Creating the BTM request also includes setting the upcoming link removal subfield to a value of 0 or 1 in the BTM request frame.

7. The method according to claim 1, wherein, The BTM request also indicates the duration of the future link disablement that will occur.

8. The method according to claim 1, wherein, The BTM request also indicates the duration of the future link disablement in the duration subfield of the BSS termination duration subfield.

9. The method according to claim 8, wherein, The duration subfield is set based on the duration for which the announcement in the beacon frame will be disabled for future links.

10. The method according to claim 1, wherein, The BTM request also includes recommendations for BSS transition candidates to be used for association should the future link disabling occur.

11. The method according to claim 1, wherein, Sending the BTM request includes sending the BTM request as a broadcast message.

12. The method according to claim 1, further comprising: Receive BTM queries; as well as The BTM request is created in response to receiving the BTM query.

13. The method according to claim 1, wherein, The BTM request includes requests that were not requested.

14. The method of claim 1, further comprising receiving a BTM response.

15. A system comprising: Memory devices; as well as A processing unit, coupled to the memory device, wherein the processing unit is configured to: Create a Basic Service Set (BSS) Transformation Management (BTM) request, wherein the BTM request indicates a future link disablement that will occur; and Send the BTM request.

16. The system according to claim 15, wherein, The BTM request indicates the future link disablement that will occur in the request mode field of the BTM request frame.

17. The system according to claim 15, wherein, The BTM request indicates the upcoming link disablement in the upcoming link disable subfield of the request mode field in the BTM request frame.

18. A non-transitory computer-readable medium storing an instruction set, which, when executed, performs a method executed by the instruction set, comprising: Create a Basic Service Set (BSS) Transformation Management (BTM) request, wherein the BTM request indicates a future link disablement that will occur; and Send the BTM request.

19. The non-transitory computer-readable medium according to claim 18, wherein, The BTM request indicates the future link disablement that will occur in the request mode field of the BTM request frame.

20. The non-transitory computer-readable medium according to claim 18, wherein, The BTM request indicates the upcoming link disablement in the upcoming link disable subfield of the request mode field in the BTM request frame.

Images