CN118120336A

CN118120336A - Method and device for deleting block acknowledgement session, multi-link equipment and storage medium

Info

Publication number: CN118120336A
Application number: CN202180103432.3A
Authority: CN
Inventors: 徐彦超; 余庆华; 王泷
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-10-27
Filing date: 2021-10-27
Publication date: 2024-05-31
Also published as: WO2023070377A1

Abstract

The application discloses a method and a device for deleting a block acknowledgement session, multi-link equipment and a storage medium, and relates to the technical field of communication. The method is performed by a first MLD, between which a BA session is established, the method comprising: waiting a first length of time after transmitting a DELBA frame to the second MLD; and deleting the BA session after the first time length is over. The technical scheme provided by the embodiment of the application can avoid the situation that the second MLD sends data to the first MLD through other links when the first MLD deletes the BA session on a certain link, thereby guaranteeing the utilization rate of air interface resources.

Description

Method and device for deleting block acknowledgement session, multi-link equipment and storage medium

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a method and a device for deleting a block acknowledgement session, a multi-link device and a storage medium.

Background

In the communication standard, a function capable of supporting Multiple Links (Multiple Links) is defined, and a device supporting the Multiple Links function is a Multiple-link device (Multi-LINK DEVICE, MLD).

Between two MLDs, a Block Ack (BA) session (Agreement) may be established, and data interaction under the same BA session may be performed on multiple links between the two MLDs. The MLD that initiates establishment of a BA session is referred to as a BA initiator (BA initiator), and the MLD that accepts establishment of a BA session is referred to as a BA Recipient (BA Recipient). One party may delete the BA session (DELBA) corresponding to the two by sending the delete BA session (DELBA) frame to the other party.

When the BA recipient sends DELBA frames to the BA initiator over one link, thereby deleting the BA session corresponding to both, the BA initiator may be sending data under the BA session on the other link, at which point, since the BA recipient has deleted the resources of the BA session on its own side by sending DELBA frames, the BA recipient will not be able to process the data sent by the BA initiator correctly, discarding the data.

Disclosure of Invention

The embodiment of the application provides a method and a device for deleting a block acknowledgement session, a multi-link device and a storage medium. The technical scheme is as follows:

According to an aspect of an embodiment of the present application, there is provided a block acknowledgement session deletion method performed by a first MLD, between which a BA session is established, the method including:

waiting a first length of time after transmitting a DELBA frame to the second MLD;

and deleting the BA session after the first time length is over.

Transmitting a BA session deletion request frame to the second MLD, the BA session deletion request frame being for requesting deletion of the BA session;

Receiving a BA session deleting response frame sent by the second MLD;

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

According to an aspect of an embodiment of the present application, there is provided a block acknowledgement session deletion method, the method being performed by a first MLD, between which a BA session is established, the first MLD being a BA recipient, and a second MLD being a BA initiator, the method comprising:

And in the case that the data under the BA session transmitted by the second MLD does not exist on other links except the first link, transmitting a DelBA frame to the second MLD on the first link and deleting 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, there is provided a block acknowledgement session deletion method performed by a second MLD, between which a BA session is established with a first MLD, the method including:

Receiving a DELBA frame transmitted by the first MLD;

the first MLD waits for a first time length after sending the DERBA frame, and deletes the BA session after the first time length is over.

Receiving a BA session deletion request frame sent by the first MLD, wherein the BA session deletion request frame is used for requesting to delete the BA session;

And sending a deletion BA session response frame to the first MLD, wherein the deletion 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, there is provided a block acknowledgement session deletion method, the method being performed by a second MLD, between which a BA session is established, and a first MLD, the first MLD being a BA recipient, the second MLD being a BA initiator, the method comprising:

And receiving the DERBA frame sent by the first MLD on the first link under the condition that the first MLD ensures that no data in the BA session sent by the second MLD exists on other links except the first link.

According to an aspect of an embodiment of the present application, there is provided a block acknowledgement session deletion apparatus having a BA session established with a second multi-link device MLD, the apparatus comprising: a waiting module and a session deleting module;

the waiting module is configured to wait a first time period after transmitting a DELBA frame to the second MLD;

And the session deleting module is used for deleting the BA session after the first time length is over.

According to an aspect of an embodiment of the present application, there is provided a block acknowledgement session deletion apparatus having a BA session established between the apparatus and a second MLD, the apparatus comprising: a request frame sending module, a response frame receiving module and a session deleting module;

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

The response frame receiving module is used for receiving a BA session deleting response frame sent by the second MLD;

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

According to an aspect of the embodiment of the present application, there is provided a block acknowledgement session deletion apparatus, between which a BA session is established with a second MLD, the apparatus being a BA recipient, the second MLD being a BA initiator, the apparatus comprising: a session deletion module;

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

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

According to an aspect of an embodiment of the present application, there is provided a block acknowledgement session deletion apparatus having a BA session established between the apparatus and a first MLD, the apparatus comprising: deleting a frame receiving module;

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

According to an aspect of an embodiment of the present application, there is provided a block acknowledgement session deletion apparatus having a BA session established between the apparatus and a first MLD, the apparatus comprising: a request frame receiving module and a response frame transmitting module;

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

the response frame sending module is configured to send a BA session deletion response frame to the first MLD, where the BA session deletion 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, there is provided a block acknowledgement session deletion apparatus, between which a BA session is established with a first MLD, the first MLD being a BA recipient, the apparatus being a BA initiator, the apparatus comprising: deleting a frame receiving module;

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

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

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

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

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

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

the transceiver is configured to receive a BA session deletion 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, there is provided a first MLD, between which a BA session is established, and a second MLD, the first MLD being a BA recipient, the second MLD being a BA initiator, the first MLD including a processor;

The processor is configured to send a DELBA frame to a second MLD on a first link and delete the BA session if there is no data in the BA session sent by the second MLD on a link other than the first link.

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

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

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

The transceiver is configured to receive a BA session deletion request frame sent by the first MLD, where the BA session deletion 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, the delete BA session response frame being used by the first MLD to determine whether to delete the BA session.

According to an aspect of an embodiment of the present application, there is provided a second MLD, between which a BA session is established with a first MLD, the first MLD being a BA recipient, the second MLD being a BA initiator, the second MLD including a transceiver;

The transceiver is configured to receive a DELBA frame sent by a first MLD on a first link if the first MLD ensures that no data in the BA session sent by the second MLD is present on links other than the first link.

According to an aspect of an embodiment of the present application, there is provided a computer-readable storage medium having stored therein a computer program for execution by a processor to implement the above-described block acknowledgment session deletion method.

According to an aspect of an embodiment of the present application, there is provided a chip including programmable logic circuits and/or program instructions for implementing the above-described block acknowledgment session deletion method when the chip is running.

According to an aspect of an embodiment of the present application, there is provided a computer program product or a computer program, the computer program product or computer program including computer instructions stored in a computer-readable storage medium, from which a processor reads and executes the computer instructions to implement the above-described block acknowledgment session deletion method.

The technical scheme provided by the embodiment of the application can bring the following beneficial effects:

In the multilink scene, after a first MLD sends a DELLBA frame to a second MLD in a certain link, waiting for a first time length, deleting the BA session established between the first MLD and the second MLD after the first time length is over, and if the second MLD sends data to the first MLD through other links in the first time length, the first MLD still can correctly process the data because the first MLD does not delete the BA session, thereby guaranteeing the utilization rate of air interface resources.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for the description of the embodiments will be briefly described below, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of a wireless lan according to an embodiment of the present application;

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

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

fig. 4 is a schematic diagram of setting up a BA session provided by one embodiment of the present application;

