Buffer report sending and receiving method and apparatus

Abstract

To provide a buffer reporting method and device for reducing transmission delay on a direct link in an access point multi-link device (APMLD) and a non-APMLD.SOLUTION: The method further includes that the non-APMLD generates a buffer report, and sends the buffer report to the APMLD on the first uplink / downlink, where the buffer report is used to request duration of direct transmission performed by the first associated non-APSTA of the non-APMLD on the first direct link, and the first direct link is a link between the first target non-APSTA and the first associated non-APSTA; The first target non-APSTA and the first associated non-APSTA belong to a same BSS, and the APMLD allocates a second transmission duration to the first associated non-APSTA, where the second transmission duration includes duration of direct transmission performed by the first associated non-APSTA on the first direct link.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] This application claims priority to Chinese Patent Application No. 202110838424.5, entitled "BUFFER REPORT SENDING AND RECEIVING METHOD, AND APPARATUS," filed with the State Intellectual Property Office of China on July 23, 2021, and Chinese Patent Application No. 202111093436.6, entitled "BUFFER REPORT SENDING AND RECEIVING METHOD, AND APPARATUS," filed with the State Intellectual Property Office of China on September 17, 2021, both of which are incorporated herein by reference in their entireties.

[0002] [Technical field] The present application relates to the field of communication technology, and in particular to a buffer report sending and receiving method and apparatus. [Background technology]

[0003] Wireless fidelity (Wi-Fi) systems are deployed on unlicensed spectrum, and stations (STAs) in the system use channel resources through contention. After successfully contending for the channel, a station may reserve a duration for data transmission. The duration is called a transmission opportunity (TXOP). A station that successfully reserves a TXOP is called a TXOP holder. In a TXOP, only the TXOP holder can actively transmit data; other stations can only receive data or transmit response frames for received data.

[0004] In the Institute of Electrical and Electronics Engineers (IEEE) 802.11be standard, the TXOP mechanism is extended as follows: an access point station (AP STA) acting as a TXOP holder may allocate a portion of the duration in a reserved TXOP to a non-access point station (non-AP STA) so that the non-AP STA can perform point-to-point (P2P) transmission with another non-AP STA or transmit uplink data to the AP STA during the allocated duration.

[0005] In the extended TXOP mechanism, when allocating a portion of the duration in a TXOP to a non-AP STA, the AP STA acting as the TXOP holder may need to know the transmission duration required by the non-AP STA. Summary of the Invention

[0006] The embodiments of the present application provide a buffer report sending and receiving method and device. Thus, an AP corresponding to a direct link of an AP MLD can decide to allocate a duration in a TXOP obtained by the AP for transmission on the direct link to an associated non-AP STA, so as to transmit data on the direct link in a timely manner and reduce transmission delay on the direct link.

[0007] According to a first aspect, a buffer report transmission method is provided. The method is applied to a non-access point multilink device (non-AP MLD), and multiple uplinks / downlinks are set up between the non-AP MLD and the access point multilink device (AP MLD). The method includes: the non-AP MLD generates a buffer report and transmits the buffer report to the AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. The buffer report is used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, where the first direct link is a link between a first target non-AP STA and a first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belong to the same basic service set (BSS).

[0008] Based on this solution, the non-AP MLD sends a buffer report to the AP MLD. The buffer report can be used to request the duration of a direct transmission performed by a first associated non-AP STA of the non-AP MLD on a first direct link. Thus, after receiving the buffer report, the AP MLD can know that the first associated non-AP STA of the non-AP MLD will perform a direct transmission on the first direct link, so that the associated non-AP STA of the AP MLD corresponding to the first direct link can assign the duration of the transmission on the first direct link to the first associated non-AP STA in the TXOP obtained by the associated non-AP STA. In this way, data can be transmitted on the direct link in a timely manner, and the transmission delay on the direct link can be reduced.

[0009] In some possible designs, the buffer report includes link information, where the link information indicates the first direct link.

[0010] Based on this possible design, the direct link on which direct transmission should be performed can be indicated to the AP MLD, so that the associated AP corresponding to the direct link can allocate the duration of transmission on the direct link in the TXOP obtained by the associated AP.

[0011] In some possible designs, the link information is an identifier or a bitmap of the first direct link.

[0012] Based on this possible design, the direct link can be indicated explicitly based on the direct link identifier, or the direct link can be indicated implicitly based on the bitmap.

[0013] In some possible designs, the buffer report includes transmission duration information, the transmission duration information indicating a first transmission duration, the first transmission duration being a duration of a direct transmission performed by a first associated non-AP STA of the non-AP MLD on the first direct link.

[0014] Based on this possible design, the transmission duration of the direct transmission to be performed may be indicated to the AP MLD, so that the AP MLD may allocate a corresponding duration for the direct transmission.

[0015] In some possible designs, the first uplink / downlink is any one of multiple uplinks / downlinks.

[0016] Based on this possible design, the non-AP MLD may send the buffer report to the AP MLD on any uplink / downlink to improve the flexibility of sending the buffer report.

[0017] In some possible designs, the buffer report further includes buffer type information, where the buffer type information indicates that the buffer report is a buffer report corresponding to a direct transmission.

[0018] Based on this possible design, the buffer report can be indicated to the AP MLD as a buffer report corresponding to a direct transmission, so that the AP MLD can allocate a transmission duration in the TXOP obtained by the associated AP corresponding to the direct link.

[0019] In some possible designs, the buffer report includes link information, but does not include link information indicating the first direct link, the transmission duration information indicates a first transmission duration, and the first transmission duration is a duration of a direct transmission performed by a first associated non-AP STA of the non-AP MLD on the first direct link.

[0020] In some possible designs, the first uplink / downlink identifier is the same as the first direct link identifier.

[0021] Based on two possible designs, the buffer report is transmitted on the first uplink / downlink whose identifier is the same as the identifier of the first direct link to implicitly indicate that the buffer report is used to request the duration of direct transmission on the first direct link, which may reduce signaling overhead.

[0022] In some possible designs, the transmission duration information includes a first transmission duration or a size of a first buffer, the first buffer being used to cache data transmitted by a first associated non-AP STA of the non-AP MLD on the first direct link.

[0023] In some possible designs, the non-AP MLD sending the buffer report to the AP MLD on a first uplink / downlink of the multiple uplinks / downlinks includes: the non-AP MLD sending a management frame to the AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. The management frame includes the buffer report. Based on this possible design, the buffer report may be carried in the management frame.

[0024] In some possible designs, the management frame includes an aggregate control field, and the aggregate control field includes the buffer report. Based on the possible designs, the buffer report may be carried in the aggregate control field of the management frame.

[0025] In some possible designs, the frame header of the management frame includes multilink device information, and the multilink device information indicates non-AP MLD.

[0026] In some possible designs, the non-AP MLD sending the buffer report to the AP MLD on a first uplink / downlink of the multiple uplinks / downlinks includes: the non-AP MLD sending a data frame to the AP MLD on the first uplink / downlink of the multiple uplinks / downlinks. The data frame includes an aggregate control field, and the aggregate control field includes the buffer report. Based on this possible design, the buffer report may be carried in the aggregate control field of the data frame.

[0027] In some possible designs, the frame header of the data frame includes multilink device information, and the multilink device information indicates a non-AP MLD. Based on this possible design, the non-AP MLD can indicate to the AP MLD a duration of the direct transmission.

[0028] In some possible designs, the non-AP MLD sending the buffer report to the AP MLD on a first uplink / downlink of the multiple uplinks / downlinks may include: the non-AP MLD sending a data frame to the AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. The data frame includes a QoS control field, and the QoS control field includes the buffer report. For example, the data frame is a QoS Null frame.

[0029] In some possible designs, the buffer report further includes a resource request type, where the resource request type indicates that the buffer report is a buffer report corresponding to a direct transmission.

[0030] In some possible designs, bit 7 or bit 3 in the QoS Control field of the QoS Null frame is used to carry the resource request type.

[0031] According to a second aspect, a buffer report receiving method is provided. The method is applied to an access point multilink device (AP MLD), and multiple uplinks / downlinks are set up between the AP MLD and a non-access point multilink device (non-AP MLD). The method includes: the AP MLD receives a buffer report from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. The buffer report is used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between a first target non-AP STA and a first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belong to the same basic service set (BSS). Then, the AP MLD determines a second transmission duration and transmits first duration indication information. The first duration indication information indicates the second transmission duration. The second transmission duration includes a duration of direct transmission on the first direct link assigned by the AP MLD to the first associated non-AP STA of the non-AP MLD.

[0032] Based on this solution, the buffer report received by the AP MLD can be used to request the duration of a direct transmission performed by a first associated non-AP STA of the non-AP MLD on the first direct link. Thus, the AP MLD can know that the first associated non-AP STA of the non-AP MLD will perform a direct transmission on the first direct link, so that the associated AP of the AP MLD corresponding to the first direct link can assign the duration of the transmission on the first direct link in the TXOP obtained by the associated AP to the first associated non-AP STA. In this way, data can be transmitted on the direct link in a timely manner, and the transmission delay on the direct link can be reduced.

[0033] In some possible designs, the buffer report includes link information, where the link information indicates the first direct link.

[0034] In some possible designs, the link information is an identifier or a bitmap of the first direct link.

[0035] In some possible designs, the buffer report includes transmission duration information, the transmission duration information indicating a first transmission duration, the first transmission duration being a duration of a direct transmission performed by a first associated non-AP STA of the non-AP MLD on the first direct link.

[0036] In some possible designs, the first uplink / downlink is any one of multiple uplinks / downlinks.

[0037] In some possible designs, the buffer report further includes buffer type information, where the buffer type information indicates that the buffer report is a buffer report corresponding to a direct transmission.

[0038] In some possible designs, the buffer report includes link information, but does not include link information indicating the first direct link, the transmission duration information indicates a first transmission duration, and the first transmission duration is a duration of a direct transmission performed by a first associated non-AP STA of the non-AP MLD on the first direct link.

[0039] In some possible designs, the first uplink / downlink identifier is the same as the first direct link identifier.

[0040] In some possible designs, the transmission duration information includes a first transmission duration or a size of a first buffer, the first buffer being used to cache data transmitted by a first associated non-AP STA of the non-AP MLD on the first direct link.

[0041] In some possible designs, the AP MLD receiving a buffer report from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks includes: the AP MLD receiving a management frame from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks, the management frame including the buffer report.

[0042] In some possible designs, the management frame includes an aggregate control field, and the aggregate control field includes the buffer report.

[0043] In some possible designs, the frame header of the management frame includes multilink device information, and the multilink device information indicates non-AP MLD.

[0044] In some possible designs, the AP MLD receiving a buffer report from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks includes: the AP MLD receiving a data frame from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks, the data frame including an aggregate control field, the aggregate control field including the buffer report.

[0045] In some possible designs, a frame header of a data frame includes multilink device information, and the multilink device information indicates non-AP MLD.

[0046] In some possible designs, the AP MLD receiving a buffer report from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks includes: the AP MLD receiving a data frame from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. The data frame includes a QoS control field, and the QoS control field includes the buffer report. For example, the data frame is a QoS Null frame.

[0047] In some possible designs, the buffer report further includes a resource request type, where the resource request type indicates that the buffer report is a buffer report corresponding to a direct transmission.

[0048] In some possible designs, bit 7 or bit 3 in the QoS Control field of the QoS Null frame is used to carry the resource request type.

[0049] For the technical effects brought about by any possible design of the second aspect, please refer to the technical effects brought about by the corresponding design of the first aspect, and the details will not be described again in this specification.

[0050] According to a third aspect, a communication method is provided. The method is applied to a source access point multilink device (AP MLD), and multiple uplinks / downlinks are set up between the source AP MLD and a non-access point multilink device (non-AP MLD). The method includes: the source AP MLD generates a basic service set transition management (BTM) request frame and transmits the BTM request frame to the non-AP MLD on any one of the multiple uplinks / downlinks. The BTM request frame includes indication information, which indicates that a disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of one of the multiple uplinks / downlinks.

[0051] Based on this solution, the source AP MLD adds indication information to the BTM request frame to indicate that the disassociation timer and / or validity interval in the BTM request frame is in units of one TBTT of multiple uplinks / downlinks. Therefore, the non-AP MLD can accurately obtain the time to send the disassociation frame or the validity time of the BSS transition candidate list, thereby improving the efficiency of BSS transition.

[0052] In some possible designs, the indication information is an identifier of one uplink / downlink among the multiple uplinks / downlinks or a basic service set identifier corresponding to one of the multiple uplinks / downlinks.

[0053] According to a fourth aspect, a communication method is provided. The method is applied to a source access point multilink device (AP MLD), and multiple uplinks / downlinks are set up between the source AP MLD and a non-access point multilink device (non-AP MLD). The method includes: the source AP MLD generating a basic service set transition management (BTM) request frame and transmitting the BTM request frame to the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. A disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of the first uplink / downlink of the multiple uplinks / downlinks.

[0054] Based on this solution, the disassociation timer and / or validity interval in the BTM request frame are in units of the TBTT of the uplink / downlink used to transmit the BTM request frame, so that the non-AP MLD can accurately obtain the time to transmit the disassociation frame or the validity time of the BSS transition candidate list based on the uplink / downlink on which the BTM request frame is received, thereby improving the efficiency of BSS transition.

[0055] According to a fifth aspect, a communication method is provided. The method includes: a source access point multilink device (AP MLD) generates a basic service set transition management (BTM) request frame and transmits the BTM request frame to a non-AP MLD. The BTM request frame includes one or more neighbor report elements, where the neighbor report elements indicate candidate access points (APs) recommended by the source AP MLD to the non-AP MLD. When the candidate access points belong to the candidate AP MLD, the neighbor report elements include a basic variant multilink element, where the basic variant multilink element includes a multilink control field and a common information field, but does not include a link information field.

