WO2023070377A1

WO2023070377A1 - Block acknowledgment agreement deletion method and apparatus, and multi-link device and storage medium

Info

Publication number: WO2023070377A1
Application number: PCT/CN2021/126756
Authority: WO
Inventors: 徐彦超; 余庆华; 王泷
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-10-27
Filing date: 2021-10-27
Publication date: 2023-05-04
Also published as: CN118120336A

Abstract

The present application relates to the technical field of communications. Disclosed are a block acknowledgment (BA) agreement deletion method and apparatus, and a multi-link device (MLD) and a storage medium. The method is executed by a first MLD, wherein a BA agreement is established between the first MLD and a second MLD. The method comprises: after sending a DELBA frame to a second MLD, waiting for a first time length; and after the first time length ends, deleting a BA agreement. The technical solution provided in the embodiments of the present application can prevent the situation where when a first MLD deletes a BA agreement in a certain link, a second MLD sends data to the first MLD by means of other links, and thus the utilization rate of air interface resources is ensured.

Description

Block confirmation session deletion method, device, multi-link device and storage medium

technical field

The embodiments of the present application relate to the field of communication technologies, and in particular to a method and device for deleting a block acknowledgment session, a multi-link device, and a storage medium.

Background technique

In the communication standard, the function that can support multiple links (Multiple Links) is defined, and the device that supports the multi-link function is a multi-link device (Multi-Link Device, MLD).

Between two MLDs, a block acknowledgment (BlockAck, BA) session (Agreement) can be established, and data exchange under the same BA session can be performed on multiple links between the two MLDs. The MLD that initiates the establishment of a BA session is called the BA Originator, and the MLD that accepts the establishment of the BA session is called the BA Recipient. One party can delete the BA session corresponding to both parties by sending a delete BA session (DELBA) frame to the other party.

When the BA receiver sends a DELBA frame to the BA initiator through a link to delete the corresponding BA session, the BA initiator may be sending data under the BA session on other links. At this time, due to the BA The receiving side has deleted the resources of the BA session on the local side by sending the DELBA frame, and the BA receiving side will not be able to correctly process the data sent by the BA initiator and discard the data.

Contents of the invention

Embodiments of the present application provide a method and device for deleting a block acknowledgment session, a multi-link device, and a storage medium. Described technical scheme is as follows:

According to an aspect of an embodiment of the present application, a method for deleting a block acknowledgment session is provided, the method is executed by a first MLD, and a BA session is established between the first MLD and the second MLD, and the method includes:

Waiting for a first length of time after sending a DELBA frame to the second MLD;

After the first length of time expires, the BA session is deleted.

sending a delete BA session request frame to the second MLD, where the delete BA session request frame is used to request deletion of the BA session;

receiving the delete BA session response frame sent by the second MLD;

Based on the delete BA session response frame, determine whether to delete the BA session.

According to an aspect of an embodiment of the present application, a method for deleting a block confirmation session is provided, the method is executed by a first MLD, a BA session is established between the first MLD and a second MLD, and the first MLD is The BA acceptor, the second MLD is a BA initiator, and the method includes:

If there is no data under the BA session sent by the second MLD on links other than the first link, send a DELBA frame to the second MLD on the first link, and Delete the BA session.

The first MLD is not allowed to send DELBA frames, and the BA session is deleted.

According to an aspect of an embodiment of the present application, a method for deleting a block acknowledgment session is provided, the method is executed by a second MLD, and a BA session is established between the second MLD and the first MLD, and the method includes:

receiving the DELBA frame sent by the first MLD;

Wherein, the first MLD waits for a first time length after sending the DELBA frame, and deletes the BA session after the first time length ends.

receiving a delete BA session request frame sent by the first MLD, where the delete BA session request frame is used to request deletion of the BA session;

Sending a delete BA session response frame to the first MLD, where the delete BA session response frame is used for the first MLD to determine whether to delete the BA session.

According to an aspect of an embodiment of the present application, a method for deleting a block acknowledgment session is provided, the method is executed by a second MLD, a BA session is established between the second MLD and the first MLD, and the first MLD is The BA acceptor, the second MLD is a BA initiator, and the method includes:

When the first MLD ensures that there is no data under the BA session sent by the second MLD on links other than the first link, receive the first link on the first link DELBA frame sent by MLD.

According to an aspect of the embodiment of the present application, there is provided a device for deleting a block acknowledgment session, the device establishes a BA session with the second multi-link device MLD, and the device includes: a waiting module and a session deleting module;

The waiting module is configured to wait for a first length of time after sending a DELBA frame to the second MLD;

The session deletion module is configured to delete the BA session after the first time period ends.

According to an aspect of the embodiment of the present application, a device for deleting a block confirmation session is provided. A BA session is established between the device and the second MLD, and the device includes: a request frame sending module, a response frame receiving module, and a session deletion module;

The request frame sending module is configured to send a delete BA session request frame to the second MLD, and the delete BA session request frame is used to request to delete the BA session;

The response frame receiving module is configured to receive the delete BA session response frame sent by the second MLD;

The session deletion module is configured to determine whether to delete the BA session based on the delete BA session response frame.

According to an aspect of an embodiment of the present application, a device for deleting a block confirmation session is provided, a BA session is established between the device and a second MLD, the device is a BA acceptor, and the second MLD is a BA initiator , the device includes: a session deletion module;

The session deletion module is configured to, in the case that there is no data under the BA session sent by the second MLD on other links than the first link, send the The second MLD sends a DELBA frame and deletes the BA session.

The session deletion module is configured to not allow the device to send DELBA frames, and delete the BA session.

According to an aspect of the embodiment of the present application, a device for deleting a block acknowledgment session is provided, a BA session is established between the device and the first MLD, and the device includes: a deletion frame receiving module;

The deletion frame receiving module is configured to receive the DELBA frame sent by the first MLD;

According to an aspect of the embodiment of the present application, a block acknowledgment session deletion device is provided, a BA session is established between the device and the first MLD, and the device includes: a request frame receiving module and a response frame sending module;

The request frame receiving module is configured to receive a delete BA session request frame sent by the first MLD, and the delete BA session request frame is used to request deletion of the BA session;

The response frame sending module is configured to send a delete BA session response frame to the first MLD, and the delete BA session response frame is used for the first MLD to determine whether to delete the BA session.

According to an aspect of the embodiment of the present application, a device for deleting a block confirmation session is provided, a BA session is established between the device and a first MLD, the first MLD is a BA acceptor, and the device is a BA initiator , the device includes: a deletion frame receiving module;

The deletion frame receiving module is configured to, when the first MLD ensures that there is no data under the BA session sent by the second MLD on links other than the first link, The delete BA session DELBA frame sent by the first MLD is received on a link.

According to an aspect of an embodiment of the present application, a first MLD is provided, a BA session is established between the first MLD and a second MLD, and the first MLD includes a processor;

The processor is configured to wait for a first length of time after sending a DELBA frame to the second MLD;

The processor is configured to delete the BA session after the first time period ends.

According to an aspect of an embodiment of the present application, a first MLD is provided, a BA session is established between the first MLD and a second MLD, and the first MLD includes a transceiver and a processor;

The transceiver is configured to send a delete BA session request frame to the second MLD, where the delete BA session request frame is used to request deletion of the BA session;

The transceiver is configured to receive a delete BA session response frame sent by the second MLD;

The processor is configured to determine whether to delete the BA session based on the delete BA session response frame.

According to an aspect of an embodiment of the present application, a first MLD is provided, a BA session is established between the first MLD and a second MLD, the first MLD is a BA acceptor, and the second MLD is a BA an initiator, the first MLD includes a processor;

The processor is configured to, in the case that there is no data under the BA session sent by the second MLD on other links than the first link, send the message to the second MLD on the first link The second MLD sends a DELBA frame and deletes the BA session.

The processor is configured to not allow the first MLD to send DELBA frames, and delete the BA session.

According to an aspect of an embodiment of the present application, a second MLD is provided, a BA session is established between the second MLD and the first MLD, and the second MLD includes a transceiver;

The transceiver is configured to receive the DELBA frame sent by the first MLD;

The transceiver is configured to receive a delete BA session request frame sent by the first MLD, where the delete BA session request frame is used to request deletion of the BA session;

The transceiver is configured to send a delete BA session response frame to the first MLD, where the delete BA session response frame is used for the first MLD to determine whether to delete the BA session.

According to an aspect of an embodiment of the present application, a second MLD is provided, a BA session is established between the second MLD and the first MLD, the first MLD is a BA receiver, and the second MLD is a BA an initiator, the second MLD includes a transceiver;

The transceiver is configured to, when the first MLD ensures that there is no data under the BA session sent by the second MLD on links other than the first link, on the first link Receive the DELBA frame sent by the first MLD on the road.

According to an aspect of the embodiments of the present application, a computer-readable storage medium is provided, and a computer program is stored in the storage medium, and the computer program is used for execution by a processor, so as to implement the above method for deleting a block confirmation session.

