WO2020238812A1 - 一种适用于多链路的通信方法及相关设备 - Google Patents

一种适用于多链路的通信方法及相关设备 Download PDF

Info

Publication number
WO2020238812A1
WO2020238812A1 PCT/CN2020/091940 CN2020091940W WO2020238812A1 WO 2020238812 A1 WO2020238812 A1 WO 2020238812A1 CN 2020091940 W CN2020091940 W CN 2020091940W WO 2020238812 A1 WO2020238812 A1 WO 2020238812A1
Authority
WO
WIPO (PCT)
Prior art keywords
sequence number
field
confirmation
link
block confirmation
Prior art date
Application number
PCT/CN2020/091940
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
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP20814644.9A priority Critical patent/EP3968731B1/en
Priority to EP23186955.3A priority patent/EP4287580A3/en
Publication of WO2020238812A1 publication Critical patent/WO2020238812A1/zh

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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1614—Details of the supervisory signal using bitmaps
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1685—Details of the supervisory signal the supervisory signal being transmitted in response to a specific request, e.g. to a polling signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1835—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/27—Evaluation or update of window size, e.g. using information derived from acknowledged [ACK] packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • 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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • This application relates to the field of communication technology, and in particular to a communication method and related equipment suitable for multi-link.
  • OFDMA orthogonal frequency division multiple access
  • the 802.11ax standard and the standards before 802.11ax have configured multiple links for the wireless fidelity (WiFi) of the same working frequency band, but a different basic service set (BSS) is established in each link , Only one link can communicate with the stations in the BSS to which the link belongs at a time, which affects the communication efficiency.
  • WiFi wireless fidelity
  • BSS basic service set
  • the embodiments of the present application provide a communication method and related equipment suitable for multiple links, which can improve communication efficiency.
  • an embodiment of the present application provides a communication method suitable for multiple links, including: a first device sends an ADDBA request frame to a second device, the ADDBA request frame includes at least one reference value of a first buffer size field and A reference value of the second buffer size field; the first device and the second device are multilink entities including one or more links; the first device receives the ADDBA response frame sent by the second device, and the ADDBA response frame includes at least one The confirmation value of the first buffer size field and the confirmation value of the second buffer size field; according to the ADDBA request frame and the ADDBA response frame, a multi-link between the multiple links of the first device and the multiple links of the second device is established Road block confirmation dialog; where a first buffer size field is used to indicate the size of a local buffer space corresponding to one of the links of the first device and the second device, and the second buffer size field is used to indicate The size of a global buffer space maintained by the first device and the second device.
  • the first device maintains multiple first sending windows and one second sending window, where multiple first sending windows and multiple chains of the first device Corresponding to the path, the second sending window corresponds to the multilink entity of the first device.
  • the sending of data packets is managed and controlled through the sending window, so that data packets can be sent on multiple links.
  • a first sending window corresponds to one of the multiple links.
  • a first sending window has a start sequence number of WinStartO1, an end sequence number of WinEndO1, and a window size of WinSizeO1, where WinSizeO1 is equal to The confirmation value of the first buffer size field corresponding to the link; the start sequence number of the second sending window is WinStartO2, the end sequence number is WinEndO2, and the window size is WinSizeO2, where WinSizeO2 is equal to the second negotiated through the ADDBA request frame and the ADDBA response frame Confirmation value of the buffer size.
  • the sending of data packets is guaranteed by the size of the sending window, the starting sequence number and the ending sequence number.
  • the ADDBA request frame includes the first block confirmation start sequence number control field and the second block confirmation start sequence number control field.
  • the first block confirmation start sequence number control field is used to indicate the second block confirmation start sequence number control field.
  • the first initial sequence number of the initial sequence number of the first scoreboard of the link of the device may also be used to indicate the first initial sequence number of the initial sequence number of the first receiving window of the link of the second device.
  • the type of the first initial sequence number is the local sequence number;
  • the second block of confirmation start sequence number control field is used to indicate the second initial sequence number of the start sequence number of the second scoreboard of the multilink entity of the second device , Can also be used to indicate the first initial sequence number of the initial sequence number of the second receiving window of the link of the second device.
  • the type of the second initial serial number is a global serial number.
  • the first initial sequence number instructs the low MAC layer of the second device to maintain a scoreboard or receiving window
  • the second initial sequence number instructs the high MAC layer of the second device to maintain a scoreboard or receiving window.
  • the ADDBA request frame includes at least one of the link bitmap field and the reference value of the at least one first buffer size field, or the link number field, the multiple link identification number field, and At least one of the reference values of the at least one first buffer size field;
  • the ADDBA response frame includes at least one of the link bitmap field and the confirmation value of the at least one first buffer size field, or, the number of links field, multiple At least one of the link identity number field and the confirmation value of the at least one first buffer size field.
  • the first buffer size is negotiated through the ADDBA request frame and the ADDBA response frame to ensure that the size of the local buffer space of each link of the first device and the second device is the same.
  • the ADDBA request frame includes the first block of confirmation parameter set field, the first block of confirmation parameter set field includes the reference value of the second buffer size field; the ADDBA response frame includes the second block of confirmation parameter set field, The second block confirmation parameter set field includes the confirmation value of the second buffer size.
  • the second buffer size is negotiated through the ADDBA request frame and the ADDBA response frame to ensure that the size of the global buffer space of the multilink entity of the first device and the second device are the same.
  • the first device sends a data packet to the second device; and receives a confirmation message replying to the data packet from the second device.
  • the data packet includes a local sequence number and a global sequence number.
  • the local sequence number is the identifier assigned to the data packet by the link sending the data packet among multiple links
  • the global sequence number is the identifier assigned to the data packet by the multilink entity.
  • the first device sends a block confirmation request frame or a multi-user block confirmation request trigger frame to the second device, and the block confirmation request frame or the multi-user block confirmation request trigger frame includes a start sequence number control field, The start sequence number control field includes the start sequence number; the block confirmation request frame or the multi-user block confirmation request trigger frame also includes the first indication information, the first indication information is used to indicate the type of the start sequence number, the initial sequence number Types include local serial number or global serial number. Therefore, the second device can confirm that the data packet is received through the type of the initial serial number, and generate a block confirmation bitmap corresponding to the local serial number or a block confirmation bitmap corresponding to the global serial number.
  • the first device receives the block confirmation frame sent by the second device, the block confirmation frame includes a start sequence number control field, and the start sequence number control field includes a start sequence number and a block confirmation bitmap ;
  • the block confirmation bitmap is used to indicate the reception of the data packet received by the second device;
  • the block confirmation frame also includes the block confirmation BA control field, the BA control field includes the second indication information, the second indication information is used to indicate the start The type of the serial number, the type of the initial serial number is a local serial number or a global serial number, and the first bit in the block confirmation bitmap corresponds to the initial serial number.
  • both the ADDBA request frame and the ADDBA response frame include a block confirmation function field, and the block confirmation function field includes information used to indicate the function type of the multilink block confirmation session;
  • Function types include: multi-link block confirmation request, multi-link block confirmation response, multi-link block confirmation dialog removal; among them, the information in the ADDBA request frame indicates that the multi-link block confirmation session is a multi-link block confirmation request;
  • ADDBA The information in the response frame indicates that the multilink block confirmation session is a multilink block confirmation response.
  • an embodiment of the present application provides a communication method suitable for multiple links, including: a second device receives an ADDBA request frame sent by a first device, and the ADDBA request frame includes at least one reference value of a first buffer size field and A reference value of the second buffer size field; the first device and the second device are multi-link entities including one or more links; the ADDBA response frame sent by the second device to the first device, the ADDBA response frame includes at least one The confirmation value of the first buffer size field and the confirmation value of the second buffer size field; according to the ADDBA request frame and the ADDBA response frame, a multi-link between the multiple links of the first device and the multiple links of the second device is established Road block confirmation dialog; where a first buffer size field is used to indicate the size of a local buffer space corresponding to one of the links of the first device and the second device, and the second buffer size field is used to indicate The size of a global buffer space maintained by the first device and the second device.
  • the second device maintains a receiving window, where the receiving window corresponds to the link entity of the second device; where the starting sequence number of the receiving window is WinStartB2, The end sequence number is WinEndB2, and the window size is WinSizeB2, where WinSizeB2 is equal to the smaller value in the confirmation value of the second buffer size field and the maximum length block confirmation bitmap.
  • the sending of data packets is managed and controlled through the sending window, so that data packets can be sent on multiple links, thereby improving communication efficiency.
  • the second device maintains multiple first receiving windows and one second receiving window, wherein the multiple first receiving windows and multiple pieces of the second device The link corresponds, and the second receiving window corresponds to the link entity of the second device.
  • the sending of data packets is managed and controlled through the sending window, so that data packets can be sent on multiple links, thereby improving communication efficiency.
  • a first receiving window corresponds to one of the multiple links.
  • the first receiving window has a start sequence number of WinStartB1, an end sequence number of WinEndB1, and a window size of WinSizeB1, where WinSizeB1 is equal to the chain
  • the confirmation value of the first buffer size field corresponding to the path and the smaller value in the block confirmation bitmap of the maximum length; the start sequence number of the second receiving window is WinStartB2, the end sequence number is WinEndB2, and the window size is WinSizeB2.
  • the confirmation value equal to the second buffer size and the smaller value in the block confirmation bitmap of the maximum length. Reorder the received data packets by the size of the receiving window, the start sequence number, and the end sequence number.
  • the ADDBA request frame includes the first block confirmation start sequence number control field and the second block confirmation start sequence number control field.
  • the first block confirmation start sequence number control field is used to indicate the second block confirmation start sequence number control field.
  • the first initial sequence number of the starting sequence number of the first scoreboard of the link of the device may also be used to indicate the first initial sequence number of the starting sequence number of the first receiving window of the link of the second device.
  • the type of the initial serial number is the local serial number.
  • the second block confirmation start sequence number control field is used to indicate the second initial sequence number of the start sequence number of the second scoreboard of the multilink entity of the second device, and can also be used to indicate the link status of the second device.
  • the first initial serial number of the initial serial number of the second receiving window, and the type of the second initial serial number is the global serial number.
  • the first initial sequence number instructs the low MAC layer of the second device to maintain a scoreboard or receiving window
  • the second initial sequence number instructs the high MAC layer of the second device to maintain a scoreboard or receiving window.
  • the ADDBA request frame includes at least one of the link bitmap field and the reference value of the at least one first buffer size field, or the link number field, the multiple link identification number field, and At least one of the reference values of the at least one first buffer size field;
  • the ADDBA response frame includes at least one of the link bitmap field and the confirmation value of the at least one first buffer size field, or, the number of links field, multiple At least one of the link identity number field and the confirmation value of the at least one first buffer size field.
  • the first buffer size is negotiated through the ADDBA request frame and the ADDBA response frame to ensure that the size of the local buffer space of each link of the first device and the second device is the same.
  • the first buffer size is negotiated through the ADDBA request frame and the ADDBA response frame to ensure that the size of the local buffer space of each link of the first device and the second device is the same.
  • the ADDBA request frame includes the first block of confirmation parameter set field, the first block of confirmation parameter set field includes the reference value of the second buffer size field; the ADDBA response frame includes the second block of confirmation parameter set field, The second block confirmation parameter set field includes the confirmation value of the second buffer size.
  • the second buffer size is negotiated through the ADDBA request frame and the ADDBA response frame to ensure that the size of the global buffer space of the multilink entity of the first device and the second device are the same.
  • the second device receives the data packet sent by the first device; and sends a confirmation message for responding to the data packet to the first device.
  • the data packet includes a local sequence number and a global sequence number.
  • the local sequence number is the identifier assigned to the data packet by the link sending the data packet among multiple links
  • the global sequence number is the identifier assigned to the data packet by the multilink entity.
  • the second device receives the block confirmation request frame or the multi-user block confirmation request trigger frame sent by the first device, and the block confirmation request frame or the multi-user block confirmation request trigger frame includes the start sequence number control field ,
  • the start sequence number control field includes the start sequence number;
  • the block confirmation request frame or the multi-user block confirmation request trigger frame also includes the first indication information, the first indication information is used to indicate the type of the start sequence number, the start sequence number
  • the types include local serial number or global serial number. Therefore, the second device can confirm that the data packet is received through the type of the initial serial number, and generate a block confirmation bitmap corresponding to the local serial number or a block confirmation bitmap corresponding to the global serial number.
  • the second device maintains multiple first scoreboards and one second scoreboard; multiple first scoreboards correspond to multiple links, and the second scoreboard corresponds to multiple links.
  • Link entities correspond; the start sequence number of a first scoreboard is WinStartR1, and the end sequence number is WinEndR1; the scoreboard size WinSizeR1 is equal to the value of the confirmation value of the first buffer size field corresponding to the corresponding link and the maximum length
  • the block confirms the smaller value in the bitmap.
  • the confirmation message is a block confirmation frame;
  • the block confirmation frame includes the start sequence number control field, and the start sequence number control field includes the start sequence number and the block confirmation bitmap; the block confirmation bitmap Used to indicate the reception status of the data packet received by the second device.
  • the block confirmation frame also includes a block confirmation BA control field, the BA control field includes second indication information, the second indication information is used to indicate the type of the starting sequence number, the type of the starting sequence number is the local sequence number or the global sequence number, and The first bit in the block confirmation bitmap corresponds to the starting sequence number.
  • the sequence corresponding to the block confirmation bitmap is the local serial number
  • the sequence number corresponding to the first bit in the block confirmation bitmap is WinStartR1
  • the block confirmation bitmap is The corresponding sequence is the global sequence number
  • the sequence number corresponding to the first bit in the block confirmation bitmap is WinStartR2.
  • both the ADDBA request frame and the ADDBA response frame include a block confirmation function field, and the block confirmation function field includes information indicating the function type of the multilink block confirmation session;
  • Function types include: multi-link block confirmation request, multi-link block confirmation response, multi-link block confirmation dialog removal; among them, the information in the ADDBA request frame indicates that the multi-link block confirmation session is a multi-link block confirmation request;
  • ADDBA The information in the response frame indicates that the multilink block confirmation session is a multilink block confirmation response.
  • an embodiment of the present application provides a data frame transmission method, including: a first device sends a message frame to a second device, the message frame includes first indication information, and the first indication information is used to indicate Main link. Send second indication information to the second device through the main link, the second indication information indicates the working status or sleep state of multiple links, or negotiate TWT with the second device through the main link, so that other links are in the sleep state Or off state, thus saving power.
  • the first indication information is a special element.
  • the first device can send a message frame to the second device through the main link.
  • the message frame can carry a special element that is only carried on the main link.
  • this special element is used to indicate that the link transmitting the message frame is the primary link.
  • the main link is indicated by a special element, so that other links are in a dormant state or closed state, thereby saving power.
  • the first indication information is the link sequence number
  • the first device can send a message frame to the second device through a non-primary link.
  • the message frame can carry a reduced neighbor report element or a multi-band element to reduce
  • the version neighbor report element or the multi-band element includes a link sequence number, and the link sequence number is used to indicate the main link of the multiple links.
  • the main link is indicated by the link sequence number, so that other links are in a dormant state or closed state, thereby saving power.
  • an operation type field is added to the information field of the single-user TWT parameter or the information field of the broadcast TWT parameter, and the operation type field and the TWT channel field are combined to indicate the application of the TWT element in multiple links. Which link.
  • An indication value may be added to the broadcast TWT parameter information field, and the indication value is used to indicate which link of the multiple links the TWT element is applied to. It can work within the service window indicated by the TWT parameter, and sleep outside the service window, thereby saving power.
  • one or more link sequence numbers are added to the information field of the single-user TWT parameter and the information field of the broadcast TWT parameter, and the link sequence number is used to indicate that the TWT element is applied to multiple links Which link in.
  • the link sequence number bitmap is used to indicate which link of the multiple links the TWT element is applied to. Work within the service window indicated by the TWT parameter is realized, and sleep can be carried out outside the service window, thereby saving power.
  • an embodiment of the present application provides a data frame transmission method, including: a second device receives a message frame sent by a first device, the message frame includes first indication information, and the first indication information is used to indicate Main link.
  • the second device receives the second indication information sent by the first device through the main link.
  • the second indication information indicates the working status or dormant state of multiple links, or negotiates TWT with the first device through the main link to make other links In the sleep state or off state, so as to save power.
  • the first indication information is a special element
  • the second device can receive a message frame sent by the first device through the main link.
  • the message frame can carry a special element that is only carried in the main chain.
  • this special element is used to indicate that the link transmitting the message frame is the primary link.
  • the main link is indicated by a special element, so that other links are in a dormant state or closed state, thereby saving power.
  • the first indication information is the link sequence number
  • the second device can receive the message frame sent by the first device over the non-primary link
  • the message frame can carry a reduced neighbor report element or a multi-band element.
  • the reduced neighbor report element or the multi-band element includes a link sequence number
  • the link sequence number is used to indicate the main link of the multiple links.
  • the main link is indicated by the link sequence number, so that other links are in a dormant state or closed state, thereby saving power.
  • an embodiment of the present application provides a first communication device, and the first device is configured to implement the methods and functions performed by the first device in the first and third aspects described above, and is implemented by hardware/software, Its hardware/software includes modules corresponding to the above-mentioned functions.
  • an embodiment of the present application provides a second communication device, and the second device is configured to implement the methods and functions performed by the second device in the second and fourth aspects described above, and is implemented by hardware/software, Its hardware/software includes modules corresponding to the above-mentioned functions.
  • an embodiment of the present application provides another first device, including: a processor, a memory, and a communication bus, where the communication bus is used to implement connection and communication between the processor and the memory, and the processor executes the data stored in the memory
  • the program is used to implement the steps of the first and third aspects described above.
  • the first device provided in this application may include a module corresponding to the behavior of the first entity in the above method design.
  • the module can be software and/or hardware.
  • an embodiment of the present application provides another second device, including: a processor, a memory, and a communication bus, where the communication bus is used to implement connection and communication between the processor and the memory, and the processor executes the data stored in the memory
  • the program is used to implement the steps provided in the second and fourth aspects above.
  • the second device provided in this application may include a module corresponding to the behavior of the first device in the above method design.
  • the module can be software and/or hardware.
  • the present application provides a computer-readable storage medium that stores instructions in the computer-readable storage medium, which when run on a computer, causes the computer to execute the methods of the above aspects.
  • this application provides a computer program product containing instructions, which when run on a computer, causes the computer to execute the methods of the above-mentioned aspects.
  • a chip including a processor, configured to call and execute instructions stored in the memory from a memory, so that a communication device installed with the chip executes the method of any one of the above aspects.
  • the embodiments of the present application also provide another chip.
  • the chip may be a chip in the first device or the second device.
  • the chip includes: an input interface, an output interface, and a processing circuit.
  • the output interface and the circuit are connected through an internal connection path, and the processing circuit is used to execute the method of any one of the above aspects.
  • another chip including: an input interface, an output interface, a processor, and optionally, a memory.
  • the input interface, the output interface, the processor, and the memory pass through internal
  • the connection path is connected, the processor is used to execute the code in the memory, and when the code is executed, the processor is used to execute the method in any one of the foregoing aspects.
  • a device is provided to implement the method in any one of the foregoing aspects.
  • FIG. 1 is a schematic diagram of a multi-band operation provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of the architecture of a multi-band hardware provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of an AP and STA provided by an embodiment of the present application.
  • FIG. 5 is a schematic diagram of another AP and STA structure provided by an embodiment of the present application.
  • FIG. 6 is a schematic flowchart of a communication method suitable for multi-link according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of an ADDBA request frame provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram of a block confirmation function field provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a block confirmation parameter set field provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of a multi-link element provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a transmitting end of a first device according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a receiving end of a second device according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of an ADDBA response frame provided by an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a MAC header provided by an embodiment of the present application.
  • FIG. 15 is a schematic diagram of a block confirmation request frame or a multi-user block confirmation request trigger frame provided by an embodiment of the present application;
  • FIG. 16 is a schematic diagram of a block confirmation frame provided by an embodiment of the present application.
  • FIG. 17 is a schematic flowchart of a data frame transmission method provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram of a TWT element provided by an embodiment of the present application.
  • FIG. 19 is a schematic diagram of a single-user TWT type provided by an embodiment of the present application.
  • FIG. 20 is a schematic diagram of a type of broadcast TWT provided by an embodiment of the present application.
  • FIG. 21 is a schematic structural diagram of a first communication device provided by an embodiment of the present application.
  • FIG. 22 is a schematic structural diagram of a second communication device provided by an embodiment of the present application.
  • FIG. 23 is a schematic structural diagram of another first device proposed in an embodiment of the present application.
  • FIG. 24 is a schematic structural diagram of another second device proposed in an embodiment of the present application.
  • 802.11ax standard workers expanded the working range of 802.11ax devices from 2.4GHz, 5GHz to 2.4GHz, 5GHz and 6GHz in the 802.11ax project authorization requests (PAR).
  • PAR project authorization requests
  • the specific standard protocols involved such as the maximum bandwidth supported by the frame structure of 160M, have not been changed.
  • the 802.11a frame structure of the first generation of mainstream WiFi starts with the preamble, including the traditional short training sequence field (L-STF), the traditional long training sequence field (legacy-long training field, L-LTF), In the legacy-signal field (L-SIG), the preamble of 802.11a is called the legacy preamble.
  • L-STF traditional short training sequence field
  • L-LTF legacy-long training field
  • L-SIG legacy-signal field
  • the frame structures of subsequent mainstream WiFi protocols 802.11g, 802.11n, 802.11ac and 802.11ax all start with the traditional preamble to be compatible with traditional sites.
  • the extremely high throughput (EHT) devices of the IEEE 802.11 next-generation WiFi protocol require forward compatibility, so they will also support the working frequency bands of 802.11ax devices, that is, 2.4GHz, 5GHz and 6GHz frequency bands.
  • the next-generation WIFI protocol also needs to be forward compatible.
  • the frame structure starts with a traditional preamble, followed by a new-generation preamble.
  • the new-generation preamble includes instructions for implementing new functions of the new-generation WIFi protocol EHT, such as the ultra-large bandwidth Bandwidth indication.
  • the new-generation preamble also carries indication information, which is used to indicate that the physical layer protocol data unit (PHY protocol data unit, PPDU) is an EHT PPDU, so that it will not be misjudged by the receiver as a traditional PPDU.
  • PHY protocol data unit PHY protocol data unit
  • PPDU physical layer protocol data unit
  • 802.11a PPDU, 802.11n high throughput (HT) PPDU, 802.11ac very high throughput (VHT) PPDU or 802.11ax HE PPDU 802.11ax next-generation WiFi EHT protocol can also cooperate with more streams (such as increasing the number of streams to 16 streams) and multiple frequency bands (such as 2.4GHz, 5GHz and 6GHz) Improve peak throughput. In the same frequency band, the peak throughput can also be improved by means of multiple channel cooperation, and the delay of service transmission can be reduced.
  • multi-band or multi-channel can be collectively referred to as multi-link.
  • the 802.11ax standard and standards before 802.11ax configure multiple links in one or more working frequency bands WiFi, but each link establishes a different BSS, and only one link can belong to the link at a time Station communication within the BSS.
  • multi-link cooperation technology can also use multi-link cooperation technology to send the same type of data packets to the same site at the same time.
  • FIG. 1 is a schematic diagram of a multi-band operation provided by an embodiment of the present application.
  • WiFi working frequency bands include below 1GHz, 2.4GHz and 5GHz and high frequency 60GHz, while mainstream WiFi protocols 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, and 802.11ax mainly work at 2.4GHz and 5GHz, supporting multi-band cooperation technology.
  • Figure 1 shows the operation of 2 frequency bands.
  • the operation unit of each frequency band includes MAC processing unit (MAC unit), baseband unit (baseband unit, BBU), radio frequency unit (RFU) and antenna module ( antenna module). Among them, multiple frequency bands share the MAC processing unit and the antenna module.
  • MAC unit MAC processing unit
  • BBU baseband unit
  • RSU radio frequency unit
  • antenna module antenna module
  • FIG. 2 is a schematic diagram of a multi-band hardware architecture provided by an embodiment of the present application.
  • the multi-band hardware includes the upper media access control (MAC) layer (up MAC layer), MAC service data unit (MAC service data unit, MSDU) parsing and inverse parser, MAC control unit (MAC control unit, MCU), baseband unit (BBU), radio frequency unit (RFU), and antenna module not shown in the figure.
  • MAC media access control
  • MCU up MAC layer
  • BBU baseband unit
  • RFID radio frequency unit
  • multi-band operation also shares the upper MAC layer, parsing and inverse parser, receiving or sending the MSDU processed by the upper MAC layer through the upper MAC layer, and then distributing the MSDU to each frequency band through the parsing and inverse parser on.
  • Each frequency band has an independent MCU unit, and the MCU main unit is used to encapsulate the MSDU into an MPDU, that is, add a MAC header before the MSDU.
  • mainstream WiFi multi-band operation forms an independent BSS on each frequency band, and each BSS independently manages different sites without interfering with each other.
  • 802.11ad on high frequency 60GHz introduces FST, FST can include non-transparent FST and transparent FST.
  • the main difference between non-transparent FST and transparent FST is that the former site uses different MAC addresses in different frequency bands, while the latter site uses the same MAC address in different frequency bands.
  • the FST technology can transfer all services or certain types of services of a site from one frequency band to another frequency band for transmission, where the services are distinguished by service type (traffic identifier, TID).
  • FST conversations can occur in one frequency band, can also be switched from one channel in the same frequency band to another channel, or can occur simultaneously in multiple frequency bands and/or multiple channels.
  • site when the site’s business is transferred from one frequency band to another frequency band for transmission, only one of the frequency bands can be used for transmission at a time, and the simultaneous use of multiple frequency bands to transmit the same type of business to a site is not considered, which affects communication effectiveness.
  • the embodiments of the present application provide the following solutions.
  • FIG. 3 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • the communication system may include an access point (access point, AP) and multiple stations (station, STA).
  • the embodiments of the present application may be applicable to data communication between an AP and one or more STAs, and are also applicable to data communication between AP and AP, or data communication between STA and STA.
  • the AP can be used as the first device mentioned in this application or the second device mentioned in this application.
  • the STA can be used as the first device mentioned in this application or the second device mentioned in this application.
  • the AP can perform uplink and downlink transmissions with different STAs on different time-frequency resources.
  • AP can use different modes for uplink and downlink transmission, such as OFDMA single-user multiple-input multiple-output (SU-MIMO) mode, or OFDMA multi-user multiple-input multiple-output (multi-user multiple-output) mode. input multiple-output, MU-MIMO).
  • SU-MIMO single-user multiple-input multiple-output
  • multi-user multiple-input multiple-output multi-user multiple-output
  • input multiple-output MU-MIMO
  • AP can be the access point for mobile users to enter the wired network. It is mainly deployed in homes, buildings and campuses. The typical coverage radius is from tens of meters to hundreds of meters. Of course, it can also be deployed outdoors.
  • AP is equivalent to a bridge connecting wired and wireless networks, and its main function is to connect various wireless network clients together, and then connect the wireless network to the Ethernet.
  • the AP may be a terminal device or a network device with a WiFi chip.
  • the AP can be a device that supports the 802.11ax standard.
  • the AP can also be a device that supports multiple WLAN standards such as 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.
  • the STA can be a wireless communication chip, a wireless sensor, or a wireless communication terminal.
  • a wireless communication terminal For example, mobile phones that support WiFi communication functions, tablets that support WiFi communication functions, set-top boxes that support WiFi communication functions, smart TVs that support WiFi communication functions, smart wearable devices that support WiFi communication functions, and vehicle-mounted communication devices that support WiFi communication functions And a computer that supports WiFi communication.
  • the STA may support the 802.11ax standard.
  • STA can also support multiple WLAN standards such as 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.
  • FIG. 4 is a schematic structural diagram of an AP and STA provided by an embodiment of the present application. Since the 802.11 standard only focuses on the 802.11 PHY and MAC parts, only the PHY and MAC parts of the AP and STA are shown in the figure.
  • the AP shown in the figure is a multiple antenna structure, and the STA is a single antenna structure. In actual scenarios, AP and STA may have a multi-antenna structure, and may be devices with more than two antennas.
  • FIG. 5 is a schematic structural diagram of another AP and STA provided in an embodiment of the present application. The internal structure of AP and STA are the same.
  • TCP transmission control protocol
  • UDP user datagram protocol
  • IP Internet protocol
  • MAC logical link control
  • PHY baseband radio frequency and antenna, among which multiple antennas can be configured.
  • FIG. 6 is a schematic flowchart of a multi-link communication method provided by an embodiment of the present application.
  • the steps in the embodiment of the present application at least include:
  • block acknowledgement (BA) transmission is a mechanism introduced by the IEEE 802.11e standard, which allows the first device to send multiple data packets without receiving an acknowledgement frame, and then the first device sends one Block acknowledgement request frame (BAR), after receiving the BAR, the second device needs to feed back a BA to confirm a series of data frames sent by the first device. Since the second device puts the confirmation of multiple data packets in one BA frame for transmission, the transmission time of the confirmation frame can be reduced and the channel utilization rate can be improved.
  • the first device and the second device need to establish a multi-link BA session through the BA establishment process before sending the data packet.
  • the process of establishing a multi-link BA session is as follows:
  • the first device sends a block confirmation communication mechanism (add block acknowledgement, ADDBA) request frame to the second device, and the second device receives the ADDBA request frame sent by the first device.
  • a block confirmation communication mechanism add block acknowledgement, ADDBA
  • the ADDBA request frame includes one or more first buffer size (buffer size) fields and second buffer size (buffer size) fields, and the first buffer size field and the second buffer size field are used to provide the The second device negotiates the reference value of the corresponding buffer size field value.
  • the first device may include a multi-link entity and multiple links
  • the second device may also include a multi-link entity and multiple links
  • multiple links of the first device and multiple links of the second device Correspondingly, each link may include a low MAC layer and a physical PHY layer.
  • FIG. 7 is a schematic diagram of an ADDBA request frame provided by an embodiment of the present application.
  • the ADDBA request frame may include a block confirmation function field, a block confirmation parameter set field, and a block confirmation start sequence number control field.
  • the second device needs to feed back the confirmation frame Ack after receiving the ADDBA request frame
  • the first device also needs to feed back the confirmation frame Ack after receiving the ADDBA response frame.
  • the confirmation frame Ack in this embodiment of the application is not shown in FIG. 6 reflect.
  • the ADDBA request frame may include a block confirmation function field, and the block confirmation function field of the ADDBA request frame may add a multilink block confirmation session related function, and the block confirmation function field includes a function for indicating a multilink block confirmation session. Function type information.
  • the information in the ADDBA request frame indicates that the multi-link block confirmation session is a multi-link block confirmation request.
  • FIG. 8 is a schematic diagram of a block confirmation function field provided by an embodiment of the present application.
  • the block confirmation function field may include field values from 0 to 255.
  • a field value of 0 indicates a function requested by ADDBA
  • a field value of 1 indicates a function of an ADDBA response
  • a field value of 2 indicates a BA session deletion
  • the block confirmation function field also includes 3-127, 131, and 134-255 field values. These field values are reserved field values. The reserved field value can be used to indicate the function type of the multilink block confirmation session, such as multilink block confirmation. Request, multi-link block confirmation response, multi-link block confirmation dialogue teardown, etc.
  • the ADDBA request frame may include one or more first block confirmation start sequence fields, and may also include a second block confirmation start sequence field.
  • the ADDBA request frame includes a block confirmation start sequence number control field, the block confirmation start sequence number control field includes a 4-bit fragmentation field and a 12-bit start sequence number field, and the ADDBA request frame may also include multiple Link element.
  • Multiple first block confirmation start sequence control fields can be carried in the block confirmation start sequence number control field, and the second block confirmation start sequence field can be carried in the multilink element.
  • multiple first block confirmation start sequence control fields may be carried in the multilink element, and the second block confirmation start sequence field may be carried in the block confirmation start sequence number control field.
  • the carrying positions of the multiple first block confirmation start sequence fields and the second block confirmation start sequence fields are not limited.
  • the first block confirmation start sequence number control field is used to indicate the first initial sequence number of the first scoreboard of the link of the second device, and can also be used to indicate the second
  • the first initial serial number of the initial serial number of the first receiving window of the device, and the type of the first initial serial number is the local serial number.
  • the first receiving window and the first scoreboard are maintained by the lower MAC layer of the second device, and the first initial sequence number is used to set the initial value of the first receiving window WinStartB, which is described in detail below.
  • the second block confirmation start sequence number control field is used to indicate the second initial sequence number of the start sequence number of the second scoreboard of the multilink entity of the second device, and can also be used to indicate the The second initial sequence number of the initial sequence number of the second receiving window of the second device, and the type of the second initial sequence number is a global sequence number.
  • the second receiving window and the second scoreboard are maintained by the high MAC layer of the second device, and the second initial sequence number is used to set the initial value of the second receiving window WinStartB, which will be described in detail below.
  • the ADDBA request frame may include a block confirmation parameter set field, and the block confirmation parameter set field includes the second buffer size field.
  • FIG. 9 is a schematic diagram of a block confirmation parameter set field provided by an embodiment of the present application.
  • the block confirmation parameter set field can include 1-bit A-MSDU support, 2-bit block confirmation strategy, 3-bit service type and 10-bit buffer size.
  • the 10-bit buffer size field can be used to indicate the size of the global buffer space. , The size of each field is not limited.
  • FIG. 10 is a schematic diagram of a multi-link element provided by an embodiment of the present application.
  • the multi-link element includes an element number, a length field, and an indication field.
  • the indication field may include the following two modes: In the first mode, the indication field may include a link bitmap field and at least one first buffer size field. Wherein, the number of the first buffer size field is equal to the number of bits with a value of "1" in the link bitmap, and the link bitmap can indicate which links participate in the multilink BA session.
  • the bitmap can represent 1001.
  • the indication field may include a link number field, multiple link identification number fields, and at least one first buffer size field, where the number of link identification number fields and the number of first buffer size fields The same as the value of the link number field, the multiple link identification number field is used to indicate which links participate in the establishment of the multi-link BA session.
  • the multilink element also includes a plurality of first block confirmation start sequence control fields, and the number of first block confirmation start sequence control fields is equal to the number of links participating in the multilink BA dialogue.
  • the above indication field is not limited to being carried in a multi-link element, and can also be carried in an existing field or element in the ADDBA request frame, such as a multi-band (Multi-Band) element or an ADDBA extension element.
  • Multi-Band multi-band
  • first buffer size field and the second buffer size field may also be carried by other fields.
  • first buffer size field may also be indicated by the block confirmation parameter set field
  • second buffer size field may also be It can be indicated by the multi-link element, and the two can also be indicated by other means, which is not limited here.
  • the second device may send an acknowledgement frame Ack for responding to the ADDBA request frame to the first device, and then the first device receives the ADDBA request frame sent by the second device.
  • the confirmation frame Ack may be sent after the second device receives the ADDBA request frame sent by the first device.
  • the second device sends an ADDBA response frame to the first device, and the first device receives an ADDBA response frame sent by the second device, where the ADDBA response frame includes the confirmation value of the one or more first buffer size fields and The confirmation value of the second buffer size, the first buffer size field and the second buffer size field are used as the confirmation value for the establishment of the block confirmation dialog.
  • the ADDBA request frame and the ADDBA response frame are used to establish a multi-link block confirmation dialogue between the multiple links of the first device and the multiple links of the second device.
  • FIG. 11 is a schematic structural diagram of a transmitting end of a first device according to an embodiment of the present application.
  • the first device includes a high MAC layer and multiple links (such as link 1 and link 2), and the link includes a low MAC layer and a PHY layer.
  • the high MAC layer includes a global buffer space, in which a buffer queue can be maintained, and a global sequence number is assigned to each data packet.
  • the lower MAC layer can optionally include a local buffer space or not, and allocate a local sequence number for each data packet.
  • FIG. 12 is a schematic structural diagram of a second device provided by an embodiment of the present application.
  • the receiving end of the second device includes a high MAC layer and multiple links (such as link 1 and link 2), and the link includes a low MAC layer and a PHY layer.
  • the lower MAC layer may include a local buffer space and a first scoreboard, and the first scoreboard may be used to respond to the confirmation of the same type of data packet received on this link.
  • the high MAC layer includes a global buffer space and a second scoreboard. A reordering buffer queue can be maintained in the global buffer space. The second scoreboard can be used to respond to the same type of data packets received by the multi-link entity Confirmation.
  • the first buffer size field is used for the size of the first scoreboard for link negotiation.
  • the first buffer size field can also be used for link negotiation the size of the local buffer space. If there are n links, n first buffer size fields are required.
  • there is a first buffer size field that is, the size of the first scoreboard negotiated for each link is the same, and the size of the optional local buffer space is the same.
  • the second buffer size field is used to negotiate the size of the second scoreboard and the global buffer space for the multi-link entities. Each multi-link entity can only negotiate a second buffer size field, corresponding to the second shared high MAC layer. Scoreboard and global buffer space.
  • the size of the first buffer size field can be 64, 128, or 256. If the first device has 3 links, the first buffer size A, the first buffer size B, and the first buffer size C can be increased.
  • the size of the second buffer size can be 1024, 2048, 4096, and so on. Generally, the size of the second buffer size field is larger than the size of the first buffer size field, but there are exceptions.
  • a multi-link entity refers to an entity that includes one or more links, and the one or more links share a MAC service access point (SAP).
  • a link refers to a station with transmitting and receiving functions, such as a PHY and a MAC (such as a low MAC).
  • FIG. 13 is a schematic diagram of an ADDBA response frame provided by an embodiment of the present application.
  • the ADDBA response frame may include a block confirmation function field, a block confirmation parameter set field, and so on.
  • the block confirmation function field of the ADDBA response frame can be added to the multi-link block confirmation session related functions
  • the ADDBA response frame includes the block confirmation function field
  • the block confirmation function field includes a multi-link block confirmation session Function type information.
  • the information in the ADDBA response frame indicates that the multilink block confirmation session is a multilink block confirmation response.
  • the block confirmation function field may include field values from 0 to 255.
  • a field value of 0 indicates a function of an ADDBA request
  • a field value of 1 indicates a function of an ADDBA response
  • a field value of 2 indicates a BA session deletion and so on.
  • the block confirmation function field also includes 3-127, 131, and 134-255 field values. These field values are reserved field values.
  • the reserved field value can be used to indicate the function type of the multi-link block confirmation session.
  • the function type includes multi-link Road block confirmation request, multi-link block confirmation response, multi-link block confirmation dialog removal, etc.
  • the ADDBA response frame may include a second block confirmation parameter set field, and the second block confirmation parameter set field includes the second buffer size field.
  • FIG. 9 is a schematic diagram of a block confirmation parameter set field provided by an embodiment of the present application.
  • the block confirmation parameter set field may include a 1-bit A-MSDU, a 2-bit block confirmation strategy, a 3-bit service type, and a 10-bit buffer size.
  • the 10-bit buffer size field may be used to indicate the size of the global buffer space. The size of each field is not limited.
  • a multi-link (Multi-link) element may be added to the ADDBA response frame, and the ADDBA response frame includes the multi-link element.
  • FIG. 10 is a schematic diagram of a multi-link element provided by an embodiment of the present application.
  • the multi-link element includes an element number, a length field, and an indication field.
  • the indication field may include a link bitmap field and at least one first buffer size field. Wherein, the number of the first buffer size field is equal to the number of bits with a value of "1" in the link bitmap, and the link bitmap can indicate which links participate in the multilink BA session.
  • the bitmap can represent 1001.
  • the indication field may include a link number field, a multiple link identification number field, and at least one first buffer size field. Wherein, the number of link identification number fields and the number of first buffer size fields are the same as the value of the link number field, and the link identification number field is used to indicate which links participate in the establishment of a multi-link BA session.
  • the multilink element also includes multiple block confirmation start sequence control fields, and the number of block confirmation start sequence control fields is equal to the number of links participating in the multilink BA dialogue.
  • the above indication field is not limited to being carried in a multi-link element, and can also be carried in an existing field or element in an ADDBA request frame or response frame, such as a multi-band (Multi-Band) element, or an ADDBA extension element.
  • Multi-Band multi-band
  • first buffer size field and the second buffer size field may also be carried by other fields.
  • first buffer size field may also be indicated by the block confirmation parameter set field
  • second buffer size field may also be The multi-link element can be used to indicate, and the two can also be indicated in other ways, which are not limited here.
  • the first device may return to the second device an acknowledgement frame Ack for responding to the ADDBA response frame, and then the second device receives the ADDBA response frame sent by the first device.
  • the confirmation frame Ack may be used to indicate whether the first device receives the ADDBA response frame sent by the second device.
  • steps S601 and S602 After steps S601 and S602, a multi-link block confirmation dialogue between the multiple links of the first device and the multiple links of the second device is established, and then the following operations are performed:
  • the first device sends a data packet to the second device, and the second device receives a data frame containing the data packet sent by the first device.
  • the data packet may be a MAC service data unit (MSDU), or An aggregated MAC service data unit (aggregate MAC service data unit, A-MSDU) in which multiple data packet MSDUs are aggregated can also send management frames and control frames including MAC management protocol data unit (MMPDU).
  • the data packet may be a quality of service (QoS) data packet.
  • QoS quality of service
  • the high MAC layer of the first device maintains a global buffer space, and the high MAC layer respectively assigns a global sequence number to the received data packet passed down by the upper layer.
  • Multiple data packets with the same ⁇ receiving address, service type> can be divided into the same group of data packets, and the same group of data packets can share a 12-bit sequence number space, ranging from 0 to 4095.
  • there are other methods for allocating global serial numbers such as dividing data packets sent to the same address into the same group of data packets, and the same group of data packets share a serial number space, which is not limited by the present invention.
  • the global sequence number increases by 1. For example, if there are 3 data packets in the global buffer space, the 3 data packets are the same group of data packets, the first data packet is assigned a global serial number 1, the second data packet is assigned a global serial number 2, and the third data The package is assigned a global sequence number 3. Wherein, the global sequence number is an identifier assigned to the data packet by the multilink entity.
  • the lower MAC layer of the link of the first device can take out multiple data packets from the global buffer space of the higher MAC layer and allocate a local sequence number.
  • multiple data packets with the same ⁇ receiving address, service type> on the link can be divided into the same group of data packets, and the same group of data packets can share a 12-bit sequence number space, ranging from 0 to 4095.
  • there are other methods for allocating local serial numbers such as dividing data packets sent to the same address into the same group of data packets, and the same group of data packets share a serial number space, which is not limited by the present invention.
  • the local sequence number increases by 1.
  • the three data packets are the same group of data packets.
  • the numbers in the brackets are the local serial numbers, and the numbers outside the brackets are the global serial numbers.
  • the lower MAC layer of each link assigns a local sequence number to each of the three data packets, and the local sequence number increases sequentially.
  • the local sequence number is an identifier assigned to the data packet by the link that sends the data packet among the multiple links.
  • FIG. 14 is a schematic diagram of a MAC header provided by an embodiment of the present application.
  • the MAC header can include frame control field, address 1 field (receiving address), address 2 field (sending address), and address 3.
  • the 2-byte sequence control field may include a 12-bit sequence number and a 4-bit fragment number.
  • One of the local sequence number and the global sequence number can be carried by the sequence control field, and the other can be carried by other fields, for example, in the HT control field, or an additional sequence control field is added to the frame carrier.
  • the data packet can be sent to the second device.
  • the first device can maintain multiple first sending windows and one second sending window according to the ADDBA request frame and the ADDBA response frame.
  • the multiple first sending windows correspond to multiple links of the first device, and the second sending window corresponds to a multiple link entity of the first device.
  • each link maintains a first sending window, one of the first sending windows corresponds to one of the links, and the starting sequence number of the first sending window is WinStartO1, and the ending sequence number is WinEndO1, the window size is WinSizeO1, where the WinSizeO1 is equal to the confirmation value of the first buffer size field corresponding to the link.
  • the high MAC layer also maintains a second sending window.
  • the start sequence number of the second sending window is WinStartO2
  • the end sequence number is WinEndO2
  • the window size is WinSizeO2, where WinSizeO2 is equal to the ADDBA request frame and the ADDBA response.
  • the confirmation value of the second buffer size field negotiated by the frame.
  • the PHY layer of each link transfers the data packet to the lower MAC layer of the link.
  • the low MAC layer of each link can obtain the local sequence number from the MAC header of each data packet, and maintain a first scoreboard based on the local sequence number.
  • the first scoreboard is used to respond to the received data from this link. Confirmation of packets of the same type. Through the first scoreboard, you can count whether each link receives the data packet correctly. If the data packet is received correctly, the data packet can be counted as 1; if the data packet is not received, the data packet can be counted as 0 .
  • the ADDBA request frame includes one or more first block confirmation start sequence number control fields
  • the first block confirmation start sequence number control field includes a first initial sequence number
  • the first initial sequence number is used to indicate all The initial value of the first receiving window (optional) of the second device and the initial serial number of the first scoreboard
  • the type of the first initial serial number is a local serial number.
  • the link can confirm the data packets received on the link in turn according to the first initial sequence number, and finally form a block confirmation bitmap of the received data packet confirmed by the second device, which is included in The partial block confirmation frame is returned to the first device.
  • the partial block confirmation frame is used to respond to the confirmation of multiple data packets received on the link.
  • the partial block confirmation frame is an immediate response to the data packets received on the link, or it can be The received response to the BAR frame used to index the local sequence number.
  • the size of the block confirmation bitmap in the partial block confirmation frame can be negotiated through the first buffer size field in the ADDBA request frame and the ADDBA response frame. For the same first buffer size field, there may be block confirmation bitmaps of different lengths , See 802.11ax protocol for details.
  • the second device can maintain multiple first scoreboards, and the multiple first scoreboards correspond to multiple links, and the start sequence number of one first scoreboard is WinStartR1, and the end sequence number is WinEndR1;
  • the initial value of WinStartR1 is the first initial sequence number of the first block in the ADDBA request frame to confirm the start sequence number control field, and the size of the first scoreboard WinSizeR1 is equal to the value of the first buffer size field corresponding to the corresponding link
  • the confirmation value and the maximum length block confirm the smaller value in the bitmap.
  • the positions of WinStartR1 and WinEndR1 will move with the received data packet. For details, please refer to the 802.11-2016 protocol, which will not be repeated here.
  • WinStartR1 determines the start sequence number of the bitmap of the partial block confirmation frame (such as compressed block confirmation frame or multi-site block confirmation frame) returned by the second device.
  • the second device may also maintain multiple first receiving windows according to the ADDBA request frame and the ADDBA response frame.
  • the first receiving window is used to sort the received data packets and then submit them to the high MAC layer.
  • the multiple first receiving windows correspond to the multiple links of the second device, and further, one of the first receiving windows corresponds to one of the multiple links, and the first A receiving window start sequence number is WinStartB1, end sequence number is WinEndB1, and window size is WinSizeB1.
  • the initial value of WinStartB1 is the first initial sequence number of the first block confirmation start sequence number control field in the ADDBA request frame
  • the WinSizeB1 is equal to the confirmation value and the maximum value of the first buffer size field corresponding to the link.
  • the length of the block confirms the smaller value in the bitmap.
  • the positions of WinStartB1 and WinEndB1 will move with the received data packet.
  • the second device does not need to maintain multiple first receiving windows according to the ADDBA request frame and the ADDBA response frame.
  • the lower MAC layer of each link of the second device may sequentially pass multiple data packets to the higher MAC layer in the order of the local sequence numbers of the multiple data packets.
  • each chain The low MAC layer of the road directly passes the received multiple data packets to the high MAC layer.
  • the high MAC layer obtains the global sequence number from each data packet, and maintains a second scoreboard based on the global sequence number.
  • the second scoreboard is used to respond to data packets of the same type received by the multilink entity. confirm. Through the second scoreboard, it is possible to count whether the multi-link entity correctly receives the data packet. If the data packet is received correctly, the data packet can be counted as 1; if the data packet is not received, the data packet can be counted as 0.
  • the ADDBA request frame includes a second block confirmation start sequence number control field, and the second block confirmation start sequence number control field includes a second initial sequence number, and the second initial sequence number is used to indicate the second device's first sequence number. 2.
  • the initial value of the initial serial number of the receiving window and the second scoreboard, and the type of the second initial serial number is a global serial number.
  • the high MAC layer can confirm multiple data packets in sequence according to the second initial sequence number, and finally form a block confirmation bitmap of the received data packet confirmed by the second device, and include it in the global block confirmation frame Return to the first device.
  • the global block confirmation frame is the response of the block confirmation request frame that is used to index the global sequence number received by the multilink entity.
  • the size of the block confirmation bitmap in the global block confirmation frame is determined by the ADDBA request frame and the ADDBA response frame. For the negotiated second buffer size field, for the same second buffer size field, there may be block confirmation bitmaps of different lengths.
  • the global block acknowledgment frame is an acknowledgment that the multilink entity responds to multiple received data packets.
  • the second device can maintain multiple second scoreboards, the second scoreboard corresponds to the multi-link entity, the start sequence number of the second scoreboard is WinStartR2, and the end sequence number is WinEndR2 ,
  • the window size is WinSizeR2, where the initial value of WinStartR2 is the second initial sequence number of the second block confirmation start sequence number control field in the ADDBA request frame, and the WinSizeR2 is equal to the confirmation value of the second buffer size field and The block of maximum length confirms the smaller value in the bitmap.
  • the positions of WinStartR2 and WinEndR2 will move with the received data packets. For details, please refer to the 802.11-2016 protocol, which will not be repeated here.
  • WinStartR2 determines the start sequence number of the bitmap of the global block confirmation frame (such as compressed block confirmation frame or multi-site block confirmation frame) returned by the second device.
  • the second device may also maintain a second receiving window according to the ADDBA request frame and the ADDBA response frame, and the second receiving window may be used for data packets received by the multilink entity in the global buffer space. Sort according to the global sequence number, and transfer the data packets to the upper layer of the MAC layer of the second device in the order of the global sequence number.
  • the second receiving window corresponds to the link entity of the second device. Further, the start sequence number of the second receiving window is WinStartB2, the end sequence number is WinEndB2, and the window size is WinSizeB2, where the initial value of WinStartB2 is the second block confirmation start sequence number control field in the ADDBA request frame.
  • the initial sequence number, the WinSizeB2 is equal to the smaller value of the confirmation value of the second buffer size field and the maximum length block confirmation bitmap.
  • the positions of WinStartB2 and WinEndB2 can be moved with the received data packets. For details, please refer to the 802.11-2016 protocol, which will not be repeated here.
  • step S604 The first device sends a block confirmation request frame or a multi-user block confirmation request trigger frame to the second device.
  • the second device receives the block confirmation request frame or the multi-user block confirmation request trigger frame sent by the first device.
  • This step is optional and depends on the confirmation strategy of the sent data packet. If the strategy is block confirmation, step S604 is required. If it is a normal confirmation or implicit block request confirmation request strategy, step S604 is not required. At this time, the index of the data packet is immediately fed back.
  • FIG. 15 is a schematic diagram of a block confirmation request frame or a multi-user block confirmation request trigger frame provided by an embodiment of the present application.
  • the block confirmation request frame or the multi-user block confirmation request trigger frame may include a start sequence number control field, the start sequence number control field includes a start sequence number, the block confirmation request frame or the multi-user block confirmation request trigger
  • the frame also includes a BAR control field.
  • the BAR control field includes first indication information. The first indication information is used for the type of the starting sequence number, and the type of the starting sequence number includes a local sequence number or a global sequence number. .
  • Block confirmation request frame (for example, variants of the block confirmation request frame, including multi-service type BAR, extended compression BAR, compressed BAR and multicast BAR or basic BAR, etc.) or multi-user block confirmation request trigger frame including global block confirmation request frame and Partial block confirmation request frame.
  • the block confirmation request frame may be determined as a global block confirmation request frame or a local block confirmation request frame according to the BAR type indicated by the first indication information.
  • Block confirmation request frame (for example, variants of the block confirmation request frame, including multi-service type BAR, extended compression BAR, compressed BAR and multicast BAR or basic BAR, etc.) or multi-user block confirmation request trigger frame in the start sequence number control
  • the starting sequence number in the field is the starting local sequence number or the starting global sequence number indicated by the first indication information.
  • the second device sends a confirmation message in response to the data packet to the first device, and the first device receives a confirmation message in response to the data packet returned by the second device, where the confirmation message includes a block confirmation frame
  • the block confirmation frame includes a global block confirmation frame and a local block confirmation frame.
  • the block confirmation frame may be a compressed block confirmation frame or a multi-site block confirmation frame.
  • FIG. 16 is a schematic diagram of a block confirmation frame provided by an embodiment of the present application.
  • the block confirmation frame may include a start sequence number control field, and the start sequence number control field includes a start sequence number and a block.
  • Confirmation bitmap the block confirmation bitmap is used to indicate the reception of the data packet received by the second device
  • the block confirmation frame (including variants of the block confirmation frame, such as basic block confirmation, compression Block confirmation, multi-site block confirmation, and multi-service type block confirmation, etc.) may also include a BA control field.
  • the BA control field includes second indication information, and the second indication information is used to indicate the start of the block confirmation frame.
  • Block confirmation frames (for example, variants of block confirmation frames, including basic block confirmation, compressed block confirmation, multi-site block confirmation, and multi-service type block confirmation, etc.) include global block confirmation frames and local block confirmation frames.
  • the block confirmation frame may be determined as a global block confirmation frame or a partial block confirmation frame according to the BA type indicated by the second indication information.
  • the block confirmation frame may include a block confirmation bitmap, and if the sequence corresponding to the block confirmation bitmap is the local sequence number, then the sequence number corresponding to the first bit in the block confirmation bitmap Is the WinStartR1 or the local start sequence number in the start sequence control field; if the sequence corresponding to the block confirmation bitmap is the global sequence number, the first bit in the block confirmation bitmap The corresponding sequence number is the WinStartR2 or the global start sequence number in the start sequence control field.
  • the first device and the second device allocate a local buffer space for each of the multiple links and a global buffer space for the high MAC layer .
  • a multi-link block confirmation dialogue is established.
  • the MAC of the data packet sent by the first device includes the local serial number and the global serial number, so that the first device can send the same type of data packet to the second device over multiple links, thereby improving the efficiency of data communication .
  • FIG. 17 is a schematic flowchart of a data frame transmission method provided by an embodiment of the present application.
  • the steps in the embodiment of this application at least include:
  • the first device sends a message frame to the second device, and the second device receives the message frame sent by the first device, where the message frame includes first indication information, and the first indication information is used to indicate the multiple links
  • the main link in. Including the following two optional methods:
  • the first indication information is a special element
  • the first device may send a message frame to the second device through the main link
  • the message frame may carry a special element (for example, related to multi-link information).
  • the special element is only carried in the message frame sent by the main link, and the special element is used to indicate that the link for transmitting the message frame is the main link.
  • the message frame may be a beacon frame in the management frame.
  • the first indication information is a link sequence number
  • the first device may send a message frame to the second device through a non-primary link
  • the message frame may carry a reduced neighbor report (reduced neighbor report).
  • reduced neighbor report reduced neighbor report
  • the reduced neighbor report element or multi-band element includes a link sequence number
  • the link sequence number is used to indicate the main link of the multiple links.
  • the first device sends second indication information to the second device through the main link, or negotiates a target wake up time (TWT) with the second device through the main link.
  • TWT target wake up time
  • the second indication information indicates the working state or sleep state of the multiple links.
  • TWT negotiation is used for the first device and the second device to negotiate one or more service windows, and work within the service window, and sleep outside the service window, thereby saving power.
  • the second indication information may be carried in an operating mode indication field (OMI) or an operating mode notification frame (operating mode notification) of a high throughput (HT) control field in the MAC header.
  • the second indication information may be a bitmap. For example, if the nth bit is a value of 1, it means that the nth link is about to be in a dormant state or closed state, and if the nth bit is set to a value of 0, it means that the nth link is about to be In working condition.
  • the second indication information may be multiple link sequence numbers. If the second indication information includes link sequence number 1, the link corresponding to link sequence number 1 is in the dormant state or closed state, and vice versa.
  • FIG. 18 is a schematic diagram of a TWT element used for TWT negotiation according to an embodiment of the present application.
  • the TWT element includes element number, length, control, and TWT parameter information fields.
  • the control field includes fields such as NDP paging indication, responder power saving mode, negotiation type, and TWT information frame disable.
  • the negotiation type may include single user TWT type and broadcast TWT type.
  • FIG. 19 is a schematic diagram of a single-user TWT type provided by an embodiment of the present application.
  • the negotiation type indicates the single-user TWT type
  • the information fields of the single-user TWT parameters include request type, target wake-up time, TWT group allocation, minimum TWT wake-up time, TWT wake-up time decimal, TWT channel, NDP (Null data packet, empty) Data packet) paging and so on.
  • Figure 20 is a schematic diagram of a broadcast TWT type provided by an embodiment of the present application.
  • the information fields of the broadcast TWT parameter include request type, target wake-up time, TWT group allocation, The minimum TWT wake-up time, the decimal of the TWT wake-up time, the TWT channel, and NDP (Null Data Packet) paging.
  • a multi-link indicator can be added to the control field of the TWT element.
  • the multi-link indicator is used to indicate that the broadcast TWT parameter information or the single-user TWT parameter information can be applied to another link that is different from the link that transmits the TWT element.
  • On the link. Which link is applied to can be indicated in the following ways:
  • the first alternative is to add an operating class field to the information field of the single-user TWT parameter, and combine the operating class field and the TWT channel field to indicate which link of the multiple links the TWT element is applied to. .
  • the second optional method is to add one or more link sequence numbers to the information field of the single-user TWT parameter and the information field of the broadcast TWT parameter.
  • the link sequence number is used to indicate that the TWT element is applied to multiple links On which link.
  • the link sequence number bitmap is used to indicate which link of the multiple links the TWT element is applied to. For example, if the link sequence number bitmap is 0100, setting the second bit to 1 may indicate that the TWT element can be applied to the second link.
  • an operating class field and a TWT channel field are added to the information field of the broadcast TWT parameter to indicate which link of the multiple links the TWT element is applied to.
  • one or more link sequence numbers are added to the information field of the broadcast TWT parameter, and the link sequence number is used to indicate which link of the multiple links the TWT element is applied to.
  • the link sequence number bitmap is used to indicate which link of the multiple links the TWT element is applied to. For example, if the link sequence number bitmap is 0100, setting the second bit to 1 may indicate that the TWT element can be applied to the second link.
  • the first device indicates the main link of the multiple links to the second device, and indicates the working state or sleep state of the multiple links through the main link, or performs the operation through the main link. TWT negotiation, thereby saving power.
  • FIG. 21 is a schematic structural diagram of a first communication device provided by an embodiment of the present application.
  • the first communication device includes a sending module 2101, a receiving module 2102, and a processing module 2103.
  • the detailed description of each module is as follows .
  • the sending module 2101 is configured to send an ADDBA request frame to a second device, where the ADDBA request frame includes at least one reference value of a first buffer size field and a reference value of a second buffer size field; the second device and the first The device is a multi-link entity containing one or more links;
  • the receiving module 2102 is configured to receive an ADDBA response frame sent by the second device, where the ADDBA response frame includes at least one confirmation value of the first buffer size field and the confirmation value of the second buffer size field;
  • the processing module 2103 is configured to establish a multi-link block confirmation dialogue between the multiple links of the first device and the multiple links of the second device according to the ADDBA request frame and the ADDBA response frame ;
  • one of the first buffer size fields is used to indicate the size of a local buffer space corresponding to one of the multiple links of the first device and the second device
  • the second buffer size field Used to indicate the size of a global buffer space maintained by the first device and the second device.
  • the processing module 2103 is configured to maintain multiple first sending windows and one second sending window according to the ADDBA request frame and the ADDBA response frame, where the multiple first sending windows and the The multiple links of the first device correspond, and the second sending window corresponds to the multiple link entity of the first device.
  • one of the first sending windows corresponds to one of the multiple links, one of the first sending windows has a start sequence number of WinStartO1, an end sequence number of WinEndO1, and a window size of WinSizeO1, where the WinSizeO1 Equal to the confirmation value of the first buffer size field corresponding to the link;
  • the start sequence number of the second sending window is WinStartO2
  • the end sequence number is WinEndO2
  • the window size is WinSizeO2, where WinSizeO2 is equal to the confirmation value of the second buffer size field negotiated through the ADDBA request frame and the ADDBA response frame .
  • the processing module is configured to maintain multiple first sending windows and one second sending window according to the ADDBA request frame and the ADDBA response frame, wherein the multiple first sending windows and the multiple of the first device Corresponding to two links, and the second sending window corresponds to the multi-link entity of the first device.
  • one of the first sending windows corresponds to one of the multiple links, one of the first sending windows has a start sequence number of WinStartO1, an end sequence number of WinEndO1, and a window size of WinSizeO1, where the WinSizeO1
  • the confirmation value equal to the first buffer size corresponding to the link;
  • the start sequence number of the second sending window is WinStartO2
  • the end sequence number is WinEndO2
  • the window size is WinSizeO2 where WinSizeO2 is equal to the confirmation value of the second buffer size negotiated through the ADDBA request frame and the ADDBA response frame.
  • the ADDBA request frame includes a first block confirmation start sequence number control field and a second block confirmation start sequence number control field;
  • the first block confirmation start sequence number control field is used to indicate the first initial sequence number of the start sequence number of the first scoreboard of the link of the second device, and the type of the first initial sequence number Is the local serial number;
  • the second block confirmation start sequence number control field is used to indicate the second initial sequence number of the start sequence number of the second scoreboard of the multilink entity of the second device, and the second initial sequence number
  • the type is the global serial number.
  • the ADDBA request frame includes at least one of a link bitmap field and a reference value of the at least one first buffer size field, or a link number field, a multiple link identification number field, and the at least one At least one of the reference values of a first buffer size field;
  • the ADDBA response frame includes at least one of a link bitmap field and an acknowledgement value of the at least one first buffer size field, or a link number field At least one of multiple link identification number fields and confirmation values of the at least one first buffer size field;
  • the ADDBA request frame includes a first block confirmation parameter set field, and the first block confirmation parameter set field includes a reference value of the second buffer size field;
  • the ADDBA response frame includes a second block confirmation parameter set field, and the second block confirmation parameter set field includes the confirmation value of the second buffer size field.
  • a sending module 2101 configured to send a data packet to the second device
  • a receiving module 2102 configured to receive a confirmation message replies from the second device in response to the data packet
  • the data packet includes a local sequence number and a global sequence number
  • the local sequence number is an identifier assigned to the data packet by the link that sends the data packet among the multiple links
  • the global sequence number The identifier assigned to the data packet for the multilink entity.
  • the sending module 2101 is further configured to send a block confirmation request frame or a multi-user block confirmation request trigger frame to the second device, where the block confirmation request frame or the multi-user block confirmation request trigger frame includes a start A sequence number control field, where the starting sequence number control field includes a starting sequence number;
  • the block confirmation request frame or the multi-user block confirmation request trigger frame further includes first indication information, where the first indication information is used to indicate the type of the starting sequence number, and the type of the starting sequence number includes Local serial number or global serial number.
  • the receiving module 2202 is also configured to receive a block confirmation frame sent by the second device, the block confirmation frame includes a start sequence number control field, and the start sequence number control field includes a start sequence number and a block confirmation Bitmap; the block confirmation bitmap is used to indicate the reception status of the data packet received by the second device;
  • the block confirmation frame further includes a block confirmation BA control field, the BA control field includes the second indication information, and the second indication information is used to indicate the type of the starting sequence number, and the starting sequence number
  • the type of is a local sequence number or a global sequence number, and the first bit in the block confirmation bitmap corresponds to the starting sequence number.
  • the sending module 2101 is configured to send a message frame to a second device, where the message frame includes first indication information, and the first indication information is used to indicate a main link among multiple links.
  • the sending module 2101 is configured to send second indication information to the second device through the main link, the second indication information indicating the working status or sleep state of multiple links, or to negotiate TWT with the second device through the main link.
  • the first indication information is a special element.
  • the first device can send a message frame to the second device through the main link.
  • the message frame can carry a special element.
  • the special element is only carried in the message frame sent by the main link. This special element is used to indicate that the link that transmits the message frame is the primary link.
  • the main link is indicated by a special element, so that other links are in a dormant state or closed state, thereby saving power.
  • the first indication information is the link sequence number.
  • the first device can send a message frame to the second device through a non-primary link.
  • the message frame can carry a reduced neighbor report element or a multi-band element, a reduced neighbor report element or a multi-band
  • the element includes a link sequence number, which is used to indicate the main link of multiple links.
  • an operation type field is added to the information field of the single-user TWT parameter and the information field of the broadcast TWT parameter, and the operation type field and the TWT channel field are combined to indicate which link of the multiple links the TWT element is applied to.
  • An indication value may be added to the broadcast TWT parameter information field, and the indication value is used to indicate which link of the multiple links the TWT element is applied to.
  • one or more link sequence numbers are added to the information field of the single-user TWT parameter and the information field of the broadcast TWT parameter.
  • the link sequence number is used to indicate which of the multiple links the TWT element is applied to. .
  • the link sequence number bitmap is used to indicate which link of the multiple links the TWT element is applied to.
  • each module can also refer to the corresponding description of the method embodiment shown in FIG. 6 and FIG. 17 to execute the method and function performed by the first device in the foregoing embodiment.
  • FIG. 22 is a schematic structural diagram of a second communication device provided by an embodiment of the present application.
  • the second communication device includes a receiving module 2201, a sending module 2202, and a processing module 2203.
  • the detailed description of each module is as follows .
  • the receiving module 2201 is configured to receive an ADDBA request frame sent by a first device, where the ADDBA request frame includes at least one reference value of a first buffer size field and a reference value of a second buffer size field; the first device and the second device
  • the device is a multi-link entity containing one or more links;
  • a sending module 2202 configured to send an ADDBA response frame to the first device, where the ADDBA response frame includes the confirmation value of the at least one first buffer size field and the confirmation value of the second buffer size field;
  • the processing module 2203 is configured to establish a multi-link block confirmation dialogue between the multiple links of the first device and the multiple links of the second device according to the ADDBA request frame and the ADDBA response frame ;
  • one of the first buffer size fields is used to indicate the size of a local buffer space corresponding to one of the multiple links of the first device and the second device
  • the second buffer size field Used to indicate the size of a global buffer space maintained by the first device and the second device.
  • the processing module 2203 is configured to maintain a receiving window according to the ADDBA request frame and the ADDBA response frame, where the receiving window corresponds to the link entity of the second device;
  • the start sequence number of the receiving window is WinStartB2
  • the end sequence number is WinEndB2
  • the window size is WinSizeB2 where WinSizeB2 is equal to the comparison between the confirmation value of the second buffer size field and the maximum length block confirmation bitmap. Small value.
  • the ADDBA request frame includes a first block confirmation start sequence number control field and a second block confirmation start sequence number control field;
  • the first block confirmation start sequence number control field is used to indicate the first initial sequence number of the start sequence number of the first scoreboard of the link of the second device, and the type of the first initial sequence number is Local serial number;
  • the second block confirmation start sequence number control field is used to indicate the second initial sequence number of the start sequence number of the second scoreboard of the multilink entity of the second device, and the second initial sequence number of the second initial sequence number.
  • the type is the global serial number.
  • the ADDBA request frame includes at least one of a link bitmap field and a reference value of the at least one first buffer size field, or a link number field, a multiple link identification number field, and the at least one At least one of the reference values of a first buffer size field;
  • the ADDBA response frame includes at least one of a link bitmap field and an acknowledgement value of the at least one first buffer size field, or a link number field, a plurality of link identification number fields, and the at least one first buffer size field. At least one of the confirmation values of a buffer size field;
  • the ADDBA request frame includes a first block confirmation parameter set field, and the first block confirmation parameter set field includes a reference value of the second buffer size field;
  • the ADDBA response frame includes a second block of confirmation parameter set field, and the second block of confirmation parameter set field includes the confirmation value of the second buffer size field.
  • the receiving module 2201 is further configured to receive a data packet sent by the first device;
  • the sending module 2202 is further configured to send a confirmation message for responding to the data packet to the first device;
  • the data packet includes a local sequence number and a global sequence number
  • the local sequence number is an identifier assigned to the data packet by the link that sends the data packet among the multiple links
  • the global sequence number The identifier assigned to the data packet for the multilink entity.
  • the receiving module 2201 is further configured to receive a block confirmation request frame or a multi-user block confirmation request trigger frame sent by the first device, where the block confirmation request frame or the multi-user block confirmation request trigger frame includes An initial sequence number control field, where the initial sequence number control field includes an initial sequence number;
  • the block confirmation request frame or the multi-user block confirmation request trigger frame further includes first indication information, the first indication information is used to indicate the type of the starting sequence number, and the type of the starting sequence number includes Local serial number or global serial number.
  • the processing module 2203 is configured to maintain multiple first scoreboards and one second scoreboard; the multiple first scoreboards correspond to the multiple links, and the second scoreboard is connected to all the links. Corresponding to the multi-link entities;
  • the start sequence number of one of the first scoreboards is WinStartR1, and the end sequence number is WinEndR1;
  • the scoreboard size WinSizeR1 is equal to the confirmation value of the first buffer size field corresponding to the corresponding link and the block confirmation of the maximum length The smaller value in the bitmap;
  • the start sequence number of the second scoreboard is WinStartR2
  • the end sequence number is WinEndR2
  • the scoreboard size is WinSizeR2
  • WinSizeR2 is equal to the confirmation value of the second buffer size field and the block confirmation bit of the maximum length The smaller value in the graph.
  • the confirmation message is a block confirmation frame
  • the block confirmation frame includes a start sequence number control field, and the start sequence number control field includes a start sequence number and a block confirmation bitmap; the block confirmation bitmap is used to indicate that the second device receives The reception of said data packet;
  • the block confirmation frame further includes a block confirmation BA control field, the BA control field includes the second indication information, and the second indication information is used to indicate the type of the starting sequence number, and the starting sequence number
  • the type of is a local sequence number or a global sequence number, and the first bit in the block confirmation bitmap corresponds to the starting sequence number.
  • the sequence number corresponding to the first bit in the block confirmation bitmap is the WinStartR1;
  • sequence corresponding to the block confirmation bitmap is the global sequence number
  • sequence number corresponding to the first bit in the block confirmation bitmap is the WinStartR2.
  • the receiving module 2101 is configured to receive a message frame sent by the first device, the message frame includes first indication information, and the first indication information is used to indicate the main link among multiple links.
  • the receiving module 2201 is configured to receive The main link sends second indication information, and the second indication information indicates the working state or the sleep state of multiple links, or the TWT negotiation is performed with the first device through the main link.
  • the first indication information is a special element
  • the second device can receive a message frame sent by the first device through the main link.
  • the message frame can carry a special element, which is only carried in the message frame sent by the main link.
  • This special element is used to indicate that the link that transmits the message frame is the primary link.
  • the first indication information is the link sequence number
  • the second device can receive the message frame sent by the first device over the non-primary link.
  • the message frame can carry a reduced neighbor report element or a multi-band element, and a reduced neighbor report element or more
  • the frequency band element includes a link sequence number, which is used to indicate the main link of multiple links.
  • each module can also refer to the corresponding description of the method embodiment shown in FIG. 6 and FIG. 17 to execute the method and function performed by the second device in the foregoing embodiment.
  • FIG. 23 is a schematic structural diagram of a first device according to an embodiment of the present application.
  • the first device may include: at least one processor 2301, at least one communication interface 2302, at least one memory 2303, and at least one communication bus 2304.
  • the processor 2301 may be a central processing unit, a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute various exemplary logical blocks, modules and circuits described in conjunction with the disclosure of this application.
  • the processor may also be a combination that implements computing functions, for example, a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, and so on.
  • the communication bus 2304 may be a standard PCI bus for interconnecting peripheral components or an extended industry standard structure EISA bus. The bus can be divided into address bus, data bus, control bus, etc.
  • the communication bus 2304 is used to implement connection and communication between these components.
  • the communication interface 2302 of the device in the embodiment of the present application is used for signaling or data communication with other node devices.
  • the memory 2303 may include volatile memory, such as nonvolatile random access memory (NVRAM), phase change RAM (PRAM), magnetoresistive random access memory (magetoresistive) RAM, MRAM), etc., and may also include non-volatile memory, such as at least one disk storage device, electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), flash memory devices, such as reverse or flash memory (NOR flash memory) or reverse flash memory (NAND flash memory), semiconductor devices, such as solid state disk (SSD), etc.
  • the memory 2303 may also be at least one storage device located far away from the foregoing processor 2301.
  • the memory 2303 may also store a group of program codes, and the processor 2301 may optionally execute the programs executed in the memory 2303.
  • the communication interface 2302 sends an ADDBA request frame to the second device, where the ADDBA request frame includes at least one reference value of a first buffer size field and a reference value of a second buffer size field; the first device and the second device It is a multi-link entity containing one or more links;
  • the communication interface 2302 receives an ADDBA response frame sent by the second device, where the ADDBA response frame includes the confirmation value of the at least one first buffer size field and the confirmation value of the second buffer size field;
  • one of the first buffer size fields is used to indicate the size of a local buffer space corresponding to one of the multiple links of the first device and the second device
  • the second buffer size field Used to indicate the size of a global buffer space maintained by the first device and the second device.
  • processor 2301 is further configured to perform the following operations:
  • the first device maintains multiple first sending windows and one second sending window, wherein the multiple first sending windows and the multiple of the first device Corresponding to each link, and the second sending window corresponds to the multi-link entity of the first device;
  • one of the first sending windows corresponds to one of the multiple links, one of the first sending windows has a start sequence number of WinStartO1, an end sequence number of WinEndO1, and a window size of WinSizeO1, where the WinSizeO1
  • the confirmation value equal to the first buffer size corresponding to the link;
  • the start sequence number of the second sending window is WinStartO2
  • the end sequence number is WinEndO2
  • the window size is WinSizeO2 where WinSizeO2 is equal to the confirmation value of the second buffer size negotiated through the ADDBA request frame and the ADDBA response frame.
  • the ADDBA request frame includes at least one first block confirmation start sequence number control field and second block confirmation start sequence number control field;
  • the first block confirmation start sequence number control field is used to indicate the first initial sequence number of the start sequence number of the first scoreboard of the link of the second device, and the type of the first initial sequence number Is the local serial number;
  • the second block confirmation start sequence number control field is used to indicate the second initial sequence number of the start sequence number of the second scoreboard of the multilink entity of the second device, and the second initial sequence number
  • the type is the global serial number.
  • the ADDBA request frame includes at least one of a link bitmap field and a reference value of the at least one first buffer size field, or a link number field, a multiple link identification number field, and the at least one At least one of the reference values of a first buffer size field;
  • the ADDBA response frame includes at least one of a link bitmap field and an acknowledgement value of the at least one first buffer size field, or a link number field, multiple link identification number fields, and the at least one first buffer size field. At least one of the confirmation values of a buffer size field;
  • the ADDBA request frame includes a first block confirmation parameter set field, and the first block confirmation parameter set field includes a reference value of the second buffer size field;
  • the ADDBA response frame includes a second block confirmation parameter set field, and the second block confirmation parameter set field includes the confirmation value of the second buffer size field.
  • processor 2301 is further configured to perform the following operations:
  • the communication interface 2302 sends a data packet to the second device
  • the communication interface 2302 receives the confirmation message replies from the second device in response to the data packet;
  • the data packet includes a local sequence number and a global sequence number
  • the local sequence number is an identifier assigned to the data packet by the link that sends the data packet among the multiple links
  • the global sequence number is all The identifier assigned to the data packet by the multilink entity.
  • processor 2301 is further configured to perform the following operations:
  • the communication interface 2302 sends a block confirmation request frame or a multi-user block confirmation request trigger frame to the second device, where the block confirmation request frame or the multi-user block confirmation request trigger frame includes a start sequence number control field, and the start The initial sequence number control field includes the initial sequence number;
  • the block confirmation request frame or the multi-user block confirmation request trigger frame further includes first indication information, where the first indication information is used to indicate the type of the starting sequence number, and the type of the starting sequence number includes Local serial number or global serial number.
  • processor 2301 is further configured to perform the following operations:
  • a block confirmation frame sent by the second device is received, the block confirmation frame includes a start sequence number control field, the start sequence number control field includes a start sequence number and a block confirmation bitmap; the block confirmation bit The bitmap is used to indicate the reception status of the data packet received by the second device;
  • the block confirmation frame further includes a block confirmation BA control field, the BA control field includes the second indication information, and the second indication information is used to indicate the type of the starting sequence number, and the starting sequence number
  • the type of is a local sequence number or a global sequence number, and the first bit in the block confirmation bitmap corresponds to the starting sequence number.
  • a message frame is sent to the second device through the communication interface 2302, where the message frame includes first indication information, and the first indication information is used to indicate the main link among the multiple links.
  • the second indication information is sent to the second device through the main link, where the second indication information indicates the working state or the sleep state of multiple links, or the TWT negotiation is performed with the second device through the main link.
  • the first indication information is a special element.
  • the first device can send a message frame to the second device through the main link.
  • the message frame can carry a special element.
  • the special element is only carried in the message frame sent by the main link. This special element is used to indicate that the link that transmits the message frame is the primary link.
  • the main link is indicated by a special element, so that other links are in a dormant state or closed state, thereby saving power.
  • the first indication information is the link sequence number.
  • the first device can send a message frame to the second device through a non-primary link.
  • the message frame can carry a reduced neighbor report element or a multi-band element, a reduced neighbor report element or a multi-band
  • the element includes a link sequence number, which is used to indicate the main link of multiple links.
  • an operation type field is added to the information field of the single-user TWT parameter and the information field of the broadcast TWT parameter, and the operation type field and the TWT channel field are combined to indicate which link of the multiple links the TWT element is applied to.
  • An indication value may be added to the broadcast TWT parameter information field, and the indication value is used to indicate which link of the multiple links the TWT element is applied to.
  • one or more link sequence numbers are added to the information field of the single-user TWT parameter and the information field of the broadcast TWT parameter.
  • the link sequence number is used to indicate which link of the multiple links the TWT element is applied to.
  • the link sequence number bitmap is used to indicate which link of the multiple links the TWT element is applied to.
  • the processor may also cooperate with the memory and the communication interface to execute the operation of the first device in the above application embodiment.
  • FIG. 24 is a schematic structural diagram of a second device according to an embodiment of the present application.
  • the second device may include: at least one processor 2401, at least one communication interface 2402, at least one memory 2403, and at least one communication bus 2404.
  • the processor 2401 may be various types of processors mentioned above.
  • the communication bus 2404 may be a standard PCI bus for interconnecting peripheral components or an extended industry standard structure EISA bus. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, only one thick line is used in FIG. 24 to indicate, but it does not mean that there is only one bus or one type of bus.
  • the communication bus 2404 is used to implement connection and communication between these components. Among them, the communication interface 2402 of the device in the embodiment of the present application is used for signaling or data communication with other node devices.
  • the memory 2403 may be various types of memories mentioned above. Optionally, the memory 2403 may also be at least one storage device located far away from the foregoing processor 2401.
  • the memory 2403 stores a set of program codes, and the processor 2401 executes the programs executed by the above-mentioned OAM in the memory 2403.
  • the ADDBA request frame sent by the first device is received through the communication interface 2402, the ADDBA request frame includes at least one reference value of a first buffer size field and a reference value of a second buffer size field; the first device and the second device
  • the device is a multi-link entity containing one or more links;
  • one of the first buffer size fields is used to indicate the size of a local buffer space corresponding to one of the multiple links of the first device and the second device
  • the second buffer size field Used to indicate the size of a global buffer space maintained by the first device and the second device.
  • processor 2401 is further configured to perform the following operations:
  • the second device maintains a receiving window, where the receiving window corresponds to the link entity of the second device;
  • the start sequence number of the receiving window is WinStartB2
  • the end sequence number is WinEndB2
  • the window size is WinSizeB2 where WinSizeB2 is equal to the comparison between the confirmation value of the second buffer size field and the maximum length block confirmation bitmap. Small value.
  • processor 2401 is further configured to perform the following operations:
  • the second device maintains multiple first receiving windows and one second receiving window, where the multiple first receiving windows correspond to multiple links of the second device, and the second receiving window Corresponds to the link entity of the second device.
  • the ADDBA request frame includes a first block confirmation start sequence number control field and a second block confirmation start sequence number control field;
  • the first block confirmation start sequence number control field is used to indicate the first initial sequence number of the start sequence number of the first scoreboard of the link of the second device, and the type of the first initial sequence number is Local serial number;
  • the second block confirmation start sequence number control field is used to indicate the second initial sequence number of the start sequence number of the second scoreboard of the multilink entity of the second device, and the second initial sequence number of the second initial sequence number.
  • the type is the global serial number.
  • the ADDBA request frame includes at least one of a link bitmap field and a reference value of the at least one first buffer size field, or a link number field, a multiple link identification number field, and the at least one At least one of the reference values of a first buffer size field;
  • the ADDBA response frame includes at least one of a link bitmap field and an acknowledgement value of the at least one first buffer size field, or a link number field, multiple link identification number fields, and the at least one first buffer size field. At least one of the confirmation values of a buffer size field;
  • the ADDBA request frame includes a first block confirmation parameter set field, and the first block confirmation parameter set field includes a reference value of the second buffer size field;
  • the ADDBA response frame includes a second block confirmation parameter set field, and the second block confirmation parameter set field includes the confirmation value of the second buffer size field.
  • processor 2401 is further configured to perform the following operations:
  • the data packet includes a local sequence number and a global sequence number
  • the local sequence number is an identifier assigned to the data packet by the link that sends the data packet among the multiple links
  • the global sequence number is all The identifier assigned to the data packet by the multilink entity.
  • processor 2401 is further configured to perform the following operations:
  • the block confirmation request frame or the multi-user block confirmation request trigger frame sent by the first device is received through the communication interface 2402, the block confirmation request frame or the multi-user block confirmation request trigger frame includes a start sequence number control field, so The starting sequence number control field includes the starting sequence number;
  • the block confirmation request frame or the multi-user block confirmation request trigger frame further includes first indication information, where the first indication information is used to indicate the type of the starting sequence number, and the type of the starting sequence number includes Local serial number or global serial number.
  • processor 2401 is further configured to perform the following operations:
  • the start sequence number of the first scoreboard is WinStartR1, and the end sequence number is WinEndR1;
  • the scoreboard size WinSizeR1 is equal to the confirmation value of the first buffer size corresponding to the corresponding link and the block confirmation bitmap of the maximum length The smaller value of
  • the start sequence number of the second scoreboard is WinStartR2
  • the end sequence number is WinEndR2
  • the scoreboard size is WinSizeR2
  • WinSizeR2 is equal to the confirmation value of the second buffer size and the block confirmation bitmap of the maximum length The smaller value in.
  • the confirmation message is a block confirmation frame
  • the block confirmation frame includes a start sequence number control field, and the start sequence number control field includes a start sequence number and a block confirmation bitmap; the block confirmation bitmap is used to indicate that the second device receives The reception of said data packet;
  • the block confirmation frame further includes a block confirmation BA control field, the BA control field includes the second indication information, and the second indication information is used to indicate the type of the starting sequence number, and the starting sequence number
  • the type of is a local sequence number or a global sequence number, and the first bit in the block confirmation bitmap corresponds to the starting sequence number.
  • the sequence number corresponding to the first bit in the block confirmation bitmap is the WinStartR1;
  • sequence corresponding to the block confirmation bitmap is the global sequence number
  • sequence number corresponding to the first bit in the block confirmation bitmap is the WinStartR2.
  • the message frame sent by the first device is received through the communication interface 2402, the message frame includes the first indication information, and the first indication information is used to indicate the main link among the multiple links.
  • the second indication information sent by the first device through the main link is received through the communication interface 2402, the second indication information indicates the working status or the sleep state of multiple links, or the TWT negotiation is performed with the first device through the main link.
  • the first indication information is a special element
  • the second device can receive a message frame sent by the first device through the main link.
  • the message frame can carry a special element, and the special element is only carried in the message frame sent by the main link.
  • This special element is used to indicate that the link that transmits the message frame is the primary link.
  • the first indication information is the link sequence number
  • the second device can receive the message frame sent by the first device over the non-primary link.
  • the message frame can carry a reduced neighbor report element or a multi-band element, and a reduced neighbor report element or more
  • the frequency band element includes a link sequence number, which is used to indicate the main link of multiple links.
  • processor may also cooperate with the memory and the communication interface to perform the operation of the second device in the above application embodiment.
  • the embodiment of the present application also provides a chip system, which includes a processor, which is used to support the first device or the second device to realize the functions involved in any of the above-mentioned embodiments, for example, to generate or process the functions mentioned in the above-mentioned method.
  • the data and/or information involved may further include a memory, and the memory is used for necessary program instructions and data of the first device or the second device.
  • the chip system can be composed of chips, or include chips and other discrete devices.
  • the embodiments of the present application also provide a processor, which is configured to be coupled with a memory and used to execute any method and function related to the first device or the second device in any of the foregoing embodiments.
  • the embodiments of the present application also provide a computer program product containing instructions, which when running on a computer, causes the computer to execute any method and function related to the first device or the second device in any of the above embodiments .
  • the embodiments of the present application also provide a device for executing any method and function related to the first device or the second device in any of the foregoing embodiments.
  • An embodiment of the present application also provides a wireless communication system, which includes at least one first device and at least one second device involved in any of the foregoing embodiments.
  • the computer program product includes one or more computer instructions.
  • the computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website, computer, server, or data center.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center integrated with one or more available media.
  • the usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, and a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Landscapes

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

