WO2023001221A1 - 缓冲区报告发送、接收方法及装置 - Google Patents

缓冲区报告发送、接收方法及装置 Download PDF

Info

Publication number
WO2023001221A1
WO2023001221A1 PCT/CN2022/106968 CN2022106968W WO2023001221A1 WO 2023001221 A1 WO2023001221 A1 WO 2023001221A1 CN 2022106968 W CN2022106968 W CN 2022106968W WO 2023001221 A1 WO2023001221 A1 WO 2023001221A1
Authority
WO
WIPO (PCT)
Prior art keywords
mld
link
sta
information
uplink
Prior art date
Application number
PCT/CN2022/106968
Other languages
English (en)
French (fr)
Inventor
黄国刚
李云波
郭宇宸
淦明
李伊青
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN202111093436.6A external-priority patent/CN115696275A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to CA3227140A priority Critical patent/CA3227140A1/en
Priority to KR1020247004807A priority patent/KR20240027839A/ko
Priority to AU2022314029A priority patent/AU2022314029A1/en
Priority to CN202280050960.1A priority patent/CN117751665A/zh
Priority to EP22845385.8A priority patent/EP4358619A1/en
Publication of WO2023001221A1 publication Critical patent/WO2023001221A1/zh
Priority to US18/413,795 priority patent/US20240155717A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H04W72/0446—Resources in time domain, e.g. slots or frames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/40—Resource management for direct mode communication, e.g. D2D or sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices

Definitions

  • the present application relates to the technical field of communication, in particular to a buffer report sending and receiving method and device.
  • Wireless fidelity (Wi-Fi) systems are deployed on unlicensed spectrum, and stations (stations, STAs) in the system use channel resources through competition. After a station successfully competes for a channel, it can reserve a period of time for data transmission, and this period of time is called a transmission opportunity (TXOP).
  • TXOP transmission opportunity
  • a station that successfully reserves a TXOP is called a TXOP holder. In a TXOP, only the TXOP holder can actively send data, and other stations can only receive data or send response frames for the data they receive.
  • the TXOP mechanism is extended as follows: as the access point station (AP STA) of the TXOP holder, it can be reserved Part of the time in the TXOP is allocated to a non-access point station (non-access point station, non-AP STA), so that the non-AP STA performs point-to-point (point-to-point) with another non-AP STA within the allocated time point to point, P2P) transmission, or send uplink data to the AP STA.
  • AP STA access point station
  • non-AP STA non-access point station
  • P2P point-to-point
  • the AP STA as the TXOP holder allocates part of the TXOP time for the non-AP STA, it may need to know the transmission duration required by the non-AP STA.
  • the embodiment of the present application provides a buffer report sending and receiving method and device, so that the AP corresponding to the direct link in the AP MLD can determine to allocate a period of time for a certain subordinate non-AP STA in a certain TXOP obtained by it, It is used for transmission on the direct link, so that the data on the direct link can be sent in time, and the transmission delay on the direct link is reduced.
  • a buffer report sending method is provided, the method is applied to a non-AP MLD of a non-AP multilink device, and how many links are established between the non-AP MLD and the AP MLD uplink and downlink.
  • the method includes: the non-AP MLD generates a buffer report, and sends the buffer report to the AP MLD on the first uplink and downlink among the plurality of uplinks and downlinks.
  • the buffer report is used to request the first affiliated non-AP station non-AP STA in the non-AP MLD to perform direct transmission on the first direct link
  • the first direct link is the first direct link A link between a target non-AP STA and the first subordinate non-AP STA of the non-AP MLD, the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD belong to the same basic service set BSS.
  • the non-AP MLD sends a buffer report to the AP MLD, which can be used to request the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link
  • the AP MLD can learn that the first non-AP STA subordinate to the non-AP MLD is to perform direct transmission on the first direct link, so that the AP MLD and the first direct link
  • the affiliated AP corresponding to the connected link can allocate a period of time for the first affiliated non-AP STA within a certain TXOP obtained by it for transmission on the first direct link, so that the data on the direct link It can be sent in time to reduce the transmission delay on the direct link.
  • the buffer report includes link information, where the link information is used to indicate the above-mentioned first direct link.
  • the link information is an identifier of the first direct link, or the link information is a bitmap.
  • the identifier of the direct link can explicitly indicate the direct link, and the bitmap can implicitly indicate the direct link.
  • the buffer report includes transmission duration information, and the transmission duration information is used to indicate the first transmission duration. The duration of direct transmission on the link.
  • the first uplink and downlink is any one of multiple uplinks and downlinks.
  • non-AP MLD can send buffer reports to AP MLD on any uplink and downlink, which can improve the flexibility of sending buffer reports.
  • the buffer report also includes buffer type information, and the buffer type information is used to indicate that the buffer report is a buffer report corresponding to direct connection transmission.
  • the buffer report is the buffer report corresponding to the direct connection transmission, so that the AP MLD allocates the transmission duration within a certain TXOP obtained by the subordinate AP corresponding to the direct connection link.
  • the buffer report includes link information and does not include link information indicating the first direct link
  • the transmission duration information is used to indicate the first transmission duration
  • the first transmission duration is non -The length of time that the first subordinate non-AP STA in the AP MLD performs direct transmission on the first direct link.
  • the identifier of the first uplink and downlink is the same as the identifier of the first direct link.
  • the transmission duration information includes the first transmission duration or the size of the first buffer, and the first buffer is used to cache the first subordinate non-AP STA in the non-AP MLD to wait for the first direct link data sent on the road.
  • the non-AP MLD sends a buffer report to the AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, including: Send a management frame to the AP MLD on the first uplink and downlink, and the management frame includes a buffer report. Based on this possible design, the buffer report can be carried by the management frame.
  • the above management frame may include an aggregation control field, and the aggregation control field includes a buffer report. Based on this possible design, the buffer report can be carried through the aggregation control field of the management frame.
  • the frame header of the management frame includes multi-link device information, and the multi-link device information is used to indicate non-AP MLD.
  • the non-AP MLD sends a buffer report to the AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, including: Send a data frame to the AP MLD on the first uplink and downlink, the data frame includes an aggregation control field, and the aggregation control includes a buffer report.
  • the buffer report can be carried through the aggregation control field of the data frame.
  • the frame header of the data frame includes multi-link device information, and the multi-link device information is used to indicate non-AP MLD. Based on this possible design, the non-AP MLD that requests the direct connection transmission duration can be indicated to the AP MLD.
  • non-AP MLD sends a buffer report to AP MLD on the first uplink and downlink among multiple uplinks and downlinks, which may include: non-AP MLD in multiple uplinks and downlinks Send a data frame to the AP MLD on the first uplink and downlink, the data frame includes a QoS control field, and the QoS control field includes a buffer report.
  • the data frame is a QoS Null frame.
  • the buffer report further includes a resource request type, where the resource request type is used to indicate that the buffer report is a buffer report corresponding to direct connection transmission.
  • Bit 7 or Bit 3 of the QoS control field in the QoS Null frame is used to carry the resource request type.
  • a method for sending a buffer report is provided, the method is applied to an access point multi-link device AP MLD, and multiple uplinks and downlinks are established between the AP MLD and the non-AP multi-link device non-AP MLD link.
  • the method includes: the AP MLD receives a buffer report from a non-AP MLD on the first uplink and downlink among multiple uplinks and downlinks, and the buffer report is used to request the first subordinate contactless in the non-AP MLD The length of time for the non-AP STA at the entry point to perform direct transmission on the first direct link.
  • the first direct link is between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD.
  • the link between the first target non-AP STA and the first affiliated non-AP STA of the non-AP MLD belong to the same basic service set BSS; after that, the AP MLD determines the second transmission duration and sends the first duration indication information,
  • the first duration indication information is used to indicate the second transmission duration.
  • the second transmission duration includes the duration allocated by the AP MLD for the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link.
  • the buffer report received by the AP MLD can be used to request the first affiliated non-AP STA in the non-AP MLD to perform direct transmission on the first direct link, so that the AP MLD can know the non-AP MLD -The first subordinate non-AP STA of the AP MLD is to perform direct transmission on the first direct link, so that the subordinate AP corresponding to the first direct link in the AP MLD can obtain a certain TXOP within the AP MLD Allocate a period of time for the first affiliated non-AP STA for transmission on the first direct link, so that the data on the direct link can be sent in time and reduce the transmission delay on the direct link.
  • the buffer report includes link information, where the link information is used to indicate the above-mentioned first direct link.
  • the link information is an identifier of the first direct link, or the link information is a bitmap.
  • the buffer report includes transmission duration information, and the transmission duration information is used to indicate the first transmission duration. The duration of direct transmission on the link.
  • the above-mentioned first uplink and downlink is any uplink and downlink among multiple uplinks and downlinks.
  • the buffer report further includes buffer type information, and the buffer type information is used to indicate that the buffer report is a buffer report corresponding to direct connection transmission.
  • the buffer report includes link information and does not include link information for indicating the first direct link, and the transmission duration information is used to indicate the first transmission duration, and the first transmission duration is non- The duration of direct transmission on the first direct link of the first subordinate non-AP STA in the AP MLD.
  • the identifier of the first uplink and downlink is the same as the identifier of the first direct link.
  • the transmission duration information includes the first transmission duration or the size of the first buffer, and the first buffer is used to cache the first subordinate non-AP STA in the non-AP MLD to wait for the first direct link data sent on the road.
  • the AP MLD receives the buffer report from the non-AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, including: the first uplink and downlink of the AP MLD - Receive a management frame from the non-AP MLD on the uplink and downlink, the management frame including the buffer report.
  • the management frame may include an aggregate control field that includes a buffer report.
  • the frame header of the management frame includes multi-link device information, and the multi-link device information is used to indicate non-AP MLD.
  • the AP MLD receives the buffer report from the non-AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, including: the first uplink and downlink of the AP MLD A data frame from the non-AP MLD is received on the uplink and downlink, the data frame includes an aggregation control field, and the aggregation control includes a buffer report.
  • the frame header of the data frame includes multi-link device information, and the multi-link device information is used to indicate non-AP MLD.
  • the AP MLD receives the buffer report from the non-AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, including: the first uplink and downlink of the AP MLD
  • a data frame from the non-AP MLD is received on the uplink and downlink, the data frame includes a QoS control field, and the QoS control field includes a buffer report.
  • the data frame is a QoS Null frame.
  • the buffer report further includes a resource request type, where the resource request type is used to indicate that the buffer report is a buffer report corresponding to direct connection transmission.
  • Bit 7 or Bit 3 of the QoS control field of the QoS Null frame is used to carry the resource request type.
  • the technical effect brought by any possible design of the second aspect can refer to the technical effect brought by the corresponding design in the first aspect above, and will not be repeated here.
  • a communication method is provided, and the method is applied to a source access point multi-link device AP MLD, and multiple uplinks and downlinks are established between the source AP MLD and the non-access point multi-link device non-AP MLD link.
  • the method includes: the source AP MLD generates a basic service set transfer management BTM request frame, and sends the BTM request frame to the non-AP MLD on any uplink and downlink in a plurality of uplinks and downlinks.
  • the BTM request frame includes indication information, and the indication information is used to indicate the disassociation timer and/or effective interval in the BTM request frame with the target beacon transmission time of a certain uplink and downlink in the multiple uplinks and downlinks TBTT is the unit.
  • the source AP MLD adds indication information in the BTM request frame to indicate that the disassociation timer and/or valid time in the BTM request frame is based on the TBTT of a certain uplink and downlink in multiple uplinks and downlinks Unit, so that the non-AP MLD can accurately obtain the sending time of the disassociation frame, or the effective time of the BSS transfer candidate list, thereby improving the efficiency of BSS transfer.
  • the indication information is the identification of a certain uplink and downlink among the multiple uplinks and downlinks, or the indication information is the corresponding The ID of the base service set.
  • a communication method is provided, the method is applied to a source access point multi-link device AP MLD, and multiple uplinks and downlinks are established between the source AP MLD and the non-AP multi-link device non-AP MLD road.
  • the method includes: the source AP MLD generates a basic service set transfer management BTM request frame, and sends the BTM request frame to the non-AP MLD on the first uplink and downlink in multiple uplinks and downlinks, and removes the BTM request frame in the BTM request frame.
  • the unit of the association timer and/or the valid interval is the target beacon transmission time TBTT of the first uplink and downlink among the multiple uplinks and downlinks.
  • the disassociation timer and/or valid interval in the BTM request frame is based on the TBTT of the uplink and downlink that transmits the BTM request frame, so that the non-AP MLD can The link accurately obtains the sending time of the de-association frame, or the effective time of the BSS transfer candidate list, thereby improving the efficiency of BSS transfer.
  • a communication method includes: the source access point multi-link device AP MLD generates a basic service set transfer management BTM request frame, and sends the BTM request frame to the non-AP MLD.
  • the BTM request frame includes one or more neighbor report elements, and the neighbor report element is used to indicate the candidate access point AP recommended by the source AP MLD to the non-AP MLD; when the candidate access point belongs to the candidate AP MLD, the neighbor The report element includes a base variant multilink element, which includes a multilink control field and a common information field, and does not include a link information field.
  • the basic variant multi-link Not carrying the link information field in the element can save signaling overhead, and at the same time does not affect the execution of the BSS transfer process.
  • the multilink device media access control address occurrence field in the multilink control field is set to a first value
  • the first occurrence field in the multilink control field is set to a second value
  • the An occurrence field includes a link identification information occurrence field and a basic service set parameter change count occurrence field
  • the first value is used to indicate that the field appears in the common information field
  • the second value is used to indicate that the field does not appear in the common information field.
  • the second occurrence field in the multilink control field included in the first basic variant multilink element Set to the first value
  • the second occurrence field in the multi-link control field included in the second basic variant multi-link element is set to the second value.
  • the first basic variant multi-link element is a basic variant multi-link element included in the first neighbor report element among the multiple neighbor report elements
  • the second basic variant multi-link element is a multiple neighbor report A basic variant of a multilink element included in a neighbor report element other than the first neighbor report element in the element.
  • the second occurrence field includes one or more of the following: a media synchronization delay information occurrence field, an enhanced multi-link capability occurrence field, or a multi-link device capability occurrence field.
  • the subordinate AP of the AP MLD is the first neighbor report element of the candidate AP to carry the basic variant multi-link element
  • the second occurrence field in the multilink control field included in the basic variant multilink element is set to the first value, which will indicate that the subordinate AP of the AP MLD is the basic
  • the second occurrence field in the multilink control field included in the variant multilink element is set to a second value, so that one or more of the media synchronization delay information occurrence field, the EML capability occurrence field, or the MLD occurrence field
  • the item is carried once in the BTM request to avoid repeated carrying of the same field, thereby reducing signaling overhead.
  • a method for sending a buffer report is provided, the method is applied to a non-AP MLD of a non-AP multi-link device, and how many links are established between the non-AP MLD and the AP MLD of the access point multi-link device uplink and downlink.
  • the method includes: the non-AP MLD generates a buffer report, and the buffer report is used to request the first subordinate non-AP station non-AP STA in the non-AP MLD to transmit on the first link.
  • the first link includes a first direct link and a first uplink and downlink, and the first direct link is between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD Link, the first uplink and downlink is the link between the first affiliated AP of the AP MLD and the first affiliated non-AP STA of the non-AP MLD, the first target non-AP STA, non-AP MLD
  • the first affiliated non-AP STA of the AP MLD and the first affiliated AP of the AP MLD belong to the same basic service set BSS; the non-AP MLD sends a buffer to the AP MLD on the second uplink and downlink of the multiple uplinks and downlinks district report.
  • the non-AP MLD sends a buffer report to the AP MLD, which can be used to request the first subordinate non-AP STA in the non-AP MLD on the first direct link and the first uplink and downlink
  • the total duration of the transmission on the road so that after the AP MLD receives the buffer report, it can know that the first non-AP STA subordinate to the non-AP MLD is waiting on the first direct link and the first uplink and downlink.
  • the transmission is performed, so that the subordinate AP corresponding to the first direct link and the first uplink and downlink in the AP MLD can determine to allocate a period of time for the first subordinate non-AP STA in a certain TXOP obtained by it, using The transmission is performed on the first direct link and the first uplink and downlink, so that the data can be sent in time and the transmission delay is reduced.
  • a non-AP MLD is provided, and multiple uplinks and downlinks are established between the non-AP MLD and the AP MLD.
  • the non-AP MLD includes: a processing module and a transceiver module.
  • the processing module is used to generate a buffer report, and the buffer report is used to request the first affiliated non-AP station non-AP STA in the non-AP MLD to perform direct transmission on the first direct link,
  • the first direct link is the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD, and the first target non-AP STA and the first subordinate non-AP MLD of the non-AP MLD -AP STAs belong to the same basic service set BSS;
  • the transceiver module is configured to send a buffer report to the AP MLD on the first uplink and downlink in multiple uplinks and downlinks.
  • the non-AP MLD provided by the seventh aspect is used to realize the behavior function of the non-AP MLD in the first aspect or any possible design of the first aspect.
  • the first aspect or any of the first aspects please refer to the first aspect or any of the first aspects. The description in one possible design will not be repeated here.
  • an access point multi-link device AP MLD is provided, and multiple uplinks and downlinks are established between the AP MLD and a non-AP multi-link device non-AP MLD.
  • the AP MLD includes: a processing module and a transceiver module.
  • the transceiver module is used to receive the buffer report from the non-AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, and the buffer report is used to request the first subordinate contactless in the non-AP MLD
  • the length of time for the non-AP STA at the entry point to perform direct transmission on the first direct link is between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD.
  • the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD belong to the same basic service set BSS;
  • the processing module is used to determine the second transmission duration, and the second transmission duration includes the AP MLD allocated for the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link duration;
  • the transceiver module is further configured to send first duration indicating information, where the first duration indicating information is used to indicate the second transmission duration.
  • the AP MLD provided in the eighth aspect is used to realize the behavior function of the AP MLD in any possible design of the above-mentioned second aspect or the second aspect.
  • the AP MLD provided in the eighth aspect is used to realize the behavior function of the AP MLD in any possible design of the above-mentioned second aspect or the second aspect.
  • a source access point multi-link device AP MLD is provided, and multiple uplinks and downlinks are established between the source AP MLD and a non-AP multi-link device non-AP MLD.
  • the source AP MLD includes: a processing module and a transceiver module.
  • the processing module is used to generate a basic service set transfer management BTM request frame, the BTM request frame includes indication information, and the indication information is used to indicate the disassociation timer and/or effective interval in the BTM request frame in multiple uplinks and downlinks
  • the target beacon transmission time TBTT of a certain uplink and downlink is taken as the unit;
  • the transceiver module is used to send a BTM request frame to the non-AP MLD on any one of the multiple uplinks and downlinks.
  • the source AP MLD provided in the ninth aspect is used to realize the behavior function of the source AP MLD in the above-mentioned third aspect or any possible design of the third aspect.
  • the above-mentioned third aspect or any of the third aspects The description in the possible design will not be repeated here.
  • a source access point multi-link device AP MLD is provided, and multiple uplinks and downlinks are established between the source AP MLD and a non-AP multi-link device non-AP MLD.
  • the source AP MLD includes: a processing module and a transceiver module.
  • the processing module is used to generate a basic service set transfer management BTM request frame
  • the transceiver module is used to send a BTM request frame to the non-AP MLD on the first uplink and downlink in the multiple uplinks and downlinks, and the de-association timer and/or effective interval in the BTM request frame are based on multiple uplinks and downlinks
  • the target beacon transmission time TBTT of the first uplink and downlink in the uplink is taken as a unit.
  • the source AP MLD provided in the tenth aspect is used to realize the behavior function of the source AP MLD in the fourth aspect or any possible design of the fourth aspect.
  • the fourth aspect or any of the fourth aspects The description in the possible design will not be repeated here.
  • a source access point multi-link device AP MLD is provided, and the source AP MLD is multi-linked with a non-access point.
  • the source AP MLD includes: a processing module and a transceiver module.
  • the processing module is used to generate a basic service set transfer management BTM request frame, the BTM request frame includes one or more neighbor report elements, and the neighbor report element is used to indicate the candidate access point AP recommended by the source AP MLD to the non-AP MLD;
  • the neighbor report element includes a basic variant multi-link element, and the basic variant multi-link element includes a multi-link control field and a common information field, and does not include a link information field;
  • the transceiver module is used to send a BTM request frame to the non-AP MLD.
  • the source AP MLD provided in the eleventh aspect is used to realize the behavior function of the source AP MLD in any possible design of the above-mentioned fifth aspect or the fifth aspect.
  • any of the above-mentioned fifth aspect or the fifth aspect please refer to any of the above-mentioned fifth aspect or the fifth aspect. The description in one possible design will not be repeated here.
  • a non-AP MLD is provided, and multiple uplinks and downlinks are established between the non-AP MLD and the AP MLD.
  • the non-AP MLD includes: a processing circuit and an output interface communicating with the internal connection of the processing circuit.
  • the processing circuit is used to generate a buffer report, and the buffer report is used to request the first affiliated non-AP station non-AP STA in the non-AP MLD to perform a direct connection transmission on the first direct link,
  • the first direct link is the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD, and the first target non-AP STA and the first subordinate non-AP MLD of the non-AP MLD -AP STAs belong to the same basic service set BSS;
  • the output interface is used to send a buffer report to the AP MLD on the first uplink and downlink in the multiple uplinks and downlinks.
  • the non-AP MLD provided in the twelfth aspect is used to realize the behavior function of the non-AP MLD in any possible design of the first aspect or the first aspect above, and for details, please refer to the first aspect or the first aspect above. The description in any possible design will not be repeated here.
  • an access point multi-link device AP MLD is provided, and multiple uplinks and downlinks are established between the AP MLD and a non-AP multi-link device non-AP MLD.
  • the AP MLD includes: a processing circuit and an output interface and an input interface communicating with the internal connection of the processing circuit.
  • This input interface is used to receive a buffer report from a non-AP MLD on the first uplink and downlink among multiple uplinks and downlinks, and the buffer report is used to request the first subordinate contactless in the non-AP MLD
  • the first direct link is between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD.
  • the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD belong to the same basic service set BSS;
  • the processing circuit is used to determine the second transmission duration, and the second transmission duration includes the time allocated by the AP MLD for the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link duration;
  • the output interface is further configured to send first duration indication information, where the first duration indication information is used to indicate the second transmission duration.
  • the AP MLD provided in the thirteenth aspect is used to realize the behavior function of the AP MLD in any possible design of the above-mentioned second aspect or the second aspect.
  • the above-mentioned second aspect or any possible design of the second aspect please refer to the above-mentioned second aspect or any possible design of the second aspect. The description in the design of , will not be repeated here.
  • a source access point multi-link device AP MLD is provided, and multiple uplinks and downlinks are established between the source AP MLD and a non-AP multi-link device non-AP MLD.
  • the source AP MLD includes: a processing circuit and an output interface communicating with the internal connections of the processing circuit.
  • the processing circuit is used to generate a basic service set transfer management BTM request frame, the BTM request frame includes indication information, and the indication information is used to indicate the de-association timer and/or effective interval in the BTM request frame in multiple uplinks and downlinks
  • the target beacon transmission time TBTT of a certain uplink and downlink is taken as the unit;
  • the output interface is used to send a BTM request frame to the non-AP MLD on any one of the multiple uplinks and downlinks.
  • the source AP MLD provided in the fourteenth aspect is used to realize the behavior function of the source AP MLD in any possible design of the above-mentioned third aspect or the third aspect.
  • any of the above-mentioned third aspect or the third aspect please refer to any of the above-mentioned third aspect or the third aspect. The description in one possible design will not be repeated here.
  • a source access point multi-link device AP MLD is provided, and multiple uplinks and downlinks are established between the source AP MLD and a non-AP multi-link device non-AP MLD.
  • the source AP MLD includes: a processing circuit and an output interface communicating with the internal connections of the processing circuit.
  • the processing circuit is used to generate a basic service set transfer management BTM request frame
  • This output interface is used to send a BTM request frame to the non-AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, and the de-association timer and/or valid interval in the BTM request frame is based on multiple uplinks and downlinks.
  • the target beacon transmission time TBTT of the first uplink and downlink in the uplink is taken as a unit.
  • the source AP MLD provided in the fifteenth aspect is used to realize the behavior function of the source AP MLD in any possible design of the above-mentioned fourth aspect or the fourth aspect.
  • any of the above-mentioned fourth aspect or the fourth aspect please refer to any of the above-mentioned fourth aspect or the fourth aspect. The description in one possible design will not be repeated here.
  • a source access point multi-link device AP MLD is provided, and the source AP MLD is multi-linked with a non-access point.
  • the source AP MLD includes: a processing circuit and an output interface communicating with the internal connections of the processing circuit.
  • the processing circuit is used to generate a basic service set transfer management BTM request frame, the BTM request frame includes one or more neighbor report elements, and the neighbor report element is used to indicate the candidate access point AP recommended by the source AP MLD to the non-AP MLD;
  • the neighbor report element includes a basic variant multi-link element, and the basic variant multi-link element includes a multi-link control field and a common information field, and does not include a link information field;
  • This output interface is used to send BTM request frame to non-AP MLD.
  • the source AP MLD provided in the sixteenth aspect is used to realize the behavior function of the source AP MLD in any possible design of the above-mentioned fourth aspect or the fourth aspect.
  • any of the above-mentioned fourth aspect or the fourth aspect please refer to any of the above-mentioned fourth aspect or the fourth aspect. The description in one possible design will not be repeated here.
  • a non-AP MLD is provided, and multiple uplinks and downlinks are established between the non-AP MLD and the AP MLD.
  • the non-AP MLD includes: a processor and a transceiver communicating with the processor's internal connections.
  • the processor is configured to generate a buffer report, and the buffer report is used to request the first subordinate non-AP station non-AP STA in the non-AP MLD to perform a direct connection transmission on the first direct link,
  • the first direct link is the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD, and the first target non-AP STA and the first subordinate non-AP MLD of the non-AP MLD -AP STAs belong to the same basic service set BSS;
  • the transceiver is configured to send a buffer report to the AP MLD on the first uplink and downlink in the multiple uplinks and downlinks.
  • the non-AP MLD provided in the seventeenth aspect is used to realize the behavior function of the non-AP MLD in the first aspect or any possible design of the first aspect.
  • the first aspect or the first aspect please refer to the first aspect or the first aspect. The description in any possible design will not be repeated here.
  • an access point multi-link device AP MLD is provided, and multiple uplinks and downlinks are established between the AP MLD and a non-AP multi-link device non-AP MLD.
  • the AP MLD includes: a processor and a transceiver communicating with the internal connections of the processor.
  • the transceiver is used to receive a buffer report from a non-AP MLD on the first uplink and downlink among multiple uplinks and downlinks, and the buffer report is used to request the first subordinate contactless in the non-AP MLD
  • the first direct link is between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD.
  • the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD belong to the same basic service set BSS;
  • the processor is configured to determine a second transmission duration, where the second transmission duration includes the time allocated by the AP MLD for the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link duration;
  • the transceiver is further configured to send first duration indication information, where the first duration indication information is used to indicate the second transmission duration.
  • the AP MLD provided in the eighteenth aspect is used to realize the behavior function of the AP MLD in any possible design of the above-mentioned second aspect or the second aspect.
  • the above-mentioned second aspect or any possible design of the second aspect please refer to the above-mentioned second aspect or any possible design of the second aspect. The description in the design of , will not be repeated here.
  • a source access point multi-link device AP MLD is provided, and multiple uplinks and downlinks are established between the source AP MLD and a non-AP multi-link device non-AP MLD.
  • the source AP MLD includes: a processor and a transceiver in communication with the processor's internal connections.
  • the processor is configured to generate a basic service set transfer management BTM request frame, where the BTM request frame includes indication information, and the indication information is used to indicate that the disassociation timer and/or the effective interval in the BTM request frame are used in multiple uplinks and downlinks
  • the target beacon transmission time TBTT of a certain uplink and downlink is taken as the unit;
  • the transceiver is used to send a BTM request frame to the non-AP MLD on any one of the multiple uplinks and downlinks.
  • the source AP MLD provided in the nineteenth aspect is used to realize the behavior function of the source AP MLD in any possible design of the above-mentioned third aspect or the third aspect.
  • any of the above-mentioned third aspect or the third aspect please refer to any of the above-mentioned third aspect or the third aspect. The description in one possible design will not be repeated here.
  • a source access point multi-link device AP MLD is provided, and multiple uplinks and downlinks are established between the source AP MLD and a non-AP multi-link device non-AP MLD.
  • the source AP MLD includes: a processor and a transceiver in communication with the processor's internal connections.
  • the processor is used to generate a basic service set transfer management BTM request frame
  • the transceiver is configured to send a BTM request frame to the non-AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, and the de-association timer and/or valid interval in the BTM request frame are set in multiple uplinks and downlinks
  • the target beacon transmission time TBTT of the first uplink and downlink in the uplink is taken as a unit.
  • the source AP MLD provided in the twentieth aspect is used to realize the behavior function of the source AP MLD in the fourth aspect or any possible design of the fourth aspect.
  • any one of the fourth aspect or the fourth aspect please refer to any one of the fourth aspect or the fourth aspect. The description in one possible design will not be repeated here.
  • a source access point multi-link device AP MLD is provided, and the source AP MLD is multi-linked with a non-access point.
  • the source AP MLD includes: a processor and a transceiver in communication with the processor's internal connections.
  • the processor is used to generate a basic service set transfer management BTM request frame, the BTM request frame includes one or more neighbor report elements, and the neighbor report element is used to indicate the candidate access point AP recommended by the source AP MLD to the non-AP MLD;
  • the neighbor report element includes a basic variant multi-link element, and the basic variant multi-link element includes a multi-link control field and a common information field, and does not include a link information field;
  • This transceiver is used to send BTM request frame to non-AP MLD.
  • the source AP MLD provided in the twenty-first aspect is used to realize the behavior function of the source AP MLD in the above-mentioned fourth aspect or any possible design of the fourth aspect.
  • the above-mentioned fourth aspect or any of the fourth aspects please refer to the above-mentioned fourth aspect or any of the fourth aspects. The description in one possible design will not be repeated here.
  • an embodiment of the present application provides a computer-readable storage medium for storing a computer program, where the computer program includes instructions for executing the above-mentioned first aspect or any possible implementation manner of the first aspect.
  • an embodiment of the present application provides a computer-readable storage medium for storing a computer program, where the computer program includes instructions for executing the above-mentioned second aspect or any possible implementation manner of the second aspect.
  • an embodiment of the present application provides a computer-readable storage medium for storing a computer program, where the computer program includes instructions for executing the above-mentioned third aspect or any possible implementation manner of the third aspect.
  • an embodiment of the present application provides a computer-readable storage medium for storing a computer program, where the computer program includes instructions for executing the fourth aspect or any possible implementation manner of the fourth aspect.
  • an embodiment of the present application provides a computer-readable storage medium for storing a computer program, where the computer program includes instructions for executing the fifth aspect or any possible implementation manner of the fifth aspect.
  • an embodiment of the present application provides a computer program product, where the computer program product includes instructions for executing the first aspect or any possible implementation manner of the first aspect.
  • an embodiment of the present application provides a computer program product, where the computer program product includes instructions for executing the second aspect or any possible implementation manner of the second aspect.
  • an embodiment of the present application provides a computer program product, where the computer program product includes instructions for executing the above third aspect or any possible implementation manner of the third aspect.
  • an embodiment of the present application provides a computer program product, where the computer program product includes instructions for executing the fourth aspect or any possible implementation manner of the fourth aspect.
  • an embodiment of the present application provides a computer program product, where the computer program product includes instructions for executing the fifth aspect or any possible implementation manner of the fifth aspect.
  • an embodiment of the present application provides a communication system, where the communication system includes the non-AP MLD provided in the seventh aspect, or the twelfth aspect, or the seventeenth aspect, and the AP MLD.
  • an embodiment of the present application provides a communication system, where the communication system includes the AP MLD provided in the eighth aspect, or the thirteenth aspect, or the eighteenth aspect, and the non-AP MLD.
  • an embodiment of the present application provides a communication system, where the communication system includes the AP MLD provided in the ninth aspect, or the fourteenth aspect, or the nineteenth aspect, and the non-AP MLD.
  • an embodiment of the present application provides a communication system, where the communication system includes the AP MLD provided in the tenth aspect, or the fifteenth aspect, or the twentieth aspect, and the non-AP MLD.
  • the embodiment of the present application provides a communication system, where the communication system includes the AP MLD provided in the eleventh aspect, or the sixteenth aspect, or the twenty-first aspect, and the non-AP MLD.
  • FIG. 1 is a schematic diagram of a multi-link device provided in an embodiment of the present application
  • FIG. 2 is a schematic structural diagram of a multi-link element provided by an embodiment of the present application.
  • FIG. 3 is a schematic flow diagram of a BSS transfer management provided by an embodiment of the present application.
  • Figure 4a is a schematic diagram of a frame structure of a BTM inquiry frame provided by an embodiment of the present application.
  • FIG. 4b is a schematic diagram of a frame structure of a BTM request frame provided by an embodiment of the present application.
  • FIG. 4c is a schematic diagram of a frame structure of a BTM response frame provided by an embodiment of the present application.
  • FIG. 5 is a schematic timing diagram of a TXOP mechanism provided in an embodiment of the present application.
  • FIG. 6a is a schematic structural diagram of a communication system provided by an embodiment of the present application.
  • FIG. 6b is a schematic structural diagram of another communication system provided by an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a buffer report sending and receiving method provided by an embodiment of the present application.
  • FIG. 8a is a first structural diagram of a buffer report provided by an embodiment of the present application.
  • FIG. 8b is a second structural diagram of a buffer report provided by the embodiment of the present application.
  • FIG. 9a is a structural schematic diagram III of a buffer report provided by the embodiment of the present application.
  • FIG. 9b is a structural schematic diagram 4 of a buffer report provided by the embodiment of the present application.
  • Fig. 10a is a schematic structural diagram five of a buffer report provided by the embodiment of the present application.
  • Fig. 10b is a schematic flowchart of another buffer report sending and receiving method provided by the embodiment of the present application.
  • FIG. 11 is a schematic flowchart of a communication method provided by an embodiment of the present application.
  • FIG. 12 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 13 is a schematic flowchart of another communication method provided by the embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of a first communication device provided by an embodiment of the present application.
  • FIG. 15 is a schematic structural diagram of a second communication device provided by an embodiment of the present application.
  • FIG. 16 is a schematic structural diagram of a first communication device provided by an embodiment of the present application.
  • plural means two or more than two.
  • At least one of the following or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • at least one item (piece) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple .
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same function and effect.
  • words such as “first” and “second” do not limit the number and execution order, and words such as “first” and “second” do not necessarily limit the difference.
  • words such as “exemplary” or “for example” are used as examples, illustrations or illustrations. Any embodiment or design scheme described as “exemplary” or “for example” in the embodiments of the present application shall not be interpreted as being more preferred or more advantageous than other embodiments or design schemes.
  • the use of words such as “exemplary” or “such as” is intended to present related concepts in a concrete manner for easy understanding.
  • references to "an embodiment” throughout the specification mean that a particular feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present application. Therefore, various embodiments are not necessarily referring to the same embodiment throughout the specification. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments. It can be understood that in various embodiments of the present application, the serial numbers of the processes do not mean the order of execution, and the execution order of the processes should be determined by their functions and internal logic, and should not be used in the embodiments of the present application. The implementation process constitutes no limitation.
  • pre-defined in this application can be understood as definition, pre-definition, storage, pre-storage, pre-negotiation, pre-configuration, curing, or pre-firing.
  • Multi-link, multi-link device multi-link device, MLD
  • IEEE's next-generation wireless local area network (wireless local area network, WLAN) standard 802.11be takes extremely high throughput (EHT) as the technical goal, one of the existing key technologies That is, multi-link (multi-link, ML) communication.
  • EHT extremely high throughput
  • WLAN devices that support the next-generation IEEE 802.11 standard have the ability to send and receive in multiple frequency bands, so that they can use larger bandwidth for transmission, thereby improving throughput.
  • a WLAN device capable of simultaneously transmitting and receiving on multiple frequency bands may be called an MLD.
  • the above multiple frequency bands include but not limited to: 2.4GHz frequency band, 5GHz frequency band, and 6GHz frequency band.
  • the MLD includes at least two affiliated (affiliated) stations (stations, STAs), that is, affiliated STAs.
  • the affiliated station may be an access point station (access point station, AP STA) or a non-access point station (non-access point station, non-AP STA).
  • AP STA is referred to as AP for short in the following embodiments of this application.
  • a multi-link device whose affiliated station is an AP is called an AP multi-link device (AP multi-link device, AP MLD);
  • AP multi-link device AP multi-link device, AP MLD
  • AP MLD AP multi-link device
  • non-AP MLD non-access point multi-link device
  • each affiliated station in the MLD can establish a link for communication, so the link established by multiple affiliated stations is called a multi-link.
  • non-AP MLD and AP MLD can exchange multi-link association request (multi-link association request) frames and multi-link association response (multi-link association response) frames to realize multiple chains between them. Association (or establishment) of roads.
  • non-AP MLD and AP MLD can exchange association request frames and association response frames carrying multi-link information on one link, referred to as multi-link association request frames and multi-link association response frames. Carrying multi-link information in the multi-link association request frame and the multi-link association response frame can realize simultaneous association of multiple links between the two.
  • the link for exchanging the multi-link association request frame and the multi-link association response frame may be called a transmission link (Transmitted Link), and correspondingly, other links in the plurality of links are called non-transmission links ( Non-transmitted Link).
  • the AP MLD includes affiliated AP1 and AP2
  • the non-AP MLD includes affiliated non-AP STA1 and non-AP STA2
  • sites belonging to the same MLD AP or non-AP STA
  • MAC medium access control
  • the process of establishing a multi-link may include the following steps:
  • the non-AP MLD sends a multi-link association request frame to the AP MLD on link 1, which carries the information of the non-AP STA side of link 1 (ie non-AP STA1) and the non-AP of link 2 STA side (that is, non-AP STA2) information.
  • link 1 is a transmission link
  • link 2 is a non-transmission link.
  • Step2 The AP MLD replies to the non-AP MLD with a multi-link association response frame on link 1, which carries information on the AP side of link 1 (that is, AP1) and information on the AP side of link 2 (that is, AP2).
  • the protocol in order to carry MLD-related information in the multi-link association request frame or multi-link association response frame, the protocol defines a multi-link element (Multi-link element), which is used to carry the information of MLD and the station in MLD Information.
  • Multi-link element the frame structure of the multi-link element may be as shown in 2.
  • a station in this application refers to an AP or a non-AP STA, which will be described uniformly here, and will not be repeated in the following embodiments.
  • a multi-link element includes an element identifier (element ID) field, a length (Length) field, an element ID extension (Element ID Extension) field, a multi-link control field (Multi-Link Control), common information (Common Info) field, and link information (Link info) field.
  • the element identification field and the element identification extension field are used to identify the multi-link element.
  • the element identification field and the element identification extension field of different multi-link elements are different.
  • the element identification field can be set to 255, and the element identification extension field is set to No Value used by other multilink elements.
  • the length field is used to indicate the length of the multilink element.
  • the multilink control field may include a type (Type) field and a presence bitmap (Presence bitmap) field.
  • the type field is used to indicate the type of the multilink element, such as a basic variant (Basic variant) multilink element or a probe request variant (Probe Request variant) multilink element.
  • the present bitmap field may include one or more present fields. Specifically, the appearing bitmap field may include:
  • Multi-link device media access control address media access control, MAC
  • MLD MAC Address Present MLD MAC Address Present
  • Link ID Info Present field used to indicate whether the link ID information field in the common information field is present.
  • the link identification information field in the common information field is used to indicate the information of the transmission link.
  • Basic service set basic service set, BSS parameter change count occurrence (BSS Parameters Change Count Present) field: used to indicate whether the BSS parameter change count field in the common information field is present.
  • Medium Synchronization Delay Information Present used to indicate whether the medium synchronization delay information field in the common information field is present.
  • EML Capabilities Present used to indicate whether the EML capabilities field in the common information field is present.
  • Multilink Device Capabilities Present used to indicate whether the multilink device capabilities field in the common information field is present.
  • the Present field is set to 1 to indicate that the indicated field appears, and the Present field is set to 0 to indicate that the indicated field does not appear.
  • Present field mentioned in this application may also be referred to as “display field” or “present field”, which can be replaced with each other, and this application does not specifically limit this.
  • a to be determined (TBD) field may also be included.
  • the link information field is used to carry information about non-transmission links, and can include per-station profile (Per-STA Profile) sub-elements.
  • the per-station profile sub-elements can be one-to-one with the stations on the non-transmission links of the multi-link device correspond.
  • Each site profile sub-element may include a sub-element identification (Subelement ID) field, a length (Length) field, and a data (data) field.
  • the Data field may include a station control (STA Control) field, a station information (STA Info) field, and a station profile (STA Profile) field.
  • the site profile field may include zero or more elements (Element).
  • Tunneled direct-link setup (Tunneled direct-link setup, TDLS):
  • the two non-AP STAs can establish a direct link between each other, so that the data between the two can be Transmission is performed through the direct link without forwarding by the AP, thereby increasing the transmission rate and reducing the transmission delay.
  • the non-AP STA that establishes the direct link can be a non-AP STA that belongs to a non-AP MLD, or can be an independent non-AP STA that does not belong to any non-AP MLD.
  • this application refers to a non-AP STA that is not affiliated to any non-AP MLD as a legacy STA.
  • two non-AP STAs associated under the same BSS can establish a direct link through the TDLS protocol or other P2P protocols.
  • P2P may also be called device to device (device to device, D2D).
  • the direct link can also be called a P2P link, a D2D link, or a TDLS link, and can be replaced with each other, which is not specifically limited in this application.
  • the TDLS protocol mainly includes the following operations related to direct links:
  • TDLS Discovery Request (TDLS Discovery Request) frames and TDLS Discovery Response (TDLS Discovery Response) frames are exchanged between the TDLS Initiator and the TDLS Responder.
  • TDLS Setup Request (TDLS Setup Request) frame
  • TDLS Setup Response (TDLS Setup Response) frame
  • TDLS Setup Confirmation (TDLS Setup Confirm) frame
  • TDLS Teardown Completed by TDLS Teardown frame.
  • TDLS Power save mainly through TDLS peer power save management (PSM) request (TDLS Peer PSM Request) frame, TDLS peer PSM response (TDLS Peer PSM Response) frame, DLS peer traffic indication ( TDLS Peer Traffic Indication) frame, and TDLS Peer Traffic Response (TDLS Peer Traffic Response) frame to complete.
  • PSM power save management
  • TDLS channel switch completed by TDLS channel switch request (TDLS Channel Switch Request) frame, TDLS channel switch response (TDLS Channel Switch Response) frame.
  • Table 1 shows whether the transmission mode of each frame in the above TDLS protocol is through AP transmission (Via AP) or direct transmission through a direct link (Direct), and the frame type of each frame.
  • TDLS setup request frame Via AP or Direct frame type TDLS discovery request frame Via AP Data Frame TDLS Discovery Response Frame direct Public action frame (belongs to management frame)
  • TDLS setup request frame Via AP Data Frame TDLS establishment response frame
  • AP Data Frame TDLS establishment confirmation frame Via AP Data Frame TDLS teardown frame
  • Both allowed Data Frame TDLS channel switch request frame direct Data Frame TDLS Channel Switching Response Frame
  • Data Frame TDLS peer energy saving management request direct Data Frame TDLS peer end energy saving management response direct Data Frame TDLS peer traffic indication frame Via AP Data Frame TDLS peer traffic response frame direct Data Frame
  • TDLS-related frames when TDLS-related frames are forwarded by the AP or sent through a direct link, they will be encapsulated into data frames for transmission, so the above-mentioned TDLS-related operations are completely transparent to the AP, that is, the AP does not perceive The above-mentioned related operations of TDLS.
  • the TDLS discovery response frame is a public action frame, which is directly sent in the form of a management frame.
  • the non-AP STA can send a BSS transition management (BSS transition management, BTM) inquiry (BTM Query) frame to the AP under the BSS , correspondingly, the AP can reply the acknowledgment (acknowledgment, Ack) frame of the BTM query frame to the non-AP STA.
  • BSS transition management BTM transition management
  • Ack acknowledgment
  • AP When AP wants non-AP STA to perform BSS transfer, it can send BTM request (BTM request) frame to non-AP STA.
  • BTM request BTM request
  • the non-AP STA replies the acknowledgment frame of the BTM request frame to the AP
  • it can send a BTM response (BTM response) frame to the AP to indicate acceptance or rejection of the BSS transfer request.
  • the AP can reply the confirmation frame of the BTM response frame.
  • FIG. 4a it is the frame structure of the BTM query frame, including: category (Category) field, wireless network management (wireless network management, WNM) action (WNM Action) field, dialogue token (Dialog Token) field, BSS transfer Query Reason (BSS Transition Query Reason) field, BSS Transition Candidate List (BSS Transition Candidate List) field. in:
  • BSS Transfer Inquiry Reason Field Carries the reason why the non-AP STA sends the BTM inquiry frame.
  • BSS transfer candidate list field an optional field, carrying one or more neighbor report elements (Neighbor Report element), which are used to indicate the candidate BSS determined by the non-AP STA.
  • FIG. 4b it is the frame structure of the BTM request frame, including: category (Category) field, wireless network management (wireless network management, WNM) action (WNM Action) field, dialogue token (Dialog Token) field, request mode (Request Mode) field, Disassociation Timer (Disassociation Timer) field, Validity Interval field, BSS Termination Duration (BSS Termination Duration) field, session information uniform resource locator (uniform resource locator, URL) (Session Info URL) field, BSS Transition Candidate List (BSS Transition Candidate List) field. in:
  • category Category
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network
  • Request mode field used to indicate the specific request mode, specifically, it can include:
  • Bridge (Abridged) field If the AP does not recommend or prohibit the non-AP STA from switching to the BSS that does not appear in the BSS transfer candidate list, set the Abridged indicator bit to 0; if the AP will not appear in the BSS transfer candidate list The preference value (perferece value) of the BSS in the selection list is set to 0, and the Abridged indicator bit is set to 1.
  • Disassociation Imminent When this field is set to 1, it means that the AP will send a Disassociation frame to associate with the non-AP STA; when this field is set to 0, it means that the AP will not send Disassociation frame to associate with the non-AP STA.
  • BSS Termination Included indicates whether the BSS will be closed.
  • extended service set extend service set, ESS
  • disassociation imminent indicates whether the non-AP STA will be disassociated by the entire ESS.
  • Disassociation timer field used to indicate how long after the AP sends the disassociation frame.
  • Valid time field used to indicate how many beacon (Beacon) periods the BSS transfer candidate list is valid.
  • FIG. 4c it is the frame structure of the BTM response frame, including: category (Category) field, wireless network management (wireless network management, WNM) action (WNM Action) field, dialogue token (Dialog Token) field, BSS status Code (BTM Status Code) field, BSS Termination Delay (BSS Termination Delay) field, target BSS identification (Target BSSID) field.
  • category Category
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM wireless network management
  • WNM Action wireless network management
  • NVM Action dialogue token
  • BSS status Code BTM Status Code
  • BSS Termination Delay BSS Termination Delay
  • target BSSID target BSS identification
  • BSS status code field used to indicate whether the non-AP STA accepts the BTM request.
  • BSS termination delay field used to indicate the time to delay the termination of the BSS.
  • Target BSS ID field used to indicate the target BSSID of the BSS transfer. For non-AP MLD, if it wants to transfer to AP MLD, this field is set to the MLD MAC address (Address) of AP MLD.
  • multiple APs can form an AP cooperation set.
  • the AP cooperation set includes at least one sharing AP (Sharing AP) and at least one shared AP (Shared AP).
  • the Sharing AP can allocate a period of time for the Shared AP to use the Shared AP for data transmission.
  • the AP as a TXOP holder can allocate part of the time in the TXOP to the non-AP STA for the non-AP STA to send data.
  • the AP obtains the TXOP after sending a clear to send (CTS) frame (CTS-to-self) to itself.
  • CTS clear to send
  • the AP can send a multi-user (multi user, MU) request to send (request to send, RTS) transmission opportunity sharing (TXOP sharing, TXS) trigger frame (trigger frame, TF), the MU-RTS TXS TF can indicate a period of time , and indicate a non-AP STA, indicating that the duration is allocated to the non-AP STA. In addition, it can also indicate the transmission mode, which is used to indicate whether the duration is used for the P2P transmission of the non-AP STA or Uplink transmission.
  • MU multi-user
  • TXOP sharing, TXS transmission opportunity sharing
  • TXS trigger frame
  • the MU-RTS TXS TF can indicate a period of time , and indicate a non-AP STA, indicating that the duration is allocated to the non-AP STA.
  • the transmission mode which is used to indicate whether the duration is used for the P2P transmission of the non-AP STA or Uplink transmission.
  • the AP allocates a period of time A to non-AP STA1 for P2P transmission of non-AP STA1 as an example.
  • Non-AP STA1 can send CTS after receiving the MU-RTS TXS TF, and then send a single user (Single user, SU) physical layer protocol data unit (physical protocol data unit, PPDU) to non-AP STA2, namely SU PPDU,
  • the non-AP STA2 can reply the SU PPDU block acknowledgment (block acknowledgment, BA).
  • block acknowledgment BA
  • the AP can continue to send PPDUs within the TXOP.
  • the non-AP STA1 can send the required transmission duration to the AP.
  • the above TXOP sharing mechanism may have some problems.
  • the present application provides a buffer report sending and receiving method, which is applicable to a scenario including multi-link devices, and used to solve problems related to the TXOP sharing mechanism in this scenario.
  • the methods for sending and receiving buffer reports provided by this application will be described in detail below in conjunction with the accompanying drawings.
  • the method provided by this application can be applied to Wi-Fi scenarios or WLAN scenarios, for example, it can be applied to IEEE 802.11 system standards, such as 802.11a/b/g standard, 802.11n standard, 802.11ac standard, 802.11ax standard, or its next generation (such as the 802.11be standard) or a later generation standard.
  • the embodiments of the present application may be applicable to wireless local area network systems such as the Internet of Things (Internet of Things, IoT) or the Internet of Vehicles (vehicle to X, V2X).
  • the embodiment of the present application can also be applicable to other possible communication systems, for example, long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division) duplex, TDD), universal mobile telecommunications system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, and the fifth generation (5th generation, 5G) communication system, etc.
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD time division duplex
  • UMTS universal mobile telecommunications system
  • WiMAX worldwide interoperability for microwave access
  • 5G fifth generation
  • the above-mentioned communication system applicable to the present application is only an example, and the communication system applicable to the present application is not limited thereto, and will be described in a unified manner here, and will not be described in detail below.
  • the present application provides a WLAN communication system applicable to the embodiment of the present application.
  • the WLAN communication system includes an AP MLD 601 and a non-AP MLD 602.
  • the AP MLD 601 includes multiple subordinate APs
  • FIG. 6a takes the multiple subordinate APs including AP1, AP2, and AP3 as an example for illustration.
  • the non-AP MLD 602 includes multiple subordinate non-AP STAs.
  • the multiple subordinate non-AP STAs include non-AP STA1, non-AP STA2, and non-AP STA3 as an example for illustration.
  • the multiple uplinks and downlinks include uplink and downlink 1 between AP1 and non-AP STA1, AP2 and non-AP STA1.
  • - Uplink and downlink 2 between AP STA2 and uplink and downlink 3 between AP3 and non-AP STA3 are taken as examples for illustration.
  • 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 a subordinate non-AP STA in the non-AP MLD 602.
  • the target non-AP STA at both ends of a direct link belongs to the same BSS as the affiliated non-AP STA in the non-AP MLD 602, or in other words, is associated with the same AP in the AP MLD 601.
  • the link ID of the direct link in the same BSS is the same as the link ID of the uplink and downlink.
  • the target non-AP STA may be a legacy STA, such as the target non-AP STA 603 shown in FIG. 6a.
  • a direct link 1 is established between the target non-AP STA 603 and the subordinate non-AP STA1 of the non-AP MLD 602, and an uplink and downlink link A is established between the target non-AP STA 602 and the AP1 of the AP MLD 601.
  • the target non-AP STA 603 and non-AP STA1 of non-AP MLD 602 belong to the BSS corresponding to AP1 of AP MLD 601.
  • the link identifier of the direct link 1 is the same as the link identifier of the uplink and downlink 1.
  • the target non-AP STA may be a non-AP STA subordinate to a certain non-AP MLD
  • the target non-AP STA 604 shown in FIG. 6a is a non-AP STA subordinate to the non-AP MLD A.
  • a direct link 2 is established between the target non-AP STA 604 and the subordinate non-AP STA3 of the non-AP MLD 602, and an uplink and downlink link B is established between the AP3 of the APMLD 601, and the target non-AP STA 604
  • the link identifier of the direct link 2 is the same as the link identifier of the uplink and downlink 3 .
  • the present application provides another WLAN communication system applicable to the embodiment of the present application.
  • the WLAN communication system includes a shared AP MLD (Sharing AP MLD) 6011 and a shared AP MLD (Shared AP MLD) 6012.
  • shared AP MLD Sharing AP MLD
  • shared AP MLD Shared AP MLD
  • the shared AP MLD 6011 includes multiple subordinate APs
  • FIG. 6b takes the multiple subordinate APs including AP A, AP B, and AP C as an example for illustration.
  • the shared AP MLD 6012 includes multiple subordinate APs.
  • the multiple subordinate APs include AP a, AP b, and AP c as an example for illustration.
  • Multiple links are established between the shared AP MLD 6011 and the shared AP MLD 6012.
  • the multiple links include link 1 between AP A and AP a, and between AP B and AP b Link 2 between AP C and AP C is used as an example for illustration.
  • the WLAN communication system may also include at least one target non-AP STA, and an uplink and downlink link is established between each target non-AP STA and an AP in the shared AP MLD 6012.
  • the target non-AP STA at both ends of an uplink and downlink belongs to the same BSS as the AP in the shared AP MLD 6012, or is associated with the same AP in the shared AP MLD 6011.
  • the link ID of the uplink and downlink in the same BSS is the same as the ID of the link between the sharing AP and the shared AP.
  • the target non-AP STA may be a legacy STA, such as the target non-AP STA 6013 shown in Figure 6b.
  • the target non-AP STA 6013 establishes an uplink and downlink X with AP a of the shared AP MLD 6012, and establishes an uplink and downlink A with AP A of the shared AP MLD 6011, and the target non-AP STA 6013 and AP a of shared AP MLD 6012 belong to the BSS corresponding to AP A of shared AP MLD 6011.
  • the link identifier of the uplink and downlink X is the same as the link identifier of the link 1 .
  • the target non-AP STA may be a non-AP STA subordinate to a certain non-AP MLD, for example, the target non-AP STA 6014 shown in FIG. 6a is a non-AP STA subordinate to the non-AP MLD A.
  • the target non-AP STA 6014 establishes an uplink and downlink Y with the AP c of the shared AP MLD 6012, and establishes an uplink and downlink B with the AP C of the shared AP MLD 6011, and the target non-AP STA 6014 and the AP c of the shared AP MLD 6012 belong to the BSS corresponding to the shared AP C of the AP MLD 6011.
  • the link identifier of the uplink and downlink Y is the same as the link identifier of the link 3 .
  • the non-AP MLD involved in this application can be a wireless communication chip, a wireless sensor or a wireless communication terminal.
  • a user terminal a user device, an access device, a subscriber station, a subscriber unit, a mobile station, a user agent, and a user equipment that support a Wi-Fi communication function.
  • the user terminal may include various handheld devices with wireless communication functions, vehicle-mounted devices, wearable devices, Internet of things (Internet of things, IoT) devices, computing devices or other processing devices connected to wireless modems, and various forms of User equipment (user equipment, UE), mobile station (mobile station, MS), terminal (terminal), terminal equipment (terminal equipment), portable communication equipment, handsets, portable computing equipment, entertainment equipment, gaming equipment or systems, A global positioning system device or any other suitable device or the like configured for network communication via a wireless medium.
  • the non-AP MLD can support the 802.11be standard or the next-generation WLAN standard of 802.11be.
  • Non-AP MLD can also support multiple WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.
  • the AP MLD involved in the embodiment of the present application can be a device that is deployed in a wireless communication network to provide wireless communication functions for its associated non-AP STA, and is mainly deployed in homes, buildings, and campuses, with a typical coverage radius of several tens Of course, it can also be deployed outdoors.
  • AP MLD is equivalent to a bridge connecting the wired network and the wireless network. Its main function is to connect various wireless network clients together, and then connect the wireless network to the Ethernet.
  • the AP MLD can be a base station with a Wi-Fi chip, a router, a gateway, a repeater, a communication server, a switch or a bridge and other communication equipment, wherein the base station can include various forms of macro base stations, micro base station, relay station, etc.
  • the AP MLD can support the 802.11be standard or the next-generation WLAN standard of 802.11be.
  • AP MLD can also support WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.
  • this application provides a buffer report sending and receiving method, so that the AP corresponding to the direct link in the AP MLD can determine that in a certain TXOP obtained by it, it is a non-AP MLD affiliated with the non-AP MLD.
  • the AP STA allocates a period of time for transmission on the direct link, so that the data on the direct link can be sent in time, reducing the transmission delay on the direct link.
  • the executive body may perform some or all of the steps in the embodiments of the present application, these steps or operations are only examples, and the embodiments of the present application may also perform other operations or variations of various operations.
  • each step may be performed in a different order presented in the embodiment of the present application, and it may not be necessary to perform all operations in the embodiment of the present application.
  • FIG. 7 is a schematic flow chart of the buffer report sending and receiving method provided by the embodiment of the present application. The method includes the following steps:
  • the non-AP MLD generates a buffer report (buffer report).
  • the buffer report is used to request the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link.
  • the first direct link is a link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD.
  • the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD belong to the same BSS.
  • the first subordinate non-AP STA in the non-AP MLD - AP STA and the first target non-AP STA have established the first direct link as an example.
  • the direct links established between other non-AP STAs in the non-AP MLD and other target non-AP STAs For features of the direct link and related implementations, reference may be made to the first direct link and related descriptions provided in this application.
  • the first affiliated non-AP STA of the non-AP MLD may be non-AP STA3 in the non-AP MLD 602, and correspondingly, the first target non-AP STA is the target non-AP STA -AP STA 604, the first direct link is direct link 2.
  • the first subordinate non-AP STA of the non-AP MLD may be the non-AP STA1 in the non-AP MLD 602.
  • the first target non-AP STA is the target non-AP STA 603, and the first non-AP STA is The link is direct link 1.
  • the buffer report includes link information and transmission duration information.
  • the transmission duration information is used to indicate the first transmission duration
  • the first transmission duration is the duration during which the first subordinate non-AP STA in the non-AP MLD performs direct transmission on the first direct link.
  • the first transmission duration may be a normalized time duration.
  • the normalized time length may refer to a time length determined by a reference bandwidth (for example, 80 MHz), a reference rate, and the like.
  • the transmission duration information may include the size of the first buffer.
  • the first buffer is used to buffer the data to be sent by the first subordinate non-AP STA in the non-AP MLD on the first direct link, or in other words, the first buffer is used to buffer the non-AP MLD The data to be sent by the first subordinate non-AP STA to the first target non-AP STA.
  • the buffer report may not indicate the direct link Which target non-AP STA is the other end of the road except the first affiliated non-AP STA, that is, the buffer report does not indicate the target non-AP STA, but indicates the direct link through the link information.
  • the first transmission duration may be determined according to the size of the first buffer.
  • the first transmission duration may be calculated according to the size of the first buffer zone, a reference bandwidth, a reference rate, and the like.
  • the transmission duration information may include the first transmission duration.
  • the first transmission duration may be determined according to the size of the first buffer, a reference bandwidth, a reference rate, and the like.
  • the transmission duration information when the transmission duration information includes the size of the first buffer, the transmission duration information implicitly indicates the first transmission duration.
  • the transmission duration information includes the first transmission duration, the transmission duration information explicitly indicates the first transmission duration.
  • the link information is used to indicate the first direct link.
  • the link information may be an identifier of the first direct link. If the first direct link is the direct link 1 shown in FIG. 6 a , the identifier of the first direct link is the identifier of the direct link 1 . Since the identifier of the direct link 1 is the same as the identifier of the uplink and downlink 1, the identifier of the direct link 1 is also the identifier of the uplink and downlink 1.
  • the link identification information includes the identification of the first direct link
  • taking the transmission duration information including the size of the first buffer as an example
  • the structure of the buffer report may be as shown in FIG. 8a.
  • the link identification (link ID) field is used to carry the identification of the direct link
  • the buffer size field is used to carry the size of the buffer.
  • the buffer report may also include type (Type) information and/or number of direct links (Numbers of direct link) information.
  • Type type
  • Number of direct links Number of direct link
  • This type of information is used to indicate that one or more uplinks and downlinks are established between the non-AP MLD and the AP MLD.
  • the information on the number of direct links is used to indicate the number N of direct links with data to be transmitted. For example, in the system shown in FIG. 6a, there are two direct links. If there is data to be transmitted on direct link 1, If there is no data to be transmitted on direct link 2, the number of direct links is 1; if there is data to be transmitted on both direct link 1 and direct link 2, the number of direct links is 2.
  • the buffer report further includes type (Type) information and/or number of direct links (Numbers of direct links) information
  • the structure of the buffer report may be as shown in FIG. 8b.
  • the type field is used to carry type information. For example, when the type field is set to 1, it can indicate that there are multiple uplinks and downlinks established between the non-AP MLD and the AP MLD; when the type field is set to 0, It can indicate that there is an uplink and downlink established between non-AP MLD and AP MLD.
  • the number of direct links field is used to carry information about the number of direct links.
  • the link identification field and the buffer size field may be repeated N times, and the N link identification fields carry N Link identification information, and N buffer size fields respectively carry the sizes of N buffers.
  • the link information may be a bitmap.
  • the size of this bitmap is the total number of uplinks and downlinks established between non-AP MLD and AP MLD. For example, under the system shown in FIG. 6a, the size of the bitmap is 3.
  • each bit in the bitmap corresponds to an uplink and downlink established between the non-AP MLD and the AP MLD.
  • the bit corresponding to the direct link can be set to 1 to indicate that the direct link is the identifier corresponding to this bit Direct links with the same ID for the uplink and downlink.
  • the identifier of direct link 1 is the same as the identifier of uplink and downlink 1, assuming that the bits in the bitmap are from left to The right corresponds to the uplink and downlink 1, the uplink and downlink 2, and the uplink and downlink 3 in turn, and the bitmap can be set to 100.
  • setting the first bit to 1 indicates that the direct link is the direct link 1 whose identifier is the same as that of the uplink and downlink 1 corresponding to this bit.
  • the link identification information includes a bitmap
  • the transmission duration information including the size of the first buffer as an example
  • the structure of the buffer report may be as shown in Figure 9a.
  • the bitmap field is used to carry the bitmap
  • the size of this field is the same as that of the bitmap
  • the buffer size field is used to carry the size of the buffer.
  • the buffer report may also include type (Type) information and/or bitmap size (Bitmap size).
  • Type type
  • Bitmap size bitmap size
  • the buffer report further includes type (Type) information and/or bitmap size
  • the structure of the buffer report may be as shown in FIG. 9b.
  • the function of the type field can refer to the relevant description above
  • the bitmap size field is used to carry the size of the bitmap.
  • the buffer size field may be repeated N times, carrying the sizes of N buffers respectively.
  • the bitmap carried in the bitmap field indicates the multiple direct links. For example, in the scenario shown in FIG. 6a, if both direct link 1 and direct link 2 have data to be transmitted, then The bitmap can be set to 101.
  • the transmission duration information includes the buffer size as an example for illustration.
  • the buffer size field in Figures 8a-9b can be replaced with the transmission duration Field, used to carry the transmission duration.
  • Case 2 The buffer report includes transmission duration information and does not include link information.
  • the non-AP MLD sends a buffer report to the AP MLD on the first uplink and downlink among the multiple uplinks and downlinks.
  • the AP MLD receives the buffer report from the non-AP MLD on the first uplink and downlink.
  • the buffer report is as described in the above case 1, the first uplink and downlink is any one of the multiple uplinks and downlinks established between the non-AP MLD and the AP MLD .
  • the uplink and downlink in this application refer to enabled (enabled) uplink and downlink.
  • the first uplink and downlink can be It is any one of the uplink and downlink 1, the uplink and downlink 2, and the uplink and downlink 3.
  • the buffer report is as described in the above-mentioned case 2.
  • the first uplink and downlink are identified in multiple uplinks and downlinks established between non-AP MLD and AP MLD. Links with the same uplink and downlink identifiers, that is, the identifiers of the first uplink and downlink links are the same as the identifiers of the first direct link.
  • the first direct link is direct link 1
  • the first uplink and downlink is uplink and downlink 1.
  • the buffer report is as described in the above case 2, if there is data to be transmitted on multiple direct links, it is necessary to send the buffered data on the uplink and downlink corresponding to each direct link. district report.
  • the non-AP MLD sends direct link 1 to AP MLD on uplink and downlink 1.
  • the corresponding buffer report indicates the duration of the direct transmission on the direct link 1, and sends the buffer report corresponding to the direct link 3 to the AP MLD on the uplink and downlink 3, indicating that the direct connection The duration of direct transmission on link 3.
  • the non-AP MLD can first determine the content of the buffer report, and then determine the uplink and downlink for sending the buffer report to the AP MLD according to the content of the buffer report .
  • the non-AP MLD may first determine the uplink and downlink used to send the buffer report to the AP MLD, and then determine the content of the buffer report according to the selected uplink and downlink. This application does not specifically limit it.
  • the buffer report can be carried in the management frame.
  • the non-AP MLD sends a buffer report to the AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, which may include: the first uplink and downlink of the non-AP MLD among the multiple uplinks and downlinks
  • a management frame is sent to the AP MLD on the link, and the management frame includes a buffer report.
  • the buffer report may be carried in the aggregated control (aggregated control, A-control) field in the header of the management frame, that is, the management frame includes the A-control field, and the A-control field includes the buffer Report.
  • aggregated control aggregated control, A-control
  • 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 the direct connection transmission. That is, the buffer report carried in this type of A-control includes the buffer report corresponding to the direct connection transmission. It can be understood that the buffer report corresponding to the direct connection transmission is used to request the duration of the direct connection transmission on the direct connection link.
  • the buffer report may be carried in the frame body of the management frame.
  • 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 the direct connection transmission. That is, the buffer report carried in this type of management frame includes the buffer report corresponding to the direct connection transmission.
  • the frame header of the management frame may also include multi-link device information, and the multi-link device information is used to indicate non-AP MLD.
  • the buffer report may be carried in the aggregation control A-control field in the frame header of the data frame.
  • the non-AP MLD sends a buffer report to the AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, which may include: the first uplink and downlink of the non-AP MLD among the multiple uplinks and downlinks Send a data frame to the AP MLD on the link, the data frame includes the A-control field, and the A-control field includes a buffer report.
  • 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 the buffer report corresponding to the direct connection transmission. Reference may be made to the relevant description above, and details are not repeated here.
  • the buffer report may be carried in a quality of service (quality of service, QoS) control (control) (that is, QoS control) field of the data frame.
  • QoS quality of service
  • control that is, QoS control
  • the data frame can be a QoS Null frame, that is, the buffer report can be carried in the QoS control field of the QoS Null frame.
  • the frame header of the data frame may also include multi-link device information, and the multi-link device information is used to indicate non-AP MLD.
  • the AP MLD determines the second transmission duration.
  • the AP MLD can obtain the TXOPs in multiple BSSs before step S703, and the multiple BSSs are the BSSs corresponding to the multiple subordinate APs of the AP MLD.
  • the AP MLD can learn that the first subordinate non-AP STA of the non-AP MLD is to perform direct transmission on the first direct link, so that the AP MLD and the first direct link
  • the corresponding subordinate AP may determine to allocate a period of time for the first subordinate non-AP STA within a certain TXOP obtained by it for transmission on the first direct link.
  • the second transmission duration includes the duration allocated by the AP MLD for the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link.
  • the second transmission duration is a period of time within a certain TXOP obtained by the subordinate AP corresponding to the first direct link in the AP MLD.
  • the subordinate AP corresponding to the first direct link in the AP MLD is AP1.
  • the second transmission duration may be the same as or different from the first transmission duration. That is to say, the duration allocated by AP MLD is not necessarily equal to the duration requested by non-AP MLD.
  • the AP MLD sends the first duration indication information.
  • the non-AP MLD receives the first duration indication information from the AP MLD.
  • the first duration indication information is used to indicate the second transmission duration.
  • the first duration indication information may be carried in a trigger frame.
  • the trigger frame carrying the first duration indication information may be MU-RTS TXS TF.
  • the trigger frame may include non-AP MLD information to indicate that the second transmission duration is allocated to the first subordinate non-AP STA of the non-AP MLD.
  • the trigger frame may also include first mode information, and the first mode information may be used to indicate that the second transmission duration is used for direct transmission and uplink transmission of the first non-AP STA subordinate to the non-AP MLD.
  • the non-AP MLD after the non-AP MLD receives the trigger frame, when the first mode information indicates that the second transmission duration is used for direct-connection transmission and uplink transmission of the first non-AP STA subordinate to the non-AP MLD, it can Perform direct transmission and uplink transmission on the first direct link within the second transmission duration.
  • the non-AP MLD sends a buffer report to the AP MLD, which can be used to request the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link
  • the AP MLD can learn that the first non-AP STA subordinate to the non-AP MLD is to perform direct transmission on the first direct link, so that the AP MLD and the first direct link
  • the affiliated AP corresponding to the connected link can determine to allocate a period of time for the first affiliated non-AP STA within a certain TXOP obtained by it for transmission on the first direct link, so that the direct link on the direct link Data can be sent in time, reducing the transmission delay on the direct link.
  • multiple uplinks and downlinks are established between non-AP MLD and AP MLD as an example. It can be appropriately modified to apply to only one uplink and downlink between non-AP MLD and AP MLD. It is applicable to the scenario where there is an uplink and downlink established between the legacy STA and the AP MLD.
  • the above-mentioned buffer report may not carry link information, and the structure of the buffer report may be as shown in Figure 10a, where the type field is set to 0, indicating non-AP MLD (or legacy STA) There is an uplink and downlink type established between AP MLD and AP MLD.
  • the non-AP MLD can also request the duration of the uplink transmission.
  • the non-AP MLD may generate a direct connection buffer report for the duration of requesting direct connection transmission, and an uplink buffer report for the duration of requesting uplink transmission or report the size of the uplink buffer.
  • the buffer report involved in the process shown in Figure 7 can be considered as the direct connection buffer report.
  • the relevant implementation of the uplink buffer report is similar to the direct connection buffer report, and reference may be made to the above description, and details will not be repeated here.
  • the uplink buffer report may include traffic identifier (traffic identifier, TID) information and transmission duration information, and is used to request the transmission duration corresponding to a certain TID. Since there is a mapping relationship (TID-to-link mapping) between the TID and the link, the AP MLD can determine according to the buffer report to allocate a period of time in the TXOP obtained by the subordinate AP corresponding to the link corresponding to the TID. Uplink transmission.
  • traffic identifier traffic identifier
  • TID traffic identifier
  • transmission duration information is used to request the transmission duration corresponding to a certain TID. Since there is a mapping relationship (TID-to-link mapping) between the TID and the link, the AP MLD can determine according to the buffer report to allocate a period of time in the TXOP obtained by the subordinate AP corresponding to the link corresponding to the TID. Uplink transmission.
  • the uplink buffer report may include TID information and queue size (Queue Size) information, where the queue size information is used to indicate the queue size of the TID indicated by the TID information.
  • the duration of the uplink buffer report request for uplink transmission may be determined.
  • the service identification information may include TID or bitmap
  • the transmission duration information may include the buffer size or transmission duration.
  • the buffer report may also include buffer type information, and the buffer type information is used to indicate whether the buffer report where the buffer type information is located is a buffer report corresponding to direct connection transmission, or Upstream buffer report.
  • management frames or different types of A-controls may be used to respectively carry the direct connection buffer report and the uplink buffer report.
  • the buffer report can also include Resource Request Type (Resource Request Type), the resource request type is used to indicate whether the buffer report is used for uplink resource requests or direct connection resource requests.
  • Resource Request Type Resource Request Type
  • the resource request type may also be called a buffer type.
  • the resource request type is used to indicate whether the buffer report is used for uplink resource requests or direct connection resource requests, which can be understood as: the buffer type is used to indicate whether the buffer report is an uplink buffer report or a direct connection buffer district report.
  • the direct connection buffer report may also include channel width information, where the channel width information is used to indicate the reference bandwidth.
  • channel width information is used to indicate the reference bandwidth.
  • reference bandwidth reference may be made to the relevant description in the above step S701, which will not be repeated here.
  • Bit 7 of the QoS control field in the QoS Null frame can be used to carry the resource request type.
  • Bit 7 of the QoS control field is set to the third value, it can indicate that the buffer report is used for uplink resource requests; when Bit 7 of the QoS control field is set to the fourth value, it can indicate that the buffer report is used for direct connection resource requests .
  • the third value may be 0, and correspondingly, the fourth value may be 1.
  • the third value may be 1, and correspondingly, the fourth value may be 0.
  • the function or setting of each bit of the QoS control field in the QoS Null frame can be shown in Table 2 below:
  • the TID field used to carry TID information, indicating the TID corresponding to the buffer report.
  • Ack Policy Indicator (Ack Policy Indicator) field: it is used to indicate the adopted acknowledgment policy, which can refer to the relevant definitions in the 802.11be standard, and will not be repeated here.
  • Resource Request Type field used to indicate the resource request type.
  • TXOP Duration Requested used to carry the transmission duration information in the buffer report, indicating the requested transmission duration.
  • the requested TXOP duration field when the requested TXOP duration field is set to 0, it means that no transmission duration is requested, or the transmission duration is 0; when the requested TXOP duration field is set to non-zero, the requested transmission duration can be multiplied by the value of this field 32 microseconds. Therefore, the transmission duration corresponding to this field may range from 32 microseconds to 8160 microseconds.
  • Queue Size (Queue Size) field: used to carry queue size information, indicating the queue size of the TID.
  • Channel Width field used to carry channel width information, indicating the reference bandwidth.
  • Channel Width Channel Width
  • Table 3 the corresponding relationship between the value of the channel width field and the reference bandwidth may be shown in Table 3 below.
  • the resource request type when the resource request type is set to 0, it indicates that the buffer report is an uplink buffer report, and when the resource request type field is set to 1, it indicates that the buffer report is a direct connection buffer report. Therefore, the settings shown in Table 2 above may indicate that the uplink buffer report includes TID information, resource request type, and transmission duration information; or, 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.
  • the QoS Null frame sent by the Non-AP STA in Table 2 can be understood as the QoS Null frame sent to the AP when the Non-AP STA supports TXS.
  • the Non-AP STA can be a Non-AP EHT STA or a Non-AP STA that supports future evolved WLAN standards.
  • Bit 3 of the QoS control field in the QoS Null frame can be used to carry the resource request type.
  • Bit 3 of the QoS control field is set to the third value, it can indicate that the buffer report is used for uplink resource requests; when Bit 3 of the QoS control field is set to the fourth value, it can indicate that the buffer report is used for direct connection resource requests .
  • the function or setting of each bit of the QoS control field in the QoS Null frame can be as shown in Table 4 below:
  • Table 2 and Table 4 are only illustrative examples of the uplink buffer report including TID information, resource request type, and transmission duration information. This application does not limit that the uplink buffer report must be as shown in the table 2 or Table 4, for example, the TID field in Table 2 and Table 4 can also be replaced with a link information field to carry link information. Similarly, it is not limited that the direct connection buffer report must be as shown in Table 2 or Table 4. For example, the channel width field in Table 2 and Table 4 can be replaced with a link information field for carrying link information.
  • the subordinate AP corresponding to the link corresponding to the TID can obtain it TXS is performed in TXOP, and a period of time is allocated for uplink transmission.
  • any subordinate AP in the AP MLD that has a link with the non-AP MLD can perform TXS within a certain TXOP obtained by it, and allocate a period of time for the uplink on the transmission.
  • the present application also provides a buffer report sending and receiving method, in which a buffer report can be used to request the transmission duration of the direct link and the transmission duration of the uplink.
  • the buffer report sending and receiving method includes the following steps:
  • the non-AP MLD generates a buffer report.
  • the buffer report is used to request the first affiliated non-AP STA in the non-AP MLD to transmit on the first link.
  • the first link includes a first direct link and a first uplink and downlink.
  • the first direct link is a link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD.
  • the first uplink and downlink are links between the first affiliated AP of the AP MLD and the first affiliated non-AP STA of the non-AP MLD, and the first target non-AP STA and the first affiliated non-AP MLD.
  • the first subordinate AP that belongs to the non-AP STA and the AP MLD belongs to the same BSS.
  • the first direct link may be direct link 1
  • the first uplink and downlink may be uplink and downlink 1.
  • the buffer report may include link information, transmission duration information, and second mode information.
  • the second mode information is used to indicate whether the transmission duration information indicates the uplink transmission duration or the total duration of uplink transmission and direct connection transmission.
  • link information and the transmission duration information reference may be made to the related description in the above step S701, which will not be repeated here.
  • the second mode information may be 1-bit indication information.
  • bit When the bit is set to 0, it means that the transmission information indicates the uplink transmission duration; when the bit is set to 1, it indicates that the transmission information indicates the uplink transmission duration. The total duration of transfers and direct transfers.
  • the buffer report The second mode information in can be set to 1, and the transmission duration information is the sum of the sizes of the uplink buffer and the direct connection buffer, or the sum of the uplink transmission duration and the direct connection transmission duration. If the non-AP STA3 subordinate to the non-AP MLD has no direct data to be transmitted on the direct link 2, and there is uplink data to be transmitted on the uplink and downlink 3, the second mode information in the buffer report It can be set to 0, and the transmission duration information is the size of the uplink buffer or the uplink transmission duration.
  • the uplink buffer is used for buffering uplink data to be transmitted
  • the direct connection buffer is used for buffering data to be transmitted on the direct link
  • the buffer report may include transmission duration information and second mode information. Reference may be made to the relevant description of the second case in the above-mentioned step S701, and details are not repeated here.
  • the non-AP MLD sends a buffer report to the AP MLD on the second uplink and downlink of the multiple uplinks and downlinks.
  • the second uplink and downlink may be any one of a plurality of uplinks and downlinks, or the second uplink and downlink is the same as the first uplink and downlink in step S1001, Reference may be made to relevant descriptions in the above step S702, which will not be repeated here.
  • the AP MLD determines the third transmission duration.
  • the third transmission duration includes the duration allocated by the AP MLD for the first subordinate non-AP STA in the non-AP MLD to transmit on the first link, that is, includes the duration for the first direct link
  • the duration used for the direct connection transmission in the third transmission duration may be a period of time within a certain TXOP obtained by the subordinate AP corresponding to the first link in the AP MLD.
  • the duration used for uplink transmission in the third transmission duration can be corresponding to the first uplink and downlink A period of time within a certain TXOP obtained by the subordinate AP; in the default case of TID-to-link mapping, the duration used for uplink transmission in the third transmission duration can be established with the non-AP MLD in the AP MLD A period of time within a certain TXOP obtained by any subordinate AP that has a link.
  • the AP MLD sends the second duration indication information.
  • the non-AP MLD receives the second duration indication information from the AP MLD.
  • the second duration indication information is used to indicate the third transmission duration, and reference may be made to relevant descriptions in the above step S704, which will not be repeated here.
  • the non-AP MLD sends a buffer report to the AP MLD, which can be used to request the first subordinate non-AP STA in the non-AP MLD on the first direct link and the first uplink and downlink
  • the total duration of the transmission on the road so that after the AP MLD receives the buffer report, it can know that the first non-AP STA subordinate to the non-AP MLD is waiting on the first direct link and the first uplink and downlink.
  • the transmission is performed, so that the subordinate AP corresponding to the first direct link and the first uplink and downlink in the AP MLD can determine to allocate a period of time for the first subordinate non-AP STA in a certain TXOP obtained by it, using The transmission is based on the first direct link and the first uplink and downlink, so that the data can be sent in time and the transmission delay is reduced.
  • the methods provided in the foregoing embodiments of the present application may also be appropriately modified to be applicable to a scenario of an AP cooperation group.
  • the Sharing AP MLD in the AP cooperation group can realize the function of the AP MLD in the above method
  • the Shared AP MLD can realize the function of the non-AP MLD in the above method.
  • the buffer report generated and sent by the Shared AP MLD is used to request the first subordinate AP in the Share AP MLD to transmit on the first uplink and downlink.
  • the link between the first subordinate AP and the target non-AP STA such as the uplink and downlink X shown in Figure 6b.
  • this application also provides some related solutions in BSS transfer scenarios.
  • the source AP MLD can send a BTM request frame to the non-AP MLD to request the non-AP MLD to transfer to the target AP MLD.
  • Some fields of the BTM request frame are related to the link.
  • the deassociation timer field and the effective interval field take the target beacon transmission time (target beacon transmission time, TBTT) of a certain uplink and downlink as the unit, such as deassociation
  • TBTT target beacon transmission time
  • the BTM request frame can be sent through any enabled uplink and downlink between the source AP MLD and the non-AP MLD.
  • their TBTT and timing synchronization function may be different. Therefore, when sending a BTM request frame on any of the enabled uplinks and downlinks, the non-AP MLD may not be able to know which uplink and downlink's TBTT unit is used for the associated timer field and the valid interval field.
  • this application provides the following two methods for the BSS transfer scenario, taking the establishment of multiple uplinks and downlinks between the source AP MLD and the non-AP MLD as an example, as shown in Figure 11, the first method can Including the following steps:
  • the source AP MLD generates a BTM request frame.
  • the BTM request frame includes indication information, and the indication information is used to indicate that the disassociation timer and/or valid time in the BTM request frame is based on the TBTT of a certain uplink and downlink among the multiple uplinks and downlinks .
  • the indication information may be the identifier of the certain uplink and downlink among the multiple uplinks and downlinks, or the indication information is the corresponding ID of the certain uplink and downlink among the multiple uplinks and downlinks.
  • Basic service set identifier basic service set identifier, BSSID.
  • the indication information may be an identifier of the uplink and downlink C or a BSSID corresponding to the uplink and downlink C.
  • the source AP MLD sends a BTM request frame to the non-AP MLD on any one of the multiple uplinks and downlinks.
  • the non-AP MLD receives the BTM request frame from the source AP MLD on any uplink and downlink.
  • the source AP MLD may send the non-AP MLD on any one of the uplink and downlink A, uplink and downlink B, or uplink and downlink C BTM request frame.
  • the source AP MLD adds indication information in the BTM request frame to indicate that the disassociation timer and/or valid time in the BTM request frame is based on the TBTT of a certain uplink and downlink in multiple uplinks and downlinks Unit, so that the non-AP MLD can accurately obtain the sending time of the disassociation frame, or the effective time of the BSS transfer candidate list, thereby improving the efficiency of BSS transfer.
  • the second method may include the following steps:
  • the source AP MLD generates a BTM request frame.
  • the BTM request frame does not additionally add the above indication information, for example, the frame structure of the BTM request frame may be as shown in FIG. 4b.
  • the source AP MLD sends a BTM request frame to the non-AP MLD on the first uplink and downlink among the multiple uplinks and downlinks.
  • the non-AP MLD receives the BTM request frame from the source AP MLD on the first uplink and downlink.
  • the disassociation timer and/or valid interval in the BTM request frame takes the TBTT of the first uplink and downlink among the multiple uplinks and downlinks as a unit. That is to say, the disassociation timer and/or valid interval in the BTM request frame is based on the TBTT of the uplink and downlink where the BTM request frame is transmitted.
  • the source AP MLD sends the BTM request frame to the non-AP MLD on the uplink and downlink C.
  • the disassociation timer and/or valid interval in the BTM request frame is based on the TBTT of the uplink and downlink that transmits the BTM request frame, so that the non-AP MLD can The link accurately obtains the sending time of the de-association frame, or the effective time of the BSS transfer candidate list, thereby improving the efficiency of BSS transfer.
  • the present application also provides a method to describe the content and field settings carried in the neighbor report element carried in the BTM request frame. As shown in Figure 13, the method includes:
  • the source AP MLD generates a BTM request frame.
  • the BTM request frame includes one or more neighbor report elements, and the neighbor report elements are used to indicate the candidate AP recommended by the source AP MLD to the non-AP MLD.
  • the neighbor report element may include a basic variant multi-link element as a subelement.
  • the basic variant multilink element includes a multilink control field and a common information field, and does not include a link information field.
  • the link information field For the structure of the multi-link control field, the common information field, and the link information field, reference may be made to the relevant description in FIG. 2 , and details are not repeated here.
  • the source AP MLD sends a BTM request frame to the non-AP MLD.
  • the non-AP MLD receives the BTM request frame from the source AP MLD.
  • the source AP MLD can send the BTM request frame to the non-AP MLD on any uplink and downlink.
  • the MLD MAC address occurrence field in the multi-link control field may be set to a first value; the first occurrence field in the multi-link control field may be set to a second value, the The first presence field may include a link identification information presence field and a BSS parameter change count presence field.
  • the first value is used to indicate that the field appears in the common information field
  • the second value is used to indicate that the field does not appear in the common information field.
  • the MLD MAC address occurrence field is set to the first value, indicating that the MLD MAC address field appears in the common information field
  • the link identification information occurrence field is set to the second value, indicating that the link identification information field does not appear in the common information field .
  • the first value may be 1, and correspondingly, the second value may be 0.
  • the first value may be 0, and correspondingly, the second value may be 1.
  • the candidate APs indicated by the multiple neighbor report elements belong to the same candidate AP MLD:
  • the second occurrence field in the multilink control field included in the first basic variant multilink element is set to the first value, and the second occurrence field in the multilink control field included in the second basic variant multilink element Set to the second value.
  • the first basic variant multi-link element is a basic variant multi-link element included in the first neighbor report element among the multiple neighbor report elements
  • the second basic variant multi-link element is a multiple neighbor report A basic variant of a multilink element included in a neighbor report element other than the first neighbor report element in the element.
  • the BTM request frame includes three neighbor report elements, the three neighbor report elements respectively indicate candidate AP1, candidate AP2, and candidate AP3, and the candidate AP1, candidate AP2, and candidate AP3 belong to the same candidate AP MLD as an example,
  • the first neighbor report element may be the neighbor report element indicating the candidate AP1
  • the first basic variant multi-link element is the basic variant multi-link element in the neighbor report element indicating the candidate AP1.
  • the second basic variant multi-link element includes a basic variant multi-link element in the neighbor report element indicating candidate AP2 and a basic variant multi-link element in the neighbor report element indicating candidate AP3.
  • the second appearance field may include one or more of the following: a media synchronization delay information appearance field, an EML capability appearance field, or an MLD appearance field.
  • the second occurrence field in the multilink control field included in the basic variant multilink element is set to the first value, which will indicate that the subordinate AP of the AP MLD is the basic variant in other neighbor report elements of the candidate AP
  • the second occurrence field in the multilink control field included in the multilink element is set to a second value, so that the field indicated by the second occurrence field (media synchronization delay information occurrence field, EML capability occurrence field, or MLD occurrence field One or more of them) are carried once in the BTM request to avoid repeated carrying of the same field, thereby reducing signaling overhead.
  • the method of the embodiment of the present application is described above, and the communication device of the embodiment of the present application is introduced below.
  • the communication device of the embodiment of the present application includes a first communication device, a second communication device, and a third communication device.
  • the first A communication device is a non-AP MLD in the above method, which has any function of the non-AP MLD in the above method
  • the second communication device is an AP MLD in the above method, which has any function of the AP MLD in the above method
  • the third communication device is the source AP MLD in the above method, which has any function of the source AP MLD in the above method.
  • the first communication device includes: a processing module and a transceiver module.
  • the processing module is used to generate a buffer report, and the buffer report is used to request the first affiliated non-AP station non-AP STA in the non-AP MLD to perform direct transmission on the first direct link,
  • the first direct link is the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD, and the first target non-AP STA and the first subordinate non-AP MLD of the non-AP MLD -AP STAs belong to the same basic service set BSS;
  • the transceiver module is configured to send a buffer report to the AP MLD on the first uplink and downlink in multiple uplinks and downlinks.
  • processing module and the transceiver module of the first communication device may have the following relationships with the non-AP MLD:
  • the processing module and the transceiver module are the processing module and the transceiver module of the non-AP MLD first subordinate to the non-AP STA.
  • the processing module and the transceiver module are the centralized processing module and the centralized transceiver module of the non-AP MLD.
  • the processing module is the processing module of the first affiliated non-AP STA of the non-AP MLD
  • the transceiver module is the centralized transceiver module of the non-AP MLD.
  • the processing module is the centralized processing module of the non-AP MLD
  • the transceiver module is the first transceiver module of the non-AP MLD subordinate to the non-AP STA.
  • the first communication device provided in the embodiment of the present application is the non-AP MLD in the above method, which has any function of the non-AP MLD in the method shown in Figure 7 above, and details can be found in the above method, here No longer.
  • the second communication device includes: a processing module and a transceiver module.
  • the transceiver module is used to receive the buffer report from the non-AP MLD on the first uplink and downlink among the multiple uplinks and downlinks, and the buffer report is used to request the first subordinate contactless in the non-AP MLD
  • the length of time for the non-AP STA at the entry point to perform direct transmission on the first direct link is between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD.
  • the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD belong to the same basic service set BSS;
  • the processing module is used to determine the second transmission duration, and the second transmission duration includes the AP MLD allocated for the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link duration;
  • the transceiver module is further configured to send first duration indicating information, where the first duration indicating information is used to indicate the second transmission duration.
  • processing module and the transceiver module of the second communication device may have the following relationships with the AP MLD:
  • the processing module and the transceiver module are the processing module and the transceiver module of the affiliated AP corresponding to the first direct link in the AP MLD.
  • the processing module and the transceiver module are the centralized processing module and the centralized transceiver module of AP MLD.
  • the processing module is the processing module of the subordinate AP corresponding to the first direct link in the AP MLD
  • the transceiver module is the centralized transceiver module of the AP MLD.
  • the processing module is a centralized processing module of the AP MLD
  • the transceiver module is a transceiver module of the AP corresponding to the first direct link in the AP MLD.
  • the second communication device provided in the embodiment of the present application is the AP MLD in the above method, which has any function of the AP MLD in the method shown in FIG.
  • the third communication device includes: a processing module and a transceiver module.
  • the processing module is used to generate a basic service set transfer management BTM request frame, the BTM request frame includes indication information, and the indication information is used to indicate the disassociation timer and/or effective interval in the BTM request frame in multiple uplinks and downlinks
  • the target beacon transmission time TBTT of a certain uplink and downlink is taken as the unit; the transceiver module is used to send a BTM request frame to the non-AP MLD on any uplink and downlink of the multiple uplinks and downlinks.
  • the processing module is used to generate a basic service set transfer management BTM request frame; the transceiver module is used to send a BTM request frame to the non-AP MLD on the first uplink and downlink in multiple uplinks and downlinks, and the BTM request
  • the disassociation timer and/or valid interval in the frame takes the target beacon transmission time TBTT of the first uplink and downlink among the multiple uplinks and downlinks as a unit.
  • the processing module is used to generate a basic service set transfer management BTM request frame, the BTM request frame includes one or more neighbor report elements, and the neighbor report element is used to indicate the candidate access point AP recommended by the source AP MLD to the non-AP MLD;
  • the neighbor report element includes a basic variant multi-link element, and the basic variant multi-link element includes a multi-link control field and a common information field, and does not include a link information field;
  • the The transceiver module is used to send the BTM request frame to the non-AP MLD.
  • processing module and the transceiver module of the third communication device may have the following relationships with the source AP MLD:
  • the processing module and the transceiver module are the processing module and the transceiver module of a certain subordinate AP of the source AP MLD.
  • the processing module and the transceiver module are the centralized processing module and the centralized transceiver module of the source AP MLD.
  • the processing module is a processing module of a certain subordinate AP of the source AP MLD
  • the transceiver module is a centralized transceiver module of the source AP MLD.
  • the processing module is a centralized processing module of the source AP MLD
  • the transceiver module is a transceiver module of a certain subordinate AP of the source AP MLD.
  • the third communication device provided in the embodiment of the present application is the source AP MLD in the above method, which has any function of the source AP MLD in the method shown in FIG. 11 or FIG. 12 or FIG. 13.
  • the above method please refer to the above method, which will not be repeated here.
  • first communication device the second communication device, and the third communication device according to the embodiments of the present application
  • the following describes the possible product forms of the first communication device, the second communication device, and the third communication device.
  • any product of any form having the features of the first communication device described above in FIG. 14 any product of any form having the features of the second communication device described in FIG.
  • Products of any form with the features of the third communication device fall within the scope of protection of this application.
  • the following introduction is only an example, and the product forms of the first communication device, the second communication device, and the third communication device in the embodiment of the present application are not limited thereto.
  • 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 a general bus architecture.
  • the first communication device includes a processor and a transceiver internally connected to communicate with the processor.
  • the processor is configured to generate a buffer report, and the buffer report is used to request the first subordinate non-AP station non-AP STA in the non-AP MLD to perform a direct connection transmission on the first direct link,
  • the first direct link is the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD, and the first target non-AP STA and the first subordinate non-AP MLD of the non-AP MLD -AP STAs belong to the same basic service set BSS;
  • the transceiver is configured to send a buffer report to the AP MLD on the first uplink and downlink in the multiple uplinks and downlinks.
  • the first communication device may further include a memory, where the memory is used to store instructions executed by the processor.
  • the second communication device includes a processor and a transceiver internally connected to communicate with the processor.
  • the transceiver is used to receive a buffer report from a non-AP MLD on the first uplink and downlink among multiple uplinks and downlinks, and the buffer report is used to request the first subordinate contactless in the non-AP MLD
  • the first direct link is between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD.
  • the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD belong to the same basic service set BSS;
  • the processor is configured to determine a second transmission duration, where the second transmission duration includes the time allocated by the AP MLD for the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link duration;
  • the transceiver is further configured to send first duration indication information, where the first duration indication information is used to indicate the second transmission duration.
  • the second communication device may further include a memory, where the memory is used to store instructions executed by the processor.
  • the third communication device includes a processor and a transceiver internally connected to communicate with the processor.
  • the processor is configured to generate a basic service set transfer management BTM request frame, where the BTM request frame includes indication information, and the indication information is used to indicate that the de-association timer and/or effective interval in the BTM request frame are used in multiple uplinks and downlinks
  • the processor is used to generate a basic service set transfer management BTM request frame; the transceiver is used to send a BTM request frame to the non-AP MLD on the first uplink and downlink in multiple uplinks and downlinks, and the BTM request
  • the disassociation timer and/or valid interval in the frame takes the target beacon transmission time TBTT of the first uplink and downlink among the multiple uplinks and downlinks as a unit.
  • the processor is used to generate a basic service set transfer management BTM request frame, the BTM request frame includes one or more neighbor report elements, and the neighbor report element is used to indicate the candidate access point AP recommended by the source AP MLD to the non-AP MLD;
  • the neighbor report element includes the basic variant multi-link element, the basic variant multi-link element includes the multi-link control field and the common information field, and does not include the link information field; the Transceiver for sending BTM request frames to non-AP MLD.
  • the third communication device may further include a memory, where the memory is used to store instructions executed by the processor.
  • 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 a general-purpose processor.
  • the general-purpose processor implementing the first communication means includes a processing circuit and an output interface internally connected and communicating with the processing circuit.
  • the processing circuit is used to generate a buffer report, and the buffer report is used to request the first affiliated non-AP station non-AP STA in the non-AP MLD to perform a direct connection transmission on the first direct link,
  • the first direct link is the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD, and the first target non-AP STA and the first subordinate non-AP MLD of the non-AP MLD -AP STAs belong to the same basic service set BSS;
  • the output interface is used to send a buffer report to the AP MLD on the first uplink and downlink in the multiple uplinks and downlinks.
  • the general-purpose processor may further include a storage medium for storing instructions executed by the processing circuit.
  • the general-purpose processor implementing the second communication means includes a processing circuit and an output interface and an input interface internally connected and communicating with the processing circuit.
  • This input interface is used to receive a buffer report from a non-AP MLD on the first uplink and downlink among multiple uplinks and downlinks, and the buffer report is used to request the first subordinate contactless in the non-AP MLD
  • the first direct link is between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD.
  • the link between the first target non-AP STA and the first subordinate non-AP STA of the non-AP MLD belong to the same basic service set BSS;
  • the processing circuit is used to determine the second transmission duration, and the second transmission duration includes the time allocated by the AP MLD for the first subordinate non-AP STA in the non-AP MLD to perform direct transmission on the first direct link duration;
  • the output interface is further configured to send first duration indication information, where the first duration indication information is used to indicate the second transmission duration.
  • the general-purpose processor may further include a storage medium for storing instructions executed by the processing circuit.
  • the general-purpose processor implementing the third communication means includes a processing circuit and an output interface internally connected and communicating with the processing circuit.
  • the processing circuit is used to generate a basic service set transfer management BTM request frame, the BTM request frame includes indication information, and the indication information is used to indicate the de-association timer and/or effective interval in the BTM request frame in multiple uplinks and downlinks
  • the target beacon transmission time TBTT of one of the uplinks and downlinks is the unit; the output interface is used to send a BTM request frame to the non-AP MLD on any one of the uplinks and downlinks.
  • the processing circuit is used to generate a basic service set transfer management BTM request frame; the output interface is used to send a BTM request frame to the non-AP MLD on the first uplink and downlink in multiple uplinks and downlinks, and the BTM request
  • the disassociation timer and/or valid interval in the frame takes the target beacon transmission time TBTT of the first uplink and downlink among the multiple uplinks and downlinks as a unit.
  • the processing circuit is used to generate a basic service set transfer management BTM request frame, the BTM request frame includes one or more neighbor report elements, and the neighbor report element is used to indicate the candidate access point AP recommended by the source AP MLD to the non-AP MLD;
  • the neighbor report element includes a basic variant multi-link element, and the basic variant multi-link element includes a multi-link control field and a common information field, and does not include a link information field;
  • the Output interface used to send BTM request frame to non-AP MLD.
  • the general-purpose processor may further include a storage medium for storing instructions executed by the processing circuit.
  • the first communication device, the second communication device, and the third communication device described in the embodiments of the present application can also be implemented using the following: one or more field programmable gate arrays ( field-programmable gate array (FPGA), programmable logic device (programmable logic device, PLD), controller, state machine, gate logic, discrete hardware components, any other suitable circuit, or Any combination of circuits with various functions.
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • controller state machine
  • gate logic discrete hardware components
  • discrete hardware components any other suitable circuit, or Any combination of circuits with various functions.
  • first communication device second communication device
  • third communication device in various product forms respectively have any functions of the non-AP MLD, AP MLD, and source AP MLD in the above-mentioned method embodiments. No longer.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices or units, and may also be electrical, mechanical or other forms of connection.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units can be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of this application is essentially or part of the contribution to the prior art, or all or part of the technical solution can be embodied in the form of software products, and the computer software products are stored in a storage medium
  • several instructions are included to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (read-only memory, ROM), random access memory (random access memory, RAM), magnetic disk or optical disc and other media that can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供一种缓冲区报告发送、接收方法及装置，适用于Wi-Fi系统中non-AP MLD与AP MLD之间建立有多条上下行链路的场景，使得直连链路上的数据能够及时发送，降低直连链路上的传输时延。该方法包括：non-AP MLD生成缓冲区报告，并在该多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告。其中，该缓冲区报告用于请求non-AP MLD中的第一隶属non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和第一隶属non-AP STA之间的链路，第一目标non-AP STA和第一隶属non-AP STA属于同一BSS。相应的，AP MLD收到该缓冲区报告后，可以为该第一隶属non-AP STA分配第二传输时长，该第二传输时长包括用于第一隶属non-AP STA在第一直连链路上进行直连传输的时长。

Description

缓冲区报告发送、接收方法及装置
本申请要求于2021年07月23日提交国家知识产权局、申请号为202110838424.5、申请名称为“缓冲区报告发送、接收方法及装置”的中国专利申请的优先权和于2021年09月17日提交国家知识产权局、申请号为202111093436.6、申请名称为“缓冲区报告发送、接收方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及缓冲区报告发送、接收方法及装置。
背景技术
无线保真(wireless fidelity，Wi-Fi)系统部署在非授权频谱上，系统中的站点(station，STA)通过竞争来使用信道资源。某个站点在信道竞争成功之后，可以预留一段时间进行数据传输，该段时间被称为一个传输机会(transmission opportunity，TXOP)。成功预留TXOP的站点被称为TXOP持有者(holder)。在一个TXOP内，只有TXOP holder可以主动发送数据，其他站点只能进行数据接收或者发送其收到的数据的响应帧。
在电气和电子工程师协会(institute of electrical and electronics engineers，IEEE)802.11be标准中，对TXOP机制进行了如下扩展：作为TXOP holder的接入点站点(access point station，AP STA)可以将其预留的TXOP内的一部分时间分配给非接入点站点(non-access point station,non-AP STA)，使得该non-AP STA在被分配的时间内与另一non-AP STA进行点到点(point to point，P2P)传输，或者向该AP STA发送上行数据。
在扩展的TXOP机制中，作为TXOP holder的AP STA为non-AP STA分配TXOP内的部分时间时，可能需要获知该non-AP STA所需的传输时长。
发明内容
本申请实施例提供缓冲区报告发送、接收方法及装置，使得AP MLD中与直连链路所对应的AP可以确定在其获得的某个TXOP内为某个隶属non-AP STA分配一段时间，用于直连链路上的传输，从而使得直连链路上的数据能够及时发送，降低直连链路上的传输时延。
第一方面，提供一种缓冲区报告发送方法，该方法应用于非接入点多链路设备non-AP MLD，该non-AP MLD与接入点多链路设备AP MLD之间建立有多条上下行链路。该方法包括：non-AP MLD生成缓冲区报告，并在该多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告。其中，该缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS。
基于该方案，non-AP MLD向AP MLD发送缓冲区报告，该缓冲区报告能够用于请求non-AP MLD中的第一隶属non-AP STA在第一直连链路上进行直连传输的时长，使得AP MLD在收到该缓冲区报告后，可以获知non-AP MLD的第一隶属non-AP STA在第一直连链路上待进行直连传输，从而AP MLD中与第一直连链路所对应的隶属AP可以在其获得的某个TXOP内为第一隶属non-AP STA分配一段时间，用于第一直连链路 上的传输，从而使得直连链路上的数据能够及时发送，降低直连链路上的传输时延。
在一些可能的设计中，该缓冲区报告包括链路信息，该链路信息用于指示上述第一直连链路。
基于该可能的设计，能够向AP MLD指示待进行直连传输的直连链路，从而使得该直连链路对应的隶属AP可以在其获得的某个TXOP内分配时间，用于该直连链路上的传输。
在一些可能的设计中，该链路信息为第一直连链路的标识，或者，该链路信息为比特位图。
基于该可能的设计，通过直连链路的标识能够显式指示直连链路，通过比特位图能够隐式指示直连链路。
在一些可能的设计中，该缓冲区报告包括传输时长信息，传输时长信息用于指示第一传输时长，第一传输时长为non-AP MLD中的第一隶属non-AP STA在第一直连链路上进行直连传输的时长。
基于该可能的设计，能够向AP MLD指示待进行直连传输的传输时长，从而使得AP MLD能够分配相应的时长，用于直连传输。
在一些可能的设计中，该第一上下行链路为多条上下行链路中的任意一条上下行链路。
基于该可能的设计，non-AP MLD可以在任意一条上下行链路上向AP MLD发送缓冲区报告，可以提高缓冲区报告发送时的灵活性。
在一些可能的设计中，该缓冲区报告还包括缓冲区类型信息，缓冲区类型信息用于指示缓冲区报告为直连传输对应的缓冲区报告。
基于该可能的设计，能够向AP MLD指示缓冲区报告为直连传输对应的缓冲区报告，从而使得AP MLD在直连链路对应的隶属AP获得的某个TXOP内分配传输时长。
在一些可能的设计中，该缓冲区报告包括链路信息，且不包括用于指示第一直连链路的链路信息，传输时长信息用于指示第一传输时长，第一传输时长为non-AP MLD中的第一隶属non-AP STA在第一直连链路上进行直连传输的时长。
在一些可能的设计中，第一上下行链路的标识和第一直连链路的标识相同。
基于上述两种可能的设计，通过在标识与第一直连链路的标识相同的第一上下行链路上发送缓冲区报告，隐式指示该缓冲区报告用于请求第一直连链路的进行直连传输的时长，从而节省信令开销。
在一些可能的设计中，传输时长信息包括第一传输时长或第一缓冲区的大小，第一缓冲区用于缓存non-AP MLD中的第一隶属non-AP STA待在第一直连链路上发送的数据。
在一些可能的设计中，non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告，包括：non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送管理帧，管理帧包括缓冲区报告。基于该可能的设计，可以通过管理帧携带缓冲区报告。
在一些可能的设计中，上述管理帧可以包括聚合控制字段，该聚合控制字段包括缓冲区报告。基于该可能的设计，可以通过管理帧的聚合控制字段携带缓冲区报告。
在一些可能的设计中，该管理帧的帧头包括多链路设备信息，该多链路设备信息用于指示non-AP MLD。
在一些可能的设计中，non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告，包括：non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送数据帧，数据帧包括聚合控制字段，聚合控制包括缓冲区报告。基于该可能的设计，可以通过数据帧的聚合控制字段携带缓冲区报告。
在一些可能的设计中，该数据帧的帧头包括多链路设备信息，多链路设备信息用于指示non-AP MLD。基于该可能的设计，能够向AP MLD指示请求直连传输时长的non-AP MLD。
在一些可能的设计中，non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告，可以包括：non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送数据帧，该数据帧包括QoS control字段，QoS control字段包括缓冲区报告。示例性的，该数据帧为QoS Null帧。
在一些可能的设计中，该缓冲区报告还包括资源请求类型，该资源请求类型用于指示缓冲区报告为直连传输对应的缓冲区报告。
在一些可能的设计中，QoS Null帧中的QoS control字段的Bit 7或Bit 3用于承载该资源请求类型。
第二方面，提供一种缓冲区报告发送方法，该方法应用于接入点多链路设备AP MLD，AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该方法包括：AP MLD在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；之后，AP MLD确定第二传输时长，并发送第一时长指示信息，该第一时长指示信息用于指示该第二传输时长。其中，该第二传输时长包括AP MLD为non-AP MLD中的第一隶属non-AP STA分配的用于在第一直连链路上进行直连传输的时长。
基于该方案，AP MLD接收到的缓冲区报告能够用于请求non-AP MLD中的第一隶属non-AP STA在第一直连链路上进行直连传输的时长，使得AP MLD可以获知non-AP MLD的第一隶属non-AP STA在第一直连链路上待进行直连传输，从而AP MLD中与第一直连链路所对应的隶属AP可以在其获得的某个TXOP内为第一隶属non-AP STA分配一段时间，用于第一直连链路上的传输，进而使得直连链路上的数据能够及时发送，降低直连链路上的传输时延。
在一些可能的设计中，该缓冲区报告包括链路信息，该链路信息用于指示上述第一直连链路。
在一些可能的设计中，该链路信息为第一直连链路的标识，或者，该链路信息为比特位图。
在一些可能的设计中，该缓冲区报告包括传输时长信息，传输时长信息用于指示第一传输时长，第一传输时长为non-AP MLD中的第一隶属non-AP STA在第一直连链路上进行直连传输的时长。
在一些可能的设计中，上述第一上下行链路为多条上下行链路中的任意一条上下行链路。
在一些可能的设计中，缓冲区报告还包括缓冲区类型信息，缓冲区类型信息用于指示缓冲区报告为直连传输对应的缓冲区报告。
在一些可能的设计中，缓冲区报告包括链路信息，且不包括用于指示第一直连链路的链路信息，传输时长信息用于指示第一传输时长，第一传输时长为non-AP MLD中的第一隶属non-AP STA在第一直连链路上进行直连传输的时长。
在一些可能的设计中，第一上下行链路的标识和第一直连链路的标识相同。
在一些可能的设计中，传输时长信息包括第一传输时长或第一缓冲区的大小，第一缓冲区用于缓存non-AP MLD中的第一隶属non-AP STA待在第一直连链路上发送的数据。
在一些可能的设计中，AP MLD在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的缓冲区报告，包括：AP MLD在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的管理帧，该管理帧包括缓冲区报告。
在一些可能的设计中，该管理帧可以包括聚合控制字段，该聚合控制字段包括缓冲区报告。
在一些可能的设计中，该管理帧的帧头包括多链路设备信息，多链路设备信息用于指示non-AP MLD。
在一些可能的设计中，AP MLD在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的缓冲区报告，包括：AP MLD在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的数据帧，数据帧包括聚合控制字段，聚合控制包括缓冲区报告。
在一些可能的设计中，该数据帧的帧头包括多链路设备息，该多链路设备信息用于指示non-AP MLD。
在一些可能的设计中，AP MLD在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的缓冲区报告，包括：AP MLD在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的数据帧，该数据帧包括QoS control字段，QoS control字段包括缓冲区报告。示例性的，该数据帧为QoS Null帧。
在一些可能的设计中，该缓冲区报告还包括资源请求类型，该资源请求类型用于指示缓冲区报告为直连传输对应的缓冲区报告。
在一些可能的设计中，QoS Null帧的QoS control字段的Bit 7或Bit 3用于承载该资源请求类型。
其中，第二方面的任一可能的设计所带来的技术效果，可参考上述第一方面中相应设计所带来的技术效果，在此不再赘述。
第三方面，提供一种通信方法，该方法应用于源接入点多链路设备AP MLD，该源AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该方法包括：源AP MLD生成基本服务集转移管理BTM请求帧，并在多条上下行链路中的任一条上下行链路上向non-AP MLD发送BTM请求帧。其中，该BTM请求帧包括指示信息，指示信息用于指示BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的某一条上下行链路的目标信标传输时间TBTT为单位。
基于该方案，源AP MLD在BTM请求帧中添加指示信息，以指示BTM请求帧中的去关联定时器和/或有效时间以多条上下行链路中的某一条上下行链路的TBTT为单位，从而使得non-AP MLD可以准确获取去关联帧的发送时间，或BSS转移备选列表的有效时间，进而提高BSS转移的效率。
在一些可能的设计中，该指示信息为多条上下行链路中的某一条上下行链路的标识，或者，指示信息为多条上下行链路中的某一条上下行链路的对应的基本服务集的标识。
第四方面，提供一种通信方法，该方法应用于源接入点多链路设备AP MLD，源AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该方法包括：源AP MLD生成基本服务集转移管理BTM请求帧，并在多条上下行链路中的第一上下行链路上向non-AP MLD发送BTM请求帧，BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的第一上下行链路的目标信标传输时间TBTT为单位。
基于该方案，BTM请求帧中的去关联定时器和/或有效间隔以传输该BTM请求帧的上下行链路的TBTT为单位，使得non-AP MLD可以根据收到该BTM请求帧的上下行链路 准确获取去关联帧的发送时间，或BSS转移备选列表的有效时间，进而提高BSS转移的效率。
第五方面，提供一种通信方法，该方法包括：源接入点多链路设备AP MLD生成基本服务集转移管理BTM请求帧，并向non-AP MLD发送该BTM请求帧。其中，该BTM请求帧包括一个或多个邻居报告元素，该邻居报告元素用于指示源AP MLD向non-AP MLD推荐的候选接入点AP；当候选接入点属于候选AP MLD时，邻居报告元素包括基本变体多链路元素，基本变体多链路元素包括多链路控制字段和共同信息字段，且不包括链路信息字段。
基于该方案，BTM请求帧的邻居报告元素中携带基本变体多链路元素来指示候选AP所属的AP MLD时，由于在BSS转移过程中无需获取链路信息，从而在基本变体多链路元素中不携带链路信息字段可以节省信令开销，同时不影响BSS转移流程执行。
在一些可能的设计中，该多链路控制字段中的多链路设备媒体接入控制地址出现字段设置为第一数值，多链路控制字段中的第一出现字段设置为第二数值，第一出现字段包括链路标识信息出现字段和基本服务集参数更改计数出现字段，第一数值用于指示字段在共同信息字段中出现，第二数值用于指示字段在共同信息字段中不出现。
在一些可能的设计中，该多个邻居报告元素指示的多个候选AP属于同一候选AP MLD的情况下：第一基本变体多链路元素包括的多链路控制字段中的第二出现字段设置为第一数值，第二基本变体多链路元素包括的多链路控制字段中的第二出现字段设置为第二数值。其中，第一基本变体多链路元素为多个邻居报告元素中的第一个邻居报告元素包括的基本变体多链路元素，第二基本变体多链路元素为多个邻区报告元素中除第一个邻居报告元素外的邻居报告元素包括的基本变体多链路元素。
在一些可能的设计中，第二出现字段包括以下一项或多项：媒体同步时延信息出现字段、增强多链路能力出现字段、或多链路设备能力出现字段。
基于上述可能的设计，对于同一BTM请求帧指示的多个候选AP属于同一AP MLD的情况，可以指示该AP MLD的隶属AP为候选AP的第一个邻居报告元素中携带基本变体多链路元素，且将该基本变体多链路元素包括的多链路控制字段中的第二出现字段设置为第一数值，将指示该AP MLD的隶属AP为候选AP的其他邻居报告元素中的基本变体多链路元素所包括的多链路控制字段中的第二出现字段设置为第二数值，使得媒体同步时延信息出现字段、EML能力出现字段、或MLD出现字段中的一项或多项在BTM请求中携带一次，避免重复携带相同的字段，从而减少信令开销。
第六方面，提供一种缓冲区报告发送方法，该方法应用于非接入点多链路设备non-AP MLD，该non-AP MLD与接入点多链路设备AP MLD之间建立有多条上下行链路。该方法包括：non-AP MLD生成缓冲区报告，该缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一链路上进行传输的时长，该第一链路包括第一直连链路和第一上下行链路，该第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，该第一上下行链路为该AP MLD的第一隶属AP和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA、non-AP MLD的第一隶属non-AP STA、以及AP MLD的第一隶属AP属于同一基本服务集BSS；non-AP MLD在该多条上下行链路中的第二上下行链路上向AP MLD发送缓冲区报告。
基于该方案，non-AP MLD向AP MLD发送缓冲区报告，该缓冲区报告能够用于请求non-AP MLD中的第一隶属non-AP STA在第一直连链路和第一上下行链路上进行传输的总时长，使得AP MLD在收到该缓冲区报告后，可以获知non-AP MLD的第一隶 属non-AP STA在第一直连链路和第一上下行链路上待进行传输，从而AP MLD中与第一直连链路和第一上下行链路上所对应的隶属AP可以确定在其获得的某个TXOP内为第一隶属non-AP STA分配一段时间，用于第一直连链路和第一上下行链路上的传输，从而使得数据能够及时发送，降低传输时延。
第七方面，提供一种非接入点多链路设备non-AP MLD，该non-AP MLD与接入点多链路设备AP MLD之间建立有多条上下行链路。该non-AP MLD包括：处理模块和收发模块。
该处理模块，用于生成缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该收发模块，用于在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告。
第七方面提供的non-AP MLD用于实现上述第一方面或第一方面的任一种可能的设计中non-AP MLD的行为功能，具体细节可参见上述第一方面或第一方面的任一种可能的设计中的描述，此处不再赘述。
第八方面，提供一种接入点多链路设备AP MLD，该AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该AP MLD包括：处理模块和收发模块。
该收发模块，用于在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该处理模块，用于确定第二传输时长，第二传输时长包括AP MLD为non-AP MLD中的第一隶属non-AP STA分配的用于在第一直连链路上进行直连传输的时长；
该收发模块，还用于发送第一时长指示信息，该第一时长指示信息用于指示该第二传输时长。
第八方面提供的AP MLD用于实现上述第二方面或第二方面的任一种可能的设计中AP MLD的行为功能，具体细节可参见上述第二方面或第二方面的任一种可能的设计中的描述，此处不再赘述。
第九方面，提供一种源接入点多链路设备AP MLD，该源AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该源AP MLD包括：处理模块和收发模块。
该处理模块，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括指示信息，指示信息用于指示BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的某一条上下行链路的目标信标传输时间TBTT为单位；
该收发模块，用于在多条上下行链路中的任一条上下行链路上向non-AP MLD发送BTM请求帧。
第九方面提供的源AP MLD用于实现上述第三方面或第三方面的任一种可能的设计中源AP MLD的行为功能，具体细节可参见上述第三方面或第三方面的任一种可能的设计中的描述，此处不再赘述。
第十方面，提供一种源接入点多链路设备AP MLD，该源AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该源AP MLD包括：处理模块和收发模块。
该处理模块，用于生成基本服务集转移管理BTM请求帧；
该收发模块，用于在多条上下行链路中的第一上下行链路上向non-AP MLD发送BTM请求帧，BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的第一上下行链路的目标信标传输时间TBTT为单位。
第十方面提供的源AP MLD用于实现上述第四方面或第四方面的任一种可能的设计中源AP MLD的行为功能，具体细节可参见上述第四方面或第四方面的任一种可能的设计中的描述，此处不再赘述。
第十一方面，提供一种源接入点多链路设备AP MLD，该源AP MLD与非接入点多链路。该源AP MLD包括：处理模块和收发模块。
该处理模块，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括一个或多个邻居报告元素，邻居报告元素用于指示源AP MLD向non-AP MLD推荐的候选接入点AP；当候选接入点属于候选AP MLD时，邻居报告元素包括基本变体多链路元素，基本变体多链路元素包括多链路控制字段和共同信息字段，且不包括链路信息字段；
该收发模块，用于向non-AP MLD发送BTM请求帧。
第十一方面提供的源AP MLD用于实现上述第五方面或第五方面的任一种可能的设计中源AP MLD的行为功能，具体细节可参见上述第五方面或第五方面的任一种可能的设计中的描述，此处不再赘述。
第十二方面，提供一种非接入点多链路设备non-AP MLD，该non-AP MLD与接入点多链路设备AP MLD之间建立有多条上下行链路。该non-AP MLD包括：处理电路以及与处理电路内部连接通信的输出接口。
该处理电路，用于生成缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该输出接口，用于在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告。
第十二方面提供的non-AP MLD用于实现上述第一方面或第一方面的任一种可能的设计中non-AP MLD的行为功能，具体细节可参见上述第一方面或第一方面的任一种可能的设计中的描述，此处不再赘述。
第十三方面，提供一种接入点多链路设备AP MLD，该AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该AP MLD包括：处理电路以及与处理电路内部连接通信的输出接口和输入接口。
该输入接口，用于在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该处理电路，用于确定第二传输时长，第二传输时长包括AP MLD为non-AP MLD中的第一隶属non-AP STA分配的用于在第一直连链路上进行直连传输的时长；
该输出接口，还用于发送第一时长指示信息，该第一时长指示信息用于指示该第二传输时长。
第十三方面提供的AP MLD用于实现上述第二方面或第二方面的任一种可能的设计中AP MLD的行为功能，具体细节可参见上述第二方面或第二方面的任一种可能的设计 中的描述，此处不再赘述。
第十四方面，提供一种源接入点多链路设备AP MLD，该源AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该源AP MLD包括：处理电路以及与处理电路内部连接通信的输出接口。
该处理电路，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括指示信息，指示信息用于指示BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的某一条上下行链路的目标信标传输时间TBTT为单位；
该输出接口，用于在多条上下行链路中的任一条上下行链路上向non-AP MLD发送BTM请求帧。
第十四方面提供的源AP MLD用于实现上述第三方面或第三方面的任一种可能的设计中源AP MLD的行为功能，具体细节可参见上述第三方面或第三方面的任一种可能的设计中的描述，此处不再赘述。
第十五方面，提供一种源接入点多链路设备AP MLD，该源AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该源AP MLD包括：处理电路以及与处理电路内部连接通信的输出接口。
该处理电路，用于生成基本服务集转移管理BTM请求帧；
该输出接口，用于在多条上下行链路中的第一上下行链路上向non-AP MLD发送BTM请求帧，BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的第一上下行链路的目标信标传输时间TBTT为单位。
第十五方面提供的源AP MLD用于实现上述第四方面或第四方面的任一种可能的设计中源AP MLD的行为功能，具体细节可参见上述第四方面或第四方面的任一种可能的设计中的描述，此处不再赘述。
第十六方面，提供一种源接入点多链路设备AP MLD，该源AP MLD与非接入点多链路。该源AP MLD包括：处理电路以及与处理电路内部连接通信的输出接口。
该处理电路，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括一个或多个邻居报告元素，邻居报告元素用于指示源AP MLD向non-AP MLD推荐的候选接入点AP；当候选接入点属于候选AP MLD时，邻居报告元素包括基本变体多链路元素，基本变体多链路元素包括多链路控制字段和共同信息字段，且不包括链路信息字段；
该输出接口，用于向non-AP MLD发送BTM请求帧。
第十六方面提供的源AP MLD用于实现上述第四方面或第四方面的任一种可能的设计中源AP MLD的行为功能，具体细节可参见上述第四方面或第四方面的任一种可能的设计中的描述，此处不再赘述。
第十七方面，提供一种非接入点多链路设备non-AP MLD，该non-AP MLD与接入点多链路设备AP MLD之间建立有多条上下行链路。该non-AP MLD包括：处理器以及与处理器内部连接通信的收发器。
该处理器，用于生成缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该收发器，用于在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告。
第十七方面提供的non-AP MLD用于实现上述第一方面或第一方面的任一种可能的 设计中non-AP MLD的行为功能，具体细节可参见上述第一方面或第一方面的任一种可能的设计中的描述，此处不再赘述。
第十八方面，提供一种接入点多链路设备AP MLD，该AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该AP MLD包括：处理器以及与处理器内部连接通信的收发器。
该收发器，用于在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该处理器，用于确定第二传输时长，第二传输时长包括AP MLD为non-AP MLD中的第一隶属non-AP STA分配的用于在第一直连链路上进行直连传输的时长；
该收发器，还用于发送第一时长指示信息，该第一时长指示信息用于指示该第二传输时长。
第十八方面提供的AP MLD用于实现上述第二方面或第二方面的任一种可能的设计中AP MLD的行为功能，具体细节可参见上述第二方面或第二方面的任一种可能的设计中的描述，此处不再赘述。
第十九方面，提供一种源接入点多链路设备AP MLD，该源AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该源AP MLD包括：处理器以及与处理器内部连接通信的收发器。
该处理器，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括指示信息，指示信息用于指示BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的某一条上下行链路的目标信标传输时间TBTT为单位；
该收发器，用于在多条上下行链路中的任一条上下行链路上向non-AP MLD发送BTM请求帧。
第十九方面提供的源AP MLD用于实现上述第三方面或第三方面的任一种可能的设计中源AP MLD的行为功能，具体细节可参见上述第三方面或第三方面的任一种可能的设计中的描述，此处不再赘述。
第二十方面，提供一种源接入点多链路设备AP MLD，该源AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路。该源AP MLD包括：处理器以及与处理器内部连接通信的收发器。
该处理器，用于生成基本服务集转移管理BTM请求帧；
该收发器，用于在多条上下行链路中的第一上下行链路上向non-AP MLD发送BTM请求帧，BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的第一上下行链路的目标信标传输时间TBTT为单位。
第二十方面提供的源AP MLD用于实现上述第四方面或第四方面的任一种可能的设计中源AP MLD的行为功能，具体细节可参见上述第四方面或第四方面的任一种可能的设计中的描述，此处不再赘述。
第二十一方面，提供一种源接入点多链路设备AP MLD，该源AP MLD与非接入点多链路。该源AP MLD包括：处理器以及与处理器内部连接通信的收发器。
该处理器，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括一个或多个邻 居报告元素，邻居报告元素用于指示源AP MLD向non-AP MLD推荐的候选接入点AP；当候选接入点属于候选AP MLD时，邻居报告元素包括基本变体多链路元素，基本变体多链路元素包括多链路控制字段和共同信息字段，且不包括链路信息字段；
该收发器，用于向non-AP MLD发送BTM请求帧。
第二十一方面提供的源AP MLD用于实现上述第四方面或第四方面的任一种可能的设计中源AP MLD的行为功能，具体细节可参见上述第四方面或第四方面的任一种可能的设计中的描述，此处不再赘述。
第二十二方面，本申请实施例提供一种计算机可读存储介质，用于存储计算机程序，所述计算机程序包括用于执行上述第一方面或第一方面任意可能的实现方式的指令。
第二十三方面，本申请实施例提供一种计算机可读存储介质，用于存储计算机程序，所述计算机程序包括用于执行上述第二方面或第二方面任意可能的实现方式的指令。
第二十四方面，本申请实施例提供一种计算机可读存储介质，用于存储计算机程序，所述计算机程序包括用于执行上述第三方面或第三方面任意可能的实现方式的指令。
第二十五方面，本申请实施例提供一种计算机可读存储介质，用于存储计算机程序，所述计算机程序包括用于执行上述第四方面或第四方面任意可能的实现方式的指令。
第二十六方面，本申请实施例提供一种计算机可读存储介质，用于存储计算机程序，所述计算机程序包括用于执行上述第五方面或第五方面任意可能的实现方式的指令。
第二十七方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括用于执行上述第一方面或第一方面任意可能的实现方式的指令。
第二十八方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括用于执行上述第二方面或第二方面任意可能的实现方式的指令。
第二十九方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括用于执行上述第三方面或第三方面任意可能的实现方式的指令。
第三十方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括用于执行上述第四方面或第四方面任意可能的实现方式的指令。
第三十一方面，本申请实施例提供一种计算机程序产品，所述计算机程序产品包括用于执行上述第五方面或第五方面任意可能的实现方式的指令。
第三十二方面，本申请实施例提供一种通信系统，所述通信系统包括上述第七方面或第十二方面或第十七方面所提供的non-AP MLD，和，AP MLD。
第三十三方面，本申请实施例提供一种通信系统，所述通信系统包括上述第八方面或第十三方面或第十八方面所提供的AP MLD，和，non-AP MLD。
第三十四方面，本申请实施例提供一种通信系统，所述通信系统包括上述第九方面或第十四方面或第十九方面所提供的AP MLD，和，non-AP MLD。
第三十五方面，本申请实施例提供一种通信系统，所述通信系统包括上述第十方面或第十五方面或第二十方面所提供的AP MLD，和，non-AP MLD。
第三十六方面，本申请实施例提供一种通信系统，所述通信系统包括上述第十一方 面或第十六方面或第二十一方面所提供的AP MLD，和，non-AP MLD。
附图说明
图1为本申请实施例提供的一种多链路设备的示意图；
图2为本申请实施例提供的一种多链路元素的结构示意图；
图3为本申请实施例提供的一种BSS转移管理的流程示意图；
图4a为本申请实施例提供的一种BTM询问帧的帧结构示意图；
图4b为本申请实施例提供的一种BTM请求帧的帧结构示意图；
图4c为本申请实施例提供的一种BTM响应帧的帧结构示意图；
图5为本申请实施例提供的一种TXOP机制的时序示意图；
图6a为本申请实施例提供的一种通信系统的结构示意图；
图6b为本申请实施例提供的另一种通信系统的结构示意图；
图7为本申请实施例提供的一种缓冲区报告发送、接收方法的流程示意图；
图8a为本申请实施例提供的一种缓冲区报告的结构示意图一；
图8b为本申请实施例提供的一种缓冲区报告的结构示意图二；
图9a为本申请实施例提供的一种缓冲区报告的结构示意图三；
图9b为本申请实施例提供的一种缓冲区报告的结构示意图四；
图10a为本申请实施例提供的一种缓冲区报告的结构示意图五；
图10b为本申请实施例提供的又一种缓冲区报告发送、接收方法的流程示意图；
图11为本申请实施例提供的一种通信方法的流程示意图；
图12为本申请实施例提供的另一种通信方法的流程示意图；
图13为本申请实施例提供的又一种通信方法的流程示意图；
图14为本申请实施例提供的一种第一通信装置的结构示意图；
图15为本申请实施例提供的一种第二通信装置的结构示意图；
图16为本申请实施例提供的一种第一通信装置的结构示意图。
具体实施方式
在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A，B可以是单数或者复数。
在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。
另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
可以理解，说明书通篇中提到的“实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各个实施例未必指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。可以理解，在本申请的各种实施例中，各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
可以理解，在本申请中，“当…时”以及“若”均指在某种客观情况下会做出相应的处理，并非是限定时间，且也不要求实现时要有判断的动作，也不意味着存在其它限定。
可以理解，本申请中的预定义可以理解为定义、预先定义、存储、预存储、预协商、预配置、固化、或预烧制。
可以理解，本申请实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，比如其当前所基于的方案，而独立实施，解决相应的技术问题，达到相应的效果，也可以在某些场景下，依据需求与其他特征进行结合。相应的，本申请实施例中给出的装置也可以相应的实现这些特征或功能，在此不予赘述。
本申请中，除特殊说明外，各个实施例之间相同或相似的部分可以互相参考。在本申请中各个实施例、以及各实施例中的各个实施方式/实施方法/实现方法中，如果没有特殊说明以及逻辑冲突，不同的实施例之间、以及各实施例中的各个实施方式/实施方法/实现方法之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例、以及各实施例中的各个实施方式/实施方法/实现方法中的技术特征根据其内在的逻辑关系可以组合形成新的实施例、实施方式、实施方法、或实现方法。以下所述的本申请实施方式并不构成对本申请保护范围的限定。
为了方便理解本申请实施例的技术方案，首先给出本申请相关技术的简要介绍如下。
1、多链路、多链路设备(multi-link device，MLD)：
为了达到极高吞吐率的技术目标，IEEE的下一代无线局域网(wireless local area network，WLAN)标准802.11be将极高吞吐率(extremely high throughput，EHT)作为技术目标，其中一个已有的关键技术即为多链路(multi-link，ML)通信。
多链路通信的核心思想是支持下一代IEEE 802.11标准的WLAN设备拥有在多个频段上发送和接收的能力，从而可以使用更大的带宽进行传输，进而提升吞吐率。其中，拥有在多个频段上同时发送和接收的能力的WLAN设备可以称为MLD。示例性的，上述多个频段包括但不限于：2.4GHz频段、5GHz频段、以及6GHz频段。
本申请中，MLD包括至少两个隶属的(affiliated)站点(station，STA)，即affiliated STA。其中，该隶属的站点可以为接入点站点(access point station，AP STA)或非接入点站点(non-access point station，non-AP STA)。
为描述方便，本申请下述实施例将AP STA简称为AP。隶属的站点为AP的多链路设备称为AP多链路设备(AP multi-link device，AP MLD)；隶属的站点为non-AP STA的多链路设备可以称为non-AP多链路设备(non-access point multi-link device，non-AP MLD)。
本申请中，MLD中的每一个隶属的站点可以建立一个链路进行通信，从而多个隶属的站点建立的链路便称为多链路。
通常，non-AP MLD和AP MLD之间可以通过交换多链路关联请求(multi-link  association request)帧和多链路关联响应(multi-link association response)帧，实现二者之间多条链路的关联(或建立)。具体的，non-AP MLD和AP MLD可以在一条链路上交换携带有多链路信息的关联请求帧和关联响应帧，简称为多链路关联请求帧和多链路关联响应帧。在该多链路关联请求帧和多链路关联响应帧中携带多链路信息，可以实现二者之间多条链路的同时关联。
其中，进行多链路关联请求帧和多链路关联响应帧交换的链路可以称为传输链路(Transmitted Link)，相应的，多条链路中的其他链路称为非传输链路(Non-transmitted Link)。
示例性的，如图1所示，以AP MLD包括隶属的AP1和AP2，non-AP MLD包括隶属的non-AP STA1和non-AP STA2，且隶属于同一MLD的站点(AP或non-AP STA)共享高媒体接入控制(medium access control，MAC)层，各自拥有独立的物理层(physical，PHY)和低MAC层为例，多链路建立的流程可以包括如下步骤：
Step1、non-AP MLD在链路1上向AP MLD发送多链路关联请求帧，其中携带链路1的non-AP STA侧(即non-AP STA1)信息，以及链路2的non-AP STA侧(即non-AP STA2)信息。其中，链路1为传输链路，链路2为非传输链路。
Step2、AP MLD在链路1上向non-AP MLD回复多链路关联响应帧，其中携带链路1的AP侧(即AP1)信息，以及链路2的AP侧(即AP2)信息。
上述流程中，为了在多链路关联请求帧或多链路关联响应帧中携带MLD的相关信息，协议定义了多链路元素(Multi-link element)，用于承载MLD的信息以及MLD中站点的信息。其中，多链路元素的帧结构可以如2所示。
需要说明的是，除特殊说明外，本申请中的站点指AP或non-AP STA，在此统一说明，下述实施例不再赘述。
参见图2，多链路元素包括元素标识(element identifier，element ID)字段、长度(Length)字段、元素标识扩展(Element ID Extension)字段、多链路控制字段(Multi-Link Control)、共同信息(Common Info)字段、以及链路信息(Link info)字段。
其中，元素标识字段和元素标识扩展字段用于标识多链路元素，不同多链路元素的元素标识字段和元素标识扩展字段不同，通常元素标识字段可以设置为255，元素标识扩展字段设置为未被其他多链路元素使用的值。长度字段用于指示多链路元素的长度。
多链路控制字段可以包括类型(Type)字段以及出现比特位图(Presence bitmap)字段。类型字段用于指示多链路元素的类型，如基本变体(Basic variant)多链路元素或探测请求变体(Probe Request variant)多链路元素。出现比特位图字段可以包括一个或多个出现(present)字段。具体的，出现比特位图字段可以包括：
多链路设备媒体访问控制地址(media access control，MAC)出现(MLD MAC Address Present)字段：用于指示共同信息字段中的MLD MAC地址字段是否出现。
链路标识信息出现(Link ID Info Present)字段：用于指示共同信息字段中的链路标识信息字段是否出现。其中，共同信息字段中的链路标识信息字段用于指示传输链路的信息。
基本服务集(basic service set，BSS)参数更改计数出现(BSS Parameters Change Count Present)字段：用于指示共同信息字段中的BSS参数更改计数字段是否出现。
媒体同步时延信息出现(Medium Synchronization Delay Information Present)字段： 用于指示共同信息字段中的媒体同步时延信息字段是否出现。
增强多链路(enhanced multi-link，EML)能力出现(EML Capabilities Present)字段：用于指示共同信息字段中的EML能力字段是否出现。
多链路设备能力出现(MLD Capabilities Present)字段：用于指示共同信息字段中的多链路设备能力字段是否出现。
对于上述涉及的Present字段，通常Present字段设置为1表示其指示的字段出现，Present字段设置为0表示其指示的字段不出现。
需要说明的是，本申请涉及的“出现(Present)字段”也可以称为“展示字段”或“存在字段”，可以相互替换，本申请对此不作具体限定。
在共同信息字段中，除包括Present字段指示出现的字段外，还可以包括待定(to be determined，TBD)字段。
链路信息字段用于承载非传输链路的相关信息，可以包括每站点轮廓(Per-STA Profile)子元素，每站点轮廓子元素可以与多链路设备的非传输链路上的站点一一对应。
每站点轮廓子元素可以包括子元素标识(Subelement ID)字段、长度(Length)字段、以及数据(data)字段。Data字段可以包括站点控制(STA Control)字段、站点信息(STA Info)字段、以及站点轮廓(STA Profile)字段。该站点轮廓字段可以包括零个或者多个元素(Element)。
以上对多链路元素的帧结构以及部分字段的功能进行了介绍，其余字段的介绍可参见IEEE 802.11be标准中的定义，在此不予赘述。
2、隧道直连链路建立(tunneled direct-link setup，TDLS)：
对于关联在同一个BSS下的两个non-AP STA，若这两个non-AP STA处于无线通信可达范围内，可以在彼此之间建立直连链路，使得二者之间的数据可以通过该直连链路进行传输，无需通过AP的转发，从而提高传输速率，降低传输时延。
可以理解的，建立直连链路的non-AP STA可以是隶属于non-AP MLD的non-AP STA，或者可以为独立的non-AP STA，即不隶属于任何non-AP MLD。为了方便描述，本申请将不隶属于任何non-AP MLD的non-AP STA称为legacy STA。
通常，关联在同一个BSS下的两个non-AP STA可以通过TDLS协议或其他P2P协议建立直连链路。
本申请中，P2P也可以称为设备到设备(device to device，D2D)。直连链路也可以称为P2P链路或D2D链路或TDLS链路，可以相互替换，本申请对此不做具体限定。
TDLS协议中主要包括下述与直连链路相关的操作：
TDLS发现(TDLS Discovery)：通过TDLS发起端和TDLS响应端交换TDLS发现请求(TDLS Discovery Request)帧和TDLS发现响应(TDLS Discovery Response)帧完成。
TDLS建立(TDLS Setup)：通过TDLS发起端和TDLS响应端交换TDLS建立请求(TDLS Setup Request)帧、TDLS建立响应(TDLS Setup Response)帧、以及TDLS建立确认(TDLS Setup Confirm)帧完成。通过这三个帧的交互，TDLS发起端和TDLS响应端可以完成TDLS对等秘钥(TDLS Peer Key，TPK)的派生。
TDLS拆除(TDLS Teardown)：通过TDLS拆除(TDLS Teardown)帧完成。
TDLS节能(TDLS Power save)：主要通过TDLS对等节能管理(power save management，PSM)请求(TDLS Peer PSM Request)帧、TDLS对端PSM响应(TDLS Peer PSM Response)帧、DLS对端流量指示(TDLS Peer Traffic Indication)帧、以及TDLS对端流量响应(TDLS Peer Traffic Response)帧来完成。
TDLS信道切换(TDLS channel switch)：通过TDLS信道切换请求(TDLS Channel Switch Request)帧、TDLS信道切换响应(TDLS Channel Switch Response)帧完成。
如下表1所示，示出了上述TDLS协议中的各个帧的传输方式是通过AP传输(Via AP)还是通过直连链路直接传输(Direct)、以及各个帧的帧类型。
表1
帧 Via AP or Direct 帧类型
TDLS发现请求帧 Via AP 数据帧
TDLS发现响应帧 Direct 公共行动帧(属于管理帧)
TDLS建立请求帧 Via AP 数据帧
TDLS建立响应帧 Via AP 数据帧
TDLS建立确认帧 Via AP 数据帧
TDLS拆除帧 Both allowed 数据帧
TDLS信道切换请求帧 Direct 数据帧
TDLS信道切换响应帧 Direct 数据帧
TDLS对端节能管理请求 Direct 数据帧
TDLS对端节能管理响应 Direct 数据帧
TDLS对端流量指示帧 Via AP 数据帧
TDLS对端流量响应帧 Direct 数据帧
由上表1可得，TDLS相关的帧通过AP转发或通过直连链路发送时，会封装成数据帧进行发送，从而TDLS的上述相关操作对AP来说是完全透明的，即AP不感知TDLS的上述相关操作。值得注意的是，TDLS发现响应帧为公共行动帧，其直接以管理帧的形式发送。
3、BSS转移：
如图3所示，为BSS转移管理操作流程。其中，对于关联在BSS下的non-AP STA，由于链路质量差或其他原因，non-AP STA可以向该BSS下的AP发送BSS转移管理(BSS transition management，BTM)询问(BTM Query)帧，相应的，AP可以向non-AP STA回复该BTM询问帧的确认(acknowledgement，Ack)帧。
当AP想让non-AP STA进行BSS转移时，可以向non-AP STA发送BTM请求(BTM request)帧。相应的，non-AP STA向AP回复该BTM请求帧的确认帧后，可以向AP发送BTM响应(BTM response)帧以指示接受或拒绝BSS转移请求。相应的，AP可以回复该BTM响应帧的确认帧。
如图4a所示，为BTM询问帧的帧结构，包括：类别(Category)字段、无线网络管理(wireless network management，WNM)行动(WNM Action)字段、对话令牌(Dialog Token)字段、BSS转移询问原因(BSS Transition Query Reason)字段、BSS转移备选列表(BSS Transition Candidate List)字段。其中：
BSS转移询问原因字段：携带non-AP STA发送BTM询问帧的原因。
BSS转移备选列表字段：为可选字段，携带一个或多个邻居报告元素(Neighbor Report element)，该邻居报告元素用于指示non-AP STA确定的候选BSS。
如图4b所示，为BTM请求帧的帧结构，包括：类别(Category)字段、无线网络管理(wireless network management，WNM)行动(WNM Action)字段、对话令牌(Dialog Token)字段、请求模式(Request Mode)字段、去关联定时器(Disassociation Timer)字段、有效时间(Validity Interval)字段、BSS终止持续时间(BSS Termination Duration)字段、会话信息统一资源定位符(uniform resource locator，URL)(Session Info URL)字段、BSS转移备选列表(BSS Transition Candidate List)字段。其中：
请求模式字段：用于指示具体的请求模式，具体的，可以包括：
1)、包括首选备选列表(Preferred Candidate List Included)字段：指示是否携带喜欢的备选列表，即BTM请求帧是否包括BSS转移备选列表字段。
2)、桥接(Abridged)字段：如果AP不推荐或者禁止non-AP STA切换到未出现在BSS转移备选列表中的BSS，将Abridged指示位设置为0；如果AP将未出现在BSS转移备选列表中的BSS的喜好值(perferece value)设置为0，将Abridged指示位设置为1。
3)、去关联即将发生(Disassociation Imminent)：当该字段置1时，表示AP会发送去关联(Disassociation)帧去关联该non-AP STA；当该字段置0时，表示AP不会发送Disassociation帧去关联该non-AP STA。
4)、包括BSS终止(BSS Termination Included)：指示该BSS是否会关闭。
5)、扩展服务集(extend service set，ESS)去关联即将发生(ESS Disassociation Imminent)：指示该non-AP STA是否会被整个ESS去关联。
去关联定时器字段：用于指示AP在多久后发送去关联帧。
有效时间字段：用于指示BSS转移备选列表在多少个信标(Beacon)周期内有效。
如图4c所示，为BTM响应帧的帧结构，包括：类别(Category)字段、无线网络管理(wireless network management，WNM)行动(WNM Action)字段、对话令牌(Dialog Token)字段、BSS状态码(BTM Status Code)字段、BSS终止时延(BSS Termination Delay)字段、目标BSS标识(Target BSSID)字段。其中：
BSS状态码字段：用于指示non-AP STA是否接受BTM请求。
BSS终止时延字段：用于指示延迟BSS终止的时间。
目标BSS标识字段：用于指示BSS转移的目标BSSID。对于non-AP MLD而言，如果其想转移到AP MLD，则该字段设置为AP MLD的MLD MAC地址(Address)。
以上对BTM询问帧、BTM请求帧、以及BTM响应帧的帧结构以及部分字段的功能进行了介绍，其余字段的介绍可参见IEEE 802.11相关标准中的定义，在此不予赘述。
4、AP协作集：
在AP协作场景中，多个AP可以组成一个AP协作集。AP协作集中包括至少一个分享AP(即Sharing AP)和至少一个被分享的AP(即Shared AP)。
在AP协作过程中，Sharing AP可以为Shared AP分配一段时间用于Shared AP进行数据传输。
如背景技术所述，作为TXOP holder的AP可以为non-AP STA分配TXOP内的部分时间，用于该non-AP STA发送数据。示例性的，如图5所示，假设AP在发送给自己的清除发送(clear to send，CTS)帧(CTS-to-self)之后获得TXOP。然后，AP可以发送多用户(multi user，MU)请求发送(request to send，RTS)传输机会共享(TXOP sharing，TXS)触发帧(trigger frame，TF)，该MU-RTS TXS TF可以指示一段时长，并指示一个non-AP STA，表示该段时长是给该non-AP STA分配的，此外还可以指示传输模式，该传输模式用于指示该段时长用于该non-AP STA的P2P传输还是上行传输。
图5中以AP向non-AP STA1分配一段时长A，用于non-AP STA1的P2P传输为例进行说明。non-AP STA1收到该MU-RTS TXS TF后可以发送CTS，之后向non-AP STA2发送单用户(Single user，SU)物理层协议数据单元(physical protocol data unit，PPDU)，即SU PPDU，non-AP STA2可以回复该SU PPDU的块确认(block acknowledge，BA)。在AP为non-AP STA分配的时间结束后，AP可以继续在该TXOP内发送PPDU。
可选的，在AP发送MU-RTS TXS TF之前，non-AP STA1可以向AP发送其所需要的传输时长。
在涉及到多链路设备的场景中，上述TXOP共享机制可能存在一些问题。基于此，本申请提供一种缓冲区报告发送、接收方法，其可以适用于包括多链路设备的场景，用于解决该场景下TXOP共享机制的相关问题。
下面将结合附图对本申请提供的缓冲区报告发送、接收方法进行详细说明。本申请提供的方法可以适用于Wi-Fi场景或WLAN场景，例如可以适用于IEEE 802.11系统标准，例如802.11a/b/g标准、802.11n标准、802.11ac标准、802.11ax标准，或其下一代(例如802.11be标准)或更下一代的标准中。或者，本申请实施例可以适用于物联网(internet of things，IoT)或车联网(vehicle to X，V2X)等无线局域网系统中。当然， 本申请实施例还可以适用于其他可能的通信系统，例如，长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、全球互联微波接入(worldwide interoperability for microwave access，WiMAX)通信系统、以及第五代(5th generation，5G)通信系统等。
其中，上述适用本申请的通信系统仅是举例说明，适用本申请的通信系统不限于此，在此统一说明，以下不再赘述。
参见图6a，为本申请提供一种本申请实施例适用的WLAN通信系统，该WLAN通信系统包括AP MLD 601和non-AP MLD 602。
其中，AP MLD 601包括多个隶属AP，图6a中以该多个隶属AP包括AP1、AP2、和AP3为例进行说明。non-AP MLD 602包括多个隶属non-AP STA，图6a中以该多个隶属non-AP STA包括non-AP STA1、non-AP STA2、和non-AP STA3为例进行说明。
AP MLD 601和non-AP MLD 602之间建立有多条上下行链路，图6a中以该多条上下行链路包括AP1和non-AP STA1之间的上下行链路1、AP2和non-AP STA2之间的上下行链路2、AP3和non-AP STA3之间的上下行链路3为例进行说明。
此外，该WLAN通信系统还可以包括至少一个目标non-AP STA，每个目标non-AP STA与non-AP MLD 602中的某个隶属non-AP STA之间建立有直连链路。一条直连链路两端的目标non-AP STA与non-AP MLD 602中的该隶属non-AP STA属于同一BSS，或者说，关联AP MLD 601中的同一AP。同一BSS中的直连链路的链路标识和上下行链路的链路标识相同。
可选的，该目标non-AP STA可以是legacy STA，例如图6a所示的目标non-AP STA 603。该目标non-AP STA 603与non-AP MLD 602的隶属non-AP STA1之间建立有直连链路1，与AP MLD 601的AP1之间建立有上下行链路A，目标non-AP STA 603与non-AP MLD 602的隶属non-AP STA1同属于AP MLD 601的AP1对应的BSS。其中，直连链路1的链路标识和上下行链路1的链路标识相同。
或者，该目标non-AP STA可以是某个non-AP MLD的隶属non-AP STA，例如图6a所示的目标non-AP STA 604，其为non-AP MLD A的隶属non-AP STA。该目标non-AP STA 604与non-AP MLD 602的隶属non-AP STA3之间建立有直连链路2，与APMLD 601的AP3之间建立有上下行链路B，目标non-AP STA 604与non-AP MLD 602的隶属non-AP STA3属于AP MLD 601的AP3对应的BSS。其中，直连链路2的链路标识和上下行链路3的链路标识相同。
参见图6b，为本申请提供另一种本申请实施例适用的WLAN通信系统，该WLAN通信系统包括分享的AP MLD(Sharing AP MLD)6011和被分享的AP MLD(Shared AP MLD)6012。
其中，分享的AP MLD 6011包括多个隶属AP，图6b中以该多个隶属AP包括AP A、AP B、和AP C为例进行说明。被分享的AP MLD 6012包括多个隶属AP，图6b中以该多个隶属AP包括AP a、AP b、和AP c为例进行说明。
分享的AP MLD 6011和被分享的AP MLD 6012之间建立有多条链路，图6b中以该多条链路包括AP A和AP a之间的链路1、AP B和AP b之间的链路2、AP C和AP c之间的链路3为例进行说明。
此外，该WLAN通信系统还可以包括至少一个目标non-AP STA，每个目标non-AP STA与被分享的AP MLD 6012中的某个AP之间建立有上下行链路。一条上下行链路两端的目标non-AP STA与被分享的AP MLD 6012中的该AP属于同一BSS，或者说，关联分享的AP MLD 6011中的同一AP。同一BSS中的上下行链路的链路标识和sharing AP与shared AP之间的链路的标识相同。
可选的，该目标non-AP STA可以是legacy STA，例如图6b所示的目标non-AP STA 6013。该目标non-AP STA 6013与被分享的AP MLD 6012的AP a之间建立有上下行链路X，与分享的AP MLD 6011的AP A之间建立有上下行链路A，目标non-AP STA 6013与被分享的AP MLD 6012的AP a属于分享的AP MLD 6011的AP A对应的BSS。其中，上下行链路X的链路标识和链路1的链路标识相同。
或者，该目标non-AP STA可以是某个non-AP MLD的隶属non-AP STA，例如图6a所示的目标non-AP STA 6014，其为non-AP MLD A的隶属non-AP STA。该目标non-AP STA 6014与被分享的AP MLD 6012的AP c之间建立有上下行链路Y，与分享的AP MLD 6011的AP C之间建立有上下行链路B，目标non-AP STA 6014与被分享的AP MLD 6012的AP c属于分享的AP MLD 6011的AP C对应的BSS。其中，上下行链路Y的链路标识和链路3的链路标识相同。
本申请涉及的non-AP MLD可以为无线通讯芯片、无线传感器或无线通信终端。例如支持Wi-Fi通讯功能的用户终端、用户装置，接入装置，订户站，订户单元，移动站，用户代理，用户装备。其中，用户终端可以包括各种具有无线通信功能的手持设备、车载设备、可穿戴设备、物联网(internet of things，IoT)设备、计算设备或连接到无线调制解调器的其它处理设备，以及各种形式的用户设备(user equipment，UE)，移动台(mobile station，MS)，终端(terminal)，终端设备(terminal equipment)，便携式通信设备，手持机，便携式计算设备，娱乐设备，游戏设备或系统，全球定位系统设备或被配置为经由无线介质进行网络通信的任何其他合适的设备等。此外，non-AP MLD可以支持802.11be制式或者802.11be的下一代WLAN制式。non-AP MLD也可以支持802.11ax、802.11ac、802.11n、802.11g、802.11b及802.11a等多种WLAN制式。
本申请实施例涉及的AP MLD可以为一种部署在无线通信网络中为其关联的non-AP STA提供无线通信功能的装置，主要部署于家庭、大楼内部以及园区内部，典型覆盖半径为几十米至上百米，当然，也可以部署于户外。AP MLD相当于一个连接有线网和无线网的桥梁，主要作用是将各个无线网络客户端连接到一起，然后将无线网络接入以太网。具体的，AP MLD可以是带有Wi-Fi芯片的基站、路由器、网关、中继器，通信服务器，交换机或网桥等通信设备，其中，所述基站可以包括各种形式的宏基站，微基站，中继站等。此外，AP MLD可以支持802.11be制式或者802.11be的下一代WLAN制式。AP MLD也可以支持802.11ax、802.11ac、802.11n、802.11g、802.11b及802.11a等WLAN制式。
在上述图6a所示的系统中，由于直连链路的建立对于AP MLD是透明的，即AP MLD无法获知哪个隶属AP对应的BSS中建立有直连链路，从而AP MLD本身可能无法获知在TXOP内为哪个直连链路分配传输时长，进而可能导致直连链路上的传输时延增大。
基于此，本申请提供一种缓冲区报告发送、接收方法，使得AP MLD中与直连链路所对应的AP可以确定在其获得的某个TXOP内为non-AP MLD的某个隶属non-AP  STA分配一段时间，用于直连链路上的传输，从而使得直连链路上的数据能够及时发送，降低直连链路上的传输时延。
下面将结合说明书附图，以图6a所示的AP MLD 601与non-AP STA 602之间的交互为例，对本申请实施例提供的缓冲区报告发送、接收方法进行展开说明。
可以理解的，本申请实施例中，执行主体可以执行本申请实施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。
请参见图7，为本申请实施例提供的缓冲区报告发送、接收方法的流程示意图，该方法包括如下步骤：
S701、non-AP MLD生成缓冲区报告(buffer report)。
其中，该缓冲区报告用于请求该non-AP MLD中的第一隶属non-AP STA在第一直连链路上进行直连传输的时长。第一直连链路为第一目标non-AP STA和该non-AP MLD的第一隶属non-AP STA之间的链路。第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一BSS。
可以理解的，non-AP MLD中可以有多个隶属non-AP STA与多个目标non-AP STA之间建立有多条直连链路，本申请以non-AP MLD中的第一隶属non-AP STA与第一目标non-AP STA之间建立有第一直连链路为例进行说明，non-AP MLD中的其他隶属non-AP STA与其他目标non-AP STA之间建立的直连链路的特征以及相关实现可参考本申请提供的第一直连链路及其相关的说明。
示例性的，如图6a所示，该non-AP MLD的第一隶属non-AP STA可以为non-AP MLD 602中的non-AP STA3，相应的，第一目标non-AP STA为目标non-AP STA 604，第一直连链路为直连链路2。
或者，该non-AP MLD的第一隶属non-AP STA可以为non-AP MLD 602中的non-AP STA1，相应的，第一目标non-AP STA为目标non-AP STA 603，第一直连链路为直连链路1。
对于该缓冲区报告包括的信息，可能存在如下两种情况：
情况一、该缓冲区报告包括链路信息和传输时长信息。
其中，传输时长信息用于指示第一传输时长，该第一传输时长为non-AP MLD中的第一隶属non-AP STA在第一直连链路上进行直连传输的时长。
可选的，该第一传输时长可以为归一化时间长度。归一化时间长度可以指通过参考带宽(例如80MHz)、参考速率等确定的时长。
作为一种可能的实现，该传输时长信息可以包括第一缓冲区的大小。该第一缓冲区用于缓存non-AP MLD中的第一隶属non-AP STA待在第一直连链路上发送的数据，或者说，该第一缓冲区用于缓存non-AP MLD中的第一隶属non-AP STA待向第一目标non-AP STA发送的数据。
可以理解的，在non-AP MLD中的第一隶属non-AP STA与多个目标non-AP STA之间建立有多条直连链路的情况下，该缓冲区报告可以不指示直连链路上除第一隶属non-AP STA外的另一端是哪个目标non-AP STA，即缓冲区报告不指示目标non-AP STA，而是通过链路信息指示直连链路。
示例性的，在传输时长信息包括第一缓冲区的大小的情况下，可以根据该第一缓冲 区的大小确定出第一传输时长。例如，可以根据第一缓冲区的大小、参考带宽、参考速率等计算第一传输时长。
作为另一种可能的实现，该传输时长信息可以包括第一传输时长。示例性的，该第一传输时长可以是根据第一缓冲区的大小、参考带宽、参考速率等确定的。
也就是说，在传输时长信息包括第一缓冲区的大小时，该传输时长信息隐式指示第一传输时长。在传输时长信息包括第一传输时长时，该传输时长信息显式指示第一传输时长。
其中，该链路信息用于指示第一直连链路。
作为一种可能的实现，该链路信息可以为第一直连链路的标识。若第一直连链路为图6a所示的直连链路1，则第一直连链路的标识为该直连链路1的标识。由于直连链路1的标识与上下行链路1的标识相同，从而该直连链路1的标识也是上下行链路1的标识。
作为一种具体的示例，在链路标识信息包括第一直连链路的标识时，以传输时长信息包括第一缓冲区的大小为例，该缓冲区报告的结构可以如图8a所示。其中，链路标识(link ID)字段用于携带直连链路的标识，缓冲区大小字段用于携带缓冲区的大小。
可选的，在链路标识信息包括第一直连链路的标识时，该缓冲区报告还可以包括类型(Type)信息和/或直连链路数量(Numbers of direct link)信息。该类型信息用于指示non-AP MLD与AP MLD之间建立有一条或多条上下行链路。直连链路数量信息用于指示有数据待传输的直连链路的数量N，例如图6a所示的系统，存在两条直连链路，若直连链路1上有数据待传输，直连链路2上没有数据待传输，则直连链路数量为1；若直连链路1和直连链路2上均有数据待传输，则直连链路数量为2。
示例性的，缓冲区报告还包括类型(Type)信息和/或直连链路数量(Numbers of direct link)信息时，该缓冲区报告的结构可以如图8b所示。其中，类型字段用于携带类型信息，示例性的，当类型字段设置为1时，可以指示non-AP MLD与AP MLD之间建立有多条上下行链路；当类型字段设置为0时，可以指示non-AP MLD与AP MLD之间建立有一条上下行链路。直连链路数量字段用于携带直连链路数量信息。
示例性的，在N大于1时，即在多个直连链路上有数据待传输时，可以将链路标识字段和缓冲区大小字段重复N次，该N个链路标识字段分别携带N个链路标识信息，N个缓冲区大小字段分别携带N个缓冲区的大小。
作为另一可能的实现，该链路信息可以为比特位图。该比特位图的大小为non-AP MLD与AP MLD之间建立的上下行链路的总数。例如图6a所示的系统下，该比特位图的大小为3。
可选的，该比特位图中的每个比特分别对应non-AP MLD与AP MLD之间建立的一条上下行链路。当标识与某条上下行链路的标识相同的直连链路上有数据待传输时，可以将该直连链路对应的比特设置为1，以指示直连链路为标识与该比特对应的上下行链路的标识相同的直连链路。
例如图6a所示的系统下，第一直连链路为直连链路1时，直连链路1的标识与上下行链路1的标识相同，假设比特位图中的比特从左到右依次对应上下行链路1、上下行链路2、以及上下行链路3，则该比特位图可以设置为100。其中，第一个比特设置为1指示直连链路为标识与该比特对应的上下行链路1的标识相同的直连链路1。
作为一种具体的示例，在链路标识信息包括比特位图时，以传输时长信息包括第一 缓冲区的大小为例，该缓冲区报告的结构可以如图9a所示。其中，比特位图字段用于携带比特位图，该字段的大小与比特位图的大小相同，缓冲区大小字段用于携带缓冲区的大小。
可选的，在链路标识信息包括比特位图时，该缓冲区报告还可以包括类型(Type)信息和/或比特位图大小(Bitmap size)。该类型信息的功能可参考上述相关说明。比特位图大小用于指示该比特位图的大小。
示例性的，缓冲区报告还包括类型(Type)信息和/或比特位图大小时，该缓冲区报告的结构可以如图9b所示。其中，类型字段的功能可参考上述相关说明，比特位图大小字段用于携带比特位图大小。
示例性的，在多个直连链路上有数据待传输时，可以将缓冲区大小字段重复N次，分别携带N个缓冲区的大小。此外，比特位图字段携带的比特位图指示该多条直连链路，例如，图6a所示的场景中，若直连链路1和直连链路2上均有数据待传输，则该比特位图可以设置为101。
上述图8a-图9b的结构中以传输时长信息包括缓冲区大小为例进行说明，在传输时长信息包括第一传输时长时，可以将图8a-图9b中的缓冲区大小字段替换为传输时长字段，用于携带传输时长。
情况二、该缓冲区报告包括传输时长信息，且不包括链路信息。
其中，传输时长信息、以及链路信息可参考上述情况一中的相关说明，在此不再赘述。
S702、non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告。相应的，AP MLD在第一上下行链路上接收来自non-AP MLD的缓冲区报告。
作为一种可能的实现，缓冲区报告如上述情况一所述，该第一上下行链路为non-AP MLD和AP MLD之间建立的多条上下行链路中的任意一条上下行链路。
需要说明的是，除特殊说明外，本申请中的上下行链路指使能的(enabled)上下行链路。
示例性的，如图6a所示的场景中，若上下行链路1、上下行链路2、以及上下行链路3均为使能的上下行链路，该第一上下行链路可以为上下行链路1、上下行链路2、或上下行链路3中的任意一条上下行链路。
作为另一种可能的实现，缓冲区报告如上述情况二所述，该第一上下行链路为non-AP MLD和AP MLD之间建立的多条上下行链路中标识与第一直连链路的标识相同的上下行链路，即第一上下行链路的标识和第一直连链路的标识相同。
示例性的，如图6a所示的场景中，若第一直连链路为直连链路1，则第一上下行链路为上下行链路1。
可以理解的是，在缓冲区报告如上述情况二所述时，若在多条直连链路上有数据待传输，则需要在每条直连链路对应的上下行链路上分别发送缓冲区报告。例如，图6a所示的场景中，若直连链路1和直连链路2上均有数据待发送，则non-AP MLD在上下行链路1上向AP MLD发送直连链路1对应的缓冲区报告，指示在该直连链路1上进行直连传输的时长，以及在上下行链路3上向AP MLD发送直连链路3对应的缓冲区报告，指示在该直连链路3上进行直连传输的时长。
可选的，对于缓冲区报告的内容以及发送方式：non-AP MLD可以先确定缓冲区报告的内容，再根据缓冲区报告的内容确定用于向AP MLD发送该缓冲区报告的上下行链 路。或者，non-AP MLD可以先确定用于向AP MLD发送缓冲区报告的上下行链路，再根据选择的上下行链路确定缓冲区报告的内容。本申请对此不作具体限定。
对于承载缓冲区报告的承载方式：
作为一种可能的实现，该缓冲区报告可以携带在管理帧中。换言之，non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告，可以包括：non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送管理帧，该管理帧包括缓冲区报告。
作为一种具体的示例，缓冲区报告可以携带在该管理帧帧头中的聚合控制(aggregated control，A-control)字段中，即管理帧包括A-control字段，该A-control字段包括缓冲区报告。
可选的，携带缓冲报区告的A-control字段可以是新定义的一类A-control，该类A-control可以携带有直连传输对应的缓冲区报告。即携带在该类A-control中的缓冲区报告包括直连传输对应的缓冲区报告。可以理解的，直连传输对应的缓冲区报告用于请求在直连链路上进行直连传输的时长。
作为另一种具体的示例，缓冲区报告可以携带在该管理帧的帧体中。
可选的，该管理帧可以是新定义的一类管理帧，该类管理帧可以携带直连传输对应的缓冲区报告。即携带在该类管理帧中的缓冲区报告包括直连传输对应的缓冲区报告。
可选的，该缓冲区报告携带在管理帧中的情况下，该管理帧的帧头还可以包括多链路设备信息，该多链路设备信息用于指示non-AP MLD。
作为另一种可能的实现，该缓冲区报告可以携带在数据帧帧头中的聚合控制A-control字段中。换言之，non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告，可以包括：non-AP MLD在多条上下行链路中的第一上下行链路上向AP MLD发送数据帧，该数据帧包括A-control字段，A-control字段包括缓冲区报告。
可选的，携带缓冲报区告的A-control字段可以是新定义的一类A-control，该类A-control可以携带直连传输对应的缓冲区报告。可参考上述相关说明，在此不再赘述。
作为又一种可能的实现，该缓冲区报告可以携带在数据帧的服务质量(quality of service，QoS)控制(control)(即QoS control)字段中。示例性的，该数据帧可以为QoS Null帧，即该缓冲区报告可以携带在QoS Null帧的QoS control字段中。
可选的，该缓冲区报告携带在数据帧中的情况下，该数据帧的帧头还可以包括多链路设备信息，该多链路设备信息用于指示non-AP MLD。
S703、AP MLD确定第二传输时长。
其中，AP MLD可以在步骤S703之前获取多个BSS内的TXOP，该多个BSS为AP MLD的多个隶属AP分别对应的BSS。在收到缓冲区报告后，AP MLD可以获知non-AP MLD的第一隶属non-AP STA在第一直连链路上待进行直连传输，从而AP MLD中与第一直连链路所对应的隶属AP可以确定在其获得的某个TXOP内为第一隶属non-AP STA分配一段时间，用于第一直连链路上的传输。
也就是说，该第二传输时长包括AP MLD为non-AP MLD中的第一隶属non-AP STA分配的用于在第一直连链路上进行直连传输的时长。该第二传输时长为AP MLD中与第一直连链路所对应的隶属AP所获得的某个TXOP内的一段时间。
示例性的，如图6a所示的场景中，第一直连链路为直连链路1时，AP MLD中与 第一直连链路所对应的隶属AP为AP1。
可选的，该第二传输时长与第一传输时长可以相同也可以不同。也就是说，AP MLD分配的时长不一定与non-AP MLD请求的时长相等。
S704、AP MLD发送第一时长指示信息。相应的，non-AP MLD接收来自AP MLD的第一时长指示信息。
其中，该第一时长指示信息用于指示第二传输时长。示例性的，该第一时长指示信息可以携带在触发帧中。
可选的，该携带该第一时长指示信息的触发帧可以为MU-RTS TXS TF。该情况下，该触发帧可以包括non-AP MLD的信息，来指示第二传输时长是分配给non-AP MLD的第一隶属non-AP STA的。
可选的，该触发帧还可以包括第一模式信息，该第一模式信息可以用于指示第二传输时长用于non-AP MLD的第一隶属non-AP STA的直连传输和上行传输。
可选的，non-AP MLD收到该触发帧后，当第一模式信息指示第二传输时长用于non-AP MLD的第一隶属non-AP STA的直连传输和上行传输时，则可以在第二传输时长内进行第一直连链路上的直连传输和上行传输。
基于该方案，non-AP MLD向AP MLD发送缓冲区报告，该缓冲区报告能够用于请求non-AP MLD中的第一隶属non-AP STA在第一直连链路上进行直连传输的时长，使得AP MLD在收到该缓冲区报告后，可以获知non-AP MLD的第一隶属non-AP STA在第一直连链路上待进行直连传输，从而AP MLD中与第一直连链路所对应的隶属AP可以确定在其获得的某个TXOP内为第一隶属non-AP STA分配一段时间，用于第一直连链路上的传输，从而使得直连链路上的数据能够及时发送，降低直连链路上的传输时延。
上述实施例中以non-AP MLD和AP MLD之间建立有多条上下行链路为例进行了说明，其可以进行适当变型以适用于non-AP MLD和AP MLD之间仅建立有一条上下行链路的场景，或者适用于legacy STA和AP MLD之间建立有一条上下行链路的场景。例如，该两种场景下，上述缓冲区报告中可以不携带链路信息，缓冲区报告的结构可以如图10a所示，其中，类型字段设置为0，指示non-AP MLD(或legacy STA)与AP MLD之间建立有一条上下行链路类型。
上述实施例以non-AP MLD请求在直连链路上进行直连传输的时长为例进行说明。此外，non-AP MLD还可以请求进行上行传输的时长。该情况下，non-AP MLD可以生成直连缓冲区报告用于请求进行直连传输的时长，以及上行缓冲区报告用于请求进行上行传输的时长或者汇报上行缓冲区大小。
可以理解的，在non-AP MLD既上报直连缓冲区报告又上报上行缓冲区报告的情况下，图7所示流程中涉及的缓冲区报告可以认为是直连缓冲区报告。
对于上行缓冲区报告，一种可能的实现方式中，上行缓冲区报告的相关实现类似于直连缓冲区报告，可参考上述说明，在此不再赘述。
另一种可能的实现方式中，上行缓冲区报告可以包括业务标识(traffic identifier，TID)信息和传输时长信息，用于请求某个TID对应的传输时长。由于TID与链路之间存在映射关系(TID-to-link mapping)，从而AP MLD根据该缓冲区报告能够确定在该TID对应的链路所对应的隶属AP获得的TXOP内分配一段时间用于上行传输。
又一种可能的实现方式中，上行缓冲区报告可以包括TID信息和队列大小(Queue  Size)信息，该队列大小信息用于指示TID信息指示的TID的队列大小。可选的，根据该TID的队列大小，可以确定该上行缓冲区报告请求的用于上行传输的时长。
可选的，上行缓冲区报告中，该业务标识信息可以包括TID或比特位图，该传输时长信息可以包括缓冲区大小或传输时长，可参考上述直连缓冲区报告中链路信息和传输时长的相关说明，在此不再赘述。
为了区分直连缓冲区报告和上行缓冲区报告，作为一种可能的实现，直连缓冲区报告和上行缓冲区报告在同一类A-control，或同一类管理帧中携带时，在图7所示流程中的特征的基础上，该缓冲区报告还可以包括缓冲区类型信息，该缓冲区类型信息用于指示该缓冲区类型信息所在的缓冲区报告是直连传输对应的缓冲区报告，还是上行缓冲区报告。
作为另一种可能的实现，可以使用不同类型的管理帧或不同类型的A-control分别携带直连缓冲区报告和上行缓冲区报告。
作为又一种可能的实现，直连缓冲区报告或上行缓冲区报告在QoS Null帧中的QoS control字段中携带时，在图7所示流程中的特征的基础上，缓冲区报告还可以包括资源请求类型(Resource Request Type)，该资源请求类型用于指示缓冲区报告用于上行资源请求，还是用于直连资源请求。
可选的，该资源请求类型也可以称为缓冲区类型。相应的，资源请求类型用于指示缓冲区报告用于上行资源请求，还是用于直连资源请求，可以理解为：该缓冲区类型用于指示缓冲区报告是上行缓冲区报告，还是直连缓冲区报告。
可选的，该可能的实现中，直连缓冲区报告还可以包括信道宽度信息，该信道宽度信息用于指示参考带宽。参考带宽的说明可参考上述步骤S701中的相关说明，在此不予赘述。
在缓冲区报告包括资源请求类型时，一种可能的实现方式中，可以使用QoS Null帧中的QoS control字段的Bit 7承载资源请求类型。在QoS control字段的Bit 7设置为第三数值时，可以指示缓冲区报告用于上行资源请求；在QoS control字段的Bit 7设置为第四数值时，可以指示缓冲区报告用于直连资源请求。
示例性的，该第三数值可以0，相应的，第四数值可以为1。或者，该第三数值可以1，相应的，第四数值可以为0。以第三数值为1，第四数值为1为例，QoS Null帧中的QoS control字段的各个比特的功能或设置可以如下表2所示：
表2
Figure PCTCN2022106968-appb-000001
其中，TID字段：用于承载TID信息，指示缓冲区报告所对应的TID。
确认策略指示(Ack Policy Indicator)字段：用于指示所采用的确认策略，可参考802.11be标准中的相关定义，在此不予赘述。
资源请求类型(Resource Request Type)字段：用于指示资源请求类型。
请求的TXOP时长(TXOP Duration Requested)字段：用于承载缓冲区报告中的传输时长信息，指示所请求的传输时长。示例性的，请求的TXOP时长字段设置为0时，表示不请求传输时长，或传输时长为0；请求的TXOP时长字段设置为非0时，请求的传输时长可以为该字段的取值乘以32微秒，从而，该字段对应的传输时长的范围可以为32微秒到8160微秒。
队列大小(Queue Size)字段：用于承载队列大小信息，指示TID的队列大小。
信道宽度(Channel Width)字段：用于承载信道宽度信息，指示参考带宽。示例性的，信道宽度字段的取值与参考带宽的对应关系可以如下表3所示。
表3
信道宽度字段取值 参考带宽
0 20MHz
1 40MHz
2 80MHz
3 160MHz
4 320MHz
5-15 预留(Reserved)
其中，资源请求类型设置为0时，表示缓冲区报告为上行缓冲区报告，资源请求类型字段设置为1时，表示缓冲区报告为直连缓冲区报告。从而，上述表2所示的设置可以表示上行缓冲区报告包括TID信息、资源请求类型、以及传输时长信息；或者，上行缓冲区报告包括TID信息、资源请求类型信息、以及队列大小信息。直连缓冲区报告可以包括信道宽度信息、资源请求类型、以及传输时长信息。
可选的，表2中Non-AP STA发送的QoS Null帧可以理解为Non-AP STA支持TXS时，向AP发送的QoS Null帧。此外，Non-AP STA可以为Non-AP EHT STA或支持未来演进的WLAN标准的Non-AP STA。
另一种可能的实现方式中，可以使用QoS Null帧中的QoS control字段的Bit 3承载资源请求类型。在QoS control字段的Bit 3设置为第三数值时，可以指示缓冲区报告用 于上行资源请求；在QoS control字段的Bit 3设置为第四数值时，可以指示缓冲区报告用于直连资源请求。
示例性的，以第三数值为1，第四数值为1为例，QoS Null帧中的QoS control字段的各个比特的功能或设置可以如下表4所示：
表4
Figure PCTCN2022106968-appb-000002
其中，表4中的说明可参考上述表2中的相关描述，在此不再赘述。需要说明的是，表2和表4中仅是示例性的以上行缓冲区报告包括TID信息、资源请求类型、以及传输时长信息为例进行说明，本申请并不限定上行缓冲区报告必须如表2或表4所示，例如，表2和表4中的TID字段也可以替换为链路信息字段用于承载链路信息。同样，也不限定直连缓冲区报告必须如表2或表4所示，例如，表2和表4中的信道宽度字段可以替换为替换为链路信息字段用于承载链路信息。
可选的，AP MLD收到上行缓冲区报告后，在TID-to-link mapping由AP MLD和non-AP MLD协商的情况下，该TID对应的链路所对应的隶属AP可以在其获得的TXOP内进行TXS，分配一段时间用于上行传输。在TID-to-link mapping默认的情况下，该AP MLD中与该non-AP MLD建立有链路的任意隶属AP可以在其获得的某个TXOP内进行TXS，分配一段时间用于上行链路上的传输。
上述实施例中给出了直连缓冲区报告和上行缓冲区报告独立存在的方案。此外，本申请还提供一种缓冲区报告发送、接收方法，该方法中可以用一个缓冲区报告请求直连链路的传输时长以及上行链路的传输时长。如图10b所示，该缓冲区报告发送、接收方法方法包括如下步骤：
S1001、non-AP MLD生成缓冲区报告。
其中，该缓冲区报告用于请求non-AP MLD中的第一隶属non-AP STA在第一链路上进行传输的时长。该第一链路包括第一直连链路和第一上下行链路。
其中，该第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路。该第一上下行链路为该AP MLD的第一隶属AP和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA、non-AP MLD的第一隶属non-AP STA、以及AP MLD的第一隶属AP属于同一BSS。
示例性的，如图6a所示的场景中，第一直连链路可以为直连链路1，第一上下行链路可以为上下行链路1。
对于该缓冲区报告包括的信息：
作为一种可能的实现方式，该缓冲区报告可以包括链路信息、传输时长信息、以及 第二模式信息。其中，第二模式信息用于指示传输时长信息指示的是上行传输时长，还是上行传输和直连传输的总时长。链路信息和传输时长信息可参考上述步骤S701中的相关说明，在此不再赘述。
可选的，该第二模式信息可以为1比特的指示信息，当该比特设置为0时，表示传输信息指示的是上行传输时长；当该比特设置为1时，表示传输信息指示的是上行传输和直连传输的总时长。
例如图6a所示的场景中，若non-AP MLD的隶属non-AP STA1在直连链路1上有待传输的数据，且在上下行链路1上有待传输的上行数据，则缓冲区报告中的第二模式信息可以设置为1，传输时长信息为上行缓冲区和直连缓冲区的大小之和，或者为上行传输时长和直连传输时长之和。若non-AP MLD的隶属non-AP STA3在直连链路2上没有待传输的直连数据，且在上下行链路3上有待传输的上行数据，则缓冲区报告中的第二模式信息可以设置为0，传输时长信息为上行缓冲区的大小或者为上行传输时长。
可以理解的，上行缓冲区用于缓存待传输的上行数据，直连缓冲区用于缓存待在直连链路上传输的数据。
作为另一种可能的实现方式，该缓冲区报告可以包括传输时长信息和第二模式信息。可参考上述上述步骤S701中情况二的相关说明，在此不再赘述。
S1002、non-AP MLD在该多条上下行链路中的第二上下行链路上向AP MLD发送缓冲区报告。
可选的，该第二上下行链路可以为多条上下行链路中的任意一条上下行链路，或者，该第二上下行链路与步骤S1001中的第一上下行链路相同，可参考上述步骤S702中的相关说明，在此不再赘述。
S1003、AP MLD确定第三传输时长。
其中，该第三传输时长包括AP MLD为non-AP MLD中的第一隶属non-AP STA分配的用于在第一链路上进行传输的时长，即包括了用于在第一直连链路上进行直连传输的时长以及在第一上下行链路上进行上行传输的时长。该第三传输时长中用于直连传输的时长可以为AP MLD中与第一链路所对应的隶属AP所获得的某个TXOP内的一段时间。在上行缓冲区报告包括TID时，在TID-to-link mapping由AP MLD和non-AP MLD协商的情况下，该第三传输时长中用于上行传输的时长可以为第一上下行链路对应的隶属AP所获得的某个TXOP内的一段时间；在TID-to-link mapping默认的情况下，该第三传输时长中用于上行传输的时长可以为AP MLD中与该non-AP MLD建立有链路的任意隶属AP所获得的某个TXOP内的一段时间。
S1004、AP MLD发送第二时长指示信息。相应的，non-AP MLD接收来自AP MLD的第二时长指示信息。
其中，该第二时长指示信息用于指示第三传输时长，可参考上述步骤S704中的相关说明，在此不再赘述。
基于该方案，non-AP MLD向AP MLD发送缓冲区报告，该缓冲区报告能够用于请求non-AP MLD中的第一隶属non-AP STA在第一直连链路和第一上下行链路上进行传输的总时长，使得AP MLD在收到该缓冲区报告后，可以获知non-AP MLD的第一隶属non-AP STA在第一直连链路和第一上下行链路上待进行传输，从而AP MLD中与第一直连链路和第一上下行链路上所对应的隶属AP可以确定在其获得的某个TXOP内为第一隶属non-AP STA分配一段时间，用于第一直连链路和第一上下行链路上的传输， 从而使得数据能够及时发送，降低传输时延。
此外，本申请上述实施例提供的方法还可以进行适当变型以适用于AP协作组的场景。例如，AP协作组中的Sharing AP MLD可以实现上述方法中AP MLD的功能，Shared AP MLD可以实现上述方法中non-AP MLD的功能。区别在于，Shared AP MLD生成并发送的缓冲区报告用于请求Share AP MLD中的第一隶属AP在第一上下行链路上进行传输的时长，该第一上下行链路为Share AP MLD中的第一隶属AP与目标non-AP STA之间的链路，例如图6b所示的上下行链路X。
可选的，除上述TXOP共享机制中的解决方案外，本申请还提供一些BSS转移场景中的相关解决方案。
由前述相关技术的简要介绍部分可知，源AP MLD可以向non-AP MLD发送BTM请求帧，以请求该non-AP MLD转移到目标AP MLD。该BTM请求帧的部分字段与链路相关，例如，去关联定时器字段和有效间隔字段以某条上下行链路的目标信标传输时间(target beacon transmission time，TBTT)为单位，如去关联定时器字段指示在多少个TBTT后发送去关联帧。
通常，该BTM请求帧可以通过源AP MLD和non-AP MLD之间的任意一条使能的上下行链路发送。然而，对于源AP MLD和non-AP MLD之间的不同上下行链路，其TBTT和定时同步功能(timing synchronization function，TSF)可以不同。因此，在任意一条使能的上下行链路上发送BTM请求帧时，non-AP MLD可能无法获知关联定时器字段和有效间隔字段以哪条上下行链路的TBTT为单位。
基于此，本申请提供如下两种方法，用于BSS转移场景，以源AP MLD和non-AP MLD之间建立有多条上下行链路为例，如图11所示，第一种方法可以包括如下步骤：
S1101、源AP MLD生成BTM请求帧。
其中，该BTM请求帧包括指示信息，该指示信息用于指示该BTM请求帧中的去关联定时器和/或有效时间以多条上下行链路中的某一条上下行链路的TBTT为单位。
可选的，该指示信息可以为多条上下行链路中的该某一条上下行链路的标识，或者，指示信息为多条上下行链路中的该某一条上下行链路的对应的基本服务集的标识(basic service set identifier，BSSID)。
示例性的，以源AP MLD和non-AP MLD之间建立有上下行链路A、上下行链路B、以及上下行链路C为例，若去关联定时器和/或有效时间以上下行链路C的TBTT为单位，该指示信息可以为上下行链路C的标识或该上下行链路C对应的BSSID。
S1102、源AP MLD在多条上下行链路中的任一条上下行链路上向non-AP MLD发送BTM请求帧。相应的，non-AP MLD在该任一条上下行链路上接收来自源AP MLD的BTM请求帧。
示例性的，基于步骤S1101中的示例，源AP MLD可以在上下行链路A、上下行链路B、或上下行链路C中的任一条上下行链路上向non-AP MLD发送该BTM请求帧。
基于该方案，源AP MLD在BTM请求帧中添加指示信息，以指示BTM请求帧中的去关联定时器和/或有效时间以多条上下行链路中的某一条上下行链路的TBTT为单位，从而使得non-AP MLD可以准确获取去关联帧的发送时间，或BSS转移备选列表的有效时间，进而提高BSS转移的效率。
如图12所示，第二种方法可以包括如下步骤：
S1201、源AP MLD生成BTM请求帧。
其中，该BTM请求帧不额外添加上述指示信息，例如，该BTM请求帧的帧结构可以如图4b所示。
S1202、源AP MLD在多条上下行链路中的第一上下行链路上向non-AP MLD发送BTM请求帧。相应的，non-AP MLD在该第一上下行链路上接收来自源AP MLD的BTM请求帧。
其中，该BTM请求帧中的去关联定时器和/或有效间隔以该多条上下行链路中的该第一上下行链路的TBTT为单位。也就是说，BTM请求帧中的去关联定时器和/或有效间隔以传输该BTM请求帧的上下行链路的TBTT为单位。
示例性的，以源AP MLD和non-AP MLD之间建立有上下行链路A、上下行链路B、以及上下行链路C为例，若去关联定时器和/或有效时间以上下行链路C的TBTT为单位，则源AP MLD在上下行链路C上向non-AP MLD发送该BTM请求帧。
基于该方案，BTM请求帧中的去关联定时器和/或有效间隔以传输该BTM请求帧的上下行链路的TBTT为单位，使得non-AP MLD可以根据收到该BTM请求帧的上下行链路准确获取去关联帧的发送时间，或BSS转移备选列表的有效时间，进而提高BSS转移的效率。
此外，本申请还提供一种方法对BTM请求帧中携带邻居报告元素中携带的内容以及字段设置进行说明。如图13所示，该方法包括：
S1301、源AP MLD生成BTM请求帧。
其中，该BTM请求帧包括一个或多个邻区报告元素，该邻区报告元素用于指示源AP MLD向non-AP MLD推荐的候选AP。
当该候选AP属于候选AP MLD时，或者说，该候选AP为候选AP MLD的隶属AP时，该邻居报告元素中可以包括基本变体多链路元素，作为子元素(subelement)。该基本变体多链路元素包括多链路控制字段和共同信息字段，且不包括链路信息字段。其中，多链路控制字段、共同信息字段、以及链路信息字段的结构可以参考图2的相关说明，在此不再赘述。
S1302、源AP MLD向non-AP MLD发送BTM请求帧。相应的，non-AP MLD接收来自源AP MLD的BTM请求帧。
可选的，源AP MLD可以在任一条上下行链路上向non-AP MLD发送该BTM请求帧。
基于该方案，由于在BSS转移过程中无需获取链路信息，从而在基本变体多链路元素中不携带链路信息字段可以节省信令开销，同时不影响BSS转移流程执行。
可选的，在上述步骤S1301中，该多链路控制字段中的MLD MAC地址出现字段可以设置为第一数值；该多链路控制字段中的第一出现字段可以设置为第二数值，该第一出现字段可以包括链路标识信息出现字段和BSS参数更改计数出现字段。
其中，第一数值用于指示字段在共同信息字段中出现，第二数值用于指示字段在共同信息字段中不出现。例如，MLD MAC地址出现字段设置为第一数值，表示MLD MAC地址字段在共同信息字段中出现，链路标识信息出现字段设置为第二数值，表示链路标识信息字段在共同信息字段中不出现。
示例性的，该第一数值可以1，相应的，第二数值可以为0。或者，该第一数值可以0，相应的，第二数值可以为1。
可选的，在BTM请求帧包括多个邻居报告元素，且该多个邻居报告元素指示的候 选AP属于同一候选AP MLD的情况下：
第一基本变体多链路元素包括的多链路控制字段中的第二出现字段设置为第一数值，第二基本变体多链路元素包括的多链路控制字段中的第二出现字段设置为第二数值。其中，第一基本变体多链路元素为多个邻居报告元素中的第一个邻居报告元素包括的基本变体多链路元素，第二基本变体多链路元素为多个邻区报告元素中除第一个邻居报告元素外的邻居报告元素包括的基本变体多链路元素。
示例性的，以BTM请求帧包括三个邻居报告元素，该三个邻居报告元素分别指示候选AP1、候选AP2、候选AP3，且候选AP1、候选AP2、以及候选AP3属于同一候选AP MLD为例，则第一个邻居报告元素可以为指示候选AP1的邻居报告元素，第一基本变体多链路元素为该指示候选AP1的邻居报告元素中的基本变体多链路元素。第二基本变体多链路元素包括指示候选AP2的邻居报告元素中的基本变体多链路元素和指示候选AP3的邻居报告元素中的基本变体多链路元素。
可选的，该第二出现字段可以包括以下一项或多项：媒体同步时延信息出现字段、EML能力出现字段、或MLD出现字段。
基于该方案，对于同一BTM请求帧指示的多个候选AP属于同一AP MLD的情况，可以指示该AP MLD的隶属AP为候选AP的第一个邻居报告元素中携带基本变体多链路元素，且将该基本变体多链路元素包括的多链路控制字段中的第二出现字段设置为第一数值，将指示该AP MLD的隶属AP为候选AP的其他邻居报告元素中的基本变体多链路元素所包括的多链路控制字段中的第二出现字段设置为第二数值，使得第二出现字段指示的字段(媒体同步时延信息出现字段、EML能力出现字段、或MLD出现字段中的一项或多项)在BTM请求中携带一次，避免重复携带相同的字段，从而减少信令开销。
以上介绍了本申请实施例的方法，以下介绍本申请实施例的通信装置，本申请实施例的通信装置包括第一通信装置、第二通信装置、以及第三通信装置，应理解，所述第一通信装置为上述方法中的non-AP MLD，其具有上述方法中non-AP MLD的任意功能，所述第二通信装置为上述方法中的AP MLD，其具有上述方法中AP MLD的任意功能，所述第三通信装置为上述方法中的源AP MLD，其具有上述方法中源AP MLD的任意功能。
如图14所示，第一通信装置包括：处理模块和收发模块。
该处理模块，用于生成缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该收发模块，用于在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告。
可选的，第一通信装置的处理模块和收发模块，与non-AP MLD可能存在如下几种关系：
1)、该处理模块和收发模块为non-AP MLD的第一隶属non-AP STA的处理模块和收发模块。
2)、该处理模块和收发模块为non-AP MLD的集中处理模块和集中收发模块。
3)、该处理模块为non-AP MLD的第一隶属non-AP STA的处理模块，该收发模块为non-AP MLD的集中收发模块。
4)、该处理模块为non-AP MLD的集中处理模块，该收发模块为non-AP MLD的第一隶属non-AP STA的收发模块。
应理解，本申请实施例提供的第一通信装置即为上述方法中的non-AP MLD，其具有上述图7所示方法中non-AP MLD的任意功能，具体细节可参见上述方法，此处不再赘述。
如图15所示，第二通信装置包括：处理模块和收发模块。
该收发模块，用于在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该处理模块，用于确定第二传输时长，第二传输时长包括AP MLD为non-AP MLD中的第一隶属non-AP STA分配的用于在第一直连链路上进行直连传输的时长；
该收发模块，还用于发送第一时长指示信息，该第一时长指示信息用于指示该第二传输时长。
可选的，第二通信装置的处理模块和收发模块，与AP MLD可能存在如下几种关系：
1)、该处理模块和收发模块为AP MLD中与第一直连链路所对应的隶属AP的处理模块和收发模块。
2)、该处理模块和收发模块为AP MLD的集中处理模块和集中收发模块。
3)、该处理模块为AP MLD中第一直连链路所对应的隶属AP的处理模块，该收发模块为AP MLD的集中收发模块。
4)、该处理模块为AP MLD的集中处理模块，该收发模块为AP MLD中与第一直连链路所对应的隶属AP的收发模块。
应理解，本申请实施例提供的第二通信装置即为上述方法中的AP MLD，其具有上述图7所示方法中AP MLD的任意功能，具体细节可参见上述方法，此处不再赘述。
如图16所示，第三通信装置包括：处理模块和收发模块。
该处理模块，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括指示信息，指示信息用于指示BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的某一条上下行链路的目标信标传输时间TBTT为单位；该收发模块，用于在多条上下行链路中的任一条上下行链路上向non-AP MLD发送BTM请求帧。
或者，
该处理模块，用于生成基本服务集转移管理BTM请求帧；该收发模块，用于在多条上下行链路中的第一上下行链路上向non-AP MLD发送BTM请求帧，BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的第一上下行链路的目标信标传输时间TBTT为单位。
或者，
该处理模块，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括一个或多个邻居报告元素，邻居报告元素用于指示源AP MLD向non-AP MLD推荐的候选接入点AP；当候选接入点属于候选AP MLD时，邻居报告元素包括基本变体多链路元素，基本变体多链路元素包括多链路控制字段和共同信息字段，且不包括链路信息字段；该收发模块，用于向non-AP MLD发送BTM请求帧。
可选的，第三通信装置的处理模块和收发模块，与源AP MLD可能存在如下几种关系：
1)、该处理模块和收发模块为源AP MLD的某一隶属AP的处理模块和收发模块。
2)、该处理模块和收发模块为源AP MLD的集中处理模块和集中收发模块。
3)、该处理模块为源AP MLD的某一隶属AP的处理模块，该收发模块为源AP MLD的集中收发模块。
4)、该处理模块为源AP MLD的集中处理模块，该收发模块为源AP MLD的某一隶属AP的收发模块。
应理解，本申请实施例提供的第三通信装置即为上述方法中的源AP MLD，其具有上述图11或图12或图13所示方法中源AP MLD的任意功能，具体细节可参见上述方法，此处不再赘述。
以上介绍了本申请实施例的第一通信装置、第二通信装置、以及第三通信装置，以下介绍所述第一通信装置、第二通信装置、以及第三通信装置可能的产品形态。应理解，但凡具备上述图14所述的第一通信装置的特征的任何形态的产品，和但凡具备上述图15所述的第二通信装置的特征的任何形态的产品，以及但凡具备上述图16所述的第三通信装置的特征的任何形态的产品，都落入本申请的保护范围。还应理解，以下介绍仅为举例，不限制本申请实施例的第一通信装置、第二通信装置、以及第三通信装置的产品形态仅限于此。
作为一种可能的产品形态，本申请实施例所述的第一通信装置、第二通信装置、以及第三通信装置，可以由一般性的总线体系结构来实现。
所述第一通信装置，包括处理器和与所述处理器内部连接通信的收发器。
该处理器，用于生成缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该收发器，用于在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告。
可选地，所述第一通信装置还可以包括存储器，所述存储器用于存储处理器执行的指令。
所述第二通信装置，包括处理器和与所述处理器内部连接通信的收发器。
该收发器，用于在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该处理器，用于确定第二传输时长，第二传输时长包括AP MLD为non-AP MLD中的第一隶属non-AP STA分配的用于在第一直连链路上进行直连传输的时长；
该收发器，还用于发送第一时长指示信息，该第一时长指示信息用于指示该第二传输时长。
可选地，所述第二通信装置还可以包括存储器，所述存储器用于存储处理器执行的指令。
所述第三通信装置，包括处理器和与所述处理器内部连接通信的收发器。
该处理器，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括指示信息，指示信息用于指示BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的某一条上下行链路的目标信标传输时间TBTT为单位；该收发器，用于在多条上下行链路中的任一条上下行链路上向non-AP MLD发送BTM请求帧。
或者，
该处理器，用于生成基本服务集转移管理BTM请求帧；该收发器，用于在多条上下行链路中的第一上下行链路上向non-AP MLD发送BTM请求帧，BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的第一上下行链路的目标信标传输时间TBTT为单位。
或者，
该处理器，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括一个或多个邻居报告元素，邻居报告元素用于指示源AP MLD向non-AP MLD推荐的候选接入点AP；当候选接入点属于候选AP MLD时，邻居报告元素包括基本变体多链路元素，基本变体多链路元素包括多链路控制字段和共同信息字段，且不包括链路信息字段；该收发器，用于向non-AP MLD发送BTM请求帧。
可选地，所述第三通信装置还可以包括存储器，所述存储器用于存储处理器执行的指令。
作为另一种可能的产品形态，本申请实施例所述的第一通信装置、第二通信装置、以及第三通信装置，可以由通用处理器来实现。
实现所述第一通信装置的通用处理器包括处理电路和与所述处理电路内部连接通信的输出接口。
该处理电路，用于生成缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该输出接口，用于在多条上下行链路中的第一上下行链路上向AP MLD发送缓冲区报告。
可选地，该通用处理器还可以包括存储介质，所述存储介质用于存储处理电路执行的指令。
实现所述第二通信装置的通用处理器包括处理电路和与所述处理电路内部连接通信的输出接口和输入接口。
该输入接口，用于在多条上下行链路中的第一上下行链路上接收来自non-AP MLD的缓冲区报告，缓冲区报告用于请求non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，第一直连链路为第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA之间的链路，第一目标non-AP STA和non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
该处理电路，用于确定第二传输时长，第二传输时长包括AP MLD为non-AP MLD中的第一隶属non-AP STA分配的用于在第一直连链路上进行直连传输的时长；
该输出接口，还用于发送第一时长指示信息，该第一时长指示信息用于指示该第二传输时长。
可选地，该通用处理器还可以包括存储介质，所述存储介质用于存储处理电路执行的指令。
实现所述第三通信装置的通用处理器包括处理电路和与所述处理电路内部连接通信的输出接口。
该处理电路，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括指示信息，指示信息用于指示BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的某一条上下行链路的目标信标传输时间TBTT为单位；该输出接口，用于在多条上下行链路中的 任一条上下行链路上向non-AP MLD发送BTM请求帧。
或者，
该处理电路，用于生成基本服务集转移管理BTM请求帧；该输出接口，用于在多条上下行链路中的第一上下行链路上向non-AP MLD发送BTM请求帧，BTM请求帧中的去关联定时器和/或有效间隔以多条上下行链路中的第一上下行链路的目标信标传输时间TBTT为单位。
或者，
该处理电路，用于生成基本服务集转移管理BTM请求帧，BTM请求帧包括一个或多个邻居报告元素，邻居报告元素用于指示源AP MLD向non-AP MLD推荐的候选接入点AP；当候选接入点属于候选AP MLD时，邻居报告元素包括基本变体多链路元素，基本变体多链路元素包括多链路控制字段和共同信息字段，且不包括链路信息字段；该输出接口，用于向non-AP MLD发送BTM请求帧。
可选地，该通用处理器还可以包括存储介质，所述存储介质用于存储处理电路执行的指令。
作为又一种可能的产品形态，本申请实施例所述的第一通信装置、第二通信装置、以及第三通信装置，还可以使用下述来实现：一个或多个现场可编程门阵列(field-programmable gate array，FPGA)、可编程逻辑器件(programmable logic device，PLD)、控制器、状态机、门逻辑、分立硬件部件、任何其它适合的电路、或者能够执行本申请通篇所描述的各种功能的电路的任意组合。
应理解，上述各种产品形态的第一通信装置、第二通信装置、以及第三通信装置，分别具有上述方法实施例中non-AP MLD、AP MLD、和源AP MLD的任意功能，此处不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例中描述的各方法步骤和单元，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各实施例的步骤及组成。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。本领域普通技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参见前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分，或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (39)

  1. 一种缓冲区报告发送方法，其特征在于，所述方法应用于非接入点多链路设备non-AP MLD，所述non-AP MLD与接入点多链路设备AP MLD之间建立有多条上下行链路，所述方法包括：
    所述non-AP MLD生成缓冲区报告，所述缓冲区报告用于请求所述non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，所述第一直连链路为第一目标non-AP STA和所述non-AP MLD的第一隶属non-AP STA之间的链路，所述第一目标non-AP STA和所述non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
    所述non-AP MLD在所述多条上下行链路中的第一上下行链路上向所述AP MLD发送所述缓冲区报告。
  2. 根据权利要求1所述的方法，其特征在于，所述缓冲区报告包括链路信息，所述链路信息用于指示所述第一直连链路。
  3. 根据权利要求2所述的方法，其特征在于，所述链路信息为所述第一直连链路的标识，或者，所述链路信息为比特位图。
  4. 根据权利要求2或3所述的方法，其特征在于，所述缓冲区报告包括传输时长信息，所述传输时长信息用于指示第一传输时长，所述第一传输时长为所述non-AP MLD中的第一隶属non-AP STA在所述第一直连链路上进行直连传输的时长。
  5. 根据权利要求2-4任一项所述的方法，其特征在于，所述第一上下行链路为所述多条上下行链路中的任意一条上下行链路。
  6. 根据权利要求2-5任一项所述的方法，其特征在于，所述缓冲区报告还包括缓冲区类型信息，所述缓冲区类型信息用于指示所述缓冲区报告为直连传输对应的缓冲区报告。
  7. 根据权利要求1所述的方法，其特征在于，所述缓冲区报告包括链路信息，且不包括用于指示所述第一直连链路的链路信息，所述传输时长信息用于指示第一传输时长，所述第一传输时长为所述non-AP MLD中的第一隶属non-AP STA在所述第一直连链路上进行直连传输的时长。
  8. 根据权利要求7所述的方法，其特征在于，所述第一上下行链路的标识和所述第一直连链路的标识相同。
  9. 根据权利要求4、7、或8任一项所述的方法，其特征在于，所述传输时长信息包括所述第一传输时长或第一缓冲区的大小，所述第一缓冲区用于缓存所述non-AP MLD中的第一隶属non-AP STA待在所述第一直连链路上发送的数据。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，所述non-AP MLD在所述多条上下行链路中的第一上下行链路上向所述AP MLD发送所述缓冲区报告，包括：
    所述non-AP MLD在所述多条上下行链路中的第一上下行链路上向所述AP MLD发送管理帧，所述管理帧包括所述缓冲区报告。
  11. 根据权利要求10所述的方法，其特征在于，所述管理帧包括聚合控制字段，所述聚合控制字段包括所述缓冲区报告。
  12. 根据权利要求10或11所述的方法，其特征在于，所述管理帧的帧头包括多链路设备信息，所述多链路设备信息用于指示所述non-AP MLD。
  13. 根据权利要求1-9任一项所述的方法，其特征在于，所述non-AP MLD在所述多条上下行链路中的第一上下行链路上向所述AP MLD发送所述缓冲区报告，包括：
    所述non-AP MLD在所述多条上下行链路中的第一上下行链路上向所述AP MLD发送数 据帧，所述数据帧包括聚合控制字段，所述聚合控制包括所述缓冲区报告。
  14. 根据权利要求13所述的方法，其特征在于，所述数据帧的帧头包括多链路设备信息，所述多链路设备信息用于指示所述non-AP MLD。
  15. 一种缓冲区报告接收方法，其特征在于，所述方法应用于接入点多链路设备AP MLD，所述AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路，所述方法包括：
    所述AP MLD在所述多条上下行链路中的第一上下行链路上接收来自所述non-AP MLD的缓冲区报告，所述缓冲区报告用于请求所述non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，所述第一直连链路为第一目标non-AP STA和所述non-AP MLD的第一隶属non-AP STA之间的链路，所述第一目标non-AP STA和所述non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
    所述AP MLD确定第二传输时长，所述第二传输时长包括所述AP MLD为所述non-AP MLD中的第一隶属non-AP STA分配的用于在所述第一直连链路上进行直连传输的时长；
    所述AP MLD发送第一时长指示信息，所述第一时长指示信息用于指示所述第二传输时长。
  16. 根据权利要求15所述的方法，其特征在于，所述缓冲区报告包括链路信息，所述链路信息用于指示所述第一直连链路。
  17. 根据权利要求16所述的方法，其特征在于，所述链路信息为所述第一直连链路的标识，或者，所述链路信息为比特位图。
  18. 根据权利要求16或17所述的方法，其特征在于，所述缓冲区报告包括传输时长信息，所述传输时长信息用于指示第一传输时长，所述第一传输时长为所述non-AP MLD中的第一隶属non-AP STA在所述第一直连链路上进行直连传输的时长。
  19. 根据权利要求16-18任一项所述的方法，其特征在于，所述第一上下行链路为所述多条上下行链路中的任意一条上下行链路。
  20. 根据权利要求16-19任一项所述的方法，其特征在于，所述缓冲区报告还包括缓冲区类型信息，所述缓冲区类型信息用于指示所述缓冲区报告为直连传输对应的缓冲区报告。
  21. 根据权利要求15所述的方法，其特征在于，所述缓冲区报告包括链路信息，且不包括用于指示所述第一直连链路的链路信息，所述传输时长信息用于指示第一传输时长，所述第一传输时长为所述non-AP MLD中的第一隶属non-AP STA在所述第一直连链路上进行直连传输的时长。
  22. 根据权利要求21所述的方法，其特征在于，所述第一上下行链路的标识和所述第一直连链路的标识相同。
  23. 根据权利要求18、21、或22任一项所述的方法，其特征在于，所述传输时长信息包括所述第一传输时长或第一缓冲区的大小，所述第一缓冲区用于缓存所述non-AP MLD中的第一隶属non-AP STA待在所述第一直连链路上发送的数据。
  24. 根据权利要求15-23任一项所述的方法，其特征在于，所述AP MLD在所述多条上下行链路中的第一上下行链路上接收来自所述non-AP MLD的缓冲区报告，包括：
    所述AP MLD在所述多条上下行链路中的第一上下行链路上接收来自所述non-AP MLD的管理帧，所述管理帧包括所述缓冲区报告。
  25. 根据权利要求24所述的方法，其特征在于，所述管理帧包括聚合控制字段，所述聚合控制字段包括所述缓冲区报告。
  26. 根据权利要求24或25所述的方法，其特征在于，所述管理帧的帧头包括多链路设备信息，所述多链路设备信息用于指示所述non-AP MLD。
  27. 根据权利要求15-26任一项所述的方法，其特征在于，所述AP MLD在所述多条上下行链路中的第一上下行链路上接收来自所述non-AP MLD的缓冲区报告，包括：
    所述AP MLD在所述多条上下行链路中的第一上下行链路上接收来自所述non-AP MLD的数据帧，所述数据帧包括聚合控制字段，所述聚合控制包括所述缓冲区报告。
  28. 根据权利要求27所述的方法，其特征在于，所述数据帧的帧头包括多链路设备信息，所述多链路设备信息用于指示所述non-AP MLD。
  29. 一种非接入点多链路设备non-AP MLD，其特征在于，所述non-AP MLD与接入点多链路设备AP MLD之间建立有多条上下行链路，所述non-AP MLD包括：处理模块和收发模块；
    所述处理模块，用于生成缓冲区报告，所述缓冲区报告用于请求所述non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，所述第一直连链路为第一目标non-AP STA和所述non-AP MLD的第一隶属non-AP STA之间的链路，所述第一目标non-AP STA和所述non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
    所述收发模块，用于在所述多条上下行链路中的第一上下行链路上向所述AP MLD发送所述缓冲区报告。
  30. 根据权利要求29所述的non-AP MLD，其特征在于，所述non-AP MLD用于实现如权利要求2-14任一项所述的方法。
  31. 一种接入点多链路设备AP MLD，其特征在于，所述AP MLD与非接入点多链路设备non-AP MLD之间建立有多条上下行链路，所述AP MLD包括：处理模块和收发模块；
    所述收发模块，用于在所述多条上下行链路中的第一上下行链路上接收来自所述non-AP MLD的缓冲区报告，所述缓冲区报告用于请求所述non-AP MLD中的第一隶属非接入点站点non-AP STA在第一直连链路上进行直连传输的时长，所述第一直连链路为第一目标non-AP STA和所述non-AP MLD的第一隶属non-AP STA之间的链路，所述第一目标non-AP STA和所述non-AP MLD的第一隶属non-AP STA属于同一基本服务集BSS；
    所述处理模块，用于确定第二传输时长，所述第二传输时长包括所述AP MLD为所述non-AP MLD中的第一隶属non-AP STA分配的用于在所述第一直连链路上进行直连传输的时长；
    所述收发模块，还用于发送第一时长指示信息，所述第一时长指示信息用于指示所述第二传输时长。
  32. 根据权利要求31所述的AP MLD，其特征在于，所述AP MLD用于实现如权利要求16-28任一项所述的方法。
  33. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序包括用于执行权利要求1-14任一项方法的指令。
  34. 一种计算机可读存储介质，其特征在于，用于存储计算机程序，所述计算机程序包括用于执行权利要求15-28任一项方法的指令。
  35. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行权利要求1-14任一项方法的指令。
  36. 一种计算机程序产品，其特征在于，所述计算机程序产品包括用于执行权利要求15-28任一项方法的指令。
  37. 一种通信装置，所述通信装置用于非接入点多链路设备non-AP MLD，其特征在于，所述通信装置用于实现如权利要求1-14任一项所述的方法。
  38. 一种通信装置，所述通信装置用于接入点多链路设备AP MLD，其特征在于，所述通信装置用于实现如权利要求15-28任一项所述的方法。
  39. 一种通信系统，其特征在于，所述通信系统包括：
    如权利要求37所述的通信装置，和/或，如权利要求38所述的通信装置。
