CN114173430A

CN114173430A - Management method and device for block acknowledgement session in wireless local area network

Info

Publication number: CN114173430A
Application number: CN202010948015.6A
Authority: CN
Inventors: 王云贵
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2020-09-10
Filing date: 2020-09-10
Publication date: 2022-03-11
Also published as: WO2022052863A1

Abstract

A method and device for managing BA session in WLAN are disclosed, belonging to the technical field of wireless communication. The first multi-link device sends a BA session establishment request to the associated second multi-link device, wherein the BA session establishment request is used for requesting to establish a BA session on the target link. The first multi-link device receives a BA session setup response from the second multi-link device to the BA session setup request. When the BA session establishment response indicates that the BA session establishment was successful, the first multi-link device sends data to the second multi-link device on the target link. Upon receiving a BA message from the second multi-link device on the first link, the first multi-link device maintains the BA session on the first link. When the first multilink equipment receives the BA message from the second multilink equipment on any link, the first multilink equipment keeps the BA conversation alive, and the effective management and maintenance of the BA conversation are realized.

Description

Management method and device for block acknowledgement session in wireless local area network

Technical Field

The present invention relates to the field of wireless communication technologies, and in particular, to a method and an apparatus for managing a Block Acknowledgement (BA) session in a Wireless Local Area Network (WLAN).

Background

With the development of WLAN technology, wireless devices may support multi-link communication. A wireless device supports multilink communication, meaning that the wireless device supports simultaneous communication over multiple frequency bands, or simultaneous communication over different channels of the same frequency band. A wireless device supporting multi-link communication is generally called a multi-link device (MLD). The multi-link device includes a plurality of Stations (STAs).

Currently, the multilink devices in WLANs fall into two categories: access Point (AP) multilink devices (i.e., AP MLD) and non-access point (non-AP) multilink devices (i.e., non-AP MLD). The STA in the access point multilink device is an AP. The STAs in the non-access point multilink device are non-AP STAs. The non-access point multilink device may associate to the access point multilink device, i.e., one or more links may be established between the non-access point multilink device and the access point multilink device.

Devices in the WLAN may establish a BA session for each service type that needs to transmit data, and if there are multiple links between two associated multi-link devices, how to implement BA session establishment and maintenance based on the multiple links is a problem.

Disclosure of Invention

The application provides a method and a device for managing BA sessions in a WLAN, which are used for realizing the management of the BA sessions on a plurality of links among multilink equipment.

In a first aspect, a method for managing a BA session in a WLAN is provided. The method comprises the following steps: the first multi-link device sends a BA session establishment request to a second multi-link device, the first multi-link device being associated with the second multi-link device. The BA session establishment request is for requesting establishment of a BA session on a target link, the target link including a plurality of links between the first multi-link device and the second multi-link device. The first multi-link device receives a BA session setup response from the second multi-link device to the BA session setup request. When the BA session establishment response indicates that the BA session establishment was successful, the first multi-link device sends data to the second multi-link device on the target link. Upon receiving a BA message from the second multi-link device on the first link, the first multi-link device maintains the BA session on the first link, which is any one of the target links.

In the present application, two multilink devices establish a BA session on multiple links, and when a first multilink device receives a BA message from a second multilink device on one link, the first multilink device maintains the BA session on the link, that is, when the first multilink device receives a BA message from the second multilink device on any one link, the BA session between the first multilink device and the second multilink device remains active, thereby implementing effective maintenance of the BA session, and thus enabling reliability of data transmission to be higher.

Optionally, the BA session establishment request includes a service identifier of a target service type, and the BA session establishment request is used to request establishment of a BA session of the target service type on a target link. The BA session establishment request may be used to request establishment of a BA session for one service type on the target link, or may also be used to request establishment of a BA session for multiple service types on the target link.

In a first possible implementation, the BA sessions of all links in the target link share a timeout timer. In this case, the implementation procedure for the first multilink device to maintain the BA session on the first link includes: the first multi-link device maintains BA sessions for all of the target links.

Optionally, the implementation process of the first multi-link device maintaining BA sessions of all links in the target link includes: the first multi-link device resets the timeout timer for the BA session.

In this first possible implementation, the BA session establishment request includes a timeout duration of a timeout timer of the BA session.

In a second possible implementation, a timeout timer is used for the BA session for each of the target links individually. In this case, the implementation procedure for the first multilink device to maintain the BA session on the first link includes: the first multi-link device resets a timeout timer for the BA session for the first link.

In this second possible implementation manner, the BA session establishment request includes multiple sets of per-link parameters corresponding to multiple links in the target link, where each set of per-link parameters includes a link identifier of the corresponding link and an timeout duration of a BA session timeout timer of the link.

Optionally, in combination with the second possible implementation manner, the target link further includes a second link. When the first multi-link device does not receive a BA message from the second multi-link device on the second link within the timing period of the BA session for the second link, the first multi-link device sends a link update message to the second multi-link device, the link update message indicating that the second link is disabled in the target link.

Optionally, when the first multi-link device does not receive the BA message from the second multi-link device on the second link within the timing period of the second link, the implementation process of the first multi-link device sending the link update message to the second multi-link device includes: and when the continuous loss times of the BA messages from the second multi-link equipment on the second link reach a target threshold value in the timing period of the second link, the first multi-link equipment sends a link updating message to the second multi-link equipment. Or, when the first multilink device does not reach the target threshold value for the continuous loss times of the BA messages from the second multilink device on the second link within the timing period, the first multilink device resets the timeout timer of the BA session of the second link at the end time of the timing period of the second link and clears the continuous loss times.

Optionally, the target link further includes a third link. And when the first multilink equipment is in the target duration and the continuous loss times of the BA messages from the second multilink equipment on the third link reach a target threshold value, the first multilink equipment sends a link updating message to the second multilink equipment, wherein the link updating message is used for indicating that the third link is disabled in the target link.

Optionally, the target duration is equal to a timeout duration of a timeout timer of a BA session of the third link. When BA sessions of all links in the target link share one timeout timer, the timeout duration of the timeout timer of the BA session of the third link is the timeout duration of the shared timeout timer.

Optionally, the BA session establishment request comprises a target threshold value.

Optionally, the link update message includes a cause code indicating that the BA message reply is timed out.

Optionally, when all links in the target link are disabled, the first multi-link device sends a BA session deletion request to the second multi-link device, where the BA session deletion request is used to request deletion of the BA session.

Optionally, the first multilink device is an access point multilink device, the second multilink device is a non-access point multilink device, and when all links in the target link are disabled: when a fourth link which is not disabled due to BA message reply timeout exists in the target link, the first multi-link device sends a link activation request to the second multi-link device, and the link activation request is used for requesting to activate the fourth link. The first multilink device enables the fourth link when the first multilink device receives a link activation success response from the second multilink device for the link activation request. Correspondingly, the implementation process of sending the BA session deletion request from the first multi-link device to the second multi-link device includes: and when the first multi-link equipment determines that the fourth link fails to be activated, the first multi-link equipment sends the BA session deletion request to the second multi-link equipment.

Optionally, in combination with the first possible implementation manner, when the first multi-link device does not receive a BA message from the second multi-link device on all links in the target link within the timing period of the BA session, the first multi-link device sends a BA session deletion request to the second multi-link device, where the BA session deletion request is used to request deletion of the BA session.

Optionally, the BA session delete request includes a cause code indicating that the BA message reply is timed out.