According to an aspect of an embodiment of the present application, a chip is provided, the chip includes a programmable logic circuit and/or program instructions, and when the chip is running, is used to implement the above method for deleting a block confirmation session.

According to an aspect of the embodiments of the present application, a computer program product or computer program is provided, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and a processor reads from the The computer-readable storage medium reads and executes the computer instructions, so as to realize the above method for deleting a block confirmation session.

The technical solutions provided in the embodiments of the present application can bring the following beneficial effects:

In a multi-link scenario, after a link sends a DELBA frame to the second MLD, the first MLD waits for the first time period, and deletes the link between the first MLD and the second MLD only after the first time period ends. For the established BA session, if the second MLD sends data to the first MLD through other links within the first period of time, since the first MLD has not deleted the BA session, it can still process the data correctly, thereby ensuring the air interface resource utilization.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings that need to be used in the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can also be obtained based on these drawings without creative effort.

FIG. 1 is a schematic diagram of a wireless local area network provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a multi-link function provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of a multi-link function provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of establishing a BA session provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of deleting a BA session provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of deleting a BA session provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of deleting a BA session provided by an embodiment of the present application;

FIG. 8 is a flowchart of a method for deleting a block confirmation session provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of deleting a BA session provided by an embodiment of the present application;

Fig. 10 is a flowchart of a method for deleting a block confirmation session provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of deleting a BA session provided by an embodiment of the present application;

FIG. 12 is a schematic diagram of deleting a BA session provided by an embodiment of the present application;

FIG. 13 is a schematic diagram of deleting a BA session provided by an embodiment of the present application;

Fig. 14 is a flowchart of a method for deleting a block confirmation session provided by an embodiment of the present application;

Fig. 15 is a schematic diagram of deleting a BA session provided by an embodiment of the present application;

FIG. 16 is a schematic diagram of deleting a BA session provided by an embodiment of the present application;

Fig. 17 is a flowchart of a method for deleting a block confirmation session provided by an embodiment of the present application;

Fig. 18 is a block diagram of a device for deleting a block confirmation session provided by an embodiment of the present application;

Fig. 19 is a block diagram of an apparatus for deleting a block confirmation session provided by an embodiment of the present application;

Fig. 20 is a block diagram of a device for deleting a block confirmation session provided by an embodiment of the present application;

Fig. 21 is a block diagram of a device for deleting a block confirmation session provided by an embodiment of the present application;

Fig. 22 is a block diagram of a device for deleting a block confirmation session provided by an embodiment of the present application;

Fig. 23 is a block diagram of a device for deleting a block confirmation session provided by an embodiment of the present application;

Fig. 24 is a block diagram of a device for deleting a block confirmation session provided by an embodiment of the present application;

Fig. 25 is a schematic structural diagram of a multi-link device provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution and advantages of the present application clearer, the implementation manners of the present application will be further described in detail below in conjunction with the accompanying drawings.

The network architecture and business scenarios described in the embodiments of the present application are for more clearly illustrating the technical solutions of the embodiments of the present application, and do not constitute limitations on the technical solutions provided by the embodiments of the present application. The evolution of the technology and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

Please refer to FIG. 1, which shows a block diagram of a wireless local area network provided by an exemplary embodiment of the present application. The wireless local area network may include: a station (Station, STA) MLD 10 and an access point (Access Point, AP) MLD 20.

STAMLD 10 contains one or more logical entity STAs, and STAs can be wireless communication chips, wireless sensors or wireless communication terminals. For example, mobile phones supporting wireless fidelity (Wireless Fidelity, WiFi) communication functions, tablet computers supporting WiFi communication functions, set-top boxes supporting WiFi communication functions, smart TVs supporting WiFi communication functions, smart wearable devices supporting WiFi communication functions, A vehicle communication device supporting the WiFi communication function and a computer supporting the WiFi communication function.

AP MLD 20 contains one or more logical entities AP. Among them, AP can be the access point for mobile users to enter the wired network. It is mainly deployed in homes, buildings, and campuses. The typical coverage radius is tens of meters to hundreds of meters. Of course, it can also be deployed outdoors. The AP is equivalent to a bridge connecting the wired network and the wireless network. Its main function is to connect various wireless network clients together, and then connect the wireless network to the Ethernet. Specifically, the AP may be a terminal device or a network device with a WiFi chip.

In the embodiment of this application, a multi-link is established between the STA MLD 10 and the AP MLD 20. Exemplarily, link 1 and link 2 exist between STA MLD 10 and AP MLD 20, STA MLD 10 includes: STA1 and STA2, AP MLD 20 includes: AP1 and AP2, STA1 and STA2 communicate with AP1 and AP2 respectively Transmission, that is, AP1 and AP2 are peer-to-peer logical entities of STA1 and STA2 respectively, and their corresponding links are link 1 and link 2 respectively.

In the embodiment of this application, both STA MLD 10 and AP MLD 20 support the 802.11 standard. It can be understood that the STA MLD 10 and the AP MLD 20 in the embodiment of the present application can also support the evolution standard of the 802.11 standard, and can also support other communication standards. For example, it supports 802.11be and subsequent versions.

Before introducing the technical solution of this application, some technical knowledge involved in this application will be introduced.

In related standards, functions that can support multiple links (Multiple Links) are defined. According to the definition of both ends of the communication in the standard, one is STA MLD and the other is AP MLD. The STA MLD and AP MLD that have established multi-links can take advantage of multi-links to send and receive data on multiple links to achieve high throughput/low latency and other advantages.

In related standards, MAC Protocol Data Unit (MPDU) can be received using all allowed links, which is beneficial to reduce delay. The MPDU packets under the Aggregated MPDU (Aggregated MPDU, AMPDU) BA session belonging to the same traffic identifier (Traffic Identifier, TID) can be transmitted on any link.

As shown in Figure 2 and Figure 3, two links are established between STA MLD and AP MLD: link 1 and link 2, AMPDU1 is transmitted on link 1, and AMPDU2, AMPDU1 and AMPDU2 are transmitted on link 2 MPDUs in correspond to BA sessions under the same TID.

In related standards, for establishing a BA session between two MLD devices, the process of establishing a session can only be performed on a certain link between the two MLD devices, that is, establishing a BA session request (ADDBA Request) frame and establishing a BA session response (ADDBA Response) frame interaction process.

As shown in Figure 4, there are two links between AP MLD and STA MLD: link 1 and link 2. When AP MLD expects to establish a BA session with STA MLD on a certain TID, AP MLD can choose to send an ADDBA request frame to STA MLD on link 1. If STA MLD accepts the request to establish a BA session, it can choose to Link 1 replies an ADDBA response frame to AP MLD, and carries the BA session establishment success field in this frame. When this TID can be used on both link 1 and link 2, the BA session on this TID is established between AP MLD and STA MLD, and the BA session can be sent on both links later AMPDUs. Among them, the AP MLD that initiates the establishment of the BA session is called the BA initiator, and the STA MLD that accepts the establishment of the BA session is called the BA acceptor.

In related standards, a BA session timeout (Block Ack Timeout Value) will be negotiated during the establishment of a BA session. For the BA receiver side, if it does not receive MPDU/AMPDU/Block Ack Request (BAR) and other frames under the corresponding BA session from the BA initiator within the duration of the BA session timeout time, the BA accepts Party can tear down (tear down) this BA session. The BA receiver can delete the corresponding BA session by sending a DELBA frame to the BA initiator. Correspondingly, after the STA MLD sends the DELBA frame and deletes the BA session, it will also delete the resources corresponding to the BA session in the STA MLD. The above process is shown in Figure 5.

In related standards, when the BA receiver deletes the BA session, it will also delete the corresponding BA session resources, so if the BA initiator sends data to the BA receiver in the form of AMPDU under the BA session, The BA receiver will not be able to process these AMPDUs correctly.

As shown in Figure 6, when the STA as the BA receiver sends a DELBA frame to the AP, the STA will delete the corresponding BA session, after which the AP cannot continue to send AMPDUs under the deleted BA session to the STA , otherwise, the STA will discard the data because it deleted the BA session.

Under the relevant mechanism, the AMPDU sent by the BA initiator can be sent on any suitable link, and the DELBA frame sent by the BA receiver can also be sent on any suitable link. In this way, in a multi-link scenario, the following situation will occur: As shown in Figure 7, for a BA session on a certain TID, the AP MLD acts as the BA initiator, and the STA MLD acts as the BA receiver. When the AP MLD and the STA MLD On all links corresponding to this BA session, AP MLD does not send MPDU/AMPDU/BAR under this BA session within the time period of the negotiated BA session timeout period, and STA MLD will consider that this can be deleted at this time. The BA session thus sends the DELBA frame on link 1, but at this time the AP MLD just sends the AMPDU under the BA session on the link 2, but since the STA MLD sends the DELBA frame directly, the corresponding BA session Delete, this will cause STA MLD to be unable to correctly process the AMPDU sent by AP MLD, resulting in packet loss.