fig. 5 is a schematic diagram of deleting BA sessions provided by one embodiment of the present application;

fig. 6 is a schematic diagram of deleting BA sessions provided by one embodiment of the present application;

fig. 7 is a schematic diagram of deleting BA sessions provided by one embodiment of the present application;

FIG. 8 is a flow chart of a method for block acknowledgment session deletion provided by one embodiment of the present application;

Fig. 9 is a schematic diagram of deleting BA sessions provided by one embodiment of the present application;

FIG. 10 is a flow chart of a method for block acknowledgment session deletion provided by one embodiment of the present application;

fig. 11 is a schematic diagram of deleting BA sessions provided by one embodiment of the present application;

fig. 12 is a schematic diagram of deleting BA sessions provided by one embodiment of the present application;

fig. 13 is a schematic diagram of deleting BA sessions provided by one embodiment of the present application;

FIG. 14 is a flow chart of a method for block acknowledgment session deletion provided by one embodiment of the present application;

fig. 15 is a schematic diagram of deleting BA sessions provided by one embodiment of the present application;

fig. 16 is a schematic diagram of deleting BA sessions provided by one embodiment of the present application;

FIG. 17 is a flow chart of a method for block acknowledgment session deletion provided by one embodiment of the present application;

FIG. 18 is a block diagram of a block acknowledgment session deletion apparatus provided by one embodiment of the present application;

FIG. 19 is a block diagram of a block acknowledgment session deletion apparatus provided by one embodiment of the present application;

FIG. 20 is a block diagram of a block acknowledgment session deletion apparatus provided by one embodiment of the present application;

FIG. 21 is a block diagram of a block acknowledgment session deletion apparatus provided by one embodiment of the present application;

FIG. 22 is a block diagram of a block acknowledgment session deletion apparatus provided by one embodiment of the present application;

FIG. 23 is a block diagram of a block acknowledgment session deletion apparatus provided by one embodiment of the present application;

FIG. 24 is a block diagram of a block acknowledgment session deletion apparatus provided by one embodiment of the present application;

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

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the present application more apparent, the embodiments of the present application will be described in further detail with reference to the accompanying drawings.

The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided by the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided by the embodiments of the present application is applicable to similar technical problems.

Referring to fig. 1, a block diagram of a wireless local area network according to an exemplary embodiment of the present application is shown, where the wireless local area network may include: station (STA) MLD 10 and Access Point (AP) MLD 20.

STAMLD 10 includes one or more logic entities STA, which may be a wireless communication chip, a wireless sensor, or a wireless communication terminal. Such as a mobile phone supporting wireless fidelity (WIRELESS FIDELITY, WIFI) communication functions, a tablet computer supporting WiFi communication functions, a set top box supporting WiFi communication functions, a smart television supporting WiFi communication functions, a smart wearable device supporting WiFi communication functions, a vehicle communication device supporting WiFi communication functions, and a computer supporting WiFi communication functions.

The AP MLD 20 includes one or more logical entities AP. The AP may be an access point for a mobile user to enter a wired network, and is mainly deployed in a home, a building, or a campus, where a typical coverage radius is several tens meters to hundreds meters, and of course, may be deployed outdoors. The AP is equivalent to a bridge connecting a wired network and a wireless network, and mainly serves to connect each wireless network client together and then access 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 the present application, a multilink is established between the STA MLD 10 and the AP MLD 20. Illustratively, there is a link 1 and a link 2 between the STA MLD 10 and the AP MLD 20, the STA MLD 10 includes: STA1 and STA2, the AP MLD 20 includes: AP1 and AP2, STA1 and STA2 perform data transmission with AP1 and AP2, respectively, 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 the present application, both STA MLD 10 and AP MLD 20 support the 802.11 standard. It can be understood that, in the embodiment of the present application, the STA MLD 10 and the AP MLD 20 may also support the evolution standard of the 802.11 standard, and may also support other communication standards. For example, support for 802.11be, etc., and subsequent versions.

Before the technical scheme of the application is described, some technical knowledge related to the application is described.

In the relevant standards, functions are defined that can support Multiple Links (Multiple Links). One is STA MLD and one is AP MLD, as defined in the standard for both ends of communication. The multi-link STA MLD and the multi-link AP MLD can utilize the advantages of the multi-link to transmit and receive data on a plurality of links so as to achieve the advantages of high throughput, low time delay and the like.

In related standards, media access control protocol data units (MAC Protocol Data Unit, MPDUs) may be received using all allowed links, which is advantageous in reducing delay. MPDU packets under an aggregate MPDU (AGGREGATED MPDU, AMPDU) BA session belonging to the same communication identifier (TRAFFIC IDENTIFIER, TID) may be transmitted on either link.

As shown in fig. 2 and 3, two links are established between STA MLD and AP MLD: link 1 and link 2, transmitting AMPDU1 on link 1 and transmitting AMPDU2 on link 2, MPDUs in AMPDU1 and AMPDU2 corresponding to BA session under the same TID.

In the related standard, for establishing a BA session between two MLD devices, the session establishment procedure, i.e., the interaction procedure of establishing a BA session Request (ADDBA Request) frame and establishing a BA session Response (ADDBA Response) frame, may be performed only on one link between two MLD devices.

As shown in fig. 4, there are two links between the AP MLD and the STA MLD: link 1 and link 2. When the AP MLD expects to establish a BA session with the STA MLD over a TID, the AP MLD may choose to send an ADDBA request frame to the STA MLD over link 1, and if the STA MLD accepts the request to establish the BA session, may choose to reply to the AP MLD over link 1 with an ADDBA response frame and carry the BA session establishment success field in this frame. In the case where this TID is available on both link 1 and link 2, a BA session on this TID is established between the AP MLD and the STA MLD, and the AMPDUs for this BA session may be subsequently sent on both links. Wherein, the AP MLD that initiates establishment of the BA session is called a BA initiator, and the STA MLD that accepts establishment of the BA session is called a BA recipient.

In the relevant standard, a BA session timeout is negotiated during the establishment of the BA session (Block Ack Timeout Value). For the BA recipient, if it does not receive frames such as MPDU/AMPDU/block acknowledgement request (Block Ack Request, BAR) from the BA initiator for the corresponding BA session within the duration of the BA session timeout, the BA recipient may tear down (tear down) this BA session. The BA recipient may delete the BA session corresponding to the DELBA frame by sending both to the BA initiator. Correspondingly, after STA MLD transmits DELBA frames and deletes the BA session, the corresponding resources in this BA session are deleted in STA MLD. The above process is shown in fig. 5.

In the related standard, when the BA receiver deletes the BA session, the corresponding BA session resources will be deleted, so if the BA initiator sends data to the BA receiver in the form of AMPDUs under the BA session, the BA receiver will not process these AMPDUs correctly.

As shown in fig. 6, after the STA acting as the BA recipient sends a DELBA frame to the AP, the STA may drop the corresponding BA session, after which the AP may not continue to send the STA with the dropped BA session AMPDUs, otherwise, the STA may drop the data because the BA session was dropped.

Under the relevant mechanism, the AMPDU sent by the BA initiator may be sent on any suitable link, and the DELBA frame sent by the BA recipient may be sent on any suitable link. This results in the following situations in a multi-link scenario: as shown in fig. 7, for a BA session on a TID, the AP MLD acts as a BA initiator, the STA MLD acts as a BA receiver, when the AP MLD and the STA MLD do not transmit MPDUs/AMPDUs/BARs etc. under the BA session during the period of time timeout of the negotiated BA session on all links corresponding to the BA session, the STA MLD considers that the BA session can be deleted at this time to transmit DELBA frames on link 1, but at this time the AP MLD just transmits AMPDUs under the BA session on link 2, but because the STA MLD deletes the corresponding BA session directly after transmitting the DELBA frames, the STA MLD cannot process the AMPDUs transmitted by the AP MLD correctly, which causes packet loss.

