WO2021218435A1 - 一种多链路通信方法及相关装置 - Google Patents

一种多链路通信方法及相关装置 Download PDF

Info

Publication number
WO2021218435A1
WO2021218435A1 PCT/CN2021/080316 CN2021080316W WO2021218435A1 WO 2021218435 A1 WO2021218435 A1 WO 2021218435A1 CN 2021080316 W CN2021080316 W CN 2021080316W WO 2021218435 A1 WO2021218435 A1 WO 2021218435A1
Authority
WO
WIPO (PCT)
Prior art keywords
link
ssn
winstart
receiving end
sequence number
Prior art date
Application number
PCT/CN2021/080316
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 华为技术有限公司
Publication of WO2021218435A1 publication Critical patent/WO2021218435A1/zh
Priority to US17/971,843 priority Critical patent/US20230040554A1/en

Links

Images

Classifications

    • 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/1621—Group acknowledgement, i.e. the acknowledgement message defining a range of identifiers, e.g. of sequence numbers
    • 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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • 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/1642—Formats specially adapted for sequence numbers
    • 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/1832—Details of sliding window management
    • 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
    • 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/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • 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/04—Error control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information

Definitions

  • This application relates to the field of communication technology, and in particular to a multi-link communication method and related devices.
  • multi-link devices can support multi-link communication, such as simultaneous communication on 2.4GHz, 5GHz, and 60GHz frequency bands, even when the number of antennas is limited. Multi-link devices can also switch on different frequency bands to select the best frequency band to ensure its communication quality. As more and more application traffic is carried by the wireless network, high speed is the evolution goal of the wireless fidelity (wreless-fidelity, WiFi) system. In order to increase the peak rate of the sites in the multi-link device, multi-link aggregation communication has become a feature of the next-generation wireless local area networks (WLAN) technology.
  • WLAN wireless local area networks
  • Multi-link aggregation communication involves coordination between multiple links.
  • Multiple media access control protocol data units (MAC protocol data unit, MPDU) of the same service identifier (Traffic Identifier, TID) at the data sender can pass multiple Two links are used for transmission to increase the transmission rate of the TID data packet.
  • the data receiving end sorts the data packets of the same TID received on multiple links according to the SN according to the sequence number (SN) carried in the header of each MPDU frame.
  • the protocol requires that the MAC layer must deliver the complete MSDU (MAC Service Data unit, MAC layer service data unit) to the upper layer in order.
  • a starting sequence number (SSN) value is set in the BAR, but there are other links that are less than this value.
  • the pending MPDU with the SSN value will cause the receiving end to move the starting sequence number of the scoreboard (indicated as: WinStart), which will cause the subsequent MPDUs sent by the sending end to be less than the SSN value even if they are correctly received by the receiving end.
  • the receiving end discards.
  • embodiments of the present application provide a multi-link aggregation transmission method and device, a chip system, a computer-readable storage medium, and a computer program product.
  • the first aspect of the embodiments of the present application provides a multi-link aggregation transmission method, which is applied to the receiving end of multi-link aggregation transmission, and includes:
  • the receiving end receives at least one of a data frame and a BAR frame on multiple links between the receiving end and the sending end; the multiple links include the first link;
  • the receiving end receives a block confirmation request BAR frame on the first link, and the BAR frame carries the SSN_1 corresponding to the first link;
  • the receiving end adjusts the current start sequence number WinStart value of the scoreboard window according to the SSN corresponding to at least two of the multiple links; wherein, at least two of the multiple links correspond to SSN includes SSN_1 corresponding to the first link and SSN corresponding to other links stored locally by the receiving end;
  • the receiving end processes the data frames received on the multi-link according to the adjusted WinStart.
  • a multi-link device which serves as a receiving end of multi-link aggregation transmission, including:
  • a transceiver configured to receive at least one of a data frame and a BAR frame on multiple links with the sending end; the multiple links include the first link;
  • the transceiver is configured to receive a block confirmation request BAR frame on the first link, where the BAR frame carries the SSN_1 corresponding to the first link;
  • the processor is configured to adjust the WinStart value of the current scoreboard window starting sequence number according to the SSN corresponding to at least two of the multiple links; wherein, at least two of the multiple links correspond to SSN includes SSN_1 corresponding to the first link and SSN corresponding to other links stored locally by the receiving end;
  • the processor is further configured to process the data frame received on the multi-link according to the adjusted WinStart.
  • the third aspect of the embodiments of the present application provides a multi-link aggregation transmission method, which is applied to the receiving end of multi-link aggregation transmission, and includes:
  • the receiving end receives data frames on multiple links with the sending end; the multiple links include the first link;
  • the receiving end parses the initial sequence number SSN_1 corresponding to the first link carried in the BAR frame; wherein the SSN_1 is the sequence number of the next data frame sent on the first link, or the SSN_1 is greater than the sequence number of the data frame discarded by the sending end on the first link;
  • the receiving end processes the data frames received on the multi-link.
  • a multi-link device which serves as a receiving end of multi-link aggregation transmission, including:
  • a transceiver configured to receive data frames on multiple links with the sending end; the multiple links include the first link;
  • the transceiver is further configured to receive a block confirmation request BAR frame on the first link;
  • the processor is configured to parse the initial sequence number SSN_1 corresponding to the first link carried in the BAR frame; wherein the SSN_1 is the sequence number of the next data frame sent on the first link, or The SSN_1 is greater than the sequence number of the data frame discarded by the sending end on the first link;
  • the processor is further configured to process data frames received on the multi-link.
  • a chip system including at least one processor and an interface; wherein,
  • the interface is used to input data frames from multiple links with the sending end; the multiple links include the first link;
  • the interface is also used to input a block confirmation request BAR frame received on the first link, and the BAR frame carries the SSN_1 corresponding to the first link;
  • the processor is configured to adjust the WinStart value of the current scoreboard window starting sequence number according to the SSN corresponding to at least two of the multiple links; wherein, at least two of the multiple links correspond to SSN includes SSN_1 corresponding to the first link and SSN corresponding to other links stored locally by the receiving end;
  • the processor is further configured to process the data frame received on the multi-link according to the adjusted WinStart.
  • a chip system including at least one processor and an interface; wherein,
  • the interface is used to input data frames received on multiple links with the sending end; the multiple links include the first link;
  • the interface is also used to input the block confirmation request BAR frame received on the first link;
  • the processor is configured to parse the initial sequence number SSN_1 corresponding to the first link carried in the BAR frame; wherein the SSN_1 is the sequence number of the next data frame to be sent on the first link, Or the SSN_1 is greater than the sequence number of the data frame discarded by the sending end on the first link;
  • the processor is further configured to process data frames received on the multi-link.
  • the current SSN is adjusted according to the SSN_1 corresponding to the first link and the SSN corresponding to other links stored locally by the receiving end.
  • the WinStart value of the starting sequence number of the scoreboard window includes:
  • processing of the data frame received on the multi-link according to the adjusted WinStart includes:
  • adjusting the WinStart value of the current scoreboard window starting sequence number according to the SSN corresponding to each link includes:
  • the maximum value of WinStart is the largest WinStart among WinStart before receiving the BAR and WinStart after receiving the BAR; wherein, the WinStart after receiving the BAR is the SSN minimum value; the SSN minimum value is the first SSN_1 of SSN_1 corresponding to the link and the smallest SSN among SSNs corresponding to other links stored locally.
  • processing of the data frame received on the multi-link according to the adjusted WinStart includes:
  • the SSN_1 is the sequence number of the data frame to be sent next on the first link, or the SSN_1 is greater than the sequence number of the data frame discarded by the sending end on the first link.
  • a multi-link aggregation transmission method which is applied to the sending end of multi-link aggregation transmission, and includes:
  • the sending end sends data frames on multiple links with the receiving end; the multiple links include the first link;
  • the sending end sends a block confirmation request BAR frame on the first link; the BAR frame carries the initial sequence number SSN_1 corresponding to the first link; wherein the SSN_1 is the first link The sequence number of the next data frame to be sent, or the SSN_1 is greater than the sequence number of the data frame discarded by the sending end on the first link.
  • a multi-link device which, as a sender of multi-link aggregation transmission, includes:
  • a transceiver configured to send data frames on multiple links with the receiving end; the multiple links include the first link;
  • the transceiver is further configured to send a block confirmation request BAR frame on the first link;
  • the processor is configured to parse the initial sequence number SSN_1 corresponding to the first link carried in the BAR frame; wherein the SSN_1 is the sequence number of the next data frame sent on the first link, Or the SSN_1 is greater than the sequence number of the data frame discarded by the sending end on the first link.
  • An eighth aspect of the present application provides a chip system, including: at least one processor and an interface;
  • the interface is configured to output data frames sent on multiple links with the receiving end; the multiple links include the first link;
  • the interface is also used to output the block confirmation request BAR frame sent on the first link;
  • the processor is configured to carry the initial sequence number SSN_1 corresponding to the first link in the BAR frame; wherein the SSN_1 is the sequence number of the next data frame sent on the first link, or The SSN_1 is greater than the sequence number of the discarded data frame on the first link.
  • a ninth aspect of the embodiments of the present application provides a first multi-link communication device configured to implement the method and function performed by the receiving end in the first aspect or the third aspect described above.
  • Hardware/software implementation, and its hardware/software includes modules corresponding to the above-mentioned functions.
  • a second multi-link communication device is provided, and the second multi-link device is configured to implement the methods and functions performed by the sending end of the seventh aspect described above, and is implemented by hardware/software, Its hardware/software includes modules corresponding to the above-mentioned functions.
  • the eleventh aspect of the embodiments of the present application provides a computer program product containing instructions, which, when run on a computer, causes the computer to execute any one of the foregoing first aspect, third aspect, or seventh aspect Methods.
  • the twelfth aspect of the embodiments of the present application provides a computer-readable storage medium, which is used to store instructions. When the instructions are executed, the first aspect or the third aspect or the aforementioned The method described in any one of the seven aspects is implemented.
  • the thirteenth aspect of the embodiments of the present application provides a chip, including a processor, configured to call and execute instructions stored in the memory from the memory, so that the communication device with the chip installed executes the first aspect or the third aspect or The seventh method.
  • the fourteenth aspect of the embodiments of the present application provides another chip.
  • the chip may be a chip in a first multi-link device or a second multi-link device.
  • the chip includes: an input interface, an output interface, and a processing circuit.
  • the interface, the output interface, and the circuit are connected through an internal connection path, and the processing circuit is used to execute the method of the first aspect, the third aspect, or the seventh aspect.
  • 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 an internal connection path.
  • 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 of the first aspect or the third aspect or the seventh aspect.
  • the sixteenth aspect of the embodiments of the present application provides a device for implementing the method in any one of the foregoing aspects.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of transmission between multi-link devices according to an embodiment of the present application.
  • FIG. 3A is a schematic structural diagram of a multi-link device provided by an embodiment of the present application.
  • 3B is a schematic structural diagram of a multi-link communication device provided by an embodiment of the present application.
  • FIG. 3C is a schematic structural diagram of a multi-link communication device provided by an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a chip system provided by an embodiment of the present application.
  • Figure 5 is a schematic diagram of a BAR frame
  • Fig. 6 is another schematic diagram of a BAR frame
  • Figure 7 is a schematic diagram of a BA frame
  • Fig. 8 is another schematic diagram of a BA frame
  • Figure 9 is a schematic diagram of multi-link aggregation transmission
  • Figure 10 is a diagram of a multi-link aggregation transmission architecture
  • Figure 11 is a schematic diagram of a modified BAR frame
  • Figure 12 is a schematic diagram of yet another modified BAR frame
  • FIG. 13 is a schematic flowchart of a multi-link aggregation transmission provided by an embodiment of the present application.
  • FIG. 14 is a schematic diagram of another multi-link aggregation transmission process provided by an embodiment of the present application.
  • FIG. 15 is a schematic diagram of another multi-link aggregation transmission process proposed by an embodiment of the present application.
  • FIG. 16 is a schematic diagram of a flow of multi-link aggregation transmission
  • FIG. 17 is a schematic diagram of another multi-link aggregation transmission process provided by an embodiment of the present application.
  • FIG. 18 is a schematic diagram of another multi-link aggregation transmission process proposed by an embodiment of the present application.
  • FIG. 19 is a schematic diagram of another multi-link aggregation transmission process provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present application.
  • the communication system includes access point equipment and site equipment.
  • the communication system may include one or more access points (access points, AP), and only one is shown in FIG. 1.
  • the communication system also includes one or more stations (stations, STAs), such as STA1 to STA6 shown in FIG. 1. Among them, there are multiple links between STA2 and AP, and STA2 is a multi-link device; there are also multiple links between STA4 and STA5, and STA4 and STA5 are also multi-link devices.
  • the multi-link device in the embodiment of the present application may be a site device or an access point device.
  • the architecture shown in FIG. 1 can also be extended to application scenarios of base stations (BS) and user equipment (UE).
  • BS base stations
  • UE user equipment
  • AP can be the access point for mobile users to enter the wired network. It is mainly deployed in homes, buildings, and parks. The typical coverage radius is tens of meters to hundreds of meters. Of course, it can also be deployed outdoors.
  • the AP is equivalent to a bridge connecting 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 802.11be and the future 802.11 standard.
  • the AP can also be a device supporting multiple wireless local area networks (WLAN) standards such as 802.11ax, 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 mobile phone that supports WiFi communication function For example, a mobile phone that supports WiFi communication function, a tablet computer that supports WiFi communication function, a set-top box that supports WiFi communication function, a smart TV that supports WiFi communication function, a smart wearable device that supports WiFi communication function, and a vehicle-mounted communication device that supports WiFi communication function And a computer that supports WiFi communication.
  • the STA can support 802.11be and future 802.11 standard devices. STA can also support multiple WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.
  • FIG. 2 is a schematic diagram of an association relationship between multi-link devices according to an embodiment of the present application.
  • the multi-link device shown in FIG. 2 includes a first multi-link device and a second multi-link device.
  • the first multi-link device or the second multi-link device may respectively include at least one multi-link logical entity, one
  • the multi-link logical entity may include one or more stations, and each station works on a different link.
  • STA1 and STA2 in the first multi-link device belong to one multi-link logical entity
  • STAn in the first multi-link device belongs to another multi-link logical entity.
  • STA1 and STA2 in the second multi-link device belong to one multi-link logical entity, and STAn in the second multi-link device belongs to another multi-link logical entity. If the first multi-link device needs to communicate with the second multi-link device, each station in the first multi-link device needs to be associated with a corresponding station in the second multi-link device.
  • STA1 in the first multi-link device is associated with STA1 in the second multi-link device and works on aggregate link 1 (referred to as link 1).
  • STA2 in the first multi-link device is associated with STA2 in the second multi-link device, and works on aggregate link 2 (referred to as link 2).
  • STAn in the first multi-link device is associated with STAn in the second multi-link device, and works on aggregate link n (link n). This enables each station in the first multi-link device to establish a connection with the corresponding station in the second multi-link device on its respective link, so as to realize multi-link communication between the two multi-link devices.
  • the multi-link device involved in the embodiments of the present application may include a hardware structure and a software module, and implement the above-mentioned functions in the form of a hardware structure, a software module, or a hardware structure plus a software module.
  • One of the above-mentioned functions can be implemented in a hardware structure, a software module, or a hardware structure plus a software module.
  • FIG. 3A is a schematic structural diagram of a multi-link device 200 provided by an embodiment of this application.
  • the multi-link device 200 may include a processor 201, a transceiver 205, and optionally a memory 202.
  • the transceiver 205 may be called a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing the transceiver function.
  • the transceiver 205 may include a receiver and a transmitter.
  • the receiver may be referred to as a receiver or a receiving circuit, etc., to implement a receiving function;
  • the transmitter may be referred to as a transmitter or a transmitting circuit, etc., to implement a transmitting function.
  • the memory 202 may store a computer program or software code or instruction 204, and the computer program or software code or instruction 204 may also be referred to as firmware.
  • the processor 201 can control the MAC layer and the PHY layer by running the computer program or software code or instruction 203 therein, or by calling the computer program or software code or instruction 204 stored in the memory 202, so as to realize the following aspects of this application. Examples.
  • the processor 201 may be a central processing unit (CPU), and the memory 202 may be, for example, a read-only memory (ROM) or a random access memory (RAM).
  • the processor 201 and the transceiver 205 described in this application can be implemented in an integrated circuit (IC), analog IC, radio frequency integrated circuit RFIC, mixed signal IC, application specific integrated circuit (ASIC), printed circuit Printed circuit board (PCB), electronic equipment, etc.
  • IC integrated circuit
  • analog IC analog IC
  • radio frequency integrated circuit RFIC radio frequency integrated circuit
  • mixed signal IC mixed signal IC
  • ASIC application specific integrated circuit
  • PCB printed circuit Printed circuit board
  • electronic equipment etc.
  • the above-mentioned multi-link device 200 may further include an antenna 206.
  • the modules included in the multi-link device 200 are only examples for illustration, and this application is not limited thereto.
  • FIG. 3B is a schematic structural diagram of a first multi-link communication device provided by an embodiment of the present application.
  • the first multi-link communication apparatus may include a processing module 301 and a sending module 302.
  • the sending module 302 corresponds to a baseband circuit and a radio frequency circuit included in the first multi-link device.
  • the first multi-link communication device serves as the sender of multi-link aggregation transmission, wherein the detailed description of each module is as follows.
  • the sending module 302 is configured to send data frames on multiple links with the second multi-link device; the multiple links include the first link;
  • the sending module 302 is further configured to send a block confirmation request BAR frame on the first link;
  • the processing module 301 is configured to parse the initial sequence number SSN_1 corresponding to the first link carried in the BAR frame; wherein the SSN_1 is the sequence number of the next data frame sent on the first link , Or the SSN_1 is greater than the sequence number of the data frame discarded by the first multilink device on the first link.
  • the content and functions of the elements or fields included in the data frame and the BAR frame can refer to the description of the subsequent method embodiments, which will not be repeated here.
  • FIG. 3C is a schematic structural diagram of a second multi-link communication device provided by an embodiment of the present application.
  • the second multi-link communication apparatus may include a receiving module 401 and a processing module 402.
  • the second multi-link communication device serves as the receiving end of multi-link aggregation transmission, and the detailed description of each module is as follows.
  • the receiving module 401 is configured to receive data frames on multiple links with the sending end; the multiple links include the first link;
  • the receiving module 401 is further configured to receive a block confirmation request BAR frame on the first link;
  • the processing module 402 is configured to analyze the initial sequence number SSN_1 corresponding to the first link carried in the BAR frame; wherein the SSN_1 is the sequence number of the next data frame to be sent on the first link, or The SSN_1 is greater than the sequence number of the data frame discarded by the sending end on the first link;
  • the processing module 402 is further configured to process data frames received on the multi-link.
  • the receiving module 401 is configured to receive at least one of a data frame and a BAR frame on multiple links with the sending end; the multiple links include the first link;
  • the receiving module 401 is configured to receive a block confirmation request BAR frame on the first link, where the BAR frame carries the SSN_1 corresponding to the first link;
  • the processing module 402 is configured to adjust the current start sequence number WinStart value of the scoreboard window according to the SSN corresponding to at least two of the multiple links; wherein, at least two of the multiple links
  • the corresponding SSN includes SSN_1 corresponding to the first link and SSN corresponding to other links stored locally by the receiving end;
  • the SSN corresponding to each link mentioned in this application refers to the respective SSN of each link.
  • the value of the respective SSN of each link may be the same or different; the multi-link communication device may
  • the SSN of each link can be set uniformly or separately, which is not limited in this application.
  • the second multi-link communication device further includes a memory or a buffer for storing the respective SSNs of the multiple links;
  • the processor 402 is further configured to process the data frame received on the multi-link according to the adjusted WinStart.
  • each module can also correspond to the corresponding description of the method embodiment of the present application, and execute the method and function performed by the second multi-link device in the foregoing embodiment.
  • the embodiment of the present application also provides a processor, which is configured to be coupled with the memory and used to execute any method and function related to the first multi-link device or the second multi-link device in any one of the embodiments of the present application .
  • 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 one of the embodiments of the present application involving the first multi-link device or the second multi-link device. Any method and function of the device.
  • the embodiment of the present application also provides a device for executing any method and function related to the first multi-link device or the second multi-link device in any one of the foregoing embodiments of the present application.
  • An embodiment of the present application also provides a wireless communication system, which includes at least one first multi-link device and at least one second multi-link device involved in any embodiment of the present application.
  • the multi-link device described in the above embodiment may be an access point or a station, but the scope of the multi-link device described in this application is not limited to this, and the structure of the multi-link device may not be Figure 3A ⁇ Figure 3C restrictions.
  • the multilink device can be a standalone device or can be part of a larger device.
  • the realization form of the multi-link device may be:
  • Independent integrated circuit IC or chip, or, chip system or subsystem
  • the IC collection may also include storage for storing data and instructions Components; (3) Modules that can be embedded in other devices; (4) Receivers, smart terminals, wireless devices, handhelds, mobile units, vehicle-mounted devices, cloud devices, artificial intelligence devices, etc.; (5) Others, etc. .
  • the implementation form of the multi-link device is a chip or a chip system
  • the chip shown in FIG. 4 includes a processor 501 and an interface 502.
  • the number of processors 501 may be one or more, and the number of interfaces 502 may be more than one.
  • the chip or chip system may include a memory 503.
  • the sender sends an MPDU, and at the same time sets the confirmation policy subfield in the quality of service (QoS) field to normal reception. If the receiver receives the MPDU correctly, it returns a message to the sender The ACK message indicates that it has received the MPDU correctly.
  • QoS quality of service
  • Block confirmation method based on normal confirmation the sender sends an aggregation (aggregation MPDU, A-MPDU), and at the same time sets the confirmation policy subfield in the QoS field to normal block confirmation, and the receiver parses each MPDU in it separately, according to each Whether each MPDU is successfully received, a block acknowledgement (BA) frame is returned.
  • BA block acknowledgement
  • a bitmap will be carried in the BA frame to indicate whether the corresponding MPDU or MSDU is successfully received. If a certain MPDU or MSDU is successfully received, the corresponding Bit is set to 1, otherwise it is set to 0.
  • the MPDU whose confirmation policy subfield in the QoS field is set to normal block confirmation is referred to as a QoS data frame or a data frame (indicated by data in the figure).
  • Block acknowledgement request (BAR) based on request:
  • the sender can send one or A-MPDUs, and at the same time set the acknowledgement policy subfield in the QoS field to request block acknowledgement. Only after the sending end sends a BAR frame, the receiving end returns a BA frame according to the previous reception of each MPDU or MSDU.
  • the format of the BAR frame is shown in Figure 5, which includes: frame control, duration, receiving address, sending address, BAR control, initial sequence control, frame check sequence and other fields; among them, the BAR control field includes: BAR confirmation strategy, Multi-TID, compressed bitmap, multicast retransmission mode, number of TID/TID and reserved (B5 ⁇ B11) sub-fields, the meaning of each main sub-field is as follows:
  • BAR confirmation strategy This indicator is used when delaying block confirmation. For a delayed block acknowledgment session, if the indicator position is 0, it means that after receiving the BAR frame, the receiving end will return an ACK after the short interframe space (SIFS); when the indicator position is 1, it means the receiving end There is no need to return an ACK after receiving the BAR frame.
  • SIFS short interframe space
  • Compressed bitmap If it is set to 1, it means that the BAR requires the receiving end to return a BA with a compressed bitmap.
  • the multi-TID indicator is not set to 1, this field carries the TID of the block confirmation session. If the multi-TID indicator bit is set to 1, this field carries the number of TIDs in the multi-TID BAR frame.
  • Starting sequence control field This field uses 12 bits (B4 to B15) to carry the starting sequence number (SSN).
  • Multi-TID This indicator bit is used to indicate whether the BAR is a basic BAR frame or a multi-TID BAR frame.
  • the frame format is shown in Figure 6.
  • each TID has a per-TID information and start sequence control field.
  • Each TID information field contains the TID value, and immediately following this field is the sequence control field corresponding to the TID.
  • the frame format of BA is shown in Figure 7. It includes: frame control, duration, receiving address, sending address, BA control, initial sequence control, frame check sequence and other fields; among them, BA control includes BA confirmation strategy, multiple TID, compressed bitmap, multicast retransmission Mode, TID/TID number and reserved (B5 ⁇ B11) subfields, the meaning of each main subfield is as follows:
  • BA confirmation strategy This indicator is used when delaying block confirmation. For a delayed block confirmation response, if the indication position is 0, it means that the receiving end will return an ACK after the SIFS after receiving the BA frame; when the indication position is 1, the receiving end does not need to return an ACK after receiving the BAR frame.
  • Compressed bitmap If it is set to 1, it means that the BA frame contains a compressed or 8 octet block confirmation bitmap. If set to 0, the BA frame contains uncompressed or 128 eight-bit block confirmation bitmaps.
  • the multi-TID indicator is not set to 1, this field carries the TID of the block confirmation session. If the multi-TID indicator bit is set to 1, this field carries the number of TIDs in the multi-TID BA frame.
  • Start sequence control field This field uses 12 bits in it to carry the start sequence number SSN.
  • the block confirmation bitmap can be 128 octets in the case of uncompressed BA, or 8 octets in the case of compressed BA.
  • the bitmap can indicate the receiving status of up to 64 MSDUs.
  • each MSDU is represented by a 16-bit bit, and each bit represents MSDU fragments (if any).
  • each MSDU is represented by a single bit. In this case, the representation of the reception status of each fragment is not supported.
  • Multi-TID This indicator bit is used to indicate whether the BA is a basic BA frame or a multi-TID BA frame.
  • the frame format is shown in Figure 8.
  • each TID has a per-TID information field, a starting sequence control field, and a BA bitmap field.
  • Each TID information field contains the TID value, followed by this field is the sequence control field and BA dot matrix corresponding to the TID.
  • the initialization of the block confirmation session is started by the initiator sending an "ADDBA request” frame.
  • the responder sends an ACK as a response to the correctly received "ADDBA request” frame.
  • the responder sends an "ADDBA response” frame, and if the initiator receives this frame correctly, it responds with an ACK. If the expected ACK is not received, the initiator and responder will retransmit "ADDBA request" and "ADDBA response". If the session establishment is unsuccessful, it will be detected by the initiating end's no-operation timeout.
  • the "ADDBA Request” and “ADDBA Response” frames carry the following main information:
  • Block confirmation strategy This field indicates whether the session is an immediate block confirmation or a delayed block confirmation session.
  • TID This field gives the communication type used in this session.
  • Buffer size This field indicates the number of frame buffers used by the responder to reorder frames. If this value is set by the initiator, it is the expected value, and the value set by the responder is the true value. Before the initiator requests a block confirmation, the number of MPDUs that have not received a response cannot exceed this value.
  • Block acknowledgment timeout value This field specifies how long the block acknowledgment session will terminate when there is no frame exchange in this session.
  • Start sequence number The sequence number of the first data frame sent by the initiator.
  • the receiving end maintains a scoreboard data structure to record which MPDUs have been received correctly.
  • the receiving end When the receiving end needs to return to BA, it will convert the scoreboard into a bitmap.
  • the BA frame will further indicate the serial number corresponding to the first bit in the bitmap, and the subsequent bits correspond to the subsequent serial numbers.
  • the sequence number of the MAC service data unit (MSDU) is 12 bits
  • the scoreboard represents a window of 4096 sequence number space (Sequence Number Space).
  • the scoreboard window is defined by the window start sequence number (WinStart), window end sequence number (WinEnd), and window length (WinSize).
  • Multi-link aggregation communication involves coordination between multiple links.
  • the MPDUs of the same TID of the data sending end can be transmitted through multiple links: link 1, link 2, link 3, and link n to increase The transmission rate of this TID data.
  • the data receiving end sorts the data packets of the same TID received on the multiple links according to the SN according to the sequence number (SN) carried in the header of each MPDU frame.
  • the protocol requires that the MAC layer must deliver MPDUs to the upper layer in order.
  • the sender sends A-MPDU1 and A-MPDU2 on link 1 and link 2, where the SNs corresponding to the MPDUs contained in A-MPDU1 are 1 ⁇ 31; the SNs corresponding to the MPDUs contained in A-MPDU2 are 32 ⁇ 59.
  • the receiving end feeds back the BA to the sending end on link 1 and link 2 respectively, and indicates which MPDUs are successfully received and which MPDUs are not successfully received. Assuming that the BA sent on link 2 is not successfully received by the sending end, it then sends a BAR frame on link 2 to request the receiving end to return to the BA, and set the SSN in the BAR frame to 32.
  • the receiving end will move WinStart to 32 after receiving the BAR frame, but this will cause the incorrectly received MPDUs in A-MPDU1 in the subsequent retransmission process, even if the receiving end is successfully received because its SN is less than WinStart And was discarded.
  • Prior art 1 For each link in a multi-link aggregation scenario, a scoreboard mechanism is used separately.
  • each link in addition to a global reorder buffer (Global Reorder Buffer), each link also has a local scoreboard or local reorder buffer ( Local Reorder Buffer).
  • Local Reorder Buffer In order to avoid MPDUs waiting too long in the local buffer, a new BAR frame called Local BAR (L-BAR) needs to be introduced.
  • the frame format is shown in Figure 11:
  • the difference from the BAR frame shown in Figure 5 is that the reserved bit B5 is used to indicate whether to carry the SN dot matrix indication information of the MPDU transmitted on the link, which is used to indicate the transmission on the link.
  • the SN range corresponding to MPDUs, and the SN corresponding to the first bit is indicated by the start sequence number field.
  • the receiving end After receiving the L-BAR frame, the receiving end determines how to move the start sequence number (WinStart) of the scoreboard window corresponding to the link according to the SN dot matrix indication information of the MPDU transmitted by the link carried by it.
  • WinStart start sequence number
  • the technical solution provided by the first prior art requires modifying the existing BAR frame and adding an SN dot matrix diagram indicating information of the MPDU transmitted by the link to each link, and the signaling overhead is huge.
  • a reserved bit (reserved bit) B5 is used to indicate whether the receiving end needs to move the scoreboard according to the BAR frame.
  • the start sequence number of the window (WinStart), the field corresponding to this B5 can be called "whether to move indication”.
  • the sender When the sender wants the receiver to move the start sequence number (WinStart) of the scoreboard window according to the BAR frame, the sender must ensure that the SN of the MPDU sent is greater than the SSN carried in the BAR frame, that is, the SN of the MPDU is less than The SSN carried in the BAR frame will not be sent.
  • WinStart start sequence number
  • the technical solution provided by the second prior art also needs to modify the existing BAR frame, and the multiple links of the sender need to be able to interact with each other to determine under what circumstances the receiver can move the starting sequence number of the scoreboard window (WinStart), when the receiver needs to move WinStart, set the "Move Instruction" to 1.
  • WinStart the starting sequence number of the scoreboard window
  • WinStart the starting sequence number of the scoreboard window
  • this application provides a movement rule for the start sequence number (WinStart) of the scoreboard window for multi-link aggregation transmission.
  • the moving rule of the starting sequence number (WinStart) of the scoreboard window acts on the receiving end and comprehensively refers to the respective SSNs of multiple links to decide whether to move the WinStart.
  • the SSN corresponding to multiple links in this application refers to the respective SSN of the multiple links.
  • the value of the respective SSN of each link may be the same, may be partially different, or may be different. ;
  • the sender can set the SSN of each link uniformly or separately, which is not limited in this application.
  • the receiving end comprehensively considers the SSN of multiple links maintained or stored locally;
  • the multiple links involved in the embodiments of this application refer to multiple links between the sending end and the receiving end; the receiving end can consider whether to move WinStart after comprehensively considering the respective SSNs of the multiple links.
  • the respective SSNs of all links in the multiple links may also be considered SSNs corresponding to at least two links in the multiple links.
  • the receiving end when the receiving end receives a BAR frame sent by a certain link, when the receiving end adjusts WinStart, it not only considers the SSN carried in the BAR frame, but also It also needs to be compared with the SSN carried in the BAR sent by other links, and take the smallest value in order to adjust the value of WinStart to the minimum value of the corresponding SSN of the BAR sent by multiple links, so that the sent MPDU will not appear.
  • the SN is smaller than the case of WinStart. It should be understood that the SSN carried in the BAR sent by other links has been stored locally at the receiving end, so there is no need for interaction between multiple links at the sending end.
  • the receiving end receives the MPDU sent by a certain link, if the SN corresponding to the data frame sent by a certain link falls outside the current scoreboard window, but is within half of the sequence window space range, then adjust WinStart , So that WinEnd is equal to the SN, if there is an SSN that is smaller than the adjusted WinStart among the SSNs of each link stored locally, then the locally stored SSN that is smaller than WinStart is updated to WinStart.
  • the sender does not need to change the SSN setting rules of the existing BAR frame, nor does it need to interact between multiple links at the sender.
  • the receiver adjusts WinStart according to the receiving conditions of the multiple links. This method does not need to modify the existing BAR frame, nor is it mandatory for the sending end to be able to interact between multiple links, which is especially suitable for non-collocated multiple link aggregation scenarios.
  • WinStart window start sequence number
  • the SSN of each link is initialized to SSN_0, which is carried in the ADDBA Request/Response frame;
  • the scoreboard is moved to the right to adapt to the SN, that is, the scoreboard window
  • the receiving end when the receiving end receives a BAR frame sent by a certain link, the SSN value carried in the BAR frame is combined with the SSN value corresponding to other links
  • the minimum value of is recorded as WinStart_x; then it is compared with the WinStart_y stored locally before receiving the BAR frame, and the maximum value of the two is used as the current WinStart to adjust the scoreboard window; then use the adjusted scoreboard window to adjust each chain
  • the received data frame is processed.
  • the receiving end can adjust WinStart adaptively.
  • the purpose of this is to take into account the MPDU sent by multiple links. This method does not require interaction between multiple links, and it does not need to change the existing BAR frame. It saves signaling overhead to a great extent and takes into account the transmission of multiple links.
  • WinStart window start sequence number
  • the SSN of each link is initialized to SSN_0, which is carried in the ADDBA Request/Response frame;
  • the SSN_i carried in the BAR frame and the SSN of other links stored locally at the receiving end take the minimum value and record it as WinStart_x, that is, min(SSN_1,SSN_2,...,SSN_N) is marked as WinStart_x, WinStart before receiving the BAR frame is marked as WinStart_y, then WinStart is moved to max(WinStart_x,WinStart_y);
  • this application Based on the aforementioned rules for sending BAR by the sender and WinStart movement rules by the receiver, this application implements the multi-chain provided by this application in the network system shown in Figure 1 and the structure of the multi-link device shown in Figures 2 to 4
  • the method of channel aggregation transmission is shown in Figure 13, including:
  • Step 100 The sending end sends data frames (MPDUs) to the receiving end on multiple links; among them, for data frames sent on different links, the corresponding SSNs may be the same or different;
  • Step 101 The receiving end receives the data frame on multiple links
  • Step 102 The sending end sends a block confirmation request BAR frame on the first link; the BAR frame carries a starting sequence number SSN_1 corresponding to the first link;
  • the SSN_1 is the sequence number of the next data frame sent on the first link, or the SSN_1 is greater than the number of the data frame discarded by the sending end on the first link. serial number;
  • Step 103 The receiving end receives a block confirmation request BAR frame on the first link
  • Step 104 The receiving end adjusts the WinStart value of the current start sequence number of the scoreboard window according to the respective SSNs of the multiple links;
  • Step 105 The receiving end processes the data frame received on the multi-link according to the adjusted WinStart.
  • the sending end can be the AP shown in Figure 1, and correspondingly, the receiving end is STA2; or the sending end is STA2 and the receiving end is AP; or the sending end is STA4 and the receiving end is STA5; or the sending end is STA5, The receiving end is STA4.
  • the sending end is the first multi-link device as shown in Figure 2, and the receiving end is the second multi-link device; the multiple links are respectively link 1, link 2, link 3...link n.
  • Steps 100 and 102 performed by the above sending end may be performed by the transceiver 205 of the multilink device 200 as shown in FIG. 3A, or by the sending module 302 in the first multilink communication device as shown in FIG. 3B. Execution; It can also be executed through the interface 302 in the chip system as shown in FIG. 4.
  • Steps 101 and 103 performed by the receiving end may be performed by the transceiver 205 of the multi-link device 200 as shown in FIG. 3A, and step 104 may be performed by the processor 201.
  • Steps 101 and 103 performed by the receiving end may also be performed by the receiving module 401 of the second multi-link communication device as shown in FIG. 3B, and steps 104 and 105 may be performed by the processing module 402.
  • Steps 101 and 103 can also be executed by the interface 302 in the chip system as shown in FIG. 4, and step 104 and step 105 can also be executed by the processor 301.
  • the receiving end also stores the SSN and scoreboard window parameters corresponding to each link, such as WinStart, WinSize, and optionally WinEnd, which can be stored through the memory 202 shown in FIG. 3A, or as shown in FIG. 4
  • the specific form of the memory 303 is not limited to tables and so on.
  • the first embodiment will describe the movement rule 1 of the start sequence number (WinStart) of the scoreboard window in the technical solution of link aggregation transmission as shown in FIG. 13 in this application.
  • the sending end sends MPDUs to the receiving end through two aggregated links as an example.
  • the confirmation strategy fields of MPDUs are all set to the block confirmation strategy based on the request, and there is no situation where the SN of a certain MPDU falls under WinEnd ⁇ SN ⁇ WinStart+2 ⁇ 11.
  • both SSN_1 and SSN_2 are initialized to SSN_0, where SSN_0 is the ADDBA request sent by the sender and the start sequence number carried in the ADDBA response frame sent by the receiver to the sender, SSN_1 and SSN_2 are aggregation link 1 respectively And the SSN value carried in the BAR frame received on aggregated link 2.
  • the receiving end when the receiving end receives a BAR frame sent by a certain link, when the receiving end adjusts WinStart, it not only considers the SSN carried in the BAR frame, but also It needs to be compared with the SSN carried in the BAR sent by other links, and the smallest value is used to adjust the value of WinStart to the minimum value of the corresponding SSN of the BAR sent by multiple links, so that there will be no MPDU sent
  • the serial number is less than WinStart, which causes the receiver to be discarded even if it receives correctly.
  • SSN in the ADDBA request/response frame is set to 4, SSN_1 and SSN_2 are initialized to 4, assuming that only the block confirmation strategy is used on link1 and link2 and the sender has not sent a BAR frame before, and has not sent an MPDU with SN greater than 103 (The figure shows Data).
  • WinStart starting sequence number
  • Figure 15 is only an example.
  • the receiving end when the receiving end receives a BAR frame, it will adjust WinStart according to the minimum value of the SSN carried in the BAR frame and the SSN of each link maintained or stored locally; thereby avoiding other links
  • the MPDU to be sent on the road (the SN of the MPDU is smaller than the SSN carried in the BAR frame) misoperation.
  • the receiving end when it receives a BAR frame, it will adjust WinStart according to the SSN carried in the BAR frame and the minimum value of the SSN of each link maintained or stored locally; a certain link is received
  • WinStart can also be adjusted according to the SN corresponding to the data frame, and the locally stored SSN value can be adjusted adaptively.
  • the implementation of the third embodiment can ensure that the data frames sent by multiple links are received correctly and will not be deleted by mistake, which improves the efficiency of data transmission.
  • SSN in the ADDBA request/response frame is set to 0, SSN_1 and SSN_2 are initialized to 0, assuming that only the block acknowledgment strategy is used on link1 and link2 and the sender has not sent BAR frames before, and has not sent MPDUs with SN greater than 99 (In Figure 18, it is indicated as Data).
  • the SN of the MPDU sent by the sender to the receiver on Link1 is 103.
  • the movement rule 2 is applied.
  • WinStart starting sequence number
  • Figure 18 is only an example.
  • WinStart scoreboard window starting sequence number
  • WinStart when the receiving end receives a BAR frame, it will adjust WinStart according to the minimum value of the SSN carried in the BAR frame and the locally maintained or stored SSN, as well as the WinStart before receiving the BAR frame; When the data frame sent by a certain link is reached, WinStart can also be adjusted according to the SN corresponding to the data frame; thereby avoiding the error of the MPDU to be sent on other links (the SSN of the MPDU is smaller than the SSN carried in the BAR frame). operate.
  • the fifth embodiment will describe, by way of example, a multi-link transmission technical solution using the movement rule 2 of the scoreboard window start sequence number (WinStart) provided in this application.
  • SSN in the ADDBA request/response frame is set to 0, SSN_1 and SSN_2 are initialized to 0, assuming that only the block acknowledgment strategy is used on link1 and link2 and the sender has not sent BAR frames before, and has not sent MPDUs with SN greater than 99 (In Figure 19, it is indicated as Data).
  • the SN of the MPDU sent by the sender to the receiver on Link1 is 103.
  • the receiving end when receiving the BAR frame, the receiving end will adjust the WinStart according to the SSN carried in the BAR frame and the minimum value of the locally maintained or stored SSN, as well as the WinStart before receiving the BAR frame; When reaching a data frame sent by a certain link, WinStart can also be adjusted according to the SN corresponding to the data frame.
  • the implementation of the fifth embodiment can ensure that the data frames sent by multiple links are correctly received and will not be deleted by mistake, which improves the efficiency of data transmission.
  • the receiving end may receive multiple frames at the same time, which may be data frames (MPDU) or It is a BAR frame, and it can also include a data frame and a BAR frame at the same time. At this time, the receiving end can process them one by one in any order.
  • MPDU data frames
  • BAR BAR frame
  • the above method embodiment shown in FIG. 13 and the first to fifth embodiments do not need to add an SN dot matrix of the MPDU transmitted by the link for each link in the BAR frame.
  • the indication information saves signaling overhead; compared with the prior art 2 and the prior art 3, there is no need to limit the SSN settings in the BAR frame sent by the sender, and there is no need for multi-link interaction between the senders.
  • the embodiment of this application also proposes a BAR transmission rule, which does not require interaction between multiple links and does not modify the existing BAR frame.
  • a BAR transmission rule which does not require interaction between multiple links and does not modify the existing BAR frame.
  • the BAR sending rules for the sender are as follows:
  • the SSN carried in the BAR sent on each aggregated link can be set to the sequence number of the next MPDU to be sent on the link or a value greater than the sequence number of the discarded MPDU.
  • the rearrangement buffer is flushed by sending BAR, and the hole represented by the MSDU retransmitted over time is flushed out, so that subsequent complete MSDUs will not be hanged up needlessly to wait for the sequence to become complete.
  • it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it can be implemented in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions described in the embodiments of the present application are generated in whole or in part.
  • the computer may be a general-purpose computer, a special-purpose 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.
  • the computer instructions may be transmitted from a website, computer, server, or data center. Transmission to another website, computer, server or data center via wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.).
  • 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 a 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