PCT/CN2022/106968 2021-07-23 2022-07-21 缓冲区报告发送、接收方法及装置 WO2023001221A1 (zh)

Priority Applications (6)

Application Number Priority Date Filing Date Title
CA3227140A CA3227140A1 (en) 2021-07-23 2022-07-21 Buffer report sending and receiving method, and apparatus
KR1020247004807A KR20240027839A (ko) 2021-07-23 2022-07-21 버퍼 보고 송신 및 수신 방법 및 장치
AU2022314029A AU2022314029A1 (en) 2021-07-23 2022-07-21 Buffer report sending and receiving method, and apparatus
CN202280050960.1A CN117751665A (zh) 2021-07-23 2022-07-21 缓冲区报告发送、接收方法及装置
EP22845385.8A EP4358619A1 (en) 2021-07-23 2022-07-21 Buffer report sending method and device and buffer report receiving method and device
US18/413,795 US20240155717A1 (en) 2021-07-23 2024-01-16 Buffer report sending and receiving method, and apparatus

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202110838424 2021-07-23
CN202110838424.5 2021-07-23
CN202111093436.6 2021-09-17
CN202111093436.6A CN115696275A (zh) 2021-07-23 2021-09-17 缓冲区报告发送、接收方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/413,795 Continuation US20240155717A1 (en) 2021-07-23 2024-01-16 Buffer report sending and receiving method, and apparatus