In a second aspect, a first multi-link device in a wireless local area network is provided. The first multilink device comprises a plurality of functional modules, which interact to implement the method of the first aspect and its embodiments. The functional modules can be implemented based on software, hardware or a combination of software and hardware, and the functional modules can be combined or divided arbitrarily based on specific implementation.

In a third aspect, a first multi-link device in a wireless local area network is provided, including: a processor and a transceiver;

the processor is configured to invoke a computer program to implement the method according to any one of the first aspect in cooperation with the transceiver.

In a fourth aspect, a computer storage medium is provided, having stored thereon instructions that, when executed by a processor of a computer device, implement the method of the first aspect and its embodiments described above.

In a fifth aspect, a chip is provided, where the chip includes programmable logic circuits and/or program instructions, and when the chip runs, the method in the first aspect and its embodiments is implemented.

Drawings

Fig. 1 is a diagram illustrating an application scenario of an embodiment of the present application applied to a WLAN;

fig. 2 is a schematic structural diagram of an associated access point multilink device and a non-access point multilink device according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of another associated access point multilink device and non-access point multilink device provided in an embodiment of the present application;

fig. 4 is a schematic structural diagram of another associated access point multilink device and non-access point multilink device provided in an embodiment of the present application;

fig. 5 is a schematic diagram of a communication scenario of an access point multilink device and a non-access point multilink device according to an embodiment of the present application;

fig. 6 is a schematic diagram of a communication scenario of another access point multi-link device and a non-access point multi-link device according to an embodiment of the present application;

fig. 7 is a flowchart illustrating a method for managing a BA session in a WLAN according to an embodiment of the present application;

fig. 8 is a schematic diagram of a BA session between multiple link devices according to an embodiment of the present application;

fig. 9 is a schematic frame structure diagram of a BA session establishment request according to an embodiment of the present application;

fig. 10 is a schematic diagram of a frame structure of a BA session establishment response according to an embodiment of the present application;

fig. 11 is a schematic diagram of a BA session performed between multiple link devices according to an embodiment of the present application;

fig. 12 is a schematic frame structure diagram of another BA session establishment request provided in the embodiment of the present application;

fig. 13 is a schematic diagram of a frame structure of another BA session establishment response according to an embodiment of the present application;

fig. 14 is a schematic diagram of a frame structure of a link update message according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a first multi-link device in a wireless local area network according to an embodiment of the present application;

fig. 16 is a block diagram of a multi-link device according to an embodiment of the present disclosure.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

The multilink device includes one or more subordinate stations, which are logical stations, "multilink device includes subordinate stations" is briefly described as "multilink device includes stations" in the embodiment of the present application. The affiliated stations may be APs or non-AP STAs. For convenience of description, the present application refers to a multi-link device whose affiliated station is an AP as an access point multi-link device (AP multi-link device), and refers to a multi-link device whose affiliated station is a non-AP STA as a non-access point multi-link device (non-AP multi-link device).

The multi-link device may implement wireless communication according to 802.11 series protocols, for example, according to an Extra High Throughput (EHT), or according to a draft protocol based on 802.11be, or compatibly supporting the draft protocols of the EHT and 802.11be, so as to implement communication with other devices, which may or may not be multi-link devices.

The embodiment of the application is applied to the WLAN, and the WLAN comprises the access point multilink equipment and the non-access point multilink equipment. One or more links may be established between the non-access point multilink device and the access point multilink device, each link connecting one non-AP STA in the non-access point multilink device and one AP in the access point multilink device. The non-AP STA and the AP at two ends of one link are associated. Multiple APs in an access point multilink device operate independently, e.g., a portion of the APs operate and another portion of the APs sleep. A plurality of non-AP STAs in the non-access point multilink device work independently, for example, one part of the non-AP STAs works, and the other part of the non-AP STAs is dormant. The method comprises the steps that an access point multilink device is associated with a non-access point multilink device, at least one AP in the access point multilink device is associated with at least one non-AP STA in the non-access point multilink device, and the access point multilink device has at least one link with the non-access point multilink device.

Optionally, fig. 1 shows an application scenario diagram of the embodiment of the present application applied to a WLAN. As shown in fig. 1, the application scenario includes a multi-link device 101 and a multi-link device 102. Multilink device 101 is associated with multilink device 102. Multiple links can be used for communication between the multi-link device 101 and the multi-link device 102, so that the effect of improving throughput is achieved. Referring to fig. 1, a multi-link device 101 is an access point multi-link device and a multi-link device 102 is a non-access point multi-link device. Of course, the WLAN may also include other devices. The number and types of devices shown in fig. 1 are merely exemplary.

Fig. 2 and 3 show a schematic diagram of the structure of an associated access point multi-link device and non-access point multi-link device, respectively. Two links, link 1 and link 2, are provided between the access point multilink device and the non-access point multilink device. Fig. 2 and 3 mainly illustrate Physical layer (PHY) and Media Access Control (MAC) layer portions in an Access point multilink device and a non-Access point multilink device.

As shown in fig. 2, the AP multi-link device includes a plurality of APs (including AP1 and AP2) that are independent of each other at a low mac (low mac) layer and a PHY layer, and are independent of each other at a high mac (high mac) layer; the non-access point multilink device includes a plurality of non-AP STAs (including the non-AP STA1 and the non-AP STA2) which are independent of each other at a lower MAC layer and a PHY layer and are also independent of each other at an upper MAC layer.

As shown in fig. 3, a plurality of APs (including AP1 and AP2) included in the access point multilink device are independent of each other at the lower MAC layer and the PHY layer, sharing the upper MAC layer. A plurality of non-AP STAs (including the non-AP STA1 and the non-AP STA2) included in the non-access point multilink device are independent of each other at the lower MAC layer and the PHY layer, sharing the higher MAC layer.

Optionally, instead of the structure that the access point multilink device uses a high MAC layer in common, the access point multilink device may also use a structure that high MAC layers are mutually independent; or, the access point multilink device may adopt a structure shared by high MAC layers, and the non-access point multilink device may adopt a structure in which high MAC layers are independent of each other. For example, the upper MAC layer or the lower MAC layer may be implemented by one processor in a chip system of the multi-link device, or may be implemented by different processors in one chip system, respectively.

Optionally, the multi-link device in the embodiment of the present application may be a single-antenna device, or may be a multi-antenna device. For example, it may be a device with more than two antennas. In the embodiment of the present application, the number of antennas included in the multi-link device is not limited, and fig. 4 illustrates an example in which the access point multi-link device is a multi-antenna and the non-access point multi-link device is a single antenna. In the embodiment of the present application, the multi-link device may allow services of the same service type to be transmitted on multiple links.

The operating frequency band of the multi-link device may include, but is not limited to: sub 1 gigahertz (GHz), 2.4GHz, 5GHz, 6GHz and 60 GHz. Fig. 5 and 6 are diagrams illustrating communication between an access point multi-link device and a non-access point multi-link device through multiple links in a WLAN, respectively.

Fig. 5 shows a scenario where an access point multi-link device 101 and a non-access point multi-link device 102 communicate. The access point multilink device 101 includes affiliated APs 1 and 2, the non-access point multilink device 102 includes affiliated non-AP STAs 1 and 2, and the access point multilink device 101 and the non-access point multilink device 102 communicate in parallel using link 1 and link 2. For example, the AP1 operating in the 2.4GHz band in the access point multi-link device 101 transmits uplink or downlink data between the non-AP STA1 operating in the 2.4GHz band in the non-access point multi-link device 102 via the link 1. The AP2 operating in the 5GHz band in the access point multi-link device 101 transmits uplink or downlink data between the non-AP STA2 operating in the 5GHz band in the non-access point multi-link device 102 through the link 2.