[0056] Based on this solution, when the neighbor report element in the BTM request frame carries a basic variant multilink element indicating the AP MLD to which the candidate AP belongs, the basic variant multilink element does not carry the link information field because link information does not need to be acquired during BSS transition, which can reduce signaling overhead and does not affect BSS transition.

[0057] In some possible designs, a multilink device medium access control address present field in the multilink control field is set to a first value, and a first presence field in the multilink control field is set to a second value, the first presence field including a link identifier information present field and a basic service set parameter change count present field, where the first value indicates that the field is present in the common information field and the second value indicates that the field is not present in the common information field.

[0058] In some possible designs, when multiple candidate APs indicated by multiple neighbor report elements belong to the same candidate AP MLD, a second presence field in a multilink control field included in a first basic variant multilink element is set to a first value, and a second presence field in a multilink control field included in a second basic variant multilink element is set to a second value. The first basic variant multilink element is a basic variant multilink element included in a first neighbor report element of the multiple neighbor report elements, and the second basic variant multilink element is a basic variant multilink element included in a neighbor report element other than the first neighbor report element of the multiple neighbor report elements.

[0059] In some possible designs, the second presence field includes one or more of a media synchronization delay information presence field, an extended multilink capability presence field, or a multilink device capability presence field.

[0060] According to a possible design, when multiple candidate APs indicated by the same BTM request frame belong to the same AP MLD, a first neighbor report element indicating that the AP MLD's associated AP is a candidate AP carries a basic modified multilink element, and a second presence field in the multilink control field included in the basic modified multilink element is set to a first value, and a second presence field in the multilink control field included in the basic modified multilink element of another neighbor report element indicating that the AP MLD's associated AP is a candidate AP is set to a second value. Therefore, the BTM request frame carries one or more of the medium synchronization delay information presence field, the EML capability presence field, or the MLD presence field only once to avoid repeatedly carrying the same field. This may reduce signaling overhead.

[0061] According to a sixth aspect, a buffer report transmission method is provided. The method is applied to a non-access point multilink device (non-AP MLD), and multiple uplinks / downlinks are set up between the non-AP MLD and the access point multilink device (AP MLD). The method includes: the non-AP MLD generates a buffer report. The buffer report is used to request a duration of a transmission performed by a first associated non-AP station (non-AP STA) of the non-AP MLD on a first link, the first link including a first direct link and a first uplink / downlink. The first direct link is a link between a first target non-AP STA and a first associated non-AP STA of the non-AP MLD, the first uplink / downlink is a link between a first associated AP of the AP MLD and a first associated non-AP STA of the non-AP MLD, and the first target non-AP STA, the first associated non-AP STA of the non-AP MLD, and the first associated AP of the AP MLD belong to the same basic service set (BSS). The non-AP MLD sends a buffer report to the AP MLD on a second uplink / downlink of the multiple uplinks / downlinks.

[0062] Based on this solution, the non-AP MLD sends a buffer report to the AP MLD. The buffer report can be used to request the total duration of transmissions performed by a first associated non-AP STA of the non-AP MLD on the first direct link and the first uplink / downlink. Thus, after receiving the buffer report, the AP MLD can know that the first associated non-AP STA of the non-AP MLD should transmit on the first direct link and the first uplink / downlink. Thus, the associated AP of the AP MLD corresponding to the first direct link and the first uplink / downlink can decide to assign the first associated non-AP STA the duration of transmissions on the first direct link and the first uplink / downlink in the TXOP obtained by the associated AP. In this way, data can be transmitted in a timely manner, and transmission delays can be reduced.

[0063] According to a seventh aspect, a non-AP multilink device (non-AP MLD) is provided. Multiple uplinks / downlinks are set up between the non-AP MLD and the access point multilink device (AP MLD). The non-AP MLD includes a processing module and a transceiver module.

[0064] The processing module is configured to generate a buffer report, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between the first target non-AP STA and the first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0065] The transceiver module is configured to transmit the buffer report to the AP MLD on a first uplink / downlink of the plurality of uplinks / downlinks.

[0066] The non-AP MLD provided in the seventh aspect is configured to implement the functions of the non-AP MLD in the first aspect or any one of the possible designs of the first aspect. For details, please refer to the description in the first aspect or any one of the possible designs of the first aspect. For details, the description will not be repeated in this specification.

[0067] According to an eighth aspect, an access point multilink device (AP MLD) is provided. Multiple uplinks / downlinks are set up between the AP MLD and a non-access point multilink device (non-AP MLD). The AP MLD includes a processing module and a transceiver module.

[0068] The transceiver module is configured to receive a buffer report from the non-AP MLD on a first uplink / downlink of the plurality of uplinks / downlinks, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between a first target non-AP STA and a first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0069] The processing module is configured to determine a second transmission duration, the second transmission duration comprising a duration of a direct transmission on the first direct link assigned by the AP MLD to a first associated non-AP STA of the non-AP MLD.

[0070] The transceiver module is further configured to transmit a first duration indication, the first duration indication indicating the second transmission duration.

[0071] The AP MLD provided in the eighth aspect is configured to implement the function of the AP MLD in the second aspect or any one of the possible designs of the second aspect. For details, please refer to the description in the second aspect or any one of the possible designs of the second aspect. For details, the description will not be repeated in this specification.

[0072] According to a ninth aspect, a source access point multilink device (AP MLD) is provided. Multiple uplinks / downlinks are set up between the source AP MLD and a non-access point multilink device (non-AP MLD). The source AP MLD includes a processing module and a transceiver module.

[0073] The processing module is configured to generate a basic service set transition management (BTM) request frame, the BTM request frame including indication information, the indication information indicating that a disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of one uplink / downlink of a plurality of uplinks / downlinks.

[0074] The transceiver module is configured to transmit a BTM request frame to the non-AP MLD on any one of a plurality of uplinks / downlinks.

[0075] The source AP MLD provided in the ninth aspect is configured to implement the function of the source AP MLD in the third aspect or any one of the possible designs of the third aspect. For details, please refer to the description in the third aspect or any one of the possible designs of the third aspect. For details, the description will not be repeated in this specification.

[0076] According to a tenth aspect, a source access point multilink device (AP MLD) is provided. Multiple uplinks / downlinks are set up between the source AP MLD and a non-access point multilink device (non-AP MLD). The source AP MLD includes a processing module and a transceiver module.

[0077] The processing module is configured to generate a basic service set transition management (BTM) request frame.

[0078] The transceiver module is configured to transmit a BTM request frame to the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks, wherein the disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of the first uplink / downlink of the multiple uplinks / downlinks.

[0079] The source AP MLD provided in the tenth aspect is configured to implement the function of the source AP MLD in the fourth aspect or any one of the possible designs of the fourth aspect. For details, please refer to the description in the fourth aspect or any one of the possible designs of the fourth aspect. For details, the description will not be repeated in this specification.

[0080] According to an eleventh aspect, there is provided a source access point multilink device (AP MLD), which includes: a processing module and a transceiver module.

[0081] The processing module is configured to generate a basic service set transition management (BTM) request frame. The BTM request frame includes one or more neighbor report elements, where the neighbor report elements indicate candidate access points (APs) recommended by the source AP MLD for non-AP MLD. When the candidate access points belong to the candidate AP MLD, the neighbor report elements include a basic modified multilink element, where the basic modified multilink element includes a multilink control field and a common information field, but does not include a link information field.

[0082] The transceiver module is configured to transmit a BTM request frame to the non-AP MLD.

[0083] The source AP MLD provided in the eleventh aspect is configured to implement the function of the source AP MLD in the fifth aspect or any one of the possible designs of the fifth aspect. For details, please refer to the description in the fifth aspect or any one of the possible designs of the fifth aspect. The details will not be described again in this specification.

[0084] According to a twelfth aspect, there is provided a non-access point multilink device (non-AP MLD). Multiple uplinks / downlinks are set up between the non-AP MLD and the access point multilink device (AP MLD). The non-AP MLD includes a processing circuit and an output interface internally connected to the processing circuit and communicating with the processing circuit.

[0085] The processing circuitry is configured to generate a buffer report, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between the first target non-AP STA and the first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0086] The output interface is configured to send the buffer report to the AP MLD on a first uplink / downlink of the plurality of uplinks / downlinks.

[0087] The non-AP MLD provided in the twelfth aspect is configured to implement the functions of the non-AP MLD in the first aspect or any one of the possible designs of the first aspect. For details, please refer to the description in the first aspect or any one of the possible designs of the first aspect. For details, the description will not be repeated in this specification.

[0088] According to a thirteenth aspect, there is provided an access point multilink device (AP MLD), in which multiple uplinks / downlinks are set up between the AP MLD and a non-access point multilink device (non-AP MLD), and the AP MLD includes a processing circuit, and an output interface and an input interface internally connected to the processing circuit and communicating with the processing circuit.

[0089] The input interface is configured to receive a buffer report from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between a first target non-AP STA and a first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0090] The processing circuitry is configured to determine a second transmission duration, the second transmission duration comprising a duration of a direct transmission on a first direct link assigned by the AP MLD to a first associated non-AP STA of the non-AP MLD.

[0091] The output interface is further configured to transmit a first duration indication, the first duration indication indicating the second transmission duration.

[0092] The AP MLD provided in the thirteenth aspect is configured to perform the function of the AP MLD in the second aspect or any one of the possible designs of the second aspect. For details, please refer to the description in the second aspect or any one of the possible designs of the second aspect. For details, the description will not be repeated in this specification.

[0093] According to a fourteenth aspect, there is provided a source access point multilink device (AP MLD), where multiple uplinks / downlinks are set up between the source AP MLD and a non-access point multilink device (non-AP MLD). The source AP MLD includes a processing circuit and an output interface internally connected to the processing circuit and communicating with the processing circuit.

[0094] The processing circuitry is configured to generate a basic service set transition management (BTM) request frame, the BTM request frame including indication information, the indication information indicating that a disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of one uplink / downlink of a plurality of uplinks / downlinks.

[0095] The output interface is configured to transmit the BTM request frame to the non-AP MLD on any one of a plurality of uplinks / downlinks.

[0096] The source AP MLD provided in the fourteenth aspect is configured to implement the function of the source AP MLD in the third aspect or any one of the possible designs of the third aspect. For details, please refer to the description in the third aspect or any one of the possible designs of the third aspect. For details, the description will not be repeated in this specification.

[0097] According to a fifteenth aspect, there is provided a source access point multilink device (AP MLD), where multiple uplinks / downlinks are set up between the source AP MLD and a non-access point multilink device (non-AP MLD). The source AP MLD includes a processing circuit and an output interface internally connected to the processing circuit and communicating with the processing circuit.

[0098] The processing circuitry is configured to generate a basic service set transition management (BTM) request frame.

[0099] The output interface is configured to transmit a BTM request frame to the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks, wherein the disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of the first uplink / downlink of the multiple uplinks / downlinks.

[0100] The source AP MLD provided in the fifteenth aspect is configured to implement the function of the source AP MLD in the fourth aspect or any one of the possible designs of the fourth aspect. For details, please refer to the description in the fourth aspect or any one of the possible designs of the fourth aspect. For details, the description will not be repeated in this specification.

[0101] According to a sixteenth aspect, there is provided a source access point multilink device (AP MLD), the source AP MLD including: a processing circuit; and an output interface internally coupled to and in communication with the processing circuit.

[0102] The processing circuitry is configured to generate a basic service set transition management (BTM) request frame. The BTM request frame includes one or more neighbor report elements, where the neighbor report elements indicate candidate access points (APs) recommended by the source AP MLD for non-AP MLD. When the candidate access points belong to the candidate AP MLD, the neighbor report elements include a basic modified multilink element, where the basic modified multilink element includes a multilink control field and a common information field, but does not include a link information field.

[0103] The output interface is configured to send a BTM request frame to the non-AP MLD.

[0104] The source AP MLD provided in the sixteenth aspect is configured to implement the function of the source AP MLD in the fourth aspect or any one of the possible designs of the fourth aspect. For details, please refer to the description in the fourth aspect or any one of the possible designs of the fourth aspect. For details, the description will not be repeated in this specification.

[0105] According to a seventeenth aspect, there is provided a non-AP multilink device (non-AP MLD). Multiple uplinks / downlinks are set up between the non-AP MLD and the access point multilink device (AP MLD). The non-AP MLD includes a processor and a transceiver internally connected to the processor and communicating with the processor.

[0106] The processor is configured to generate a buffer report, the buffer report used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between the first target non-AP STA and the first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0107] The transceiver is configured to transmit a buffer report to the AP MLD on a first uplink / downlink of the plurality of uplinks / downlinks.

[0108] The non-AP MLD provided in the seventeenth aspect is configured to implement the function of the non-AP MLD in the first aspect or any one of the possible designs of the first aspect. For details, please refer to the description in the first aspect or any one of the possible designs of the first aspect. For details, the description will not be repeated in this specification.

[0109] According to an eighteenth aspect, there is provided an access point multilink device (AP MLD), wherein multiple uplinks / downlinks are set up between the AP MLD and a non-access point multilink device (non-AP MLD), and the AP MLD includes a processor and a transceiver internally connected to the processor and communicating with the processor.

[0110] The transceiver is configured to receive a buffer report from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between a first target non-AP STA and a first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0111] The processor is configured to determine a second transmission duration, the second transmission duration comprising a duration of a direct transmission on the first direct link assigned by the AP MLD to a first associated non-AP STA of the non-AP MLD.

[0112] The transceiver is further configured to transmit a first duration indication, the first duration indication indicating the second transmission duration.

[0113] The AP MLD provided in the eighteenth aspect is configured to perform the function of the AP MLD in the second aspect or any one of the possible designs of the second aspect. For details, please refer to the description in the second aspect or any one of the possible designs of the second aspect. For details, the description will not be repeated in this specification.

[0114] According to a nineteenth aspect, there is provided a source access point multilink device (AP MLD), wherein multiple uplinks / downlinks are set up between the source AP MLD and a non-access point multilink device (non-AP MLD), and the source AP MLD includes a processor and a transceiver internally connected to the processor and communicating with the processor.