Publications (1)

Publication Number Publication Date
WO2023001221A1 true WO2023001221A1 (zh) 2023-01-26

Family

ID=84979743

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/106968 WO2023001221A1 (zh) 2021-07-23 2022-07-21 缓冲区报告发送、接收方法及装置

Country Status (8)

Country Link
US (1) US20240155717A1 (zh)
EP (1) EP4358619A1 (zh)
KR (1) KR20240027839A (zh)
CN (3) CN116528288A (zh)
AU (1) AU2022314029A1 (zh)
CA (1) CA3227140A1 (zh)
TW (1) TW202306429A (zh)
WO (1) WO2023001221A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116963314A (zh) * 2023-09-21 2023-10-27 南京云程半导体有限公司 一种协作组播方法、电子设备及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017166197A1 (zh) * 2016-03-31 2017-10-05 华为技术有限公司 一种缓存处理方法和用户设备
US20190215905A1 (en) * 2014-08-21 2019-07-11 Lg Electronics Inc. Method and apparatus for triggering uplink data in wireless lan
CN112492682A (zh) * 2020-06-01 2021-03-12 中兴通讯股份有限公司 数据发送方法及装置、数据接收方法及装置
CN112771940A (zh) * 2018-10-01 2021-05-07 高通股份有限公司 针对来自交叠无线局域网的协调式传输的功率控制
CN114762439A (zh) * 2020-06-24 2022-07-15 索尼集团公司 频域中具有被共享的txop的单个bss中的协调站

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105682137B (zh) * 2013-08-09 2019-04-30 株式会社Kt 终端之间直接通信中缓冲状态报告传输方法及其装置
KR20170062719A (ko) * 2015-11-30 2017-06-08 주식회사 아이티엘 고효율 무선랜에서 상향링크 다중 사용자 전송을 지원하기 위한 채널 액세스 방법 및 장치
US20170332385A1 (en) * 2016-05-11 2017-11-16 Qualcomm Incorporated Buffer status reporting in a wireless local area network (wlan)
US11510269B2 (en) * 2019-07-01 2022-11-22 Qualcomm Incorporated Signaling for multi-link communication in a wireless local area network (WLAN)
US11602002B2 (en) * 2020-01-04 2023-03-07 Nxp Usa, Inc. Method and apparatus for multi-link operations
US11736939B2 (en) * 2020-01-04 2023-08-22 Nxp Usa, Inc. Apparatus and method for multi-link management in multi-link communication systems

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190215905A1 (en) * 2014-08-21 2019-07-11 Lg Electronics Inc. Method and apparatus for triggering uplink data in wireless lan
WO2017166197A1 (zh) * 2016-03-31 2017-10-05 华为技术有限公司 一种缓存处理方法和用户设备
CN112771940A (zh) * 2018-10-01 2021-05-07 高通股份有限公司 针对来自交叠无线局域网的协调式传输的功率控制
CN112492682A (zh) * 2020-06-01 2021-03-12 中兴通讯股份有限公司 数据发送方法及装置、数据接收方法及装置
CN114762439A (zh) * 2020-06-24 2022-07-15 索尼集团公司 频域中具有被共享的txop的单个bss中的协调站

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116963314A (zh) * 2023-09-21 2023-10-27 南京云程半导体有限公司 一种协作组播方法、电子设备及存储介质
CN116963314B (zh) * 2023-09-21 2023-12-22 南京云程半导体有限公司 一种协作组播方法、电子设备及存储介质