Fig. 6 illustrates a scenario in which the access point multi-link device 101 communicates with a non-access point multi-link device 102A and a non-access point multi-link device 102B. The access point multi-link device 101 includes subordinate APs 1 to 3, the non-access point multi-link device 102A includes subordinate non-AP STAs 1 and 2, and the non-access point multi-link device 102B includes subordinate non-AP STAs 3 and 4. The access point multi-link device 101 communicates with the non-access point multi-link device 102A using link 1 and link 3, and communicates with the non-access point multi-link device 102B using link 2 and link 3, respectively. For example, the AP1 operating in the 2.4GHz band in the access point multi-link device transmits uplink or downlink data between the non-AP STA1 operating in the 2.4GHz band in the non-access point multi-link device 102A over link 1. The AP2 operating in the 5GHz band in the access point multi-link device transmits uplink or downlink data between the non-AP STA3 operating in the 5GHz band in the non-access point multi-link device 102B via the link 2. The AP3 operating in the 6GHz band in the access point multilink device 101 transmits uplink or downlink data between the non-access point multilink device 102A and the non-AP STA2 operating in the 6GHz band through the link 3, and also transmits uplink or downlink data between the non-access point multilink device 102B and the non-AP STA4 operating in the 6GHz band through the link 3.

Fig. 5 shows that the access point multi-link device supports 2 frequency bands (2.4GHz, 5GHz), and fig. 6 shows that the access point multi-link device supports three frequency bands (2.4GHz, 5GHz, 6GHz), one for each link. A link is also understood herein as a station operating on the link. In practical applications, the access point multi-link device and the non-access point multi-link device may also support more or fewer frequency bands, that is, the access point multi-link device and the non-access point multi-link device may operate on more or fewer links, which is not limited in this embodiment of the present application.

For convenience of explanation, in the following embodiments of the present application, a non-AP STA in a non-access point multilink device is simply referred to as an STA.

For example, a multi-link device is a device having a wireless communication function, the device may be a complete device, and may also be a chip or a processing system installed in the complete device, and the device installed with the chip or the processing system may implement the method and the function of the embodiment of the present application under the control of the chip or the processing system.

The non-access point multi-link device in the embodiment of the present application has a wireless transceiving function, can support 802.11 series protocols, and can communicate with an access point multi-link device or other non-access point multi-link devices or single-link devices, for example, the non-access point multi-link device is any user communication device that allows a user to communicate with an AP and further communicate with a WLAN. For example, the non-access point multilink device may be a tablet Computer, a desktop Computer, a laptop Computer, a notebook Computer, an Ultra-mobile Personal Computer (UMPC), a handheld Computer, a netbook, a Personal Digital Assistant (PDA), a mobile phone, or other user equipment that can be networked, or an internet of things node in the internet of things, or a vehicle-mounted communication device in the vehicle networking, and the non-access point multilink device may also be a chip and a processing system in these terminals.

The access point multilink device in the embodiment of the application is a device for providing access service for the STA, and can support 802.11 series protocols. For example, the access point multilink device may be a communication device such as a communication server, a router, a switch, a bridge, etc., or the access point multilink device may include various forms of macro base stations, micro base stations, relay stations, etc., or the access point multilink device may also be a chip and processing system in these various forms of devices.

In the embodiment of the present application, the multi-link device can support high-speed low-latency transmission, and with the continuous evolution of WLAN application scenarios, the multi-link device can be applied to more scenarios, such as sensor nodes in a smart city (e.g., smart water meters, smart electricity meters, smart air detection nodes), smart devices in a smart home (e.g., smart cameras, projectors, display screens, televisions, stereos, refrigerators, washing machines, etc.), nodes in the internet of things, entertainment terminals (e.g., wearable devices such as Augmented Reality (AR), Virtual Reality (VR), etc.), smart devices in smart offices (e.g., printers, projectors, etc.), car networking devices in car networking, some infrastructures in daily life scenarios (e.g., automatic vending machines, business-super self-help navigation consoles, self-help cash registering devices, a self-service ordering machine, etc.). The specific form of the multilink device in the embodiment of the present application is not particularly limited, and is merely an exemplary illustration.

At present, the communication mode between devices is: the sending end equipment sends data to the receiving end equipment, and the receiving end equipment returns a confirmation frame to the sending end equipment after receiving the data, wherein the confirmation frame is used for confirming whether the data is correctly received. In order to improve WLAN performance, the sending end device may aggregate a plurality of MAC Protocol Data Units (MPDUs) into one aggregated MPDU (a-MPDU) by using a frame aggregation technique in the MAC layer. Because all the MPDUs in the same a-MPDU are transmitted by using one physical layer protocol data unit (PPDU), the overhead of a PPDU preamble can be reduced, and transmission efficiency is further improved. Accordingly, the receiving-end device confirms whether the a-MPDU is correctly received using the BA frame.

And the BA session means that the receiving end equipment adopts a BA frame to confirm whether to correctly receive the data sent by the sending end equipment. In the embodiment of the application, the sending end device sends the a-MPDU to the receiving end device, and the receiving end device adopts a BA frame to confirm whether the a-MPDU is correctly received, which may be referred to as a BA session process. A process in which a sending-end device sends one or more MPDUs to a receiving-end device, and then sends a Block Acknowledgement Request (BAR) frame to the receiving-end device, and the receiving-end device uses the BA frame to confirm whether the one or more MPDUs are correctly received, which may also be referred to as a BA session process. 802.11n provides a BA session management method for a single-link device, and embodiments of the present application provide a BA session management method for a multi-link device, specifically including establishment and maintenance of a BA session.

Fig. 7 is a flowchart illustrating a method for managing a BA session in a WLAN according to an embodiment of the present application. The method may be applied to the scenario shown in any one of fig. 1 to 6, as shown in fig. 7, the method includes:

step 701, the first multilink device sends a BA session establishment request to the second multilink device.

The first multi-link device is associated with a second multi-link device having a plurality of links therebetween. The first multilink equipment is access point multilink equipment, and the second multilink equipment is non-access point multilink equipment; or, the first multi-link device is a non-access point multi-link device, and the second multi-link device is an access point multi-link device. The BA session establishment request is for requesting establishment of a BA session on the target link. The BA session establishment request includes a link identification of the target link. The target link includes a plurality of links between the first multi-link device and the second multi-link device.

Optionally, the BA session establishment request further includes a traffic identifier of the target traffic type, which may also be referred to as a Traffic Identifier (TID), and the BA session establishment request is used to request to establish a BA session of the target traffic type on the target link. The BA session establishment request may be for requesting establishment of a BA session for one traffic type on the target link, or may be for requesting establishment of a BA session for multiple traffic types on the target link.

Alternatively, the BA session establishment request may also be referred to as an add block acknowledgement request (ADDBA request) frame.

Step 702, the second multi-link device sends a BA session establishment response to the BA session establishment request to the first multi-link device.

And after receiving the BA session establishment request from the first multi-link equipment, the second multi-link equipment replies a BA session establishment response to the first multi-link equipment. The BA session establishment response indicates success of BA session establishment or indicates a reason for refusal of establishment of the BA session. The BA session setup response indication includes the link identification of the target link.