In order to solve the above problems, the embodiment of the present application provides the following technical solutions. The technical scheme of the application is described and illustrated by the following examples.

Referring to fig. 8, a flowchart of a block acknowledgment session deletion method according to an embodiment of the present application is shown. The method can be applied to the wireless local area network shown in fig. 1. The method may comprise the steps of:

Step 802: the first MLD waits for a first length of time after transmitting the DELBA frame to the second MLD.

Wherein a BA session is established between the first MLD and the second MLD. Illustratively, the first MLD is a BA initiator and the second MLD is a BA recipient; or, the first MLD is a BA recipient and the second MLD is a BA initiator. Illustratively, the first MLD is an AP MLD and the second MLD is a STA MLD; or, the first MLD is STA MLD and the second MLD is AP MLD.

The first MLD is the device that expects to delete the BA session. The first MLD transmits a DELBA frame to the second MLD, the DELBA frame indicating that the first MLD is to delete the BA session.

In one embodiment of the application, the BA recipient does not receive MPDU/AMPDU/BAR frames under the corresponding BA session from the BA initiator for the duration of the BA session timeout period before the first MLD transmits the DERBA frame to the second MLD.

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

In one embodiment of the application, the first time period is determined by a BA session establishment procedure. The BA session establishment procedure is shown in fig. 4, and will not be described here.

Illustratively, the first time length suggested by the BA initiator is carried in an ADDBA request frame, and the consent reply of the BA recipient is carried in an ADDBA response frame, whereby the first time length is determined by the establishment procedure of the BA session. Illustratively, one first time length suggested by the BA initiator is carried in an ADDBA request frame, and a different first time length suggested by the BA recipient and the agreement acknowledgement of the BA recipient are carried in an ADDBA response frame, whereby the first time length is determined by the establishment procedure of the BA session.

In one embodiment of the application, the first time length is determined by the first MLD and indicated by the DELLA frame.

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

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

The maximum time of the PPDU refers to the maximum time allowed for transmission by one PPDU. Illustratively, the PPDU maximum time is set to 5.484ms.

Step 804: after the first length of time has elapsed, the first MLD deletes the BA session.

The first MLD waits for a first time period after transmitting the DELBA frame to the second MLD, and deletes the BA session established between the first MLD and the second MLD after the first time period is completed. Illustratively, deleting a BA session refers to: the corresponding resources under the BA session for correctly receiving/processing data from the peer MLD are deleted.

Illustratively, the first MLD of the BA recipient sends DELBA frames to the second MLD of the BA initiator and waits for a first length of time, after which the BA session is deleted. If the first MLD of the BA recipient sends data to the second MLD of the BA initiator for a first length of time, the second MLD of the BA initiator may correctly receive/process the data based on the undeleted BA session.

Illustratively, the first MLD of the BA initiator transmits DELBA frames to the second MLD of the BA recipient and waits for a first length of time, after which the BA session is deleted. The first MLD of the BA initiator, at the time point of transmitting the DELBA frame to the second MLD of the BA recipient, ensures that the local side does not have a data transmission behavior performed simultaneously, so that there is no case where the second MLD of the BA recipient still receives the data transmitted by the first MLD of the BA initiator after the BA session is deleted.

In one embodiment of the present application, before step 804, the method further includes the following steps:

In the case where the first MLD is a BA recipient and the second MLD is a BA initiator, the second MLD transmits data to the first MLD; the first MLD receives data sent by the second MLD in the process of waiting for the first time length; wherein the end time point of the interaction sequence of the data is no later than the time point of the first MLD deleting the BA session.

Wherein the interactive sequence of data comprises: data, and acknowledgement frames for the data. Exemplary, the interactive sequence of data includes: AMPDU, and the BA frame to which the AMPDU corresponds.

That is, after receiving the DELBA frame, the second MLD device of the BA initiator may continue to transmit the AMPDUs under the corresponding BA session to the first MLD for the period of time that the first MLD device of the BA recipient waits to drop the BA session, and the end time point of the interaction sequence of the transmitted AMPDUs may not exceed the time point when the first MLD drops the BA session.

in the case where the first MLD is a BA recipient and the second MLD is a BA initiator, the second MLD does not actively transmit data to the first MLD.

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

In summary, in the technical solution provided in this embodiment, in a multi-link scenario, after a first MLD sends a DELBA frame to a second MLD in a certain link, the first MLD waits for a first time period, and after the first time period ends, the BA session established between the first MLD and the second MLD is deleted, if in the first time period, the second MLD sends data to the first MLD through other links, and because the first MLD has not deleted the BA session, the data can still be correctly processed, thereby guaranteeing the utilization rate of air interface resources.

An exemplary embodiment corresponding to fig. 8 described above is described with reference to fig. 9.

STA MLD, acting as BA recipient, does not immediately delete the corresponding BA session after sending DELBA to AP MLD on link 1. STA MLD will delete the corresponding BA session after waiting for a period of time later (i.e., the first time period). During this delay waiting period, even though the AP MLD still has AMPDUs on link 2 that were sent in the corresponding BA session, the STA MLD can still process these AMPDUs correctly since the BA session on the STA MLD side still exists.

Referring to fig. 10, a flowchart of a block acknowledgment session deletion method according to an embodiment of the present application is shown. The method can be applied to the wireless local area network shown in fig. 1. The method may comprise the steps of:

Step 1002: the first MLD transmits a delete BA session request frame to the second MLD for requesting deletion of the BA session.

The first MLD is the device that expects to delete the BA session. The first MLD transmits a delete BA session request frame to the second MLD for requesting deletion of the BA session.

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

Step 1004: the second MLD receives the deletion 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, the delete BA session response frame being used by the first MLD to determine whether to delete the BA session.

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

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

That is, if the first MLD deletes the BA session, the first MLD needs to perform an interaction negotiation process with the second MLD, and frames interacted by the interaction negotiation process include the BA session deletion request frame and the BA session deletion response frame as described above. Illustratively, deleting a BA session refers to: the corresponding resources under the BA session for correctly receiving/processing data from the peer MLD are deleted. Illustratively, the first MLD of the BA recipient sends a delete BA session request frame to the second MLD of the BA initiator and receives a delete BA session response frame replied to the second MLD of the BA initiator, and the first MLD of the BA recipient determines whether to delete the BA session based on the delete BA session response frame. If the first MLD of the BA recipient requests to delete the BA session by deleting the BA session request frame, the second MLD of the BA initiator is transmitting data to the first MLD of the BA recipient, and the second MLD of the BA initiator informs the first MLD of the BA recipient by deleting the BA session response frame, so that the second MLD of the BA initiator does not delete the BA session, thereby correctly receiving/processing data based on the un-deleted BA session.

Illustratively, the first MLD of the BA initiator sends a delete BA session request frame to the second MLD of the BA recipient and receives a delete BA session response frame replied to the second MLD of the BA recipient, and the first MLD of the BA initiator determines whether to delete the BA session based on the delete BA session response frame. The first MLD of the BA initiator, at the time point of sending the BA session deletion request frame to the second MLD of the BA recipient, ensures that the local side does not have a data sending behavior performed simultaneously, so that there is no case that the second MLD of the BA recipient still receives the data sent by the first MLD of the BA initiator after the BA session is deleted.

In one embodiment of the present application, step 1006 is alternatively implemented as: in the case that the second MLD considers that the BA session can be deleted at the point of time when the BA session deletion request frame is received, the second MLD transmits a first BA session deletion 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.