[0115] The processor is configured to generate a basic service set transition management (BTM) request frame, the BTM request frame including indication information, the indication information indicating that a disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of one uplink / downlink of a plurality of uplinks / downlinks.

[0116] The transceiver is configured to transmit a BTM request frame to the non-AP MLD on any one of a plurality of uplinks / downlinks.

[0117] The source AP MLD provided in the nineteenth aspect is configured to implement the function of the source AP MLD in the third aspect or any one of the possible designs of the third aspect. For details, please refer to the description in the third aspect or any one of the possible designs of the third aspect. For details, the description will not be repeated in this specification.

[0118] According to a twentieth aspect, there is provided a source access point multilink device (AP MLD). Multiple uplinks / downlinks are set up between the source AP MLD and a non-access point multilink device (non-AP MLD). The source AP MLD includes a processor and a transceiver internally connected to the processor and communicating with the processor.

[0119] The processor is configured to generate a basic service set transition management (BTM) request frame.

[0120] The transceiver is configured to transmit a BTM request frame to the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks, wherein the disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of the first uplink / downlink of the multiple uplinks / downlinks.

[0121] The source AP MLD provided in the twentieth aspect is configured to implement the function of the source AP MLD in the fourth aspect or any one of the possible designs of the fourth aspect. For details, please refer to the description in the fourth aspect or any one of the possible designs of the fourth aspect. For details, the description will not be repeated in this specification.

[0122] According to a twenty-first aspect, there is provided a source access point multilink device (AP MLD), the source AP MLD including: a processor; and a transceiver internally coupled to and in communication with the processor.

[0123] The processor is configured to generate a basic service set transition management (BTM) request frame. The BTM request frame includes one or more neighbor report elements, where the neighbor report elements indicate candidate access points (APs) recommended by the source AP MLD for the non-AP MLD. When the candidate access points belong to the candidate AP MLD, the neighbor report elements include a basic modified multilink element, where the basic modified multilink element includes a multilink control field and a common information field, but does not include a link information field.

[0124] The transceiver is configured to transmit a BTM request frame to the non-AP MLD.

[0125] The source AP MLD provided in the 21st aspect is configured to implement the function of the source AP MLD in the 4th aspect or any one of the possible designs of the 4th aspect. For details, please refer to the description in the 4th aspect or any one of the possible designs of the 4th aspect. For details, the description will not be repeated in this specification.

[0126] According to a twenty-second aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program, the computer program including instructions used to perform the first aspect or any one of the possible implementations of the first aspect.

[0127] According to a twenty-third aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program, the computer program including instructions used to perform the second aspect or any one of the possible implementations of the second aspect.

[0128] According to a twenty-fourth aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program, the computer program including instructions used to perform the third aspect or any one of the possible implementations of the third aspect.

[0129] According to a twenty-fifth aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program, the computer program including instructions used to perform the fourth aspect or any one of the possible implementations of the fourth aspect.

[0130] According to a twenty-sixth aspect, an embodiment of the present application provides a computer-readable storage medium configured to store a computer program, the computer program including instructions used to perform the fifth aspect or any one of the possible implementations of the fifth aspect.

[0131] According to a twenty-seventh aspect, an embodiment of the present application provides a computer program product, the computer program product including instructions used to perform the first aspect or any one of the possible implementations of the first aspect.

[0132] According to a twenty-eighth aspect, an embodiment of the present application provides a computer program product, the computer program product including instructions used to perform the second aspect or any one of the possible implementations of the second aspect.

[0133] According to a twenty-ninth aspect, an embodiment of the present application provides a computer program product, the computer program product including instructions used to perform the third aspect or any one of the possible implementations of the third aspect.

[0134] According to a thirtieth aspect, an embodiment of the present application provides a computer program product, the computer program product including instructions used to perform the fourth aspect or any one of the possible implementations of the fourth aspect.

[0135] According to a thirty-first aspect, an embodiment of the present application provides a computer program product, the computer program product including instructions used to perform the fifth aspect or any one of the possible implementations of the fifth aspect.

[0136] According to a thirty-second aspect, an embodiment of the present application provides a communication system, the communication system including the non-AP MLD and the AP MLD provided in the seventh aspect, the twelfth aspect, or the seventeenth aspect.

[0137] According to a thirty-third aspect, an embodiment of the present application provides a communication system, the communication system including the AP MLD and the non-AP MLD provided in the eighth aspect, the thirteenth aspect, or the eighteenth aspect.

[0138] According to a thirty-fourth aspect, an embodiment of the present application provides a communication system, the communication system including the AP MLD and the non-AP MLD provided in the ninth aspect, the fourteenth aspect, or the nineteenth aspect.

[0139] According to a thirty-fifth aspect, an embodiment of the present application provides a communication system, the communication system including the AP MLD and the non-AP MLD provided in the tenth aspect, the fifteenth aspect, or the twentieth aspect.

[0140] According to a thirty-sixth aspect, an embodiment of the present application provides a communication system, the communication system including the AP MLD and the non-AP MLD provided in the eleventh aspect, the sixteenth aspect, or the twenty-first aspect. [Brief explanation of the drawings]

[0141] [Figure 1]FIG. 1 is a schematic diagram of a multi-link device according to an embodiment of the present application. [Figure 2] 1 is a schematic diagram of a structure of a multi-link element according to an embodiment of the present application; [Figure 3] 1 is a schematic flowchart of BSS transition management according to an embodiment of the present application; [Figure 4a] FIG. 2 is a schematic diagram of a frame structure of a BTM query frame according to an embodiment of the present application; [Figure 4b] FIG. 2 is a schematic diagram of a frame structure of a BTM request frame according to an embodiment of the present application; [Figure 4c] FIG. 2 is a schematic diagram of a frame structure of a BTM response frame according to an embodiment of the present application; [Figure 5] FIG. 1 is a schematic diagram of a time sequence of a TXOP mechanism according to an embodiment of the present application. [Figure 6a] 1 is a schematic diagram of the structure of a communication system according to an embodiment of the present application; [Figure 6b] FIG. 2 is a schematic diagram of the structure of another communication system according to an embodiment of the present application; [Figure 7] 1 is a schematic flowchart of a buffer report sending and receiving method according to an embodiment of the present application; [Figure 8a] 1 is a schematic diagram of a buffer report structure according to an embodiment of the present application; [Figure 8b] 2 is a schematic diagram of a buffer report structure according to an embodiment of the present application; [Figure 9a] 3 is a schematic diagram of a buffer report structure according to an embodiment of the present application; [Figure 9b] 4 is a schematic diagram of a buffer report structure according to an embodiment of the present application; [Figure 10a] 5 is a schematic diagram of a buffer report structure according to an embodiment of the present application; [Figure 10b] 4 is a schematic flowchart of another buffer report sending and receiving method according to an embodiment of the present application; [Figure 11] 1 is a schematic flowchart of a communication method according to an embodiment of the present application; [Figure 12]4 is a schematic flowchart of another communication method according to an embodiment of the present application; [Figure 13] 4 is a schematic flowchart of yet another communication method according to an embodiment of the present application; [Figure 14] 1 is a schematic diagram of the structure of a first communication device according to an embodiment of the present application; [Figure 15] FIG. 2 is a schematic diagram of the structure of a second communication device according to an embodiment of the present application; [Figure 16] 1 is a schematic diagram of the structure of a first communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE INVENTION

[0142] Unless otherwise specified, " / " in the description of the embodiments of the present application represents an "or" relationship between related objects. For example, A / B may represent A or B. In the present application, "and / or" only describes a correlation for describing related objects and represents that three relationships may exist. For example, A and / or B may represent the following three cases: when only A exists, when both A and B exist, and when only B exists. A and B may be singular or plural.

[0143] In the description of this application, unless otherwise specified, "plurality" means two or more. At least one of the following items (moieties) or similar expressions refers to any combination of these items, including any combination of singular items (moieties) or plural items (moieties). For example, at least one of the items (moieties) a, b, or c can refer to a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c can be singular or plural.

[0144] In addition, to clearly describe the technical solutions in the embodiments of the present application, terms such as "first" and "second" are used in the embodiments of the present application to distinguish between identical or similar items having essentially the same function and purpose. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity or execution order, and that words such as "first" and "second" do not indicate clear distinctions. In addition, in the embodiments of the present application, words such as "example" or "for example" are used to provide an example, illustration, or explanation. Any embodiment or design manner described as an "example" or "for example" in the embodiments of the present application should not be described as being preferred or having more advantages than another embodiment or design manner. Rather, the use of the words "example" or "for example" is intended to present related concepts in a specific way for ease of understanding.

[0145] It may be understood that the term "embodiment" referred to throughout this specification means that a particular feature, structure, or characteristic associated with an embodiment is included in at least one embodiment of the present application. Thus, embodiments throughout this specification do not necessarily refer to the same embodiment. In addition, these particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. It may be understood that the sequence numbers of the processes described above do not imply an execution order in various embodiments of the present application. The execution order of the processes should be determined based on the functions and internal logic of the processes and should not be interpreted as any limitation on the implementation process of the embodiments of the present application.

[0146] In this application, it can be understood that "when" and "if" mean that the corresponding processing is performed in an objective situation, are not intended to limit the time, do not require a decision action during implementation, and do not imply any other limitations.

[0147] It will be appreciated that "predefine" in this application may be understood as "define," "predefine," "store," "prestore," "prenegotiate," "preconfigure," "incorporate," or "pre-burn."

[0148] It can be understood that in some scenarios, some optional features in the embodiments of the present application can be implemented independently to solve corresponding technical problems and achieve corresponding effects, without relying on other features, for example, on the solutions on which the optional features are currently based. Alternatively, in some scenarios, optional features are combined with other features based on requirements. Correspondingly, the devices provided in the embodiments of the present application can also implement these features or functions accordingly. Details will not be described herein.

[0149] In this application, unless otherwise specified, the same or similar parts of the embodiments shall refer to each other. In the embodiments and implementation forms / implementation methods in the embodiments of this application, unless otherwise specified or unless a logical contradiction occurs, the terms and / or descriptions shall be consistent and may be cross-referenced between different embodiments and between implementation forms / implementation methods in the embodiments. The technical features in different embodiments and implementation forms / implementation methods in the embodiments may be combined to form new embodiments, implementation forms, or implementation methods according to their internal logical relationships. The following implementation forms of this application are not intended to limit the protection scope of this application.

[0150] In order to facilitate understanding of the technical solutions in the embodiments of the present application, first, a brief description of the technologies related to the present application is given below.

[0151] 1. Multi-link device (MLD)

[0152] In order to achieve the technical goal of extremely high throughput, the next-generation wireless local area network (WLAN) standard IEEE802.11be uses extremely high throughput (EHT) as its technical goal, and the existing main technology is multi-link (ML) communication.

[0153] The core concept of multilink communication is that WLAN devices supporting the next-generation IEEE 802.11 standard have the ability to transmit and receive on multiple frequency bands so that larger bandwidths can be used for transmission. This can further improve throughput. WLAN devices that have the ability to simultaneously transmit and receive on multiple frequency bands are sometimes referred to as MLDs. For example, multiple frequency bands include, but are not limited to, the 2.4 GHz frequency band, the 5 GHz frequency band, and the 6 GHz frequency band.

[0154] In this application, an MLD includes at least two affiliated stations (STAs), which may be access point stations (AP STAs) or non-access point stations (non-AP STAs).

[0155] For ease of explanation, AP STA will be referred to as AP for short in the following embodiments of this application. A multi-link device whose associated station is an AP may be referred to as an AP multi-link device (AP MLD), and a multi-link device whose associated station is a non-AP STA may be referred to as a non-access point multi-link device (non-AP MLD).

[0156] In this application, each associated station of an MLD may set up a link for communication, and a link set up by multiple associated stations is called a multilink.

[0157] Typically, association (or setup) of multiple links between a non-AP MLD and an AP MLD may be implemented by exchanging multi-link association request frames and multi-link association response frames. Specifically, the non-AP MLD and the AP MLD may exchange association request frames and association response frames (abbreviated as multi-link association request frames and multi-link association response frames) carrying multi-link information on one link. The multi-link information is carried in the multi-link association request frame and the multi-link association response frame to implement simultaneous association of multiple links between a non-AP MLD and an AP MLD.

[0158] The link over which the Multi-Link Association Request Frame and the Multi-Link Association Response Frame are exchanged may be referred to as the Transmitted Link, and correspondingly, another link of the plurality of links may be referred to as the Non-Transmitted Link.

[0159] For example, as shown in Figure 1, the AP MLD includes associated AP1 and associated AP2, and the non-AP MLD includes associated non-AP STA1 and associated non-AP STA2. Stations (APs or non-AP STAs) belonging to the same MLD share a higher medium access control (MAC) layer, and each has an independent physical (PHY) layer and lower MAC layer. The multilink setup procedure may include the following steps:

[0160] Step 1: The non-AP MLD sends a multi-link association request frame to the AP MLD on link 1, and the multi-link association request frame carries information on the non-AP STA side of link 1 (i.e., non-AP STA1) and the non-AP STA side of link 2 (i.e., non-AP STA2). Link 1 is a transmitting link, and link 2 is a non-transmitting link.

[0161] Step 2: The AP MLD responds to the non-AP MLD with a multi-link association response frame on link 1, and the multi-link association response frame carries information on the AP side of link 1 (i.e., AP1) and information on the AP side of link 2 (i.e., AP2).

[0162] In the above procedure, the protocol defines a multi-link element that is used to carry information about the MLD and information about the stations of the MLD in order to carry information related to the MLD in a multi-link association request frame or a multi-link association response frame. The frame structure of the multi-link element can be shown in Figure 2.

[0163] Please note that unless otherwise specified, a station in this application is an AP or a non-AP STA, which is uniformly described in this specification and will not be described again in detail in the following embodiments.

[0164] See Figure 2. A Multi-Link element includes an element identifier (element ID) field, a length field, an element ID extension field, a Multi-Link Control field, a common info field, and a link info field.