Optionally, when the BA session establishment request includes the service identifier of the target service type, the BA session establishment response may further include the service identifier of the target service type, so as to indicate that the BA session establishment response is for the target service type.

Alternatively, the BA session setup response may also be referred to as an add block acknowledgement response (ADDBA response) frame.

And step 703, when the BA session establishment response indicates that the BA session establishment is successful, the first multi-link device sends data to the second multi-link device on the target link.

Optionally, the data transmitted by the first multi-link device to the second multi-link device comprises quality of service (QoS) data, which may be transmitted in the form of a-MPDUs. Optionally, when the BA session establishment response indicates that the BA session establishment for the target service type is successful, the first multi-link device sends QoS data of the target service type to the second multi-link device on the target link.

For example, the target link includes a first link and a second link, and the first multi-link device transmits data to the second multi-link device over the target link, including: the first multi-link device transmits data to the second multi-link device on the first link; or the first multilink equipment transmits data to the second multilink equipment on the second link; alternatively, the first multi-link device transmits data to the second multi-link device on both the first link and the second link.

Step 704, when the second multilink device receives data from the first multilink device, the second multilink device sends a BA message to the first multilink device over the first link.

The first link is any one of the target links. Optionally, when the second multi-link device receives data from the second multi-link device on the first link, the second multi-link device sends a BA message to the first multi-link device on the first link.

In this embodiment of the application, when a plurality of links are provided between the first multilink device and the second multilink device, the second multilink device may further send a BA message for data on one link after receiving the data on the other link. For example, the target link includes a first link and a second link, and the second multi-link device sends a BA message to the first multi-link device over the first link or the second link when the second multi-link device receives data from the second multi-link device over the second link.

Step 705, the first multi-link device maintains a BA session on the first link.

The first multi-link device maintains the BA session on the first link, i.e., the first multi-link device keeps the BA session active on the first link, which may also be referred to as the first multi-link device enables the first link to conduct the BA session.

In the embodiment of the application, two multilink devices establish a BA session on multiple links, and when a first multilink device receives a BA message from a second multilink device on one link, the first multilink device maintains the BA session on the link, that is, when the first multilink device receives a BA message from the second multilink device on any one link, the BA session between the first multilink device and the second multilink device is kept alive, so that the BA session is effectively maintained, and the reliability of data transmission is high.

In a first alternative embodiment of the present application, the BA sessions of all links in the target link share one timeout timer, that is, the first multi-link device sets the same timing period for the BA sessions of all links in the target link. Then, in step 705 above, the first multi-link device maintains the BA session on the first link, which may be: the first multi-link device maintains BA sessions for all of the target links. E.g., all links share a BA session, maintaining the BA session also maintains the BA session for the first link. The implementation process comprises the following steps: the first multi-link device resets the timeout timer for the BA session.

Optionally, the first multilink device first starts the timeout timer for the BA session, either upon receiving a BA session setup response from the second multilink device or upon receiving the first BA message from the second multilink device on any of the target links. For example, the first multi-link device may send data on any of the target links after receiving a BA session setup response from the second multi-link device, and the first multi-link device may start a timeout timer for the BA session when a BA message is received from the second multi-link device on that link.

For example, the first multi-link device includes AP1 and AP2, the second multi-link device includes STA1 and STA2, and the target links include link 1 between AP1 and STA1 and link 2 between AP2 and STA 2. Fig. 8 is a schematic diagram of a BA session performed between multiple link devices according to an embodiment of the present disclosure. As shown in fig. 8, after the first multi-link device establishes a BA session with the second multi-link device on the target link, AP1 sends data 1 on link 1, and when AP1 receives BA message 1 from STA1 on link 1, the first multi-link device starts a timeout timer for the BA session. Then AP1 sends data 2 on link 1, AP2 sends data 3 on link 2, AP1 does not receive BA message 2 from STA1 on link 1, AP2 receives BA message 3 from STA2 on link 2, and the first multi-link device resets the timeout timer for the BA session when it receives BA message 3. Wherein, the arrow points to show the time sequence, and the overtime duration of the overtime timer is T.

Optionally, the BA session establishment request comprises a timeout duration of a timeout timer of the BA session. For example, fig. 9 is a schematic frame structure diagram of a BA session establishment request according to an embodiment of the present application. As shown in fig. 9, the BA session establishment request includes a category (category) field, a BA action (BA action) field, a session token (dialog token) field, a BA parameter set (BA parameter set) field, a BA timeout (BA timeout) field, an extension field, a BA starting sequence control (BA starting sequence control) field, and a link identification set field (optional). The BA parameter set includes a service identifier of a target service type, and the BA timeout field includes a timeout duration of a timeout timer of the BA session. The link identification set field includes link identifications of the links in the first multi-link device in the target link. The link identification of a link in the first multi-link device may be the link MAC address of the link in the first multi-link device, or an identification represented by letters, numbers, characters, or a combination thereof. For explanation and functions of other fields in the BA session establishment request, reference may be made to the relevant description of ADDBA request frame in 802.11n, and details are not repeated herein in this embodiment of the present application.

Optionally, the BA session establishment response includes a timeout duration of a timeout timer of the BA session. For example, fig. 10 is a schematic frame structure diagram of a BA session establishment response according to an embodiment of the present application. As shown in fig. 10, the BA session establishment response includes a category (category) field, a BA action (BA action) field, a session token (dialog token) field, a status code (status code) field, a BA parameter set (BA parameter set) field, a BA timeout (BA timeout) field, an extension field, and a link identification set field (optional). The BA parameter set comprises a service identifier of a target service type, and the BA overtime field comprises the overtime duration of an overtime timer of the BA session. The link identification set field includes link identifications of the links in the second multi-link device in the target link. The link identification of a link in the second multi-link device may be the link MAC address of the link in the second multi-link device, or an identification represented by letters, numbers, characters, or a combination thereof. For explanation and functions of other fields in the BA session establishment response, reference may be made to the related description of the ADDBA response frame in 802.11n, and details of the embodiment of the present application are not repeated herein.

Optionally, the BA session establishment request shown in fig. 9 and/or the BA session establishment response shown in fig. 10 may not include the link id set field, where the BA session establishment request is used to request that a BA session be established on all links between the first multi-link device and the second multi-link device, and the BA session establishment response is used to indicate whether the BA session be established successfully on all links between the first multi-link device and the second multi-link device. In this case, the target link includes all links between the first multi-link device and the second multi-link device.

In a second alternative embodiment of the present application, the BA session of each of the target links individually uses one timeout timer, that is, the first multi-link device sets a timing period for the BA session of each of the target links separately. Then, in step 705 above, the first multi-link device maintains the BA session on the first link, which may be: the first multi-link device only maintains the BA session on the first link, and the implementation process comprises the following steps: the first multi-link device resets a timeout timer for the BA session for the first link.

Optionally, the first multilink device first starts the timeout timer for the BA session of the first link, either upon receiving a BA session setup response from the second multilink device or upon receiving a first BA message from the second multilink device over the first link. For example, the first multi-link device transmits data on the first link after receiving a BA session setup response from the second multi-link device, and the first multi-link device starts a timeout timer for the BA session for the first link when a BA message is received from the second multi-link device on the first link.