Accordingly, step 1008 is alternatively implemented as: the first MLD receives a first delete BA session response frame sent by the second MLD, the first delete BA session response frame being a frame sent by the second MLD device if the second MLD believes that the BA session may be deleted at the point in time the delete BA session request frame was received.

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

That is, if the second MLD device under the BA session considers that the BA session can be deleted currently at the point in time when the BA session deletion request frame is received, the second MLD device may send a first BA session deletion response frame to the first MLD device and carry information indicating that the first MLD device that can allow the BA session deletion request frame to be sent deletes the BA session.

In one embodiment of the present application, step 1006 is alternatively implemented as: in the case that the second MLD considers that the BA session cannot be deleted at the time point when the BA session deletion request frame is received, the second MLD immediately transmits a second BA session deletion response frame to the first MLD; wherein the second delete BA session response frame is for indicating that the BA session is not allowed to be deleted; or, for indicating to delete the BA session after waiting the second length of time; or, a first point in time for indicating to delete the BA session.

Accordingly, step 1008 is alternatively implemented as: the first MLD receives a second BA session deletion response frame transmitted by the second MLD, the second BA session deletion response frame being a frame immediately transmitted by the second MLD device in the event that the second MLD considers that the BA session cannot be deleted at the point in time when the BA session deletion request frame was received.

Accordingly, step 1010 is alternatively implemented as: in response to the second delete BA session response frame indicating 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 indicating to delete the BA session after waiting the second length of time, the first MLD waits for the second length of time to delete the BA session; or, in response to the second delete BA session response frame indicating a first point in time to delete the BA session, the first MLD deletes the BA session at the first point in time.

That is, if the second MLD device under the BA session considers that the BA session cannot be deleted currently at the time point when the BA session deletion request frame is received, for example, the second MLD device is transmitting the AMPDU under the corresponding BA session on the other link, the second MLD may transmit a second BA session deletion response frame to the first MLD and carry information indicating that the first MLD of the opposite terminal is not allowed to delete the corresponding BA session, or carry information indicating the time point when the BA session is deleted or how long to delete the corresponding BA session again.

In one embodiment of the present application, step 1006 is alternatively implemented as: in the case that the second MLD considers that the BA session cannot be deleted at the time point when the BA session deletion request frame is received, the second MLD transmits a third BA session deletion response frame to the first MLD at the second time point; wherein the second time point is a time point at which the second MLD deems the BA session to be deleted; the third delete BA session response frame is used to indicate that the BA session is allowed to be deleted.

Accordingly, step 1008 is alternatively implemented as: the first MLD receives a third BA-deleting-session response frame sent by the second MLD, wherein the third BA-deleting-session response frame is a frame sent by the second MLD device at a second time point when the second MLD considers that the BA session can not be deleted at the time point when the second MLD receives the BA-deleting-session request frame, and the second time point is the time point when the second MLD considers that the BA session can be deleted.

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

That is, if the second MLD device under the BA session considers that the BA session cannot be deleted currently at the time point when the BA session deletion request frame is received, for example, the second MLD device is transmitting an AMPDU under the corresponding BA session on the other link, the second MLD does not reply immediately, but transmits a third BA session deletion response frame to the first MLD device until the second MLD device can allow the first MLD device of the opposite terminal to delete the BA session at a certain time point, and carries information indicating that the first MLD device that can allow the BA session deletion request frame to be transmitted deletes the BA session.

In summary, in the technical solution provided in this embodiment, in a multi-link scenario, if the first MLD wants to delete the BA session, an interaction negotiation process needs to be performed between the first MLD and the second MLD, and frames interacted by the interaction negotiation process include a BA session deletion request frame and a BA session deletion response frame, after the interaction negotiation process is completed, the first MLD will delete the BA session, and through the interaction negotiation process, the situation that the second MLD is transmitting data to the first MLD through other links when the first MLD deletes the BA session on a certain link is avoided, thereby guaranteeing the utilization rate of air interface resources.

An exemplary embodiment corresponding to fig. 10 described above is described with reference to fig. 11.

STA MLD acts as BA recipient, after sending a DELBA request frame (i.e. delete BA session request frame) on link 1, AP MLD chooses to reply with a DELBA response frame (i.e. delete BA session response frame) on link 1 because there is an AMPDU under the corresponding BA session sent to STA MLD on link 2, and carries information in this frame that does not allow STA MLD to delete BA session. Since the BA session for STA MLD still exists, STA MLD can still process the AMPDU on link 2 correctly.

An exemplary embodiment corresponding to fig. 10 described above is described with reference to fig. 12.

STA MLD acts as BA recipient, after sending a DELBA request frame (i.e. delete BA session request frame) on link 1, AP MLD chooses to reply with a DELBA response frame (i.e. delete BA session response frame) on link 1 because there is an AMPDU under the corresponding BA session sent to STA MLD on link 2, and carries information in this frame indicating the point in time or how long the STA MLD can delete the BA session. Since the BA session for STA MLD still exists, STA MLD can still process the AMPDU on link 2 correctly.

An exemplary embodiment corresponding to fig. 10 described above is described with reference to fig. 13.

STA MLD acts as BA recipient, which after sending a DELBA request frame (i.e., delete BA session request frame) on link 1, AP MLD chooses not to reply with a DELBA response frame (i.e., delete BA session response frame) on link 1 because there is an AMPDU under the corresponding BA session sent to STA MLD on link 2. Since the BA session for STA MLD still exists, STA MLD can still process the AMPDU on link 2 correctly. The AP MLD does not reply with a DELBA response frame on link 1 until it deems it possible to allow STA MLD to drop the BA session, and carries information in the frame indicating that STA MLD can drop the BA session.

Referring to fig. 14, a flowchart of a block acknowledgment session deletion method according to an embodiment of the present application is shown. The method can be applied to the wireless local area network shown in fig. 1. The method may comprise the steps of:

Step 1402: in the event that there is no data in the BA session sent by the second MLD on a link 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.

Wherein, a BA session is established between a first MLD and a second MLD, the first MLD is a device which expects to delete the BA session, the first MLD is a BA receiver, and the second MLD is a BA initiator.

That is, under a BA session established between MLD devices, when a first MLD of a BA recipient needs to actively drop the BA session, it is necessary to ensure that there are no AMPDUs under the corresponding BA session sent from a second MLD of the BA initiator on other links before the first MLD device sends DELBA frames on a link. Illustratively, deleting a BA session refers to: the corresponding resources under the BA session for correctly receiving/processing data from the peer MLD are deleted.

In one embodiment of the present application, the first MLD of the BA recipient does not receive MPDU/AMPDU/BAR frames under the corresponding BA session from the second MLD of the BA initiator for the duration of the BA session timeout period before the first MLD transmits the DELLBA frames to the second MLD.

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

The first MLD maintains device states on other links as a sleep (doze) state; alternatively, the first MLD uses a dynamic communication identifier to link mapping (DYNAMIC TID-to-LINK MAPPING) function to restrict the links used for data interactions under the BA session to the first links.

Where the device state on one link remains in a sleep state, no data transmission will take place on that link. Thus, in the case where the first MLD keeps the device state on the other links in a sleep state, there will be no data under the BA session sent by the second MLD on the other links than the first link.

Illustratively, a first MLD sends an indication to a second MLD on a link before maintaining the device state on the link in a sleep state, the indication informing the second MLD: the first MLD expects to maintain the device state on the link in a sleep state, and after the first MLD receives a reply acknowledgement frame of the indication from the second MLD, the device state on the link is maintained in a sleep state. Illustratively, the indication information is carried in an energy Management (Power Management) field in the frame transmitted by the first MLD.