[0165] The element identifier field and element identifier extension field are used to identify the multilink element. The element identifier field and element identifier extension field of different multilink elements are different. Typically, the element identifier field may be set to 255, and the element identifier extension field is set to a value not used by another multilink element. The length field indicates the length of the multilink element.

[0166] The Multilink Control field may include a Type field and a Presence Bitmap field. The Type field indicates the type of the Multilink element, for example, a Basic variant Multilink element or a Probe Request variant Multilink element. The Presence Bitmap field may include one or more Presence fields. Specifically, the Presence Bitmap field may include the following fields:

[0167] The Multilink Device Medium Access Control (MAC) Address Present field indicates whether the MLD MAC Address field in the common information field is present.

[0168] The Link ID Info Present field indicates whether the Link ID Info field in the Common Information field is present. The Link ID Info field in the Common Information field indicates information about the transmitted link.

[0169] The basic service set (BSS) parameters change count present field indicates whether the BSS parameters change count field in the common information field is present.

[0170] The Medium Synchronization Delay Information Present field indicates whether the Medium Synchronization Delay Information field in the common information field is present.

[0171] The enhanced multi-link (EML) Capabilities Present field indicates whether the EML capabilities field in the common information field is present.

[0172] The MLD Capabilities Present field indicates whether the multilink device capabilities field in the common information field is present.

[0173] With respect to the above-mentioned presence field, typically, when the presence field is set to 1, this indicates that the field indicated by the presence field is present, and when the presence field is set to 0, this indicates that the field indicated by the presence field is not present.

[0174] It should be noted that the "Present field" in this application may also be referred to as a "present field" or an "existing field" and may be used interchangeably, which is not particularly limited in this application.

[0175] The common information fields may further include to-be-determined (TBD) fields other than those indicated by the presence field.

[0176] The Link Information field is used to carry information related to non-transmitting links and may include a Per-STA Profile sub-element, which may correspond one-to-one to stations on non-transmitting links of a multi-link device.

[0177] The per-station profile subelement may include a Subelement ID field, a Length field, and a Data field. The Data field may include a Station Control field, a Station Info field, and a Station Profile field. The Station Profile field may include zero or multiple Elements.

[0178] The frame structure of the multilink element and the functions of some fields have been described above. For descriptions of other fields, please refer to the definitions in the IEEE 802.11be standard, and details will not be described in this specification.

[0179] 2. Tunneled direct-link setup (TDLS)

[0180] For two non-AP STAs associated with the same BSS, if the two non-AP STAs are within wireless communication coverage, a direct link may be set up between the two non-AP STAs, and data may be transmitted between the two non-AP STAs over the direct link without forwarding by the AP, which may improve the transmission rate and reduce the transmission delay.

[0181] It may be understood that the non-AP STA that sets up the direct link may be a non-AP STA that belongs to a non-AP MLD, or may be an independent non-AP STA, i.e., a non-AP STA that does not belong to any non-AP MLD. For ease of explanation, a non-AP STA that does not belong to any non-AP MLD is referred to as a legacy STA in this application.

[0182] Typically, a direct link may be set up between two non-AP STAs associated with the same BSS according to the TDLS protocol or another P2P protocol.

[0183] In this application, P2P may also be referred to as device-to-device (D2D). A direct link may also be referred to as a P2P link, a D2D link, or a TDLS link. The names may be used interchangeably. This is not particularly limited in this application.

[0184] The TDLS protocol mainly includes the following operations related to direct links:

[0185] TDLS discovery is completed by exchanging a TDLS discovery request frame and a TDLS discovery response frame between a TDLS initiator and a TDLS responder.

[0186] TDLS Setup is completed by exchanging a TDLS Setup Request frame, a TDLS Setup Response frame, and a TDLS Setup Confirm frame between a TDLS initiator and a TDLS responder. Through the exchange of these three frames, the TDLS initiator and the TDLS responder can complete the derivation of a TDLS Peer Key (TPK).

[0187] TDLS Teardown is completed by using the TDLS Teardown frame.

[0188] TDLS Power Save is primarily accomplished by using the TDLS Peer PSM Request frame, the TDLS Peer PSM Response frame, the TDLS Peer Traffic Indication frame, and the TDLS Peer Traffic Response frame.

[0189] A TDLS channel switch is completed by using a TDLS Channel Switch Request frame and a TDLS Channel Switch Response frame.

[0190] Table 1 shows the frame type of each frame and the transmission method of each frame in the TDLS protocol, which is transmission by using an AP (Via AP) or direct transmission on a direct link (Direct). [Table 1]

[0191] As can be seen from Table 1, when a TDLS-related frame is forwarded by an AP or transmitted on a direct link, the TDLS-related frame is encapsulated in a data frame for transmission. Therefore, the aforementioned TDLS-related operations are completely transparent to the AP, i.e., the AP does not detect the aforementioned TDLS-related operations. Note that the TDLS discovery response frame is a public action frame and is transmitted directly in the form of a management frame.

[0192] 3.BSS transition

[0193] 3 shows a BSS transition management operation process. For a non-AP STA associated with a BSS, due to insufficient link quality or another reason, the non-AP STA may send a BSS transition management (BTM) query frame to the AP of the BSS. In response, the AP may reply to the non-AP STA with an acknowledgment (Ack) frame for the BTM query frame.

[0194] When an AP wants a non-AP STA to perform a BSS transition, the AP may send a BTM request frame to the non-AP STA. In response, after responding to the AP with an acknowledgment frame for the BTM request frame, the non-AP STA may send a BTM response frame to the AP to indicate whether to accept or reject the BSS transition request. In response, the AP may respond with an acknowledgment frame for the BTM response frame.

[0195] Figure 4a shows the frame structure of a BTM query frame, which includes a Category field, a wireless network management (WNM) Action field, a Dialog Token field, a BSS Transition Query Reason field, and a BSS Transition Candidate List field.

[0196] The BSS transition query reason field carries the reason why a non-AP STA is sending a BTM query frame.

[0197] The BSS Transition Candidate List field is an optional field that carries one or more Neighbor Report elements, which indicate candidate BSSs determined by non-AP STAs.

[0198] 4b shows the frame structure of a BTM request frame, which includes a Category field, a wireless network management (WNM) action field, a Dialog Token field, a Request Mode field, a Disassociation Timer field, a Validity Interval field, a BSS Termination Duration field, a Session Info URL field, and a BSS Transition Candidate List field.

[0199] The Request Mode field indicates a particular request mode and may specifically include the following fields: (1) A Preferred Candidate List Included field indicating whether a preferred candidate list is carried, i.e., whether the BTM request frame includes a BSS transition candidate list field; (2) Abridged field, in which the indication bit of the abridged field is set to 0 if the AP does not recommend or prohibit non-AP STAs from switching to a BSS that is not in the BSS transition candidate list, and the indication bit of the abridged field is set to 1 if the AP sets the preference value of a BSS that is not in the BSS transition candidate list to 0; (3) A Disassociation Imminent field, where if this field is set to 1, it indicates that the AP will send a Disassociation frame to disassociate from a non-AP STA, and if this field is set to 0, it indicates that the AP will not send a Disassociation frame to disassociate from a non-AP STA; (4) A BSS Termination Included field indicating whether the BSS has terminated; (5) an extend service set (ESS) Disassociation Imminent field, which indicates whether the non-AP STA is disassociated from the entire ESS; (6) a disassociation timer field indicating the period of time that elapses before the AP sends a disassociation frame; (7) A validity interval field indicating the number of beacon periods for which the BSS transition candidate list is valid.

[0200] Figure 4c shows the frame structure of a BTM response frame, which includes a Category field, a wireless network management (WNM) Action field, a Dialog Token field, a BTM Status Code field, a BSS Termination Delay field, and a Target BSSID field.

[0201] The BTM Status Code field indicates whether the non-AP STA accepts the BTM request.

[0202] The BSS End Delay field indicates the amount of time to delay the BSS end.

[0203] The Target BSS Identifier field indicates the target BSSID of the BSS transition. In the case of a non-AP MLD, if the non-AP MLD wants to be forwarded to the AP MLD, the field is set to the MLD MAC Address of the AP MLD.

[0204] The frame structures of the BTM query frame, BTM request frame, and BTM response frame, as well as the functions of some fields, have been described above. For descriptions of other fields, please refer to the definitions in the relevant IEEE 802.11 standard. Details will not be described here.

[0205] 4.AP Collaboration Set

[0206] In an AP cooperation scenario, multiple APs may form an AP cooperation set, which includes at least one sharing AP (i.e., sharing AP) and at least one shared AP (i.e., shared AP).

[0207] In the AP cooperation process, the sharing AP may assign a duration to the shared AP for the shared AP to perform data transmission.

[0208] As described in the background section, an AP acting as a TXOP holder may allocate a portion of the duration in a TXOP to a non-AP STA for transmitting data. For example, as shown in FIG. 5, it is assumed that the AP acquires the TXOP after transmitting a clear to send (CTS) frame to the AP (CTS-to-self). The AP may then transmit a multi-user (MU) request to send (RTS) transmission opportunity sharing (TXOP sharing) trigger frame (TF). The MU-RTS TXS TF may indicate the duration and the non-AP STA (here, the transmission mode indicates whether the duration is used for P2P transmission or uplink transmission of the non-AP STA).

[0209] 5 is explained by using an example in which an AP allocates a duration A to a non-AP STA1 for its P2P transmission. After receiving the MU-RTS TXS TF, the non-AP STA1 may transmit a CTS frame and then transmit a single user (SU) physical layer protocol data unit (PPDU), i.e., an SU PPDU, to the non-AP STA2. The non-AP STA2 may return a block acknowledgement (BA) for the SU PPDU. After the duration allocated to the non-AP STA by the AP expires, the AP may continue to transmit the PPDU in the TXOP.

[0210] Optionally, before the AP transmits the MU-RTS TXS TF, the non-AP STA1 may transmit the transmission duration requested by the AP to the AP.

[0211] In a scenario involving a multi-link device, the TXOP sharing mechanism may have some problems. In consideration of this, the present application provides a buffer report transmission and reception method. The method is applicable to a scenario involving a multi-link device and is used to solve the problems associated with the TXOP sharing mechanism in the scenario.

[0212] The buffer report transmission and reception method provided in the present application will be described in detail below with reference to the accompanying drawings. The method provided in the present application is applicable to a Wi-Fi scenario or a WLAN scenario, for example, to IEEE 802.11 system standards, for example, 802.11a / b / g standard, 802.11n standard, 802.11ac standard, 802.11ax standard, next-generation standards (for example, 802.11be standard), or successor standards of next-generation standards. Alternatively, embodiments of the present application are applicable to wireless local area network systems, for example, Internet of Things (IoT) systems or vehicle-to-X (V2X) systems. It is clear that the embodiments of the present application are also applicable to other possible communication systems, such as a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, a universal mobile telecommunication system (UMTS), a worldwide interoperability for microwave access (WiMAX) communication system, and a fifth generation (5G) communication system.

[0213] The communication system applicable to the present application is only an example for explanation, and the communication system applicable to the present application is not limited thereto, which is uniformly described in this specification and will not be described again in detail below.

[0214] 6a shows a WLAN communication system to which embodiments of the present application are applicable according to the present application. The WLAN communication system includes an AP MLD 601 and a non-AP MLD 602.

[0215] The AP MLD 601 includes multiple associated APs. Figure 6a is explained by using an example in which the multiple associated APs include AP1, AP2, and AP3. The non-AP MLD 602 ​​includes multiple associated non-AP STAs. Figure 6a is explained by using an example in which the multiple associated non-AP STAs include non-AP STA1, non-AP STA2, and non-AP STA3.

[0216] Multiple uplinks / downlinks are set up between AP MLD 601 and non-AP MLD 602. Figure 6a is explained by using an example in which the multiple uplinks / downlinks include uplink / downlink 1 between AP1 and non-AP STA1, uplink / downlink 2 between AP2 and non-AP STA2, and uplink / downlink 3 between AP3 and non-AP STA3.

[0217] In addition, the WLAN communication system may further include at least one target non-AP STA, and a direct link is established between each target non-AP STA and an associated non-AP STA of the non-AP MLD 602. The target non-AP STA and the associated non-AP STA of the non-AP MLD 602 ​​at both ends of the direct link belong to the same BSS or are associated with the same AP of the AP MLD 601. The link identifiers of the direct link and the uplink / downlink in the same BSS are the same.

[0218] Optionally, the target non-AP STA may be a legacy STA, for example, the target non-AP STA 603 shown in FIG. 6a. A direct link 1 is set up between the target non-AP STA 603 and an associated non-AP STA 1 of the non-AP MLD 602, and an uplink / downlink link A is set up between the target non-AP STA 603 and AP 1 of the AP MLD 601. The target non-AP STA 603 and the associated non-AP STA 1 of the non-AP MLD 602 ​​belong to the BSS corresponding to AP 1 of the AP MLD 601. The link identifier of the direct link 1 is the same as the link identifier of the uplink / downlink 1.

[0219] Alternatively, the target non-AP STA may be an associated non-AP STA of a non-AP MLD, such as the target non-AP STA 604 shown in FIG. 6b. The target non-AP STA 604 is an associated non-AP STA of non-AP MLD A. A direct link 2 is set up between the target non-AP STA 604 and an associated non-AP STA 3 of the non-AP MLD 602, and an uplink / downlink link B is set up between the target non-AP STA 604 and AP 3 of the AP MLD 601. The target non-AP STA 604 and the associated non-AP STA 3 of the non-AP MLD 602 ​​belong to the BSS corresponding to AP 3 of the AP MLD 601. The link identifier of the direct link 2 is the same as the link identifier of the uplink / downlink 3.

[0220] 6b shows another WLAN communication system to which embodiments of the present application can be applied according to the present application. The WLAN communication system includes a sharing AP MLD 6011 and a shared AP MLD 6012.