For example, the first multi-link device includes AP1 and AP2, the second multi-link device includes STA1 and STA2, and the target links include link 1 between AP1 and STA1 and link 2 between AP2 and STA 2. Fig. 11 is a schematic diagram of a BA session performed between multiple link devices according to an embodiment of the present application. As shown in fig. 11, after the first multi-link device establishes a BA session with the second multi-link device on the target link, the AP1 transmits data 1 on link 1. When the AP1 receives a BA message 1 from the STA1 on link 1, the first multi-link device starts a timeout timer for the BA session on link 1. The AP1 then sends data 2 on link 1, and when the AP1 receives the BA message 2 on link 1, the first multi-link device resets the timeout timer for the BA session on that link 1. Wherein, the arrow points to indicate the timing sequence, and the timeout duration of the timeout timer of the BA session of link 1 is T1.

Optionally, the BA session establishment request includes multiple sets of per-link parameters corresponding to multiple links in the target link, where each set of per-link parameters includes a link identifier of the corresponding link and a timeout duration of a timeout timer of the BA session of the link. The BA session establishment request also includes a set of multi-link generic parameters. For example, fig. 12 is a frame structure diagram of another BA session establishment request provided in the embodiment of the present application. As shown in fig. 12, the BA session establishment request includes a set of multi-link generic parameters and a plurality of sets of per-link parameters, the plurality of sets of per-link parameters including 1-n per-link parameters, n being an integer greater than 1. The multi-link general parameters include a category (category) field, a BA action (BA action) field, and a session token (dialog token) field, and each set of per-link parameters includes a link identification field, a BA parameter set (BA parameter set) field, a BA timeout (BA timeout) field, an extension field, and a BA starting sequence control (BA starting sequence control) field. The link identifier field includes a link identifier of a link in the first multi-link device corresponding to the group of per-link parameters, for example, per-link parameter 1 includes link identifier 1. The BA parameter set comprises a service identification of a target service type, and the BA timeout field comprises the timeout duration of a timeout timer of a BA session of the link. The link identification may be a link MAC address of the link in the first multi-link device, or the link identification may also be represented by letters, numbers, characters, or a combination thereof. The link identification of a link in the first multi-link device may be the link MAC address of the link in the first multi-link device, or an identification represented by letters, numbers, characters, or a combination thereof. For explanation and functions of other fields in the BA session establishment request, reference may be made to the relevant description of ADDBA request frame in 802.11n, and details are not repeated herein in this embodiment of the present application.

Optionally, the BA session establishment response includes multiple sets of per-link parameters corresponding to multiple links in the target link, where each set of per-link parameters includes a link identifier of the corresponding link and a timeout duration of a timeout timer of the BA session of the link. The BA session setup response also includes a set of multi-link generic parameters. For example, fig. 13 is a frame structure diagram of another BA session establishment response provided in the embodiment of the present application. As shown in fig. 13, the BA session setup response includes a set of multi-link generic parameters and a plurality of sets of per-link parameters, the plurality of sets of per-link parameters including 1-n per-link parameters, n being an integer greater than 1. The multi-link general parameters include a category (category) field, a BA action (BA action) field, a session token (dialog token) field, and a status code (status code) field, and each set of per-link parameters includes a link identification field, a BA parameter set (BA parameter set) field, a BA timeout (BA timeout) field, and an extension field. Wherein the status code field indicates success of establishment of the BA session or indicates a reason for refusing to establish the BA session. The link identification field includes a link identification of a link in the second multi-link device corresponding to the group of per-link parameters, for example, 1 per-link parameter includes 1 link identification. The BA parameter set comprises a service identification of a target service type, and the BA timeout field comprises the timeout duration of a timeout timer of a BA session of the link. The link identification of a link in the second multi-link device may be the link MAC address of the link in the second multi-link device, or an identification represented by letters, numbers, characters, or a combination thereof. For explanation and functions of other fields in the BA session establishment response, reference may be made to the related description of the ADDBA response frame in 802.11n, and details of the embodiment of the present application are not repeated herein.

In this embodiment of the present application, when a BA session on one of the target links is overtime, the first multilink device may disable (disable) the link in the target link; when the BA session on all of the target links times out, the first multi-link device may delete (tear down) the BA session. The first multi-link device may disable a link, i.e., the first multi-link device may stop the BA session on the link (i.e., no longer transmitting data on the link).

Two possible implementations of the first multi-link device to disable the link in the target link are described below:

in a first possible implementation manner, with reference to the second optional embodiment described above, the target link further includes a second link, where the second link is any link other than the first link. When the first multi-link device does not receive a BA message from the second multi-link device on the second link within the timing period of the BA session for the second link, the first multi-link device sends a link update message to the second multi-link device, the link update message indicating that the second link is disabled in the target link. Optionally, the link update message includes a link identification of the second link and a link status parameter, the link status parameter indicating the disabling. The link update message may also include a service identification of the target service type.

For example, with continued reference to fig. 11, after the first multi-link device establishes a BA session with the second multi-link device on the target link, the AP2 transmits data 3 on link 2. When the AP2 receives a BA message 3 from the STA2 on link 2, the first multi-link device starts a timeout timer for the BA session for link 2. The AP2 then transmits data 4 on link 2, and the first multi-link device de-enables link 2 when the AP2 does not receive a BA message 4 for data 4 on link 2 within the timing period of the BA session for link 2. Wherein the arrow points to indicate the timing sequence, and the timeout duration of the timeout timer of the BA session of link 2 is T2.

Optionally, the implementation process, when the first multilink device does not receive the BA message from the second multilink device on the second link within the timing period corresponding to the second link, that the first multilink device sends the link update message to the second multilink device includes: and when the continuous loss times of the BA messages from the second multi-link equipment on the second link reach a target threshold value in the timing period corresponding to the second link, the first multi-link equipment sends the link updating message to the second multi-link equipment.

Optionally, when the first multilink device does not reach the target threshold value for the consecutive loss times of the BA messages from the second multilink device on the second link within the timing period corresponding to the second link, the first multilink device resets the timeout timer of the BA session of the second link at the end time of the timing period corresponding to the second link, and clears the consecutive loss times.

Optionally, the BA session establishment request includes the target threshold value. If the multi-link general parameter of the BA session establishment request may include a target threshold value, all links in the target link use the same target threshold value; or, each group of link parameters of the BA session establishment request may include a target threshold, and each link in the target link adopts a target threshold.

The first multi-link device loses the BA message from the second multi-link device on the second link, which means that the first multi-link device does not receive the BA message for the data sent to the second multi-link device through the second link on the target link, and the first multi-link device needs to retransmit the data at this time. The first multi-link device sends data to the second multi-link device on the second link, and the second multi-link device may reply to the first multi-link device with a BA message for the data on the second link or other links in the target link. When the first multi-link device receives a BA message for the data on any of the target links, the first multi-link device determines that the BA message for the data is not lost on the second link, at which time the first multi-link device need not retransmit the data.

In this embodiment of the present application, a transmission mode in which data is sent on one link and a BA message is replied on another link may be implemented between multiple link devices.

In a second possible implementation manner, with reference to the first optional embodiment or the second optional embodiment, the target link further includes a third link, where the third link is any link other than the first link. And when the first multilink equipment is in the target duration and the continuous loss times of the BA messages from the second multilink equipment on the third link reach a target threshold value, the first multilink equipment sends a link updating message to the second multilink equipment, wherein the link updating message is used for indicating that the third link is disabled in the target link. Optionally, the link update message includes a link identification of the third link and a link status parameter, the link status parameter indicating the disabling. The link update message may also include a service identification of the target service type.