本申请实施例公开了一种多链路聚合传输方法及相关装置。所述方法包括：接收端在与发送端之间的多条链路上接收数据帧和BAR帧中的至少一种；所述多条链路包括第一链路；所述接收端在所述第一链路上接收块确认请求BAR帧，所述BAR帧中携带所述第一链路对应的SSN_1；所述接收端根据各条链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值；所述接收端根据调整后的WinStart，对多链路上接收的数据帧进行处理。实施本申请，接收端可以自适应的调整WinStart，该方法不需要多条链路之间进行交互，同时也不需要更改现有的BAR帧，最大程度的节约信令开销并兼顾多条链路的传输。本申请可适用于802.11be及多种wifi系统中。

Description

一种多链路通信方法及相关装置 技术领域
本申请涉及通信技术领域，尤其涉及一种多链路通信方法及相关装置。
背景技术
随着无线技术的发展，多链路设备(multi-link device，MLD)可以支持多链路通信，例如同时在2.4GHz、5GHz以及60GHz频段上进行通信，即使在天线数受限的情况下，多链路设备也可以在不同的频段上进行切换，从而选择最佳的频段，保证其通信质量。随着越来越多的应用流量由无线网络承载，高速率是无线保真(wreless-fidelity，WiFi)系统的演进目标。为了提升多链路设备中的站点的峰值速率，多链路聚合通信已经成为下一代无线局域网(wireless local area networks，WLAN)技术的特性。
多链路聚合通信涉及多条链路之间的协调工作，数据发送端的同一业务标识符(Traffic Identifier，TID)的多个媒体接入控制协议数据单元(MAC protocol data unit，MPDU)可以通过多条链路进行传输，以增大该TID数据包的传输速率。数据接收端根据每个MPDU帧头携带的序列号(sequence number,SN)对多条链路上接收的相同TID的数据包按照SN进行排序。协议要求MAC层必须按照顺序将完整的MSDU(MAC Service Data unit,MAC层服务数据单元)往上层递交。
现有技术中，通过记分板机制实现对发送端发送的MPDU的接收情况进行确认。但是，目前多链路聚合下，使用现有的记分板机制，对传输的MPDU的接收情况进行确认，会存在以下问题：
如果发送端通过一条链路(link)发送块确认请求(block acknowledgement requirement,BAR)时，在BAR中设置了一个起始序列号(Starting sequence number，SSN)值，但其他链路上有小于该SSN值的待传MPDU，会导致接收端移动记分板的起始序列号(示意为：WinStart)，从而导致之后发送端发送的小于该SSN值的MPDUs即便是被接收端正确接收，也会被接收端丢弃。
发明内容
为解决上述技术问题，本申请实施例提供一种多链路聚合传输方法和设备，芯片系统，计算机可读存储介质和计算机程序产品。
本申请实施例第一方面，提供一种多链路聚合传输方法，应用于多链路聚合传输的接收端，包括：
接收端在与发送端之间的多条链路上接收数据帧和BAR帧中的至少一种；所述多条链路包括第一链路；
所述接收端在所述第一链路上接收块确认请求BAR帧，所述BAR帧中携带所述第一链路对应的SSN_1；
所述接收端根据所述多条链路中至少两条链路对应的SSN，调整当前的记分板窗口起始 序列号WinStart值；其中，所述多条链路中至少两条链路对应的SSN，包括所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN；
所述接收端根据调整后的WinStart，对所述多链路上接收的数据帧进行处理。
本申请实施例第二方面，提供一种多链路设备，其作为多链路聚合传输的接收端，包括：
收发器，用于在与发送端之间的多条链路上接收数据帧和BAR帧中的至少一种；所述多条链路包括第一链路；
所述收发器，用于在所述第一链路上接收块确认请求BAR帧，所述BAR帧中携带所述第一链路对应的SSN_1；
处理器，用于根据所述多条链路中至少两条链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值；其中，所述多条链路中至少两条链路对应的SSN，包括所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN；
所述处理器，还用于根据调整后的WinStart，对所述多链路上接收的数据帧进行处理。
本申请实施例第三方面，提供一种多链路聚合传输方法，应用于多链路聚合传输的接收端，包括：
接收端在与发送端之间的多条链路上接收数据帧；所述多条链路包括第一链路；
所述接收端在所述第一链路上接收块确认请求BAR帧；
所述接收端解析所述BAR帧中携带的与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号；
所述接收端对所述多链路上接收的数据帧进行处理。
本申请实施例第四方面，提供一种多链路设备，其作为多链路聚合传输的接收端，包括：
收发器，用于在与发送端之间的多条链路上接收数据帧；所述多条链路包括第一链路；
所述收发器，还用于在所述第一链路上接收块确认请求BAR帧；
处理器，用于解析所述BAR帧中携带的与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号；
所述处理器，还用于对所述多链路上接收的数据帧进行处理。
本申请实施例第五方面，提供一种芯片系统，包括至少一个处理器和接口；其中，
所述接口，用于输入来自与发送端之间的多条链路上的数据帧；所述多条链路包括第一链路；
所述接口，还用于输入在所述第一链路上接收到的块确认请求BAR帧，所述BAR帧中携带所述第一链路对应的SSN_1；
处理器，用于根据所述多条链路中至少两条链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值；其中，所述多条链路中至少两条链路对应的SSN，包括所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN；
所述处理器，还用于根据调整后的WinStart，对所述多链路上接收的数据帧进行处理。
本申请实施例第六方面，提供一种芯片系统，包括至少一个处理器和接口；其中，
所述接口，用于输入在与发送端之间的多条链路上接收到的数据帧；所述多条链路包括第一链路；
所述接口，还用于输入在所述第一链路上接收到的块确认请求BAR帧；
所述处理器，用于解析所述BAR帧中携带的与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号；
所述处理器，还用于对所述多链路上接收的数据帧进行处理。
本申请实施例第一至第六方面任一方面的第一种实现方式中，所述根据所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值，包括：
调整所述WinStart为SSN最小值；其中，SSN最小值为所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN中最小的SSN。
其中，所述根据调整后的WinStart，对所述多链路上接收的数据帧进行处理，包括：
接收到某链路发送的数据帧，所述数据帧的序列号SN满足WinEnd<SN<WinStart+2^11，调整所述WinStart为WinStart＝SN-WinSize+1；
将所述多条链路对应的SSN中，小于调整后的WinStart的SSN，更新为与所述调整后的WinStart相同。换句话说，凡是小于调整后的WinStart的各链路对应的SSN，都更新为调整之后的WinStart。
本申请实施例第一至第六方面任一方面的第二种实现方式中，根据各链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值，包括：
调整所述WinStart为WinStart最大值；
其中，WinStart最大值为接收所述BAR之前的WinStart与接收所述BAR后的WinStart中最大的WinStart；其中，接收所述BAR后的WinStart为SSN最小值；所述SSN最小值为所述第一链路对应的SSN_1的SSN_1和本地存储的其他链路对应的SSN中最小的SSN。
其中，所述根据调整后的WinStart，对所述多链路上接收的数据帧进行处理，包括：
接收到某条链路发送的数据帧，所述数据帧的序列号SN满足WinEnd<SN<WinStart+2^11，调整所述WinStart为WinStart＝SN-WinSize+1。
本申请实施例第一至第六方面任一方面的第一种或第二种实现方式中，所述SSN_1为所述第一链路下一个上被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号。
本申请实施例第七方面，提供一种多链路聚合传输方法，应用于多链路聚合传输的发送端，包括：
发送端在与接收端之间的多条链路上发送数据帧；所述多条链路包括第一链路；
所述发送端在所述第一链路上发送块确认请求BAR帧；所述BAR帧中携带有与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路上下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号。
本申请实施例第八方面，提供一种多链路设备，其作为多链路聚合传输的发送端，包括：
收发器，用于在与接收端之间的多条链路上发送数据帧；所述多条链路包括第一链路；
所述收发器，还用于在所述第一链路上发送块确认请求BAR帧；
所述处理器，用于解析所述BAR帧中携带的与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路上下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被所述发送端被丢弃的数据帧的序列号。
本申请第八方面，提供一种芯片系统，包括：至少一个处理器和接口；
所述接口，用于输出在与接收端之间的多条链路上发送的数据帧；所述多条链路包括第一链路；
所述接口，还用于输出在所述第一链路上发送的块确认请求BAR帧；
所述处理器，用于在所述BAR帧中携带与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路上下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被丢弃的数据帧的序列号。
本申请实施例第九方面，提供了一种第一多链路通信装置，该第一多链路通信装置被配置为实现上述第一方面或第三方面中接收端执行的方法和功能，由硬件/软件实现，其硬件/软件包括与上述功能相应的模块。
本申请实施例第十方面，提供了一种第二多链路通信装置，该第二多链路设备被配置为实现上述第七方面发送端所执行的方法和功能，由硬件/软件实现，其硬件/软件包括与上述功能相应的模块。
本申请实施例第十一方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如前述第一方面或第三方面或第七方面的任一方面所述的方法。
本申请实施例第十二方面，提供一种计算机可读存储介质，所述计算机可读存储介质用于存储指令，当所述指令被执行时，使得如前述第一方面或第三方面或第七方面的任一方面所述的方法被实现。
本申请实施例第十三方面，提供了一种芯片，包括处理器，用于从存储器中调用并运行存储器中存储的指令，使得安装有芯片的通信设备执行上述第一方面或第三方面或第七方面的方法。
本申请实施例第十四方面，提供另一种芯片，该芯片可以为第一多链路设备或第二多链路设备内的芯片，该芯片包括：输入接口、输出接口和处理电路，输入接口、输出接口与电路之间通过内部连接通路相连，处理电路用于执行上述第一方面或第三方面或第七方面的方法。
本申请实施例第十五方面，提供另一种芯片，包括：输入接口、输出接口、处理器，可选的，还包括存储器，输入接口、输出接口、处理器以及存储器之间通过内部连接通路相连，处理器用于执行存储器中的代码，当代码被执行时，处理器用于执行上述第一方面或第三方面或第七方面的方法。
本申请实施例第十六方面，提供一种装置，用于实现上述任一方面的方法。
附图说明
为了更清楚地说明本申请实施例或背景技术中的技术方案，下面将对本申请实施例或背景技术中所需要使用的附图进行说明。
图1是本申请实施例提供的一种通信系统的架构示意图；
图2是本申请实施例提供的一种多链路设备之间传输的示意图；
图3A是本申请实施例提供的一种多链路设备的结构示意图；
图3B是本申请实施例提供的一种多链路通信装置的结构示意图；
图3C是本申请实施例提供的一种多链路通信装置的结构示意图；
图4是本申请实施例提供的一种芯片系统的结构示意图；
图5是一种BAR帧的示意图；
图6是一种BAR帧的又一示意图；
图7是一种BA帧的示意图；
图8是一种BA帧的又一示意图；
图9是一种多链路聚合传输示意图；
图10是一种多链路聚合传输架构图；
图11是一种被更改的BAR帧的示意图；
图12是又一种被更改的BAR帧的示意图；
图13是本申请实施例提供的一种多链路聚合传输的流程示意图；
图14是本申请实施例提供的又一多链路聚合传输的流程示意图；
图15是本申请实施例提出的又一多链路聚合传输的流程示意图；
图16是一种多链路聚合传输的流程示意图；
图17是本申请实施例提供的又一多链路聚合传输的流程示意图；
图18是本申请实施例提出的又一多链路聚合传输的流程示意图；
图19是本申请实施例提供的又一多链路聚合传输的流程示意图。
具体实施方式
下面结合本申请实施例中的附图对本申请实施例进行描述。
图1是本申请实施例提供的一种通信系统的架构示意图。该通信系统包括接入点设备和站点设备。通信系统中可以包含一个或多个接入点(access point，AP)，图1中只示意了1个。该通信系统中还包括一个或多个站点(station，STA)，例如图1中示意的STA1～STA6。其中，STA2与AP之间存在多条链路，STA2为多链路设备；STA4和STA5之间也存在多条链路，STA4和STA5也为多链路设备。本申请实施例中的多链路设备可以为站点设备，也可为接入点设备。
图1所示的架构也可以扩展至基站(base station，BS)和终端设备(user equipment，UE)的应用场景。其中，AP可以为移动用户进入有线网络的接入点，主要部署于家庭、大楼内部以及园区内部，典型覆盖半径为几十米至上百米，当然，也可以部署于户外。
AP相当于一个连接有线网和无线网的桥梁，主要作用是将各个无线网络客户端连接到一起，然后将无线网络接入以太网。具体的，AP可以是带有WiFi芯片的终端设备或者网络设备。AP可以为支持802.11be及未来的802.11标准制式的设备。AP也可以为支持802.11ax、802.11ac、802.11n、802.11g、802.11b及802.11a等多种无线局域网(wireless local area networks，WLAN)制式的设备。STA可以为无线通讯芯片、无线传感器或无线通信终端。例如支持WiFi通讯功能的移动电话、支持WiFi通讯功能的平板电脑、支持WiFi通讯功能的机顶盒、支持WiFi通讯功能的智能电视、支持WiFi通讯功能的智能可穿戴设备、支持WiFi通讯功能的车 载通信设备和支持WiFi通讯功能的计算机。可选地，STA可以支持802.11be及未来的802.11标准制式的设备。STA也可以支持802.11ax、802.11ac、802.11n、802.11g、802.11b及802.11a等多种WLAN制式。
虽然本申请实施例主要以部署IEEE 802.11的网络为例进行说明，本领域技术人员容易理解，本申请涉及的各个方面可以扩展到采用各种标准或协议的其它网络，例如，BLUETOOTH(蓝牙),高性能无线LAN(high performance radio LAN，HIPERLAN)(一种与IEEE 802.1 1标准类似的无线标准，主要在欧洲使用)以及广域网(WAN)、无线局域网(wireless local area network,WLAN)、个人区域网(personal area network,PAN)或其它现在已知或以后发展起来的网络。因此，无论使用的覆盖范围和无线接入协议如何，本申请提供的各种方面可以适用于任何合适的无线网络。
如图2所示，图2是本申请实施例提供的一种多链路设备之间的关联关系示意图。图2中所示的多链路设备包括第一多链路设备和第二多链路设备，第一多链路设备或第二多链路设备可以分别包括至少一个多链路逻辑实体，一个多链路逻辑实体可以包括一个或多个站点，每个站点分别工作在不同的链路上。其中，第一多链路设备中的STA1和STA2属于一个多链路逻辑实体，第一多链路设备中的STAn属于另一个多链路逻辑实体。第二多链路设备中的STA1和STA2属于一个多链路逻辑实体，第二多链路设备中的STAn属于另一个多链路逻辑实体。如果第一多链路设备需要与第二多链路设备进行通信，则需要第一多链路设备中的每个站点与第二多链路设备中对应的站点进行关联。
如图2所示，第一多链路设备中的STA1与第二多链路设备中的STA1相关联，工作在聚合链路1(简称链路1)上。第一多链路设备中的STA2与第二多链路设备中的STA2相关联，工作在聚合链路2(简称链路2)上。第一多链路设备中的STAn与第二多链路设备中的STAn相关联，工作在聚合链路n(链路n)上。使得第一多链路设备中每个站点可以在各自链路上与第二多链路设备中对应的站点建立连接，实现两个多链路设备之间的多链路通信。
本申请实施例中的所涉及的多链路设备，其可以包括硬件结构、软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能可以以硬件结构、软件模块、或者硬件结构加软件模块的方式来实现。
图3A为本申请实施例提供的一种多链路设备200的结构示意图。如图3A所示，该多链路设备200可包括：处理器201、收发器205，可选的还包括存储器202。
所述收发器205可以称为收发单元、收发机、或收发电路等，用于实现收发功能。收发器205可以包括接收器和发送器，接收器可以称为接收机或接收电路等，用于实现接收功能；发送器可以称为发送机或发送电路等，用于实现发送功能。
存储器202中可存储计算机程序或软件代码或指令204，该计算机程序或软件代码或指令204还可称为固件。处理器201可通过运行其中的计算机程序或软件代码或指令203，或通过调用存储器202中存储的计算机程序或软件代码或指令204，对MAC层和PHY层进行控制，以实现本申请下述各实施例。其中，处理器201可以为中央处理器(central processing unit，CPU)，存储器202例如可以为只读存储器(read-only memory，ROM)，或为随机存取存储器(random access memory，RAM)。
本申请中描述的处理器201和收发器205可实现在集成电路(integrated circuit，IC)、模 拟IC、射频集成电路RFIC、混合信号IC、专用集成电路(application specific integrated circuit，ASIC)、印刷电路板(printed circuit board，PCB)、电子设备等上。
上述多链路设备200还可以包括天线206，该多链路设备200所包括的各模块仅为示例说明，本申请不对此进行限制。
请参见图3B，图3B是本申请实施例提供的一种第一多链路通信装置的结构示意图，该第一多链路通信装置可以用于实现本申请实施例中涉及第一多链路设备的任意方法和功能，第一多链路通信装置可以包括处理模块301、发送模块302。可选的，发送模块302对应第一多链路设备包括的一个基带电路和一个射频电路。该第一多链路通信装置作为多链路聚合传输的发送端，其中，各个模块的详细描述如下。
在一个实施例中：
发送模块302，用于在与第二多链路设备之间的多条链路上发送数据帧；所述多条链路包括第一链路；
所述发送模块302，还用于在所述第一链路上发送块确认请求BAR帧；
所述处理模块301，用于解析所述BAR帧中携带的与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被所述第一多链路设备丢弃的数据帧的序列号。
其中，数据帧和BAR帧包括的元素或字段的内容以及功能可参考后续方法实施例的描述，此处不再赘述。
请参见图3C，图3C是本申请实施例提供的一种第二多链路通信装置的结构示意图，该第二多链路通信装置可以用于实现本申请任意实施例中涉及第二多链路设备的任意方法和功能，第二多链路通信装置可以包括接收模块401以及处理模块402。其中，第二多链路通信装置作为多链路聚合传输的接收端，各个模块的详细描述如下。
一种实现方式中，
接收模块401，用于在与发送端之间的多条链路上接收数据帧；所述多条链路包括第一链路；
所述接收模块401，还用于在所述第一链路上接收块确认请求BAR帧；
处理模块402，用于解析所述BAR帧中携带的与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号；
所述处理模块402，还用于对所述多链路上接收的数据帧进行处理。
另一种实现方式中，
接收模块401，用于在与发送端之间的多条链路上接收数据帧和BAR帧中的至少一种；所述多条链路包括第一链路；
接收模块401，用于在所述第一链路上接收块确认请求BAR帧，所述BAR帧中携带所述第一链路对应的SSN_1；
处理模块402，用于根据所述多条链路中至少两条链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值；其中，所述多条链路中至少两条链路对应的SSN，包括所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN；
应理解，本申请所说的各链路对应的SSN，是指的各条链路各自的SSN，各条链路各自 的SSN的值可以相同，也可以各不相同；多链路通信装置可以对各条链路的SSN进行统一设置，也可以分别进行设置，本申请不做限定。
可选的，第二多链路通信装置还包括存储器或者缓存，用于存储多条链路各自的SSN；
所述处理器402，还用于根据调整后的WinStart，对所述多链路上接收的数据帧进行处理。
上述两种方式中的数据帧和BAR帧包括的元素或字段的内容以及功能可参考后续方法实施例的描述，此处不再赘述。
需要说明的是，各个模块的实现还可以对应本申请方法实施例的相应描述，执行上述实施例中第二多链路设备所执行的方法和功能。
本申请实施例还提供了一种处理器，用于与存储器耦合，用于执行本申请实施例中任一实施例中涉及第一多链路设备或第二多链路设备的任意方法和功能。
本申请实施例还提供了一种包含指令的计算机程序产品，其在计算机上运行时，使得计算机执行本申请各实施例中任一实施例中涉及第一多链路设备或第二多链路设备的任意方法和功能。
本申请实施例还提供了一种装置，用于执行上述本申请实施例中任一实施例中涉及第一多链路设备或第二多链路设备的任意方法和功能。
本申请实施例还提供一种无线通信系统，该系统包括本申请任一实施例中涉及的至少一个第一多链路设备和至少一个第二多链路设备。
如前所述，以上实施例描述中的多链路设备可以是接入点或者站点，但本申请中描述的多链路设备的范围并不限于此，而且多链路设备的结构可以不受图3A～图3C的限制。多链路设备可以是独立的设备或者可以是较大设备的一部分。例如所述多链路设备的实现形式可以是：
(1)独立的集成电路IC，或芯片，或，芯片系统或子系统；(2)具有一个或多个IC的集合，可选的，该IC集合也可以包括用于存储数据，指令的存储部件；(3)可嵌入在其他设备内的模块；(4)接收机、智能终端、无线设备、手持机、移动单元、车载设备、云设备、人工智能设备等等；(5)其他等等。
对于多链路设备的实现形式是芯片或芯片系统的情况，可参见图4所示的芯片的结构示意图。图4所示的芯片包括处理器501和接口502。其中，处理器501的数量可以是一个或多个，接口502的数量可以是多个。可选的，该芯片或芯片系统可以包括存储器503。
本申请实施例并且不限制权利要求书的保护范围和适用性。本领域技术人员可以在不脱离本申请实施例范围的情况下对本申请涉及的元件的功能和部署进行适应性更改，或酌情省略、替代或添加各种过程或组件。
为便于理解，下面先对本文涉及的相关技术方案或技术术语进行简单的介绍。
1、确认机制
对于MPDU是否被正确接收，通常是通过确认机制进行确认的，通常有如下三种确认方式：
基于ACK的确认方式：发送端发送一个MPDU，同时将服务质量(quality of service,QoS)字段中的确认策略子字段设置为正常接收，接收端如果正确接收到该MPDU，则向发送端返回一个ACK消息表示其正确接收到该MPDU。
基于正常确认的块确认方式：发送端发送一个聚合(aggregation MPDU，A-MPDU)，同时将QoS字段中的确认策略子字段设置为正常块确认，接收端分别解析其中的每个MPDU，根据每个MPDU是否接收成功，返回一个块确认(block acknowledgement，BA)帧。BA帧中会携带一个bitmap来指示对应的MPDU或者MSDU是否接收成功。如果某个MPDU或者MSDU接收成功，则将相应Bit置1，否则置0。
本申请后续的实施例中，将QoS字段中的确认策略子字段设置为正常块确认的MPDU简称为QoS数据帧或者数据帧(图中用data表示)。
基于请求的块确认(block acknowledgement request,BAR)：发送端可以发送一个或者A-MPDUs，同时将QoS字段中的确认策略子字段设置为请求块确认。只有当发送端发送一个BAR帧后，接收端才根据之前各个MPDU或者MSDU的接收情况，返回一个BA帧。
2、BAR帧
BAR帧的格式如图5所示，其包括：帧控制，时长，接收地址，发送地址，BAR控制，起始序列控制，帧校验序列等字段；其中，BAR控制字段包括：BAR确认策略，多TID，压缩点阵图，组播重传模式，TID/TID数目和保留(B5～B11)等子字段，各主要子字段的含义如下：
BAR确认策略：该指示位在延迟块确认时使用。对于一个延时块确认会话，如果该指示位置0，表示接收端收到BAR帧后，在短帧间间隔(short interframe space，SIFS)后回一个ACK；当该指示位置1时，表示接收端收到BAR帧后不需要回ACK。
压缩点阵图：如果被设置1，则表示该BAR要求接收端回一个带压缩点阵图的BA。
TID/TID数目：如果多TID指示位没有被置1，则该字段承载该块确认会话的TID。如果多TID指示位被置1，则该字段承载多TID BAR帧中的TID数目。
起始序列控制字段：该字段用其中的12bits(B4～B15)来携带起始序列号(Starting sequence number,SSN)。
多TID：该指示位用于指示该BAR是基本BAR帧还是多TID BAR帧，对于多TIDBAR帧，其帧格式如图6所示。
对于多TID BAR帧，每个TID都有一个每TID信息和起始序列控制字段。每TID信息字段包含TID值，紧跟这个字段的是对应于该TID的序列控制字段。
3、BA帧
BA的帧格式如图7所示。其包括：帧控制，时长，接收地址，发送地址，BA控制，起始序列控制，帧校验序列等字段；其中，BA控制包括BA确认策略，多TID，压缩点阵图，组播重传模式，TID/TID数目和保留(B5～B11)等子字段，各主要子字段的含义如下：
BA确认策略:该指示位在延迟块确认时使用。对于一个延时块确认回话，如果该指示位置0，表示接收端收到BA帧后，在SIFS后回一个ACK；当指示位置1时，接收端收到BAR帧后不需要回ACK。
压缩点阵图：如果被设置1，则表示该BA帧包含一个压缩的或8个八位元的块确认点阵图。如果设置为0，则BA帧包含非压缩的或者128个八位元的块确认点阵图。
TID/TID数目：如果多TID指示位没有被置1，则该字段承载该块确认会话的TID。如果多TID指示位被置1，则该字段承载多TID BA帧中的TID数目。
起始序列控制字段：该字段用其中的12bits来携带起始序列号SSN。
块确认点阵图：块确认点阵图可以是非压缩BA情况下的128个八位元，也可以是在压缩BA情况下的8个八位元。点阵图最多可标示64个MSDU的接收状态。在非压缩点阵图的情况下，每个MSDU由一个16位bits来表示，各个bit代表MSDU分片(如果有的话)。在压缩点阵图的情况下每个MSDU使用单个bit来表示，这种情况下不支持对每个分片接收状态的表示。
多TID：该指示位用于指示该BA是基本BA帧还是多TID BA帧，对于多TID BA帧，其帧格式如图8所示。
对于多TID BA帧，每个TID都有一个每TID信息字段、起始序列控制字段、BA点阵图字段。每TID信息字段包含TID值，紧跟这个字段的是对应于该TID的序列控制字段和BA点阵图。
4、块确认会话的建立过程
对于某个TID数据，如果想使用块确认机制，是通过交换建立块确认(Add Block Acknowledgement，ADDBA)请求(request)/响应(response)帧来建立的。
具体的，块确认会话的初始化由发起端发送一个“ADDBA请求”帧开始。响应端发送一个ACK作为对正确收到的“ADDBA请求”帧的回应。在进一步的处理后，响应端发送一个“ADDBA响应”帧，如果发起端正确接收到此帧，则回应一个ACK。如果没有收到期望的ACK，则发起端与响应端将会重传“ADDBA请求”“ADDBA响应”。如果会话建立不成功，其会被发起端的无操作超时检测到。
其中，“ADDBA请求”与“ADDBA响应”帧携带以下主要信息：
块确认策略：该字段指示该会话是立即块确认还是延迟块确认会话。
TID：该字段给出了该会话所用的通信类别。
缓冲区大小：该字段指示响应端用来对帧进行重排序的帧缓冲区数目。如果这个值由发起端设置，则是期望值，响应端设置的值才是真实值。发起端在要求一个块确认之前，没有收到响应的MPDU数目不能超过此值。
块确认超时值：该字段给出了在此会话中没有帧交换时，块确认会话在多久后终止。
起始序列号：发起端发送的第一个数据帧的序列号。
5、记分板机制以及窗口起始序列号(WinStart)移动机制
对于块确认，接收端会维护一个记分板数据结构，以记录哪些MPDU已经被正确接收到。当接收端需要回BA时，会将记分板转换成一个点阵图(bitmap)，BA帧中会进一步指示bitmap中的第一个比特所对应的序列号，随后的比特则对应后续的序列号。目前协议中，MAC服务数据单元(MAC Service data unit,MSDU)的序列号是一个12bits，记分板表示一个大小为4096的序列号空间(Sequence Number Space)的一个窗口。记分板窗口由窗口起始序列号(WinStart)，窗口终止序列号(WinEnd)以及窗口长度(WinSize)定义。
多链路聚合通信涉及多个链路之间的协调工作。数据发送端(如图2所示第一多链路设备)的同一TID的MPDUs可以分别通过多条链路：链路1，链路2，链路3，链路n进行传输，以增大该TID数据的传输速率。数据接收端(例如第二多链路设备)根据每个MPDU帧 头携带的序列号(SN)对多条链路上接收的相同TID的数据包按照SN进行排序。协议要求MAC层必须按照顺序将MPDUs往上层递交。
但是，本申请的发明人发现，在多链路聚合下BAR的发送会存在如下问题：如果一条link在发送BAR时设置了一个SSN值，根据现有的WinStart移动规则，接收端会移动WinStart，但其他link有小于该SSN的待传MPDU，接下来即使这些MPDUs被发送且被正确接收也会被接收端丢弃。
举例来说，如图9所示：
发送端分别在链路1和链路2上发送A-MPDU1和A-MPDU2，其中A-MPDU1所包含的MPDUs对应的SN为1～31；A-MPDU2所包含的MPDUs对应的SN为32～59。接收端分别在链路1和链路2上反馈BA给发送端，并指示哪些MPDUs被成功接收哪些MPDUs未被成功接收。假设链路2上发送的BA未被发送端成功接收，其接下来在链路2上发送一个BAR帧请求接收端回BA，并将BAR帧中的SSN设置为32。接收端收到BAR帧后会将WinStart移动到32，但这会导致A-MPDU1中未被正确接收的MPDUs在接下来的重传过程中，即使被接收端成功接收也会因为其SN小于WinStart而被丢弃。
为了解决上述多链路聚合场景下的技术问题，存在如下三种现有技术：
现有技术一：针对多链路聚合场景下的每条链路，单独使用记分板机制。
具体的，如图10所示的多链路聚合架构中，接收端除了设置有一个全局重排缓冲区(Global Reorder Buffer)，每条链路还有一个本地记分板或者本地重排缓冲区(Local Reorder Buffer)。为了避免MPDUs在本地缓冲区等待过长时间，需要引入一个新的BAR帧，称为本地BAR(Local BAR，L-BAR)，其帧格式如图11所示：
与图5所示的BAR帧不同之处在于，将保留比特(reserved bit)B5用来指示是否携带本链路传输的MPDU的SN点阵图指示信息，其用于指示在本link上传输的MPDUs所对应的SN范围，并且第一个bit对应的SN用起始序列号字段进行指示。
接收端接收到该L-BAR帧之后，根据其携带的本链路传输的MPDU的SN点阵图指示信息来判断如何移动本链路对应的记分板窗口的起始序列号(WinStart)。
现有技术一提供的技术方案，需要修改现有的BAR帧，并为每条链路增加一个本链路传输的MPDU的SN点阵图指示信息，信令开销巨大。
现有技术二：约束发送端发送的MPDU的SN。
具体的，参见图12，与图5所示的BAR帧结构不同之处在于，图12的BAR帧结构中，利用保留比特(reserved bit)B5指示接收端是否需要根据该BAR帧来移动记分板窗口的起始序列号(WinStart)，该B5对应的字段可以称为“是否移动指示”。
当发送端想要接收端根据BAR帧来移动记分板窗口的起始序列号(WinStart)时，发送端必须保证其发送的MPDU的SN大于BAR帧中携带的SSN，也即，MPDU的SN小于BAR帧中携带的SSN将不能被发送。
现有技术二提供的技术方案，同样需要修改现有的BAR帧，并且需要发送端的多条链路之间能够互相交互，以判断什么情况下可以让接收端移动记分板窗口的起始序列号(WinStart)，需要让接收端移动WinStart时，将“是否移动指示”置为1。这无疑增加了发送端的复杂度；并且，在非共址(non-colocation)场景下，各条链路之间的交互，会增加延时。
现有技术三：约束发送端发送的MPDU的SSN。
现有技术三中，发送端在某条链路上发送BAR时，需要保证其他链路上没有比该BAR中携带的SSN更低的待传MPDU。
现有技术三的技术方案，同样需要发送端的聚合链路之间能够交互，这无疑增加了发送端的复杂度；并且，在non-colocation场景下，各条链路之间的交互，会增加延时。。
本申请针对上述技术问题，以及上述三种现有技术存在的缺陷，针对多链路聚合传输，提供了一种记分板窗口起始序列号(WinStart)的移动规则。
本申请提供的一种记分板窗口起始序列号(WinStart)的移动规则，作用于接收端，综合参考多条链路各自的SSN以决策是否移动WinStart。
应理解，本申请所说的多条链路对应的SSN，是指的多条链路各自的SSN，各条链路各自的SSN的值可以相同，也可以部分不同，也可以是各不相同；发送端可以对各条链路的SSN进行统一设置，也可以分别进行设置，本申请不做限定。
还应理解，本申请在接收端综合考虑多条链路各自的SSN，包括如下几种情况；
一是在接收到某条链路上发送的BAR之后，将该BAR中携带的SSN，和接收端本地维护或存储的其他链路的SSN进行综合考虑；
二是在某一个时间点，接收端对其本地维护或存储的多条链路的SSN进行综合考虑；
三是在接收到多条链路同时发送的多个BAR之后，将该多个BAR中携带的与多条链路分别对应的SSN进行综合考虑。
应理解，本申请实施例涉及的多条链路，是指的发送端和接收端之间的多条链路；接收端在综合考虑多条链路各自的SSN决策是否移动WinStart时，可以考虑该多条链路中的全部链路各自的SSN，也可以考虑该多条链路中的至少两条链路对应的SSN。
一种实现中，为了兼顾多条链路上发送的MPDU，在接收端接收到某条链路发送的BAR帧时，接收端对WinStart进行调整的时候，不仅只考虑该BAR帧携带的SSN，还需要跟其他链路发送的BAR携带的SSN进行比较，取其中最小的值，以便将WinStart的值调整为多条链路发送的BAR的对应的SSN的最小值，从而不会出现发送的MPDU的SN小于WinStart的情况。应理解，其他链路发送的BAR携带的SSN已经在接收端本地存储，因此不需要发送端多条链路之间进行交互。
另外，在接收端接收到某条链路发送的MPDU时，如果某条链路发送的数据帧对应的SN落在当前的记分板窗口外，但位于序列窗口空间范围的一半内，则调整WinStart，以便WinEnd等于该SN，如果本地存储的各链路对应的SSN中，有小于调整后的WinStart的SSN，则将本地存储的小于WinStart的SSN更新为WinStart。
发送端可以不改变现有BAR帧的SSN的设置规则，也不需要发送端多链路之间需要交互，接收端根据多条链路的接收情况来调整WinStart。该方法不需要更改现有的BAR帧，也不强制要求发送端多链路之间能够进行交互，这尤其适用于non-collocated多链路聚合场景。
举例来讲，本申请针对多链路聚合传输，提供的新的记分板窗口起始序列号(WinStart)的移动规则如下：
WinStart移动规则一
每条link的SSN都初始化为SSN_0,其携带在ADDBA Request/Response帧中；
当接收到一个BAR帧，则将WinStart移动到min(SSN_1,SSN_2,…,SSN_N)，其中SSN_i为聚合链路i上的SSN值；
当接收到一个QoS数据帧时，有以下3种情况：
如果数据帧的SN落在当前的记分板窗口内，即WinStart<＝SN<＝WinEnd，则记分板在SN表示的偏移量处置1；
如果数据帧的SN落在当前的记分板窗口外，但位于序列窗口空间范围的一半内，即WinEnd<SN<WinStart+2^11，则记分板右移以适应SN，即，将记分板窗口起始序列号设置为WinStart＝SN-WinSize+1。如果SSN_i小于WinStart，则更新SSN_i为WinStart，其中i＝1,…,N；
如果数据帧的SN超出窗口外一半序列空间以上，即WinStart+2^11<＝SN<＝WinStart，则不对记分板做任何改变。
另一种实现中，为了兼顾多条链路上发送的MPDU，在接收端接收到某条链路发送的BAR帧时，将该BAR帧携带的SSN值与其他链路对应的SSN的值中的最小值，记为WinStart_x；然后与接收该BAR帧前本地存储的WinStart_y进行比较，取两者中最大值作为当前的WinStart对记分板窗口进行调整；然后利用调整后的记分板窗口对各链路接收到的数据帧进行处理。
接收端可以自适应的调整WinStart，这样做的目的，是为了兼顾多条链路发送的MPDU，该方法不需要多条链路之间进行交互，同时也不需要更改现有的BAR帧，最大程度的节约信令开销并兼顾多条链路的传输。
举例来讲，本申请针对多链路聚合传输，提供的新的记分板窗口起始序列号(WinStart)的移动规则如下：
WinStart移动规则二：
每条link的SSN都初始化为SSN_0,其携带在ADDBA Request/Response帧中；
当接收端在某条链路(link i)上接收到一个BAR帧，将该BAR帧中携带的SSN_i和接收端本地存储的其他链路的SSN，取最小值，记为WinStart_x，即，将min(SSN_1,SSN_2,…,SSN_N)记为WinStart_x,收到BAR帧前的WinStart记为WinStart_y，则将WinStart移动到max(WinStart_x,WinStart_y)；
当接收端接收到一个QoS数据帧时，有以下3种情况：
如果数据帧的SN落在当前的记分板窗口内，即WinStart<＝SN<＝WinEnd，则记分板在SN表示的偏移量处置1；
如果数据帧的SN落在当前的记分板窗口外，但位于序列窗口空间范围的一半内，即WinEnd<SN<WinStart+2^11，则记分板右移以适应SN，且将记分板当前窗口起始序列号WinStart设置为WinStart＝SN-WinSize+1；
如果数据帧的SN超出窗口外一半序列空间以上，即WinStart+2^11<＝SN<＝WinStart，则不对记分板做任何改变。
基于上述发送端发送BAR的规则和接收端执行WinStart移动规则，本申请在图1所示的网络系统以及图2-图4所示的多链路设备的结构中，实现本申请提供的多链路聚合传输的方法如图13所示，包括：
步骤100，发送端在多条链路上向接收端发送数据帧(MPDUs)；其中，不同链路上发送 的数据帧，其对应的SSN可以相同，也可以不同；
步骤101，接收端在多条链路上接收所述数据帧；
步骤102，发送端在所述第一链路上发送块确认请求BAR帧；所述BAR帧中携带有与第一链路对应的起始序列号SSN_1；
一种可选的实现方式中，所述SSN_1为所述第一链路下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号；
步骤103，接收端在所述第一链路上接收块确认请求BAR帧；
步骤104，接收端根据多条链路各自的SSN，调整当前的记分板窗口起始序列号WinStart值；
步骤105，接收端根据调整后的WinStart，对所述多链路上接收的数据帧进行处理。
需要说明的是，以上流程仅为举例，各条链路发送数据帧和BAR帧的先后顺序本申请不做限制，接收端接收数据帧和BAR帧的时间顺序本申请也不做限制。
其中，发送端可以是如图1所示的AP，相应的，接收端为STA2；或者发送端为STA2，接收端为AP；或者发送端为STA4，接收端为STA5；或者发送端为STA5，接收端为STA4。或者发送端是如图2第一多链路设备，接收端为第二多链路设备；多条链路分别为链路1，链路2，链路3…链路n。
上述发送端执行的步骤100和步骤102，可以通过如图3A所示的多链路设备200的收发器205执行，或者通过如图3B所示的第一多链路通信装置中的发送模块302执行；还可以通过如图4所示的芯片系统中的接口302执行。
上述接收端执行的步骤101和103，可以通过如图3A所示的多链路设备200的收发器205执行，步骤104可以通过处理器201执行。上述接收端执行的步骤101和103，还可以通过如图3B所示的第二多链路通信装置的接收模块401执行，步骤104和步骤105可以通过处理模块402执行。步骤101和103还可以通过如图4所示的芯片系统中的接口302执行，步骤104和步骤105还可以通过处理器301执行。
其中，在接收端还存储各条链路对应的SSN和记分板窗口参数等，例如WinStart，WinSize，可选的还可以存储WinEnd，可以通过如图3A所示的存储器202，或图4所示的存储器303实现，具体的形式不限于表格等等。
实施例一
本实施例一将描述本申请实现如图13所示的链路聚合传输技术方案中，记分板窗口起始序列号(WinStart)的移动规则一。
如图14所示，以发送端通过两条聚合链路向接收端发送MPDUs为例进行说明。MPDUs的确认策略字段都设置为基于请求的块确认策略，并且不存在某个MPDU的SN落在WinEnd<SN<WinStart+2^11的情况。
在这种场景下，在接收端执行WinStart的移动过程如下：
在初始时刻t0，将SSN_1和SSN_2都初始化为SSN_0，其中SSN_0为发送端发送的ADDBA请求和接收端向发送端发送ADDBA响应帧中携带的起始序列号，SSN_1和SSN_2分别为聚合链路1和聚合链路2上收到的BAR帧中所携带的SSN值。接收端将WinStart设置为min(SSN_1,SSN_2)＝min(0,0)＝0。
在时刻t1，接收端在聚合链路1上收到一个BAR帧，其携带的SSN_1为20，然后接收 端将WinStart设置为min(SSN_1,SSN_2)＝min(20,0)＝0；
在时刻t2，接收端在聚合链路2上收到一个BAR帧，其携带的SSN_2为30，然后接收端将WinStart设置为min(SSN_1,SSN_2)＝min(20,30)＝20；
在时刻t3，接收端在聚合链路1上收到一个BAR帧，其携带的SSN_1为25，然后接收端将WinStart设置为min(SSN_1,SSN_2)＝min(25,30)＝25；
在时刻t4，接收端在聚合链路1上收到一个BAR帧，其携带的SSN_1为28，然后接收端将WinStart设置为min(SSN_1,SSN_2)＝min(28,30)＝28；
在时刻t5，接收端在聚合链路2上收到一个BAR帧，其携带的SSN_2为40，然后接收端将WinStart设置为min(SSN_1,SSN_2)＝min(28,40)＝28；
在时刻t6，接收端在聚合链路1上收到一个BAR帧，其携带的SSN_1为45，然后接收端将WinStart设置为min(SSN_1,SSN_2)＝min(45,40)＝40；
以此类推。
本实施例一为了兼顾多条链路上发送的MPDU，在接收端接收到某条链路发送的BAR帧时，接收端对WinStart进行调整的时候，不仅只考虑该BAR帧携带的SSN，还需要跟其他链路发送的BAR携带的SSN进行比较，取其中最小的值，以便将WinStart的值调整为多条链路发送的BAR的对应的SSN的最小值，从而不会出现发送的MPDU的序列号小于WinStart而导致接收端即使正确接收也会被丢弃的情况出现。
实施例二
实施例二中，将描述本申请实现如图13所示的链路聚合传输技术方案中，记分板窗口起始序列号(WinStart)的移动规则一，以及在该WinStart移动规则一基础上，对多条链路上发送的MPDU的处理方式。
如图15所示，仍然以发送端的多链路设备通过两条链路Link1和Link2向接收端发送MPDUs，且记分板窗口为WinStart＝4，WinSize＝100，WinEnd＝103为例。
首先ADDBA请求/响应帧中SSN设置为4，SSN_1和SSN_2都初始化为4，假设link1和link2上都只采用块确认策略且之前发送端没有发送过BAR帧，而且没有发送过SN大于103的MPDU(图中示意为Data)。
T0时刻，发送端在Link1上向接收端发送的MPDU，其SN为103，满足WinStart<SN＝WinEnd＝103，因此在序列号空间(Sequence Number Space)中，在该SN对应的偏移量(即序列号为103)处，将对应的比特置1，表示SN＝103对应的MPDU被成功接收。
T1时刻，发送端在Link2上发送BAR帧，其中携带的SSN＝6；接收端将WinStart调整为两条链路对应的SSN的最小值，即WinStart＝min(SSN_1,SSN_2)＝min(4,6)＝4。将SSN_1＝4，SSN_2＝6,WinStart＝4，WinEnd＝103存储在接收端本地。
T2时刻，发送端在Link1上重传SN＝4的MPDU，满足WinStart＝SN<WinEnd，因此，在该SN对应的偏移量(即序列号为4)处，将对应的比特置1，表示SN＝4对应的MPDU被成功接收。将SSN_1＝4，SSN_2＝6,WinStart＝4，WinEnd＝103存储在接收端本地。
相比较而言，相同场景下，如果利用现有技术提供的记分板的起始序列号(WinStart)的移动规则，如图16所示，在T1时刻，发送端在Link2上发送BAR帧，其中携带的SSN＝6；接收端将WinStart调整为该BAR对应的SSN，即WinStart＝SSN_2＝6。
在T2时刻，发送端在Link1上发送SN＝4的MPDU，由于SN＝4<WinStart,即使该SN对应的MPDU被接收端成功接收，也会被接收端丢弃或者删除。
比较图15本申请提供的多链路传输方案和图16现有技术提供的多链路传输方案可知，利用本申请实施例提供的记分板窗口起始序列号(WinStart)的移动规则一，SN＝4对应的MPDU被接收端成功接收但不会被丢弃或者删除，并且该记分板窗口起始序列号(WinStart)的移动规则，并不要求发送端在发送BAR帧时需要确保其他链路上没有待传的MPDU的序列号小于该BAR帧中的SSN，更不需要修改现有的BAR帧，因此，在保持原有的BAR帧的结构上，极大程度节约了指示开销，并实现对多条链路的MPDU的正确接收。
图15仅为举例，应用本申请提供的记分板窗口起始序列号(WinStart)的移动规则，还可以解决诸如图9所示的问题，例如，发送端在Link2上发送的BAR携带的SSN_2＝32时，在Link1上发送的A-MPDU1中的SN为1～31的MPDUs，假设对应的SSN_1＝1,此时在接收端，将WinStart调整为两者中的最小值，即WinStart＝mini(SSN_1,SSN_2)＝mini(1，32)＝1,因此接下来在Link1上重传A-MPDU1中出错的MPDU时不会被接收端丢弃或删除。
实施本实施例二，接收端在接收到的BAR帧时，会根据该BAR帧携带的SSN和本地维护或存储的各链路的SSN中的最小值，对WinStart进行调整；从而避免对其他链路上待发送的MPDU(该MPDU的SN小于BAR帧携带的SSN)进行误操作。
实施例三
本实施例三将举例描述应用本申请提供的记分板窗口起始序列号(WinStart)的移动规则一的多链路传输技术方案。
如图17所示，假设记分板尺寸WinSize＝100,ADDBA请求/响应帧中SSN设置为0，接收端本地存储的SSN_1和SSN_2都初始化为0，假设链路1和链路2上都只采用块确认策略且之前发送端没有发送过BAR帧，而且没有发送过SN大于99的数据帧。
T0时刻，发送端在链路1上发送了一个SN＝103的数据帧，由于其落在了记分板窗口之外但位于序列号空间范围内的一半，所以接收端会将WinStart移动到4。由于SSN_1＝0,SSN_2＝0,SSN_1<WinStart,SSN_2<WinStart，则在接收端本地，更新SSN_1和SSN_2为WinStart，即SSN_1＝4,SSN_2＝4。
T1时刻，发送端在链路2上发送了一个SSN＝6的BAR帧，则接收端本地将SSN_2更新为SSN_2＝6,并将WinStart移动到min(SSN_1,SSN_2)＝min(4,6)＝4。
T2时刻，发送端在链路2上发送了一个SN＝98的数据帧，由于其落在了记分板窗口之内，接收端在序列号空间中，将其对应的偏移量(98)置为1，表示正确接收且不被删除或丢弃，接收端不移动WinStart。
T3时刻，发送端在链路1上发送了一个SSN＝10的BAR帧，接收端在本地将SSN_1更新为SSN_1＝10,并将WinStart移动到min(SSN_1,SSN_2)＝min(10,6)＝6。
T4时刻，发送端在链路1上发送了一个SN＝107的数据帧，由于其落在了记分板窗口之外但位于序列号空间范围内的一半，所以接收端会将WinStart移动到WinEnd-WinSize+1＝107-100+1＝8，以便能正确接收SN＝107的数据帧，并将其在序列号空间中对应的偏移量置为1。由于SSN_1＝10,SSN_2＝6,SSN_1>WinStart,SSN_2<WinStart，则接收端在本地，将SSN_2更新为WinStart，即SSN_2＝WinStart＝8；SSN_1＝10保持不变。
应理解，将SN＝107对应的偏移量置1和调整WinStart的操作，不分时间先后顺序。
实施本实施例三，接收端在接收到的BAR帧时，会根据该BAR帧携带的SSN和本地维护或存储的各链路SSN中的最小值，对WinStart进行调整；接收到某条链路发送的数据帧时，也可以根据数据帧对应的SN，对WinStart进行调整，并且适应性的调整本地存储的SSN的值。实施本实施例三，可以保证多条链路发送的数据帧都被正确接收并不会被误删除，提升了数据传输的效率。
实施例四
实施例四中，将描述本申请实现如图13所示的链路聚合传输技术方案中，记分板窗口起始序列号(WinStart)的移动规则二，以及在该WinStart移动规则二基础上，对多条链路上发送的MPDU的处理方式。
详见图18，仍然以发送端的多链路设备通过两条链路Link1和Link2向接收端发送MPDUs，且记分板窗口为WinStart＝4，WinSize＝100，WinEnd＝103为例。
首先ADDBA请求/响应帧中SSN设置为0，SSN_1和SSN_2都初始化为0，假设link1和link2上都只采用块确认策略且之前发送端没有发送过BAR帧，而且没有发送过SN大于99的MPDU(图18中示意为Data)。
T0时刻，发送端在Link1上向接收端发送的MPDU，其SN为103，满足数据帧的SN落在当前的记分板窗口外，但位于序列窗口空间范围的一半内，即WinEnd<SN<WinStart+2^11，则记分板右移以适应SN，且将记分板当前窗口起始序列号设置为WinStart＝SN-WinSize+1＝103-100+1＝4，同时在序列号空间(Sequence Number Space)中，在该SN对应的偏移量(即序列号为103)处，将对应的比特置1，表示SN＝103对应的MPDU被成功接收。
与实施例二应用移动规则一不同，本实施例四中，应用移动规则二，此时，接收端本地存储的SSN_1和SSN_2不进行更新，仍然为SSN_1＝0，SSN_2＝0。
T1时刻，发送端在Link2上发送BAR帧，其中携带的SSN＝6；接收端记两条链路对应的SSN的最小值为WinStart_x，即WinStart_x＝min(SSN_1,SSN_2)＝min(0,6)＝0。接收端将接收BAR帧前的WinStart_y(即T0时刻的WinStart)与WinStart_x比较，取其中最大值作为当前的WinStart，即WinStart＝max{WinStart_x，WinStart_y}＝max{0,4}＝4；
接收端将SSN_1＝0，SSN_2＝6,WinStart＝4存储在本地。
T2时刻，发送端在Link1上发送SN＝4的MPDU，满足WinStart＝SN<WinEnd，因此，在该SN对应的偏移量(即序列号为4)处，将对应的比特置1，表示SN＝4对应的MPDU被成功接收。
此时，接收端本地存储的仍然是SSN_1＝0，SSN_2＝6,WinStart＝4。
T3时刻，发送端在Link1上发送BAR，其中携带的SSN＝10；接收端记两条链路对应的SSN的最小值为WinStart_x，即WinStart_x＝min(SSN_1,SSN_2)＝min(10,6)＝6。接收端将接收BAR帧前的WinStart_y(即T2时刻的WinStart)与WinStart_x比较，取其中最大值作为当前的WinStart，即WinStart＝max{WinStart_x，WinStart_y}＝max{6,4}＝6；
接收端将SSN_1＝10，SSN_2＝6,WinStart＝6存储在本地。
T4时刻，发送端在Link 2上发送SN＝107的MPDU，其满足SN落在当前的记分板窗口外，但位于序列窗口空间范围的一半内，即WinEnd<SN<WinStart+2^11，记分板右移以适应SN，且将记分板当前窗口起始序列号设置为WinStart＝SN-WinSize+1＝107-100+1＝8；此时，SN＝107落在调整后的记分板窗口中，将其对应的比特置1。
接收端将SSN_1＝10，SSN_2＝6,WinStart＝8存储在本地。
相比较而言，相同场景下，如果利用现有技术提供的记分板的起始序列号(WinStart)的移动规则，如图16所示，在T1时刻，发送端在Link2上发送BAR帧，其中携带的SSN＝6；接收端将WinStart调整为该BAR对应的SSN，即WinStart＝SSN_2＝6。
在T2时刻，发送端在Link1上发送SN＝4的MPDU，由于SN＝4<WinStart,因此，该SN对应的MPDU即便是被接收端成功接收，也会被接收端丢弃或者删除。
在T3时刻，发送端在Link1上发送BAR，其中携带的SSN＝10；接收端将WinStart调整为调整为该BAR对应的SSN，即WinStart＝SSN_1＝10，对应的，WinEnd＝109。
在T4时刻，发送端在Link 2上发送SN＝107的MPDU，其满足SN落在当前的记分板窗口内，即WinStart<SN<WinEnd，将其对应的比特置1。
比较图18本申请提供的多链路传输方案和图16现有技术提供的多链路传输方案可知，利用本申请实施例提供的记分板窗口起始序列号(WinStart)的移动规则，SN＝4对应的MPDU被接收端成功接收但不会被丢弃或者删除，并且该记分板窗口起始序列号(WinStart)的移动规则，并不要求发送端在发送BAR帧时需要确保其他链路上没有待传的MPDU的序列号小于该BAR帧中的SSN，更不需要修改现有的BAR帧，因此，在保持原有的BAR帧的结构上，极大程度节约了指示开销，并实现对多条链路的MPDU的正确接收。
图18仅为举例，应用本申请提供的记分板窗口起始序列号(WinStart)的移动规则二，还可以解决诸如图9所示的问题，例如，发送端在Link2上发送的BAR携带的SSN_2＝32时，在Link1上发送的A-MPDU1中的SN为1～31的MPDUs，假设对应的SSN_1＝1,此时在接收端，将WinStart调整为两者中的最小值，即WinStart＝mini(SSN_1,SSN_2)＝mini(1，32)＝1,因此接下来在Link1上重传A-MPDU1中出错的MPDU时不会被接收端丢弃或删除。
实施本实施例四，接收端在接收到的BAR帧时，会根据该BAR帧携带的SSN和本地维护或存储的SSN中的最小值，以及接收BAR帧之前的WinStart，对WinStart进行调整；接收到某条链路发送的数据帧时，也可以根据数据帧对应的SN，对WinStart进行调整；从而避免对其他链路上待发送的MPDU(该MPDU的SSN小于BAR帧携带的SSN)进行误操作。
实施例五
本实施例五将举例描述应用本申请提供的记分板窗口起始序列号(WinStart)的移动规则二的多链路传输技术方案。
首先ADDBA请求/响应帧中SSN设置为0，SSN_1和SSN_2都初始化为0，假设link1和link2上都只采用块确认策略且之前发送端没有发送过BAR帧，而且没有发送过SN大于99的MPDU(图19中示意为Data)。
T0时刻，发送端在Link1上向接收端发送的MPDU，其SN为103，满足数据帧的SN落在当前的记分板窗口外，但位于序列窗口空间范围的一半内，即WinEnd<SN<WinStart+2^11，则记分板右移以适应SN，且将记分板当前窗口起始序列号设置为WinStart＝SN-WinSize+1＝103-100+1＝4，同时在序列号空间(Sequence Number Space)中，在该SN对应的偏移量(即序列号为103)处，将对应的比特置1，表示SN＝103对应的MPDU被成功接收。
与实施例三应用移动规则一不同，本实施例五中，应用移动规则二，此时，接收端本地存储的SSN_1和SSN_2不进行更新，仍然为SSN_1＝0，SSN_2＝0。
T1时刻，发送端在Link2上发送BAR帧，其中携带的SSN＝6；接收端记两条链路对应 的SSN的最小值为WinStart_x，即WinStart_x＝min(SSN_1,SSN_2)＝min(0,6)＝0。接收端将接收BAR帧前的WinStart_y(即T0时刻的WinStart)与WinStart_x比较，取其中最大值作为当前的WinStart，即WinStart＝max{WinStart_x，WinStart_y}＝max{0,4}＝4；
接收端将SSN_1＝0，SSN_2＝6,WinStart＝4存储在本地。
T2时刻，发送端在Link1上发送SN＝98的MPDU，满足WinStart＝SN<WinEnd，因此，在该SN对应的偏移量(即序列号为98)处，将对应的比特置1，表示SN＝98对应的MPDU被成功接收。
此时，接收端本地存储的仍然是SSN_1＝0，SSN_2＝6,WinStart＝4。
T3时刻，发送端在Link1上发送BAR，其中携带的SSN＝10；接收端记两条链路对应的SSN的最小值为WinStart_x，即WinStart_x＝min(SSN_1,SSN_2)＝min(10,6)＝6。接收端将接收BAR帧前的WinStart_y(即T2时刻的WinStart)与WinStart_x比较，取其中最大值作为当前的WinStart，即WinStart＝max{WinStart_x，WinStart_y}＝max{6,4}＝6；
接收端将SSN_1＝10，SSN_2＝6,WinStart＝6存储在本地。
T4时刻，发送端在Link 2上发送SN＝107的MPDU，其满足SN落在当前的记分板窗口外，但位于序列窗口空间范围的一半内，即WinEnd<SN<WinStart+2^11，记分板右移以适应SN，且将记分板当前窗口起始序列号设置为WinStart＝SN-WinSize+1＝107-100+1＝8；此时，SN＝107落在调整后的记分板窗口中，将其对应的比特置1。
接收端将SSN_1＝10，SSN_2＝6,WinStart＝8存储在本地。
实施本实施例五，接收端在接收到的BAR帧时，会根据该BAR帧携带的SSN和本地维护或存储的SSN中的最小值，以及接收BAR帧之前的WinStart，对WinStart进行调整；接收到某条链路发送的数据帧时，也可以根据数据帧对应的SN，对WinStart进行调整。实施本实施例五，可以保证多条链路发送的数据帧都被正确接收并不会被误删除，提升了数据传输的效率。
应理解，上述如图13所示的方法实施例，以及实施例一～实施例五，在多链路聚合下，接收端可能同时收到多个帧，可以是数据帧(MPDU)，也可以是BAR帧，还可以同时包括数据帧和BAR帧，这时候接收端可以按照任意顺序一个一个处理。
综上所述，上述如图13所示的方法实施例，以及实施例一～实施例五，均不需要在BAR帧中针对每条链路增加一个本链路传输的MPDU的SN点阵图指示信息，节约了信令开销；与现有技术二和现有技术三相比，不需要对发送端发送的BAR帧中的SSN设置进行限制，不需要发送端多链路之间进行交互。
可选的，在上述实施例的基础上，本申请实施例还提出一种BAR发送规则，不要求多链路之间进行交互，也不对现有的BAR帧进行修改，而是在发送端在某条链路上发送BAR时，将其携带的SSN设置为该链路上即将发送的MAC协议数据单元(MAC Protocol data unit，MPDU)的序列号，或者大于该链路发送的MPDU但被发送端删除或丢弃的MPDU的序列号。
简言之，本申请实施例针对发送端发送BAR规则如下：
每条聚合链路上发送的BAR中携带的SSN可以设置为该link上下一个要被发送的MPDU的序列号或者一个大于被丢弃MPDU的序列号的一个值。
如此，通过发送BAR来冲刷重排缓冲区，将超时重传的MSDU所代表的空洞给冲刷掉， 这样后继的完整MSDU才不至于被无谓地挂起来以等待序列变得完整。在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘solid state disk(SSD))等。
以上所述的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明。凡在本申请的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本申请的保护范围之内。