Abstract

本申请实施例公开了一种适用于多链路的通信方法及相关设备。包括：第一设备向第二设备发送ADDBA请求帧，ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；接收第二设备发送的ADDBA响应帧，ADDBA响应帧包括至少一个第一缓冲大小字段的确认值和第二缓冲大小的确认值；根据ADDBA请求帧和ADDBA响应帧，建立多链路块确认对话，一个第一缓冲大小字段用于指示第一设备和第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，第二缓冲大小字段用于指示第一设备和第二设备维护的一个全局缓冲空间的大小。采用本申请实施例，可以提高通信效率。

Description

一种适用于多链路的通信方法及相关设备 技术领域
本申请涉及通信技术领域，尤其涉及一种适用于多链路的通信方法及相关设备。
背景技术
为了大幅提升无线局域网(wireless local access network，WLAN)系统的业务传输速率，电气和电子工程师协会(institute of electrical and electronics engineers，IEEE)802.11ax标准在现有正交频分复用(orthogonal frequency division multiplexing，OFDM)技术的基础上，进一步采用正交频分多址(orthogonal frequency division multiple access，OFDMA)技术。其中，OFDMA技术支持多个节点同时发送和接收数据，从而实现多站点分集增益。802.11ax标准以及802.11ax之前的标准为同一工作频段的无线保真(wreless-fidelity，WiFi)配置了多条链路，但是每条链路中建立不同的基本服务集(basic service set，BSS)，一个时刻只能在一条链路与该链路所归属的BSS内的站点通信，影响通信效率。
发明内容
本申请实施例提供一种适用于多链路的通信方法及相关设备，可以提高通信效率。
第一方面，本申请实施例提供了一种适用于多链路的通信方法，包括：第一设备向第二设备发送ADDBA请求帧，ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；第一设备和第二设备为包含一条或多条链路的多链路实体；第一设备接收第二设备发送的ADDBA响应帧，ADDBA响应帧包括至少一个第一缓冲大小字段的确认值和第二缓冲大小字段的确认值；根据ADDBA请求帧和ADDBA响应帧，建立第一设备的多条链路与第二设备的多条链路之间的多链路块确认对话；其中，一个第一缓冲大小字段用于指示第一设备和第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，第二缓冲大小字段用于指示第一设备和第二设备维护的一个全局缓冲空间的大小。通过ADDBA请求帧和ADDBA响应帧协商一个全局缓冲空间的大小和多个局部缓冲空间的大小，建立多链路的块确认对话，通过多链路的块确认对话实现在多条链路上进行通信。
在一种可能的设计中，根据ADDBA请求帧和ADDBA响应帧，第一设备维护多个第一发送窗口和一个第二发送窗口，其中，多个第一发送窗口与第一设备的多条链路相对应，第二发送窗口与第一设备的多链路实体相对应。通过发送窗口对数据包的发送进行管理和控制，使得数据包可以在多条链路上进行发送。
在另一种可能的设计中，一个第一发送窗口对应多条链路中的一条链路，一个第一发送窗口起始序号为WinStartO1,结束序号为WinEndO1，窗口大小为WinSizeO1，其中，WinSizeO1等于链路所对应的第一缓冲大小字段的确认值；第二发送窗口起始序号为WinStartO2,结束序号为WinEndO2，窗口大小为WinSizeO2，其中，WinSizeO2等于通过ADDBA请求帧和ADDBA响应帧协商的第二缓冲大小的确认值。通过发送窗口的大小、起始序号和结束序号来保障数据包的发送。
在另一种可能的设计中，ADDBA请求帧包括第一块确认起始序列号控制字段和第二块确认起始序列号控制字段，第一块确认起始序列号控制字段用于指示第二设备的链路的第一计分板的起始序列号的第一初始序列号，也可以用于指示第二设备的链路的第一接收窗口的起始序列号的第一初始序列号。第一初始序列号的类型为本地序列号；第二块确认起始序列号控制字段用于指示第二设备的多链路实体的第二计分板的起始序列号的第二初始序列号，也可以用于指示第二设备的链路的第二接收窗口的起始序列号的第一初始序列号。第二初始序列号的类型为全局序列号。通过第一初始序列号指示第二设备的低MAC层维护一个计分板或接收窗口，通过第二初始序列号指示第二设备的高MAC层维护一个计分板或接收窗口。
在另一种可能的设计中，ADDBA请求帧包括链路比特位图字段和至少一个第一缓冲大小字段的参考值中的至少一个，或，链路数目字段、多条链路身份号字段以及至少一个第一缓冲大小字段的参考值中的至少一个；ADDBA响应帧包括链路比特位图字段和至少一个第一缓冲大小字段的确认值中的至少一个，或，链路数目字段、多条链路身份号字段以及至少一个第一缓冲大小字段的确认值中的至少一个。通过ADDBA请求帧和ADDBA响应帧协商第一缓冲大小，保障第一设备和第二设备每条链路的局部缓冲空间的大小相同。
在另一种可能的设计中，ADDBA请求帧包括第一块确认参数集字段，第一块确认参数集字段包括第二缓冲大小字段的参考值；ADDBA响应帧包括第二块确认参数集字段，第二块确认参数集字段包括第二缓冲大小的确认值。通过ADDBA请求帧和ADDBA响应帧协商第二缓冲大小，保障第一设备和第二设备的多链路实体的全局缓冲空间的大小相同。
在另一种可能的设计中，第一设备向第二设备发送数据包；接收第二设备回复的响应数据包的确认消息。数据包包括本地序列号和全局序列号，本地序列号为多条链路中发送数据包的链路分配给数据包的标识，全局序列号为多链路实体分配给数据包的标识。通过本地序列号和全局序列号，实现第一设备可以在多条链路上正确发送同一类型的数据包，从而提高通信效率。
在另一种可能的设计中，第一设备向第二设备发送块确认请求帧或多用户块确认请求触发帧，块确认请求帧或多用户块确认请求触发帧包括起始序列号控制字段，起始序列号控制字段包括起始序列号；块确认请求帧或多用户块确认请求触发帧还包括第一指示信息，第一指示信息用于指示起始序列号的类型，起始序列号的类型包括本地序列号或全局序列号。从而第二设备可以通过起始序列号的类型确认接收到数据包，生成本地序列号对应的块确认比特位图或者全局序列号对应的块确认比特位图。
在另一种可能的设计中，第一设备接收第二设备发送的块确认帧，块确认帧包括起始序列号控制字段，起始序列号控制字段包括起始序列号和块确认比特位图；块确认比特位图用于指示第二设备接收到的数据包的接收情况；块确认帧还包括块确认BA控制字段，BA控制字段包括第二指示信息，第二指示信息用于指示起始序列号的类型，起始序列号的类型为本地序列号或全局序列号，且块确认比特位图中的第一比特对应起始序列号。
在另一种可能的设计中，ADDBA请求帧和ADDBA响应帧均包括块确认功能字段， 块确认功能字段包括用于指示多链路块确认会话的功能类型的信息；多链路块确认会话的功能类型包括：多链路块确认请求，多链路块确认响应，多链路块确认对话拆除；其中，ADDBA请求帧中的信息指示多链路块确认会话为多链路块确认请求；ADDBA响应帧中的信息指示多链路块确认会话为多链路块确认响应。通过ADDBA请求帧和ADDBA响应帧协商增加多链路块确认会话功能，保障多链路块确认会话建立成功。
第二方面，本申请实施例提供了一种适用于多链路的通信方法，包括：第二设备接收第一设备发送ADDBA请求帧，ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；第一设备和第二设备为包含一条或多条链路的多链路实体；第二设备向第一设备发送的ADDBA响应帧，ADDBA响应帧包括至少一个第一缓冲大小字段的确认值和第二缓冲大小字段的确认值；根据ADDBA请求帧和ADDBA响应帧，建立第一设备的多条链路与第二设备的多条链路之间的多链路块确认对话；其中，一个第一缓冲大小字段用于指示第一设备和第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，第二缓冲大小字段用于指示第一设备和第二设备维护的一个全局缓冲空间的大小。通过ADDBA请求帧和ADDBA响应帧协商一个全局缓冲空间的大小和多个局部缓冲空间的大小，建立多链路的块确认对话，通过多链路的块确认对话实现在多条链路上进行通信。
在一种可能的设计中，根据ADDBA请求帧和ADDBA响应帧，第二设备维护一个接收窗口，其中，接收窗口与第二设备的链路实体相对应；其中，接收窗口起始序号为WinStartB2,结束序号为WinEndB2，窗口大小为WinSizeB2，其中，WinSizeB2等于第二缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。通过发送窗口对数据包的发送进行管理和控制，使得数据包可以在多条链路上进行发送，从而提高了通信效率。
在另一种可能的设计中，根据ADDBA请求帧和ADDBA响应帧，第二设备维护多个第一接收窗口和一个第二接收窗口，其中，多个第一接收窗口与第二设备的多条链路相对应，第二接收窗口与第二设备的链路实体相对应。通过发送窗口对数据包的发送进行管理和控制，使得数据包可以在多条链路上进行发送，从而提高了通信效率。
在另一种可能的设计中，一个第一接收窗口对应多条链路中的一条链路，第一接收窗口起始序号为WinStartB1,结束序号为WinEndB1，窗口大小为WinSizeB1，其中，WinSizeB1等于链路所对应的第一缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值；第二接收窗口起始序号为WinStartB2,结束序号为WinEndB2，窗口大小为WinSizeB2，其中，WinSizeB2等于第二缓冲大小的确认值与最大长度的块确认比特位图中的较小值。通过接收窗口的大小、起始序号和结束序号来对接收到的数据包进行重排序。
在另一种可能的设计中，ADDBA请求帧包括第一块确认起始序列号控制字段和第二块确认起始序列号控制字段，第一块确认起始序列号控制字段用于指示第二设备的链路的第一计分板的起始序号的第一初始序列号，也可以用于指示第二设备的链路的第一接收窗口的起始序号的第一初始序列号，第一初始序列号的类型为本地序列号。第二块确认起始序列号控制字段用于指示第二设备的多链路实体的第二计分板的起始序号的第二初始序列号，也可以用于指示第二设备的链路的第二接收窗口的起始序号的第一初始序列号，第二初始序列号的类型为全局序列号。通过第一初始序列号指示第二设备的低MAC层维护 一个计分板或接收窗口，通过第二初始序列号指示第二设备的高MAC层维护一个计分板或接收窗口。
在另一种可能的设计中，ADDBA请求帧包括链路比特位图字段和至少一个第一缓冲大小字段的参考值中的至少一个，或，链路数目字段、多条链路身份号字段以及至少一个第一缓冲大小字段的参考值中的至少一个；ADDBA响应帧包括链路比特位图字段和至少一个第一缓冲大小字段的确认值中的至少一个，或，链路数目字段、多条链路身份号字段以及至少一个第一缓冲大小字段的确认值中的至少一个。通过ADDBA请求帧和ADDBA响应帧协商第一缓冲大小，保障第一设备和第二设备每条链路的局部缓冲空间的大小相同。通过ADDBA请求帧和ADDBA响应帧协商第一缓冲大小，保障第一设备和第二设备每条链路的局部缓冲空间的大小相同。
在另一种可能的设计中，ADDBA请求帧包括第一块确认参数集字段，第一块确认参数集字段包括第二缓冲大小字段的参考值；ADDBA响应帧包括第二块确认参数集字段，第二块确认参数集字段包括第二缓冲大小的确认值。通过ADDBA请求帧和ADDBA响应帧协商第二缓冲大小，保障第一设备和第二设备的多链路实体的全局缓冲空间的大小相同。
在另一种可能的设计中，第二设备接收第一设备发送数据包；向第一设备发送用于响应数据包的确认消息。数据包包括本地序列号和全局序列号，本地序列号为多条链路中发送数据包的链路分配给数据包的标识，全局序列号为多链路实体分配给数据包的标识。通过本地序列号和全局序列号，实现第二设备可以在多条链路上正确接收同一类型的数据包，从而提高通信效率。
在另一种可能的设计中，第二设备接收第一设备发送的块确认请求帧或多用户块确认请求触发帧，块确认请求帧或多用户块确认请求触发帧包括起始序列号控制字段，起始序列号控制字段包括起始序列号；块确认请求帧或多用户块确认请求触发帧还包括第一指示信息，第一指示信息用于指示起始序列号的类型，起始序列号的类型包括本地序列号或全局序列号。从而第二设备可以通过起始序列号的类型确认接收到数据包，生成本地序列号对应的块确认比特位图或者全局序列号对应的块确认比特位图。
在另一种可能的设计中，第二设备维护多个第一计分板和一个第二计分板；多个第一计分板与多条链路相对应，第二计分板与多链路实体相对应；一个第一计分板的起始序号为WinStartR1，结束序号为WinEndR1；计分板大小WinSizeR1等于所对应的链路所对应的第一缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值；第二计分板的起始序号为WinStartR2,结束序号为WinEndR2，计分板大小为WinSizeR2，其中，WinSizeR2等于第二缓冲大小的确认值与最大长度的块确认比特位图中的较小值。通过维护多个第一计分板和一个第二计分板，保障第二设备正确确认接收到的数据包。
在另一种可能的设计中，确认消息为块确认帧；块确认帧包括起始序列号控制字段，起始序列号控制字段包括起始序列号和块确认比特位图；块确认比特位图用于指示第二设备接收到的数据包的接收情况。块确认帧还包括块确认BA控制字段，BA控制字段包括第二指示信息，第二指示信息用于指示起始序列号的类型，起始序列号的类型为本地序列号或全局序列号，且块确认比特位图中的第一比特对应起始序列号。
在另一种可能的设计中，若块确认比特位图所对应的序列为本地序列号，则块确认比特位图中的第一比特所对应的序列号为WinStartR1；若块确认比特位图所对应的序列为全局序列号，则块确认比特位图中的第一比特所对应的序列号为WinStartR2。
在另一种可能的设计中，ADDBA请求帧和ADDBA响应帧均包括块确认功能字段，块确认功能字段包括用于指示多链路块确认会话的功能类型的信息；多链路块确认会话的功能类型包括：多链路块确认请求，多链路块确认响应，多链路块确认对话拆除；其中，ADDBA请求帧中的信息指示多链路块确认会话为多链路块确认请求；ADDBA响应帧中的信息指示多链路块确认会话为多链路块确认响应。通过ADDBA请求帧和ADDBA响应帧协商增加多链路块确认会话功能，保障多链路块确认会话建立成功。
第三方面，本申请实施例提供了一种数据帧传输方法，包括：第一设备向第二设备发送消息帧，消息帧包括第一指示信息，第一指示信息用于指示多条链路中的主链路。通过主链路向第二设备发送第二指示信息，第二指示信息指示多条链路的工作状态或休眠状态，或者通过主链路与第二设备进行TWT协商，使得其他链路处于休眠状态或关闭状态，从而实现节省功率。
在一种可能的设计中，第一指示信息为特殊元素，第一设备可以通过主链路向第二设备发送消息帧，该消息帧可以携带一个特殊元素，该特殊元素仅携带在主链路发送的消息帧中，该特殊元素用于指示传输该消息帧的链路为主链路。通过特殊元素指示主链路，使得其他链路处于休眠状态或关闭状态，从而实现节省功率。
在另一种可能的设计中，第一指示信息为链路序号，第一设备可以通过非主链路向第二设备发送消息帧，消息帧可以携带缩减版邻居汇报元素或多频段元素，缩减版邻居汇报元素或多频段元素包括链路序号，该链路序号用于指示多条链路的主链路。通过链路序号指示主链路，使得其他链路处于休眠状态或关闭状态，从而实现节省功率。
在另一种可能的设计中，在单用户TWT参数的信息字段或广播TWT参数的信息字段中增加操作种类字段，结合操作种类字段和TWT信道字段一起指示TWT元素应用在多条链路中的哪一条链路。可以在广播TWT参数信息字段中增加指示值，该指示值用于指示该TWT元素应用在多条链路中的哪一条链路上。实现在TWT参数指示的服务窗口内进行工作，而在服务窗口外可以进行休眠，从而节省功率。
在另一种可能的设计中，在单用户TWT参数的信息字段和广播TWT参数的信息字段中增加一个或多条链路序号，该链路序号用于指示该TWT元素应用在多条链路中的哪一条链路上。或者，通过链路序号比特位图指示该TWT元素应用在多条链路中的哪一条链路上。实现TWT参数指示的服务窗口内进行工作，而在服务窗口外可以进行休眠，从而起到节省功率的作用。
第四方面，本申请实施例提供了一种数据帧传输方法，包括：第二设备接收第一设备发送消息帧，消息帧包括第一指示信息，第一指示信息用于指示多条链路中的主链路。第二设备接收第一设备通过主链路发送第二指示信息，第二指示信息指示多条链路的工作状态或休眠状态，或者通过主链路与第一设备进行TWT协商，使得其他链路处于休眠状态或关闭状态，从而实现节省功率。
在一种可能的设计中，第一指示信息为特殊元素，第二设备可以接收第一设备通过主 链路发送的消息帧，该消息帧可以携带一个特殊元素，该特殊元素仅携带在主链路发送的消息帧中，该特殊元素用于指示传输该消息帧的链路为主链路。通过特殊元素指示主链路，使得其他链路处于休眠状态或关闭状态，从而实现节省功率。
在另一种可能的设计中，第一指示信息为链路序号，第二设备可以接收第一设备通过非主链路发送的消息帧，消息帧可以携带缩减版邻居汇报元素或多频段元素，缩减版邻居汇报元素或多频段元素包括链路序号，该链路序号用于指示多条链路的主链路。通过链路序号指示主链路，使得其他链路处于休眠状态或关闭状态，从而实现节省功率。
第五方面，本申请实施例提供了一种第一通信装置，该第一设备被配置为实现上述第一方面和第三方面中第一设备所执行的方法和功能，由硬件/软件实现，其硬件/软件包括与上述功能相应的模块。
第六方面，本申请实施例提供了一种第二通信装置，该第二设备被配置为实现上述第二方面和第四方面中第二设备所执行的方法和功能，由硬件/软件实现，其硬件/软件包括与上述功能相应的模块。
第七方面，本申请实施例提供了另一种第一设备，包括：处理器、存储器和通信总线，其中，通信总线用于实现处理器和存储器之间连接通信，处理器执行存储器中存储的程序用于实现上述第一方面和第三方面的步骤。
在一个可能的设计中，本申请提供的第一设备可以包含用于执行上述方法设计中第一实体的行为相对应的模块。模块可以是软件和/或是硬件。
第八方面，本申请实施例提供了另一种第二设备，包括：处理器、存储器和通信总线，其中，通信总线用于实现处理器和存储器之间连接通信，处理器执行存储器中存储的程序用于实现上述第二方面和第四方面提供的步骤。
在一个可能的设计中，本申请提供的第二设备可以包含用于执行上述方法设计中第一设备的行为相对应的模块。模块可以是软件和/或是硬件。
第九方面，本申请提供了一种计算机可读存储介质，计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述各方面的方法。
第十方面，本申请提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面的方法。
第十一方面，提供了一种芯片，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得安装有所述芯片的通信设备执行上述任一方面的方法。
第十二方面，本申请实施例还提供另一种芯片，该芯片可以为第一设备或第二设备内的芯片，该芯片包括：输入接口、输出接口和处理电路，所述输入接口、所述输出接口与所述电路之间通过内部连接通路相连，所述处理电路用于执行上述任一方面的方法。
第十三方面，提供另一种芯片，包括：输入接口、输出接口、处理器，可选的，还包括存储器，所述输入接口、输出接口、所述处理器以及所述存储器之间通过内部连接通路相连，所述处理器用于执行所述存储器中的代码，当所述代码被执行时，所述处理器用于执行上述任一方面中的方法。
第十四方面，提供一种装置，用于实现上述任一方面的方法。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请实施例提供的一种多频段操作的示意图；
图2是本申请实施例提供的一种多频段硬件的架构示意图；
图3是本申请实施例提供的一种通信系统的架构示意图；
图4是本申请实施例提供的一种AP和STA的结构示意图；
图5是本申请实施例提供的另一种AP和STA的结构示意图；
图6是本申请实施例提供的一种适用于多链路的通信方法的流程示意图；
图7是本申请实施例提供的一种ADDBA请求帧的示意图；
图8是本申请实施例提供的一种块确认功能字段的示意图；
图9是本申请实施例提供的一种块确认参数集字段的示意图；
图10是本申请实施例提供的一种多链路元素的示意图；
图11是本申请实施例提供的一种第一设备发送端的结构示意图；
图12是本申请实施例提供的一种第二设备接收端的结构示意图；
图13是本申请实施例提供的一种ADDBA响应帧的示意图；
图14本申请实施例提供的一种MAC头的示意图；
图15是本申请实施例提供的一种块确认请求帧或多用户块确认请求触发帧的示意图；
图16本申请实施例提供的一种块确认帧的示意图；
图17是本申请实施例提供的一种数据帧传输方法的流程示意图；
图18是本申请实施例提供的一种TWT元素的示意图；
图19是本申请实施例提供的一种单用户TWT类型的示意图；
图20是本申请实施例提供的一种广播TWT类型的示意图；
图21是本申请实施例提供的一种第一通信装置的结构示意图；
图22是本申请实施例提供的一种第二通信装置的结构示意图；
图23是本申请实施例提出的另一种第一设备的结构示意图；
图24是本申请实施例提出的另一种第二设备的结构示意图。
具体实施方式
下面结合本申请实施例中的附图对本申请实施例进行描述。
美国联邦通信委员会(federal communications commission，FCC)开放了一段新的免费频段5925-7125MHz，下述简称该段频段为6GHz。于是802.11ax标准工作者在802.11ax项目授权申请书(project authorization requests，PAR)中将802.11ax设备的工作范围从2.4GHz，5GHz拓展到2.4GHz、5GHz和6GHz。但是具体涉及的标准协议，例如帧结构所支持的最大的带宽160M都未做任何改变。
每一代主流WiFi协议都是兼容传统站点的。例如最早一代主流WiFi的802.11a帧结构以前导码开始，包括传统短训练序列域(legacy-short training field，L-STF)、传统长训 练序列域(legacy-long training field，L-LTF)、传统信令域(legacy-signal field，L-SIG)，802.11a的前导码被称为传统前导码。后续的主流WiFi协议802.11g、802.11n、802.11ac以及802.11ax的帧结构都以传统前导码开始，以便兼容传统站点。
IEEE 802.11下一代WiFi协议的极高吞吐量(extremely high throughput，EHT)设备由于需要向前兼容，因此也会支持802.11ax设备的工作频段，即支持2.4GHz，5GHz和6GHz频段。同样，下一代WIFI协议同样需要向前兼容，帧结构以传统前导码开始，紧接着是新一代前导码，该新一代前导码包括实现新一代WIFi协议EHT的新功能指示，例如关于超大带宽的带宽指示。另外，该新一代前导码还携带指示信息，该指示信息用于指示物理层协议数据单元(PHY protocol data unit，PPDU)是EHT PPDU，这样不会被接收端误判为传统的PPDU。例如802.11a的PPDU、802.11n的高吞吐量(high throughput，HT)PPDU、802.11ac的非常高吞吐率(very high throughput，VHT)PPDU或者802.11ax HE PPDU。除了通过超大带宽提高峰值吞吐量，IEEE 802.11ax下一代WiFi EHT协议还可以通过更多的流数(例如流数增加到16流)以及多个频段(例如2.4GHz，5GHz和6GHz)合作等方式提高峰值吞吐量。在同一频段上，还可以通过多个信道合作等方式提高峰值吞吐量，降低业务传输的时延。其中，多频段或多信道可以统称为多链路。
802.11ax标准以及802.11ax之前的标准在一个或多个工作频段的WiFi配置了多条链路，但是每条链路中建立不同的BSS，一个时刻只能在一条链路与该链路所归属的BSS内的站点通信。IEEE 802.11下一代WiFi EHT协议中除了使用6GHz频段的连续超大带宽，也可以通过多链路合作技术将不连续的多链路聚合成超大带宽。多链路合作技术除了聚合更大的带宽，还可以使用多链路合作技术同时发送同一类型的数据包给同一个站点。
如图1所示，图1是本申请实施例提供的一种多频段操作的示意图。WiFi工作频段包括1GHz以下、2.4GHz和5GHz以及高频60GHz，而主流WiFi协议802.11a、802.11b、802.11g、802.11n、802.11ac、和802.11ax主要工作在2.4GHz和5GHz，支持多频段合作技术。图1给出了2个频段的操作，每个频段的操作单元包括MAC处理单元(MAC unite)、基带处理单元(base band unite，BBU)、射频单元(radio frequency unite，RFU)以及天线模块(antenna module)。其中，多频段共享MAC处理单元以及天线模块。
如图2所示，图2是本申请实施例提供的一种多频段硬件的架构示意图。该多频段硬件包括上媒体接入控制(media access control，MAC)层(up MAC layer)、MAC服务数据单元(MAC service data unit，MSDU)解析和逆解析器、MAC控制单元(MAC control unite，MCU)、基带处理单元(base band unite，BBU)以及射频单元(radio frequency unite，RFU)以及图中未显示的天线模块。多频段操作除了共享MAC处理单元之外，还共享上MAC层、解析和逆解析器，通过上MAC层接收或发送MAC上层处理的MSDU，然后通过解析和逆解析器将MSDU分发到每个频段上。每个频段拥有独立的MCU单元，MCU主单元要用于将MSDU封装成MPDU，即在MSDU前加MAC头。
目前，主流WiFi多频段操作是在每个频段上形成一个独立的BSS，每个BSS独立管理不同的站点，相互不干扰。高频60GHz上的802.11ad引入FST，FST可以包括非透明FST和透明FST。非透明FST和透明FST的主要区别在于：前者站点在不同频段使用不同的MAC地址，而后者站点在不同频段使用相同的MAC地址。FST技术可以将站点的 全部业务或者某类业务从一个频段转移到另一频段进行传输，其中业务由业务类型(traffic identifier，TID)区分。另外，FST对话可以在一个频段发生，也可以在从同一个频段的一个信道转换到另一个信道，也可以同时发生在多频段和/或多信道。但是，在将站点的业务从一个频段转移到另一个频段上传输时，某一时刻只能使用其中一个频段进行传输，未考虑同时使用多个频段给某个站点传输同一类型的业务，影响通信效率。为了解决上述技术问题，本申请实施例提供了如下解决方案。
如图3所示，图3是本申请实施例提供的一种通信系统的架构示意图。该通信系统可以包括接入点(access point，AP)和多个站点(station，STA)。本申请实施例可以适用于AP与一个或多个STA之间的数据通信，也同样适用于AP与AP之间的数据通信、或者STA与STA之间的数据通信。AP可以作为本申请提及的第一设备，也可以作为本申请提及的第二设备。STA可以作为本申请提及的第一设备，也可以作为本申请提及的第二设备。引入OFDMA技术后的WLAN系统802.11ax中，AP可以在不同的时频资源上与不同的STA进行上下行传输。AP进行上下行传输可以采用不同的模式，如OFDMA单用户多输入多输出(single-user multiple-input multiple-output，SU-MIMO)模式，或者OFDMA多用户多输入多输出(multi-user multiple-input multiple-output，MU-MIMO)。
其中，AP可以为移动用户进入有线网络的接入点，主要部署于家庭、大楼内部以及园区内部，典型覆盖半径为几十米至上百米，当然，也可以部署于户外。AP相当于一个连接有线网和无线网的桥梁，主要作用是将各个无线网络客户端连接到一起，然后将无线网络接入以太网。具体地，AP可以是带有WiFi芯片的终端设备或者网络设备。AP可以为支持802.11ax制式的设备。AP也可以为支持802.11ac、802.11n、802.11g、802.11b及802.11a等多种WLAN制式的设备。STA可以是无线通讯芯片、无线传感器或无线通信终端。例如支持WiFi通讯功能的移动电话、支持WiFi通讯功能的平板电脑、支持WiFi通讯功能的机顶盒、支持WiFi通讯功能的智能电视、支持WiFi通讯功能的智能可穿戴设备、支持WiFi通讯功能的车载通信设备和支持WiFi通讯功能的计算机。可选地，STA可以支持802.11ax制式。STA也可以支持802.11ac、802.11n、802.11g、802.11b及802.11a等多种WLAN制式。
如图4所示，图4是本申请实施例提供的一种AP和STA的结构示意图。由于802.11标准只关注802.11PHY和MAC部分，图中只给出了AP和STA的PHY和MAC部分。图中给出的AP是多个天线结构，STA是单天线结构。在实际场景中，AP和STA可以具有多天线结构，并且可以是两个以上天线的设备。又如图5所示，图5是本申请实施例提供的另一种AP和STA的结构示意图。AP和STA的内部结构相同，从上至下可以依次划分为应用(application)层模块、传输控制协议(transmission control protocol，TCP)/用户数据协议(user datagram protocol，UDP)处理模块、网络协议(internet protocol，IP)处理模块、逻辑链路控制(logical link control，LLC)模块、MAC层模块以及PHY基带模块、射频和天线，其中，天线均可以配置多根。
如图6所示，图6是本申请实施例提供的一种适用于多链路的通信方法的流程示意图， 本申请实施例中的步骤至少包括：
在本申请实施例中，块确认(block acknowledgement，BA)传输是IEEE 802.11e标准引入的机制，它允许第一设备在不接收确认帧的情况下发送多个数据包，然后第一设备发送一个块确认请求帧(block acknowledgement request，BAR)，第二设备在收到BAR后需要反馈一个BA对第一设备发送的一系列数据帧进行确认。由于第二设备将对多个数据包的确认放在一个BA帧中进行传输，因此可以减少确认帧的传输时间，提高信道利用率。为了使得第一设备和第二设备之间能够使用BA传输机制进行数据包的发送和接收，第一设备和第二设备在发送数据包之前，需要通过BA建立流程来建立多链路BA会话。多链路BA会话建立流程如下：
S601，第一设备向第二设备发送建立块确认通信机制(add block acknowledgement，ADDBA)请求帧，第二设备接收第一设备发送的ADDBA请求帧。
其中，所述ADDBA请求帧包括一个或多个第一缓冲大小(buffer size)字段和第二缓冲大小(buffer size)字段，所述第一缓冲大小字段和第二缓冲大小字段用来提供给第二设备协商对应缓冲大小字段值的参考值。第一设备可以包括一个多链路实体和多条链路，第二设备也可以包括一个多链路实体和多条链路，第一设备的多条链路和第二设备的多条链路对应，所述每条链路可以包括一个低MAC层和一个物理PHY层。
如图7所示，图7是本申请实施例提供的一种ADDBA请求帧的示意图。该ADDBA请求帧可以包括块确认功能字段、块确认参数集字段和块确认起始序列号控制字段。可选的，第二设备接收到ADDBA请求帧之后需要反馈确认帧Ack，第一设备接收到ADDBA响应帧之后也需要反馈确认帧Ack，本申请实施例中的确认帧Ack并没有在图6中体现。
其中，所述ADDBA请求帧可以包括块确认功能字段，可以在ADDBA请求帧的块确认功能字段增加多链路块确认会话的相关功能，块确认功能字段包括用于指示多链路块确认会话的功能类型的信息。其中，所述ADDBA请求帧中的所述信息指示所述多链路块确认会话为多链路块确认请求。如图8所示，图8是本申请实施例提供的一种块确认功能字段的示意图。该块确认功能字段可以包括0-255字段值，例如，字段值0表示ADDBA请求的功能，字段值1表示ADDBA响应的功能，字段值2表示BA会话删除等等。该块确认功能字段还包括3-127、131和134-255字段值，这些字段值为保留字段值，可以使用该保留字段值指示多链路块确认会话的功能类型，例如多链路块确认请求，多链路块确认响应，多链路块确认对话拆除等等。
其中，所述ADDBA请求帧可以包括一个或多个第一块确认起始序列字段，还可以包括第二块确认起始序列字段。所述ADDBA请求帧包括块确认起始序列号控制字段，该块确认起始序列号控制字段包括4比特的分片字段和12比特的起始序列号字段，所述ADDBA请求帧还可以包括多链路元素。多个第一块确认起始序列控制字段可以携带在块确认起始序列号控制字段中，第二块确认起始序列字段可以携带在多链路元素。或者，多个第一块确认起始序列控制字段可以携带在多链路元素中，第二块确认起始序列字段可以携带在块确认起始序列号控制字段中。需要说明的是，多个第一块确认起始序列字段和第二块确认起始序列字段的携带位置并不限定。所述第一块确认起始序列号控制字段用于指示所述第二设备的链路的第一计分板的起始序列号的第一初始序列号，也可以用于指示所 述第二设备的第一接收窗口的起始序列号的第一初始序列号，第一初始序列号的类型为本地序列号。所述第一接收窗口和第一计分板由第二设备的低MAC层维护，第一初始序列号用于设置第一接收窗口WinStartB的初始值，下述具体介绍。所述第二块确认起始序列号控制字段用于指示所述第二设备的多链路实体的第二计分板的起始序列号的第二初始序列号，也可以用于指示所述第二设备的第二接收窗口的起始序列号的第二初始序列号，所述第二初始序列号的类型为全局序列号。所述第二接收窗口和第二计分板由第二设备的高MAC层维护，第二初始序列号用于设置第二接收窗口WinStartB的初始值，下述具体介绍。
其中，所述ADDBA请求帧可以包括块确认参数集字段，所述块确认参数集字段包括所述第二缓冲大小字段。如图9所示，图9是本申请实施例提供的一种块确认参数集字段的示意图。块确认参数集字段可以包括1比特的A-MSDU支持、2比特的块确认策略、3比特的业务类型和10比特的缓冲大小，该10比特的缓冲大小字段可以用于指示全局缓冲空间的大小，各个字段的大小并不限定。
另外，可以在ADDBA请求帧中增加一个多链路(Multi-link)元素，所述ADDBA请求帧包括多链路元素。如图10所示，图10是本申请实施例提供的一种括多链路元素的示意图。所述多链路元素包括元素号、长度字段以及指示字段。指示字段可以包括以下两种方式：第一种方式，所述指示字段可以包括链路比特位图字段、至少一个第一缓冲大小字段。其中，第一缓冲大小字段的个数等于链路比特位图中置“1”值的比特个数，链路比特位图可以表示哪几条链路参与多链路BA会话的情况。例如，如果第1条链路参与多链路BA会话建立，第2条链路不参与多链路BA会话建立，第3条链路不参与多链路BA会话建立，第4条链路参与多链路BA会话建立，则比特位图可以表示1001。第二种方式，所述指示字段可以包括链路数目字段、多条链路身份号字段以及至少一个第一缓冲大小字段，其中，链路身份号字段个数、第一缓冲大小字段的个数与链路数目字段的值相同，该多条链路身份号字段用于指示哪些链路参与多链路BA会话建立。另外，多链路元素还包括多个第一块确认起始序列控制字段，第一块确认起始序列控制字段的个数等于参与多链路BA对话的链路个数。其中，上述指示字段不限于在多链路元素中携带，也可以在ADDBA请求帧中已有的字段或元素中携带，例如多频段(Multi-Band)元素、或者ADDBA拓展元素等。
需要说明的是，一个或多个第一缓冲大小字段和第二缓冲大小字段还可以通过其他字段携带，比如第一缓冲大小字段也可以通过块确认参数集字段进行指示，第二缓冲大小字段也可以通过多链路元素进行指示，二者还可以通过其他方式指示，这里并不限定。
可选的，第二设备接收到第一设备发送的ADDBA请求帧之后，第二设备可以向第一设备发送用于响应所述ADDBA请求帧的确认帧Ack，然后第一设备接收第二设备发送的确认帧Ack。
S602，第二设备向第一设备发送ADDBA响应帧，第一设备接收所述第二设备发送的ADDBA响应帧，所述ADDBA响应帧包括所述一个或多个第一缓冲大小字段的确认值和第二缓冲大小的确认值，该第一缓冲大小字段和第二缓冲大小字段作为块确认对话建立的确认值。所述ADDBA请求帧和所述ADDBA响应帧用于建立所述第一设备的多条 链路与所述第二设备的多条链路之间的多链路块确认对话。
如图11所示，图11是本申请实施例提供的一种第一设备发送端的结构示意图。该第一设备包括一个高MAC层和多条链路(如链路1和链路2)，链路包括一个低MAC层和一个PHY层。高MAC层包括一个全局缓存空间，在全局缓冲空间中可以维持一个缓冲队列，并为每个数据包分配全局序列号。低MAC层可选的包括一个局部缓冲空间，也可以不包括局部缓冲空间，并为每个数据包分配一个本地序列号。又如图12所示，图12是本申请实施例提供的一种第二设备的结构示意图。该第二设备接收端包括一个高MAC层和多条链路(如链路1和链路2)，链路包括一个低MAC层和一个PHY层。低MAC层可以包括一个局部缓冲空间和一个第一计分板，该第一计分板可以用于响应本条链路接收到的同一类型的数据包的确认。高MAC层包括一个全局缓存空间和一个第二计分板，在全局缓冲空间中可以维持一个重排序缓冲队列，第二计分板可以用于响应多链路实体接收到的同一类型的数据包的确认。
在块确认对话中，第一缓冲大小字段用于链路协商的第一计分板的大小，可选的，第一缓冲大小字段也可以用用于链路协商局部缓冲空间的大小。如果有n条链路，则需要n个第一缓存大小字段。另一种实施方式，存在一个第一缓冲大小字段，即给每条链路协商的第一计分板的大小相同，可选的局部缓冲空间的大小是相同的。第二缓冲大小字段用来给多链路实体协商的第二计分板和全局缓冲空间的大小，每个多链路实体只会协商一个第二缓冲大小字段，对应共享高MAC层的第二计分板和全局缓冲空间。
第一缓冲大小字段的大小可以为64、128或256。如果第一设备有3条链路，则可以增加第一缓冲大小A，第一缓冲大小B和第一缓冲大小C。第二缓冲大小的大小可以为1024，2048或4096等等。通常第二缓冲大小字段的大小大于第一缓冲大小字段的大小，但也有例外。
应注意，多链路实体指的是包含一个或多条链路的实体，该一个或多条链路共享一个MAC服务访问点(service access point，SAP)。链路指的是具有发送和接收功能的站点，比如包含一个PHY和一个MAC(如低MAC)。
如图13所示，图13是本申请实施例提供的一种ADDBA响应帧的示意图，该ADDBA响应帧可以包括块确认功能字段和块确认参数集字段等等。
其中，可以在ADDBA响应帧的块确认功能字段增加多链路块确认会话的相关功能，所述ADDBA响应帧包括块确认功能字段，该块确认功能字段包括用于指示多链路块确认会话的功能类型的信息。所述ADDBA响应帧中的所述信息指示所述多链路块确认会话为多链路块确认响应。又如图8所示，该块确认功能字段可以包括0-255字段值，例如，字段值0表示ADDBA请求的功能，字段值1表示ADDBA响应的功能，字段值2表示BA会话删除等等。该块确认功能字段还包括3-127、131和134-255字段值，这些字段值为保留字段值，可以使用该保留字段值指示多链路块确认会话的功能类型，该功能类型包括多链路块确认请求、多链路块确认响应、多链路块确认对话拆除等等。
其中，所述ADDBA响应帧可以包括第二块确认参数集字段，所述第二块确认参数集字段包括所述第二缓冲大小字段。如图9所示，图9是本申请实施例提供的一种块确认参数集字段的示意图。块确认参数集字段可以包括1比特的A-MSDU、2比特的块确认策 略、3比特的业务类型和10比特的缓冲大小，该10比特的缓冲大小字段可以用于指示全局缓冲空间的大小。各个字段的大小并不限定。
可选的，可以在ADDBA响应帧中增加一个多链路(Multi-link)元素，所述ADDBA响应帧包括多链路元素。如图10所示，图10是本申请实施例提供的一种括多链路元素的示意图。所述多链路元素包括元素号、长度字段以及指示字段。所述指示字段可以包括链路比特位图字段、至少一个第一缓冲大小字段。其中，第一缓冲大小字段的个数等于链路比特位图中置“1”值的比特个数，链路比特位图可以表示哪几条链路参与多链路BA会话的情况。例如，如果第1条链路参与多链路BA会话建立，第2条链路不参与多链路BA会话建立，第3条链路不参与多链路BA会话建立，第4条链路参与多链路BA会话建立，则比特位图可以表示1001。第二，所述指示字段可以包括链路数目字段、多条链路身份号字段以及至少一个第一缓冲大小字段。其中，链路身份号字段个数、第一缓冲大小字段的个数与链路数目字段的值相同，链路身份号字段用来指示哪些链路参与多链路BA会话建立。另外，多链路元素还包括多个块确认起始序列控制字段，块确认起始序列控制字段的个数等于参与多链路BA对话的链路个数。其中，上述指示字段不限于在多链路元素中携带，也可以在ADDBA请求帧或响应帧中已有的字段或元素中携带，例如多频段(Multi-Band)元素、或者ADDBA拓展元素等。
需要说明的是，一个或多个第一缓冲大小字段和第二缓冲大小字段还可以通过其他字段携带，比如第一缓冲大小字段也可以通过块确认参数集字段进行指示，第二缓冲大小字段也可以通过多链路元素进行指示，二者还可以通过其他方式指示，这里并不限定。
可选的，在第一设备接收第二设备发送的ADDBA响应帧之后，第一设备可以向第二设备返回用于响应所述ADDBA响应帧的确认帧Ack，然后第二设备接收第一设备发送的确认帧Ack。
经过步骤S601和S602之后，建立完成所述第一设备的多条链路与所述第二设备的多条链路之间的多链路块确认对话，然后执行下述操作：
S603，第一设备向第二设备发送数据包，第二设备接收第一设备发送的包含数据包的数据帧，该数据包可以为数据包MAC服务数据单元(MAC service data unit，MSDU)、或多个数据包MSDU聚合的聚合MAC服务数据单元(aggregate MAC service data unit，A-MSDU)，还可以发送包含MAC管理协议数据单元(MAC manage protocol data unit，MMPDU)的管理帧和控制帧。该数据包可以为服务质量(quality of service，QoS)数据包。
又如图11所示，第一设备的高MAC层维护一个全局缓冲空间，高MAC层分别对接收到的上层传递下来的数据包分配一个全局序列号。对于<接收地址，业务类型>相同的多个数据包，可以划分为同一组数据包，该同一组数据包可以共享12比特的序列号空间，范围从0至4095。当然还有其他分配全局序列号的方法，例如将发送给同一地址的数据包划为同一组数据包，该同一组数据包共享一个序列号空间，本发明不做限制。高MAC层每次接收到一个数据包(属于同一组数据包)，全局序列号增加1。例如，如果全局缓冲空间中有3个数据包，该3个数据包为同一组数据包，第一个数据包分配一个全局序列号1、第二数据包分配一个全局序列号2、第三数据包分配一个全局序列号3。其中，所述全局序列号为所述多链路实体分配给所述数据包的标识。
第一设备的链路的低MAC层可以从高MAC层的全局缓冲空间中取出多个数据包，并且分配本地序列号。同样，对于链路上的<接收地址，业务类型>相同的多个数据包，可以划分为同一组数据包，该同一组数据包可以共享12比特的序列号空间，范围从0至4095。当然还有其他分配本地序列号的方法，比如将发送给同一地址的数据包划为同一组数据包，该同一组数据包共享一个序列号空间，本发明不做限制。链路每次接收到一个数据包(属于同一组数据包)，本地序列号增加1。例如，如图9所示，2条链路上分别存在3个数据包，该3个数据包为同一组数据包，括号内的数字是本地序列号，括号外的数字是全局序列号，每条链路的低MAC层分别为3个数据包分配了一个本地序列号，本地序列号依次递增。其中，本地序列号为所述多条链路中发送所述数据包的链路分配给所述数据包的标识。
如图14所示，图14本申请实施例提供的一种MAC头的示意图。在分配完成全局序列号和本地序列号之后，每条链路的低MAC分别添加MAC头，MAC头可以包括帧控制字段、地址1字段(接收地址)、地址2字段(发送地址)、地址3字段、序列控制字段、地址4、QoS控制字段以及HT控制字段中的一个或多个字段。其中，2字节的序列控制字段可以包括12比特序列号以及4比特分片号。本地序列号和全局序列号的其中一个可以通过序列控制字段携带，另一个可以通过其他字段携带，例如在HT控制字段中，或者在帧载体中额外加一个序列控制字段。最后可以向第二设备发送数据包。
其中，第一设备可以根据所述ADDBA请求帧和所述ADDBA响应帧，维护多个第一发送窗口和一个第二发送窗口。所述多个第一发送窗口与所述第一设备的多条链路相对应，所述第二发送窗口与所述第一设备的多链路实体相对应。进一步的，每条链路维护一个第一发送窗口，一个所述第一发送窗口对应所述多条链路中的一条链路，一个所述第一发送窗口起始序号为WinStartO1,结束序号为WinEndO1，窗口大小为WinSizeO1，其中，所述WinSizeO1等于所述链路所对应的第一缓冲大小字段的确认值。并且，高MAC层也维护一个第二发送窗口，所述第二发送窗口起始序号为WinStartO2,结束序号为WinEndO2，窗口大小为WinSizeO2，其中，所述WinSizeO2等于通过所述ADDBA请求帧和ADDBA响应帧协商的所述第二缓冲大小字段的确认值。
第二设备接收到数据包之后，每条链路的PHY层将该数据包传递给该条链路的低MAC层。每条链路的低MAC层可以从每个数据包的MAC头中获取本地序列号，根据本地序列号维护一个第一计分板，该第一计分板用于响应本条链路接收到的同一类型的数据包的确认。通过第一计分板可以统计每条链路是否正确接收到数据包，如果正确接收到数据包，可以将该数据包统计为1，如果没有接收到数据包，则将该数据包统计为0。另外，ADDBA请求帧包括一个或多个第一块确认起始序列号控制字段，该第一块确认起始序列号控制字段包括第一初始序列号，所述第一初始序列号用于指示所述第二设备的第一接收窗口(可选的)和第一计分板的起始序列号的初始值，第一初始序列号的类型为本地序列号。链路可以按照该第一初始序列号，依次对该链路上接收到的数据包进行确认，最后形成一个第二设备确认的接收到的数据包的情况的块确认比特位图，并包含在局部块确认帧中返回给第一设备。其中，局部块确认帧用于响应本链路接收到的多个数据包的确认，该局部块确认帧是对链路上接收到的数据包的立即响应，也可以是对在该链路上接收到的 用来索引本地序列号的BAR帧的响应。局部块确认帧中的块确认比特位图的大小可以通过ADDBA请求帧和ADDBA响应帧中第一缓冲大小字段进行协商，对于同一个第一缓冲大小字段，可能存在不同长度的块确认比特位图，详见802.11ax协议。
其中，第二设备可以维护多个第一计分板，多个第一计分板与多条链路相对应，一个所述第一计分板的起始序号为WinStartR1，结束序号为WinEndR1；WinStartR1的初始值为ADDBA请求帧中的第一块确认起始序列号控制字段的第一初始序列号，第一计分板的大小WinSizeR1等于所对应的链路所对应的第一缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。WinStartR1和WinEndR1的位置会随着接收到的数据包进行移动，具体可以参考802.11-2016协议，这里不再赘述。WinStartR1决定了第二设备返回的局部块确认帧(比如压缩块确认帧或多站点块确认帧)的比特位图的起始序列号。
可选的，第二设备也可以根据所述ADDBA请求帧和所述ADDBA响应帧，维护多个第一接收窗口，第一接收窗口用于对接收到的数据包进行排序，然后依次递交给高MAC层。所述多个第一接收窗口与所述第二设备的所述多条链路相对应，进一步的，一个所述第一接收窗口对应所述多条链路中的一条链路，所述第一接收窗口起始序号为WinStartB1,结束序号为WinEndB1，窗口大小为WinSizeB1。其中，WinStartB1的初始值为ADDBA请求帧中的第一块确认起始序列号控制字段的第一初始序列号，所述WinSizeB1等于所述链路所对应的第一缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。WinStartB1和WinEndB1的位置会随着接收到的数据包进行移动，具体可以参考802.11-2016协议，这里不再赘述。一种可能的实施方式，第二设备不需要根据所述ADDBA请求帧和所述ADDBA响应帧维护多个第一接收窗。
可选的，第二设备的每条链路的低MAC层可以按照多个数据包的本地序列号的顺序，依次将多个数据包传递给高MAC层，另外一种实施方式，每条链路的低MAC层直接将接收到的多个数据包传递给高MAC层。
然后，高MAC层从每个数据包中获取全局序列号，根据全局序列号维护一个第二计分板，该第二计分板用于响应多链路实体接收到的同一类型的数据包的确认。通过第二计分板可以统计多链路实体是否正确接收到数据包。如果正确接收到数据包，可以将该数据包统计为1，如果没有接收到数据包，则将该数据包统计为0。ADDBA请求帧包括第二块确认起始序列号控制字段，该第二块确认起始序列号控制字段包括第二初始序列号，所述第二初始序列号用于指示所述第二设备的第二接收窗口和第二计分板的的起始序列号的初始值，所述第二初始序列号的类型为全局序列号。高MAC层可以按照该第二初始序列号，依次对多个数据包进行确认，最后形成一个第二设备确认的接收到的数据包的情况的块确认比特位图，并包含在全局块确认帧中返回给第一设备。全局块确认帧为多链路实体接收到的用于索引全局序列号的块确认请求帧的响应，全局块确认帧中的块确认比特位图的大小取决于通过ADDBA请求帧和ADDBA响应帧进行协商的第二缓冲大小字段，对于同一个第二缓冲大小字段，可能存在不同长度的块确认比特位图。可选的，全局块确认帧为多链路实体响应接收到的多个数据包的确认。
其中，第二设备可以维护多个第二计分板，所述第二计分板与所述多链路实体相对应，所述第二计分板的起始序号为WinStartR2,结束序号为WinEndR2，窗口大小为 WinSizeR2，其中，WinStartR2的初始值为ADDBA请求帧中的第二块确认起始序列号控制字段的第二初始序列号，所述WinSizeR2等于所述第二缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。WinStartR2和WinEndR2的位置会随着接收到的数据包进行移动，具体可以参考802.11-2016协议，这里不再赘述。WinStartR2决定了第二设备返回的全局块确认帧(比如压缩块确认帧或多站点块确认帧)的比特位图的起始序列号。
其中，第二设备也可以根据所述ADDBA请求帧和所述ADDBA响应帧，维护一个第二接收窗口，该第二接收窗口可以用于在全局缓冲空间中对多链路实体接收到的数据包按全局序列号进行排序，并将数据包按照全局序列号的顺序依次传递给第二设备的MAC层的上一层。所述第二接收窗口与所述第二设备的所述链路实体相对应。进一步的，所述第二接收窗口起始序号为WinStartB2,结束序号为WinEndB2，窗口大小为WinSizeB2，其中，WinStartB2的初始值为ADDBA请求帧中的第二块确认起始序列号控制字段的第二初始序列号，所述WinSizeB2等于所述第二缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。WinStartB2和WinEndB2的位置可以随着接收到的数据包进行移动，具体可以参考802.11-2016协议，这里不再赘述。
S604，第一设备向第二设备发送块确认请求帧或多用户块确认请求触发帧。第二设备接收第一设备发送的块确认请求帧或多用户块确认请求触发帧。该步骤是可选的，取决发送的数据包的确认策略，如果策略是块确认，则需要S604步骤。如果是正常确认或者隐式块请求确认请求策略，则不要S604步骤，此时数据包此时索引的立即反馈。
如图15所示，图15是本申请实施例提供的一种块确认请求帧或多用户块确认请求触发帧的示意图。块确认请求帧或多用户块确认请求触发帧可以包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号，所述块确认请求帧或所述多用户块确认请求触发帧还包括BAR控制字段，该BAR控制字段包括第一指示信息，所述第一指示信息用于所述起始序列号的类型，所述起始序列号的类型包括本地序列号或全局序列号。块确认请求帧(例如块确认请求帧的变种，包括多业务类型BAR、拓展压缩BAR、压缩BAR和组播BAR或基本BAR等等)或多用户块确认请求触发帧包括全局块确认请求帧和局部块确认请求帧。可以根据第一指示信息指示的BAR类型确定块确认请求帧为全局块确认请求帧或局部块请求确认帧。块确认请求帧(例如块确认请求帧的变种，包括多业务类型BAR、拓展压缩BAR、压缩BAR和组播BAR或基本BAR等等)或多用户块确认请求触发帧中的起始序列号控制字段中的起始序列号为第一指示信息指示的起始本地序列号或起始全局序列号。
S605，第二设备向第一设备发送响应所述数据包的确认消息，所述第一设备接收所述第二设备回复的响应所述数据包的确认消息，所述确认消息包括块确认帧，块确认帧包括全局块确认帧和局部块确认帧，该块确认帧可以为压缩块确认帧或多站点块确认帧等等。
如图16所示，图16本申请实施例提供的一种块确认帧的示意图，该块确认帧可以包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号和块确认比特位图；所述块确认比特位图用于指示所述第二设备接收到的所述数据包的接收情况，所述块确认帧(包括块确认帧的变种，比如基本块确认、压缩块确认、多站点块确认和多业务类型块确 认等等)还可以包括BA控制字段，所述BA控制字段包括第二指示信息，所述第二指示信息用于指示块确认帧中的起始序列控制字段中的起始序列号的类型为本地序列号或全局序列号，且所述块确认比特位图中的第一比特对应所述起始序列号，所述比特位图中的每一比特对应的序列号的类型相同。块确认帧(例如块确认帧的变种，包括基本块确认、压缩块确认、多站点块确认和多业务类型块确认等等)包括全局块确认帧和局部块确认帧。可以根据第二指示信息指示的BA类型确定块确认帧为全局块确认帧或局部块确认帧。
其中，块确认帧可以包括块确认比特位图，若所述块确认比特位图所对应的序列为所述本地序列号，则所述块确认比特位图中的第一比特所对应的序列号为所述WinStartR1或者起始序列控制字段中的本地起始序列号；若所述块确认比特位图所对应的序列为所述全局序列号，则所述块确认比特位图中的第一比特所对应的序列号为所述WinStartR2或者起始序列控制字段中的全局起始序列号。
在本申请实施例中，通过ADDBA请求帧和ADDBA响应帧协商，第一设备和第二设备为多条链路的每条链路分配一个局部缓冲空间，以及为高MAC层分配一个全局缓冲空间。从而建立多链路的块确认对话。并且，第一设备发送的数据包的MAC中包括本地序列号和全局序列号，这样第一设备可以在多条链路上向第二设备发送同一类型的数据包，从而提高的数据的通信效率。
如图17所示，图17是本申请实施例提供的一种数据帧传输方法的流程示意图。本申请实施例中步骤至少包括：
S1701，第一设备向第二设备发送消息帧，第二设备接收第一设备发送的消息帧，所述消息帧包括第一指示信息，所述第一指示信息用于指示所述多条链路中的主链路。包括以下两种可选的方式：
第一种可选的方式，所述第一指示信息为特殊元素，第一设备可以通过主链路向第二设备发送消息帧，该消息帧可以携带一个特殊元素(例如与多链路信息相关的元素)，该特殊元素仅携带在主链路发送的消息帧中，该特殊元素用于指示传输该消息帧的链路为主链路。其中，消息帧可以为管理帧中的信标帧。
第二种可选的方式，所述第一指示信息为链路序号，第一设备可以通过非主链路向第二设备发送消息帧，所述消息帧可以携带缩减版邻居汇报(reduced Neighbor report)元素或多频段(Multi-band)元素，缩减版邻居汇报元素或多频段元素包括链路序号，该链路序号用于指示多条链路的主链路。
S1702，第一设备通过所述主链路向所述第二设备发送第二指示信息，或者通过主链路与第二设备进行目标唤醒时间(target wake up time，TWT)协商。其中，所述第二指示信息指示多条链路的工作状态或休眠状态。TWT协商用于第一设备和第二设备协商一个或多个服务窗口，在服务窗口内进行工作，而在服务窗口外可以进行休眠，从而节省功率。
具体实现中，第二指示信息可以携带在MAC头中的高吞吐量(high throughput，HT)控制字段的操作模式指示字段(operating mode indication，OMI)或者操作模式通知帧(operating mode notification)中。所述第二指示信息可以为比特位图，例如，若第n比 特为数值1表示第n条链路即将处于休眠状态或关闭状态，若第n比特置为数值0表示第n条链路即将处于工作状态。第二指示信息可以多条链路序号，如果第二指示信息包括链路序号1，则链路序号1对应的链路处于休眠状态或关闭状态，反之亦然。
如图18所示，图18是本申请实施例提供的一种用于TWT协商的TWT元素的示意图，该TWT元素包括元素号、长度、控制和TWT参数信息字段。其中，控制字段包括NDP paging指示、响应者功率节省模式、协商类型、TWT信息帧禁用等字段。协商类型可以包括单用户TWT类型和广播TWT类型。如图19所示，图19是本申请实施例提供的一种单用户TWT类型的示意图。当协商类型指示单用户TWT类型，单用户TWT参数的信息字段包括请求类型、目标唤醒时间、TWT组分配、最小TWT醒来时长、TWT醒来时长小数，TWT信道、NDP(Null data packet，空数据包)寻呼等等。如图20所示，图20是本申请实施例提供的一种广播TWT类型的示意图，当协商类型指示广播TWT类型时，广播TWT参数的信息字段包括请求类型、目标唤醒时间、TWT组分配、最小TWT醒来时长、TWT醒来时长小数、TWT信道以及NDP(Null data packet，空数据包)寻呼。其中，请求类型字段包括TWT醒来间隔的指示字段，TWT醒来间隔＝TWT醒来时长小数*2(TWT醒来间隔指数)。
其中，可以在TWT元素的控制字段中增加多链路指示，该多链路指示要用于指示广播TWT参数信息或单用户TWT参数信息可以应用在不同与传输该TWT元素的链路的另一条链路上。具体应用到哪一条链路可以通过以下方式进行指示：
针对于于单用户TWT：
第一种可选的方式，在单用户TWT参数的信息字段中增加操作种类(operating class)字段，结合操作种类字段和TWT信道字段一起指示TWT元素应用在多条链路中的哪一条链路。
第二种可选的方式，在单用户TWT参数的信息字段和广播TWT参数的信息字段中增加一个或多条链路序号，该链路序号用于指示该TWT元素应用在多条链路中的哪一条链路上。
或者，通过链路序号比特位图指示该TWT元素应用在多条链路中的哪一条链路上。例如，如果链路序号比特位图为0100，则第2个比特置1可以表示TWT元素可以应用在第2条链路上。
针对于广播TWT：
第一种可选的方式，在广播TWT参数的信息字段中增加操作种类(operating class)字段和TWT信道字段，指示TWT元素应用在多条链路中的哪一条链路。
第二种可选的方式，在广播TWT参数的信息字段中增加一个或多条链路序号，该链路序号用于指示该TWT元素应用在多条链路中的哪一条链路上。或者，通过链路序号比特位图指示该TWT元素应用在多条链路中的哪一条链路上。例如，如果链路序号比特位图为0100，则第2个比特置1可以表示TWT元素可以应用在第2条链路上。
在本申请实施例中，第一设备通过向第二设备指示多条链路中的主链路，并通过主链路来指示多条链路的工作状态或休眠状态，或者通过主链路进行TWT协商，从而起到节省功率的效果。
上述详细阐述了本申请实施例的方法，下面提供了本申请实施例的装置。
请参见图21，图21是本申请实施例提供的一种第一通信装置的结构示意图，该第一通信装置包括发送模块2101、接收模块2102以及处理模块2103，其中，各个模块的详细描述如下。
发送模块2101，用于向第二设备发送ADDBA请求帧，所述ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；所述第二设备和第一设备为包含一条或多条链路的多链路实体；
接收模块2102，用于接收所述第二设备发送的ADDBA响应帧，所述ADDBA响应帧包括至少一个所述第一缓冲大小字段的确认值和所述第二缓冲大小字段的确认值；
处理模块2103，用于根据所述ADDBA请求帧和所述ADDBA响应帧，建立所述第一设备的多条链路与所述第二设备的多条链路之间的多链路块确认对话；
其中，一个所述第一缓冲大小字段用于指示所述第一设备和所述第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，所述第二缓冲大小字段用于指示所述第一设备和所述第二设备维护的一个全局缓冲空间的大小。
可选的，处理模块2103，用于根据所述ADDBA请求帧和所述ADDBA响应帧，维护多个第一发送窗口和一个第二发送窗口，其中，所述多个第一发送窗口与所述第一设备的多条链路相对应，所述第二发送窗口与所述第一设备的多链路实体相对应。
其中，一个所述第一发送窗口对应所述多条链路中的一条链路，一个所述第一发送窗口起始序号为WinStartO1,结束序号为WinEndO1，窗口大小为WinSizeO1，其中，所述WinSizeO1等于所述链路所对应的第一缓冲大小字段的确认值；
所述第二发送窗口起始序号为WinStartO2,结束序号为WinEndO2，窗口大小为WinSizeO2，其中，所述WinSizeO2等于通过所述ADDBA请求帧和ADDBA响应帧协商的所述第二缓冲大小字段的确认值。
处理模块，用于根据所述ADDBA请求帧和所述ADDBA响应帧，维护多个第一发送窗口和一个第二发送窗口，其中，所述多个第一发送窗口与所述第一设备的多条链路相对应，所述第二发送窗口与所述第一设备的多链路实体相对应。
其中，一个所述第一发送窗口对应所述多条链路中的一条链路，一个所述第一发送窗口起始序号为WinStartO1,结束序号为WinEndO1，窗口大小为WinSizeO1，其中，所述WinSizeO1等于所述链路所对应的第一缓冲大小的确认值；
所述第二发送窗口起始序号为WinStartO2,结束序号为WinEndO2，窗口大小为WinSizeO2，其中，所述WinSizeO2等于通过所述ADDBA请求帧和ADDBA响应帧协商的所述第二缓冲大小的确认值。
其中，所述ADDBA请求帧包括第一块确认起始序列号控制字段和第二块确认起始序列号控制字段；
所述第一块确认起始序列号控制字段用于指示所述第二设备的链路的第一计分板的起始序列号的第一初始序列号，所述第一初始序列号的类型为本地序列号；
所述第二块确认起始序列号控制字段用于指示所述第二设备的多链路实体的第二计 分板的起始序列号的第二初始序列号，所述第二初始序列号的类型为全局序列号。
其中，所述ADDBA请求帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的参考值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的参考值中的至少一个；所述ADDBA响应帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的确认值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的确认值中的至少一个；
所述ADDBA请求帧包括第一块确认参数集字段，所述第一块确认参数集字段包括所述第二缓冲大小字段的参考值；
所述ADDBA响应帧包括第二块确认参数集字段，所述第二块确认参数集字段包括所述第二缓冲大小字段的确认值。
可选的，发送模块2101，用于向所述第二设备发送数据包；接收模块2102，用于接收所述第二设备回复的响应所述数据包的确认消息；
其中，所述数据包包括本地序列号和全局序列号，所述本地序列号为所述多条链路中发送所述数据包的链路分配给所述数据包的标识，所述全局序列号为所述多链路实体分配给所述数据包的标识。
可选的，发送模块2101，还用于向所述第二设备发送块确认请求帧或多用户块确认请求触发帧，所述块确认请求帧或所述多用户块确认请求触发帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号；
所述块确认请求帧或所述多用户块确认请求触发帧还包括第一指示信息，所述第一指示信息用于指示所述起始序列号的类型，所述起始序列号的类型包括本地序列号或全局序列号。
其中，接收模块2202，还用于接收所述第二设备发送的块确认帧，所述块确认帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号和块确认比特位图；所述块确认比特位图用于指示所述第二设备接收到的所述数据包的接收情况；
所述块确认帧还包括块确认BA控制字段，所述BA控制字段包括所述第二指示信息，所述第二指示信息用于指示所述起始序列号的类型，所述起始序列号的类型为本地序列号或全局序列号，且所述块确认比特位图中的第一比特对应所述起始序列号。
在另一个实施例中：
发送模块2101，用于向第二设备发送消息帧，消息帧包括第一指示信息，第一指示信息用于指示多条链路中的主链路。发送模块2101，用于通过主链路向第二设备发送第二指示信息，第二指示信息指示多条链路的工作状态或休眠状态，或者通过主链路与第二设备进行TWT协商。
其中，第一指示信息为特殊元素，第一设备可以通过主链路向第二设备发送消息帧，该消息帧可以携带一个特殊元素，该特殊元素仅携带在主链路发送的消息帧中，该特殊元素用于指示传输该消息帧的链路为主链路。通过特殊元素指示主链路，使得其他链路处于休眠状态或关闭状态，从而实现节省功率。
其中，第一指示信息为链路序号，第一设备可以通过非主链路向第二设备发送消息帧，消息帧可以携带缩减版邻居汇报元素或多频段元素，缩减版邻居汇报元素或多频段元素包 括链路序号，该链路序号用于指示多条链路的主链路。
其中，在单用户TWT参数的信息字段和广播TWT参数的信息字段中增加操作种类字段，结合操作种类字段和TWT信道字段一起指示TWT元素应用在多条链路中的哪一条链路。可以在广播TWT参数信息字段中增加指示值，该指示值用于指示该TWT元素应用在多条链路中的哪一条链路上。
其中，在单用户TWT参数的信息字段和广播TWT参数的信息字段中增加一个或多条链路序号，该链路序号用于指示该TWT元素应用在多条链路中的哪一条链路上。或者，通过链路序号比特位图指示该TWT元素应用在多条链路中的哪一条链路上。
需要说明的是，各个模块的实现还可以对应参照图6和图17所示的方法实施例的相应描述，执行上述实施例中第一设备所执行的方法和功能。
请参见图22，图22是本申请实施例提供的一种第二通信装置的结构示意图，该第二通信装置包括接收模块2201、发送模块2202以及处理模块2203，其中，各个模块的详细描述如下。
接收模块2201，用于接收第一设备发送ADDBA请求帧，所述ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；所述第一设备和第二设备为包含一条或多条链路的多链路实体；
发送模块2202，用于向所述第一设备发送的ADDBA响应帧，所述ADDBA响应帧包括所述至少一个第一缓冲大小字段的确认值和所述第二缓冲大小字段的确认值；
处理模块2203，用于根据所述ADDBA请求帧和所述ADDBA响应帧，建立所述第一设备的多条链路与所述第二设备的多条链路之间的多链路块确认对话；
其中，一个所述第一缓冲大小字段用于指示所述第一设备和所述第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，所述第二缓冲大小字段用于指示所述第一设备和所述第二设备维护的一个全局缓冲空间的大小。
处理模块2203，用于根据所述ADDBA请求帧和所述ADDBA响应帧，维护一个接收窗口，其中，所述接收窗口与所述第二设备的所述链路实体相对应；
其中，所述接收窗口起始序号为WinStartB2,结束序号为WinEndB2，窗口大小为WinSizeB2，其中，所述WinSizeB2等于所述第二缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。
其中，所述ADDBA请求帧包括第一块确认起始序列号控制字段和第二块确认起始序列号控制字段；
所述第一块确认起始序列号控制字段用于指示所述第二设备的链路的第一计分板的起始序号的第一初始序列号，所述第一初始序列号的类型为本地序列号；
所述第二块确认起始序列号控制字段用于指示所述第二设备的多链路实体的第二计分板的起始序号的第二初始序列号，所述第二初始序列号的类型为全局序列号。
其中，所述ADDBA请求帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的参考值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的参考值中的至少一个；
所述ADDBA响应帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的确认值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的确认值中的至少一个；
所述ADDBA请求帧包括第一块确认参数集字段，所述第一块确认参数集字段包括所述第二缓冲大小字段的参考值；
所述ADDBA响应帧包括第二块确认参数集字段，所述第二块确认参数集字段包括所述第二缓冲大小字段的确认值。
可选的，接收模块2201，还用于接收所述第一设备发送数据包；发送模块2202，还用于向所述第一设备发送用于响应所述数据包的确认消息；
其中，所述数据包包括本地序列号和全局序列号，所述本地序列号为所述多条链路中发送所述数据包的链路分配给所述数据包的标识，所述全局序列号为所述多链路实体分配给所述数据包的标识。
可选的，接收模块2201，还用于接收所述第一设备发送的块确认请求帧或多用户块确认请求触发帧，所述块确认请求帧或所述多用户块确认请求触发帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号；
其中，块确认请求帧或所述多用户块确认请求触发帧还包括第一指示信息，所述第一指示信息用于指示所述起始序列号的类型，所述起始序列号的类型包括本地序列号或全局序列号。
处理模块2203，用于维护多个第一计分板和一个第二计分板；所述多个第一计分板与所述多条链路相对应，所述第二计分板与所述多链路实体相对应；
一个所述第一计分板的起始序号为WinStartR1，结束序号为WinEndR1；计分板大小WinSizeR1等于所对应的链路所对应的所述第一缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值；
所述第二计分板的起始序号为WinStartR2,结束序号为WinEndR2，计分板大小为WinSizeR2，其中，所述WinSizeR2等于所述第二缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。
其中，所述确认消息为块确认帧；
所述块确认帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号和块确认比特位图；所述块确认比特位图用于指示所述第二设备接收到的所述数据包的接收情况；
所述块确认帧还包括块确认BA控制字段，所述BA控制字段包括所述第二指示信息，所述第二指示信息用于指示所述起始序列号的类型，所述起始序列号的类型为本地序列号或全局序列号，且所述块确认比特位图中的第一比特对应所述起始序列号。
其中，若所述块确认比特位图所对应的序列为所述本地序列号，则所述块确认比特位图中的第一比特所对应的序列号为所述WinStartR1；
若所述块确认比特位图所对应的序列为所述全局序列号，则所述块确认比特位图中的第一比特所对应的序列号为所述WinStartR2。
在另一个实施例中：
接收模块2101，用于接收第一设备发送消息帧，消息帧包括第一指示信息，第一指示信息用于指示多条链路中的主链路，接收模块2201，用于接收第一设备通过主链路发送第二指示信息，第二指示信息指示多条链路的工作状态或休眠状态，或者通过主链路与第一设备进行TWT协商。
其中，第一指示信息为特殊元素，第二设备可以接收第一设备通过主链路发送的消息帧，该消息帧可以携带一个特殊元素，该特殊元素仅携带在主链路发送的消息帧中，该特殊元素用于指示传输该消息帧的链路为主链路。
其中，第一指示信息为链路序号，第二设备可以接收第一设备通过非主链路发送的消息帧，消息帧可以携带缩减版邻居汇报元素或多频段元素，缩减版邻居汇报元素或多频段元素包括链路序号，该链路序号用于指示多条链路的主链路。
需要说明的是，各个模块的实现还可以对应参照图6和图17所示的方法实施例的相应描述，执行上述实施例中第二设备所执行的方法和功能。
请继续参考图23，图23是本申请实施例提出的一种第一设备的结构示意图。如图23所示，该第一设备可以包括：至少一个处理器2301，至少一个通信接口2302，至少一个存储器2303和至少一个通信总线2304。
其中，处理器2301可以是中央处理器单元，通用处理器，数字信号处理器，专用集成电路，现场可编程门阵列或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。所述处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理器和微处理器的组合等等。通信总线2304可以是外设部件互连标准PCI总线或扩展工业标准结构EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图23中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。通信总线2304用于实现这些组件之间的连接通信。其中，本申请实施例中设备的通信接口2302用于与其他节点设备进行信令或数据的通信。存储器2303可以包括易失性存储器，例如非挥发性动态随机存取内存(nonvolatile random access memory，NVRAM)、相变化随机存取内存(phase change RAM，PRAM)、磁阻式随机存取内存(magetoresistive RAM，MRAM)等，还可以包括非易失性存储器，例如至少一个磁盘存储器件、电子可擦除可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、闪存器件，例如反或闪存(NOR flash memory)或是反及闪存(NAND flash memory)、半导体器件，例如固态硬盘(solid state disk，SSD)等。存储器2303可选的还可以是至少一个位于远离前述处理器2301的存储装置。存储器2303中可选的还可以存储一组程序代码，且处理器2301可选的还可以执行存储器2303中所执行的程序。
通信接口2302向第二设备发送ADDBA请求帧，所述ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；所述第一设备和所述第二设备为包含一条或多条链路的多链路实体；
通信接口2302接收所述第二设备发送的ADDBA响应帧，所述ADDBA响应帧包括所述至少一个第一缓冲大小字段的确认值和所述第二缓冲大小字段的确认值；
根据所述ADDBA请求帧和所述ADDBA响应帧，建立所述第一设备的多条链路与所述第二设备的多条链路之间的多链路块确认对话；
其中，一个所述第一缓冲大小字段用于指示所述第一设备和所述第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，所述第二缓冲大小字段用于指示所述第一设备和所述第二设备维护的一个全局缓冲空间的大小。
可选的，处理器2301还用于执行如下操作：
根据所述ADDBA请求帧和所述ADDBA响应帧，所述第一设备维护多个第一发送窗口和一个第二发送窗口，其中，所述多个第一发送窗口与所述第一设备的多条链路相对应，所述第二发送窗口与所述第一设备的多链路实体相对应；
其中，一个所述第一发送窗口对应所述多条链路中的一条链路，一个所述第一发送窗口起始序号为WinStartO1,结束序号为WinEndO1，窗口大小为WinSizeO1，其中，所述WinSizeO1等于所述链路所对应的第一缓冲大小的确认值；
所述第二发送窗口起始序号为WinStartO2,结束序号为WinEndO2，窗口大小为WinSizeO2，其中，所述WinSizeO2等于通过所述ADDBA请求帧和ADDBA响应帧协商的所述第二缓冲大小的确认值。
其中，所述ADDBA请求帧包括至少一个第一块确认起始序列号控制字段和第二块确认起始序列号控制字段；
所述第一块确认起始序列号控制字段用于指示所述第二设备的链路的第一计分板的起始序列号的第一初始序列号，所述第一初始序列号的类型为本地序列号；
所述第二块确认起始序列号控制字段用于指示所述第二设备的多链路实体的第二计分板的起始序列号的第二初始序列号，所述第二初始序列号的类型为全局序列号。
其中，所述ADDBA请求帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的参考值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的参考值中的至少一个；
所述ADDBA响应帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的确认值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的确认值中的至少一个；
所述ADDBA请求帧包括第一块确认参数集字段，所述第一块确认参数集字段包括所述第二缓冲大小字段的参考值；
所述ADDBA响应帧包括第二块确认参数集字段，所述第二块确认参数集字段包括所述第二缓冲大小字段的确认值。
可选的，处理器2301还用于执行如下操作：
通信接口2302向所述第二设备发送数据包；
通信接口2302接收所述第二设备回复的响应所述数据包的确认消息；
所述数据包包括本地序列号和全局序列号，所述本地序列号为所述多条链路中发送所述数据包的链路分配给所述数据包的标识，所述全局序列号为所述多链路实体分配给所述数据包的标识。
可选的，处理器2301还用于执行如下操作：
通信接口2302向所述第二设备发送块确认请求帧或多用户块确认请求触发帧，所述块确认请求帧或所述多用户块确认请求触发帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号；
所述块确认请求帧或所述多用户块确认请求触发帧还包括第一指示信息，所述第一指示信息用于指示所述起始序列号的类型，所述起始序列号的类型包括本地序列号或全局序列号。
可选的，处理器2301还用于执行如下操作：
接收所述第二设备发送的块确认帧，所述块确认帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号和块确认比特位图；所述块确认比特位图用于指示所述第二设备接收到的所述数据包的接收情况；
所述块确认帧还包括块确认BA控制字段，所述BA控制字段包括所述第二指示信息，所述第二指示信息用于指示所述起始序列号的类型，所述起始序列号的类型为本地序列号或全局序列号，且所述块确认比特位图中的第一比特对应所述起始序列号。
在另一个实施例中：
通过通信接口2302向第二设备发送消息帧，消息帧包括第一指示信息，第一指示信息用于指示多条链路中的主链路。通过主链路向第二设备发送第二指示信息，第二指示信息指示多条链路的工作状态或休眠状态，或者通过主链路与第二设备进行TWT协商。
其中，第一指示信息为特殊元素，第一设备可以通过主链路向第二设备发送消息帧，该消息帧可以携带一个特殊元素，该特殊元素仅携带在主链路发送的消息帧中，该特殊元素用于指示传输该消息帧的链路为主链路。通过特殊元素指示主链路，使得其他链路处于休眠状态或关闭状态，从而实现节省功率。
其中，第一指示信息为链路序号，第一设备可以通过非主链路向第二设备发送消息帧，消息帧可以携带缩减版邻居汇报元素或多频段元素，缩减版邻居汇报元素或多频段元素包括链路序号，该链路序号用于指示多条链路的主链路。
其中，在单用户TWT参数的信息字段和广播TWT参数的信息字段中增加操作种类字段，结合操作种类字段和TWT信道字段一起指示TWT元素应用在多条链路中的哪一条链路。可以在广播TWT参数信息字段中增加指示值，该指示值用于指示该TWT元素应用在多条链路中的哪一条链路上。
其中，在单用户TWT参数的信息字段和广播TWT参数的信息字段中增加一个或多条链路序号，该链路序号用于指示该TWT元素应用在多条链路中的哪一条链路上。或者，通过链路序号比特位图指示该TWT元素应用在多条链路中的哪一条链路上。
进一步的，处理器还可以与存储器和通信接口相配合，执行上述申请实施例中第一设备的操作。
请继续参考图24，图24是本申请实施例提出的一种第二设备的结构示意图。如图所示，该第二设备可以包括：至少一个处理器2401，至少一个通信接口2402，至少一个存储器2403和至少一个通信总线2404。
其中，处理器2401可以是前文提及的各种类型的处理器。通信总线2404可以是外设 部件互连标准PCI总线或扩展工业标准结构EISA总线等。所述总线可以分为地址总线、数据总线、控制总线等。为便于表示，图24中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。通信总线2404用于实现这些组件之间的连接通信。其中，本申请实施例中设备的通信接口2402用于与其他节点设备进行信令或数据的通信。存储器2403可以是前文提及的各种类型的存储器。存储器2403可选的还可以是至少一个位于远离前述处理器2401的存储装置。存储器2403中存储一组程序代码，且处理器2401执行存储器2403中上述OAM所执行的程序。
通过通信接口2402接收第一设备发送ADDBA请求帧，所述ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；所述第一设备和所述第二设备为包含一条或多条链路的多链路实体；
通过通信接口2402向所述第一设备发送的ADDBA响应帧，所述ADDBA响应帧包括多个所述第一缓冲大小字段的确认值和所述第二缓冲大小字段的确认值；
根据所述ADDBA请求帧和所述ADDBA响应帧，建立所述第一设备的多条链路与所述第二设备的多条链路之间的多链路块确认对话；
其中，一个所述第一缓冲大小字段用于指示所述第一设备和所述第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，所述第二缓冲大小字段用于指示所述第一设备和所述第二设备维护的一个全局缓冲空间的大小。
可选的，处理器2401还用于执行如下操作：
根据所述ADDBA请求帧和所述ADDBA响应帧，所述第二设备维护一个接收窗口，其中，所述接收窗口与所述第二设备的所述链路实体相对应；
其中，所述接收窗口起始序号为WinStartB2,结束序号为WinEndB2，窗口大小为WinSizeB2，其中，所述WinSizeB2等于所述第二缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。
可选的，处理器2401还用于执行如下操作：
根据ADDBA请求帧和ADDBA响应帧，第二设备维护多个第一接收窗口和一个第二接收窗口，其中，多个第一接收窗口与第二设备的多条链路相对应，第二接收窗口与第二设备的链路实体相对应。
其中，所述ADDBA请求帧包括第一块确认起始序列号控制字段和第二块确认起始序列号控制字段；
所述第一块确认起始序列号控制字段用于指示所述第二设备的链路的第一计分板的起始序号的第一初始序列号，所述第一初始序列号的类型为本地序列号；
所述第二块确认起始序列号控制字段用于指示所述第二设备的多链路实体的第二计分板的起始序号的第二初始序列号，所述第二初始序列号的类型为全局序列号。
其中，所述ADDBA请求帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的参考值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的参考值中的至少一个；
所述ADDBA响应帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的确认值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲 大小字段的确认值中的至少一个；
所述ADDBA请求帧包括第一块确认参数集字段，所述第一块确认参数集字段包括所述第二缓冲大小字段的参考值；
所述ADDBA响应帧包括第二块确认参数集字段，所述第二块确认参数集字段包括所述第二缓冲大小字段的确认值。
可选的，处理器2401还用于执行如下操作：
通过通信接口2402接收所述第一设备发送数据包；
通过通信接口2402向所述第一设备发送用于响应所述数据包的确认消息；
所述数据包包括本地序列号和全局序列号，所述本地序列号为所述多条链路中发送所述数据包的链路分配给所述数据包的标识，所述全局序列号为所述多链路实体分配给所述数据包的标识。
可选的，处理器2401还用于执行如下操作：
通过通信接口2402接收所述第一设备发送的块确认请求帧或多用户块确认请求触发帧，所述块确认请求帧或所述多用户块确认请求触发帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号；
所述块确认请求帧或所述多用户块确认请求触发帧还包括第一指示信息，所述第一指示信息用于指示所述起始序列号的类型，所述起始序列号的类型包括本地序列号或全局序列号。
可选的，处理器2401还用于执行如下操作：
维护多个第一计分板和一个第二计分板；所述多个第一计分板与所述多条链路相对应，所述第二计分板与所述多链路实体相对应；
一个所述第一计分板的起始序号为WinStartR1，结束序号为WinEndR1；计分板大小WinSizeR1等于所对应的链路所对应的第一缓冲大小的确认值与最大长度的块确认比特位图中的较小值；
所述第二计分板的起始序号为WinStartR2,结束序号为WinEndR2，计分板大小为WinSizeR2，其中，所述WinSizeR2等于所述第二缓冲大小的确认值与最大长度的块确认比特位图中的较小值。
其中，所述确认消息为块确认帧；
所述块确认帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号和块确认比特位图；所述块确认比特位图用于指示所述第二设备接收到的所述数据包的接收情况；
所述块确认帧还包括块确认BA控制字段，所述BA控制字段包括所述第二指示信息，所述第二指示信息用于指示所述起始序列号的类型，所述起始序列号的类型为本地序列号或全局序列号，且所述块确认比特位图中的第一比特对应所述起始序列号。
其中，若所述块确认比特位图所对应的序列为所述本地序列号，则所述块确认比特位图中的第一比特所对应的序列号为所述WinStartR1；
若所述块确认比特位图所对应的序列为所述全局序列号，则所述块确认比特位图中的第一比特所对应的序列号为所述WinStartR2。
在另一个实施例中：
通过通信接口2402接收第一设备发送消息帧，消息帧包括第一指示信息，第一指示信息用于指示多条链路中的主链路。通过通信接口2402接收第一设备通过主链路发送第二指示信息，第二指示信息指示多条链路的工作状态或休眠状态，或者通过主链路与第一设备进行TWT协商。
其中，第一指示信息为特殊元素，第二设备可以接收第一设备通过主链路发送的消息帧，该消息帧可以携带一个特殊元素，该特殊元素仅携带在主链路发送的消息帧中，该特殊元素用于指示传输该消息帧的链路为主链路。
其中，第一指示信息为链路序号，第二设备可以接收第一设备通过非主链路发送的消息帧，消息帧可以携带缩减版邻居汇报元素或多频段元素，缩减版邻居汇报元素或多频段元素包括链路序号，该链路序号用于指示多条链路的主链路。
进一步的，处理器还可以与存储器和通信接口相配合，执行上述申请实施例中第二设备的操作。
本申请实施例还提供了一种芯片系统，该芯片系统包括处理器，用于支持第一设备或第二设备以实现上述任一实施例中所涉及的功能，例如生成或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，所述芯片系统还可以包括存储器，所述存储器，用于第一设备或第二设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包含芯片和其他分立器件。
本申请实施例还提供了一种处理器，用于与存储器耦合，用于执行上述各实施例中任一实施例中涉及第一设备或第二设备的任意方法和功能。
本申请实施例还提供了一种包含指令的计算机程序产品，其在计算机上运行时，使得计算机执行执行上述各实施例中任一实施例中涉及第一设备或第二设备的任意方法和功能。
本申请实施例还提供了一种装置，用于执行上述各实施例中任一实施例中涉及第一设备或第二设备的任意方法和功能。
本申请实施例还提供一种无线通信系统，该系统包括上述任一实施例中涉及的至少一个第一设备和至少一个第二设备。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导 体介质(例如固态硬盘solid state disk(SSD))等。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (32)

  1. 一种适用于多链路的通信方法，其特征在于，包括：
    第一设备向第二设备发送ADDBA请求帧，所述ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；所述第一设备和所述第二设备为包含一条或多条链路的多链路实体；
    所述第一设备接收所述第二设备发送的ADDBA响应帧，所述ADDBA响应帧包括所述至少一个第一缓冲大小字段的确认值和所述第二缓冲大小字段的确认值；
    所述第一设备根据所述ADDBA请求帧和所述ADDBA响应帧，建立所述第一设备的多条链路与所述第二设备的多条链路之间的多链路块确认对话；
    其中，一个所述第一缓冲大小字段用于指示所述第一设备和所述第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，所述第二缓冲大小字段用于指示所述第一设备和所述第二设备维护的一个全局缓冲空间的大小。
  2. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    根据所述ADDBA请求帧和所述ADDBA响应帧，所述第一设备维护多个第一发送窗口和一个第二发送窗口，其中，所述多个第一发送窗口与所述第一设备的多条链路相对应，所述第二发送窗口与所述第一设备的多链路实体相对应；
    其中，一个所述第一发送窗口对应所述多条链路中的一条链路，一个所述第一发送窗口起始序号为WinStartO1,结束序号为WinEndO1，窗口大小为WinSizeO1，其中，所述WinSizeO1等于所述链路所对应的所述第一缓冲大小的确认值；
    所述第二发送窗口起始序号为WinStartO2,结束序号为WinEndO2，窗口大小为WinSizeO2，其中，所述WinSizeO2等于通过所述ADDBA请求帧和ADDBA响应帧协商的所述第二缓冲大小的确认值。
  3. 如权利要求1或2所述的方法，其特征在于，所述ADDBA请求帧包括至少一个第一块确认起始序列号控制字段和第二块确认起始序列号控制字段；
    所述第一块确认起始序列号控制字段用于指示所述第二设备的链路的第一计分板的起始序列号的第一初始序列号的初始值，所述第一初始序列号的类型为本地序列号；
    所述第二块确认起始序列号控制字段用于指示所述第二设备的多链路实体的第二计分板的起始序列号的第二初始序列号的初始值，所述第二初始序列号的类型为全局序列号。
  4. 如权利要求1至3中任一项所述的方法，其特征在于，
    所述ADDBA请求帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的参考值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的参考值中的至少一个；
    所述ADDBA响应帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的确认值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的确认值中的至少一个；
    所述ADDBA请求帧包括第一块确认参数集字段，所述第一块确认参数集字段包括所述第二缓冲大小字段的参考值；
    所述ADDBA响应帧包括第二块确认参数集字段，所述第二块确认参数集字段包括所述第二缓冲大小字段的确认值。
  5. 如权利要求1至4中任一项所述的方法，其特征在于，所述方法还包括：
    所述第一设备向所述第二设备发送数据包；
    所述第一设备接收所述第二设备回复的响应所述数据包的确认消息；
    所述数据包包括本地序列号和全局序列号，所述本地序列号为所述多条链路中发送所述数据包的链路分配给所述数据包的标识，所述全局序列号为所述多链路实体分配给所述数据包的标识。
  6. 如权利要求5所述的方法，其特征在于，所述第一设备接收所述第二设备回复的响应所述数据包的确认消息之前，还包括：
    所述第一设备向所述第二设备发送块确认请求帧或多用户块确认请求触发帧，所述块确认请求帧或所述多用户块确认请求触发帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号；
    所述块确认请求帧或所述多用户块确认请求触发帧还包括第一指示信息，所述第一指示信息用于指示所述起始序列号的类型，所述起始序列号的类型包括本地序列号或全局序列号。
  7. 如权利要求5或6所述的方法，其特征在于，所述第一设备接收所述第二设备回复的响应所述数据包的确认消息，包括：
    所述第一设备接收所述第二设备发送的块确认帧，所述块确认帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号和块确认比特位图；所述块确认比特位图用于指示所述第二设备接收到的所述数据包的接收情况；
    所述块确认帧还包括块确认BA控制字段，所述BA控制字段包括所述第二指示信息，所述第二指示信息用于指示所述起始序列号的类型，所述起始序列号的类型为本地序列号或全局序列号，且所述块确认比特位图中的第一比特对应所述起始序列号。
  8. 一种适用于多链路的通信方法，其特征在于，包括：
    第二设备接收第一设备发送ADDBA请求帧，所述ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；所述第一设备和所述第二设备为包含一条或多条链路的多链路实体；
    所述第二设备向所述第一设备发送的ADDBA响应帧，所述ADDBA响应帧包括所 述至少一个第一缓冲大小字段的确认值和所述第二缓冲大小字段的确认值；
    所述第二设备根据所述ADDBA请求帧和所述ADDBA响应帧，建立所述第一设备的多条链路与所述第二设备的多条链路之间的多链路块确认对话；
    其中，一个所述第一缓冲大小字段用于指示所述第一设备和所述第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，所述第二缓冲大小字段用于指示所述第一设备和所述第二设备维护的一个全局缓冲空间的大小。
  9. 如权利要求8中任一项所述的方法，其特征在于，所述方法还包括：
    根据所述ADDBA请求帧和所述ADDBA响应帧，所述第二设备维护一个接收窗口，其中，所述接收窗口与所述第二设备的所述链路实体相对应；
    其中，所述接收窗口起始序号为WinStartB2,结束序号为WinEndB2，窗口大小为WinSizeB2，其中，所述WinSizeB2等于所述第二缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。
  10. 如权利要求8至9中任一项所述的方法，其特征在于，所述ADDBA请求帧包括第一块确认起始序列号控制字段和第二块确认起始序列号控制字段；
    所述第一块确认起始序列号控制字段用于指示所述第二设备的链路的第一计分板的起始序号的第一初始序列号，所述第一初始序列号的类型为本地序列号；
    所述第二块确认起始序列号控制字段用于指示所述第二设备的多链路实体的第二计分板的起始序号的第二初始序列号，所述第二初始序列号的类型为全局序列号。
  11. 如权利要求8至10中任一项所述的方法，其特征在于，
    所述ADDBA请求帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的参考值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的参考值中的至少一个；
    所述ADDBA响应帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的确认值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的确认值中的至少一个；
    所述ADDBA请求帧包括第一块确认参数集字段，所述第一块确认参数集字段包括所述第二缓冲大小字段的参考值；
    所述ADDBA响应帧包括第二块确认参数集字段，所述第二块确认参数集字段包括所述第二缓冲大小字段的确认值。
  12. 如权利要求8至11中任一项所述的方法，其特征在于，所述方法还包括：
    所述第二设备接收所述第一设备发送数据包；
    所述第二设备向所述第一设备发送用于响应所述数据包的确认消息；
    所述数据包包括本地序列号和全局序列号，所述本地序列号为所述多条链路中发送所述数据包的链路分配给所述数据包的标识，所述全局序列号为所述多链路实体分配给所述 数据包的标识。
  13. 如权利要求12所述的方法，其特征在于，所述第二设备向所述第一设备发送用于响应所述数据包的确认消息之前，还包括：
    所述第二设备接收所述第一设备发送的块确认请求帧或多用户块确认请求触发帧，所述块确认请求帧或所述多用户块确认请求触发帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号；
    所述块确认请求帧或所述多用户块确认请求触发帧还包括第一指示信息，所述第一指示信息用于指示所述起始序列号的类型，所述起始序列号的类型包括本地序列号或全局序列号。
  14. 如权利要求8所述的方法，其特征在于，所述方法还包括：
    第二设备维护多个第一计分板和一个第二计分板；所述多个第一计分板与所述多条链路相对应，所述第二计分板与所述多链路实体相对应；
    一个所述第一计分板的起始序号为WinStartR1，结束序号为WinEndR1；计分板大小WinSizeR1等于所对应的链路所对应的所述第一缓冲大小的确认值与最大长度的块确认比特位图中的较小值；
    所述第二计分板的起始序号为WinStartR2,结束序号为WinEndR2，计分板大小为WinSizeR2，其中，所述WinSizeR2等于所述第二缓冲大小的确认值与最大长度的块确认比特位图中的较小值。
  15. 如权利要求12或13所述的方法，其特征在于，所述确认消息为块确认帧；
    所述块确认帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号和块确认比特位图；所述块确认比特位图用于指示所述第二设备接收到的所述数据包的接收情况；
    所述块确认帧还包括块确认BA控制字段，所述BA控制字段包括所述第二指示信息，所述第二指示信息用于指示所述起始序列号的类型，所述起始序列号的类型为本地序列号或全局序列号，且所述块确认比特位图中的第一比特对应所述起始序列号。
  16. 如权利要求15所述的方法，其特征在于，
    若所述块确认比特位图所对应的序列为所述本地序列号，则所述块确认比特位图中的第一比特所对应的序列号为所述WinStartR1；
    若所述块确认比特位图所对应的序列为所述全局序列号，则所述块确认比特位图中的第一比特所对应的序列号为所述WinStartR2。
  17. 一种第一通信装置，其特征在于，包括：
    发送模块，用于向第二设备发送ADDBA请求帧，所述ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；所述第二设备和第一设 备为包含一条或多条链路的多链路实体；
    接收模块，用于接收所述第二设备发送的ADDBA响应帧，所述ADDBA响应帧包括至少一个所述第一缓冲大小字段的确认值和所述第二缓冲大小字段的确认值；
    处理模块，用于根据所述ADDBA请求帧和所述ADDBA响应帧，建立所述第一设备的多条链路与所述第二设备的多条链路之间的多链路块确认对话；
    其中，一个所述第一缓冲大小字段用于指示所述第一设备和所述第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，所述第二缓冲大小字段用于指示所述第一设备和所述第二设备维护的一个全局缓冲空间的大小。
  18. 如权利要求17所述的第一通信装置，其特征在于，所述第一设备包括：
    所述处理模块，还用于根据所述ADDBA请求帧和所述ADDBA响应帧，维护多个第一发送窗口和一个第二发送窗口，其中，所述多个第一发送窗口与所述第一设备的多条链路相对应，所述第二发送窗口与所述第一设备的多链路实体相对应；
    其中，一个所述第一发送窗口对应所述多条链路中的一条链路，一个所述第一发送窗口起始序号为WinStartO1,结束序号为WinEndO1，窗口大小为WinSizeO1，其中，所述WinSizeO1等于所述链路所对应的第一缓冲大小的确认值；
    所述第二发送窗口起始序号为WinStartO2,结束序号为WinEndO2，窗口大小为WinSizeO2，其中，所述WinSizeO2等于通过所述ADDBA请求帧和ADDBA响应帧协商的所述第二缓冲大小的确认值。
  19. 如权利要求17或18所述的第一通信装置，其特征在于，所述ADDBA请求帧包括第一块确认起始序列号控制字段和第二块确认起始序列号控制字段；
    所述第一块确认起始序列号控制字段用于指示所述第二设备的链路的第一计分板的起始序列号的第一初始序列号，所述第一初始序列号的类型为本地序列号；
    所述第二块确认起始序列号控制字段用于指示所述第二设备的多链路实体的第二计分板的起始序列号的第二初始序列号，所述第二初始序列号的类型为全局序列号。
  20. 如权利要求17至19中任一项所述的第一通信装置，其特征在于，
    所述ADDBA请求帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的参考值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的参考值中的至少一个；
    所述ADDBA响应帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的确认值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的确认值中的至少一个；
    所述ADDBA请求帧包括第一块确认参数集字段，所述第一块确认参数集字段包括所述第二缓冲大小字段的参考值；
    所述ADDBA响应帧包括第二块确认参数集字段，所述第二块确认参数集字段包括所述第二缓冲大小字段的确认值。
  21. 如权利要求17至20中任一项所述的第一通信装置，其特征在于，
    所述发送模块，用于向所述第二设备发送数据包；
    所述接收模块，用于接收所述第二设备回复的响应所述数据包的确认消息；
    其中，所述数据包包括本地序列号和全局序列号，所述本地序列号为所述多条链路中发送所述数据包的链路分配给所述数据包的标识，所述全局序列号为所述多链路实体分配给所述数据包的标识。
  22. 如权利要求17至21中任一项所述的第一通信装置，其特征在于，
    所述发送模块，还用于向所述第二设备发送块确认请求帧或多用户块确认请求触发帧，所述块确认请求帧或所述多用户块确认请求触发帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号；
    所述块确认请求帧或所述多用户块确认请求触发帧还包括第一指示信息，所述第一指示信息用于指示所述起始序列号的类型，所述起始序列号的类型包括本地序列号或全局序列号。
  23. 如权利要求17至22中任一项所述的第一通信装置，其特征在于，
    所述接收模块，还用于接收所述第二设备发送的块确认帧，所述块确认帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号和块确认比特位图；所述块确认比特位图用于指示所述第二设备接收到的所述数据包的接收情况；
    所述块确认帧还包括块确认BA控制字段，所述BA控制字段包括所述第二指示信息，所述第二指示信息用于指示所述起始序列号的类型，所述起始序列号的类型为本地序列号或全局序列号，且所述块确认比特位图中的第一比特对应所述起始序列号。
  24. 一种第二通信装置，其特征在于，包括：
    接收模块，用于接收第一设备发送ADDBA请求帧，所述ADDBA请求帧包括至少一个第一缓冲大小字段的参考值和一个第二缓冲大小字段的参考值；所述第一设备和第二设备为包含一条或多条链路的多链路实体；
    发送模块，用于向所述第一设备发送的ADDBA响应帧，所述ADDBA响应帧包括所述至少一个第一缓冲大小字段的确认值和所述第二缓冲大小字段的确认值；
    处理模块，用于根据所述ADDBA请求帧和所述ADDBA响应帧，建立所述第一设备的多条链路与所述第二设备的多条链路之间的多链路块确认对话；
    其中，一个所述第一缓冲大小字段用于指示所述第一设备和所述第二设备的多条链路中的一条链路对应的一个局部缓冲空间的大小，所述第二缓冲大小字段用于指示所述第一设备和所述第二设备维护的一个全局缓冲空间的大小。
  25. 如权利要求24所述的第二通信装置，其特征在于，所述第二设备还包括：
    所述处理模块，还用于根据所述ADDBA请求帧和所述ADDBA响应帧，维护一个 接收窗口，其中，所述接收窗口与所述第二设备的所述链路实体相对应；
    其中，所述接收窗口起始序号为WinStartB2,结束序号为WinEndB2，窗口大小为WinSizeB2，其中，所述WinSizeB2等于所述第二缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。
  26. 如权利要求24或25所述的第二通信装置，其特征在于，所述ADDBA请求帧包括第一块确认起始序列号控制字段和第二块确认起始序列号控制字段；
    所述第一块确认起始序列号控制字段用于指示所述第二设备的链路的第一计分板的起始序号的第一初始序列号，所述第一初始序列号的类型为本地序列号；
    所述第二块确认起始序列号控制字段用于指示所述第二设备的多链路实体的第二计分板的起始序号的第二初始序列号，所述第二初始序列号的类型为全局序列号。
  27. 如权利要求24至26中任一项所述的第二通信装置，其特征在于，
    所述ADDBA请求帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的参考值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的参考值中的至少一个；
    所述ADDBA响应帧包括链路比特位图字段和所述至少一个第一缓冲大小字段的确认值中的至少一个，或，链路数目字段、多条链路身份号字段以及所述至少一个第一缓冲大小字段的确认值中的至少一个；
    所述ADDBA请求帧包括第一块确认参数集字段，所述第一块确认参数集字段包括所述第二缓冲大小字段的参考值；
    所述ADDBA响应帧包括第二块确认参数集字段，所述第二块确认参数集字段包括所述第二缓冲大小字段的确认值。
  28. 如权利要求24至27中任一项所述的第二通信装置，其特征在于，
    所述接收模块，还用于接收所述第一设备发送数据包；
    所述发送模块，还用于向所述第一设备发送用于响应所述数据包的确认消息；
    其中，所述数据包包括本地序列号和全局序列号，所述本地序列号为所述多条链路中发送所述数据包的链路分配给所述数据包的标识，所述全局序列号为所述多链路实体分配给所述数据包的标识。
  29. 如权利要求24至28中任一项所述的第二通信装置，其特征在于，
    所述接收模块，还用于接收所述第一设备发送的块确认请求帧或多用户块确认请求触发帧，所述块确认请求帧或所述多用户块确认请求触发帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号；
    所述块确认请求帧或所述多用户块确认请求触发帧还包括第一指示信息，所述第一指示信息用于指示所述起始序列号的类型，所述起始序列号的类型包括本地序列号或全局序列号。
  30. 如权利要求24所述的第二通信装置，其特征在于，所述第二设备还包括：
    所述处理模块，还用于维护多个第一计分板和一个第二计分板；所述多个第一计分板与所述多条链路相对应，所述第二计分板与所述多链路实体相对应；
    一个所述第一计分板的起始序号为WinStartR1，结束序号为WinEndR1；计分板大小WinSizeR1等于所对应的链路所对应的所述第一缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值；
    所述第二计分板的起始序号为WinStartR2,结束序号为WinEndR2，计分板大小为WinSizeR2，其中，所述WinSizeR2等于所述第二缓冲大小字段的确认值与最大长度的块确认比特位图中的较小值。
  31. 如权利要求28或29所述的第二通信装置，其特征在于，所述确认消息为块确认帧；
    所述块确认帧包括起始序列号控制字段，所述起始序列号控制字段包括起始序列号和块确认比特位图；所述块确认比特位图用于指示所述第二设备接收到的所述数据包的接收情况；
    所述块确认帧还包括块确认BA控制字段，所述BA控制字段包括所述第二指示信息，所述第二指示信息用于指示所述起始序列号的类型，所述起始序列号的类型为本地序列号或全局序列号，且所述块确认比特位图中的第一比特对应所述起始序列号。
  32. 如权利要求31所述的第二通信装置，其特征在于，
    若所述块确认比特位图所对应的序列为所述本地序列号，则所述块确认比特位图中的第一比特所对应的序列号为所述WinStartR1；
    若所述块确认比特位图所对应的序列为所述全局序列号，则所述块确认比特位图中的第一比特所对应的序列号为所述WinStartR2。
