Receiver multilink device and receiving method thereof
By introducing multi-link devices and methods in IEEE 802.11 communication devices, establishing block Ack protocol and common sending buffer control for public service identifier mapping, the problems of data throughput and service quality in multi-link transmission are solved, and the problem of Efficient multi-link block acknowledgement and data transmission.
Patent Information
- Application Number
- CN202410916212.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2019-12-20
- Filing Date
- 2020-10-30
- Publication Date
- 2024-11-08
AI Technical Summary
The existing IEEE 802.11 communication equipment is difficult to achieve seamless high-definition movie streaming in multi-link transmission, and the multi-link block confirmation mechanism is complex, affecting data throughput and service quality.
A multi-link device and method are proposed to establish a multi-link block Ack protocol with a public service identifier (TID) mapping between the initiator and the receiver, maintain a single common sending buffer control, and realize the control of multiple links. Data transmission and block acknowledgement on the data, using instant block Ack and BlockAck request frames to ensure the data reception status, and prevent the reception reordering buffer from overflowing.
Improves the throughput and reliability of multi-link transmission, simplifies the block confirmation process, avoids receiving reorder buffer overflow, and enhances support for high-resolution video streams.
Smart Images

Figure CN118921150A_ABST
Abstract
Description
[0001] This application is a divisional application of an invention patent application with an application date of October 30, 2020, application number 202080084364.6, and invention name “Communication device and communication method for multi-link block confirmation”. Technical Field
[0002] The present embodiments generally relate to communication devices, and more particularly, to methods and devices for multi-link block acknowledgement involving multi-link traffic flows. Background Art
[0003] In today's world, communication devices are expected to operate wirelessly with the same capabilities as wired computing devices. For example, a user expects to be able to seamlessly watch a high-definition movie streamed to the user's wireless communication device. This presents challenges for the communication devices and the access points to which the communication devices wirelessly connect.
[0004] The Institute of Electrical and Electronics Engineers (IEEE) 802.11 group recently established an Extremely High Throughput (EHT) study group to address these challenges. Multi-link operation in the 2.4 GHz, 5 GHz, and 6 GHz bands has been identified as a key candidate technology for such communications. Multi-channel aggregation on multiple links is a natural way to achieve an exponential increase in communication data throughput. In current IEEE 802.11 devices, when an access point (AP) enforces admission control on an access category (AC) (e.g., via (multiple) admission control enforcement (ACM) subfields in an enhanced distributed channel access (EDCA) parameter set element), a communication device (STA) needs to establish a service flow (TS) for the AC with the AP (via an Add Service Flow (ADDTS) request / response exchange). It is also necessary to perform a block acknowledgment protocol for the corresponding TID (via an Add Block Acknowledgement (ADDBA) request / response exchange). Summary of the invention
[0005] One non-limiting and exemplary embodiment facilitates providing a receiving multi-link device (MLD) comprising: circuitry to establish a multi-link Block Ack protocol with an initiator MLD mapped to a common traffic identifier (TID) of multiple links; a receiver to receive multiple MAC layer protocol data units (MPDUs) with a common TID on one or more of the multiple links from the initiator MLD, wherein a single common transmit buffer control is maintained at the initiator MLD to feed the multiple MPDUs with the common TID for transmission on the one or more links; and a transmitter to send an immediate Block Ack on a link to the initiator MLD, the immediate Block Ack indicating a reception status of one or more of the multiple MPDUs belonging to the common TID transmitted on the link.
[0006] A non-limiting and exemplary embodiment facilitates providing a receiving method by a receiving multi-link device (MLD), the receiving method comprising: establishing a multi-link Block Ack protocol mapped to a common traffic identifier (TID) of multiple links with an initiator MLD; receiving multiple MAC layer protocol data units (MPDUs) with a common TID on one or more links of the multiple links from the initiator MLD, wherein a single common transmit buffer control is maintained at the initiator MLD to feed the multiple MPDUs with the common TID for transmission on the one or more links; and sending an immediate Block Ack to the initiator MLD, the immediate Block Ack indicating a reception status of one or more of the multiple MPDUs belonging to the common TID transmitted on the link.
[0007] A non-limiting and exemplary embodiment facilitates providing a multi-link device operating with a first plurality of subsidiary stations, the first multi-link device comprising: circuitry to establish a multi-link block acknowledgment protocol for a particular traffic identifier TID with a receiving multi-link device operating with a second plurality of subsidiary stations, wherein the particular TID corresponds to a plurality of links; and a transmitter to transmit a plurality of MAC layer protocol data units MPDUs belonging to the particular TID to the receiving multi-link device on one or more links, and to transmit a block acknowledgment request frame to request a change in a value of a window start WinStart maintained at the receiving multi-link device, wherein a single common transmit buffer control is maintained to manage transmission of the plurality of MPDUs on the one or more links.
[0008] Another non-limiting and exemplary embodiment contributes to a method for multi-link communication, comprising: establishing, at an initiator multi-link device, a multi-link block acknowledgment protocol with a receiver multi-link device for a specific traffic identifier TID, the receiver multi-link device operating with a second plurality of auxiliary stations, the initiator multi-link device operating with a first plurality of auxiliary stations, wherein the specific TID corresponds to a plurality of links; and sending a plurality of MAC layer protocol data units MPDUs belonging to the specific TID to the receiver multi-link device on one or more links, and sending a block acknowledgment request frame to request a change in a value of a window start WinStart maintained at the receiver multi-link device, wherein a single common transmit buffer control is maintained to manage transmission of the plurality of MPDUs on the one or more links.
[0009] It should be noted that general or specific embodiments may be implemented as systems, methods, integrated circuits, computer programs, storage media, or any combination thereof. Other benefits and advantages of the disclosed embodiments will become apparent from the specification and drawings. These benefits and / or advantages may be obtained individually by various embodiments and features of the specification and drawings, and these embodiments and features do not need to be provided in their entirety to obtain one or more of such benefits and / or advantages. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The accompanying drawings are used to illustrate various embodiments and explain various principles and advantages according to the present embodiments. In the accompanying drawings, the same figure numbers refer to the same or functionally similar elements in each view, and the accompanying drawings together with the following detailed description are incorporated into the specification and form a part of the specification.
[0011] Figure 1 A diagram depicting an overview of an 802.11 wireless network basic service set (BSS) in accordance with various embodiments is depicted.
[0012] Figure 2 Depicted is a diagram of communications from an initiating multi-link device (MLD) to a receiving MLD in accordance with various embodiments.
[0013] Figure 3 Depicted is a diagram of the establishment of a traffic flow (TS) and block acknowledgment (BA) protocol for a traffic identifier (TID) in accordance with various embodiments.
[0014] Figure 4 Depicted is the communication flow between the AP MLD 102 and the non-AP MLD 104 according to current multi-link communications for TS and BA establishment and subsequent communications over multiple bands / links.
[0015] Figure 5 Depicted is a communication flow between the AP MLD 102 and the non-AP MLD 104 for multi-link TS and multi-link BA establishment and communications thereafter, according to various embodiments.
[0016] Figure 6 Depicted are diagrams of multi-link Enhanced Distributed Channel Access (EDCA) parameter set elements in accordance with various embodiments.
[0017] Figure 7 Depicted are diagrams of a multilink ADDTS request frame and a multilink ADDTS response frame in accordance with various embodiments.
[0018] Figure 8 Depicted are diagrams of a multilink ADDBA request frame and a multilink ADDBA response frame in accordance with various embodiments.
[0019] Fig. 9 Depicted are various embodiments Figure 7 and Figure 8 Illustration of the multi-band elements in .
[0020] Fig.10 Depicted are diagrams of multi-band capable elements in accordance with various embodiments.
[0021] Fig.11 Depicted are diagrams of a multilink BlockAckReq frame and a multilink BlockAck frame in accordance with various embodiments.
[0022] Fig. 12A Depicted are diagrams of traffic flows and block ACK architectures in accordance with various embodiments.
[0023] Fig. 12B Depicted is a diagram of traffic flows and block ACK architecture objectives defined to take care of multi-link transmission and multi-link block ACK in accordance with various embodiments.
[0024] Fig.13 Depicted are diagrams of exemplary multi-link transmissions in accordance with various embodiments.
[0025] Fig.14 A diagram of an exemplary reference model for a multi-link block acknowledgement implementation in accordance with various embodiments is depicted.
[0026] FIG. 15A to FIG. 15D A diagram depicting how a failed multilink transmission may result in an out-of-range scoreboard context and a receive reordering buffer overflow in accordance with various embodiments.
[0027] Fig.16 A diagram of a multi-link block acknowledgement architecture 1600 is depicted in accordance with the present embodiment.
[0028] Fig.17A and Fig. 17B Depicted is a diagram of a multi-link block ACK parameter set 1700 and a multi-band element 1710 for a block ACK architecture 1600 in accordance with the present embodiment.
[0029] Fig.18 The format of an enhanced BlockAck Request (eBAR) frame 1800 for a multi-link block acknowledgement architecture 1600 according to the present embodiment is depicted.
[0030] Fig.19 Describes how to use the eBAR frame 1800 to solve the problem previously described in Fig.15A Illustration of the scoreboard context out of scope problem shown in .
[0031] Fig. 20Describes how the common transmit buffer control of the multi-link block acknowledgement architecture 1600 prevents Fig. 15C and Fig.15D Illustration of the receive reorder buffer overflow problem shown.
[0032] Fig.21 Depicted is a diagram of a multi-link block acknowledgement architecture 2100 with common multi-link scoreboard context control according to a variation of the present embodiment.
[0033] Fig.22A and Fig. 22B Depicted is a diagram of a multi-link block ACK parameter set 2200 and a multi-band element 2210 for a block ACK architecture 2100 in accordance with the present embodiment.
[0034] FIG. 23A to FIG. 23C A diagram of an ADDBA request frame 2304, an ADDBA response frame 2306, a block acknowledgement parameter set 2300, and a multilink element 2310 is depicted according to another variation of the present embodiment.
[0035] Fig.24 A schematic diagram of an initiator MLD 2400 is depicted in accordance with various embodiments.
[0036] Fig.25 A schematic diagram of a receiving MLD 2500 is depicted in accordance with various embodiments.
[0037] Fig.26 A flow chart 2600 illustrating a method for multi-link communication according to various embodiments is shown.
[0038] Fig. 27 Shown according to Figures 1 to 26 A schematic partial cross-sectional view of a multi-link device 2700 in which various embodiments may be implemented for multi-link communications is shown.
[0039] as well as Fig.28 A detailed block diagram of a multi-link device according to the present embodiment is depicted.
[0040] Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale. DETAILED DESCRIPTION
[0041] The following detailed description is merely exemplary in nature and is not intended to limit the application and uses of the embodiments or the embodiments. In addition, it is not intended to be bound by any theory proposed in the foregoing background technology or this detailed description. In addition, other desired features and characteristics will become apparent from the subsequent detailed description and the appended claims in conjunction with the accompanying drawings and the background of the present disclosure.
[0042] refer to Figure 1, which depicts an overview of an 802.11 wireless network (also referred to as a basic service set (BSS)) 100, which includes an access point (AP) 102 and multiple communication devices (STAs) 104 connected to the AP 102; the AP 102 provides the STAs with access to a distributed system (DS) (e.g., the Internet). Current IEEE 802.11 BSSs operate on a single frequency band, with an AP being able to operate on multiple frequency bands simultaneously, acting as an independent (single-link) AP on each frequency band. Most existing 802.11 STAs are single-band devices and can only join one BSS (on a particular frequency band) at any one time, while future 802.11 communication devices (e.g., extremely high throughput (EHT) communication devices) are expected to be able to operate on multiple frequency bands simultaneously. A STA with multi-link capability may be referred to as a non-AP MLD. Such a non-AP MLD may concurrently join multiple BSSs at the same time, and may establish multiple communication links with an AP on multiple frequency bands or even on multiple frequency-separated channels on the same frequency band. Such an AP that can communicate with non-AP MLDs concurrently through multiple links can be called an AP MLD. Figure 1 , AP 102 represents an APMLD, and STA 104 represents a non-AP MLD; both the AP MLD and the non-AP MLD are capable of communicating concurrently in the 2.4 GHz band, the 5 GHz band, and the 6 GHz band. This future AP 102 can establish a BSS in the 2.4 GHz band, the 5 GHz band, or the 6 GHz band as an independent BSS in the existing 802.11 system, in which case the traditional STA can join the BSS on the three bands according to the traditional authentication and association process. Alternatively, the AP can also operate a unified / virtual BSS that operates on multiple bands (i.e., the 2.4 GHz band 106, the 5 GHz band 108, and the 6 GHz band 110), as shown in BSS100. In either case, it is assumed that STA104 has joined the unified / virtual BSS100 on all three bands through separate authentication and association requests / responses on each band or through multi-link establishment negotiation (e.g., authentication and association requests / responses) on any one of the bands.
[0043] Figure 2A diagram 200 depicts the communication of a video file 202 from an AP MLD 201 to a non-AP MLD 203. In order to fully realize the throughput gains of multi-link aggregation, a traffic stream (TS) and block acknowledgement (BA) mechanism operating on multiple links is desired. Such multi-link TS and BA can help achieve a multiple increase in device throughput by enabling traffic aggregation on multiple links (e.g., 2.4GHz 204, 5GHz 206, and 6GHz 208). If there are no restrictions on traffic for any traffic identifier (TID) on any link, that is, no admission control is enforced for any access category (AC) on any link, then the establishment of a multi-link TS is optional. The streaming of high-resolution video 206 (e.g., high definition (HD) or 4K or 8K video) may require such multi-link transmission. At the Internet Protocol (IP) layer 210 of the AP MLD 201, the video file 206 is split into small IP packets. The 802.11 media access control (MAC) layer 212 of the AP MLD 201 converts the IP packets into 802.11 MAC layer protocol data units (MPDUs) and feeds them to the MAC TX queue 214, which in turn provides the MPDUs to the transceivers 216, 218, 220 in the lower MAC layer 212 and the physical layer (PHY) 222 for simultaneous transmission on the 2.4 GHz, 5 GHz, and 6 GHz frequency bands, respectively. In this way, the MPDU 224 is sent on the 2.4 GHz frequency band, the MPDU 226 is sent on the 5 GHz frequency band, and the MPDU 228 is sent on the 6 GHz frequency band to the non-AP MLD 203.
[0044] At the non-AP MLD 203, the MPDUs 224, 226, 228 are received by the transceivers 230, 232, 234 in the PHY layer 236 and the lower MAC layer 238. The MPDUs 224, 226, 228 are collected by the MAC layer 238 and reordered (if necessary) before being passed to the MAC RX queue 240 and to the IP layer 242 where the IP packets are assembled to form back the original video file 206.
[0045] In current 802.11 communication devices, admission control is usually enforced to maintain quality of service (QoS) levels for high priority services such as video (AC_VO) or voice (AC_VI). When the AP MLD enforces admission control on the access category (AC) (e.g., via the Admission Control Enforcement (ACM) subfield in the Enhanced Distributed Channel Access (EDCA) Parameter Set element), the non-AP MLD may need to establish a TS for the access category (AC) with the AP MLD via an Add Service Stream (ADDTS) request / response exchange. The Service Specification (TSPEC) element in the ADDTS request frame and the ADDTS response frame specifies various parameters related to the TS, including the Service Stream Identifier (TSID), direction, MAC Service Data Unit (MSDU) size, minimum and maximum interval ranges, and minimum, average and peak data rates, etc. If there is no restriction on the service of any access category (AC) on any link, that is, admission control is not enforced for any AC on any link, then the establishment of a multi-link TS is optional.
[0046] The block acknowledgement protocol for the corresponding TID also needs to be performed through an add block acknowledgement (ADDBA) request / response exchange. Traffic flows and block acknowledgement protocols can also be established for different bands by including multi-band elements in the ADDTS and ADDBA request / response exchanges, respectively, or via an on-channel tunnel (OCT).
[0047] Since the unmanaged addition of new high-priority services to the wireless network may have an adverse impact on the QoS of existing services, AP MLD generally enforces admission control for such services. In the presence of a large amount of existing services, AP MLD may reject a request from a non-AP MLD to establish a service flow for the access category (AC).
[0048] In order to implement multi-link transmission according to this embodiment, it will be necessary to change the TS and BA operations, because the current TS and BA establishment is established between MAC layers on a specific link. Figure 3, diagram 300 depicts a traffic stream (TS) and block acknowledgement (BA) protocol for a traffic identifier (TID) established between a multilink initiator 302 and a multilink receiver 304 according to the present embodiment. The TS and BA protocols are usually established in pairs, wherein the BA protocol is established in the opposite direction to the TS direction. The TS 306, 308, 310 are established between the transmit MAC layer 318, 320, 322 of each link and the corresponding receive MAC layer 324, 326, 328 of each link for data transmission from the multilink initiator 302 to the multilink receiver 304, while the BA protocol 312, 314, 316 is established in the opposite direction between the receive MAC layer 324, 326, 328 and the transmit MAC layer 318, 320, 322 for BA transmission from the multilink receiver 304 to the multilink initiator 302 to acknowledge the data transmission corresponding to the TS 306, 308, 310, respectively.
[0049] At the multilink initiator end, the upper layer 330 and the logical link control (LLC) layer 332 decide which link to use for the transmission of a particular TID. The MPDU for each TS 306, 308, 310 is generated at the transmit MAC layer (MAC layer 318, 320, 322) of each link and is addressed to the peer receive MAC layer (MAC layer 324, 326, 328) of the same link. At the receiving end, the reordering of MAC service data units (MSDUs) received through different links is done by the receive LLC layer 334 and passed to the receive upper layer 336. The block acknowledgement (BA) corresponding to the MPDU of each TS 306, 308, 310 is generated at the receive MAC layer (MAC layer 324, 326, 328) of the same link and is addressed to the peer transmit MAC layer (MAC layer 318, 320, 322) of each link. When a BA is not received or an MPDU is not acknowledged in the BA bitmap (the bit corresponding to the MPDU is set to 0), it is determined that the transmission of the unacknowledged MPDU has failed. Figure 4 As shown, the MAC layer retransmission of the unacknowledged MPDU occurs in the same frequency band (2.4GHz, 5GHz, 6GHz) as the failed transmission. It is also possible that instead of establishing a service flow (TS) to restrict the traffic of a specific TID to a specific link, some kind of TID mapping negotiation can be performed between the AP MLD and the non-AP MLD to map certain TIDs to specific links, for example, video traffic is mapped exclusively to the 6GHz link, audio traffic is mapped exclusively to the 5GHz link, and the rest of the traffic is mapped to the 2.4GHz link. In the absence of TS establishment or TID mapping, it is assumed that traffic of any TID can be sent on any link by default.
[0050] Figure 4A communication flow 400 is depicted between a multilink initiator 302 (AP MLD in this example) and a multilink receiver 304 (non-AP MLD in this example) for TS and BA establishment and subsequent communication according to current multilink communication. If the EDCA parameter set element received in the beacon frame in any link has the admission control mandatory (ACM) bit set for any access category (AC), the non-AP MLD (such as the multilink receiver 304) is required to establish a service flow (TS) with the multilink initiator 302 for the corresponding TID(s) before sending data frames belonging to that TID / AC on the link. TS establishment 402 for a specific TID is performed separately for each link, for example, for downlink data transmission (i.e., from AP MLD to non-AP MLD) by exchanging ADDTS request / response frames on each link. Regardless of the direction of actual data transmission, the ADDTS request is always initiated by the non-AP MLD. Similarly, BA establishment 404 for a specific TID is performed separately for each link by exchanging ADDBA request / response frames on each link. The ADDBA request is initiated by the multi-link initiator of the corresponding TS. Once the TS and BA are established in each link, data transmission and corresponding BA transmission can be performed in each link, such as 430 in the 6 GHz band, 440 in the 5 GHz band, and 450 in the 2.4 GHz band. The block acknowledgment (BlockAck) frame for data transmission in each link 430, 440, 450 is requested through a block acknowledgment request (BlockAckReq) frame, and the requested BlockAck frame is sent on the same link. Since the transmissions 430, 440, and 450 occur on different links, they can also occur simultaneously or in overlapping time, thereby realizing multi-link transmission.
[0051] When it is determined that the transmission of the data frame has failed (eg, in data transmission 452, as indicated in a BlockAck frame), the data frame is retransmitted on the same link (eg, retransmission 454).
[0052] Although multi-link transmission can be implemented in this way, the burden of scheduling, band selection, retransmission and other tasks is left to the upper layers 330, 336 ( Figure 3 ), they may not have the PHY layer 317, 319, 321, 323, 325, 327 information required to make such a decision. It would be better if the multi-link transmission decision was made at the MAC layer 318, 320, 322, 324, 326, 328 because the MAC layer has better information / control over the PHY layer.
[0053] Figure 5A communication flow for TS and BA establishment and subsequent communication between a multi-link initiator 302 and a multi-link receiver 304 according to the present embodiment is depicted. The multi-link initiator 302 may choose to listen to beacon frames sent on a single link in order to save power. In addition to the traditional EDCA parameter set elements, the beacon frame 502 on the main link (e.g., 5 GHz band) may carry a multi-band EDCA parameter set element to indicate EDCA parameters for links other than the link on which the beacon frame 502 is sent. If the ACM bit in the beacon frame 502 is set to "1" for any AC in any link, the multi-link receiver 304 needs to establish a service flow (TS) for the TID corresponding to the AC on the indicated link(s) before sending a data frame belonging to the TID / AC on the indicated link(s). Alternatively, the multi-link receiver 304 may have received beacon frames separately on each link, in which the traditional EDCA parameter set element carrying the ACM bit is set to "1".
[0054] If both the initiator and the receiver support Multilink TS and Multilink BA and have indicated the capability in the Multilink TS and Block Ack fields in the Multilink Capability element (the Multilink Capability element including the Multilink TS and Block Ack fields is in Fig.10 ), according to the present embodiment, a single frame exchange (e.g., on a channel in the main link) may be used to perform a multi-link TS setup 510 (e.g., for downlink traffic) for a specific TID applicable to multiple links (e.g., three frequency bands: 2.4 GHz, 5 GHz, and 6 GHz). Similarly, according to the present embodiment, a single frame exchange (e.g., on a channel in the main link) may be used to perform a corresponding multi-link BA setup 520 for the TID applicable to multiple links (e.g., three frequency bands: 2.4 GHz, 5 GHz, and 6 GHz). A multi-link ADDTS request frame 512 and a multi-link ADDTS response frame 514 are used to negotiate a TS setup 516 for the TIDs on multiple links. Similarly, a multi-link ADDBA request 522 and a multi-link ADDBA response 524 are used to negotiate a BA setup 526 for the TIDs on multiple links. In this downlink traffic example, the multilink ADDBA request 522 is sent by the AP 102 to the multilink receiver 304, which may be any of the non-AP MLDs 104. If the multi-band TS setup 510 is for uplink traffic, the multi-band ADDBA request would be sent in the opposite direction, i.e., from the multilink receiver 304 to the multilink initiator 302.
[0055] Once the multilink TS and multilink BA have been established in the multiple links, the multilink initiator 302 may initiate a multilink transmission 530 to the multilink receiver 304. The multilink transmission 530 includes simultaneous transmission of frames belonging to the same TS (TID / AC) in QoS data A-MPDUs 536a, 536b, and 536c, respectively, to the multilink receiver 304 over the three links.
[0056] After completing the multilink transmission 530, the multilink initiator 302 may send a multilink BlockAckReq 532 to the multilink receiver 304 on any link (e.g., on the primary link) to request a multilink block confirmation to confirm the frames 536a, 536b, 536c received on the three links. Upon receiving the multilink BlockAckReq 532 from the multilink initiator 302, the multilink receiver 304 sends a multilink block confirmation 534 on the same link where the multilink BlockAckReq 532 was received to indicate that the multilink receiver 304 successfully received the QoS data A-MPDUs 536a and 536b, but failed to receive the QoS data A-MPDU 536c sent on the 2.4 GHz band. According to this embodiment, in order to improve the success rate of retransmission by using frequency diversity, the multi-link initiator 302 may choose to retransmit the QoS data A-MPDU 538 on the 6 GHz band instead of the 2.4 GHz band used for the original transmission.
[0057] The multilink initiator 302 then sends a multilink BlockAckReq 542 to the multilink receiver 304 on a different link (e.g., on the primary 5 GHz link) to request a multilink block acknowledgment 544 that carries a consolidated BA bitmap that confirms frames received on the 6 GHz band. Therefore, it can be seen that, according to the present embodiment, a service flow is established across multiple links using a single multilink ADDTS frame exchange 512, 514 on any one link. Block acknowledgments are also established across multiple links using a single multilink ADDBA frame exchange 522, 524 on any one link. In addition, according to the present embodiment, the consolidated multilink BlockAck frame 534 confirms the multilink aggregate transmission, the multilink BlockAck frame 544 can be used to confirm transmission in another link, and the failed frame 536c can be retransmitted 538 on a different link.
[0058] Therefore, according to the present embodiment, the MLD (e.g., the AP MLD 102) includes a plurality of transceivers 216, 218, 220, each of which transmits signal frames 536c, 536a, 536b on a different frequency band among the plurality of frequency bands 204, 206, 208. The MLD further includes a medium access control (MAC) circuit 212 coupled to the plurality of transceivers 216, 218, 220, which generates a multi-link block acknowledgement request frame 532 and transmits the MAC multi-link block acknowledgement request frame 532 on one of the plurality of frequency bands 206 to request a multi-link block acknowledgement frame 534. The medium access control (MAC) circuit 212 then receives the multi-link block acknowledgement frame 534 on one of the plurality of frequency bands 206, acknowledging the signal frames 536a, 536b, 536c transmitted on the plurality of frequency bands.
[0059] In addition, according to the present embodiment, the MLD (e.g., the non-AP MLD 104) includes a plurality of transceivers 230, 232, 234 coupled to a MAC circuit 238. The plurality of transceivers 230, 232, 234 each receive a signal frame 536a, 536b, 536c on a different frequency band among the plurality of frequency bands 204, 206, 208. Upon receiving the multi-link block acknowledgement request frame 532 on one of the plurality of frequency bands 206, the MAC circuit 238 generates and transmits a multi-link block acknowledgement frame 534 on one of the plurality of frequency bands 206 to acknowledge the signal frames 536a, 536b, 536c received on the plurality of frequency bands 204, 206, 208.
[0060] Figure 6 Depicts a beacon frame 402 ( Figure 4 ) in FIG. 4 . The multi-link EDCA parameter set element 610 indicates EDCA parameters for links other than the link on which the beacon frame 402 is transmitted. The applicable links are indicated by the band ID field 612. The format of each of the parameter record fields 620 for a specific AC is depicted. If the ACM bit 622 is set to "1" for any AC in any link, the non-AP MCD needs to establish a traffic flow (TS) for the TID corresponding to the AC on the link before sending data frames belonging to the TID / AC on the indicated link. Alternatively, in place of the band ID field 612, a multi-link field may be present in the EDCA parameter set element 610 to indicate the applicable links. Alternatively, the non-AP MCD may also receive beacon frames separately on each link with a legacy EDCA parameter set element carrying the ACM bit 622 set to "1".
[0061] According to this embodiment, Figure 7A diagram 700 depicts a multilink ADDTS request frame 710 and a multilink ADDTS response frame 720, and Figure 8 A diagram 800 of a multilink ADDBA request frame 810 and a multilink ADDBA response frame 820 is depicted. The multilink ADDTS request frame 710 and the multilink ADDTS response frame 720 are used to negotiate TS establishment for TIDs on multiple links in response to information in one or more multiband elements 750 in each of the multilink ADDTS request frame 710 and the multilink ADDTS response frame 720. Similarly, the multilink ADDBA request frame 810 and the multilink ADDBA response frame 820 are used to negotiate BA establishment for TIDs on multiple links in response to information in one or more multiband elements 750 in each of the multilink ADDBA request frame 810 and the multilink ADDBA response frame 820.
[0062] refer to Fig. 9 , diagram 900 depicts a multi-band element 750 according to the current embodiment. The multi-band element 750 indicates additional bands (in addition to the transmitted link) to which the TS or BA protocol applies. The multi-band element 750 may also include a MAC address used in the link.
[0063] The multi-band element 750 includes, among other fields, a multi-band control field 910, which includes several fields, including an inter-band field 920. The inter-band field 920 is used to distinguish the multi-band elements used in multi-link TS and BA establishments. When the inter-band field 920 is set to "1", it indicates that the corresponding establishment applies to the link indicated in the band ID field 930 in addition to the link on which the frame carrying the element is sent. Therefore, the inter-band field 920 is used to distinguish the inclusion of the multi-band element 750 for multi-link ADDTS and multi-link ADDBA establishments according to the present embodiment from the traditional use for ADDTS and ADDBA establishments on different links.
[0064] exist Figure 7 and Figure 8 , each of the multilink ADDTS request frame 710, the multilink ADDTS response frame 720, the multilink ADDBA request frame 810, and the multilink ADDBA response frame 820 includes two multi-band elements 750, wherein the inter-band field 920 is set to "1", and the band ID field 930 is set to 2.4 GHz in the first multi-band element 750 and is set to 6 GHz in the second multi-band element 750. Since the frame is sent on the 5 GHz band, this indicates that multi-links are established on three links.
[0065] Although in this example, the multilink ADDBA request 810 is sent by the multilink initiator 302 to the multilink receiver 304, if the multilink TS establishment 510 is for uplink traffic, the multilink ADDBA request will be sent by the multilink receiver 304 to the multilink initiator 302. Once the TS and BA are established in the multilink, the AP 102 can initiate a multilink transmission 530 to the STA 104, and the multilink transmission 530 includes frames belonging to the same TS (TID / AC) to be transmitted to the multilink receiver 304 simultaneously through three links.
[0066] Fig.10 A diagram 1000 of a multi-band capability element 1010 is depicted in accordance with various embodiments. If both the initiator and the receiver support multi-link TS and multi-link BA, and have indicated this capability in the multi-band TS and block acknowledgement field 1020 in the multi-band capability element 1010, a multi-band TS setup 510 (downlink traffic) and a multi-band BA setup 520 applicable to a specific TID of the multi-link may be performed using a single frame exchange, for example, on a channel in the primary link. The multi-band TS and block acknowledgement field 1020 also indicates whether the AP 102 and the STA 104 support the multi-link TS and multi-link BA features, and the supported bands field 1030 indicates the bands supported by the AP 102 and the STA 104. The capabilities of the multi-link TS feature and the multi-link BA feature may also be signaled separately in different fields.
[0067] Fig.11 A diagram of a multilink BlockAckReq frame 1100 and a multilink BlockAck frame 1150 according to various embodiments is depicted. Upon completion of the multilink transmission 530, the multilink initiator 302 may send a multilink BlockAckReq frame 1100 to the multilink receiver 304 on any link (e.g., on the primary link) to request a multilink BlockAck frame 1150. The multilink BlockAck frame 1150 includes a merged BA bitmap in the BA information field 1152 that acknowledges frames received on the three links. The multiband field 1110 and the multiband field 1160 distinguish the multilink BlockAckReq frame 1100 and the multilink BlockAck frame 1150 from a prior art single-link BlockAckReq frame and a prior art single-link BlockAck frame, respectively.
[0068] The combined BA bitmap in the multilink BlockAck frame 1150 indicates that the receiver failed to receive the QoS data A-MPDU 536c sent on the 2.4 GHz band. In order to improve the success rate of retransmission by using frequency diversity, the multilink initiator 302 may choose to retransmit the QoS data A-MPDU 538 on the 6 GHz band instead of the 2.4 GHz band used for the original transmission.
[0069] The multilink initiator 302 then sends a multilink BlockAckReq frame 1100 to the multilink receiver 304 on a different link (eg, on the primary link) to request a multilink BlockAck frame 1150 carrying a combined BA bitmap acknowledging frames received on the 6 GHz band.
[0070] The receiver address (RA) and transmitter address (TA) fields are set to the MAC address of the wireless radio interface of each link. However, regardless of the contents of the RA and TA fields, if the multi-band field 1110 is set to "1", the BlockAckReq frame 1100 is interpreted as requesting a multi-link BlockAck frame, which confirms that the frame belongs to the TID indicated in the TID_INFO field 1112, regardless of the link on which the frame is received. Similarly, regardless of the contents of the RA and TA fields, if the multi-band field 1160 is set to "1", the multi-link BlockAck frame 1150 carries a merged BA bitmap in the BA information field 1152, which confirms that the frame belongs to the TID indicated in the TID_INFO field 1162, regardless of the link on which the frame is received.
[0071] Therefore, according to the present embodiment, services belonging to the same TID can be split on multiple frequency bands. In addition, block ACKs of multiple frequency bands can be combined and sent on another frequency band. According to the present embodiment, this capability is provided for existing block ACK request types such as compression, multi-TID, multi-STA, and multicast with retry (GCR) block ACK request types.
[0072] Fig. 12AA diagram 1200 of a traffic flow and block acknowledgement architecture according to various embodiments is depicted. The MAC layers 318, 320, 322, 324, 326, 328 are split into a band-agnostic unified upper MAC (UMAC) layer 1202, 1204 and a band-specific lower MAC (LMAC) layer 1206, 1208, 1210, 1212, 1214, 1216. In this architecture, the LMAC / PHY layers of different links are tightly coupled with the UMAC that coordinates the operation of the LMACAC / PHY layer specific to each link. This architecture may be suitable when the MLD is implemented as a single chip silicon hardware. The multi-link traffic flow protocol 1220, 1222, 1224 and the multi-link block acknowledgement protocol 1230, 1232, 1234 for the TID are established between the corresponding MAC layers of each link.
[0073] The upper layers 330, 336 and the LLC layers 332, 334 only need to process the unified UMAC layers 1202 and 1204, respectively. On the transmitter 302 side, the unified UMAC layer 1202 performs multi-link aggregation of TS data on three TS data paths 1240, 1242, 1244 (i.e., frames belonging to a specific service stream (TS) can be aggregated on different links) and decides which link(s) to use for transmission and retransmission. The actual link used for transmission can be transparent to the upper layers. The unified UMAC 1204 of the multi-link receiver 304 is responsible for multi-link de-aggregation (i.e., reordering frames belonging to a specific service stream (TS) received from different links) and records the reception in the merged block confirmation scoreboard.
[0074] The unified UMAC 1204 of the multilink receiver 304 is also responsible for multilink block acknowledgement generation and transmission of multilink block acknowledgements (BAs) on the selected link (2.4 GHz in this example) along the multilink BA path 1250. The multilink initiator 302 can request a multilink BA on any link by sending a multilink block acknowledgement request. The receiver 304 generates and sends a multilink block acknowledgement in response to the receipt of a multilink block acknowledgement request frame or based on an implicit request to generate a multilink BlockAck frame. The multilink BlockAck frame is sent on the same link on which the corresponding request is received.
[0075] Fig. 12BA diagram 1260 of a business flow and block acknowledgement architecture purpose defined for handling multi-link transmission and multi-link block acknowledgement according to the present embodiment is depicted. In this architecture, the MLD can be viewed as a collection of one or more affiliated STAs, each operating on one link at a time. All affiliated STAs can share a common MAC service access point (SAP) to the upper layer, and a unique MAC address can be assigned to represent the MLD. Each affiliated STA has its own MAC / PHY layer, and each MAC layer can have a unique MAC address assigned to it. The MAC address of the MLD can be the same as one of the MAC addresses of the affiliated STA, or they can be different. The MLD coordinates the operation of the affiliated STA specific to each link. For example, the initiator MLD 302 has three affiliated STAs 1280, 1282, and 1284, which operate on a 2.4 GHz link, a 5 GHz link, and a 6 GHz link, respectively. Similarly, the receiver MLD 304 has three affiliated STAs 1286, 1288, and 1290, which operate on a 2.4 GHz link, a 5 GHz link, and a 6 GHz link, respectively. STA 1280 has its own MAC layer 1266 and PHY layer 317 with MAC address TA-2, STA 1282 has its own MAC layer 1268 and PHY layer 319 with MAC address TA-5, STA 1284 has its own MAC layer 1270 and PHY layer 321 with MAC address TA-6, STA 1286 has its own MAC layer 1272 and PHY layer 323 with MAC address RA-2, STA 1288 has its own MAC layer 1274 and PHY layer 325 with MAC address RA-5, and STA 1290 has its own MAC layer 1276 and PHY layer 327 with MAC address RA-6. The MAC address of MLD 302 may be the same as that of STA 1280, i.e., TA-2, and the MAC address of MLD 304 may be the same as that of STA 1286, i.e., RA-2. This architecture may be appropriate when each affiliated STA is implemented as independent silicon, where multiple can be housed together in a module to form an MLD, in which case the MLD can be viewed as a logical cluster of STAs. Of course, as silicon technology advances, it is also possible to implement the entire MLD as a single piece of silicon hardware. It will be appreciated that various architectures of the MLD are possible. In this example, a multi-link traffic flow 1224 and a multi-link block acknowledgement protocol 1230 for a TID are established between the corresponding MLDs 302 and 304 and are link-agnostic, making management simpler.The multi-link traffic flow 1224 and the multi-link block acknowledgement protocol 1230 may be identified by the MAC address of the TID and MLD rather than by a link-specific MAC address.
[0076] At the initiator MLD 302, the MLD receives TS data from the upper layer via the common MAC SAP, performs multi-link aggregation of the TS data on the three TS data paths 1240, 1242, 1244, and decides which link(s) to use for transmission and retransmission, and passes the TS data to the corresponding STA for transmission on the link. Similarly, the receiver MLD 304 is responsible for multi-link deaggregation of the TS data received from each subordinate STA (and is also responsible for reordering frames belonging to the TS received on the three TS data paths 1240, 1242, 1244) before passing the TS to the upper layer via the shared MAC SAP.
[0077] Fig.13 A diagram 1300 of an exemplary multi-link transmission is depicted, showing transmissions on a first link 1302 in a first frequency band (e.g., 2.4 GHz), a second link 1304 in a second frequency band (e.g., 5 GHz), and a third link 1306 in a third frequency band 1306 (e.g., 6 GHz), and assuming that TS and BA establishment for the TID has been completed on the relevant links. The channel bandwidth on each link 1302, 1304, 1306 may vary depending on channel conditions and availability (e.g., 20 MHz on the 2.4 GHz band 1302, 80 MHz on the 5 GHz band 1304, and 160 MHz on the 6 GHz band 1306). In some deployments, link one 1302 (e.g., 2.4 GHz band) may be primarily used to exchange management and control frames (such as multi-link block confirmation request frames 1308 and multi-link block confirmation frames 1310) and may be referred to as a primary link, while link two 1304 (e.g., 5 GHz band) and link three 1306 (e.g., 6 GHz band) may be primarily used to exchange data frames 1312 (e.g., downlink (DL) PPDU) and may be referred to as secondary links or supplementary links. In other deployments, there may be no restrictions on the types of frames that may be sent on any link, and there may be no such primary / secondary link distinction.
[0078] After gaining access to the channels on each link, AP 102 initiates a multi-link transmission 1300, which includes a downlink PPDU 1312a on link three 1306, a downlink PPDU 1312b on link two 1304, and a downlink PPDU 1312c on link one 1302. Each PPDU may carry an aggregated MPDU (A-MPDU), each MPDU having multiple frames.
[0079] AP 102 sets the ACK policy in the QoS control field of each frame to block ACK to indicate that there should be no immediate ACK in each link, and allocates the transmission of BARs and BAs on the low-rate link (e.g., 2.4 GHz band 1302) to release the high-rate links (e.g., link 2 1304 and link 3 1306) for data transmission. In addition, each non-AP MCD, TID pair across multiple links uses the same sequence number counter to ensure that the sequence number (SN) of the transmitted frame is not repeated between links. In this example, frames with SN 1, 2, and 3 are transmitted in PPDU 1312c on link one 1302, frames with SN 4, 5, and 6 are transmitted in PPDU 1312b on link two 1304, and frames with SN 7, 8, and 9 are transmitted in PPDU 1312a on link three 1306. STA 104 (i.e., the receiver) maintains a separate BlockAck bitmap for each link at the network interface (NIC), but merges them into a single BlockAck bitmap 1314 upon receiving a multi-link BlockAckReq frame. The multi-link BA frame 1310 carries the merged bitmap 1314, which acknowledges frames received on the three links—a bit set to "1" indicates successful frame reception of a frame with an SN corresponding to that bit, and a "0" indicates failed frame reception of a frame with an SN corresponding to that bit.
[0080] In the exemplary transmission 1300, the multi-link aggregated DL PPDU frame transmission includes a frame 1312a sent on link three 1306, a frame 1312b sent on link two 1304, and a frame 1312c sent on link one 1302, and the transmission of the frame with SN 2 on link one 1302 and the transmission of the frames with SN 5 and 6 on link two 1304 failed. Upon completion of the multi-link transmission, the AP 102 sends a multi-link BlockAckReq frame 1308a to request a multi-link BA acknowledgment, which acknowledges the frames sent on the three links 1302, 1304, 1306. The multi-link BA 1310a combines the BlockAck bitmaps from the three links into a combined BlockAck bitmap 1314a. In the combined BlockAck bitmap 1314a, bits 2, 5, and 6 corresponding to SNs 2, 5, and 6 are set to "0", indicating failed reception of frames with SNs 2, 5, and 6, while the remaining bits are set to 1 to indicate successful reception. Since there are failed transmissions on link two 1304 and link one 1302, but not on link three 1306, the AP 102 may decide that the channel condition on link three is better and choose to combine the failed frames and resend them on link three 1306 in a PPDU 1312d. Subsequently, a multilink BlockAckReq frame 1308b is sent on link one 1302 to request a multilink BA 1310b carrying an acknowledgment of the frames carried in the PPDU 1312d sent on link three 1306. This time, all three retransmitted frames are successfully received, and the STA 104 sends a multilink BA 1310b with the corresponding bits in the BA bitmap set to 1.
[0081] Fig.14 A diagram 1400 depicts an exemplary reference model of a multi-link block acknowledgement implementation according to various embodiments. In a wireless communication device, the radio interface (I / F), PHY layer, and time-critical MAC functions of each link may be implemented as independent modules and may be considered as part of an independent attached STA (e.g., 1410, 1420, 1430 for 2.4 GHz band, 5 GHz band, and 6 GHz band, respectively, such as transceivers 230, 232, 234 ( Figure 2 )). All modules / STAs 1410, 1420, 1430 are connected to a host system 1405 (which may be a CPU). Physical layer (PHY) modules (e.g., 323, 325, 327 ( Fig. 12A , Fig. 12B )) and the lower MAC layer 1402 (e.g., 1212, 1214, 1216 ( Fig. 12A ) and 1272, 1274, 1276 ( Fig. 12B)) can be implemented on radio I / Fs 216, 218, 220, each of which can be an independent subordinate STA (e.g., Fig. 12B 1286, 1288, 1290), while the remaining MAC functions (i.e., the higher MAC layer 1404 (e.g., 1202 ( Fig. 12A ))) can be implemented in the host system 1405. The entire system 1400 can constitute an MLD.
[0082] Due to the low latency required to generate a BA in response to a BAR (within a short interframe space (SIFS) starting from the end of the BAR), a block ACK scoreboard for a specific band is implemented using fast but expensive on-chip memory in each radio I / F. However, maintaining a BA scoreboard that is maintained for the entire duration of all active block ACK sessions (called full-state block ACKs) increases the memory requirement burden for the receiver implementation. Therefore, most implementations reuse on-chip memory for more than one block ACK session, where the memory is used as a cache to store the state of the most recently active block ACK sessions (which are called partial-state block ACKs). The intra-band BA scoreboards 1412, 1422, 1432 are examples of on-chip memories used as BA scoreboards to record the reception status of frames received on the 2.4 GHz, 5 GHz, and 6 GHz bands, respectively. The intra-band BA scoreboard may also be referred to as a per-link BA scoreboard or a per-link scoreboard for short. Partial status block ACK saves memory but increases the risk that the block ACK scoreboard may be overwritten by another block ACK session in the next transmission opportunity (TXOP), so special handling is required to prevent data loss.
[0083] To implement the multilink block acknowledgement operation, a multilink BA scoreboard 1406 is maintained in the host system 1405. Because memory on the host system 1405 is typically cheaper, the multilink BA scoreboard 1406 can be implemented as a full-state block acknowledgement scoreboard, i.e., the scoreboard is maintained for the entire duration of the multilink block acknowledgement session.
[0084] According to the present embodiment, frames received in each link are parsed by Rx parsers 1414, 1424, 1434 and processed according to the frame type as shown in diagram 1400. Data frames 1415, 1425, 1435 that are correctly received and addressed to the receiver are recorded in the in-band BA scoreboards 1412, 1422, 1432 according to their sequence numbers (SN) before being passed up to the receive buffer 1408. The contents of the receive buffer 1408 can be reordered at regular intervals according to the data frame SN.
[0085] In conventional single-link block acknowledgement operation, at the completion of the TXOP (for implicit block acknowledgement) or upon receipt of a conventional BlockAck request (BAR) frame (for explicit block acknowledgement), the lower MAC copies the BA bitmap from the intra-band BA scoreboard and generates a BlockAck frame for immediate transmission. However, for multi-link block acknowledgement operation, explicit block acknowledgements may be used, and at the completion of the TXOP on each band, the multi-link BA scoreboard 1406 is updated with the contents of the intra-band scoreboards 1412, 1422, 1432 from the corresponding radio I / F. By the end of the multi-link transmission opportunity (TXOP), the multi-link BA scoreboard 1406 will have merged the BA bitmaps of all intra-band BA scoreboards 1412, 1422, 1432.
[0086] Finally, upon receiving a multilink BAR frame 1416 on any link, the upper layer MAC 1404 copies the BA bitmap from the multilink BA scoreboard 1406 and generates 1407 a multilink BlockAck frame for transmission. At the same time, the reception of the multilink BAR frame 1416 also triggers the upper layer MAC to reassemble complete MSDUs (all complete MSDUs with SNs lower than the starting sequence number (SSN) carried in the multilink BAR frame 1416) from the frames in the receive buffer 1408 and forward them to the upper layer in sequence. Although in the diagram 1400, the reception of the multilink BAR frame 1416 and the transmission of the multilink BA frame 1820 are shown in the 2.4 GHz band, it will be understood that the process is the same for other bands.
[0087] according to Figure 1-Figure 14 , a single block acknowledgment protocol may be negotiated between two MLDs for a TID that may be sent over one or more links. The block acknowledgment protocol may be represented by a tuple of {initiator MLD MAC address, recipient MLD MAC address and TID}. Additionally, a multi-link block acknowledgment protocol may be negotiated by exchanging a single pair of ADDBA request / response frames over any one of the enabled links between the two MLDs. Further, for MSDUs that may be sent over one or more links to a TID of a peer MLD, sequence numbers may be assigned according to a common sequence number space shared across multiple links of the MLDs.
[0088] However, potential problems may arise during multilink transmission when frames of the same TID are sent on different links simultaneously, such as when one or more of the per-link scoreboard contexts at the receiving MLD are out of range. Fig.15A, the initiator MLD can send MPDUs with SNs 1-15 on link 1 (as shown in link 1 send window 1502) and send MPDUs with SNs 16-30 on link 2 (as shown in link 2 send window 1504) to the receiver MLD. The SNs in the link 1 send window are controlled by the link 1 send control, which starts at WS_O=1 (i.e., WS_O refers to the start of the send window WinStart O ) and ends at 15 (assuming that the send window size of 15 is negotiated during the multi-link BA protocol for the two links), while the SN in the link 2 send window starts at WS_O=16 and ends at 30. For example, due to the poor quality of link 1 transmission, the receiving MLD may not be able to receive MPDUs with SN 3 and SN 5 to 15. This can be seen in the link 1 scoreboard 1512, where SN 3 and SN 5 to 15 have zero values. On the other hand, the link 2 scoreboard 1514 indicates that all MPDUs with SN 16 to 30 were successfully received by the receiving MLD. At this point, the link 2 scoreboard has been shifted to the right (from the initial WS_R=0) and now starts at WS_R=16 and ends at WE_R=30 (i.e., WS_R and WS_E refer to the starting SNWinStart of the scoreboard context, respectively. R and end SN WinEnd R ). These MPDUs are merged in the reordering buffer 1516, where the MPDU with the minimum value of the consecutively running SNs (i.e., SN 1 and SN 2) is then forwarded to the next MAC process. However, the MPDUs with SN 4 and onwards successfully received by the receiving MLD cannot be forwarded to the next MAC process because the MPDU with SN 3 is not correctly received, i.e., forwarding must be done in a first-in-first-out order. As a result, the SNs of the frames in the reordering buffer 1516 now start from 3 (i.e., WS_B=3; WS_B refers to the start WinStart of the receiving reordering buffer). B ), there are gaps at SN=3 and SN 5 to 15 because these MPDUs are not received by the receiving MLD.
[0089] refer to Fig. 15B, the initiator MLD can receive per-link BlockAck frames in each link, or multi-link BlockAck frames in one of the links, and understand the transmission status of the MPDU. As a next step, the failed MPDU on link 1 can be resent to the receiving MLD on link 2 to take advantage of the better link. However, since the scoreboard context on link 2 has been shifted to the right and is therefore out of the range of the retransmitted smaller SN, the MPDUs with smaller SNs retransmitted on link 2 will be discarded even if they are all received in an orderly manner. This is in line with IEEE802.11REVmd_D3.0, 10.25.6.3-Scoreboard context control during full-state operation, that is, if WinStart R +2 11 ≤1SN <WinStart R , no changes are made to the scoreboard record. Here SN refers to the SN of the received frame, and WinStart R Refers to the starting SN of the scoreboard context. The above is just an example to illustrate the potential problem of scoreboard contexts of different links out of range of each other, risking failure of MPDUs resent on another link. It can be appreciated that this problem will be made worse if different links have different bandwidths, and therefore different scoreboard context sizes. The scoreboard context of a link with a higher bandwidth can be expected to shift to the right faster than a link with a lower bandwidth, which increases the risk of scoreboard contexts of different links out of range of each other.
[0090] Alternatively, a receive reordering buffer overflow problem may also occur. Fig. 15C , the MPDUs with SN 3 and SN 5 to 15 that previously failed to be sent on link 1 can be resent to the receiving MLD on link 1. Fig.15A After successfully sending MPDUs with SNs 16 to 30, new MPDUs with SNs 31 to 45 may be sent to the receiving MLD on link 2. However, MPDUs with SNs 3 and 5 to 15 may again fail to be received on link 1, and MPDUs with SN 31 may fail to be received on link 2. As a result, the reordering buffer now has MPDUs with SNs from 16 to 45, with a gap at SN=31. Here, we assume that the size of the receive reordering buffer is WinSize B=30 (the sum of the buffer sizes of link 1 and link 2). According to the operating rules of the receive reordering buffer, when an MPDU with an SN greater than the end of the receive buffer is received, the end of the receiver reordering buffer is shifted to accommodate the new MPDU (i.e., WS_R=16, and WE_B=45; WE_B refers to the end of the receive reordering buffer WinStart B ), and when there is a gap in the SN of the MPDU, the content of the buffer with an SN less than the new start WS_R of the buffer (e.g., an MPDU with an SN of 4) is passed up to the next MAC process. In addition, the MPDUs with SNs 16 to 30 previously received on Link 2 are forwarded to the next MAC process, but due to the gap caused by the transmission failure of the MPDU with SN 31 (i.e., WS_R=31 and WE_B=60), the MPDUs with SNs 31 and above cannot be forwarded.
[0091] refer to Fig.15D , the failed MPDUs with SN 3 and SN 5 to 15 on Link 1 are again resent to the receiving MLD on Link 1. This time, all of these MPDUs are received successfully and their reception is recorded on the Link 1 scoreboard. However, even though the resent MPDUs are correctly received on Link 1, they cannot be recorded in the receive reordering buffer and will be discarded at the receiving MLD because the receive reordering buffer 1516 has been shifted to the right. This problem is more common when there is a large difference in bandwidth / throughput between the links (i.e., when the faster link will dominate the receive reordering buffer). When a packet with a higher SN (more than WinEnd) is received on the faster link, the receiving MLD will not receive the packet. B The receive reorder buffer will shift right (i.e. WinStart B and WinEnd B will become higher), increasing the risk of the receiver reordering buffer overflowing.
[0092] In order to solve the above problems, Fig.16 As shown, a two-tiered block acknowledgement architecture is proposed for multi-link transmission. Essentially, the initiator MLD includes a block acknowledgement for all links (or all attached STAs (if following Fig. 12B The MLD architecture in the example assumes that each link has one attached STA)) and a common transmit buffer 1602a shared between each (per) MLD-RA / TID transmit buffer control 1604, whose start SN is equal to WinStart T , and the size is WinSize T, which enables flexible retransmission across links and also prevents the receive reordering buffer at the receiving MLD from overrunning. On the other hand, the receiving MLD includes a receive reordering buffer control 1614 per MLD-TA / TID for a common receive reordering buffer 1612, whose start SN is equal to WinStart T , and the size is WinSize T , to ensure that the MPDU is forwarded to the next MAC process in the correct SN. Here, MLD-RA and MLD-TA refer to the MAC addresses of the receiving MLD and the initiating MLD, respectively. In other words, the initiating MLD maintains the send buffer and send buffer control for each TID of the multi-link block acknowledgement protocol. The initiating MLD also includes a send buffer control 1606a per L1-RA / TID (which has a start SN WinStart O And the size is WinSize O ), send buffer 1602a, block acknowledgement status per L1-RA / TID 1608a and aggregation control L1 1610a for link 1, and send buffer control 1606b per L2-RA / TID (which has a start SN WinStart O And the size is WinSize O ), send buffer 1602c, block ACK status per L2-RA / TID 1608b, and aggregation control L21610b for link 2. Here, L1-RA and L2-RA refer to the MAC addresses of the affiliated STAs of the receiving MLD operating on link 1 and link 2, respectively. In other words, if the link is part of a multi-link block ACK protocol, each affiliated STA of the initiating MLD also maintains a per-link send buffer control for each TID of the multi-link block ACK protocol. If the link is part of a multi-link block ACK protocol, each affiliated STA of the initiating MLD may also maintain a per-link send buffer for each TID of the multi-link block ACK protocol. Advantageously, the per-link send buffer controls 1606a and 1606b prevent overflow of the block ACK records (scoreboard context) maintained by each STA or station affiliated with the receiving MLD, which may be caused by the transmission of frames on one or more links, such as FIG. 15A to FIG. 15DAs shown. Advantageously, a common transmit buffer shared between all links enables flexible retransmissions across links and also prevents overruns of the receive reordering buffer at the receiver. However, storing the same MPDU in two different transmit buffers requires additional rules to ensure that the two transmit buffers remain synchronized. For example, an MPDU that has been sent on one link should not be sent on another link before receiving the transmit state on the original link. Only when feedback of a transmission failure is received on one link should the MPDU be retransmitted on the other link and the MPDU should be deleted from the per-link transmit buffer of the link of the original transmission. When feedback of a successful transmission is received through any link, or when the MSDU lifetime of the MSDU carried in the MPDU expires, the MPDU should be deleted from the per-link transmit buffer as well as the common transmit buffer. The size of the block acknowledgment record for each STA or station is independently negotiated during the multi-link block acknowledgment negotiation, which will be explained later. It will be understood that a STA attached to an initiator MLD or a receiver MLD may also be referred to as a station. The initiator MLD uses the Block Ack status to track the status of the transmitted MPDUs and is updated when a Block Ack frame is received from the receiver MLD. The role of the aggregation control is to construct an A-MPDU for transmission by aggregating two or more MPDUs.
[0093] On the other hand, the receiving MLD also includes a scoreboard context control L1 1616a for link 1 (which has a start SN WinStart R WinSize R ) and deaggregation control L1 1618a, and scoreboard context control L2 for link 2 (which has a start SN WinStart R WinSize R1616b) and deaggregation control L1 1618b. Scoreboard contexts are also called block acknowledgment records, which keep records of the reception status of MPDUs. The role of deaggregation control is to deconstruct the received A-MPDU into two or more MPDUs. The receiving MLD also maintains a common receive reordering buffer (or simply referred to as a receive buffer) for each TID of the multi-link block acknowledgment protocol. The main role of the receiver reordering buffer is to ensure that the MPDU is forwarded to the next MAC process in the correct SN order. Sharing a common receiver reordering buffer between affiliated STAs (links) ensures that the MPDUs received through different links are passed to the next MAC process in the correct order. It should be understood that the number of sets of send buffer control per RA / TID, block acknowledgment status per RA / TID, aggregation control, scoreboard context control, and deaggregation control can be extended to include 3 or more links. With this architecture, the initiator MLD maintains a dual send buffer control structure: a common send buffer control shared across multiple links, and a separate send buffer control for each link.
[0094] The multi-link extension of the HT-Immediate Block Ack mechanism may be referred to as Multi-link Block Ack and is negotiated separately for each direction between two MLDs for a particular TID. The MLD whose subordinate STAs transmit data using the Multi-link Block Ack protocol is referred to as the initiator MLD, and the MLD whose subordinate STAs are the receivers of the data is referred to as the receiver MLD. The Multi-link Block Ack protocol is uniquely identified by the tuple of {initiator MLD MAC address, receiver MLD MAC address, TID}.
[0095] In such Fig.16 In the architecture shown, the initiator MLD contains a common transmit buffer control per {receiver MLD MAC address, TID}, which is shared between the attached STAs or stations using the multi-link block acknowledgement protocol and uses WinStart T and WinSize T to submit the MPDU for transmission and release the transmit buffer upon receiving a BlockAck frame. T is the starting sequence number of the common send window across all links of the multi-link block acknowledgment protocol, WinSize T Is the size of the total send window and is equal to the receive reorder buffer maintained by the receiving MLD. WinSize TEqual to the size of the receive reorder buffer negotiated during the block ACK protocol. The size of the receive reorder buffer may be negotiated independently or may be calculated based on the size of the per-link scoreboard context. The common transmit buffer is used to store MSDUs or A-MSDUs until they are reported as successfully received or they exceed their lifetime (e.g., MSDU lifetime).
[0096] Each subordinate STA of the initiator MLD contains a per-link send buffer control and per-link block confirmation state and aggregation control for each {peer subordinate STA MAC address, TID}. Each subordinate STA also maintains a per-link send buffer valid for a short period of time (e.g., a single transmission opportunity (TXOP)) and can be used for retransmission per link, i.e., retransmission within the same TXOP.
[0097] The receiving MLD contains a common receive reordering buffer control per {originating MLD MAC address, TID} and is responsible for recording and reordering the MSDU / A-MSDU arriving from each attached STA, as well as identifying and discarding duplicate frames.
[0098] In addition, each affiliated STA of the receiving MLD contains a per-link scoreboard context control and deaggregation control for each {peer affiliated STA MAC address, TID}. Each per-link scoreboard context control contains an acknowledgment bitmap control, which contains the current reception status of the MSDU or A-MSDU received through the associated link, and can use full state or partial state operation.
[0099] The initiator MLD may store transmitted frames in the common transmit buffer until they are acknowledged as successfully received by the receiver MLD or until they are discarded at the end of the MAC Service Data Unit (MSDU) lifetime. On the other hand, stations attached to the initiator MLD may store frames in the per-link transmit buffer only for the duration of a transmission opportunity (TXOP). In other words, frames are stored in the common transmit buffer for a longer duration than in the per-link transmit buffer.
[0100] Fig.17A It shows that according to Fig.16 The block confirmation parameter set of the block confirmation architecture 1600 shown (ie, as Figure 8 fields in the ADDBA request frame 810 shown), and Fig. 17B It shows that according to Fig.16 The multi-band elements of the block confirmation architecture 1600 shown (ie, Figure 8The block acknowledgement parameter set 1700 includes a buffer size field 1702, which indicates in the ADDBA response frame the size of the scoreboard context control (i.e., WinSize ) of the link on which the ADDBA response frame is sent. R The multiband element 1710 now includes a buffer size field 1712, which indicates the size of the scoreboard context control (WinSize) for the link represented by the multiband element 1710 in the ADDBA response frame. R ).according to Fig.16 The architecture shown, the size of the receive reorder buffer WinSize B =WinSize T =WinSize across all links of the multi-link block acknowledgement protocol R Alternatively, the buffer size field 1702 in the ADDBA response frame may represent WinSize B , and the WinSize of the link on which the ADDBA response frame is sent R =WinSize B - The value of the Buffer Size field 1712 in the Multi-Band element (i.e., indirectly signals the WinSize of the link on which the ADDBA response frame is sent). R ).
[0101] Fig.18 Shown according to Fig.16 The format of the enhanced BlockAck Request (eBAR) frame of the architecture shown. According to the existing HT-Instant Block Acknowledgement rules, the BAR frame can be used to advance the WinStart R The value of the starting sequence number (SSN) is less than WinStart R The BAR is discarded, so it is not possible to move WinStart backwards R Therefore, the enhanced BAR (eBAR) frame 1800 can explicitly allow this. For example, if the shift WinStart R bit in field 1802, the receiving MLD shall replace the WinStart field of the scoreboard context (of the link on which the enhanced BAR frame was received) with the value of the Starting Sequence Number (SSN) subfield of the BAR Information field. R If this bit is not set, only when WinStart R <SSN≤WinStart R +2 11 WinStart R In addition, if you shift WinStart BIf the bit in field 1804 is set, the receiving MLD shall replace the WinStart Sequence Number subfield with the value of the Starting Sequence Number subfield of the BAR Information field. B If this bit is not set, the receiver shall not update based on the value of SSN in the BAR frame. In addition, the transmission of the eBAR frame 1800 on the link also replaces the WinStart bit of the link on the initiator side with the value of SSN. O .
[0102] Alternatively, if a protected block acknowledgement protocol has been successfully negotiated, a robust ADDBA request frame may also be used to achieve the same effect as the eBAR frame 1800. Thus, the BlockAck request frame may indicate whether the starting point of the block acknowledgement record maintained by the station should be replaced by the value of the starting sequence number (SSN) carried in the BlockAck request frame.
[0103] Fig.19 It shows how eBAR can solve the problem previously solved in Fig.15A The scoreboard context is out of range as shown in . Since after the initial transfer, the WinStart of the scoreboard 1512 on link 2 R = WS_R = 16, if the initiator MLD were to resend the failed MPDUs (originally sent on link 1) on link 2, they would be discarded by the receiver MLD because the SN is less than 16. To avoid this, the initiator MLD sends eBAR 1800 with SSN = 3, which is the minimum SN to be resent. Set the "Shift WinStart R " bit, so the receiving MLD should replace the WinStart bit of scoreboard 1902 on link 2 with the value of the Starting Sequence Number (SSN) subfield of the BAR Information field R Thereafter, as shown at 1900, the failed MPDU on link 1 may be retransmitted on link 2 without causing the scoreboard context control to become out of range. Advantageously, eBAR resolves the scoreboard context control out of range issue and facilitates cross-link retransmission.
[0104] Alternatively, if the initiating MLD decides to disable Link 1 due to repeated transmission failures, it can send a signal to the receiving MLD to disable Link 1. Upon receiving the signal to disable Link 1, the receiving MLD can shift the scoreboard context control to the left (making WinStart R =minimum SN that has not been successfully received), expecting retransmission of the failed MPDU on link 1.
[0105] like Fig.16As shown in the BlockAck architecture of , having a common send buffer control on all links of the multi-link block acknowledgement protocol will advantageously prevent the problem of overflow of the receive reordering buffer at the receiver (i.e., as previously described in Fig.15A , Fig. 15C and Fig.15D ). (WinStart T +WinSize T ) as the upper limit of the SN of the MPDU sent on each link, so that the highest SN sent on any link ≤ WinStart T +WinSize T .
[0106] Fig. 20 shows how the common send buffer control prevents Fig.15A , Fig. 15C and Fig.15D The receive reordering buffer overflow problem shown here. Here, WinStart T = refers to the start of the send window (i.e., WS_T) and is equal to the smallest SN that has not yet been confirmed as successfully received by the receiving MLD. As seen in the common send buffer control 2000, the MPDUs that previously failed to be sent on link 1 (i.e., MPDUs with SN 3 and SNs 5 to 15) are resent on link 1. The highest SN that can be safely sent on all links is determined by the common send window size (WinSize T )Limited: Highest SN=WinSitart T +WinSize T -1=32.
[0107] WinSize T is set to the buffer size value of the receive reorder buffer control 2004, and thus has the above rule to ensure that the MPDUs sent by the initiator MLD never overflow the receive reorder buffer at the receiver MLD. Now, if the failed MPDU on link 1 is resent on link 1, as Fig.15D If the initiator MLD gives up sending the MPDU (e.g., due to repeated transmission failures or due to expiration of the MPDU lifetime), the initiator MLD can shift the transmit window to the right by sending a BlockAck request frame with the SSN set to the value of the next MPDU to be sent. This makes the WinStart T and WinStart O The initiator MLD is set to SSN, and the recipient MLD is also set to SSN by setting WinStart R(ie, WS_R) and WinStart B (i.e., WS_B) is set to SSN to shift both the scoreboard and the receive window to the right. Subsequently, the transmission of MPDUs with higher SNs can be resumed. Advantageously, cross-link retransmissions are possible without overflowing the receive buffer.
[0108] According to another embodiment, if the receiving MLD supports merged block ACKs across multiple links, the scoreboard context controls for the individual links may be combined using a common multi-link scoreboard context control. Fig.21 A block confirmation architecture 2100 according to this embodiment is shown. Fig.16 Although the two architectures are almost identical, the main difference is that the receiving MLD in architecture 2100 now includes a size of (ML_WinStart R ,ML_WinSize R )'s multi-link scoreboard context control 2120. ML_WinStart R is the minimum WinStart value across all links of the Multilink Block Acknowledgement protocol negotiated by the initiator MLD and the receiver MLD R , so that ML_WinSize R ≥WinSize across all links of the multi-link block acknowledgement protocol R Another difference is that the initiator MLD in architecture 2100 maintains only one common transmit buffer 2100 shared among all links.
[0109] Architecture 2100 is based on the premise that dual transmit buffer control can be performed without separate per-link transmit buffers, such as transmit buffers 1602b and 1602c for Link 1 and Link 2, respectively, of block ACK architecture 1600. For example, the buffer in architecture 2100 is only the common transmit buffer 2102, and dual transmit buffer control is performed by address / pointer management.
[0110] The multilink scoreboard context control 2120 may operate according to the following rules for reception of data frames:
[0111] -If ML_WinStart R <=SN<=ML_WinEnd R : Set the bit at position SN in the bitmap to 1.
[0112] -If ML_WinEnd R <SN<ML_WinEnd R +2 11 :
[0113] 1) Will have from ML_WinEnd R The bits of the SN values from +1 to SN-1 are set to 0
[0114] 2)ML_WinEnd R =SN
[0115] 3)ML_WinStart R =SN-ML_WinSize R
[0116] 4) Set the bit at position SN in the bitmap to 1.
[0117] -If ML_WinEnd R +2 11 <=SN<=ML_WinEnd R : Do not make any changes
[0118] In addition, the multilink scoreboard context control 2120 may operate according to the following rules for reception of a multilink BlockAckReq (ML_BAR) frame:
[0119] -If ML_WinStart R <=SSN<=ML_WinEnd R :
[0120] 1)ML_WinStart R =SSN
[0121] 2) will have from ML_WinEnd R +1 to ML_WinSize R The bits of the SN value of -1 are set to 0
[0122] 3)ML_WinEnd R =ML_WinStart R +ML_WinSize R -1
[0123] -If ML_WinEnd R <SSN<ML_WinEnd R +2 11 :
[0124] 1)ML_WinStart R =SSN
[0125] 2)ML_WinEnd R =ML_WinStart R +ML_WinSizeR -1
[0126] 3) Will have from ML_WinStart R To ML_WinEnd R The bits of the SN value are set to 0
[0127] -If ML_WinEnd R +2 11 <=SSN<=ML_WinEnd R : Do not make any changes
[0128] The rules for updating the receive reordering buffer control when receiving a multilink BAR (ML_BAR) frame are the same as for receiving a BAR frame. In addition, the reception of a per-link BAR does not affect the ML_scoreboard, and the reception of an ML_BAR does not affect the per-link scoreboard.
[0129] exist Fig.16 The architecture shown and Fig.21 In the illustrated architecture, although it is advantageous to implement a separate send buffer control 1604 or 2104, it is also possible not to maintain such a record (WinStart T ,WinSize T ), but the initiator MLD performs control of transmissions across multiple links by referencing each per-link transmit buffer control record before each transmission to ensure that the receive reordering buffer at the receiver does not overflow. The initiator MLD ensures a minimum WinStart T (WinStart T +WinStart T ) is no greater than WinSize B In summary, the purpose of using a common transmit buffer control is to ensure that the transmission of MPDUs on different links does not cause problems for the receiving MLD, for example, overflow of the receive reordering buffer.
[0130] Fig.22A It shows that according to Fig.21 The block confirmation parameter set of the block confirmation architecture 2100 shown (i.e., as Figure 8 fields in the ADDBA request frame 810 shown), and Fig. 22B It shows that according to Fig.21 The multi-band elements of the block confirmation architecture 2100 shown (i.e., Figure 8 The block acknowledgement parameter set 2200 includes a buffer size field 2202, which indicates the size of the receive reorder buffer (ie, WinSize) in the ADDBA response frame.B ). The ADDBA request / response frame carries one multiband element for each link of the multilink block acknowledgement protocol (including the link on which the frame is sent). The multiband element 2210 now includes a buffer size field 2212, which indicates the scoreboard context control (WinSize ) of the link represented by the multiband element 2210 in the ADDBA response frame. R Each multi-band element 2210 identifies a link of the multi-link block acknowledgement protocol.
[0131] According to Fig.21 The architecture shown is 2100, WinSize T =WinSize B ≥ WinSize on all links of the multilink block acknowledgement protocol negotiated by the initiator MLD and the receiver MLD R The sum of the receive buffers on all links. A receive reordering buffer size that is larger than the sum of the receive buffers on all links can be negotiated to account for differences in link throughput. Additionally, the size of the receive reordering buffer can be negotiated independently of the size of the per-link scoreboard. This implementation can help reduce the chance of receive reordering buffer overflows due to differences in link bandwidth, etc., as previously described by being able to accommodate more MPDUs received on fast links without overflowing, while still being able to receive MPDUs from slower links. However, it must be appreciated that even though a larger sized receive reordering buffer may help mitigate some instances of receive reordering buffer overflows, it cannot by itself completely avoid the risk of receive reordering buffer overflows, and that some kind of centralized control of transmissions on different links on the initiator side will be necessary regardless of the size of the receive reordering buffer negotiated during the multi-link block acknowledgment protocol.
[0132] According to yet another embodiment, the ADDBA request and response frames may carry a multi-link element that specifies parameters related to all links of the multi-link block acknowledgement protocol negotiated between the initiator MLD and the receiver MLD. Fig.23A , Fig. 23B and Fig.23C , the ADDBA request frame 2304 and the ADDBA response frame 2306 may include a block acknowledgement parameter set field 2300 including a buffer size field 2302. The buffer size field 2302 indicates the size of the receive reorder buffer (WinSize B). The ADDBA request frame 2304 and the ADDBA response frame 2306 may also include a multilink element field 2310 including one or more link parameter fields 2312. The one or more link parameter fields may each include a link ID field 2314, a scoreboard size field 2316, and an optional MAC address field 2318. The link ID field 2314 identifies the associated link, where the link ID may be assigned during multilink establishment / association or during a separate link establishment process after association. The scoreboard size field 2316 in the multilink element 2310 in the ADDBA response frame 2306 indicates the size (WinSize) of the scoreboard context control of the link represented by the associated link ID identified in the link ID field 2314. R ). In the current embodiment, WinSize T =WinSize B ≥WinSize across all links of the multi-link block acknowledgement protocol R sum.
[0133] Fig.24A schematic diagram of an initiator MLD 2400 according to various embodiments is shown. The initiator MLD includes a common transmit buffer control 2406 with a common transmit buffer 2404 (i.e., the common transmit buffer control 1604 with the common transmit buffer 1602a in the initiator MLD of architecture 1600 and the common transmit buffer control 2104 with the common transmit buffer 2102 in the initiator MLD of architecture 2100) and a MAC-SAP 2402 for performing a distribution service (DS). The initiator MLD 2400 includes two subordinate STAs or stations (STA1 2408a and STA2 2408b). STA1 2408a includes a per-link transmit buffer control 2414a, a block acknowledgement state 2416a, and an aggregation control 2418a at the MAC layer (i.e., similar to the transmit buffer control 1606a, block acknowledgement state 1608a, and aggregation control 1610a in architecture 1600, and the transmit buffer control 2106a, block acknowledgement state 2108a, and aggregation control 2110a in architecture 2100). Similarly, STA2 2408b includes a per-link transmit buffer control 2414b, a block acknowledgement state 2416b, and aggregation control 2418b at the MAC layer (i.e., similar to the transmit buffer control 1606b, block acknowledgement state 1608b, and aggregation control 1610b in architecture 1600, and the transmit buffer control 2106b, block acknowledgement state 2108b, and aggregation control 2110b in architecture 2100). Both STAs include a PHY layer from which transmissions via Link 1 (for STA1 2408a) and Link 2 (for STA2 2408b) occur. It will be appreciated that the number of links and affiliated STAs or stations may be further extended.
[0134] Fig.25A schematic diagram of a receiver MLD 2500 according to various embodiments is shown. The receiver MLD includes a receive reordering buffer control 2506 having a receive reordering buffer 2504 (i.e., the receive reordering buffer control 1614 having the receive reordering buffer 1612 in the receiver MLD of architecture 1600 and the receive reordering buffer control 2114 having the receive reordering buffer 2112 in the receiver MLD of architecture 2100) and a MAC-SAP 2502 for performing a distribution service (DS). The receiver MLD 2500 includes two attached STAs or stations (STA1 2508a and STA2 2508b). STA1 2508a includes a scoreboard context control 2516a and a deaggregation control 2518a at the MAC layer (i.e., similar to the scoreboard context control 1616a and the deaggregation control 1618a in architecture 1600, and the scoreboard context control 2116a and the deaggregation control 2118a in architecture 2100). Similarly, STA2 2508b includes a scoreboard context control 2516b and a deaggregation control 2518b at the MAC layer (i.e., similar to the scoreboard context control 1616b and the aggregation control 1618b in architecture 1600, and the scoreboard context control 2116b and the aggregation control 2118b in architecture 2100). Both STAs include a PHY layer from which transmissions occur via Link 1 (i.e., between STA1 2508a and STA1 2408a at the initiator MLD 2400) and Link 2 (i.e., between STA2 2508b and STA2 2408b at the initiator MLD 2400). It will be appreciated that the number of links and dependent STAs or stations may be further extended.
[0135] Fig.26 A flowchart 2600 illustrating a method for multi-link communication according to various embodiments is shown. In step 2602, establishment of a block acknowledgement protocol is initiated at a first multi-link device with a second multi-link device operating with a second plurality of stations, the first multi-link device operating with a first plurality of stations, wherein a link has been established between each station in the first plurality of stations and a corresponding station in the second plurality of stations. In step 2604, frames of a traffic identifier (TID) are transmitted to the second multi-link device on one or more links based on the block acknowledgement protocol, wherein the first plurality of stations share a common transmit buffer storing frames of the TID to be transmitted to the second multi-link device and a common transmit buffer control managing transmission of frames on the one or more links, and wherein each of the first plurality of stations maintains a per-link transmit buffer control to manage transmission of frames on a corresponding one of the one or more links.
[0136] Fig. 27 Shown according to Figures 1 to 26 Schematic partial cross-sectional view of various embodiments of a multi-link device 2700 that may be implemented for multi-link communications. According to various embodiments, the multi-link device 2700 may be implemented as an AP MLD or a non-AP MLD and include one or more tributary stations or STAs.
[0137] The various functions and operations of the multilink device 2700 are arranged into layers according to a hierarchical model. In this model, the lower layers report to and receive instructions from the higher layers according to the IEEE specification. For simplicity, the details of the hierarchical model are not discussed in this disclosure.
[0138] like Fig. 27 As shown, the multi-link device 2700 may include circuitry 2714, at least one radio transmitter 2702, at least one radio receiver 2704, and multiple antennas 2712 (for simplicity, for illustration purposes, the antennas 2712 are not shown in FIG. Fig. 27 Only one antenna is depicted in FIG. 2 ). The circuit may include at least one controller 2706 for software and hardware assistance in performing the tasks it is designed to perform, including controlling communications with one or more other multi-link devices in a MIMO wireless network. The at least one controller 2706 may control at least one transmit signal generator 2708 for generating ADDBA action frames (such as ADDBA request frames and / or ADDBA response frames) to be transmitted to one or more other multi-link devices via at least one radio transmitter 2702, and control at least one receive signal processor 2710 for processing ADDBA action frames (such as ADDBA request frames and / or ADDBA response frames) received from one or more other multi-link devices via at least one radio receiver 2704. The at least one transmit signal generator 2708 and the at least one receive signal processor 2710 may be independent modules of the multi-link device 2700 that communicate with the at least one controller 2706 for the above-mentioned functions. Alternatively, the at least one transmit signal generator 2708 and the at least one receive signal processor 2710 may be included in the at least one controller 2706. It will be apparent to those skilled in the art that the arrangement of these functional modules is flexible and may vary according to actual needs and / or requirements. Data processing, storage and other related control devices may be provided on appropriate circuit boards and / or in chipsets. In various embodiments, at least one radio transmitter 2702, at least one radio receiver 2704 and at least one antenna 2712 may be controlled by at least one controller 2706. In addition, although only one radio transmitter 2702 is shown, it should be understood that there may be more than one such transmitter, i.e., one transmitter for each secondary station or STA of the multi-link device 2700.
[0139] like Fig. 27 As shown, at least one radio receiver 2704 together with at least one receive signal processor 2710 forms a receiver of the multi-link device 2700. The receiver of the multi-link device 2700 provides the functions required for multi-link communication. Although only one radio receiver 2704 is shown, it should be understood that there may be more than one such receiver, i.e., one receiver for each attached station or STA of the multi-link device 2700.
[0140] The multi-link device 2700 provides functions required for multi-link communication. For example, the multi-link device 2700 may be a first multi-link device operating with a first plurality of auxiliary stations. The circuit 2714 may initiate establishment of a block acknowledgement protocol with a second multi-link device operating with a second plurality of auxiliary stations, wherein a link has been established between each station in the first plurality of stations and a corresponding station in the second plurality of stations. The transmitter 2702 may transmit frames of a traffic identifier (TID) on one or more links to the second multi-link device based on the block acknowledgement protocol, wherein the first plurality of stations share a common transmit buffer and a common transmit buffer control, wherein the common transmit buffer stores frames of the TID to be transmitted to the second multi-link device, wherein the common transmit buffer control manages frame transmission on the one or more links, and wherein each of the first plurality of stations maintains a per-link transmit buffer control to manage frame transmission on a corresponding one of the one or more links.
[0141] Each of the first plurality of stations may maintain a separate per-link transmit buffer to store frames to be transmitted on a corresponding one of the one or more links. Circuitry 2714 may store frames in the common transmit buffer until they are acknowledged as successfully received by the second multi-link device or until they are discarded at the end of a MAC service data unit (MSDU) lifetime, the first plurality of stations storing frames in the per-link transmit buffer only for the duration of a transmission opportunity (TXOP).
[0142] The common transmit buffer control can be used to prevent overflow of a receive reordering buffer maintained by the second multilink device due to transmission of frames on one or more links; the per-link transmit buffer control is used to prevent overflow of a block acknowledgement record maintained by each of the second plurality of stations due to transmission of frames on one of the one or more links. In addition, the size of the receive reordering buffer managed by the second multilink device can be independently negotiated.
[0143] Circuit 2714 may negotiate a block acknowledgement protocol with the second multi-link device by exchanging ADDBA action frames on one of the one or more links, wherein the size of the block acknowledgement record maintained by each station in the second plurality of stations is independently negotiated.
[0144] Additionally, the circuitry may send a BlockAckReq frame to a second multi-link device on one of the one or more links to request a BlockAckReq frame, wherein the BlockAckReq frame indicates whether a starting point of a block acknowledgment record maintained by one of the second plurality of stations should be replaced with a value of a starting sequence number (SSN) carried in the BlockAckReq frame.
[0145] Fig.28 A detailed block diagram 2800 of a multi-link device 2802 according to the present embodiment is depicted. Each of the plurality of wireless I / Fs 2810, 2820, 2830 implements a corresponding one of the physical layer (PHY) processing modules 2816, 2826, 2836 and a corresponding one of the lower MAC function modules 2812, 2822, 2832. If such an architecture is implemented, the functions of the wireless I / Fs 2810, 2820, 2830 can be combined with Fig. 12B The functions of the subordinate STAs 1280, 1282, 1284, 1286, 1288, and 1290 in the AP 2802 are the same. The upper layer MAC functions can be implemented as software within a central processing unit (CPU) 2840, which can be coupled to a memory 2842 that can be used to store a multi-band BA scoreboard, an auxiliary storage 2844, and a wired communication I / F 2846 for communicating with an external network, other APs 102, or other MLDs. A power supply 2848 provides power to the AP 2802. If implemented Fig. 12B In the architecture shown, the upper layer MAC function is performed by MLD.
[0146] The present disclosure can be implemented by software, hardware or software in collaboration with hardware. Each functional block used in the description of each of the above embodiments can be implemented in part or in whole by an LSI such as an integrated circuit, and each process described in each embodiment can be controlled in part or in whole by the same LSI or a combination of LSIs. The LSI can be formed as a chip alone, or can be formed as a chip to include some or all of the functional blocks. The LSI may include data input and output coupled thereto. Depending on the degree of integration, the LSI here may be referred to as an IC, a system LSI, a super LSI or an ultra LSI. However, the technology for implementing the integrated circuit is not limited to the LSI, and can be implemented by using a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (field programmable gate array) that can be programmed after manufacturing the LSI or a reconfigurable processor in which the connection and setting of the circuit unit arranged inside the LSI can be reconfigured can be used. The present disclosure can be implemented as digital processing or analog processing. If the future integrated circuit technology replaces the LSI due to the advancement of semiconductor technology or other derivative technologies, the future integrated circuit technology can be used to integrate the functional blocks. Biotechnology can also be applied.
[0147] The present disclosure may be implemented by any kind of device, apparatus or system having a communication function, which is referred to as a communication device.
[0148] The communication device may include a transceiver and a processing / control circuit. The transceiver may include and / or act as a receiver and a transmitter. As a transmitter and a receiver, the transceiver may include an RF (radio frequency) module, which includes an amplifier, an RF modulator / demodulator, etc., and one or more antennas.
[0149] Some non-limiting examples of such communication devices include phones (e.g., cellular (mobile) phones, smart phones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telehealth / telemedicine (telehealth and medical) devices, and vehicles providing communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.
[0150] Communication devices are not limited to being portable or movable, and may also include any type of apparatus, device, or system that is not portable or stationary, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other “things” in an “Internet of Things” (IoT) network.
[0151] Communications may include exchanging data through, for example, cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.
[0152] The communication device may include a device such as a controller or a sensor, which is coupled to the communication device that performs the communication functions described in the present disclosure. For example, the communication device may include a controller or a sensor that generates a control signal or a data signal that is used by the communication device that performs the communication functions of the communication device.
[0153] Communications equipment may also include infrastructure such as base stations, access points, and any other device, apparatus, or system that communicates with or controls devices such as those in the non-limiting examples above.
[0154] As a framework (for example, Fig. 12A , Fig. 12B , Fig.16 , Fig.21 and Fig.28 The MLD of the present disclosure may be logical and may be implemented by multiple separate communication devices that share a common MAC data service interface to an upper layer, as a non-limiting example of the architecture shown in FIG.
[0155] A non-limiting example of a station may be a station included in a first plurality of stations attached to a multi-link station logical entity (i.e., such as an MLD), wherein as part of the first plurality of stations attached to the multi-link station logical entity, the stations of the first plurality of stations share a common medium access control (MAC) data service interface to an upper layer, wherein the common MAC data service interface is associated with a common MAC address or traffic identifier (TID). The station may include circuitry that initiates establishment of a block acknowledgement protocol with a second multi-link device operating with a second plurality of attached stations, wherein a link has been established between each station in the first plurality of stations and a corresponding station in the second plurality of stations; and a transmitter that transmits frames for the TID to the second multi-link device on one or more links based on the block acknowledgement protocol, wherein the first plurality of stations share a common transmit buffer and a common transmit buffer control, the common transmit buffer storing frames for the TID to be transmitted to the second multi-link device, the common transmit buffer control managing frame transmission on the one or more links, and wherein each of the first plurality of stations maintains a per-link transmit buffer control to manage frame transmission on a corresponding one of the one or more links.
[0156] Therefore, it can be seen that the present embodiment provides a communication device and method for operating on multiple links so as to fully realize the throughput gain of multi-link communications.
[0157] Although exemplary embodiments have been presented in the foregoing detailed description of the present embodiment, it should be understood that there are a large number of variations. It should also be understood that the exemplary embodiments are examples and are not intended to limit the scope, applicability, operation or configuration of the present disclosure in any way. On the contrary, the foregoing detailed description will provide those skilled in the art with a convenient solution for implementing the exemplary embodiments, and it should be understood that various changes may be made to the steps and methods of the operations described in the exemplary embodiments and the functions and arrangements of the modules and structures of the devices described in the exemplary embodiments without departing from the scope of the subject matter set forth in the appended claims.
Claims
1. A receiving multi-link device MLD, include: Circuit, establishes a multi-link block Ack protocol with the initiator MLD that is mapped to a common service identifier TID of multiple links; a receiver that receives, from the initiator MLD, a plurality of MAC layer protocol data units MPDUs having a common TID on one or more of the plurality of links, wherein a single common transmit buffer control is maintained at the initiator MLD to feed the plurality of MPDUs having the common TID for transmission on the one or more links; and A transmitter sends an immediate block Ack to the initiator MLD on a link, wherein the immediate block Ack indicates a reception status of one or more MPDUs sent on the link among the multiple MPDUs belonging to the common TID.
2. The receiving MLD according to claim 1, in, The immediate Block Ack of each link is merged into the multi-link Block Ack scoreboard.
3. The receiving MLD according to claim 2, in, The multi-link block Ack scoreboard includes a bitmap, the bitmap includes a plurality of bits, each bit indicating whether a corresponding MPDU is successfully received.
4. The receiving MLD according to claim 1, in, The multi-link block Ack protocol is established according to the TID in the following manner: receiving an Add Block Acknowledgement ADDBA request frame on an enabled link; and An Add Block Acknowledgement ADDBA response frame is sent on an enabled link.
5. The receiving MLD according to claim 1, in, The circuit maintains a single common receive reordering buffer to reorder multiple MPDUs received on the one or more links.
6. A receiving method performed by a receiving multi-link device MLD, the receiving method include: Establish a multi-link block Ack protocol with the initiator MLD that is mapped to a common service identifier TID of multiple links; receiving from the initiator MLD a plurality of MAC layer protocol data units MPDUs having a common TID on one or more of the plurality of links, wherein a single common transmit buffer control is maintained at the initiator MLD to feed the plurality of MPDUs having the common TID for transmission on the one or more links; as well as An immediate Block Ack is sent to the initiator MLD, the immediate Block Ack indicating a reception status of one or more MPDUs sent on the link among the plurality of MPDUs belonging to the common TID.
7. The receiving method according to claim 6, include: Merge the immediate Block Ack of each link into the multi-link Block Ack scoreboard.
8. The receiving method according to claim 7, in, The multi-link block Ack scoreboard includes a bitmap, the bitmap includes a plurality of bits, each bit indicating whether a corresponding MPDU is successfully received.
9. The receiving method according to claim 6, in, The multi-link block Ack protocol is established according to the TID in the following manner: receiving an Add Block Acknowledgement ADDBA request frame on an enabled link; and An Add Block Acknowledgement ADDBA response frame is sent on an enabled link.
10. The receiving method according to claim 6, comprising: A single common receive reordering buffer is maintained to reorder multiple MPDUs received on the one or more links.