In order to solve the above problems, the embodiments of the present application provide the following technical solutions. In the following, the technical solution of the present application will be described through several embodiments.

Please refer to FIG. 8 , which shows a flowchart of a method for deleting a block confirmation session provided by an embodiment of the present application. The method can be applied to the wireless local area network shown in FIG. 1 . The method may include the steps of:

Step 802: After the first MLD sends the DELBA frame to the second MLD, it waits for a first length of time.

Wherein, a BA session is established between the first MLD and the second MLD. Exemplarily, the first MLD is the BA initiator, and the second MLD is the BA acceptor; or, the first MLD is the BA acceptor, and the second MLD is the BA initiator. Exemplarily, the first MLD is AP MLD, and the second MLD is STA MLD; or, the first MLD is STA MLD, and the second MLD is AP MLD.

The first MLD is the device that is expected to delete the BA session. The first MLD sends a DELBA frame to the second MLD, where the DELBA frame is used to indicate that the first MLD will delete the BA session.

In one embodiment of the present application, before the first MLD sends the DELBA frame to the second MLD, the BA acceptor does not receive the MPDU/ AMPDU/BAR frame.

The first time length is a period of time that the first MLD needs to wait between the time point when the DELBA frame is sent and the time point when the BA session is deleted.

In an embodiment of the present application, the first time length is determined through a process of establishing a BA session. The establishment process of the BA session is shown in FIG. 4 , and details are not described here.

Exemplarily, the ADDBA request frame carries the first time length suggested by the BA initiator, and the ADDBA response frame carries the BA acceptor's consent response, thus, the first time length is determined through the establishment process of the BA session. Exemplarily, the ADDBA request frame carries a first time length suggested by the BA initiator, and the ADDBA response frame carries the BA acceptor's consent response and another different first time length suggested by the BA acceptor, thereby , determine the first time length through the establishment process of the BA session.

In an embodiment of the present application, the first time length is determined by the first MLD and indicated by a DELBA frame.

Exemplarily, the first MLD autonomously determines the first time length, and notifies the second MLD of the value of the first time length through a DELBA frame.

In an embodiment of the present application, the first time length is the maximum time of a physical layer protocol data unit (Physical Protocol Data Unit, PPDU).

Wherein, the PPDU maximum time refers to the maximum time allowed for a PPDU to be transmitted. Exemplarily, the maximum time of PPDU is set to 5.484ms.

Step 804: The first MLD deletes the BA session after the first time period ends.

After sending the DELBA frame to the second MLD, the first MLD waits for a first time period, and deletes the BA session established between the first MLD and the second MLD after the first time period ends. Exemplarily, deleting a BA session refers to: deleting corresponding resources under the BA session for correctly receiving/processing data from the peer MLD.

Exemplarily, the first MLD of the BA receiver sends a DELBA frame to the second MLD of the BA initiator, and waits for a first time length, and deletes the BA session after the first time length expires. If the first MLD of the BA recipient sends data to the second MLD of the BA initiator within the first length of time, the second MLD of the BA initiator can correctly receive/process the data based on the undeleted BA session.

Exemplarily, the first MLD of the BA initiator sends a DELBA frame to the second MLD of the BA receiver, and waits for a first time length, and deletes the BA session after the first time length expires. When the first MLD of the BA initiator sends the DELBA frame to the second MLD of the BA receiver, it ensures that there will be no simultaneous data transmission on this side. Therefore, there will be no second MLD of the BA receiver After the BA session is deleted, the data sent by the first MLD of the BA initiator is still received.

In one embodiment of the present application, before step 804, the following steps are also included:

When the first MLD is the receiver of BA and the second MLD is the initiator of BA, the second MLD sends data to the first MLD; the first MLD receives the data sent by the second MLD while waiting for the first length of time ; Wherein, the end time point of the data interaction sequence is not later than the time point when the first MLD deletes the BA session.

Wherein, the data interaction sequence includes: data, and a data response frame. Exemplarily, the data exchange sequence includes: an AMPDU, and a BA frame corresponding to the AMPDU.

That is, after receiving the DELBA frame, the second MLD device of the BA initiator can continue to send the corresponding BA session information to the first MLD while the first MLD device of the BA receiver is waiting to delete the BA session. AMPDU, and the end time point of the interaction sequence of the sent AMPDU will not exceed the time point when the first MLD deletes the BA session.

In the case that the first MLD is the receiver of the BA and the second MLD is the initiator of the BA, the second MLD does not actively send data to the first MLD.

That is, after receiving the DELBA frame, the second MLD device of the BA initiator will not actively send the AMPDU under the corresponding BA session to the first MLD device of the BA receiver again.

To sum up, in the technical solution provided by this embodiment, in a multi-link scenario, the first MLD waits for the first length of time after sending a DELBA frame to the second MLD on a certain link, and after the end of the first time length , the BA session established between the first MLD and the second MLD will be deleted. If within the first time period, the second MLD sends data to the first MLD through other links, since the first MLD has not deleted the BA session , so the data can still be processed correctly, thereby ensuring the utilization of air interface resources.

The embodiment corresponding to the above-mentioned FIG. 8 is exemplarily described with reference to FIG. 9 .

STA MLD, as the BA recipient, will not delete the corresponding BA session immediately after it sends DELBA to AP MLD on link 1. STA MLD will delete the corresponding BA session after waiting for a period of time (that is, the first time length) in the subsequent delay. During this delay waiting period, even if the AP MLD still sends AMPDUs under the corresponding BA session on link 2, since the BA session on the STA MLD side still exists, the STA MLD can still process these AMPDUs correctly.

Please refer to FIG. 10 , which shows a flowchart of a method for deleting a block confirmation session provided by an embodiment of the present application. The method can be applied to the wireless local area network shown in FIG. 1 . The method may include the steps of:

Step 1002: the first MLD sends a delete BA session request frame to the second MLD, and the delete BA session request frame is used to request to delete the BA session.

The first MLD is the device that is expected to delete the BA session. The first MLD sends a delete BA session request frame to the second MLD, where the delete BA session request frame is used to request to delete the BA session.

In one embodiment of the present application, before the first MLD sends a delete BA session request frame to the second MLD, the BA acceptor does not receive the corresponding BA session download frame from the BA initiator within the BA session timeout period. MPDU/AMPDU/BAR frames.

Step 1004: The second MLD receives the delete BA session request frame sent by the first MLD.

Step 1006: the second MLD sends a delete BA session response frame to the first MLD, and the delete BA session response frame is used for the first MLD to determine whether to delete the BA session.

Step 1008: the first MLD receives the delete BA session response frame sent by the second MLD.

Step 1010: The first MLD determines whether to delete the BA session based on the delete BA session response frame.

That is, if the first MLD deletes the BA session, the first MLD needs to perform an interactive negotiation process with the second MLD, and the frames exchanged during the interactive negotiation process include the above-mentioned delete BA session request frame and delete BA session response frame. Exemplarily, deleting a BA session refers to: deleting corresponding resources under the BA session for correctly receiving/processing data from the peer MLD. Exemplarily, the first MLD of the BA acceptor sends a delete BA session request frame to the second MLD of the BA initiator, and receives a delete BA session response frame replied by the second MLD of the BA initiator, and the first MLD of the BA acceptor Based on the delete BA session response frame, it is determined whether to delete the BA session. If the first MLD of the BA receiver requests to delete the BA session by deleting the BA session request frame, and the second MLD of the BA initiator is sending data to the first MLD of the BA receiver, then the second MLD of the BA initiator deletes the BA session. The session response frame notifies the first MLD of the BA recipient, so the second MLD of the BA initiator does not delete the BA session, and thus correctly receives/processes data based on the undeleted BA session.

Exemplarily, the first MLD of the BA initiator sends a delete BA session request frame to the second MLD of the BA acceptor, and receives a delete BA session response frame replied by the second MLD of the BA acceptor, and the first MLD of the BA initiator Based on the delete BA session response frame, it is determined whether to delete the BA session. When the first MLD of the BA initiator sends a delete BA session request frame to the second MLD of the BA receiver, it ensures that there will be no simultaneous data transmission on this side. Therefore, there will be no second MLD of the BA receiver. The second MLD still receives the data sent by the first MLD of the BA initiator after the BA session is deleted.

In an embodiment of the present application, step 1006 is replaced by: when the second MLD considers that the BA session can be deleted at the time point when the request frame for deleting the BA session is received, the second MLD sends the first delete message to the first MLD. A BA session response frame; wherein, the first delete BA session response frame is used to indicate that the BA session is allowed to be deleted.

Correspondingly, step 1008 is alternatively implemented as follows: the first MLD receives the first delete BA session response frame sent by the second MLD, and the first delete BA session response frame is at the point in time when the second MLD considers that the delete BA session request frame is received The frame sent by the second MLD device can be deleted in the case of the BA session.