Claims (25)

  1. 一种多链路聚合传输方法，应用于多链路聚合传输的接收端，其特征在于，包括：
    接收端在与发送端之间的多条链路上接收数据帧和BAR帧中的至少一种；所述多条链路包括第一链路；
    所述接收端在所述第一链路上接收块确认请求BAR帧，所述BAR帧中携带所述第一链路对应的SSN_1；
    所述接收端根据所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值；
    所述接收端根据调整后的WinStart，对所述多链路上接收的数据帧进行处理。
  2. 如权利要求1所述的方法，其特征在于，所述接收端根据所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值，包括：
    接收端调整所述WinStart为SSN最小值；其中，SSN最小值为所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN中最小的SSN。
  3. 如权利要求2所述的方法，其特征在于，所述根据调整后的WinStart，对所述多链路上接收的数据帧进行处理，包括：
    接收到某链路发送的数据帧，所述数据帧的序列号SN满足WinEnd<SN<WinStart+2^11，调整所述WinStart为WinStart＝SN-WinSize+1；
    将所述多条链路对应的SSN中，小于调整后的WinStart的SSN，更新为与所述调整后的WinStart相同。
  4. 如权利要求1所述的方法，其特征在于，所述接收端根据各链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值，包括：
    接收端调整所述WinStart为WinStart最大值；
    其中，WinStart最大值为接收所述BAR之前的WinStart与接收所述BAR后的WinStart中最大的WinStart；其中，接收所述BAR后的WinStart为SSN最小值；所述SSN最小值为所述第一链路对应的SSN_1的SSN_1和所述接收端本地存储的其他链路对应的SSN中最小的SSN。
  5. 如权利要求4所述的方法，其特征在于，所述根据调整后的WinStart，对所述多链路上接收的数据帧进行处理，包括：
    接收到某条链路发送的数据帧，所述数据帧的序列号SN满足WinEnd<SN<WinStart+2^11，调整所述WinStart为WinStart＝SN-WinSize+1。
  6. 如权利要求3或5所述的方法，其特征在于，所述SSN_1为所述第一链路下一个上被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号。
  7. 一种多链路设备，其作为多链路聚合传输的接收端，其特征在于，包括：
    收发器，用于在与发送端之间的多条链路上接收数据帧和BAR帧中的至少一种；所述多条链路包括第一链路；
    所述收发器，用于在所述第一链路上接收块确认请求BAR帧，所述BAR帧中携带所述第一链路对应的SSN_1；
    处理器，用于根据所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN，调整当前的记分板窗口起始序列号WinStart；
    所述处理器，还用于根据调整后的WinStart，对所述多链路上接收的数据帧进行处理。
  8. 如权利要求7所述的设备，其特征在于，所述接收端根据所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值，包括：
    接收端调整所述WinStart为SSN最小值；其中，SSN最小值为所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN中最小的SSN。
  9. 如权利要求8所述的设备，其特征在于，所述根据调整后的WinStart，对所述多链路上接收的数据帧进行处理，包括：
    接收到某链路发送的数据帧，所述数据帧的序列号SN满足WinEnd<SN<WinStart+2^11，调整所述WinStart为WinStart＝SN-WinSize+1；
    将所述多条链路对应的SSN中，小于调整后的WinStart的SSN，更新为与所述调整后的WinStart相同。
  10. 如权利要求7所述的设备，其特征在于，所述接收端根据各链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值，包括：
    接收端调整所述WinStart为WinStart最大值；
    其中，WinStart最大值为接收所述BAR之前的WinStart与接收所述BAR后的WinStart中最大的WinStart；其中，接收所述BAR后的WinStart为SSN最小值；所述SSN最小值为所述第一链路对应的SSN_1的SSN_1和所述接收端本地存储的其他链路对应的SSN中最小的SSN。
  11. 如权利要求10所述的设备，其特征在于，所述根据调整后的WinStart，对所述多链路上接收的数据帧进行处理，包括：
    接收到某条链路发送的数据帧，所述数据帧的序列号SN满足WinEnd<SN<WinStart+2^11，调整所述WinStart为WinStart＝SN-WinSize+1。
  12. 如权利要求9或11所述的设备，其特征在于，所述SSN_1为所述第一链路下一个上被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号。
  13. 一种多链路聚合传输方法，应用于多链路聚合传输的发送端，其特征在于，包括：
    发送端在与接收端之间的多条链路上发送数据帧；所述多条链路包括第一链路；
    所述发送端在所述第一链路上发送块确认请求BAR帧；所述BAR帧中携带有与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路上下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号。
  14. 一种多链路设备，其作为多链路聚合传输的发送端，其特征在于，包括：
    收发器，用于在与接收端之间的多条链路上发送数据帧；所述多条链路包括第一链路；
    所述收发器，还用于在所述第一链路上发送块确认请求BAR帧；
    所述处理器，用于解析所述BAR帧中携带的与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路上下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被所述发送端被丢弃的数据帧的序列号。
  15. 一种芯片系统，其特征在于，包括：至少一个处理器和接口；
    所述接口，用于输入在与发送端之间的多条链路上接收到的数据帧和BAR帧中的至少一种；所述多条链路包括第一链路；
    所述接口，用于输入在所述第一链路上接收到的块确认请求BAR帧，所述BAR帧中携带所述第一链路对应的SSN_1；
    处理器，用于根据所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN，调整当前的记分板窗口起始序列号WinStart；
    所述处理器，还用于根据调整后的WinStart，对所述多链路上接收的数据帧进行处理。
  16. 如权利要求15所述的芯片系统，其特征在于，所述芯片系统还包括存储器，用于存储其他链路对应的SSN中最小的SSN；
    所述处理器根据所述第一链路对应的SSN_1以及所述接收端本地存储的其他链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值，包括：
    所述处理器调整所述WinStart为SSN最小值；其中，SSN最小值为所述第一链路对应的SSN_1以及所述存储器中存储的其他链路对应的SSN中最小的SSN。
  17. 如权利要求16所述的芯片系统，其特征在于，所述处理器根据调整后的WinStart，对所述多链路上接收的数据帧进行处理，包括：
    在所述接入输入接收到的某链路发送的数据帧，所述数据帧的序列号SN满足WinEnd<SN<WinStart+2^11，所述处理器调整所述WinStart为WinStart＝SN-WinSize+1；
    所述处理器，还用于将所述多条链路对应的SSN中，小于调整后的WinStart的SSN，更新为与所述调整后的WinStart相同。
  18. 如权利要求17所述的芯片系统，其特征在于，所述处理器根据各链路对应的SSN，调整当前的记分板窗口起始序列号WinStart值，包括：
    所述处理器调整所述WinStart为WinStart最大值；
    其中，WinStart最大值为接收所述BAR之前的WinStart与接收所述BAR后的WinStart 中最大的WinStart；其中，接收所述BAR后的WinStart为SSN最小值；所述SSN最小值为所述第一链路对应的SSN_1的SSN_1和所述存储器中存储的其他链路对应的SSN中最小的SSN。
  19. 如权利要求18所述的芯片系统，其特征在于，所述处理器根据调整后的WinStart，对所述多链路上接收的数据帧进行处理，包括：
    所述接口输入接收到的某条链路发送的数据帧，所述数据帧的序列号SN满足WinEnd<SN<WinStart+2^11，所述处理器调整所述WinStart为WinStart＝SN-WinSize+1。
  20. 如权利要求17或18所述的芯片系统，其特征在于，所述SSN_1为所述第一链路下一个上被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被发送端丢弃的数据帧的序列号。
  21. 一种芯片系统，其特征在于，包括至少一个处理器和接口；
    所述接口，用于输出在与接收端之间的多条链路上发送的数据帧；所述多条链路包括第一链路；
    所述接口，还用于输出在所述第一链路上发送的块确认请求BAR帧；
    所述处理器，用于在所述BAR帧中携带与第一链路对应的起始序列号SSN_1；其中所述SSN_1为所述第一链路上下一个被发送的数据帧的序列号，或者所述SSN_1大于所述第一链路上被丢弃的数据帧的序列号。
  22. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质用于存储指令，当所述指令被执行时，使得如权利要求1～6,13中任一项所述的方法被实现。
  23. 一种计算机程序产品，其特征在于，所述计算机程序产品用于存储指令，当所述指令被执行时，使得如权利要求1～6,13中任一项所述的方法被实现。
  24. 一种程序，其特征在于，所述程序在计算机上运行时，使得如权利要求1～6,13中任一项所述的方法被实现。
  25. 一种装置，其特征在于，所述装置用于实现如权利要求1～6,13中任一项所述的方法。