Also Published As

Publication number Publication date
TW202306429A (zh) 2023-02-01
CN116528287B (zh) 2024-01-05
CA3227140A1 (en) 2023-01-26
EP4358619A1 (en) 2024-04-24
CN117751665A (zh) 2024-03-22
CN116528287A (zh) 2023-08-01
CN116528288A (zh) 2023-08-01
US20240155717A1 (en) 2024-05-09
AU2022314029A1 (en) 2024-01-25
KR20240027839A (ko) 2024-03-04

Similar Documents

Publication Publication Date Title
WO2021089022A1 (zh) 一种多链路设备间的通信方法和装置
US9503976B2 (en) Grouping-based data transceiving method in wireless LAN system and apparatus for supporting same
US9538368B2 (en) Method for transceiving data on basis of grouping in wireless LAN system, and device for supporting same
US9060359B2 (en) Method and apparatus for transceiving data in a wireless LAN system
JP5722424B2 (ja) ６０ＧＨｚにおけるＢＳＳ／ＰＢＳＳをサポートし且つスケジューリングがないネットワーキング
CN113411831B (zh) 数据传输的方法和装置
US9456456B2 (en) Grouping-based data transceiving method in wireless LAN system and apparatus for supporting same
WO2020216133A1 (zh) 一种通信方法及设备
US20240155717A1 (en) Buffer report sending and receiving method, and apparatus
WO2022012560A1 (zh) 数据传输方法及装置
KR20220104644A (ko) 다중 링크를 지원하는 통신 시스템에서 저지연 통신을 위한 방법 및 장치
CN116133043A (zh) 多链路通信方法、装置及可读存储介质
CN115696275A (zh) 缓冲区报告发送、接收方法及装置
WO2023066181A1 (zh) 业务优先级确定方法以及相关装置
WO2024131809A1 (zh) 一种通信的方法和通信装置
WO2022152184A1 (zh) 多链路的重配置方法及装置
WO2023124105A1 (zh) 数据传输的方法与通信装置
CN118234060A (zh) 一种通信的方法和通信装置
KR20230062436A (ko) Emlsr을 지원하는 무선랜에서 링크 설정을 위한 방법 및 장치
WO2023133178A1 (en) Triggered txop sharing (txs) power save
CN116868617A (zh) 在支持多个链路的通信系统中用于接收下行链路流量的方法和装置
CN118044279A (zh) 用于在支持多链路的通信系统中发送用于nstr操作的同步信息的方法和装置
Huang et al. An interference-aware power control scheme in wireless mesh networks

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22845385

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022314029

Country of ref document: AU

Ref document number: AU2022314029

Country of ref document: AU

WWE Wipo information: entry into national phase

Ref document number: 2022845385

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 202280050960.1

Country of ref document: CN

ENP Entry into the national phase

Ref document number: 2024503900

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: MX/A/2024/001066

Country of ref document: MX

Ref document number: 3227140

Country of ref document: CA

ENP Entry into the national phase

Ref document number: 2022314029

Country of ref document: AU

Date of ref document: 20220721

Kind code of ref document: A

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112024001360

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 20247004807

Country of ref document: KR

Kind code of ref document: A

Ref document number: 2022845385

Country of ref document: EP

Effective date: 20240117

WWE Wipo information: entry into national phase

Ref document number: 1020247004807

Country of ref document: KR

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112024001360

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20240123