Wherein the dynamic communication identifier-to-link mapping function is a function that prohibits data interaction on one link in a BA session. Thus, in the case where the first MLD uses the dynamic communication identifier to link mapping function to restrict the link used for data interaction under the BA session to the first link, there will be no data under the BA session sent by the second MLD on other links than the first link.

Illustratively, the dynamic communication identifier-to-link mapping function is implemented by: the first MLD sends a communication identifier to link map request to the second MLD, the communication identifier to link map request being used to request limiting of data transmission on a link, after the first MLD receives a communication identifier to link map response from the second MLD, if the communication identifier to link map response carries information allowing limiting of data transmission of the link, no data interaction under BA session will take place on the link.

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

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

In summary, in the technical solution provided in this embodiment, in a multi-link scenario, if the first MLD wants to send a DELBA frame on the first link, so as to delete a BA session, the first MLD needs to ensure that there is currently no data under the BA session sent by the second MLD on other links except the first link, so as to avoid a situation that the second MLD is sending data to the first MLD through other links when the first MLD deletes the BA session on a certain link, thereby ensuring the utilization rate of air interface resources.

The embodiment corresponding to fig. 14 described above is exemplarily described with reference to fig. 15.

When the BA recipient is STA MLD, before STA MLD wants to transmit DELBA frames on link 1, STA MLD may keep STA status on other links than the link transmitting DELBA frames in sleep (doze) state, i.e., STA status on link 2 in sleep state, so that AP MLD does not transmit data to STA MLD on link 2.

An exemplary embodiment corresponding to fig. 14 described above is described with reference to fig. 16.

Before the BA recipient wants to send DELBA frames on link 1, the BA recipient can restrict the links that data reception under the corresponding BA session is allowed to use to link 1 by using the communication identifier-to-link mapping function. So that the BA initiator does not send the corresponding AMPDU on the BA session to the BA recipient on link 2.

Referring to fig. 17, a flowchart of a block acknowledgment session deletion method according to an embodiment of the present application is shown. The method can be applied to the wireless local area network shown in fig. 1. The method may comprise the steps of:

Step 1702: the first MLD is not allowed to send DELBA frames and delete BA sessions.

Wherein, a 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. The DELBA frame is used to indicate that the sender is about to 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 transmit DELBA frames, i.e., is not allowed to actively delete the BA session.

Illustratively, during the process of establishing the BA session, negotiating a BA session timeout period, even if the first MLD of the BA recipient does not receive MPDU/AMPDU/BAR frames under the corresponding BA session from the second MLD of the BA initiator within the duration of the BA session timeout period, the first MLD will not actively transmit DERBA frames.

Illustratively, during the establishment of the BA session, a BA session timeout is not negotiated, nor is the first MLD, which is the recipient of the BA, allowed to actively send DelBA frames after the BA session is established.

In summary, in the technical solution provided in this embodiment, in a multi-link scenario, the first MLD serving as the BA receiver is not allowed to actively transmit the DELBA frame, which avoids the situation that when the first MLD actively transmits the DELBA frame on a link and deletes the BA session, the second MLD is transmitting data to the first MLD through other links, thereby guaranteeing the utilization rate of the air interface resource.

It will be appreciated that the above method embodiments may be implemented alone or in combination, and the application is not limited in this regard.

The following are examples of the apparatus of the present application that may be used to perform the method embodiments of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method of the present application.

Referring to fig. 18, a block diagram of a block acknowledgment session deletion apparatus according to one embodiment of the present application is shown. The device has the function of realizing the method example, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. The device may be the first MLD described above or may be provided in the first MLD. A BA session is established between the device and the second MLD. As shown in fig. 18, the apparatus 1800 may include: a wait module 1810 and a session delete module 1820;

the waiting module 1810 is configured to wait a first time period after transmitting a DELBA frame to the second MLD;

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

In one embodiment of the present application, the first time length is determined by an establishment procedure of the BA session;

Or alternatively, the first and second heat exchangers may be,

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

Or alternatively, the first and second heat exchangers may be,

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

In one embodiment of the application, the apparatus further comprises: a data receiving module;

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

Wherein the end time point of the interaction sequence of the data is no later than the time point when the device deleted the BA session.

Referring to fig. 19, a block diagram of a block acknowledgment session deletion apparatus according to an embodiment of the present application is shown. The device has the function of realizing the method example, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. The device may be the first MLD described above or may be provided in the first MLD. A BA session is established between the device and the second MLD. As shown in fig. 19, the apparatus 1900 may include: a request frame transmission module 1910, a response frame reception module 1920, and a session deletion module 1930;

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

The response frame receiving module 1920 is configured to receive the BA session deletion 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 BA session deletion response frame.

In one embodiment of the present application, the deleting the BA session response frame comprises: a first BA-session-deleted response frame, the first BA-session-deleted response frame being a frame transmitted by the second MLD device if the second MLD believes that the BA-session can be deleted at a point in time when the BA-session-deleted request frame was received;

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

In one embodiment of the present application, the deleting the BA session response frame comprises: a second BA-session-deleted response frame, which is a frame immediately transmitted by the second MLD device in a case where the second MLD considers that the BA session cannot be deleted at a point of time when the BA-session-deleted request frame is received;

said session deletion module 1930, configured to, in response to said second BA session deletion response frame, indicate that deletion of said BA session is not allowed, and not delete said BA session;

Or alternatively, the first and second heat exchangers may be,

The session deletion module 1930 is configured to, in response to the second BA session deletion response frame, instruct 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 alternatively, the first and second heat exchangers may be,

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

In one embodiment of the present application, the deleting the BA session response frame comprises: a third BA-session-deletion-response frame that is a frame transmitted by the second MLD device at a second point in time that the second MLD considers that the BA session can be deleted, in a case where the second MLD considers that the BA session cannot be deleted at the point in time when the BA-session-deletion-request frame is received;

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

Referring to fig. 20, a block diagram of a block acknowledgment session deletion apparatus according to an embodiment of the present application is shown. The device has the function of realizing the method example, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. The device may be the first MLD described above or may be provided in the first MLD. A BA session is established between the apparatus and a second MLD, the apparatus 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 send a DELBA frame to a second MLD on a first link, and delete the BA session when there is no data under the BA session sent by the second MLD on a link other than the first link.

In one embodiment of the application, the apparatus further comprises: a link confirmation module;

The link confirmation module is used for keeping the equipment states on the other links to be in a sleep state;

Or alternatively, the first and second heat exchangers may be,

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

Referring to fig. 21, a block diagram of a block acknowledgment session deletion apparatus according to an embodiment of the present application is shown. The device has the function of realizing the method example, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. The device may be the first MLD described above or may be provided in the first MLD. A BA session is established between the apparatus and a second MLD, the apparatus being a BA recipient and the second MLD being a BA initiator. As shown in fig. 21, the apparatus 2100 may include: a session deletion module 2110;

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

Referring to fig. 22, a block diagram of a block acknowledgment session deletion apparatus according to one embodiment of the present application is shown. The device has the function of realizing the method example, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. The device may be the second MLD described above or may be provided in the second MLD. A BA session is established between the apparatus and the first MLD. As shown in fig. 22, the apparatus 2200 may include: delete frame receive module 2210;

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

Or alternatively, the first and second heat exchangers may be,

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

Or alternatively, the first and second heat exchangers may be,

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

In one embodiment of the application, the apparatus further comprises: a data transmission module;

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

Or alternatively, the first and second heat exchangers may be,

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