Correspondingly, step 1010 is alternatively implemented as: in response to the first delete BA session response frame being used to indicate that the BA session is allowed to be deleted, the first MLD deletes the BA session.

That is, if the second MLD device under the BA session thinks that the BA session can be deleted at the moment when it receives the delete BA session request frame, the second MLD can send a first delete BA session response frame to the first MLD, It also carries information indicating that the first MLD device that sends the delete BA session request frame can be allowed to delete the BA session.

In an embodiment of the present application, step 1006 is replaced by: when the second MLD considers that the BA session cannot be deleted at the time point when the request frame for deleting the BA session is received, the second MLD immediately sends the first MLD Two delete BA session response frames; wherein, the second delete BA session response frame is used to indicate that the BA session is not allowed to be deleted; or, to indicate to delete the BA session after waiting for a second length of time; or, to indicate to delete the BA session first time point.

Correspondingly, step 1008 is alternatively implemented as: the first MLD receives the second delete BA session response frame sent by the second MLD, and the second delete BA session response frame is at the point in time when the second MLD considers that the delete BA session request frame is received Frame sent immediately by the second MLD device in case the BA session cannot be deleted.

Correspondingly, step 1010 is alternatively implemented as: in response to the second delete BA session response frame being used to indicate that the BA session is not allowed to be deleted, the first MLD does not delete the BA session; or, in response to the second delete BA session response frame being used to indicate Deleting the BA session after waiting for a second length of time, the first MLD deletes the BA session after waiting for a second length of time; or, in response to the first time point when the second delete BA session response frame is used to indicate the deletion of the BA session, the first MLD in The BA session is deleted at the first time point.

That is, if the second MLD device under the BA session receives the request frame for deleting the BA session, it thinks that the BA session cannot be deleted at present, for example, the second MLD device is sending the corresponding BA session message on other links. AMPDU, the second MLD may send a second delete BA session response frame to the first MLD, and carry information indicating that the first MLD at the opposite end is not allowed to delete the corresponding BA session, or carry the time point or It is how long to delete the corresponding BA session information.

In an embodiment of the present application, step 1006 is replaced by: when the second MLD considers that the BA session cannot be deleted at the time point when the request frame for deleting the BA session is received, the second MLD sends a message to the second MLD at the second time point An MLD sends a third delete BA session response frame; wherein, the second time point is a time point when the second MLD believes that the BA session can be deleted; the third delete BA session response frame is used to indicate that the BA session is allowed to be deleted.

Correspondingly, step 1008 is alternatively implemented as: the first MLD receives the third delete BA session response frame sent by the second MLD, and the third delete BA session response frame is at the point in time when the second MLD considers that the delete BA session request frame is received In the case that the BA session cannot be deleted, the frame is sent by the second MLD device at the second time point, and the second time point is a time point at which the second MLD considers that the BA session can be deleted.

Correspondingly, step 1010 is alternatively implemented as: in response to the third delete BA session response frame being used to indicate that the BA session is allowed to be deleted, the second MLD deletes the BA session.

That is, if the second MLD device under the BA session receives the request frame for deleting the BA session, it thinks that the BA session cannot be deleted at present, for example, the second MLD device is sending the corresponding BA session message on other links. AMPDU, the second MLD will not reply immediately, but will send a third delete BA session to the first MLD device until the second MLD device can allow the first MLD device at the opposite end to delete the BA session at a certain point in time A response frame, carrying information indicating that the first MLD device sending the delete BA session request frame can be allowed to delete the BA session.

To sum up, in the technical solution provided by this embodiment, in a multi-link scenario, if the first MLD wants to delete the BA session, the first MLD needs to perform an interactive negotiation process with the second MLD, and the interactive negotiation process The interacted frames include delete BA session request frame and delete BA session response frame. After the interactive negotiation process is completed, the first MLD will delete the BA session. Through the interactive negotiation process, it is avoided that the first MLD deletes the BA session on a certain link. During the BA session, the second MLD is sending data to the first MLD through other links, so as to ensure the utilization of air interface resources.

The embodiment corresponding to the above-mentioned FIG. 10 is exemplarily described with reference to FIG. 11 .

STA MLD is the BA recipient, after it sends a DELBA request frame (that is, deletes the BA session request frame) on link 1, because AP MLD has an AMPDU under the corresponding BA session sent to STA MLD on link 2, AP The MLD chooses to reply a DELBA response frame (that is, delete the BA session response frame) on the link 1, and carry information that the STA MLD is not allowed to delete the BA session in this frame. Since the BA session of STA MLD still exists, STA MLD can still correctly process the AMPDU on link 2.

The embodiment corresponding to the above-mentioned FIG. 10 is exemplarily described with reference to FIG. 12 .

STA MLD is the BA recipient, after it sends a DELBA request frame (that is, deletes the BA session request frame) on link 1, because AP MLD has an AMPDU under the corresponding BA session sent to STA MLD on link 2, AP MLD chooses to reply a DELBA response frame on link 1 (that is, delete the BA session response frame), and carry information in this frame indicating the time point when STA MLD can delete the BA session or how long it takes before deleting the BA session . Since the BA session of STA MLD still exists, STA MLD can still correctly process the AMPDU on link 2.

The embodiment corresponding to the above-mentioned FIG. 10 is exemplarily described with reference to FIG. 13 .

STA MLD is the BA recipient, after it sends a DELBA request frame (that is, deletes the BA session request frame) on link 1, because AP MLD has an AMPDU under the corresponding BA session sent to STA MLD on link 2, AP MLD chooses not to reply a DELBA response frame on link 1 (ie delete BA session response frame). Since the BA session of STA MLD still exists, STA MLD can still correctly process the AMPDU on link 2. Until the AP MLD considers that the STA MLD can be allowed to delete the BA session, the AP MLD replies with a DELBA response frame on link 1, and carries information indicating that the STA MLD can delete the BA session in the frame.

Please refer to FIG. 14 , which shows a flowchart of a method for deleting a block confirmation session provided by an embodiment of the present application. The method can be applied to the wireless local area network shown in FIG. 1 . The method may include the steps of:

Step 1402: If there is no data under the BA session sent by the second MLD on other links other than the first link, the first MLD sends a DELBA frame to the second MLD on the first link, and deletes the BA session.

A BA session is established between the first MLD and the second MLD, the first MLD is a device expected to delete the BA session, the first MLD is a BA receiver, and the second MLD is a BA initiator.

That is, under the BA session established between MLD devices, when the first MLD of the BA receiver needs to delete the BA session actively, before the first MLD device sends a DELBA frame on a link, it needs to ensure that other links There will be no AMPDU under the corresponding BA session sent from the second MLD of the BA initiator. Exemplarily, deleting a BA session refers to: deleting corresponding resources under the BA session for correctly receiving/processing data from the peer MLD.

In one embodiment of the present application, before the first MLD sends a DELBA frame to the second MLD, the first MLD of the BA receiver does not receive any information from the second MLD of the BA initiator within the duration of the BA session timeout period. To the MPDU/AMPDU/BAR frame under the corresponding BA session.

In an embodiment of the present application, in order to ensure that there is no data under the BA session sent by the second MLD on links other than the first link, before step 1402, the first MLD will also perform the following steps:

The first MLD keeps the state of devices on other links in the doze state; or, the first MLD uses the dynamic communication identifier to link mapping (dynamic TID-to-Link mapping) function to transfer the data under the BA session Links used for interaction are limited to the first link.

Wherein, in the case that the state of a device on a link remains in a sleep state, no data transmission will be performed on this link. Therefore, when the first MLD keeps the state of devices on other links in sleep state, there will be no data under the BA session sent by the second MLD on other links other than the first link.

Exemplarily, the first MLD sends indication information to the second MLD on the link before keeping the state of the device on the link as the sleep state, and the indication information is used to inform the second MLD that the first MLD expects to The state of the devices on the link is kept in the sleep state, and after the first MLD receives the reply confirmation frame of the indication information from the second MLD, the state of the devices on the link is kept in the sleep state. Exemplarily, the indication information is carried in a power management (Power Management) field in the frame sent by the first MLD.

Wherein, the dynamic communication identifier-to-link mapping function is a function that prohibits data interaction on a link under the BA session. Therefore, when the first MLD uses the dynamic communication identifier to link mapping function to limit the links used for data interaction under the BA session to the first link, other links other than the first link will There will be no data under the BA session sent by the second MLD.

Exemplarily, the dynamic communication identifier-to-link mapping function is implemented in the following manner: the first MLD sends a communication identifier-to-link mapping request to the second MLD, and the communication identifier-to-link mapping request is used to request to limit a certain For data transmission on a link, after the first MLD receives a communication identifier-to-link mapping response from the second MLD, if the communication identifier-to-link mapping response carries information that allows data transmission on the link to be restricted, Then data interaction under the BA session will not be performed on this link.

Step 1404: the second MLD receives the delete BA session DELBA frame sent by the first MLD on the first link.

At this time, there is no data under the BA session sent by the second MLD on links other than the first link.