PCT/CN2021/080316 2020-04-29 2021-03-11 一种多链路通信方法及相关装置 WO2021218435A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/971,843 US20230040554A1 (en) 2020-04-29 2022-10-24 Multi-link communication method and related apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010355213.1A CN113573359B (zh) 2020-04-29 2020-04-29 一种多链路通信方法及相关装置
CN202010355213.1 2020-04-29

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/971,843 Continuation US20230040554A1 (en) 2020-04-29 2022-10-24 Multi-link communication method and related apparatus

Publications (1)

Publication Number Publication Date
WO2021218435A1 true WO2021218435A1 (zh) 2021-11-04

Family

ID=78158401

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/080316 WO2021218435A1 (zh) 2020-04-29 2021-03-11 一种多链路通信方法及相关装置

Country Status (3)

Country Link
US (1) US20230040554A1 (zh)
CN (1) CN113573359B (zh)
WO (1) WO2021218435A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023151250A1 (zh) * 2022-02-11 2023-08-17 华为技术有限公司 多链路通信方法及装置

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116095611A (zh) * 2021-10-30 2023-05-09 华为技术有限公司 组播业务的数据传输方法、通信装置及存储介质
CN114501543A (zh) * 2022-01-10 2022-05-13 华为技术有限公司 多链路通信的方法和多链路设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180205502A1 (en) * 2017-01-19 2018-07-19 Qualcomm Incorporated Multi-link block acknowledgement management
US20190150214A1 (en) * 2017-01-19 2019-05-16 Qualcomm Incorporated Packet based link aggregation architectures
WO2019191108A1 (en) * 2018-03-30 2019-10-03 Intel Corporation Multi-access management services packet recovery mechanisms
US20200021400A1 (en) * 2018-07-11 2020-01-16 Qualcomm Incorporated Enhanced reliability techniques for shared spectrum
US20200037288A1 (en) * 2018-08-10 2020-01-30 Po-Kai Huang Block acknowledgement and fragmentation in multi-link communication between multi-link logical entities

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101933271B (zh) * 2008-03-17 2013-08-14 美国博通公司 用于具有受保护mac序列号的安全块应答的方法和系统
US20160080115A1 (en) * 2014-09-12 2016-03-17 Samsung Electronics Co., Ltd. Methods for efficient acknowledgement in wireless systems
WO2016126055A1 (ko) * 2015-02-03 2016-08-11 엘지전자 주식회사 무선랜 시스템에서 정책 지시자 기반 확인응답 신호 송수신 방법 및 이를 위한 장치
US10123330B2 (en) * 2015-07-01 2018-11-06 Samsung Electronics Co., Ltd. Methods to enable efficient wideband operations in local area networks using OFDMA

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180205502A1 (en) * 2017-01-19 2018-07-19 Qualcomm Incorporated Multi-link block acknowledgement management
US20190150214A1 (en) * 2017-01-19 2019-05-16 Qualcomm Incorporated Packet based link aggregation architectures
CN110199549A (zh) * 2017-01-19 2019-09-03 高通股份有限公司 基于分组的链路聚合架构
WO2019191108A1 (en) * 2018-03-30 2019-10-03 Intel Corporation Multi-access management services packet recovery mechanisms
US20200021400A1 (en) * 2018-07-11 2020-01-16 Qualcomm Incorporated Enhanced reliability techniques for shared spectrum
US20200037288A1 (en) * 2018-08-10 2020-01-30 Po-Kai Huang Block acknowledgement and fragmentation in multi-link communication between multi-link logical entities

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023151250A1 (zh) * 2022-02-11 2023-08-17 华为技术有限公司 多链路通信方法及装置