Referring to fig. 23, a block diagram of a block acknowledgment session deletion apparatus according to one embodiment of the present application is shown. The device has the function of realizing the method example, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. The device may be the second MLD described above or may be provided in the second MLD. A BA session is established between the apparatus and the first MLD. As shown in fig. 23, the apparatus 2300 may include: request frame receiving module 2310 and response frame transmitting module 2320;

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

The response frame sending module 2320 is configured to send a BA session deletion response frame to the first MLD, where the BA session deletion 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 a first BA session deletion response frame to the first MLD if the apparatus considers that the BA session can be deleted at a time point when the BA session deletion request frame is received;

Wherein the first delete BA session response frame is to indicate that deletion of the BA session is allowed.

In one embodiment of the present application, the response frame sending module 2320 is configured to send a second BA session deletion response frame to the first MLD immediately when the apparatus considers that the BA session cannot be deleted at the time point when the BA session deletion request frame is received;

wherein the second BA session response frame is for indicating that deletion of the BA session is not allowed; or, to instruct deletion of the BA session after waiting a second length of time; or, a first point in time for indicating deletion of the BA session.

In one embodiment of the present application, the response frame sending module 2320 is configured to send a third BA session deletion response frame to the first MLD at a second time point when the apparatus considers that the BA session cannot be deleted at the time point when the BA session deletion request frame is received;

Wherein the second point in time is a point in time at which the apparatus deems the BA session to be deleted; the third delete BA session response frame is to indicate that deletion of the BA session is allowed.

Referring to fig. 24, a block diagram of a block acknowledgment session deletion apparatus according to one embodiment of the present application is shown. The device has the function of realizing the method example, and the function can be realized by hardware or can be realized by executing corresponding software by hardware. The device may be the second MLD described above or may be provided in the second MLD. A BA session is established between the apparatus and a first MLD, the first MLD being a BA recipient and the apparatus being a BA initiator. As shown in fig. 24, the apparatus 2400 may include: delete frame receive module 2410;

The delete frame receiving module 2410 is configured to receive a DELBA frame sent by the first MLD on the first link if the first MLD ensures that there is no data in the BA session sent by the second MLD on a link other than the first link.

In one 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 by:

the first MLD maintaining device states on the other links as sleep states;

Or alternatively, the first and second heat exchangers may be,

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

It should be noted that, when the apparatus provided in the foregoing embodiment performs the functions thereof, only the division of the respective functional modules is used as an example, in practical application, the foregoing functional allocation may be performed by different functional modules according to actual needs, that is, the content structure of the device is divided into different functional modules, so as to perform all or part of the functions described above.

The specific manner in which the various modules perform the operations in the apparatus of the above embodiments have been described in detail in connection with the embodiments of the method, and will not be described in detail herein.

Referring to fig. 25, a schematic structural diagram of a multi-link device according to an embodiment of the present application is shown, where the multi-link device may be the first MLD or the 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 may be implemented as one transceiver 2506, and the transceiver 2506 may be a communication chip.

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

The memory 2504 may be used to store a computer program that the processor 2501 uses to execute to implement the steps performed by the multilink device in the above-described method embodiments.

Further, the memory 2504 may be implemented by any type of volatile or nonvolatile memory device or combination thereof, including but not limited to: random-Access Memory (RAM) and Read-Only Memory (ROM), 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 Memory technology, compact disc Read-Only (Compact Disc Read-Only Memory, CD-ROM), high density digital video disc (Digital Video Disc, DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices.

When the multi-link device is implemented as the first MLD, the processor 2501 and the transceiver 2506 in the embodiments of the present application may execute the steps executed by the first MLD device in the methods shown in any one of fig. 8 to 9, which are not described herein.

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

The processor 2501 for waiting a first length of time after transmitting a DELBA frame to the second MLD;

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

When the multi-link device is implemented as the first MLD, the processor 2501 and the transceiver 2506 in the embodiments of the present application may execute the steps executed by the first MLD device in the methods shown in any one of fig. 10 to 13, which are not described herein.

The transceiver 2506 for sending a delete BA session request frame to the second MLD, the delete BA session request frame for requesting deletion of the BA session;

The transceiver 2506 is configured to receive a 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.

When the multi-link device is implemented as the first MLD, the processor 2501 and the transceiver 2506 in the embodiments of the present application may execute the steps executed by the first MLD device in the methods shown in any one of fig. 14 to 16, which are not described herein.

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

The processor 2501 is configured to send a DELBA frame to a second MLD on a first link and delete the BA session if there is no data in the BA session sent by the second MLD on a link other than the first link.

When the multi-link device is implemented as the first MLD, the processor 2501 and the transceiver 2506 in the embodiments of the present application may execute the steps executed by the first MLD device in the method shown in fig. 17, which are not described herein.

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

When the multi-link device is implemented as the second MLD, the processor 2501 and the transceiver 2506 in the embodiments of the present application may execute the steps executed by the second MLD device in the methods shown in any one of fig. 8 to 9, which are not described herein.

In one possible implementation, 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 for receiving DELBA frames transmitted by the first MLD;

When the multi-link device is implemented as the second MLD, the processor 2501 and the transceiver 2506 in the embodiments of the present application may execute the steps executed by the second MLD device in the methods shown in any one of fig. 10 to 13, which are not described herein.

the transceiver 2506 is configured to receive a BA session deletion request frame sent by the first MLD, where the BA session deletion 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, the delete BA session response frame being used by the first MLD to determine whether to delete the BA session.

When the multi-link device is implemented as the second MLD, the processor 2501 and the transceiver 2506 in the embodiments of the present application may execute the steps executed by the second MLD device in the methods shown in any one of fig. 14 to 16, which are not described herein.

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

The transceiver 2506 is configured to receive a DELBA frame transmitted by a first MLD on a first link if the first MLD ensures that no data in the BA session transmitted by the second MLD is present on links other than the first link.

The embodiment of the application also provides a computer readable storage medium, wherein the storage medium stores a computer program, and the computer program is used for being executed by a processor to realize the block confirmation session deletion method.

Alternatively, the computer-readable storage medium may include: read-Only Memory (ROM), random-Access Memory (RAM), solid state disk (Solid STATE DRIVES, SSD), optical disk, or the like. 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), among others.

The embodiment of the application also provides a chip, which comprises a programmable logic circuit and/or program instructions and is used for realizing the block acknowledgement session deletion method when the chip runs.

Embodiments of the present application also provide a computer program product or computer program comprising computer instructions stored in a computer readable storage medium, from which a processor reads and executes the computer instructions to implement the above-described block acknowledgment session deletion method.

The processor in the embodiment of the application comprises: 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, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

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

References herein to "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

In addition, the step numbers described herein are merely exemplary of one possible execution sequence among steps, and in some other embodiments, the steps may be executed out of the order of numbers, such as two differently numbered steps being executed simultaneously, or two differently numbered steps being executed in an order opposite to that shown, which is not limiting.

Those skilled in the art will appreciate that in one or more of the examples described above, the functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, these 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 foregoing description of the exemplary embodiments of the application is not intended to limit the application to the particular embodiments disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the application.

Claims

A block acknowledgment, BA, session deletion method, the method performed by a first multi-link device, MLD, having a BA session established between the first MLD and a second MLD, the method comprising:

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

and deleting the BA session after the first time length is over.
The method of claim 1, wherein the step of determining the position of the substrate comprises,

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

Or alternatively, the first and second heat exchangers may be,

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

Or alternatively, the first and second heat exchangers may be,

The first time length is the 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:

Receiving data sent by the second MLD in the process of waiting for the first time length under the condition that the first MLD is a BA receiver and the second MLD is a BA initiator;