To sum up, in the technical solution provided by this embodiment, in a multi-link scenario, if the first MLD wants to send a DELBA frame on the first link to delete the BA session, the first MLD needs to ensure that the first link There is currently no data under the BA session sent by the second MLD on other links other than the link, so as to avoid that when the first MLD deletes the BA session on a link, the second MLD is sending to the first MLD through other links Data status, so as to ensure the utilization of air interface resources.

The embodiment corresponding to the above-mentioned FIG. 14 is exemplarily described with reference to FIG. 15 .

When the BA recipient is STA MLD, before STA MLD wants to send DELBA frame on link 1, STA MLD can keep the STA state on other links except the link sending DELBA frame as sleep (doze ) state, that is, the STA state on the link 2 is kept as a sleep state, so that the AP MLD will not send data to the STA MLD on the link 2 like this.

The embodiment corresponding to the above-mentioned FIG. 14 is exemplarily described with reference to FIG. 16 .

Before the BA recipient wants to send a DELBA frame on link 1, the BA recipient can limit the links allowed to be used for data reception under the corresponding BA session to link 1 by using the communication identifier to link mapping function superior. In this way, the BA initiator will not send the AMPDU on the corresponding BA session to the BA receiver on the link 2.

Please refer to FIG. 17 , which shows a flowchart of a method for deleting a block confirmation session provided by an embodiment of the present application. The method can be applied to the wireless local area network shown in FIG. 1 . The method may include the steps of:

Step 1702: Do not allow the first MLD to send DELBA frames, and delete the BA session.

Wherein, a BA session is established between the first MLD and the second MLD. The first MLD is the BA receiver, and the second MLD is the BA initiator. The DELBA frame is used to indicate that the sender will delete the BA session.

That is, under the BA session established between the MLD devices, the first MLD as the BA recipient is not allowed to actively send the DELBA frame, that is, the first MLD as the BA recipient is not allowed to actively delete the BA session.

Exemplarily, during the process of establishing a BA session, a BA session timeout period is negotiated, even if the first MLD of the BA receiver does not receive a corresponding message from the second MLD of the BA initiator within the duration of the BA session timeout For the MPDU/AMPDU/BAR frame under the BA session, the first MLD will not actively send the DELBA frame.

Exemplarily, in the process of establishing the BA session, a BA session timeout period is not negotiated, and the first MLD as the BA receiver is not allowed to actively send the DELBA frame after the BA session is established.

To sum up, in the technical solution provided by this embodiment, in a multi-link scenario, the first MLD as the BA receiver is not allowed to actively send DELBA frames, so as to prevent the first MLD from actively sending DELBA frames on a certain link , when the BA session is deleted, the second MLD is sending data to the first MLD through other links, so as to ensure the utilization of air interface resources.

It can be understood that the above method embodiments may be implemented individually or in combination, which is not limited in the present application.

The following are device embodiments of the present application, which can be used to implement the method embodiments of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments of the present application.

Please refer to FIG. 18 , which shows a block diagram of an apparatus for deleting a block confirmation session provided by an embodiment of the present application. The device has the function of realizing the above method example, and the function may be realized by hardware, or may be realized by executing corresponding software by hardware. The device may be the first MLD described above, or be set in the first MLD. A BA session is established between the device and the second MLD. As shown in Figure 18, the apparatus 1800 may include: a waiting module 1810 and a session deletion module 1820;

The waiting module 1810 is configured to wait for a first length of time after sending the DELBA frame to the second MLD;

The session deletion module 1820 is configured to delete the BA session after the first time period ends.

In an embodiment of the present application, the first time length is determined through the establishment process of the BA session;

or,

The first time length is determined by the device and indicated by the DELBA frame;

or,

The first time length is the maximum time of the PPDU.

In an embodiment of the present application, the device further includes: a data receiving module;

The data receiving module is configured to, when the device is a BA receiver and the second MLD is a BA initiator, receive the data sent by the second MLD while waiting for the first length of time. data;

Wherein, the end time point of the data interaction sequence is not later than the time point when the device deletes the BA session.

Please refer to FIG. 19 , which shows a block diagram of an apparatus for deleting a block confirmation session provided by an embodiment of the present application. The device has the function of realizing the above method example, and the function may be realized by hardware, or may be realized by executing corresponding software by hardware. The device may be the first MLD described above, or be set in the first MLD. A BA session is established between the device and the second MLD. As shown in Figure 19, the apparatus 1900 may include: a request frame sending module 1910, a response frame receiving module 1920 and a session deleting module 1930;

The request frame sending module 1910 is configured to send a delete BA session request frame to the second MLD, where the delete BA session request frame is used to request to delete the BA session;

The response frame receiving module 1920 is configured to receive the delete BA session response frame sent by the second MLD;

The session deletion module 1930 is configured to determine whether to delete the BA session based on the delete BA session response frame.

In an embodiment of the present application, the delete BA session response frame includes: a first delete BA session response frame, and the first delete BA session response frame When the time point of the session request frame can delete the BA session, the frame sent by the second MLD device;

The session deletion module 1930 is configured to delete the BA session in response to the first delete BA session response frame indicating that the BA session is allowed to be deleted.

In an embodiment of the present application, the delete BA session response frame includes: a second delete BA session response frame, and the second delete BA session response frame When the time point of the session request frame cannot delete the BA session, the frame sent immediately by the second MLD device;

The session deletion module 1930 is configured to respond to the second delete BA session response frame indicating that the BA session is not allowed to be deleted, and not delete the BA session;

or,

The session deletion module 1930 is configured to, in response to the second delete BA session response frame, indicate to delete the BA session after waiting for a second length of time, and delete the BA session after waiting for the second length of time;

or,

The session deletion module 1930 is configured to delete the BA session at the first time point in response to the first time point at which the second delete BA session response frame indicates deletion of the BA session.

In an embodiment of the present application, the delete BA session response frame includes: a third delete BA session response frame, and the third delete BA session response frame If the time point of the session request frame cannot delete the BA session, the frame sent by the second MLD device at the second time point, the second time point is that the second MLD thinks that the BA session can be deleted The point in time of the BA session;

The session deletion module 1930 is configured to delete the BA session in response to the third delete BA session response frame indicating that the BA session is allowed to be deleted.

Please refer to FIG. 20 , which shows a block diagram of an apparatus for deleting a block confirmation session provided by an embodiment of the present application. The device has the function of realizing the above method example, and the function may be realized by hardware, or may be realized by executing corresponding software by hardware. The device may be the first MLD described above, or be set in the first MLD. A BA session is established between the device and a second MLD, the device being a BA recipient, and the second MLD being a BA initiator. As shown in FIG. 20, the apparatus 2000 may include: a session deletion module 2010;

The session deletion module 2010 is configured to, in the case that there is no data under the BA session sent by the second MLD on other links than the first link, send The second MLD sends a DELBA frame, and deletes the BA session.

In an embodiment of the present application, the device further includes: a link confirmation module;

The link confirmation module is used to keep the state of the devices on the other links in sleep state;

or,

The link confirmation module is configured to use a dynamic communication identifier-to-link mapping function to limit the link used for data interaction under the BA session to the first link.

Please refer to FIG. 21 , which shows a block diagram of an apparatus for deleting a block confirmation session provided by an embodiment of the present application. The device has the function of realizing the above method example, and the function may be realized by hardware, or may be realized by executing corresponding software by hardware. The device may be the first MLD described above, or be set in the first MLD. A BA session is established between the device and a second MLD, the device being a BA recipient, and the second MLD being a BA initiator. As shown in Figure 21, the apparatus 2100 may include: a session deletion module 2110;

The session deletion module 2110 is configured to not allow the device to send DELBA frames, and delete the BA session.

Please refer to FIG. 22 , which shows a block diagram of an apparatus for deleting a block confirmation session provided by an embodiment of the present application. The device has the function of realizing the above method example, and the function may be realized by hardware, or may be realized by executing corresponding software by hardware. The device may be the second MLD described above, or be set in the second MLD. A BA session is established between the device and the first MLD. As shown in FIG. 22, the apparatus 2200 may include: a deletion frame receiving module 2210;

The deletion frame receiving module 2210 is configured to receive the DELBA frame sent by the first MLD;

or,

The first time length is determined by the first MLD and indicated by the DELBA frame;

or,

The first time length is the maximum time of the PPDU.

In an embodiment of the present application, the device further includes: a data sending module;

The data sending module is configured to not actively send data to the first MLD when the first MLD is a BA receiver and the device is a BA initiator;

or,

The data sending module is configured to send the data to the first MLD when the first MLD is a BA receiver and the device is a BA initiator, and the end time of the data interaction sequence The point is not later than the time point when the first MLD deletes the BA session.

Please refer to FIG. 23 , which shows a block diagram of an apparatus for deleting a block confirmation session provided by an embodiment of the present application. The device has the function of realizing the above method example, and the function may be realized by hardware, or may be realized by executing corresponding software by hardware. The device may be the second MLD described above, or be set in the second MLD. A BA session is established between the device and the first MLD. As shown in Figure 23, the device 2300 may include: a request frame receiving module 2310 and a response frame sending module 2320;