[0221] The sharing AP MLD 6011 includes multiple associated APs. Figure 6b is explained by using an example where the multiple associated APs include AP A, AP B, and AP C. The shared AP MLD 6012 includes multiple associated APs. Figure 6b is explained by using an example where the multiple associated APs include AP a, AP b, and AP c.

[0222] Multiple links are set up between the sharing AP MLD 6011 and the shared AP MLD 6012. Figure 6b is explained by using an example where the multiple links include link 1 between AP A and AP a, link 2 between AP B and AP b, and link 3 between AP C and AP c.

[0223] In addition, the WLAN communication system may further include at least one target non-AP STA, and an uplink / downlink is set up between each target non-AP STA and an AP of the shared AP MLD 6012. The target non-AP STA and the AP of the shared AP MLD 6012 at both ends of the uplink / downlink belong to the same BSS or are associated with the same AP of the sharing AP MLD 6011. The link identifiers of the uplink / downlink and the link between the sharing AP and the shared AP in the same BSS are the same.

[0224] Optionally, the target non-AP STA may be a legacy STA, for example, the target non-AP STA 6013 shown in FIG. 6b. An uplink / downlink X is set up between the target non-AP STA 6013 and AP A of the shared AP MLD 6012, and an uplink / downlink A is set up between the target non-AP STA 6013 and AP A of the sharing AP MLD 6011. The target non-AP STA 6013 and AP a of the shared AP MLD 6012 belong to the BSS corresponding to AP A of the sharing AP MLD 6011. The link identifier of uplink / downlink X is the same as the link identifier of link 1.

[0225] Alternatively, the target non-AP STA may be an associated non-AP STA of the non-AP MLD, for example, the target non-AP STA 6014 shown in FIG. 6a. The target non-AP STA 6014 is an associated non-AP STA of the non-AP MLD A. An uplink / downlink Y is set up between the target non-AP STA 6014 and AP c of the shared AP MLD 6012, and an uplink / downlink B is set up between the target non-AP STA 6014 and AP C of the sharing AP MLD 6011. The target non-AP STA 6014 and AP c of the shared AP MLD 6012 belong to the BSS corresponding to AP C of the sharing AP MLD 6011. The link identifier of the uplink / downlink Y is the same as the link identifier of link 3.

[0226] The non-AP MLD in this application may be a wireless communication chip, a wireless sensor, or a wireless communication terminal, such as a user terminal, user device, access device, subscriber station, subscriber unit, mobile station, user agent, or user equipment, supporting Wi-Fi communication functions. The user terminal may include various devices with wireless communication functions, such as handheld devices, in-vehicle devices, wearable devices, Internet of Things (IoT) devices, computing devices, other processing devices connected to a wireless modem, various forms of user equipment (UE), mobile stations (MS), terminals, terminal devices, portable communication devices, handheld devices, portable computing devices, entertainment devices, gaming devices or systems, global positioning system devices, or any other suitable devices configured to perform network communication by using a wireless medium. Additionally, the non-AP MLD may support the 802.11be standard or the next-generation WLAN standard of the 802.11be standard. Non-AP MLD may also support multiple WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0227] The AP MLD in the embodiment of the present application provides wireless communication functions for non-AP STAs associated with the AP MLD and may be a device deployed in a wireless communication network, mainly deployed in homes, buildings, and parks. A typical coverage radius is from several tens of meters to several hundred meters. It is clear that the AP may alternatively be deployed outdoors. The AP MLD corresponds to a bridge connecting a wired network and a wireless network. The main function of the AP MLD is to connect various wireless network clients to each other and then connect the wireless network to an Ethernet. Specifically, the AP MLD may be a communication device with a Wi-Fi chip, such as a base station, router, gateway, repeater, communication server, switch, or bridge. The base station may include various forms of macro base station, micro base station, relay station, etc. In addition, the AP MLD may support the 802.11be standard or the next-generation WLAN standard of the 802.11be standard. AP MLD may also support WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0228] In the system shown in Figure 6a, the direct link setup is transparent to the AP MLD. In other words, the AP MLD cannot know the associated AP corresponding to the BSS to which the direct link is set up. Therefore, the AP MLD cannot know the direct link to which the transmission duration in the TXOP is assigned, and further, the transmission delay on the direct link may increase.

[0229] In consideration of this, the present application provides a buffer report transmission and reception method. Thus, an AP corresponding to a direct link of an AP MLD can decide to allocate a duration in a TXOP obtained by the AP for transmission on the direct link to an associated non-AP STA of a non-AP MLD, so as to transmit data on the direct link in a timely manner and reduce transmission delay on the direct link.

[0230] Hereinafter, with reference to the accompanying drawings, the buffer report sending and receiving method provided in the embodiment of the present application will be described in detail by using the interaction between the AP MLD 601 and the non-AP MLD 602 ​​shown in FIG. 6a as an example.

[0231] It can be understood that an executing entity may perform some or all of the steps in the embodiments of the present application. The steps or operations are merely examples. The embodiments of the present application may further include performing other operations or variations of various operations. In addition, the steps may be performed in an order different from that presented in the embodiments of the present application, and not all operations in the embodiments of the present application need to be performed.

[0232] 7 is a schematic flowchart of a buffer report sending and receiving method according to an embodiment of the present application. The method includes the following steps:

[0233] S701: A non-AP MLD generates a buffer report.

[0234] The buffer report is used to request a duration of a direct transmission performed by a first associated non-AP STA of the non-AP MLD on a first direct link. The first direct link is a link between the first target non-AP STA and the first associated non-AP STA of the non-AP MLD. The first target non-AP STA and the first associated non-AP STA of the non-AP MLD belong to the same BSS.

[0235] It can be understood that multiple direct links can be set up between multiple associated non-AP STAs of a non-AP MLD and multiple target non-AP STAs. This application will be described by using an example in which a first direct link is set up between a first associated non-AP STA of a non-AP MLD and a first target non-AP STA. For features and related implementations of a direct link set up between another associated non-AP STA of a non-AP MLD and another target non-AP STA, please refer to the description related to the first direct link and the first direct link in this application.

[0236] For example, as shown in Figure 6a, the first associated non-AP STA of the non-AP MLD may be non-AP STA3 of the non-AP MLD 602. Correspondingly, the first target non-AP STA is target non-AP STA 604, and the first direct link is direct link 2.

[0237] Alternatively, the first associated non-AP STA of the non-AP MLD may be non-AP STA1 of the non-AP MLD 602. Correspondingly, the first target non-AP STA is target non-AP STA 603, and the first direct link is direct link 1.

[0238] Regarding the information contained in the buffer report, there are two possible cases:

[0239] Case 1: The buffer report includes link information and transmission duration information.

[0240] The transmission duration information indicates a first transmission duration, where the first transmission duration is a duration of a direct transmission performed by a first associated non-AP STA of the non-AP MLD on a first direct link.

[0241] Optionally, the first transmission duration may be a normalized time length, which may be a duration determined based on a reference bandwidth (e.g., 80 MHz), a reference rate, etc.

[0242] In a possible implementation, the transmission duration information may include a size of a first buffer used to cache data to be transmitted on a first direct link by a first associated non-AP STA of the non-AP MLD or to cache data to be transmitted to a first target non-AP STA by the first associated non-AP STA of the non-AP MLD.

[0243] It may be understood that when multiple direct links are set up between a first associated non-AP STA of a non-AP MLD and multiple target non-AP STAs, the buffer report may not indicate the target non-AP STA at the end of the direct link that is not the first associated non-AP STA. In other words, the buffer report does not indicate the target non-AP STA, but indicates the direct link based on the link information.

[0244] For example, when the transmission duration information includes the size of the first buffer, the first transmission duration may be determined based on the size of the first buffer. For example, the first transmission duration may be calculated based on the size of the first buffer, a reference bandwidth, a reference rate, etc.

[0245] In another possible implementation, the transmission duration information may include a first transmission duration. For example, the first transmission duration may be determined based on a size of the first buffer, a reference bandwidth, a reference rate, etc.

[0246] In other words, when the transmission duration information includes the size of the first buffer, the transmission duration information implicitly indicates the first transmission duration. When the transmission duration information includes the first transmission duration, the transmission duration information explicitly indicates the first transmission duration.

[0247] The link information indicates the first direct link.

[0248] In a possible implementation, the link information may be an identifier of the first direct link. If the first direct link is Direct Link 1 shown in Fig. 6a, the identifier of the first direct link is the identifier of Direct Link 1. Since the identifier of Direct Link 1 is the same as the identifier of Uplink / Downlink 1, the identifier of Direct Link 1 is also the identifier of Uplink / Downlink 1.

[0249] In a particular example, when the link identifier information includes an identifier of a first direct link, for example, when the transmission duration information includes the size of a first buffer, the structure of the buffer report may be shown in Figure 8a. The link ID field is used to carry the identifier of the direct link, and the buffer size field is used to carry the buffer size.

[0250] Optionally, when the link identifier information includes an identifier of a first direct link, the buffer report may further include type information and / or information about the number of direct links. The type information indicates that one or more uplinks / downlinks are set up between the non-AP MLD and the AP MLD. The information about the number of direct links indicates the number N of direct links through which data should be transmitted. For example, in the system shown in FIG. 6a, there are two direct links. If data should be transmitted on direct link 1 and not on direct link 2, the number of direct links is 1. If data should be transmitted on both direct link 1 and direct link 2, the number of direct links is 2.

[0251] For example, the buffer report may further include type information and / or information about the number of direct links, and the structure of the buffer report may be shown in FIG. 8b. The type field is used to carry the type information. For example, when the type field is set to 1, this may indicate that multiple uplinks / downlinks are set up between the non-AP MLD and the AP MLD. When the type field is set to 0, this may indicate that one uplink / downlink is set up between the non-AP MLD and the AP MLD. The number of direct links field is used to carry information about the number of direct links.

[0252] For example, when N is greater than 1, i.e., when data is to be transmitted over multiple direct links, the link identifier field and buffer size field may be repeated N times. The N link identifier fields separately carry N link identifier information, and the N buffer size fields separately carry the sizes of N buffers.

[0253] In another possible implementation, the link information may be a bitmap. The size of the bitmap is the total number of uplinks / downlinks set up between the non-AP MLD and the AP MLD. For example, in the system shown in Figure 6a, the size of the bitmap is 3.

[0254] Optionally, each bit in the bitmap corresponds to one uplink / downlink set up between the non-AP MLD and the AP MLD. When data should be transmitted on a direct link whose identifier is the same as the identifier of the uplink / downlink, the bit corresponding to the direct link may be set to 1 to indicate that the direct link is a direct link whose identifier is the same as the identifier of the uplink / downlink corresponding to the bit.

[0255] For example, in the system shown in FIG. 6a, when the first direct link is direct link 1, the identifier of direct link 1 is the same as the identifier of uplink / downlink 1. The bits in the bitmap are assumed to correspond to uplink / downlink 1, uplink / downlink 2, and uplink / downlink 3, from left to right, and the bitmap may be set to 100. The first bit is set to 1, which indicates that the direct link is direct link 1, whose identifier is the same as the identifier of uplink / downlink 1 corresponding to the bit.

[0256] In a particular example, when the link identifier information includes a bitmap, for example, when the transmission duration information includes the size of the first buffer, the structure of the buffer report may be as shown in Figure 9a. The bitmap field is used to carry the bitmap, and the size of the field is the same as the size of the bitmap, and the buffer size field is used to carry the buffer size.

[0257] Optionally, when the link identifier information includes a bitmap, the buffer report may further include type information and / or bitmap size. For the function of the type information, see the related description above. The bitmap size indicates the size of the bitmap.

[0258] For example, the buffer report may further include type information and / or bitmap size, and the structure of the buffer report may be shown in Figure 9b. For the function of the type field, please refer to the related description above. The bitmap size field is used to carry the bitmap size.

[0259] For example, when data is to be transmitted over multiple direct links, the buffer size field may be repeated N times, with the N buffer size fields separately carrying the sizes of the N buffers. Additionally, a bitmap carried in the bitmap field indicates the multiple direct links. For example, in the scenario shown in FIG. 6a, if data is to be transmitted over both direct link 1 and direct link 2, the bitmap may be set to 101.

[0260] 8a to 9b, an example in which the transmission duration information includes a buffer size is used for explanation. When the transmission duration information includes a first transmission duration, the buffer size field in FIG. 8a to 9b can be replaced with a transmission duration field used to convey the transmission duration.

[0261] Case 2: The buffer report contains transmission duration information but no link information.

[0262] For the transmission duration information and link information, please refer to the related description in Case 1. The details will not be described again in this specification.

[0263] S702: The non-AP MLD sends a buffer report to the AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. In response, the AP MLD receives a buffer report from the non-AP MLD on the first uplink / downlink.

[0264] In one possible implementation, the buffer reporting is as described in Case 1, and the first uplink / downlink is any one of multiple uplinks / downlinks set up between non-AP MLD and AP MLD.

[0265] Please note that unless otherwise specified, uplinks / downlinks in this application are enabled uplinks / downlinks.

[0266] For example, in the scenario shown in FIG. 6a, if uplink / downlink 1, uplink / downlink 2, and uplink / downlink 3 are all enabled uplink / downlinks, the first uplink / downlink can be any one of uplink / downlink 1, uplink / downlink 2, or uplink / downlink 3.

[0267] In another possible implementation, the buffer reporting is as described in Case 2, and the first uplink / downlink is an uplink / downlink whose identifier is the same as the identifier of the first direct link among the multiple uplinks / downlinks set up between the non-AP MLD and the AP MLD. In other words, the identifier of the first uplink / downlink is the same as the identifier of the first direct link.

[0268] For example, in the scenario shown in FIG. 6a, if the first direct link is direct link 1, then the first uplink / downlink is uplink / downlink 1.