Wherein an end time point of the interactive sequence of data is no later than a time point when the first MLD deletes the BA session.
A block acknowledgment, BA, session deletion method, the method performed by a first multi-link device, MLD, between which a BA session is established, the method comprising:

Transmitting a BA session deletion request frame to the second MLD, the BA session deletion request frame being for requesting deletion of the BA session;

Receiving a BA session deleting response frame sent by the second MLD;

Based on the delete BA session response frame, determining whether to delete the BA session.
The method of claim 4, wherein the deleting the BA session response frame comprises: a first BA-session-deleted response frame, the first BA-session-deleted response frame being a frame transmitted by the second MLD device if the second MLD believes that the BA-session can be deleted at a point in time when the BA-session-deleted request frame was received;

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

and deleting the BA session in response to the first deleting BA session response frame, wherein the first deleting BA session response frame is used for indicating that the BA session is allowed to be deleted.
The method of claim 4, wherein the deleting the BA session response frame comprises: a second BA-session-deleted response frame, which is a frame immediately transmitted by the second MLD device in a case where the second MLD considers that the BA session cannot be deleted at a point of time when the BA-session-deleted request frame is received;

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

Responsive to the second delete BA session response frame indicating that deletion of the BA session is not allowed, not deleting the BA session;

Or alternatively, the first and second heat exchangers may be,

Responsive to the second delete BA session response frame for indicating to delete the BA session after waiting a second length of time, waiting to delete the BA session after the second length of time;

Or alternatively, the first and second heat exchangers may be,

And deleting the BA session at a first time point in response to the second BA session deleting response frame being used for indicating the first time point of deleting the BA session.
The method of claim 4, wherein the deleting the BA session response frame comprises: a third BA-session-deletion-response frame that is a frame transmitted by the second MLD device at a second point in time that the second MLD considers that the BA session can be deleted, in a case where the second MLD considers that the BA session cannot be deleted at the point in time when the BA-session-deletion-request frame is received;

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

And deleting the BA session in response to the third deleting BA session response frame, wherein the BA session is allowed to be deleted.
A block acknowledgment, BA, session deletion method, performed by a first multi-link device, MLD, having a BA session established between the first MLD and a second MLD, the first MLD being a BA recipient, the second MLD being a BA initiator, the method comprising:

And when the data under the BA session transmitted by the second MLD does not exist on other links except the first link, transmitting a deletion BA session DELLBA frame to the second MLD on the first link, and deleting the BA session.
The method of claim 8, wherein the method further comprises:

maintaining the device state on the other link in a sleep state;

Or alternatively, the first and second heat exchangers may be,

The link used for data interaction under the BA session is restricted to the first link using a dynamic communication identifier to link mapping function.
A block acknowledgment, BA, session deletion method, performed by a first multi-link device, MLD, having a BA session established between the first MLD and a second MLD, the first MLD being a BA recipient, the second MLD being a BA initiator, the method comprising:

the first MLD is not allowed to send delete BA session DELBA frames and delete the BA session.
A block acknowledgment, BA, session deletion method, the method performed by a second multi-link device, MLD, having a BA session established between the second MLD and a first MLD, the method comprising:

Receiving a deleted BA session DELLA frame sent by the first MLD;

the first MLD waits for a first time length after sending the DERBA frame, and deletes the BA session after the first time length is over.
The method of claim 11, wherein the step of determining the position of the probe is performed,

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

Or alternatively, the first and second heat exchangers may be,

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

Or alternatively, the first and second heat exchangers may be,

The first time length is the 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:

In the case that the first MLD is a BA recipient and the second MLD is a BA initiator, not actively transmitting data to the first MLD;

Or alternatively, the first and second heat exchangers may be,

And in the case that the first MLD is a BA receiver and the second MLD is a BA initiator, sending the data to the first MLD, wherein the ending time point of the interaction sequence of the data is no later than the time point of the first MLD deleting the BA session.
A block acknowledgment, BA, session deletion method, the method performed by a second multi-link device, MLD, having a BA session established between the second MLD and a first MLD, the method comprising:

Receiving a BA session deletion request frame sent by the first MLD, wherein the BA session deletion request frame is used for requesting to delete the BA session;

And sending a deletion BA session response frame to the first MLD, wherein the deletion BA session response frame is used for the first MLD to determine whether to delete the BA session.
The method of claim 14, wherein the transmitting a delete BA session response frame to the first MLD comprises:

Transmitting a first delete BA session response frame to the first MLD in a case where the second MLD considers that the BA session can be deleted at a point in time when the delete BA session request frame is received;

Wherein the first delete BA session response frame is to indicate that deletion of the BA session is allowed.
The method of claim 14, wherein the transmitting a delete BA session response frame to the first MLD comprises:

In the case that the second MLD considers that the BA session cannot be deleted at the time point when the BA session deletion request frame is received, immediately transmitting a second BA session deletion response frame to the first MLD;

wherein the second BA session response frame is for indicating that deletion of the BA session is not allowed; or, to instruct deletion of the BA session after waiting a second length of time; or, a first point in time for indicating deletion of the BA session.
The method of claim 14, wherein the transmitting a delete BA session response frame to the first MLD comprises:

transmitting a third BA session response frame to the first MLD at a second point in time, in the event that the second MLD considers that the BA session cannot be deleted at the point in time when the BA session deletion request frame was received;

wherein the second point in time is a point in time at which the second MLD deems the BA session to be deleted; the third delete BA session response frame is to indicate that deletion of the BA session is allowed.
A block acknowledgment, BA, session deletion method, the method performed by a second multi-link device, MLD, having a BA session established between the second MLD and a first MLD, the first MLD being a BA recipient, the second MLD being a BA initiator, the method comprising:

and receiving a deleted BA session DELLBA frame sent by the first MLD on the first link under the condition that the first MLD ensures that no data in the BA session sent by the second MLD exists on other links except the first link.
The method of claim 18, wherein 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 by:

the first MLD maintaining device states on the other links as sleep states;

Or alternatively, the first and second heat exchangers may be,

The first MLD uses a dynamic communication identifier to link mapping function to restrict links used for data interactions under the BA session to the first link.
A block acknowledgment, BA, session deletion apparatus, wherein a BA session is established between the apparatus and a second multi-link device, MLD, the apparatus comprising: a waiting module and a session deleting module;

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

And the session deleting module is used for deleting the BA session after the first time length is over.
The apparatus of claim 20, wherein the device comprises a plurality of sensors,

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

Or alternatively, the first and second heat exchangers may be,

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

Or alternatively, the first and second heat exchangers may be,

The first time length is the maximum time of a physical layer protocol data unit (PPDU).
The apparatus according to claim 20 or 21, characterized in that the apparatus further comprises: a data receiving module;

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

Wherein the end time point of the interaction sequence of the data is no later than the time point when the device deleted the BA session.
A block acknowledgment, BA, session deletion apparatus, wherein a BA session is established between the apparatus and a second multi-link device, MLD, the apparatus comprising: a request frame sending module, a response frame receiving module and a session deleting module;

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

The response frame receiving module is used for receiving a BA session deleting response frame sent by the second MLD;

the session deleting module is configured to determine whether to delete the BA session based on the BA session deleting response frame.
The apparatus of claim 23, wherein the delete BA session response frame comprises: a first BA-session-deleted response frame, the first BA-session-deleted response frame being a frame transmitted by the second MLD device if the second MLD believes that the BA-session can be deleted at a point in time when the BA-session-deleted request frame was received;

The session deletion module is configured to delete the BA session in response to the first delete BA session response frame indicating permission to delete the BA session.
The apparatus of claim 23, wherein the delete BA session response frame comprises: a second BA-session-deleted response frame, which is a frame immediately transmitted by the second MLD device in a case where the second MLD considers that the BA session cannot be deleted at a point of time when the BA-session-deleted request frame is received;

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