The request frame receiving module 2310 is configured to receive a delete BA session request frame sent by the first MLD, where the delete BA session request frame is used to request deletion of the BA session;

The response frame sending module 2320 is configured to send a delete BA session response frame to the first MLD, and the delete BA session response frame is used for the first MLD to determine whether to delete the BA session.

In one embodiment of the present application, the response frame sending module 2320 is configured to send the response frame to the The first MLD sends a first delete BA session response frame;

Wherein, the first delete BA session response frame is used to indicate that the BA session is allowed to be deleted.

In one embodiment of the present application, the response frame sending module 2320 is configured to immediately send the response frame to the The first MLD sends a second delete BA session response frame;

Wherein, the second delete BA session response frame is used to indicate that the BA session is not allowed to be deleted; or, used to indicate to delete the BA session after waiting for a second length of time; or, used to indicate to delete the BA session the first point in time.

In one embodiment of the present application, the response frame sending module 2320 is configured to, when the device considers that the BA session cannot be deleted at the time point when the request frame for deleting the BA session is received, at the Sending a third delete BA session response frame to the first MLD at two time points;

Wherein, the second time point is a time point when the device considers that the BA session can be deleted; the third delete BA session response frame is used to indicate that the BA session is allowed to be deleted.

Please refer to FIG. 24 , which shows a block diagram of an apparatus for deleting a block confirmation session provided by an embodiment of the present application. The device has the function of realizing the above method example, and the function may be realized by hardware, or may be realized by executing corresponding software by hardware. The device may be the second MLD described above, or be set in the second MLD. A BA session is established between the device and a first MLD, the first MLD is a BA acceptor, and the device is a BA initiator. As shown in FIG. 24, the apparatus 2400 may include: a deletion frame receiving module 2410;

The deletion frame receiving module 2410 is configured to, when the first MLD ensures that there is no data under the BA session sent by the second MLD on links other than the first link, The DELBA frame sent by the first MLD is received on the first link.

In an embodiment of the present application, the first MLD ensures that there is no data under the BA session sent by the second MLD on links other than the first link through the following steps:

The first MLD keeps the state of the devices on the other links in a sleep state;

or,

The first MLD uses a dynamic communication identifier to link mapping function to limit the links used for data interaction under the BA session to the first link.

It should be noted that when the device provided by the above embodiment realizes its functions, it only uses the division of the above-mentioned functional modules as an example for illustration. In practical applications, the above-mentioned function allocation can be completed by different functional modules according to actual needs. That is, the content structure of the device is divided into different functional modules to complete all or part of the functions described above.

Regarding the apparatus in the foregoing embodiments, the specific manner in which each module executes operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Please refer to FIG. 25 , which shows a schematic structural diagram of a multi-link device provided by an embodiment of the present application. The multi-link device may be the above-mentioned first MLD, or may be implemented as the above-mentioned second MLD. The multi-link device may include: a processor 2501 , a receiver 2502 , a transmitter 2503 , a memory 2504 and a bus 2505 .

The processor 2501 includes one or more processing cores, and the processor 2501 executes various functional applications by running software programs and modules.

The receiver 2502 and the transmitter 2503 can be realized as a transceiver 2506, and the transceiver 2506 can be a communication chip.

The memory 2504 is connected to the processor 2501 through the bus 2505 .

The memory 2504 may be used to store a computer program, and the processor 2501 is used to execute the computer program, so as to implement various steps performed by the multi-link device in the foregoing method embodiments.

In addition, the memory 2504 can be realized by any type of volatile or non-volatile storage device or their combination, and the volatile or non-volatile storage device includes but not limited to: random access memory (Random-Access Memory, RAM) And read-only memory (Read-Only Memory, ROM), erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM), electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), flash memory or other solid-state storage technologies, compact disc read-only memory (CD-ROM), high-density digital video disc (Digital Video Disc, DVD) or other optical storage, tape cartridges, tapes, disks storage or other magnetic storage devices.

Wherein, when the multi-link device is implemented as the first MLD, the processor 2501 and the transceiver 2506 involved in the embodiment of the present application can execute any of the methods shown in FIG. 8 to FIG. 9 above, and the first MLD The steps performed by the device will not be repeated here.

In a possible implementation manner, when the multi-link device is implemented as a first MLD, a BA session is established between the first MLD and the second MLD;

The processor 2501 is configured to wait for a first length of time after sending the DELBA frame to the second MLD;

The processor 2501 is configured to delete the BA session after the first time period ends.

Wherein, when the multi-link device is implemented as the first MLD, the processor 2501 and the transceiver 2506 involved in the embodiment of the present application can execute the method shown in any one of the above-mentioned Figures 10 to 13, and the first MLD The steps performed by the device will not be repeated here.

The transceiver 2506 is configured to send a delete BA session request frame to the second MLD, where the delete BA session request frame is used to request to delete the BA session;

The transceiver 2506 is configured to receive the delete BA session response frame sent by the second MLD;

The processor 2501 is configured to determine whether to delete the BA session based on the delete BA session response frame.

Wherein, when the multi-link device is implemented as the first MLD, the processor 2501 and the transceiver 2506 involved in the embodiment of the present application can execute any of the methods shown in FIG. 14 to FIG. 16 above, and the first MLD The steps performed by the device will not be repeated here.

In a possible implementation manner, when the multi-link device is implemented as a first MLD, a BA session is established between the first MLD and the second MLD, the first MLD is a BA receiver, and the second MLD 2. MLD is the initiator of BA;

The processor 2501 is configured to, when there is no data under the BA session sent by the second MLD on other links than the first link, send the The second MLD sends a DELBA frame and deletes the BA session.

Wherein, when the multi-link device is implemented as the first MLD, the processor 2501 and the transceiver 2506 involved in the embodiment of the present application may perform the steps performed by the first MLD device in the method shown in FIG. 17 above, I won't repeat them here.

The processor 2501 is configured to not allow the first MLD to send DELBA frames, and delete the BA session.

Wherein, when the multi-link device is implemented as the second MLD, the processor 2501 and the transceiver 2506 involved in the embodiment of the present application can execute the method shown in any one of the above-mentioned Fig. 8 to Fig. 9, and the second MLD The steps performed by the device will not be repeated here.

In a possible implementation manner, when the multi-link device is implemented as a second MLD, a BA session is established between the second MLD and the first MLD;

The transceiver 2506 is configured to receive the DELBA frame sent by the first MLD;

Wherein, when the multi-link device is implemented as the second MLD, the processor 2501 and the transceiver 2506 involved in the embodiment of the present application can execute any of the methods shown in FIG. 10 to FIG. 13 above, and the second MLD The steps performed by the device will not be repeated here.

The transceiver 2506 is configured to receive a delete BA session request frame sent by the first MLD, where the delete BA session request frame is used to request deletion of the BA session;

The transceiver 2506 is configured to send a delete BA session response frame to the first MLD, where the delete BA session response frame is used for the first MLD to determine whether to delete the BA session.

Wherein, when the multi-link device is implemented as the second MLD, the processor 2501 and the transceiver 2506 involved in the embodiment of the present application can execute any of the methods shown in FIGS. 14 to 16 above, and the second MLD The steps performed by the device will not be repeated here.

In a possible implementation manner, when the multi-link device is implemented as a second MLD, a BA session is established between the second MLD and the first MLD, the first MLD is a BA recipient, and the second MLD 2. MLD is the initiator of BA;

The transceiver 2506 is configured to, when the first MLD ensures that there is no data under the BA session sent by the second MLD on links other than the first link, Receive the DELBA frame sent by the first MLD on the link.

The embodiment of the present application also provides a computer-readable storage medium, where a computer program is stored in the storage medium, and the computer program is used to be executed by a processor, so as to implement the above method for deleting a block confirmation session.

Optionally, the computer-readable storage medium may include: a read-only memory (Read-Only Memory, ROM), a random-access memory (Random-Access Memory, RAM), a solid-state hard drive (Solid State Drives, SSD) or an optical disc. Wherein, the random access memory may include resistive random access memory (Resistance Random Access Memory, ReRAM) and dynamic random access memory (Dynamic Random Access Memory, DRAM).

The embodiment of the present application also provides a chip, the chip includes a programmable logic circuit and/or program instructions, and when the chip is running, it is used to implement the above method for deleting a block confirmation session.

The embodiment of the present application also provides a computer program product or computer program, the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and the processor reads from the computer-readable storage medium The medium reads and executes the computer instructions, so as to realize the above-mentioned block confirmation session deletion method.

The processor in this embodiment of the present application includes: an application specific integrated circuit (Application Specific Integrated Circuit, ASIC).

It should be understood that the "indication" mentioned in the embodiments of the present application may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct or indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated, configuration and is configuration etc.