PCT/CN2020/091940 2019-05-25 2020-05-22 一种适用于多链路的通信方法及相关设备 WO2020238812A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP20814644.9A EP3968731B1 (en) 2019-05-25 2020-05-22 Communication method applicable to multiple links, and related devices
EP23186955.3A EP4287580A3 (en) 2019-05-25 2020-05-22 Communication method applicable to multiple links, and related devices

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910455575.5A CN112074020B (zh) 2019-05-25 2019-05-25 一种适用于多链路的通信方法及相关设备
CN201910455575.5 2019-05-25

Publications (1)

Publication Number Publication Date
WO2020238812A1 true WO2020238812A1 (zh) 2020-12-03

Family

ID=73553477

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/091940 WO2020238812A1 (zh) 2019-05-25 2020-05-22 一种适用于多链路的通信方法及相关设备

Country Status (3)

Country Link
EP (2) EP4287580A3 (zh)
CN (4) CN112074020B (zh)
WO (1) WO2020238812A1 (zh)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113992607A (zh) * 2021-09-09 2022-01-28 新华三信息安全技术有限公司 报文处理方法及装置
WO2022052863A1 (zh) * 2020-09-10 2022-03-17 华为技术有限公司 无线局域网中块确认会话的管理方法及装置
CN114896114A (zh) * 2022-03-01 2022-08-12 北京百度网讯科技有限公司 计分板实现方法、装置、计分板、电子设备及存储介质
CN115150037A (zh) * 2021-03-30 2022-10-04 成都极米科技股份有限公司 多链路块确认协议建立的方法、装置、系统及存储介质
CN115150027A (zh) * 2021-03-30 2022-10-04 成都极米科技股份有限公司 多链路块确认方法、装置及存储介质
CN115209568A (zh) * 2021-04-09 2022-10-18 成都极米科技股份有限公司 多链路系统业务流数据传输的管理方法、装置及存储介质
US20220407622A1 (en) * 2019-11-04 2022-12-22 Hyundai Motor Company Method and apparatus for transmitting and receiving block ack in wireless lan system
US20230224069A1 (en) * 2020-04-29 2023-07-13 Beijing Xiaomi Mobile Software Co., Ltd. Data transmission method and apparatus, and communication device and storage medium
EP4280807A4 (en) * 2021-01-18 2024-03-06 Beijing Xiaomi Mobile Software Co., Ltd. COMMUNICATION METHOD UNDER MULTIPLE LINKS AND COMMUNICATION DEVICE

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117938320A (zh) * 2021-01-12 2024-04-26 北京小米移动软件有限公司 块确认方法及装置、存储介质
CN116234068A (zh) * 2021-01-15 2023-06-06 华为技术有限公司 多链路的重配置方法及装置
CN115150028B (zh) * 2021-03-30 2023-08-01 深圳市极米软件科技有限公司 多链路设备之间建立块确认协议的方法、装置及介质
CN115189854A (zh) * 2021-04-07 2022-10-14 华为技术有限公司 信息指示方法及通信装置
CN115334617B (zh) * 2021-05-11 2024-06-14 极米科技股份有限公司 通过建立接入点进行数据传输的方法、装置及存储介质
CN115442874A (zh) * 2021-06-01 2022-12-06 华为技术有限公司 多链路通信方法、存储介质及电子设备
WO2022266876A1 (en) * 2021-06-23 2022-12-29 Nokia Shanghai Bell Co., Ltd. Indication of sequence number for groupcast frame
WO2023019591A1 (zh) * 2021-08-20 2023-02-23 Oppo广东移动通信有限公司 通信方法、装置、设备及存储介质
WO2023087312A1 (zh) * 2021-11-22 2023-05-25 Oppo广东移动通信有限公司 无线通信的方法和设备
CN114126001B (zh) * 2022-01-25 2022-04-19 成都极米科技股份有限公司 传输软接入设备系统参数的方法、装置、设备和介质
CN114630368B (zh) * 2022-04-22 2023-03-24 成都极米科技股份有限公司 控制在多链路上进行数据传输的方法、装置、设备及介质
CN117896851A (zh) * 2022-10-14 2024-04-16 华为技术有限公司 通信方法和通信装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104541568A (zh) * 2012-05-11 2015-04-22 新加坡科技研究局 用于确定与通信参数有关的信息的方法以及通信设备
US20150282005A1 (en) * 2014-03-28 2015-10-01 Qualcomm Incorporated Link aggregation in wireless local area networks
CN106464354A (zh) * 2014-06-19 2017-02-22 Lg电子株式会社 用于发送帧的方法和设备
CN106506125A (zh) * 2015-09-08 2017-03-15 华为技术有限公司 建立、拆除块确认通信机制的方法和装置
CN109040869A (zh) * 2018-08-14 2018-12-18 中天宽带技术有限公司 Epon系统中基于oam协议的onu快速升级方法
US20190150214A1 (en) * 2017-01-19 2019-05-16 Qualcomm Incorporated Packet based link aggregation architectures

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9363752B2 (en) * 2013-12-27 2016-06-07 Qualcomm Incorporated Target wake time flow identification in TWT acknowledgement
US10827425B2 (en) * 2015-01-28 2020-11-03 Qualcomm Incorporated Triggered target wake time operation
US10135957B2 (en) * 2015-06-15 2018-11-20 Qualcomm Incorporated Methods and apparatus for communicating high efficiency control information
US10187905B2 (en) * 2015-06-24 2019-01-22 Marvell World Trade Ltd. Target wake time (TWT) scheduling for orthogonal frequency-division multiple access (OFDMA) channelization
US20170055300A1 (en) * 2015-08-20 2017-02-23 Qualcomm Incorporated Block acknowledgment mechanism
CN105813077A (zh) * 2016-04-14 2016-07-27 天津大学 基于802.11ah减少开销降低终端功耗的通信方法
US11284301B2 (en) * 2017-04-17 2022-03-22 Qualcomm Incorporated Flow control for wireless devices
US10735566B2 (en) * 2017-06-23 2020-08-04 Qualcomm Incorporated Large media access control service data unit (MSDU) delivery
US10750445B2 (en) * 2017-09-01 2020-08-18 Intel IP Corporation Methods and apparatus to facilitate target wake time management between access points and devices

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104541568A (zh) * 2012-05-11 2015-04-22 新加坡科技研究局 用于确定与通信参数有关的信息的方法以及通信设备
US20150282005A1 (en) * 2014-03-28 2015-10-01 Qualcomm Incorporated Link aggregation in wireless local area networks
CN106464354A (zh) * 2014-06-19 2017-02-22 Lg电子株式会社 用于发送帧的方法和设备
CN106506125A (zh) * 2015-09-08 2017-03-15 华为技术有限公司 建立、拆除块确认通信机制的方法和装置
US20190150214A1 (en) * 2017-01-19 2019-05-16 Qualcomm Incorporated Packet based link aggregation architectures
CN109040869A (zh) * 2018-08-14 2018-12-18 中天宽带技术有限公司 Epon系统中基于oam协议的onu快速升级方法

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CABRAL, ORLANDO ET AL.: "Implementation of Multi-service IEEE 802.11e Block Acknowledgement Policies", IAENG INTERNATIONAL JOURNAL OF COMPUTER SCIENCE, vol. 36, no. 1,, 17 February 2009 (2009-02-17), XP055339253, DOI: 20200803163248 *

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220407622A1 (en) * 2019-11-04 2022-12-22 Hyundai Motor Company Method and apparatus for transmitting and receiving block ack in wireless lan system
US20230224069A1 (en) * 2020-04-29 2023-07-13 Beijing Xiaomi Mobile Software Co., Ltd. Data transmission method and apparatus, and communication device and storage medium
WO2022052863A1 (zh) * 2020-09-10 2022-03-17 华为技术有限公司 无线局域网中块确认会话的管理方法及装置
EP4280807A4 (en) * 2021-01-18 2024-03-06 Beijing Xiaomi Mobile Software Co., Ltd. COMMUNICATION METHOD UNDER MULTIPLE LINKS AND COMMUNICATION DEVICE
CN115150037A (zh) * 2021-03-30 2022-10-04 成都极米科技股份有限公司 多链路块确认协议建立的方法、装置、系统及存储介质
CN115150027A (zh) * 2021-03-30 2022-10-04 成都极米科技股份有限公司 多链路块确认方法、装置及存储介质
CN115150027B (zh) * 2021-03-30 2023-06-30 极米科技股份有限公司 多链路块确认方法、装置及存储介质
CN115150037B (zh) * 2021-03-30 2023-11-28 极米科技股份有限公司 多链路块确认协议建立的方法、装置、系统及存储介质
CN115209568A (zh) * 2021-04-09 2022-10-18 成都极米科技股份有限公司 多链路系统业务流数据传输的管理方法、装置及存储介质
CN113992607A (zh) * 2021-09-09 2022-01-28 新华三信息安全技术有限公司 报文处理方法及装置
CN113992607B (zh) * 2021-09-09 2023-11-03 新华三信息安全技术有限公司 报文处理方法及装置
CN114896114A (zh) * 2022-03-01 2022-08-12 北京百度网讯科技有限公司 计分板实现方法、装置、计分板、电子设备及存储介质
CN114896114B (zh) * 2022-03-01 2023-03-24 北京百度网讯科技有限公司 计分板实现方法、装置、计分板、电子设备及存储介质