Optionally, the BA session establishment request includes the target threshold, and when the second possible implementation manner is combined with the second optional embodiment, the setting manner of the target threshold may refer to the related description in the first possible implementation manner, and this embodiment of the present application is not described herein again. The target duration may be equal to a timeout duration of a timeout timer of a BA session of the third link.

For example, after the first multilink device sends data to the second multilink device on the third link, if a BA message for the data from the second multilink device is not received on the target link within a certain time period (usually, a short frame interval), the first multilink device adds a continuous loss record corresponding to the third link, where the continuous loss record includes the number of continuous losses after the BA message is lost and a loss timestamp corresponding to the lost BA message, and the loss timestamp may be a time when the first multilink device determines that the BA message is lost. If the time length from the loss timestamp in one continuous loss record to the current timestamp is greater than the target time length, the first multilink equipment deletes the continuous loss record; if the first multi-link device receives any data frame on the third link, or receives a BA message for data sent to the second multi-link device through the third link on any link in the target link, the first multi-link device clears all the continuous loss records corresponding to the third link.

Optionally, the link update message includes a reason code, and the reason code indicates that the BA message replies to a timeout (BA timeout for short).

For example, fig. 14 is a schematic diagram of a frame structure of a link update message according to an embodiment of the present application. As shown in fig. 14, the link update message includes: a category (category) field, a BA action (BA action) field, a session token (dialog token) field, a link identification field, and a link state parameter field. The category field is used to indicate the message type, which may be a BA session negotiation. The BA action field is used to indicate a frame type, which may be a custom block acknowledgement update (ADDBA update) frame, or alternatively, an ADDBA request frame, i.e., a link update message reuse ADDBA request frame. The session token field is used to identify the transmission.

Optionally, the link identifier field includes a link identifier of a link to be updated in the target link; the link state parameter field indicates the state of the link to be updated. For example, the link state parameter field indicates whether the link to be updated is enabled or disabled. When the link state parameter field indicates that the link to be updated is disabled, the link state parameter field also indicates a reason for the disabling. For example, when the value of the link state parameter field is 0, link enable is indicated; when the value of the link state parameter field is 1, indicating that the reason for link de-enabling is BA overtime; when the value of the link state parameter field is 2, it indicates that the reason for link de-enablement is other reasons.

Or, the link identification field includes link identifications of all links in the target link; the link state parameter field indicates the state of each link. For example, the target link includes link 1, link 2 and link 3, and the link identifier field includes link identifier 1 of link 1, link identifier 2 of link 2 and link identifier 3 of link 3 in turn; the link status parameter field uses different bits to indicate the status of the three links, for example, the link status parameter field is denoted as 012, which indicates link 1 is enabled, link 2 is disabled because of BA timeout, and link 3 is disabled because of other reasons.

Two cases of the first multilink device deleting a BA session are explained below:

in a first case, with reference to the first possible implementation manner and/or the second possible implementation manner, when all links in the target link are disabled, the first multi-link device sends a BA session deletion request to the second multi-link device, where the BA session deletion request is used to request deletion of the BA session.

When the last link in the target link reaches the disable condition, the first multi-link device may directly send a BA session deletion request to the second multi-link device, or the first multi-link device may send a link update message indicating to disable the link to the second multi-link device first, and then send the BA session deletion request to the second multi-link device.

Optionally, the first multi-link device is an access point multi-link device, and the second multi-link device is a non-access point multi-link device. When all links in the target link are disabled, the first multilink device may further determine whether a link exists in the target link that is disabled due to not a BA message reply timeout.

When a fourth link exists in the target link that is not disabled due to a BA message reply timeout, the first multi-link device sends a link activation request to the second multi-link device, the link activation request requesting activation of the fourth link. The first multilink device enables the fourth link when the first multilink device receives a link activation success response from the second multilink device for the link activation request. Optionally, the link activation request comprises a link identification of the fourth link and a link status parameter, the link status parameter indicating enablement. The frame structure of the link activation request may refer to a frame structure of a link update message, which is not described herein again in this embodiment of the present application.

For example, when the fourth link is disabled due to the fourth link being in a dormant state, that is, the APs and/or STAs at both ends of the fourth link are in the dormant state, the first multi-link device may send a wake up packet to the second multi-link device on the fourth link (that is, the link activation request may be a wake up packet) to wake up the STA connected to the fourth link, so as to activate the fourth link.

For another example, when the fourth link is disabled due to the fourth link not having Simultaneous Transmit and Receive (STR) capability, the first multi-link device may send a link activation request on any link with the second multi-link device to activate the fourth link. The link activation request may indicate that all links of the target link other than the fourth link are disabled.

In the first case, when all the links in the target link are disabled and there is no link in the target link that is not disabled due to the timeout of BA message reply, or when all the links in the target link are disabled and the first multi-link device determines that the fourth link that is not disabled due to the timeout of BA message reply fails to be activated, the first multi-link device sends the BA session deletion request to the second multi-link device.

Optionally, when the first multi-link device does not receive a link activation response to the link activation request for requesting activation of the fourth link or receives a link activation failure response to the link activation request for requesting activation of the fourth link, the first multi-link device determines that the fourth link activation fails.

In a second case, in combination with the first optional embodiment, when the first multi-link device does not receive a BA message from the second multi-link device on all links in the target link within the timing period of the BA session, the first multi-link device sends a BA session deletion request to the second multi-link device, where the BA session deletion request is used to request deletion of the BA session.

Optionally, the second multilink device sends an acknowledgement frame to the first multilink device after receiving the BA session deletion request from the first multilink device.

Alternatively, the BA session delete request may also be referred to as a delete block acknowledgement (delete BA) frame. The BA session delete request includes a reason code indicating that the BA message reply has timed out.

The sequence of steps of the management method for the BA session in the WLAN provided in the embodiment of the present application may be appropriately adjusted, and the steps may also be correspondingly increased or decreased according to the situation. Any method that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application is covered by the protection scope of the present application, and thus the detailed description thereof is omitted.

To sum up, in the management method for a BA session provided in this embodiment of the present application, two multilink devices establish a BA session on multiple links, and when a first multilink device receives a BA message from a second multilink device on one link, the first multilink device maintains the BA session on the link, that is, when the first multilink device receives a BA message from the second multilink device on any one link, the BA session between the first multilink device and the second multilink device remains active, thereby implementing effective maintenance on the BA session, and thus enabling reliability of data transmission to be higher. In addition, the first multi-link device can also enable or disable each link in a plurality of links for establishing the BA session independently, so that the effective maintenance of the BA session on each link is realized, and the flexibility of BA session management is improved.

Fig. 15 is a schematic structural diagram of a first multi-link device in a wireless local area network according to an embodiment of the present application. The first multi-link device may be, for example, multi-link device 101 or multi-link device 102 in fig. 1. As shown in fig. 15, the first multilink device 150 includes:

a sending module 1501, configured to send a BA session establishment request to a second multi-link device, where the first multi-link device is associated with the second multi-link device, and the BA session establishment request is used to request establishment of a BA session on a target link, where the target link includes multiple links between the first multi-link device and the second multi-link device.

A receiving module 1502 is configured to receive a BA session establishment response from the second multi-link device to the BA session establishment request.

The sending module 1501 is further configured to send data to the second multi-link device on the target link when the BA session establishment response indicates that the BA session establishment is successful.

A processing module 1503, configured to maintain a BA session on the first link when a BA message is received on the first link from the second multi-link device, where the first link is any one of the target links.

Optionally, the BA session establishment request includes a service identifier of the target service type, and the BA session establishment request is used to request establishment of a BA session of the target service type on the target link.