The "plurality" mentioned herein means two or more. "And/or" describes the association relationship of associated objects, indicating that there may be three types of relationships, for example, A and/or B may indicate: A exists alone, A and B exist simultaneously, and B exists independently. The character "/" generally indicates that the contextual objects are an "or" relationship.

In addition, the numbering of the steps described herein only exemplarily shows a possible sequence of execution among the steps. In some other embodiments, the above-mentioned steps may not be executed according to the order of the numbers, such as two different numbers The steps are executed at the same time, or two steps with different numbers are executed in the reverse order as shown in the illustration, which is not limited in this embodiment of the present application.

Those skilled in the art should be aware that, in the foregoing one or more examples, the functions described in the embodiments of the present application may be implemented by hardware, software, firmware or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above are only exemplary embodiments of the application, and are not intended to limit the application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the application shall be included in the protection of the application. within range.

Claims

A block confirmation BA session deletion method, characterized in that the method is executed by a first multi-link device MLD, and a BA session is established between the first MLD and the second MLD, and the method includes:

Waiting for a first length of time after sending the delete BA session DELBA frame to the second MLD;

After the first length of time expires, the BA session is deleted.
The method according to claim 1, characterized in that,

The first time length is determined through the establishment process of the BA session;

or,

The first time length is determined by the first MLD and indicated by the DELBA frame;

or,

The first time length is a maximum time of a physical layer protocol data unit PPDU.
The method according to claim 1 or 2, characterized in that the method further comprises:

When the first MLD is a BA acceptor and the second MLD is a BA initiator, receive data sent by the second MLD while waiting for the first length of time;

Wherein, the end time point of the data interaction sequence is no later than the time point when the first MLD deletes the BA session.
A block confirmation BA session deletion method, characterized in that the method is executed by a first multi-link device MLD, and a BA session is established between the first MLD and the second MLD. The method includes:

sending a delete BA session request frame to the second MLD, where the delete BA session request frame is used to request deletion of the BA session;

receiving the delete BA session response frame sent by the second MLD;

Based on the delete BA session response frame, determine whether to delete the BA session.
The method according to claim 4, wherein the delete BA session response frame comprises: a first delete BA session response frame, and the first delete BA session response frame is considered to be received by the second MLD When the time point of deleting the BA session request frame can delete the BA session, the frame sent by the second MLD device;

The determining whether to delete the BA session based on the delete BA session response frame includes:

Deleting the BA session in response to the first delete BA session response frame being used to indicate that the BA session is allowed to be deleted.
The method according to claim 4, wherein the delete BA session response frame comprises: a second delete BA session response frame, and the second delete BA session response frame is considered to be received by the second MLD When the time point of deleting the BA session request frame cannot delete the BA session, the frame sent immediately by the second MLD device;

The determining whether to delete the BA session based on the delete BA session response frame includes:

In response to the second delete BA session response frame being used to indicate that the BA session is not allowed to be deleted, the BA session is not deleted;

or,

In response to the second delete BA session response frame being used to indicate that the BA session is deleted after waiting for a second length of time, the BA session is deleted after waiting for the second length of time;

or,

In response to the first time point at which the second delete BA session response frame is used to indicate deletion of the BA session, the BA session is deleted at the first time point.
The method according to claim 4, wherein the deletion of the BA session response frame comprises: a third deletion of the BA session response frame, and the third deletion of the BA session response frame is considered to be received by the second MLD When the time point of the delete BA session request frame cannot delete the BA session, the frame sent by the second MLD device at a second time point, the second time point is the frame that the second MLD considers A point in time at which the BA session can be deleted;

The determining whether to delete the BA session based on the delete BA session response frame includes:

Deleting the BA session in response to the third delete BA session response frame being used to indicate that the BA session is allowed to be deleted.
A block confirmation BA session deletion method, characterized in that the method is executed by a first multi-link device MLD, a BA session is established between the first MLD and a second MLD, and the first MLD is a BA accepting party, the second MLD is a BA initiator, and the method includes:

If there is no data under the BA session sent by the second MLD on other links other than the first link, send a delete BA session DELBA to the second MLD on the first link frame, and delete the BA session.
The method according to claim 8, characterized in that the method further comprises:

maintaining the state of devices on the other link in a sleep state;

or,

Using a dynamic communication identifier-to-link mapping function, the links used for data interaction under the BA session are limited to the first link.
A block confirmation BA session deletion method, characterized in that the method is executed by a first multi-link device MLD, a BA session is established between the first MLD and a second MLD, and the first MLD is a BA accepting party, the second MLD is a BA initiator, and the method includes:

The first MLD is not allowed to send a delete BA session DELBA frame, and deletes the BA session.
A block confirmation BA session deletion method, characterized in that the method is executed by a second multi-link device MLD, and a BA session is established between the second MLD and the first MLD, and the method includes:

receiving the delete BA session DELBA frame sent by the first MLD;

Wherein, the first MLD waits for a first time length after sending the DELBA frame, and deletes the BA session after the first time length ends.
The method according to claim 11, characterized in that,

The first time length is determined through the establishment process of the BA session;

or,

The first time length is determined by the first MLD and indicated by the DELBA frame;

or,

The first time length is a maximum time of a physical layer protocol data unit PPDU.
The method according to claim 11 or 12, characterized in that the method further comprises:

When the first MLD is a BA recipient and the second MLD is a BA initiator, not actively sending data to the first MLD;

or,

When the first MLD is the BA receiver and the second MLD is the BA initiator, send the data to the first MLD, and the end time point of the data interaction sequence is no later than the The time point when the first MLD deletes the BA session.
A block confirmation BA session deletion method, characterized in that the method is executed by a second multi-link device MLD, and a BA session is established between the second MLD and the first MLD, and the method includes:

receiving a delete BA session request frame sent by the first MLD, where the delete BA session request frame is used to request deletion of the BA session;

Sending a delete BA session response frame to the first MLD, where the delete BA session response frame is used for the first MLD to determine whether to delete the BA session.
The method according to claim 14, wherein the sending a delete BA session response frame to the first MLD comprises:

When the second MLD believes that the BA session can be deleted at the time point of receiving the delete BA session request frame, send a first delete BA session response frame to the first MLD;

Wherein, the first delete BA session response frame is used to indicate that the BA session is allowed to be deleted.
The method according to claim 14, wherein the sending a delete BA session response frame to the first MLD comprises:

When the second MLD believes that the BA session cannot be deleted at the time point when the request frame for deleting the BA session is received, immediately send a second delete BA session response frame to the first MLD;

Wherein, the second delete BA session response frame is used to indicate that the BA session is not allowed to be deleted; or, used to indicate to delete the BA session after waiting for a second length of time; or, used to indicate to delete the BA session the first point in time.
The method according to claim 14, wherein the sending a delete BA session response frame to the first MLD comprises:

In the case where the second MLD believes that the BA session cannot be deleted at the time point when the request frame for deleting the BA session is received, send a third delete BA session response frame to the first MLD at a second time point ;

Wherein, the second time point is a time point when the second MLD considers that the BA session can be deleted; the third delete BA session response frame is used to indicate that the BA session is allowed to be deleted.
A block confirmation BA session deletion method, characterized in that the method is executed by a second multi-link device MLD, a BA session is established between the second MLD and a first MLD, and the first MLD is a BA accepting party, the second MLD is a BA initiator, and the method includes:

When the first MLD ensures that there is no data under the BA session sent by the second MLD on links other than the first link, receive the first link on the first link Delete BA session DELBA frame sent by MLD.
The method according to claim 18, wherein the first MLD ensures that the data under the BA session sent by the second MLD does not exist on links other than the first link through the following steps:

The first MLD keeps the state of the devices on the other links in a sleep state;

or,

The first MLD uses a dynamic communication identifier-to-link mapping function to limit links used for data interaction under the BA session to the first link.
A block confirmation BA session deletion device, characterized in that a BA session is established between the device and the second multi-link device MLD, and the device includes: a waiting module and a session deletion module;

The waiting module is configured to wait for a first length of time after sending the delete BA session DELBA frame to the second MLD;

The session deletion module is configured to delete the BA session after the first time period ends.
The device according to claim 20, characterized in that,

The first time length is determined through the establishment process of the BA session;

or,

The first time length is determined by the device and indicated by the DELBA frame;

or,

The first time length is a maximum time of a physical layer protocol data unit PPDU.
The device according to claim 20 or 21, further comprising: a data receiving module;

The data receiving module is configured to, when the device is a BA receiver and the second MLD is a BA initiator, receive the data sent by the second MLD while waiting for the first length of time. data;

Wherein, the end time point of the data interaction sequence is not later than the time point when the device deletes the BA session.
A block confirmation BA session deletion device, characterized in that a BA session is established between the device and the second multi-link device MLD, and the device includes: a request frame sending module, a response frame receiving module and a session deletion module;

The request frame sending module is configured to send a delete BA session request frame to the second MLD, and the delete BA session request frame is used to request to delete the BA session;