[0269] It may be understood that when the buffer report is as described in Case 2, if data is to be transmitted on multiple direct links, the buffer report needs to be transmitted separately on the uplink / downlink corresponding to each direct link. For example, in the scenario shown in FIG. 6a, if data is to be transmitted on both direct link 1 and direct link 3, the non-AP MLD sends a buffer report corresponding to direct link 1 to the AP MLD on uplink / downlink 1 to indicate the duration of the direct transmission on direct link 1, and sends a buffer report corresponding to direct link 3 to the AP MLD on uplink / downlink 3 to indicate the duration of the direct transmission on direct link 3.

[0270] Optionally, the content and transmission manner of the buffer report are as follows: The non-AP MLD may first determine the content of the buffer report, and then determine the uplink / downlink to be used for sending the buffer report to the AP MLD based on the content of the buffer report. Alternatively, the non-AP MLD may first determine the uplink / downlink to be used for sending the buffer report to the AP MLD, and then determine the content of the buffer report based on the determined uplink / downlink. This is not particularly limited in the present application.

[0271] The scheme for conveying the buffer report is as follows.

[0272] In a possible implementation, the buffer report may be carried in a management frame. In other words, the non-AP MLD transmitting the buffer report to the AP MLD on a first uplink / downlink of the multiple uplinks / downlinks may include: the non-AP MLD transmitting a management frame to the AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. The management frame includes the buffer report.

[0273] In a particular example, the buffer report may be carried in an aggregated control (A-control) field in a frame header of a management frame. In other words, the management frame includes an A-control field, and the A-control field includes the buffer report.

[0274] Optionally, the A-control field carrying the buffer report may be a newly defined type of A-control, and this type of A-control may carry a buffer report corresponding to a direct transmission. In other words, the buffer report carried in this type of A-control includes a buffer report corresponding to a direct transmission. It can be understood that the buffer report corresponding to a direct transmission is used to request the duration of the direct transmission on the direct link.

[0275] In another particular example, the buffer report may be carried in the frame body of a management frame.

[0276] Optionally, the management frame may be a newly defined type of management frame, and this type of management frame may carry a buffer report corresponding to a direct transmission. In other words, the buffer report carried in this type of management frame includes a buffer report corresponding to a direct transmission.

[0277] Optionally, when the buffer report is carried in a management frame, the frame header of the management frame may further include multilink device information, where the multilink device information indicates non-AP MLD.

[0278] In another possible implementation, the buffer report may be carried in an Aggregate Control (A-Control) field of the frame header of the data frame. In other words, it is not possible for a non-AP MLD to send a buffer report to an AP MLD on a first uplink / downlink of multiple uplinks / downlinks. It may include: a non-AP MLD sending a data frame to an AP MLD on a first uplink / downlink of a plurality of uplinks / downlinks, the data frame including an A-control field, and the A-control field including a buffer report.

[0279] Optionally, the A-control field carrying the buffer report may be a newly defined type of A-control, which may carry a buffer report corresponding to direct transmission. For details, please refer to the related description above. The details will not be described again in this specification.

[0280] In yet another possible implementation, the buffer report may be carried in a quality of service (QoS) control (i.e., QoS control) field of a data frame. For example, the data frame may be a QoS Null frame. In other words, the buffer report may be carried in the QoS control field of the QoS Null frame.

[0281] Optionally, when the buffer report is carried in a data frame, the frame header of the data frame may further include multilink device information, where the multilink device information indicates non-AP MLD.

[0282] S703: The AP MLD determines a second transmission duration.

[0283] Before step S703, the AP MLD may obtain TXOPs in multiple BSSs. The multiple BSSs are BSSs corresponding to multiple associated APs of the AP MLD individually. After receiving the buffer report, the AP MLD may know that a first associated non-AP STA of the non-AP MLD performs direct transmission on the first direct link, so that the associated AP corresponding to the first direct link of the AP MLD may decide to assign the first associated non-AP STA the duration in the TXOP obtained by the associated AP for transmission on the first direct link.

[0284] In other words, the second transmission duration includes the duration of a direct transmission on the first direct link assigned by the AP MLD to the first associated non-AP STA of the non-AP MLD, and the second transmission duration is the duration in the TXOP obtained by the associated AP of the AP MLD corresponding to the first direct link.

[0285] For example, in the scenario shown in FIG. 6a, when the first direct link is direct link 1, the associated AP of the AP MLD corresponding to the first direct link is AP1.

[0286] Optionally, the second transmission duration may be the same as or different from the first transmission duration, i.e., the duration assigned by AP MLD is not necessarily equal to the duration requested by non-AP MLD.

[0287] S704: The AP MLD sends first duration indication information, and in response, the non-AP MLD receives first duration indication information from the AP MLD.

[0288] The first duration indication indicates the second transmission duration. For example, the first duration indication may be carried in a trigger frame.

[0289] Optionally, the trigger frame carrying the first duration indication information may be an MU-RTS TXS TF, in which case the trigger frame may include information about a non-AP MLD to indicate that the second transmission duration is assigned to a first associated non-AP STA of the non-AP MLD.

[0290] Optionally, the trigger frame may further include first mode information, which may indicate that the second transmission duration is used by the first associated non-AP STA of the non-AP MLD to perform direct transmission and uplink transmission.

[0291] Optionally, when the first mode information indicates that the second transmission duration is used by a first associated non-AP STA of the non-AP MLD to perform direct transmission and uplink transmission, after receiving the trigger frame, the non-AP MLD may perform direct transmission and uplink transmission on the first direct link in the second transmission duration.

[0292] Based on this solution, the non-AP MLD sends a buffer report to the AP MLD. The buffer report can be used to request the duration of a direct transmission performed by a first associated non-AP STA of the non-AP MLD on a first direct link. Thus, after receiving the buffer report, the AP MLD can know that the first associated non-AP STA of the non-AP MLD will perform a direct transmission on the first direct link, and thereby the associated non-AP STA of the AP MLD corresponding to the first direct link can decide to assign the first associated non-AP STA the duration of the transmission on the first direct link in the TXOP obtained by the associated non-AP STA. In this way, data can be transmitted on the direct link in a timely manner, and the transmission delay on the direct link can be reduced.

[0293] The above-described embodiments are described using an example in which multiple uplinks / downlinks are set up between a non-AP MLD and an AP MLD. Appropriate modifications may be made so that the embodiments are applicable to a scenario in which only one uplink / downlink is set up between a non-AP MLD and an AP MLD, or a scenario in which one uplink / downlink is set up between a legacy STA and an AP MLD. For example, in the two scenarios, the buffer report may not carry link information, and the structure of the buffer report may be shown in Figure 10a. The type field is set to 0, indicating that one uplink / downlink is set up between a non-AP MLD (or a legacy STA) and an AP MLD.

[0294] The foregoing embodiment is described by using an example in which a non-AP MLD requests the duration of a direct transmission on a direct link. In addition, the non-AP MLD may further request the duration of an uplink transmission. In this case, the non-AP MLD may generate a direct buffer report, which is used to request the duration of the direct transmission, and an uplink buffer report, which is used to request the duration of the uplink transmission or report the uplink buffer size.

[0295] It may be understood that when a non-AP MLD reports both a direct buffer report and an uplink buffer report, the buffer report in the procedure shown in FIG. 7 may be considered as a direct buffer report.

[0296] In a possible implementation, the related implementation of the uplink buffer reporting is similar to that of the direct buffer reporting. For the uplink buffer reporting, please refer to the above description. The details will not be described again in this specification.

[0297] In another possible implementation, the uplink buffer report may include traffic identifier (TID) information and transmission duration information, and is used to request a transmission duration corresponding to the TID. Since there is a mapping relationship between the TID and the link (TID-to-link mapping), the AP MLD can determine, based on the buffer report, to allocate the duration in the TXOP obtained by the associated AP corresponding to the link corresponding to the TID for uplink transmission.

[0298] In yet another possible implementation, the uplink buffer report may include TID information and queue size information, where the queue size information indicates the queue size of the TID indicated by the TID information. Optionally, the duration for the uplink transmission requested by the uplink buffer report may be determined based on the queue size of the TID.

[0299] Optionally, in the uplink buffer report, the traffic identifier information may include a TID or a bitmap, and the transmission duration information may include a buffer size or a transmission duration. For details, please refer to the related descriptions of the link information and the transmission duration of the direct buffer report. The details will not be described again in this specification.

[0300] In a possible implementation, to distinguish between a direct buffer report and an uplink buffer report, based on the characteristics of the procedure shown in Figure 7, when a direct buffer report and an uplink buffer report are carried in the same type of A control or the same type of management frame, the buffer report may further include buffer type information. The buffer type information indicates whether the buffer report in which the buffer type information is located is a buffer report corresponding to a direct transmission or an uplink buffer report.

[0301] In another possible implementation, different types of management frames or different types of A-control may be used to carry the direct buffer report and the uplink buffer report, respectively.

[0302] In yet another possible implementation, based on the characteristics of the procedure shown in Figure 7, when a direct buffer report or an uplink buffer report is carried in the QoS Control field in a QoS Null frame, the buffer report may further include a Resource Request Type, which indicates whether the buffer report is used for an uplink resource request or a direct resource request.

[0303] Optionally, the resource request type may also be referred to as a buffer type. Correspondingly, the resource request type indicates whether the buffer report is used for an uplink resource request or a direct resource request, which can be understood as follows: the buffer type indicates whether the buffer report is an uplink buffer report or a direct buffer report.

[0304] Optionally, in this possible implementation, the direct buffer report may further include channel width information, where the channel width information indicates a reference bandwidth. For the reference bandwidth, please refer to the related description in step S701. Details will not be described again in this specification.

[0305] In a possible implementation, when the buffer report includes a resource request type, bit 7 in the QoS Control field of the QoS Null frame may be used to carry the resource request type. When bit 7 in the QoS Control field is set to a third value, this may indicate that the buffer report is used for uplink resource request. When bit 7 in the QoS Control field is set to a fourth value, this may indicate that the buffer report is used for direct resource request.

[0306] For example, the third value may be 0. Correspondingly, the fourth value may be 1. Alternatively, the third value may be 1. Correspondingly, the fourth value may be 0. For example, the third value is 1 and the fourth value is 1. The function or setting of each bit in the QoS Control field of a QoS Null frame may be shown in Table 2. [Table 2]

[0307] The TID field is used to carry TID information and indicates the TID corresponding to the buffer report.

[0308] The Ack Policy Indicator field indicates the acknowledgement policy to be used. For details, please refer to the relevant definitions in the 802.11be standard. Details will not be repeated here.

[0309] The Resource Request Type field indicates the resource request type.

[0310] The TXOP Duration Requested field is used to carry the transmission duration information of the buffer report and indicates the requested transmission duration. For example, when the TXOP Duration Requested field is set to 0, this indicates that no transmission duration is requested or that the transmission duration is 0. When the TXOP Duration Requested field is set to a non-zero value, the requested transmission duration may be the value of the field multiplied by 32 microseconds. Therefore, the transmission duration corresponding to the field may range from 32 microseconds to 8160 microseconds.

[0311] The Queue Size field carries queue size information and is used to indicate the queue size of the TID.

[0312] The Channel Width field is used to convey channel width information and indicates a reference bandwidth. For example, Table 3 may show the correspondence between the value of the Channel Width field and the reference bandwidth. [Table 3]

[0313] When the resource request type field is set to 0, this indicates that the buffer report is an uplink buffer report. When the resource request type field is set to 1, this indicates that the buffer report is a direct buffer report. Therefore, the settings shown in Table 2 may indicate that the uplink buffer report includes TID information, resource request type, and transmission duration information. Alternatively, the uplink buffer report includes TID information, resource request type information, and queue size information. The direct buffer report may include channel width information, resource request type, and transmission duration information.

[0314] Optionally, the QoS Null frame transmitted by the non-AP STA in Table 2 may be understood as a QoS Null frame transmitted to the AP when the non-AP STA supports TXS. In addition, the non-AP STA may be a non-AP EHT STA or a non-AP STA that supports future evolved WLAN standards.

[0315] In another possible implementation, bit 3 in the QoS Control field of the QoS Null frame may be used to carry the resource request type. When bit 3 in the QoS Control field is set to a third value, this may indicate that buffer reporting is used for uplink resource request. When bit 3 in the QoS Control field is set to a fourth value, this may indicate that buffer reporting is used for direct resource request.

[0316] For example, the third value is 1 and the fourth value is 1. Table 4 may show the function or setting of each bit in the QoS Control field of a QoS Null frame. [Table 4]

[0317] For Table 4, please refer to the relevant description of Table 2. Details will not be described again in this specification. It should be noted that Tables 2 and 4 are only examples in which an uplink buffer report includes TID information, resource request type, and transmission duration information. In the present application, an uplink buffer report is not limited to what is shown in Table 2 or Table 4. For example, the TID field in Table 2 and Table 4 may alternatively be replaced with a link information field used to carry link information. Similarly, a direct buffer report is not limited to what is shown in Table 2 or Table 4. For example, the channel width field in Table 2 and Table 4 may alternatively be replaced with a link information field used to carry link information.

[0318] Optionally, after the AP MLD receives the uplink buffer report, when the TID-to-link mapping is negotiated by the AP MLD and the non-AP MLD, the associated AP corresponding to the link corresponding to the TID may perform TXS in the obtained TXOP and allocate a duration for uplink transmission. When the TID-to-link mapping is set by default, any associated AP that sets up a link of the AP MLD with the non-AP MLD may perform TXS in the TXOP obtained by the associated AP and allocate a duration for uplink transmission.

[0319] The above embodiment provides a solution in which the direct buffer report is independent of the uplink buffer report. In addition, the present application further provides a buffer report transmission and reception method, in which the buffer report can be used to request the direct link transmission duration and the uplink transmission duration. As shown in Figure 10b, the buffer report transmission and reception method includes the following steps:

[0320] S1001: A non-AP MLD generates a buffer report.

[0321] The buffer report is used to request the duration of a transmission performed by a first associated non-AP STA of the non-AP MLD on a first link, including a first direct link and a first uplink / downlink.