Also Published As

Publication number Publication date
EP4287580A3 (en) 2024-01-10
EP4287580A2 (en) 2023-12-06
EP3968731A4 (en) 2022-07-06
CN118338462A (zh) 2024-07-12
CN118338463A (zh) 2024-07-12
CN112074020B (zh) 2024-03-26
CN118338464A (zh) 2024-07-12
CN112074020A (zh) 2020-12-11
EP3968731B1 (en) 2023-08-16
EP3968731A1 (en) 2022-03-16

Similar Documents

Publication Publication Date Title
WO2020238812A1 (zh) 一种适用于多链路的通信方法及相关设备
US7630403B2 (en) MAC aggregation frame with MSDU and fragment of MSDU
US11258543B2 (en) Wireless communication method supporting multi-user cascading transmission and wireless communication terminal using same
US8743711B2 (en) Techniques for managing heterogeneous traffic streams
US11540318B2 (en) Carrier set determination method and device, storage medium and electronic device
CN117793791A (zh) 数据传输的方法和装置
US12057941B2 (en) Data packet acknowledgment method, apparatus, device, and computer-readable storage medium
US11108503B2 (en) Multiple traffic class data aggregation in a wireless local area network
US20230209518A1 (en) Communication method and apparatus
US10932179B2 (en) Support of A-MSDU in A-MPDU
US12004144B2 (en) Multi-band single mac communication system
CN117793792B (zh) 数据传输的方法和装置
WO2023036050A1 (zh) 一种通信方法及装置
WO2016138824A1 (zh) 数据发送方法、接收方法、发送装置及接收装置
CN117042045A (zh) 数据传输方法及装置
CN118102423A (zh) 信息指示方法及设备

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: 20814644

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2020814644

Country of ref document: EP

Effective date: 20211206