The response frame receiving module is configured to receive the delete BA session response frame sent by the second MLD;

The session deletion module is configured to determine whether to delete the BA session based on the delete BA session response frame.
The device according to claim 23, wherein the delete BA session response frame comprises: a first delete BA session response frame, and the first delete BA session response frame is considered to be received by the second MLD When the time point of deleting the BA session request frame can delete the BA session, the frame sent by the second MLD device;

The session deletion module is configured to delete the BA session in response to the first delete BA session response frame indicating that the BA session is allowed to be deleted.
The device according to claim 23, wherein the delete BA session response frame comprises: a second delete BA session response frame, and the second delete BA session response frame is considered to be received by the second MLD When the time point of deleting the BA session request frame cannot delete the BA session, the frame sent immediately by the second MLD device;

The session deletion module is configured to indicate that the BA session is not allowed to be deleted in response to the second delete BA session response frame, and not to delete the BA session;

or,

The session deletion module is configured to, in response to the second delete BA session response frame, indicate to delete the BA session after waiting for a second length of time, and delete the BA session after waiting for the second length of time;

or,

The session deletion module is configured to delete the BA session at the first time point in response to the first time point at which the second delete BA session response frame indicates deletion of the BA session.
The device according to claim 23, wherein the delete BA session response frame comprises: a third delete BA session response frame, and the third delete BA session response frame is considered to be received by the second MLD When the time point of the delete BA session request frame cannot delete the BA session, the frame sent by the second MLD device at a second time point, the second time point is the frame that the second MLD considers A point in time at which the BA session can be deleted;

The session deletion module is configured to delete the BA session in response to the third delete BA session response frame indicating that the BA session is allowed to be deleted.
A block confirmation BA session deletion device, characterized in that a BA session is established between the device and a second multi-link device MLD, the device is a BA acceptor, and the second MLD is a BA initiator, so The device includes: a session deletion module;

The session deletion module is configured to, in the case that there is no data under the BA session sent by the second MLD on other links than the first link, send the The second MLD sends a delete BA session DELBA frame, and deletes the BA session.
The device according to claim 27, further comprising: a link confirmation module;

The link confirmation module is used to keep the state of the devices on the other links in sleep state;

or,

The link confirmation module is configured to use a dynamic communication identifier-to-link mapping function to limit the link used for data interaction under the BA session to the first link.
A block confirmation BA session deletion device, characterized in that a BA session is established between the device and a second multi-link device MLD, the device is a BA acceptor, and the second MLD is a BA initiator, so The device includes: a session deletion module;

The session deletion module is configured to not allow the device to send a delete BA session DELBA frame, and delete the BA session.
A block confirmation BA session deletion device, characterized in that a BA session is established between the device and the first multi-link device MLD, and the device includes: a deletion frame receiving module;

The deletion frame receiving module is configured to receive the deletion BA session DELBA frame sent by the first MLD;

Wherein, the first MLD waits for a first time length after sending the DELBA frame, and deletes the BA session after the first time length ends.
The device according to claim 30, characterized in that,

The first time length is determined through the establishment process of the BA session;

or,

The first time length is determined by the first MLD and indicated by the DELBA frame;

or,

The first time length is a maximum time of a physical layer protocol data unit PPDU.
The device according to claim 30 or 31, further comprising: a data sending module;

The data sending module is configured to not actively send data to the first MLD when the first MLD is a BA receiver and the device is a BA initiator;

or,

The data sending module is configured to send the data to the first MLD when the first MLD is a BA receiver and the device is a BA initiator, and the end time of the data interaction sequence The point is not later than the time point when the first MLD deletes the BA session.
A block confirmation BA session deletion device, characterized in that a BA session is established between the device and the first multi-link device MLD, and the device includes: a request frame receiving module and a response frame sending module;

The request frame receiving module is configured to receive a delete BA session request frame sent by the first MLD, and the delete BA session request frame is used to request deletion of the BA session;

The response frame sending module is configured to send a delete BA session response frame to the first MLD, and the delete BA session response frame is used for the first MLD to determine whether to delete the BA session.
The device according to claim 33, characterized in that,

The response frame sending module is configured to send a first delete BA session response to the first MLD when the device believes that the BA session can be deleted at the time point of receiving the delete BA session request frame frame;

Wherein, the first delete BA session response frame is used to indicate that the BA session is allowed to be deleted.
The device according to claim 33, characterized in that,

The response frame sending module is configured to immediately send a second delete BA to the first MLD when the device considers that the BA session cannot be deleted at the time point of receiving the delete BA session request frame session response frame;

Wherein, the second delete BA session response frame is used to indicate that the BA session is not allowed to be deleted; or, used to indicate to delete the BA session after waiting for a second length of time; or, used to indicate to delete the BA session the first point in time.
The device according to claim 33, characterized in that,

The response frame sending module is configured to send a response frame to the first MLD at a second time point when the device believes that the BA session cannot be deleted at the time point when the request frame for deleting the BA session is received. The third deletes the BA session response frame;

Wherein, the second time point is a time point when the device considers that the BA session can be deleted; the third delete BA session response frame is used to indicate that the BA session is allowed to be deleted.
A block confirmation BA session deletion device, characterized in that a BA session is established between the device and a first multi-link device MLD, the first MLD is a BA acceptor, and the device is a BA initiator, so Said device comprises: delete frame receiving module;

The deletion frame receiving module is configured to, when the first MLD ensures that there is no data under the BA session sent by the second MLD on links other than the first link, The delete BA session DELBA frame sent by the first MLD is received on a link.
The device according to claim 37, wherein the first MLD ensures that the data under the BA session sent by the second MLD does not exist on links other than the first link through the following steps:

The first MLD keeps the state of the devices on the other links in a sleep state;

or,

The first MLD uses a dynamic communication identifier-to-link mapping function to limit links used for data interaction under the BA session to the first link.
A first multi-link device MLD, characterized in that a block acknowledgment BA session is established between the first MLD and the second MLD, and the first MLD includes a processor;

The processor is configured to wait for a first length of time after sending a delete BA session DELBA frame to the second MLD;

The processor is configured to delete the BA session after the first time period ends.
A first multi-link device MLD, characterized in that a block acknowledgment BA session is established between the first MLD and the second MLD, and the first MLD includes a transceiver and a processor;

The transceiver is configured to send a delete BA session request frame to the second MLD, where the delete BA session request frame is used to request deletion of the BA session;

The transceiver is configured to receive a delete BA session response frame sent by the second MLD;

The processor is configured to determine whether to delete the BA session based on the delete BA session response frame.
A first multi-link device MLD, characterized in that a block confirmation BA session is established between the first MLD and the second MLD, the first MLD is a BA receiver, and the second MLD is a BA initiator On the other hand, the first MLD includes a processor;

The processor is configured to, in the case that there is no data under the BA session sent by the second MLD on other links than the first link, send the message to the second MLD on the first link The second MLD sends a delete BA session DELBA frame, and deletes the BA session.
A first multi-link device MLD, characterized in that a block confirmation BA session is established between the first MLD and the second MLD, the first MLD is a BA receiver, and the second MLD is a BA initiator On the other hand, the first MLD includes a processor;

The processor is configured to not allow the first MLD to send a delete BA session DELBA frame, and delete the BA session.
A second multi-link device MLD, characterized in that a block acknowledgment BA session is established between the second MLD and the first MLD, and the second MLD includes a transceiver;

The transceiver is configured to receive the delete BA session DELBA frame sent by the first MLD;

Wherein, the first MLD waits for a first time length after sending the DELBA frame, and deletes the BA session after the first time length ends.
A second multi-link device MLD, characterized in that a block acknowledgment BA session is established between the second MLD and the first MLD, and the second MLD includes a transceiver;

The transceiver is configured to receive a delete BA session request frame sent by the first MLD, where the delete BA session request frame is used to request deletion of the BA session;

The transceiver is configured to send a delete BA session response frame to the first MLD, where the delete BA session response frame is used for the first MLD to determine whether to delete the BA session.
A second multi-link device MLD, characterized in that a block confirmation BA session is established between the second MLD and the first MLD, the first MLD is a BA receiver, and the second MLD is a BA initiator side, the second MLD includes a transceiver;

The transceiver is configured to, when the first MLD ensures that there is no data under the BA session sent by the second MLD on links other than the first link, on the first link Receive the delete BA session DELBA frame sent by the first MLD on the road.
A computer-readable storage medium, wherein a computer program is stored in the storage medium, and the computer program is used to be executed by a processor to realize the block confirmation session according to any one of claims 1 to 19 delete method.
A chip, characterized in that the chip includes a programmable logic circuit and/or program instructions, which are used to implement the block confirmation session deletion method according to any one of claims 1 to 19 when the chip is running.
A computer program product or computer program, characterized in that the computer program product or computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium, and the processor reads the computer-readable storage medium from the computer-readable storage medium And execute the computer instructions to realize the block confirmation session deletion method according to any one of claims 1 to 19.