[0322] The first direct link is a link between the first target non-AP STA and the first associated non-AP STA of the non-AP MLD. The first uplink / downlink is a link between the first associated AP of the AP MLD and the first associated non-AP STA of the non-AP MLD. The first target non-AP STA, the first associated non-AP STA of the non-AP MLD, and the first associated AP of the AP MLD belong to the same BSS.

[0323] For example, in the scenario shown in FIG. 6a, the first direct link may be direct link 1 and the first uplink / downlink may be uplink / downlink 1.

[0324] There are two possible implementations for the information contained in the buffer report:

[0325] In a possible implementation, the buffer report may include link information, transmission duration information, and second mode information. The second mode information indicates whether the transmission duration information indicates an uplink transmission duration or indicates a total duration of uplink transmission and direct transmission. For the link information and the transmission duration information, please refer to the related description in step S701. Details will not be described again in this specification.

[0326] Optionally, the second mode information may be 1-bit indication information. When the bit is set to 0, this indicates that the transmission information indicates the uplink transmission duration. When the bit is set to 1, this indicates that the transmission information indicates the total duration of the uplink transmission and the direct transmission.

[0327] For example, in the scenario shown in FIG. 6a, if an associated non-AP STA1 of non-AP MLD should transmit data on direct link 1 and should transmit uplink data on uplink / downlink 1, the second mode information of the buffer report may be set to 1. The transmission duration information is the sum of the sizes of the uplink buffer and the direct buffer, or the sum of the uplink transmission duration and the direct transmission duration. If an associated non-AP STA3 of non-AP MLD does not transmit direct data on direct link 2 and should transmit uplink data on uplink / downlink 3, the second mode information of the buffer report may be set to 0. The transmission duration information is the size of the uplink buffer or the uplink transmission duration.

[0328] It can be understood that the uplink buffer is used to cache uplink data to be transmitted, and the direct buffer is used to cache data to be transmitted on the direct link.

[0329] In another possible implementation, the buffer report may include transmission duration information and second mode information. For details, please refer to the relevant description of Case 2 in step S701. The details will not be described again in this specification.

[0330] S1002: The non-AP MLD sends a buffer report to the AP MLD on a second uplink / downlink of the multiple uplinks / downlinks.

[0331] Optionally, the second uplink / downlink can be any one of multiple uplinks / downlinks, or the second uplink / downlink is the same as the first uplink / downlink in step S1001. For details, please refer to the relevant description of step S702. The details will not be described again in this specification.

[0332] S1003: The AP MLD determines a third transmission duration.

[0333] The third transmission duration includes a duration of transmission on the first link assigned by the AP MLD to the first associated non-AP STA of the non-AP MLD, i.e., a duration of direct transmission on the first direct link and a duration of uplink transmission on the first uplink / downlink. The duration for direct transmission in the third transmission duration may be the duration in the TXOP obtained by the associated AP of the AP MLD corresponding to the first link. When the uplink buffer report includes a TID, if a TID-to-link mapping is negotiated by the AP MLD and the non-AP MLD, the duration for uplink transmission in the third transmission duration may be the duration in the TXOP obtained by the associated AP of the first uplink / downlink. When the TID-to-link mapping is set by default, the duration for uplink transmission in the third transmission duration may be the duration in the TXOP obtained by any associated AP of the AP MLD that sets up a link with the non-AP MLD.

[0334] S1004: The AP MLD sends second duration indication information, and in response, the non-AP MLD receives second duration indication information from the AP MLD.

[0335] The second duration indication information indicates a third transmission duration. For the second duration indication information, please refer to the related description in step S704. The details will not be described again in this specification.

[0336] Based on this solution, the non-AP MLD sends a buffer report to the AP MLD. The buffer report can be used to request the total duration of transmissions performed by a first associated non-AP STA of the non-AP MLD on the first direct link and the first uplink / downlink. Thus, after receiving the buffer report, the AP MLD can know that the first associated non-AP STA of the non-AP MLD should transmit on the first direct link and the first uplink / downlink. Thus, the associated AP of the AP MLD corresponding to the first direct link and the first uplink / downlink can decide to assign the first associated non-AP STA the duration of transmissions on the first direct link and the first uplink / downlink in the TXOP obtained by the associated AP. In this way, data can be transmitted in a timely manner, and transmission delays can be reduced.

[0337] In addition, the method provided in the above-mentioned embodiments of the present application may be further modified appropriately to be applicable to the scenario of an AP cooperating set. For example, the sharing AP MLD in the AP cooperating set may perform the function of the AP MLD in this method, and the shared AP MLD may perform the function of the non-AP MLD in this method. The difference lies in that the buffer report generated and transmitted by the shared AP MLD is used to request the duration of the transmission performed by the first associated AP of the shared AP MLD on the first uplink / downlink. The first uplink / downlink is the link between the first associated AP of the shared AP MLD and the target non-AP STA, for example, uplink / downlink X shown in Figure 6b.

[0338] Optionally, in addition to the solution in the TXOP sharing mechanism, the present application further provides some related solutions in a BSS transition scenario.

[0339] As can be seen from the brief introduction of the related art, a source AP MLD may send a BTM request frame to a non-AP MLD to request that the non-AP MLD be forwarded to the target AP MLD. Some fields of the BTM request frame are link-related. For example, the disassociation timer field and the validity interval field use the target beacon transmission time (TBTT) of the uplink / downlink as units. For example, the disassociation timer field indicates the number of TBTTs after which the disassociation frame is transmitted.

[0340] Normally, the BTM request frame can be transmitted on any enabled uplink / downlink between the source AP MLD and the non-AP MLD. However, if the uplink / downlink between the source AP MLD and the non-AP MLD is different, the TBTT and timing synchronization function (TSF) may be different. Therefore, when the BTM request frame is transmitted on any enabled uplink / downlink, the non-AP MLD cannot know the TBTT of the uplink / downlink used as the unit of the Disassociation Timer field and the Validity Interval field.

[0341] In consideration of this, the present application provides the following two methods to be used in a BSS transition scenario. For example, multiple uplinks / downlinks are set up between a source AP MLD and a non-AP MLD. As shown in Figure 11, the first method may include the following steps:

[0342] S1101: The source AP MLD generates a BTM request frame.

[0343] The BTM request frame includes indication information, and the indication information indicates that the disassociation timer and / or validity interval in the BTM request frame is in units of TBTT of one of multiple uplinks / downlinks.

[0344] Optionally, the indication information may be an identifier of one of the multiple uplinks / downlinks or a basic service set identifier (BSSID) corresponding to one of the multiple uplinks / downlinks.

[0345] For example, uplink / downlink A, uplink / downlink B, and uplink / downlink C are set up between the source AP MLD and the non-AP MLD. When the TBTT of uplink / downlink C is used as the unit of the disassociation timer and / or validity interval, the indication information may be an identifier of uplink / downlink C or a BSSID corresponding to uplink / downlink C.

[0346] S1102: The source AP MLD sends a BTM request frame to the non-AP MLD on any one of multiple uplinks / downlinks. In response, the non-AP MLD receives a BTM request frame from the source AP MLD on any uplink / downlink.

[0347] Correspondingly, based on the example of step S1101, the source AP MLD may send a BTM request frame to the non-AP MLD on any one of uplink / downlink A, uplink / downlink B, and uplink / downlink C.

[0348] Based on this solution, the source AP MLD adds indication information to the BTM request frame to indicate that the disassociation timer and / or validity interval in the BTM request frame is in units of one TBTT of multiple uplinks / downlinks. Therefore, the non-AP MLD can accurately obtain the time to send the disassociation frame or the validity time of the BSS transition candidate list, thereby improving the efficiency of BSS transition.

[0349] As shown in FIG. 12, the second method may include the following steps.

[0350] S1201: The source AP MLD generates a BTM request frame.

[0351] No indication information is added to the BTM request frame. For example, the frame structure of the BTM request frame may be shown in Figure 4b.

[0352] S1202: The source AP MLD sends a BTM request frame to the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. In response, the non-AP MLD receives a BTM request frame from the source AP MLD on the first uplink / downlink.

[0353] The disassociation timer and / or validity interval in the BTM request frame is in units of the TBTT of the first uplink / downlink of the multiple uplinks / downlinks. In other words, the disassociation timer and / or validity interval in the BTM request frame is in units of the TBTT of the uplink / downlink on which the BTM request frame is transmitted.

[0354] For example, uplink / downlink A, uplink / downlink B, and uplink / downlink C are set up between the source AP MLD and the non-AP MLD. If the TBTT of uplink / downlink C is used as the unit of the disassociation timer and / or valid interval, the source AP MLD sends a BTM request frame on uplink / downlink C to the non-AP MLD.

[0355] Based on this solution, the disassociation timer and / or validity interval in the BTM request frame are in units of the TBTT of the uplink / downlink used to transmit the BTM request frame, so that the non-AP MLD can accurately obtain the time to transmit the disassociation frame or the validity time of the BSS transition candidate list based on the uplink / downlink on which the BTM request frame is received, thereby improving the efficiency of BSS transition.

[0356] In addition, the present application further provides a method for describing the content and field settings carried in a neighbor report element carried in a BTM request frame. As shown in Figure 13, the method includes the following steps:

[0357] S1301: The source AP MLD generates a BTM request frame.

[0358] The BTM request frame includes one or more neighbor report elements, which indicate candidate APs recommended by the source AP MLD for non-AP MLD.

[0359] When the candidate AP belongs to the candidate AP MLD or is an associated AP of the candidate AP MLD, the neighbor report element may include a basic modified multilink element as a subelement. The basic modified multilink element includes a multilink control field and a common information field, but does not include a link information field. For the structures of the multilink control field, common information field, and link information field, please refer to the related description of Figure 2. Details will not be described again in this specification.

[0360] S1302: The source AP MLD sends a BTM request frame to the non-AP MLD. In response, the non-AP MLD receives a BTM request frame from the source AP MLD.

[0361] Optionally, the source AP MLD may send a BTM request frame to the non-AP MLD on any uplink / downlink.

[0362] Based on this solution, the basic variant multilink element does not carry the link information field because link information does not need to be acquired during BSS transition, which can reduce signaling overhead and does not affect BSS transition.

[0363] Optionally, in step S1301, an MLD MAC address presence field in the multilink control field may be set to a first value, and a first presence field in the multilink control field may be set to a second value. The first presence field may include a link identifier information presence field and a BSS parameter change count presence field.

[0364] A first value indicates that the field is present in the common information field, and a second value indicates that the field is not present in the common information field. For example, when the MLD MAC address present field is set to a first value, this indicates that the MLD MAC address field is present in the common information field. When the link identifier information present field is set to a second value, this indicates that the link identifier information field is not present in the common information field.

[0365] For example, the first value may be 1. Correspondingly, the second value may be 0. Alternatively, the first value may be 0. Correspondingly, the second value may be 1.

[0366] Optionally, when the BTM request frame includes multiple neighbor report elements and the candidate APs indicated by the multiple neighbor report elements belong to the same candidate AP MLD, a second presence field in a multilink control field included in a first basic variant multilink element is set to a first value, and a second presence field in a multilink control field included in a second basic variant multilink element is set to a second value. The first basic variant multilink element is a basic variant multilink element included in a first neighbor report element of the multiple neighbor report elements, and the second basic variant multilink element is a basic variant multilink element included in a neighbor report element other than the first neighbor report element of the multiple neighbor report elements.

[0367] For example, a BTM request frame may include three neighbor report elements, each indicating candidate AP1, candidate AP2, and candidate AP3, which belong to the same candidate AP MLD. The first neighbor report element may be the neighbor report element indicating candidate AP1, and the first basic variant multilink element may be the basic variant multilink element within the neighbor report element indicating candidate AP1. The second basic variant multilink element may include the basic variant multilink element within the neighbor report element indicating candidate AP2 and the basic variant multilink element within the neighbor report element indicating candidate AP3.

[0368] Optionally, the second presence field may include one or more of a media synchronization delay information presence field, an EML capability presence field, or an MLD presence field.

[0369] Based on the solution, when multiple candidate APs indicated by the same BTM request frame belong to the same AP MLD, a first neighbor report element indicating that the associated AP of the AP MLD is a candidate AP carries a basic modified multilink element, and a second presence field in the multilink control field included in the basic modified multilink element is set to a first value, and a second presence field in the multilink control field included in the basic modified multilink element of another neighbor report element indicating that the associated AP of the AP MLD is a candidate AP is set to a second value. Therefore, to avoid repeatedly carrying the same field, the BTM request frame carries the field indicated by the second presence field (one or more of the medium synchronization delay information presence field, the EML capability presence field, or the MLD presence field) only once. This can reduce signaling overhead.

[0370] The method in the embodiment of the present application has been described above. The communication device in the embodiment of the present application will now be described. The communication device in the embodiment of the present application includes a first communication device, a second communication device, and a third communication device. It should be understood that the first communication device is a non-AP MLD in the method and has any function of the non-AP MLD in the method. The second communication device is an AP MLD in the method and has any function of the AP MLD in the method. The third communication device is a source AP MLD in the method and has any function of the source AP MLD in the method.

[0371] As shown in FIG. 14, the first communication device includes a processing module and a transceiver module.

[0372] The processing module is configured to generate a buffer report, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between the first target non-AP STA and the first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0373] The transceiver module is configured to transmit the buffer report to the AP MLD on a first uplink / downlink of the plurality of uplinks / downlinks.

[0374] Optionally, the processing module and the transceiver module in the first communication device may have some of the following relationships with non-AP MLD: (1) The processing module and the transceiver module are the processing module and the transceiver module in the first associated non-AP STA of the non-AP MLD; (2) The processing module and the transceiver module are the central processing module and the central transceiver module in the non-AP MLD; (3) the processing module is a processing module in a first associated non-AP STA of the non-AP MLD, and the transceiver module is a central transceiver module in the non-AP MLD; (4) The processing module is a central processing module in the non-AP MLD, and the transceiver module is a transceiver module in a first associated non-AP STA of the non-AP MLD.