Also Published As

Publication number Publication date
US20230040554A1 (en) 2023-02-09
CN113573359A (zh) 2021-10-29
CN113573359B (zh) 2024-05-03

Similar Documents

Publication Publication Date Title
EP3968731A1 (en) Communication method applicable to multiple links, and related devices
WO2021218435A1 (zh) 一种多链路通信方法及相关装置
TWI452883B (zh) Ｗｌａｎ服務中提供可靠多播服務方法及系統
US11424862B2 (en) Data retransmission method and device, data response method and device, and storage medium
US8578230B2 (en) Enhanced block acknowledgement
US8832515B2 (en) Block acknowledgement mechanism including sequence number acknowledgement and retry bit
US8488523B2 (en) Method of transmitting and processing data block of specific protocol layer in wireless communication system
WO2021185211A1 (zh) 数据传输的方法和装置
US7424661B2 (en) Packet transmission system in wireless LAN
US11750329B2 (en) Apparatus and method for block acknowledgement management in multi-link communication systems
CN113169821A (zh) 用于多频带业务流的通信设备和通信方法
JP2008510351A (ja) 共通無線チャネルによって接続された複数の局を含むネットワークにおいてデータパケットに対して確認応答する方法
WO2021139681A1 (zh) 一种数据帧的接收状态确定方法及通信装置
WO2020233190A1 (zh) 多链路系统的mpdu发送、接收方法及装置、存储介质、发送端、接收端
US8755403B2 (en) Block acknowledgement for wireless communication methods, apparatuses and systems
WO2022094974A1 (zh) 数据传输方法、装置、计算机设备及存储介质
WO2023151250A1 (zh) 多链路通信方法及装置
WO2023130713A1 (zh) 多链路通信的方法和多链路设备
WO2023019581A1 (zh) 记分板状态更新方法、装置、设备及存储介质
WO2024007327A1 (en) Method of resource efficiency improvement
CN117356161A (zh) Bar帧的传输方法、装置、设备及存储介质

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21797023

Country of ref document: EP

Kind code of ref document: A1