In a first possible implementation, the processing module 1503 is configured to maintain BA sessions for all links in the target link.

Optionally, the processing module 1503 is configured to reset a timeout timer of the BA session.

Optionally, the BA session establishment request comprises a timeout duration of a timeout timer of the BA session.

In a second possible implementation, the processing module 1503 is configured to reset a timeout timer of the BA session of the first link.

Optionally, the BA session establishment request includes multiple sets of per-link parameters corresponding to multiple links in the target link, where each set of per-link parameters includes a link identifier of the corresponding link and an timeout duration of a timeout timer of the BA session of the link.

With reference to the second possible implementation manner, the target link further includes a second link, and the sending module 1501 is further configured to: and when the first multi-link device does not receive a BA message from the second multi-link device on the second link within the timing period of the BA session of the second link, sending a link update message to the second multi-link device, wherein the link update message is used for indicating that the second link is disabled in the target link.

Optionally, the sending module 1501 is configured to: and when the continuous loss times of the BA messages from the second multi-link equipment on the second link reach a target threshold value in the timing period of the first multi-link equipment, the first multi-link equipment sends a link updating message to the second multi-link equipment.

Optionally, the processing module 1503 is further configured to: when the continuous loss times of the BA messages from the second multi-link equipment on the second link in the timing period of the first multi-link equipment do not reach the target threshold value, resetting the overtime timer of the BA session of the second link at the end time of the timing period, and clearing the continuous loss times.

With reference to the first possible implementation manner or the second possible implementation manner, the target link further includes a third link, and the sending module 1501 is further configured to: and when the first multilink equipment is in the target duration and the continuous loss times of the BA messages from the second multilink equipment on the third link reach a target threshold value, the first multilink equipment sends a link updating message to the second multilink equipment, wherein the link updating message is used for indicating that the third link is enabled in the target link.

Optionally, the target duration is equal to a timeout duration of a timeout timer of a BA session of the third link.

Optionally, the sending module 1501 is further configured to: and when all the links in the target link are disabled, sending a BA session deletion request to the second multi-link equipment, wherein the BA session deletion request is used for requesting to delete the BA session.

Optionally, the first multilink device is an access point multilink device, the second multilink device is a non-access point multilink device, and when all links in the target link are disabled. The sending module 1501 is further configured to send a link activation request to the second multi-link device when there is a fourth link in the target link that is not disabled due to the BA message reply timeout, where the link activation request is used to request activation of the fourth link. The processing module 1503 is further configured to enable the fourth link when the first multi-link device receives a link activation success response from the second multi-link device to the link activation request. The sending module 1501 is further configured to send a BA session deletion request to the second multi-link device when the first multi-link device determines that the fourth link activation fails.

In combination with the first implementable manner, the sending module 1501 is further configured to: and when the first multi-link device does not receive the BA message from the second multi-link device on all links in the target link within the timing period of the BA session, sending a BA session deletion request to the second multi-link device, wherein the BA session deletion request is used for requesting to delete the BA session.

To sum up, according to the first multilink device provided in the embodiment of the present application, a BA session is established on multiple links with the second multilink device, and when the first multilink device receives a BA message from the second multilink device on one link, the first multilink device maintains the BA session on the link, that is, when the first multilink device receives a BA message from the second multilink device on any one link, the BA session between the first multilink device and the second multilink device remains active, so that the BA session is effectively maintained, and thus, the reliability of data transmission is high. In addition, the first multi-link device can also enable or disable each link in a plurality of links for establishing the BA session independently, so that the effective maintenance of the BA session on each link is realized, and the flexibility of BA session management is improved.

With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

An embodiment of the present application provides a first multi-link device in a wireless local area network, including: a processor and a transceiver;

the processor is configured to invoke a computer program, and implement, in cooperation with the transceiver, the action performed by the first multilink device in the foregoing method embodiment.

For example, fig. 16 is a block diagram of a multi-link device provided in an embodiment of the present application. As shown in fig. 16, the multilink device 160 includes: a processor 1601 and a transceiver 1602. The transceiver 1602 is configured to perform transceiving actions of the first multi-link device or the second multi-link device in the above-described method embodiments under the control of the processor 1601.

Optionally, the multi-link device 160 also includes a memory 1603, a communication bus 1604, and a communication interface 1605.

The processor 1601 may be a general processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the present solution.

The communication bus 1604 may include a path for passing information between the aforementioned components.

Memory 1603 may be, but is not limited to, a read-only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an electrically erasable programmable read-only Memory (EEPROM), a compact disc read-only Memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a magnetic disk or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 1603 may be self-contained and coupled to the processor 1601 via a communication bus 1604. Memory 1603 may also be integrated with the processor 1601.

The memory 1603 is used for storing program codes for executing the scheme of the application and is controlled by the processor 1601 to execute. Processor 1601 is used to execute program code stored in memory 1603. One or more software modules may be included in the program code. The one or more software modules may be software modules provided in the embodiment shown in fig. 15.

Communication interface 1605, using transceiver 1602, is used for communicating with other devices or communication networks, such as ethernet, Radio Access Network (RAN), WLAN, etc.

For one embodiment, an access point device may include multiple processors. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

An embodiment of the present application further provides a system for managing a BA session in a wireless local area network, including: a first and a second multilink device associated. The first multi-link device is the multi-link device shown in fig. 15, and can implement the actions performed by the first multi-link device in the above method embodiments; the second multi-link device is capable of performing the actions performed by the second multi-link device in the above-described method embodiments.

An embodiment of the present application further provides a computer storage medium, where instructions are stored on the computer storage medium, and when the instructions are executed by a processor of a computer device, the instructions implement the actions performed by the first multi-link device or the second multi-link device in the foregoing method embodiments.

It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.

In the embodiments of the present application, the terms "first", "second", and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.

The term "and/or" in this application is only one kind of association relationship describing the associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

The above description is only exemplary of the present application and is not intended to limit the present application, and any modifications, equivalents, improvements, etc. made within the spirit and principles of the present application are intended to be included within the scope of the present application.

Claims

1. A method for managing a block acknowledgement, BA, session in a wireless local area network, the method comprising:

a first multi-link device sending a BA session establishment request to a second multi-link device, the first multi-link device being associated with the second multi-link device, the BA session establishment request requesting establishment of a BA session on a target link, the target link comprising a plurality of links between the first multi-link device and the second multi-link device;

the first multi-link device receiving a BA session establishment response from the second multi-link device to the BA session establishment request;

when the BA session establishment response indicates that the BA session is successfully established, the first multi-link device sends data to the second multi-link device on the target link;

when a BA message is received on a first link from the second multi-link device, the first multi-link device maintains the BA session on the first link, the first link being any one of the target links.

2. The method of claim 1, wherein the BA session establishment request comprises a service identifier of a target service type, and wherein the BA session establishment request is for requesting establishment of a BA session of the target service type on the target link.

3. The method of claim 1 or 2, wherein the first multi-link device maintaining the BA session on the first link comprises:

the first multi-link device maintains the BA sessions for all of the target links.

4. The method of claim 3, wherein the first multi-link device maintaining the BA sessions for all of the target links comprises:

the first multi-link device resets a timeout timer for the BA session.

5. The method of claim 4, wherein the BA session establishment request comprises a timeout duration of a timeout timer of the BA session.

6. The method of claim 1 or 2, wherein the first multi-link device maintaining the BA session on the first link comprises:

the first multi-link device resets a timeout timer for the BA session for the first link.

7. The method of claim 6, wherein the BA session establishment request comprises multiple sets of per-link parameters corresponding to multiple ones of the target links, each set of per-link parameters comprising a link identifier of the corresponding link and a timeout duration of a BA session for the link.

8. The method of claim 6 or 7, wherein the target link further comprises a second link, and wherein the method further comprises:

when the first multi-link device does not receive a BA message from the second multi-link device on the second link within the timing period of the BA session of the second link, the first multi-link device sends a link update message to the second multi-link device, wherein the link update message is used for indicating that the second link is disabled in the target link.

9. The method of claim 8, wherein the first multi-link device sending a link update message to the second multi-link device when the first multi-link device does not receive a BA message on the second link within the timing period of the second link comprises:

and when the continuous loss times of the BA messages from the second multi-link equipment on the second link reach a target threshold value in the timing period, the first multi-link equipment sends the link updating message to the second multi-link equipment.

10. The method of claim 9, further comprising:

when the continuous loss times of the BA messages from the second multi-link equipment on the second link in the timing period of the first multi-link equipment do not reach the target threshold value, the first multi-link equipment resets the timeout timer of the BA session of the second link at the end time of the timing period and clears the continuous loss times.

11. The method according to any one of claims 1 to 7, wherein the target link further comprises a third link, the method further comprising:

when the first multilink device is in a target duration, the continuous loss times of BA messages from the second multilink device on the third link reach a target threshold value, the first multilink device sends a link update message to the second multilink device, and the link update message is used for indicating that the third link is disabled in the target link.

12. The method of claim 11, wherein the target duration is equal to a timeout duration of a timeout timer of the BA session for the third link.

13. Method according to any of claims 9 to 12, wherein said BA session establishment request comprises said target threshold value.

14. A method according to any of claims 8 to 13, wherein said link update message includes a cause code indicating that a BA message reply has timed out.

15. The method according to claim 8 or 11, characterized in that the method further comprises:

and when all the links in the target link are disabled, the first multi-link equipment sends a BA session deletion request to the second multi-link equipment, wherein the BA session deletion request is used for requesting to delete the BA session.

16. The method of claim 15, wherein the first multi-link device is an access point multi-link device and the second multi-link device is a non-access point multi-link device, and wherein when all of the target links are disabled, the method further comprises:

when a fourth link which is not disabled due to BA message reply timeout exists in the target link, the first multi-link device sends a link activation request to the second multi-link device, wherein the link activation request is used for requesting to activate the fourth link;

when the first multi-link device receives a link activation success response from the second multi-link device for the link activation request, the first multi-link device enables the fourth link;

the first multi-link device sending a BA session deletion request to the second multi-link device, including:

and when the first multi-link equipment determines that the fourth link activation fails, the first multi-link equipment sends the BA session deletion request to the second multi-link equipment.

17. The method according to any one of claims 3 to 5, further comprising:

when the first multi-link device does not receive a BA message from the second multi-link device on all links in the target link within the timing period of the BA session, the first multi-link device sends a BA session deletion request to the second multi-link device, where the BA session deletion request is used to request deletion of the BA session.

18. Method according to any of claims 15 to 17, wherein said BA session delete request comprises a cause code indicating a BA message reply timeout.

19. A first multi-link device in a wireless local area network, the first multi-link device comprising:

a sending module, configured to send a block acknowledgement, BA, session establishment request to a second multi-link device, the first multi-link device being associated with the second multi-link device, the BA session establishment request being used to request establishment of a BA session on a target link, the target link comprising multiple links between the first multi-link device and the second multi-link device;

a receiving module, configured to receive a BA session establishment response from the second multi-link device to the BA session establishment request;

the sending module is further configured to send data to the second multilink device on the target link when the BA session establishment response indicates that the BA session is successfully established;

a processing module, configured to maintain the BA session on a first link when a BA message is received on the first link from the second multi-link device, where the first link is any one of the target links.

20. The first multilink device of claim 19, wherein said BA session establishment request includes a service identification of a target traffic type, and wherein said BA session establishment request requests establishment of a BA session of said target traffic type over said target link.

21. The first multilink device of claim 19 or 20, wherein said processing module is configured to:

maintaining the BA sessions for all of the target links.

22. The first multilink device of claim 21, wherein said processing module is configured to:

resetting a timeout timer for the BA session.

23. The first multilink device of claim 22, wherein said BA session establishment request comprises a timeout duration of a timeout timer of said BA session.

24. The first multilink device of claim 19 or 20, wherein said processing module is configured to:

resetting a timeout timer for the BA session for the first link.

25. The first multilink device of claim 24, wherein said BA session establishment request includes a plurality of sets of per-link parameters corresponding to a plurality of links of said target link, each set of said per-link parameters including a link identification of the corresponding link and a timeout duration of a BA session timeout timer for said link.

26. The first multilink device of claim 24 or 25, wherein the target link further includes a second link, and wherein the sending module is further configured to:

when the first multi-link device does not receive a BA message from the second multi-link device on the second link within the timing period of the BA session of the second link, sending a link update message to the second multi-link device, wherein the link update message is used for indicating that the second link is disabled in the target link.

27. The first multilink device of claim 26, wherein said transmitting module is configured to:

28. The first multilink device of claim 27, wherein said processing module is further configured to:

when the continuous loss times of the BA messages from the second multi-link equipment on the second link in the timing period of the first multi-link equipment do not reach the target threshold value, resetting an overtime timer of the BA session of the second link at the end time of the timing period, and clearing the continuous loss times.

29. The first multilink device of any one of claims 19 to 25, wherein the target link further includes a third link, and wherein the sending module is further configured to:

30. The first multilink device of claim 29, wherein said target duration is equal to a timeout duration of a timeout timer of said BA session of said third link.

31. The first multilink device of any of claims 27 to 30, wherein said BA session establishment request includes said target threshold value.

32. A first multilink device according to any one of claims 26 to 31, wherein said link update message includes a cause code indicating a BA message reply timeout.

33. The first multilink device of claim 26 or 29, wherein said transmitting module is further configured to:

and when all the links in the target link are disabled, sending a BA session deletion request to the second multi-link equipment, wherein the BA session deletion request is used for requesting to delete the BA session.

34. The first multi-link device of claim 33, wherein the first multi-link device is an access point multi-link device and the second multi-link device is a non-access point multi-link device, when all links in the target link are disabled;

the sending module is further configured to send a link activation request to the second multi-link device when a fourth link that is not disabled due to timeout of BA message reply exists in the target link, where the link activation request is used to request activation of the fourth link;

the processing module is further configured to enable the fourth link when the first multi-link device receives a link activation success response from the second multi-link device to the link activation request;

the sending module is further configured to send the BA session deletion request to the second multilink device when the first multilink device determines that the fourth link activation fails.

35. The first multilink device of any one of claims 21 to 23, wherein said transmitting module is further configured to:

and when the first multi-link equipment does not receive the BA message from the second multi-link equipment on all links in the target link within the timing period of the BA session, sending a BA session deletion request to the second multi-link equipment, wherein the BA session deletion request is used for requesting to delete the BA session.

36. A first multilink device according to any of claims 33 to 35, wherein said BA session delete request includes a cause code indicating a BA message reply timeout.

37. A first multi-link device in a wireless local area network, comprising: a processor and a transceiver;

the processor for invoking a computer program to implement the method of any of claims 1 to 18 in cooperation with the transceiver.