[0375] It should be understood that the first communication device provided in this embodiment of the present application is a non-AP MLD in the present method, and has any function of the non-AP MLD in the method shown in Figure 7. For specific details, please refer to the method. The details will not be described again in this specification.

[0376] As shown in FIG. 15, the second communication device includes a processing module and a transceiver module.

[0377] The transceiver module is configured to receive a buffer report from the non-AP MLD on a first uplink / downlink of the plurality of uplinks / downlinks, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between a first target non-AP STA and a first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0378] The processing module is configured to determine a second transmission duration, the second transmission duration including a duration of direct transmission on the first direct link assigned by the AP MLD to the first associated non-AP STA of the non-AP MLD.

[0379] The transceiver module is further configured to transmit a first duration indication, the first duration indication indicating the second transmission duration.

[0380] Optionally, the processing module and the transceiver module in the second communication device may have some of the following relationships with the AP MLD: (1) The processing module and the transceiver module are processing modules and transceiver modules in the associated AP of the AP MLD corresponding to the first direct link; (2) The processing module and the transceiver module are the central processing module and the central transceiver module in the AP MLD; (3) the processing module is a processing module in an associated AP of the AP MLD corresponding to the first direct link, and the transceiver module is a central transceiver module in the AP MLD; (4) The processing module is a central processing module in the AP MLD, and the transceiver module is a transceiver module in the associated AP of the AP MLD corresponding to the first direct link.

[0381] It should be understood that the second communication device provided in this embodiment of the present application is the AP MLD in this method, and has any function of the AP MLD in the method shown in Figure 7. For specific details, please refer to the method. The details will not be described again in this specification.

[0382] As shown in FIG. 16, the third communication device includes a processing module and a transceiver module.

[0383] The processing module is configured to generate a basic service set transition management (BTM) request frame. The BTM request frame includes indication information, where the indication information indicates that a disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of one uplink / downlink of the multiple uplinks / downlinks. The transceiver module is configured to transmit the BTM request frame to the non-AP MLD on any one of the multiple uplinks / downlinks.

[0384] Alternatively, the processing module is configured to generate a basic service set transition management (BTM) request frame. The transceiver module is configured to transmit the BTM request frame to the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. The disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of the first uplink / downlink of the multiple uplinks / downlinks.

[0385] Alternatively, the processing module is configured to generate a basic service set transition management (BTM) request frame. The BTM request frame includes one or more neighbor report elements, where the neighbor report elements indicate candidate access points (APs) recommended by the source AP MLD to the non-AP MLD. When the candidate access points belong to the candidate AP MLD, the neighbor report elements include a basic modified multilink element, where the basic modified multilink element includes a multilink control field and a common information field, but does not include a link information field. The transceiver module is configured to transmit the BTM request frame to the non-AP MLD.

[0386] Optionally, the processing module and the transceiver module in the third communication device may have some of the following relationships with the source AP MLD: (1) The processing module and the transceiver module are the processing module and the transceiver module in the associated AP of the source AP MLD; (2) The processing module and the transceiver module are the central processing module and the central transceiver module in the source AP MLD; (3) The processing module is a processing module in the associated AP of the source AP MLD, and the transceiver module is a central transceiver module in the source AP MLD; (4) The processing module is a central processing module in the source AP MLD, and the transceiver module is a transceiver module in the associated AP of the source AP MLD.

[0387] It should be understood that the third communication device provided in this embodiment of the present application is the source AP MLD in this method, and has any function of the source AP MLD in the method shown in Figure 11, Figure 12, or Figure 13. For specific details, please refer to the method. The details will not be described again in this specification.

[0388] The first communication device, the second communication device, and the third communication device in the embodiments of the present application have been described above. Hereinafter, possible product forms of the first communication device, the second communication device, and the third communication device will be described. It should be understood that any product form having the features of the first communication device described in FIG. 14, any product form having the features of the second communication device described in FIG. 15, and any product form having the features of the third communication device described in FIG. 16 fall within the scope of protection of the present application. It should be further understood that the following description is merely an example and does not limit the product forms of the first communication device, the second communication device, and the third communication device in the embodiments of the present application.

[0389] As a possible product form, the first communication device, the second communication device and the third communication device described in the embodiments of the present application may be implemented by using a general-purpose bus architecture.

[0390] The first communication device includes a processor and a transceiver internally coupled to the processor for communication with the processor.

[0391] The processor is configured to generate a buffer report, the buffer report used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between the first target non-AP STA and the first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0392] The transceiver is configured to transmit a buffer report to the AP MLD on a first uplink / downlink of the plurality of uplinks / downlinks.

[0393] Optionally, the first communication device may further include a memory configured to store instructions to be executed by the processor.

[0394] The second communication device includes a processor and a transceiver internally coupled to the processor for communication with the processor.

[0395] The transceiver is configured to receive a buffer report from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between a first target non-AP STA and a first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0396] The processor is configured to determine a second transmission duration, the second transmission duration comprising a duration of direct transmission on the first direct link assigned by the AP MLD to the first associated non-AP STA of the non-AP MLD.

[0397] The transceiver is further configured to transmit a first duration indication, the first duration indication indicating the second transmission duration.

[0398] Optionally, the second communication device may further include a memory configured to store instructions to be executed by the processor.

[0399] The third communication device includes a processor and a transceiver internally coupled to the processor for communication with the processor.

[0400] The processor is configured to generate a basic service set transition management (BTM) request frame. The BTM request frame includes instruction information, and the instruction information indicates that a disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of one uplink / downlink of the multiple uplinks / downlinks. The transceiver is configured to transmit the BTM request frame to the non-AP MLD on any one of the multiple uplinks / downlinks.

[0401] Alternatively, the processor is configured to generate a basic service set transition management (BTM) request frame. The transceiver is configured to transmit the BTM request frame to the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. The disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of the first uplink / downlink of the multiple uplinks / downlinks.

[0402] Alternatively, the processor is configured to generate a basic service set transition management (BTM) request frame. The BTM request frame includes one or more neighbor report elements, where the neighbor report elements indicate candidate access points (APs) recommended by the source AP MLD to the non-AP MLD. When the candidate access points belong to the candidate AP MLD, the neighbor report elements include a basic modified multilink element, where the basic modified multilink element includes a multilink control field and a common information field, but does not include a link information field. The transceiver is configured to transmit the BTM request frame to the non-AP MLD.

[0403] Optionally, the third communication device may further include a memory configured to store instructions to be executed by the processor.

[0404] As another possible product form, the first communication device, the second communication device, and the third communication device described in the embodiments of the present application may be implemented by using a general-purpose processor.

[0405] A general-purpose processor implementing the first communication device includes a processing circuit and an output interface interconnected to and in communication with the processing circuit.

[0406] The processing circuitry is configured to generate a buffer report, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between the first target non-AP STA and the first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0407] The output interface is configured to send the buffer report to the AP MLD on a first uplink / downlink of the plurality of uplinks / downlinks.

[0408] Optionally, the general-purpose processor may further include a storage medium configured to store instructions executed by the processing circuitry.

[0409] A general-purpose processor implementing the second communication device includes a processing circuit, and an output interface and an input interface interconnected to and in communication with the processing circuit.

[0410] The input interface is configured to receive a buffer report from the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between a first target non-AP STA and a first associated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS).

[0411] The processing circuitry is configured to determine a second transmission duration, the second transmission duration comprising a duration of direct transmission on the first direct link assigned by the AP MLD to the first associated non-AP STA of the non-AP MLD.

[0412] The output interface is further configured to transmit a first duration indication, the first duration indication indicating the second transmission duration.

[0413] Optionally, the general-purpose processor may further include a storage medium configured to store instructions executed by the processing circuitry.

[0414] A general-purpose processor implementing the third communication device includes a processing circuit and an output interface interconnected to and in communication with the processing circuit.

[0415] The processing circuit is configured to generate a basic service set transition management (BTM) request frame. The BTM request frame includes instruction information, and the instruction information indicates that a disassociation timer and / or a validity interval in the BTM request frame are in units of a target beacon transmission time (TBTT) of one uplink / downlink of the multiple uplinks / downlinks. The output interface is configured to transmit the BTM request frame to the non-AP MLD on any one of the multiple uplinks / downlinks.

[0416] Alternatively, the processing circuitry is configured to generate a basic service set transition management (BTM) request frame. The output interface is configured to transmit the BTM request frame to the non-AP MLD on a first uplink / downlink of the multiple uplinks / downlinks. The disassociation timer and / or validity interval in the BTM request frame is in units of a target beacon transmission time (TBTT) of the first uplink / downlink of the multiple uplinks / downlinks.

[0417] Alternatively, the processing circuit is configured to generate a basic service set transition management (BTM) request frame. The BTM request frame includes one or more neighbor report elements, where the neighbor report elements indicate candidate access points (APs) recommended by the source AP MLD to the non-AP MLD. When the candidate access points belong to the candidate AP MLD, the neighbor report elements include a basic modified multilink element, where the basic modified multilink element includes a multilink control field and a common information field, but does not include a link information field. The output interface is configured to transmit the BTM request frame to the non-AP MLD.

[0418] Optionally, the general-purpose processor may further include a storage medium configured to store instructions executed by the processing circuitry.

[0419] As yet another possible product form, the first communication device, the second communication device, and the third communication device described in the embodiments of the present application may be further implemented by using the following components: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuitry, or any combination of circuitry capable of performing the various functions described in the present application.

[0420] It should be understood that the first communication device, the second communication device, and the third communication device in various product forms each have any of the functions of non-AP MLD, AP MLD, and source AP MLD in the method embodiment, and the details will not be described again in this specification.

[0421] Those skilled in the art may recognize that, in combination with the examples described in the embodiments disclosed herein, the method steps and units may be implemented by electronic hardware, computer software, or a combination thereof. In order to clearly explain the compatibility between hardware and software, the above generally describes the steps and configurations of each embodiment based on functions. Whether a function is performed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0422] For convenience and concise description, it can be clearly understood by those skilled in the art that the detailed operation processes of the described systems, devices and units can be referred to the corresponding processes in the method embodiments, and the details will not be described again in this specification.

[0423] In some embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the described device embodiments are merely examples. For example, the division into units is merely a logical division of function, and other divisions may occur in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. In addition, the shown or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. Indirect couplings or communication connections between devices or units may be implemented in electrical, mechanical, or other forms.

[0424] The units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, in other words, they may be located in one location or distributed over multiple network units. To achieve the objectives of the solutions of the embodiments in this application, some or all of the units may be selected based on actual requirements.

[0425] In addition, the functional units in the embodiments of the present application may be integrated into one processing unit, each unit may exist physically independently, or two or more units may be integrated into one unit. The integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0426] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application, or a portion contributing to the prior art, or all or a portion of the technical solution, may be implemented in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or a portion of the steps of the method described in the embodiments of the present application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0427] The above description is merely a specific embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications or replacements that can be easily conceived by those skilled in the art within the technical scope disclosed in the present application shall fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. A buffer report transmission method, the method being applied to a non-AP multilink device (non-AP MLD), and multiple uplinks or downlinks are set up between the non-AP MLD and an access point multilink device (AP MLD), the method comprising: generating, by the non-AP MLD, a buffer report, the buffer report being used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between a first target non-AP STA and the first associated non-AP STA of the non-AP MLD, the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS); transmitting, by the non-AP MLD, the buffer report to the AP MLD on a first uplink or downlink of the plurality of uplinks or downlinks; Including, The method, wherein the buffer report further includes buffer type information, and the buffer type information indicates that the buffer report is a buffer report corresponding to a direct transmission.

2. The method of claim 1 , wherein the buffer report includes link information, the link information indicating the first direct link.

3. The method of claim 2 , wherein the link information is an identifier or a bitmap of the first direct link.

4. 2. The method of claim 1, wherein the buffer report includes link information and does not include link information indicating the first direct link, and transmission duration information indicates a first transmission duration, the first transmission duration being a duration of the direct transmission performed by the first associated non-AP STA of the non-AP MLD on the first direct link.

5. The method of claim 4 , wherein the identifier of the first uplink or downlink is the same as the identifier of the first direct link.

6. A buffer report receiving method, the method being applied to an access point multilink device (AP MLD), where multiple uplinks or downlinks are set up between the AP MLD and a non-access point multilink device (non-AP MLD), the method comprising: receiving, by the AP MLD, from the non-AP MLD on a first uplink or downlink of the plurality of uplinks or downlinks, a buffer report used to request a duration of a direct transmission performed by a first associated non-access point station (non-AP STA) of the non-AP MLD on a first direct link, the first direct link being a link between a first target non-AP STA and the first associated non-AP STA of the non-AP MLD, the first target non-AP STA and the first associated non-AP STA of the non-AP MLD belonging to the same basic service set (BSS); The method, wherein the buffer report further includes buffer type information, and the buffer type information indicates that the buffer report is a buffer report corresponding to a direct transmission.

7. The method comprises: determining, by the AP MLD, a second transmission duration, the second transmission duration comprising a duration of the direct transmission on the first direct link assigned by the AP MLD to the first associated non-AP STA of the non-AP MLD; transmitting, by the AP MLD, a first duration indication, wherein the first duration indication indicates the second transmission duration; The method of claim 6 further comprising:

8. The method of claim 6 , wherein the buffer report includes link information, the link information indicating the first direct link.

9. The method of claim 8 , wherein the link information is an identifier or a bitmap of the first direct link.

10. 7. The method of claim 6, wherein the buffer report includes link information and does not include link information indicating the first direct link, and transmission duration information indicates a first transmission duration, the first transmission duration being a duration of the direct transmission performed by the first associated non-AP STA of the non-AP MLD on the first direct link.

11. The method of claim 10 , wherein the identifier of the first uplink or downlink is the same as the identifier of the first direct link.

12. 12. A computer readable storage medium configured to store a computer program, the computer program comprising instructions used to perform the method of any one of claims 1 to 11.

13. A communication device, the communication device being applied to a non-access point multi-link device (non-AP MLD), the communication device being configured to perform the method according to any one of claims 1 to 11.

Images