Or alternatively, the first and second heat exchangers may be,

The session deletion module is configured to respond to the second BA session deletion response frame to instruct deletion of 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 alternatively, the first and second heat exchangers may be,

The session deletion module is configured to delete the BA session at a first time point in response to the second BA session deletion response frame indicating the first time point at which the BA session is deleted.
The apparatus of claim 23, wherein the delete BA session response frame comprises: a third BA-session-deletion-response frame that is a frame transmitted by the second MLD device at a second point in time that the second MLD considers that the BA session can be deleted, in a case where the second MLD considers that the BA session cannot be deleted at the point in time when the BA-session-deletion-request frame is received;

The session deletion module is configured to delete the BA session in response to the third delete BA session response frame indicating permission to delete the BA session.
A block acknowledgment, BA, session deletion apparatus, wherein a BA session is established between the apparatus and a second multi-link device, MLD, the apparatus being a BA recipient, the second MLD being a BA initiator, the apparatus comprising: a session deletion module;

The session deletion module is configured to send a BA session delete DELBA frame to a second MLD on a first link and delete the BA session when there is no data under the BA session sent by the second MLD on a link other than the first link.
The apparatus of claim 27, wherein the apparatus further comprises: a link confirmation module;

The link confirmation module is used for keeping the equipment states on the other links to be in a sleep state;

Or alternatively, the first and second heat exchangers may be,

The link confirmation module is configured to limit a link used for data interaction under the BA session to the first link using a dynamic communication identifier-to-link mapping function.
A block acknowledgment, BA, session deletion apparatus, wherein a BA session is established between the apparatus and a second multi-link device, MLD, the apparatus being a BA recipient, the second MLD being a BA initiator, the apparatus comprising: a session deletion module;

The session deletion module is configured to not allow the apparatus to send a delete BA session DELBA frame and delete the BA session.
A block acknowledgment, BA, session deletion apparatus, wherein a BA session is established between the apparatus and a first multi-link device, MLD, the apparatus comprising: deleting a frame receiving module;

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

the first MLD waits for a first time length after sending the DERBA frame, and deletes the BA session after the first time length is over.
The apparatus of claim 30, wherein the device comprises a plurality of sensors,

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

Or alternatively, the first and second heat exchangers may be,

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

Or alternatively, the first and second heat exchangers may be,

The first time length is the maximum time of a physical layer protocol data unit (PPDU).
The apparatus according to claim 30 or 31, characterized in that the apparatus further comprises: a data transmission module;

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

Or alternatively, the first and second heat exchangers may be,

The data sending module is configured to send the data to the first MLD when the first MLD is a BA recipient and the device is a BA initiator, where an end time point of an interaction sequence of the data is not later than a time point when the first MLD deletes the BA session.
A block acknowledgment, BA, session deletion apparatus, wherein a BA session is established between the apparatus and a first multi-link device, MLD, the apparatus comprising: a request frame receiving module and a response frame transmitting module;

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

the response frame sending module is configured to send a BA session deletion response frame to the first MLD, where the BA session deletion response frame is used for the first MLD to determine whether to delete the BA session.
The apparatus of claim 33, wherein the device comprises a plurality of sensors,

The response frame sending module is configured to send a first BA session deletion response frame to the first MLD if the apparatus considers that the BA session can be deleted at the time point when the BA session deletion request frame is received;

Wherein the first delete BA session response frame is to indicate that deletion of the BA session is allowed.
The apparatus of claim 33, wherein the device comprises a plurality of sensors,

The response frame sending module is configured to send a second BA session deletion response frame to the first MLD immediately, if the apparatus considers that the BA session cannot be deleted at the time point when the BA session deletion request frame is received;

wherein the second BA session response frame is for indicating that deletion of the BA session is not allowed; or, to instruct deletion of the BA session after waiting a second length of time; or, a first point in time for indicating deletion of the BA session.
The apparatus of claim 33, wherein the device comprises a plurality of sensors,

The response frame sending module is configured to send a third BA session response frame to the first MLD at a second time point, in a case where the apparatus considers that the BA session cannot be deleted at the time point when the BA session deletion request frame is received;

Wherein the second point in time is a point in time at which the apparatus deems the BA session to be deleted; the third delete BA session response frame is to indicate that deletion of the BA session is allowed.
A block acknowledgment, BA, session deletion apparatus, wherein a BA session is established between the apparatus and a first multi-link device, MLD, the first MLD being a BA recipient, the apparatus being a BA initiator, the apparatus comprising: deleting a frame receiving module;

the deletion frame receiving module is configured to receive, on a first link, a deletion BA session DELBA frame sent by the first MLD when the first MLD ensures that there is no data under the BA session sent by the second MLD on a link other than the first link.
The apparatus of claim 37, wherein the first MLD ensures that no data in the BA session sent by the second MLD is present on links other than the first link by:

the first MLD maintaining device states on the other links as sleep states;

Or alternatively, the first and second heat exchangers may be,

The first MLD uses a dynamic communication identifier to link mapping function to restrict links used for data interactions under the BA session to the first link.
A first multi-link device, MLD, wherein a block acknowledgment, BA, session is established between the first MLD and a second MLD, the first MLD comprising a processor;

the processor is configured to wait a first time period 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 has ended.
A first multi-link device, MLD, having a block acknowledgment, BA, session established between the first MLD and a second MLD, the first MLD comprising a transceiver and a processor;

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

the transceiver is configured to receive a BA session deletion 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, wherein a block acknowledgment, BA, session is established between the first MLD and a second MLD, the first MLD being a BA recipient, the second MLD being a BA initiator, the first MLD comprising a processor;

The processor is configured to send a delete BA session DELBA frame to a second MLD on a first link and delete the BA session if there is no data under the BA session sent by the second MLD on a link other than the first link.
A first multi-link device, MLD, wherein a block acknowledgment, BA, session is established between the first MLD and a second MLD, the first MLD being a BA recipient, the second MLD being a BA initiator, the first MLD comprising a processor;

The processor is configured to disallow the first MLD to send a delete BA session DELBA frame and delete the BA session.
A second multi-link device, MLD, wherein a block acknowledgment, BA, session is established between said second MLD and the first MLD, said second MLD comprising a transceiver;

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

the first MLD waits for a first time length after sending the DERBA frame, and deletes the BA session after the first time length is over.
A second multi-link device, MLD, wherein a block acknowledgment, BA, session is established between said second MLD and the first MLD, said second MLD comprising a transceiver;

The transceiver is configured to receive a BA session deletion request frame sent by the first MLD, where the BA session deletion 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, the delete BA session response frame being used by the first MLD to determine whether to delete the BA session.
A second multi-link device, MLD, wherein a block acknowledgment, BA, session is established between said second MLD and a first MLD, said first MLD being a BA recipient, said second MLD being a BA initiator, said second MLD comprising a transceiver;

The transceiver is configured to receive, on a first link, a delete BA session DELBA frame sent by a first MLD if the first MLD ensures that there is no data under the BA session sent by the second MLD on a link other than the first link.
A computer readable storage medium having stored therein a computer program for execution by a processor to implement the block acknowledgment session deletion method of any one of claims 1 to 19.
A chip comprising programmable logic circuitry and/or program instructions for implementing the block acknowledgment session deletion method of any one of claims 1 to 19 when the chip is running.
A computer program product or computer program comprising computer instructions stored in a computer readable storage medium, from which a processor reads and executes the computer instructions to implement the block acknowledgment session deletion method of any one of claims 1 to 19.