Multi-link communication method and apparatus

Abstract

This application discloses a multi-link communication method and apparatus. The method includes: a transmitter transmits a first A-MPDU, and a receiver receives the first A-MPDU. The receiver obtains a locally recorded scoreboard context, and when the first A-MPDU satisfies at least one of the following conditions, namely a first condition, a second condition, a third condition or a fourth condition, the receiver refreshes the scoreboard context based on the SN of the first A-MPDU. According to the method provided in this application, the receiver can properly and effectively refresh the local scoreboard context to ensure that the receiver correctly feeds back the reception status of all MPDUs in the A-MPDU received by the receiver.

Description

[Technical field]

[0001] [CROSS REFERENCE TO RELATED APPLICATIONS] This application claims priority to Chinese Patent Application No. 202210076088.X, entitled "MULTI-LINK COMMUNICATION METHOD AND APPARATUS," filed with the State Intellectual Property Office of China on January 23, 2022, and Chinese Patent Application No. 202210109328.1, entitled "MULTI-LINK COMMUNICATION METHOD AND APPARATUS," filed with the State Intellectual Property Office of China on January 28, 2022, the entire contents of both of which are incorporated herein by reference.

[0002] [Technical field] This application relates to the field of communications technology, and in particular to a multi-link communication method and apparatus. [Background technology]

[0003] Next-generation wireless local area network (WLAN) standards are developing and evolving toward continuous improvement of throughput. WLAN system standards are mainly studied and discussed in the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard group. For example, the main technology used to target extremely high throughput (EHT) may include multi-link (ML) communication. Based on multi-link communication, a multi-link device may perform communication on 2.4 GHz, 5 GHz, and 6 GHz frequency bands to select an optimal frequency band to ensure communication quality of the multi-link device.

[0004] In a multi-link communication scenario, an access point multi-link device may transmit data packets corresponding to the same traffic identifier to a station multi-link device through multiple links. Furthermore, when a station multi-link device maintains a local scoreboard on each link, stations on different links may not be able to correctly feedback the reception status of all MPDUs in a received aggregate media access control protocol data unit (A-MPDU) in the existing block acknowledgement mechanism.

[0005] Therefore, in a multi-link communication scenario, how to ensure that receiving devices on different links correctly feed back the reception status of all MPDUs in a received A-MPDU needs to be urgently solved. Summary of the Invention

[0006] This application provides a multi-link communication method and apparatus for effectively ensuring that a receiver correctly feeds back the reception status of all MPDUs in an A-MPDU received by the receiver.

[0007] According to a first aspect, an embodiment of the present application provides a multi-link communication method. The method includes: a receiver receives a first aggregate medium access control protocol data unit (A-MPDU); the receiver obtains a locally recorded scoreboard context, and refreshes the scoreboard context based on a sequence number SN of the first A-MPDU when the first A-MPDU satisfies any one or more of the following conditions: the first condition is that a STA associated with the receiver has a WinStart R ≦SN <WinStart R +2 11 The second condition includes receiving an MPDU having a SN that is B -WinSize R≦SN <WinStart B Any MPDU with a SN satisfying B -WinSize R ≦SN <WinStart B the first condition includes that all MPDUs having an SN satisfying the first condition are received by other STAs associated with the receiver, and the third condition includes that no frame in any other A-MPDU received before the first A-MPDU has not been acknowledged by the BA, any MPDU in any A-MPDU received before the first A-MPDU has been acknowledged by the BA, or all MPDUs carried in any A-MPDU received before the first A-MPDU have been acknowledged by the BA.

[0008] In a possible implementation, the first A-MPDU further satisfies a fourth condition, including: another MPDU with the SN in the first A-MPDU has not yet satisfied the first condition, the second condition and the third condition; the MPDU with the SN received by the STA associated with the receiver is the first MPDU in the first A-MPDU that satisfies the first condition, the second condition and the third condition; or the scoreboard context of the STA associated with the receiver has not been refreshed based on the MPDU in the first A-MPDU.

[0009] In a possible implementation, the receiver has separate scoreboard context control on each link, the link being between the receiver and the transmitter.

[0010] In a possible implementation, the STA associated with the receiver can use the reordering buffer information to update the scoreboard context.

[0011] In a possible implementation, the SNs in the first A-MPDU belong to the same traffic identifier TID.

[0012] According to the method provided in this embodiment of the present application, the receiver can properly and efficiently refresh the local scoreboard context.

[0013] For a specific description of the first aspect or any one of the possible implementation methods, it can be understood that reference can be made to the following description of the third scoreboard context control operation to the tenth scoreboard context control operation, the method shown in the following FIG. 4, etc. The details will not be described again one by one here.

[0014] According to a second aspect, an embodiment of the present application provides a multi-link communication method, the method including: a transmitter transmits a second A-MPDU, the A-MPDU includes indication information, the indication information instructing the receiver whether to refresh a scoreboard context of the receiver.

[0015] In a possible implementation, the indication information indicates whether the STA corresponding to the link used to transmit the second A-MPDU refreshes the scoreboard context of the STA.

[0016] In a possible implementation, the indication information is carried in the MPDU delimiter or in the high throughput control field.

[0017] For a specific description of the second aspect or any one of the possible implementation manners, it can be understood that reference can be made to the method shown in Fig. 5 and the description shown in Fig. 6a to Fig. 6d below. Details will not be described again one by one here.

[0018] According to a third aspect, an embodiment of the present application provides a communication device configured to perform a method according to the first aspect or any one of the possible implementations of the first aspect, the communication device comprising a unit for performing a method according to the first aspect or any one of the possible implementations of the first aspect.

[0019] For example, the communication device may be a transmitter, a chip within a transmitter, and so on.

[0020] According to a fourth aspect, an embodiment of the present application provides a communication device configured to perform a method according to the second aspect or any one of the possible implementations of the second aspect, the communication device comprising a unit for performing a method according to the second aspect or any one of the possible implementations of the second aspect.

[0021] For example, the communication device may be a receiver, a chip within a receiver, and so on.

[0022] In the third or fourth aspect, the communication device may include a transceiver unit and a processing unit. For a specific description of the transceiver unit and the processing unit, please refer to the embodiment of the device shown below.

[0023] According to a fifth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to execute the method as set forth in the first aspect or any one of the possible implementations of the first aspect. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method as set forth in the first aspect or any one of the possible implementations of the first aspect is executed.

[0024] In a possible implementation, the memory is located external to the communication device.

[0025] In a possible implementation, the memory is located within the communication device.

[0026] In this embodiment of the application, the processor and the memory may be further integrated into one component, in other words, the processor and the memory may be further integrated together.

[0027] In a possible implementation, the communication device further comprises a transceiver, the transceiver being configured to receive or transmit signals, for example the transceiver may be further configured to receive A-MPDUs or the like.

[0028] In this embodiment of the application, the communication device may be a transmitter, a chip within a transmitter, and so on.

[0029] According to a sixth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to execute the method as set forth in the second aspect or any one of the possible implementations of the second aspect. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method as set forth in the second aspect or any one of the possible implementations of the second aspect is executed.

[0030] In a possible implementation, the memory is located external to the communication device.

[0031] In a possible implementation, the memory is located within the communication device.

[0032] In this embodiment of the application, the processor and the memory may be further integrated into one component, in other words, the processor and the memory may be further integrated together.

[0033] In a possible implementation, the communication device further includes a transceiver, the transceiver being configured to receive signals or to transmit signals, for example the transceiver may be configured to transmit A-MPDUs.

[0034] In this embodiment of the application, the communication device may be a receiver, a chip within a receiver, and so on.

[0035] According to a seventh aspect, an embodiment of the present application provides a communication device, the communication device including a logic circuit and an interface, the logic circuit coupled to the interface, the interface configured to input a first A-MPDU, and the logic circuit configured to refresh a local scoreboard context based on the first A-MPDU.

[0036] Optionally, the interface is further configured to output a BA frame.

[0037] Optionally, the communication device further includes a memory configured to store any one or more of a third scoreboard context control action through a tenth scoreboard context control action.

[0038] According to an eighth aspect, an embodiment of the present application provides a communication device, the communication device including a logic circuit and an interface, the logic circuit being coupled to the interface, the logic circuit being configured to generate a first A-MPDU, and the interface being configured to output the first A-MPDU.

[0039] In some other embodiments of the present application, the interface is configured to output a second A-MPDU, where the second A-MPDU includes the indication information.

[0040] According to a ninth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium is configured to store a computer program, which, when executed on a computer, enables the method as set forth in the first aspect or any one of the possible implementations of the first aspect to be performed.

[0041] According to a tenth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium is configured to store a computer program, which, when executed on a computer, enables the method shown in the second aspect or any one of the possible implementations of the second aspect to be performed.

[0042] According to an eleventh aspect, an embodiment of the present application provides a computer program product. The computer program product includes a computer program or computer code. When the computer program product is executed on a computer, the method as shown in the first aspect or any one of the possible implementations of the first aspect is enabled to be executed.

[0043] According to a twelfth aspect, an embodiment of the present application provides a computer program product, the computer program product comprising a computer program or computer code, which, when executed on a computer, enables the method as set forth in the second aspect or any one of the possible implementations of the second aspect to be performed.

[0044] According to a thirteenth aspect, an embodiment of the present application provides a computer program, which, when run on a computer, performs the method as set forth in the first aspect or any one of the possible implementations of the first aspect.

[0045] According to a fourteenth aspect, an embodiment of the present application provides a computer program which, when run on a computer, performs the method as set forth in the second aspect or any one of the possible implementations of the second aspect.

[0046] According to a fifteenth aspect, an embodiment of the present application provides a wireless communication system. The wireless communication system includes a transmitter and a receiver. The transmitter is configured to perform a method as shown in the first aspect or any one of the possible implementations of the first aspect. The receiver is configured to perform a method as shown in the second aspect or any one of the possible implementations of the second aspect.

[0047] WinStart in the first to fifteenth aspects R ≦SN <WinStart R +2 11 WinSize R= 1024 as an example. R Alternatively, it may be 64, 128, 256 or 512. Therefore, the WinStart R ≦SN <WinStart R +2 11 Alternatively, use WinStart R ≦SN <WinStart R +2*WinSize R These are not listed one by one here. [Brief description of the drawings]

[0048] [Figure 1a] FIG. 2 is a schematic diagram of a multi-link communication scenario according to an embodiment of the present application; [Figure 1b] FIG. 2 is a schematic diagram of a multi-link communication scenario according to an embodiment of the present application; [Figure 1c] FIG. 2 is a schematic diagram of a multi-link communication scenario according to an embodiment of the present application; [Diagram 2] 1 is a schematic flowchart of a multi-link communication method according to an embodiment of the present application; [Figure 3a] FIG. 2 is a schematic diagram of a scoreboard context control operation according to an embodiment of the present application. [Figure 3b] FIG. 2 is a schematic diagram of a scoreboard context control operation according to an embodiment of the present application. [Figure 3c] FIG. 2 is a schematic diagram of a scoreboard context control operation according to an embodiment of the present application. [Figure 3d] FIG. 2 is a schematic diagram of a scoreboard context control operation according to an embodiment of the present application. [Figure 3e] FIG. 2 is a schematic diagram of a scoreboard context control operation according to an embodiment of the present application. [Figure 3f] FIG. 2 is a schematic diagram of a scoreboard context control operation according to an embodiment of the present application. [Figure 4]1 is a schematic flowchart of a multi-link communication method according to an embodiment of the present application; [Diagram 5] 4 is a schematic flowchart of another multi-link communication method according to an embodiment of the present application. [Figure 6a] 1 is a schematic diagram of an MPDU subframe structure according to an embodiment of this application; [Figure 6b] FIG. 2 is a schematic diagram of an aggregation control field format according to an embodiment of the present application. [Figure 6c] FIG. 2 is a schematic diagram of an aggregation control field format according to an embodiment of the present application. [Figure 6d] FIG. 2 is a schematic diagram of a frame structure of command and status type control information according to an embodiment of the present application; [Figure 7] 1 is a schematic diagram of the structure of a communication device according to an embodiment of this application; [Figure 8] 1 is a schematic diagram of the structure of a communication device according to an embodiment of this application; [Figure 9] 1 is a schematic diagram of the structure of a communication device according to an embodiment of this application; [Figure 10a] FIG. 2 is a schematic diagram of a scoreboard context control operation according to an embodiment of the present application. [Figure 10b] FIG. 2 is a schematic diagram of a scoreboard context control operation according to an embodiment of the present application. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0049] In order to make the objectives, technical solutions and advantages of this application clearer, the following further describes this application in detail with reference to the accompanying drawings.

[0050] In the specification, claims and accompanying drawings of this application, terms such as "first", "second", etc. are merely intended to distinguish between different objects and do not indicate a particular order. Furthermore, the terms "comprise", "have", and any other variations thereof are intended to cover a non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the recited steps or units, but optionally further includes unrecited steps or units, or optionally further includes other steps or units inherent to the process, method, product or device.

[0051] An "embodiment" referred to in this specification means that a particular feature, structure, or characteristic described with reference to the embodiment may be included in at least one embodiment of this application. The terms appearing in various places in this specification do not necessarily refer to the same embodiment, nor do they refer to an embodiment that is separate or optional, exclusive of other embodiments. Those skilled in the art may understand that the embodiments described in this application may be combined with other embodiments, both in an explicit and implicit manner.

[0052] In this application, "at least one" means one or more, "multiple" means two or more, and "at least two" means two or more (including three). The term "and / or" is used to describe an association relationship to describe related objects, and indicates that three relationships may exist. For example, "A and / or B" may represent three cases: only A is present, only B is present, and both A and B are present, where A and B may be singular or plural. The character " / " generally indicates an "or" relationship between related objects. "At least one of the following items" or similar expressions indicate any combination of these items. For example, at least one of a, b, or c may represent a, b, c, "a and b," "a and c," "b and c," or "a, b, and c."

[0053] The multi-link communication method provided in this application may be applied to a wireless communication system. The wireless communication system may include a WLAN, a cellular network, etc. The method may be implemented by a communication device in the wireless communication system, a logic circuit or a processor in the communication device, etc. The communication device may be a wireless communication device that supports parallel transmission on multiple links, for example, called a multi-link device (MLD) or a multi-band device. For example, in a wireless local area network, the communication device supports communication by using a protocol of the IEEE 802.11 series. The protocols of the IEEE 802.11 series include 802.11be, next generation 802.11be, 802.11ax, 802.11a / b / g / n / ac, etc., which are not listed one by one here.

[0054] First, the multilink device in this application will be described below.

[0055] The central idea of ​​multi-link communication is that a WLAN device supporting the IEEE 802.11 standard, for example, an EHT device, can transmit and / or receive on multiple frequency bands, so that a larger bandwidth is available for transmission, thereby improving throughput. For example, the multiple frequency bands mainly include, but are not limited to, the 2.4 GHz Wi-Fi frequency band, the 5 GHz Wi-Fi frequency band, or the 6 GHz Wi-Fi frequency band. For example, the access and / or transmission on each frequency band is called one link, and therefore the access and / or transmission on multiple frequency bands is called multiple links. For example, a device supporting multi-link communication is called a multi-link device (MLD). Figure 1a is a schematic diagram of a multi-link communication scenario according to an embodiment of this application. For example, there are multiple access points (AP) or stations (STA) on an MLD device, forming an AP multi-link device (AP MLD) or a non-AP multi-link device (non-AP MLD). The communication between MDLs is a multi-link communication. In Figure 1a, Link 1 and Link 2 form a multi-link.

[0056] A multilink device includes one or more affiliated stations. An affiliated station is a logical station and may operate on a link, a frequency band, a channel, etc. An affiliated station may be an access point (AP) or a non-access point station (non-AP STA). In general, a multilink device whose affiliated station is an AP may be referred to as an AP multilink, an AP multilink device, or an AP MLD. A multilink device whose affiliated station is a non-AP STA may be referred to as a multilink STA, a multilink STA device, or an STA multilink device. Alternatively, a multilink device whose affiliated station is a non-AP STA may be referred to as a multilink non-AP, a multilink non-AP device, a non-AP MLD, etc. In the following, a multilink device whose affiliated station is an AP is referred to as an AP MLD, and a multilink device whose affiliated station is a non-AP STA is referred to as a non-AP MLD. An AP MLD has one or more affiliated APs, and a STA MLD has one or more affiliated STAs.

[0057] A multi-link device may implement wireless communication in accordance with an 802.11 series of protocols, such as an extremely high throughput (EHT)-compliant multi-link device or an 802.11be-compliant or 802.11be-compatible multi-link device, to communicate with other devices.

[0058] A multilink device (which may be a non-AP MLD or an AP MLD) is a communication device having a wireless communication function. The communication device may be a device, or may be a chip, a processing system, etc. installed in the device. A device in which a chip or a processing system is installed may realize the method and functions in the embodiments of this application under the control of the chip or the processing system. For example, the multilink device in the embodiments of this application may have a wireless transceiver function, support 802.11 series protocols, and may communicate with an AP multilink device or a non-AP multilink device. For example, a non-AP multilink device is any user communication device that allows a user to communicate with an AP and thus communicate with a WLAN. For example, a non-AP multilink device may be a user equipment that can access a network, such as a tablet computer, a desktop computer, a laptop computer, a notebook computer, an ultra-mobile personal computer (UMPC), a handheld computer, a netbook, a personal digital assistant (PDA), or a mobile phone, or may be an Internet of Things node in the Internet of Things, an in-vehicle communication device in the Internet of Vehicles, etc. Alternatively, the non-AP multilink device may be a chip and processing system in the above terminal. The AP multilink device may be a device that provides services to the non-AP multilink device, and may support 802.11 series protocols. For example, the AP multilink device may be a communication entity such as a communication server, a router, a switch, or a network bridge. Alternatively, the AP multilink device may include various types of macro base stations, micro base stations, relay stations, etc. Obviously, the AP multilink device may also be a chip and processing system in various types of devices. The 802.11 protocol may be a protocol that supports 802.11be or is compatible with 802.11be.

[0059] It can be understood that the multi-link device (which may be non-AP MLD or AP MLD) may support high-rate and low-latency transmission. With the continuous development of application scenarios of wireless local area networks, the multi-link device may be further applied to more scenarios, such as serving as a sensor node (e.g., smart water meter, smart electric meter or smart air detection node) in a smart city, a smart device (e.g., smart camera, projector, display screen, TV, stereo, refrigerator or washing machine) in a smart home, a node in the Internet of Things, an entertainment terminal (e.g., AR, VR or other wearable device), a smart device (e.g., printer or projector) in a smart office, an Internet of Vehicles device in the Internet of Vehicles, or an infrastructure (e.g., vending machine, self-service navigation console, self-checkout device or self-service food machine) in daily life scenarios. The specific form of the multi-link device is not limited in this embodiment of this application. This is merely an example for the purpose of explanation here.

[0060] Referring to the above multi-link device, Fig. 1b is a schematic diagram of a multi-link communication scenario according to an embodiment of this application. As shown in Fig. 1b, the AP MLD includes AP1, AP2, ... and APn, and the non-AP MLD includes STA1, STA2, ... and APn, where n is a positive integer. The AP MLD and the non-AP MLD may communicate in parallel through link 1, link 2, ... and link n. STA1 in the non-AP MLD establishes an association relationship with AP1 in the AP MLD, STA2 in the non-AP MLD establishes an association relationship with AP2 in the AP MLD, and STAn in the non-AP MLD establishes an association relationship with APn in the AP MLD, and so on. Thus, communication may be performed after the association relationship between one or more STAs in the non-AP MLD and one or more APs in the AP MLD is established.

[0061] Fig. 1c is a schematic diagram of a multi-link communication scenario according to an embodiment of this application. As shown in Fig. 1c, at least one AP and at least one STA are included. Fig. 1c shows two STAs, for example, STA1 and STA2, and one non-AP MLD. For example, the non-AP MLD may communicate with the AP through two links, and the non-AP MLD includes two cooperating STAs that are not shown in Fig. 1c. In another example, STA2 or STA3 may communicate with the AP through one link. Specifically, the system shown in Fig. 1c includes both multi-link communication and single-link communication.

[0062] The methods provided in this application may be applicable to, but are not limited to, single-user uplink / downlink transmission, multi-user uplink / downlink transmission, vehicle-to-everything (V2X, where X can represent anything), and device-to-device (D2D). For example, V2X may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), vehicle-to-network (V2N), etc.

[0063] The sender shown below in this application can be understood as an MLD for sending data by using a block acknowledgement (BA) mechanism. The sender may also be called an originator MLD, and the party receiving the data is called a receiver. The receiver may also be called a recipient MLD. For example, the sender may be a non-AP MLD, and the receiver may be an AP MLD. In another example, the sender may be an AP MLD, and the receiver may be a non-AP MLD. There may be multiple links between the sender and the receiver. Each link is used for communication between a STA affiliated with the originator MLD and a STA affiliated with the recipient MLD.

[0064] Figure 2 is a schematic flowchart of a multi-link communication method according to an embodiment of this application. The multi-link communication method is realized based on a block acknowledgement (BA) mechanism. The BA mechanism may aggregate multiple "acknowledgements" into one frame, thereby improving channel efficiency. As shown in Figure 2, the method includes the following steps:

[0065] 201: The transmitter sends a block acknowledgement add (ADDBA) request frame to the receiver. In response, the receiver receives an ADDBA request frame.

[0066] 202: The receiver transmits an ADDBA response frame to the transmitter. In response, the transmitter receives the ADDBA response frame.

[0067] Through the above steps 201 and 202, this may also be referred to as successfully establishing a BA protocol, successfully establishing a BA mechanism, or successfully establishing a BA session between the sender and the receiver.

[0068] 203: The transmitter sends an aggregate medium access control protocol data unit (A-MPDU) to the receiver. In response, the receiver receives the A-MPDU.

[0069] It can be understood that when the transmitter needs to send multiple media access control (MAC) protocol data units (MPDUs) to the receiver based on the BA session established between the transmitter and the receiver, the transmitter may convert the multiple MPDUs into one A-MPDU through aggregation. In other words, after receiving the A-MPDU, the receiver performs deaggregation control on the A-MPDU to obtain the multiple MPDUs. For example, each MPDU in the A-MPDU has a sequence number (SN), and the SN indicates the sequence of each MPDU in the A-MPDU.

[0070] For example, the maximum number of MPDUs included in one A-MPDU may be 1024. For example, the scoreboard window size may be changed and may be determined through negotiation in the interaction between the ADDBA request frame and the ADDBA response frame. For example, the scoreboard window size may be 64, 128, 256, 512, 1024, etc. Data aggregated by one A-MPDU may not exceed the scoreboard window size, but may be smaller than the scoreboard window size.

[0071] 204: The transmitter sends a BA request (BAR) frame to the receiver. In response, the receiver receives the BAR frame.

[0072] It can be understood that step 204 is illustrated by using an example in which a transmitter sends a BA request frame. Optionally, the transmitter may further set an ACK policy in the transmitted A-MPDU to implicit BAR. Thus, the transmitter may not need to send a BAR frame separately.

[0073] 205: The receiver sends a BA frame to the transmitter based on the BAR frame, and the BA frame is used to acknowledge the reception status of the MPDU in the A-MPDU. Correspondingly, the transmitter receives the BA frame.

[0074] In general, a receiver needs to maintain a block acknowledgement record (BA record). The BA record contains a bitmap indexed by sequence number and a 12-bit unsigned integer starting sequence number (WinStart), which may indicate the lowest sequence number position in the bitmap. R (which may be represented by,WinEnd,), and the highest sequence number in the current transmission window (WinEnd, R (may be represented by, for example, WinSize R For ease of explanation, the following describes the receiver scoreboard with three parameter definitions: WinStart R , WinSize R and WinEnd R The method provided in the embodiment of this application will be described using examples including WinStart R represents the starting sequence number of the scoreboard, and WinSize R represents the scoreboard window size (e.g., it could be 1024), and WinEnd R represents the end sequence number of the scoreboard (the current end sequence number of the scoreboard).

[0075] For example, after obtaining multiple MPDUs based on the A-MPDU, the receiver performs a scoreboard context control operation for each MPDU. After the score is recorded, the received MPDUs are delivered to a receive reordering buffer, where the MPDUs are sorted based on the sequence of SN, and the correctly received MPDUs are delivered to the upper layer. If an incorrectly received MPDU appears in the reordering process, the SN corresponding to the MPDU is sent to the WinStart B and all MPDUs that are correctly received in sequence and that are before the MPDU corresponding to the SN are delivered to the upper layer. For MPDUs after the SN, the receiver can deliver the correctly received MPDUs and MPDUs after the SN to the upper layer only after it has received the MPDU corresponding to the SN.

[0076] Fig. 3f is a schematic diagram of a scoreboard context control operation according to an embodiment of this application. For example, as shown in Fig. 3f, after de-aggregating one A-MPDU, the receiver obtains four MPDUs with SN: 102, 103, 105 and 100. In this case, the receiver may record 1 in the bit position corresponding to the SN in the scoreboard context, where "1" indicates that the MPDU corresponding to the SN is correctly received, and a bitmap is formed based on the scoring result, and the bitmap is placed in the BA frame as the corresponding acknowledgement of the A-MPDU. In Fig. 3f, the WinStart R =98, and WinSize R =12, WinEnd R =109.

[0077] The sequence number space of a BA record may contain 4096 SNs, and the scoreboard window may be moved within the sequence number space. When a BA session is established, the scoreboard may be initialized. For example, WinStart RThe WinEnd may be set to the start sequence number (SSN) provided by the ADDBA request frame. When an MPDU arrives, if the SN of the MPDU falls within the space represented by the scoreboard, the receiver uses the SN to index the scoreboard and records correct receipt of the MPDU. If the SN is outside the space represented by the scoreboard but R ~WinStart R +2 11 (within half of the sequence number space), the receiver moves the scoreboard window to the right (this is called the WinEnd R WinEnd to make it equal to SN R When a BAR frame arrives, the scoreboard window is moved to the right, so that the WinStart R is equal to the SSN provided by the BAR frame, and a BA frame is replied with the recorded contents of the scoreboard.

[0078] For example, when receiving an MPDU with SN, the receiver checks whether the MPDU has a corresponding scoreboard record for a BA session. A BA session is identified by a transmitter address (TA) and a TID. If no scoreboard record exists, the receiver may create a scoreboard for the BA session and reuse the memory of other sessions.

[0079] It should be noted that in the multi-link communication scenario shown in the embodiment of this application, each link between the transmitter and the receiver maintains its own scoreboard context control, and there exists an MLD common scoreboard. Devices on each link (e.g., each STA in the MLD, or each AP in the MLD) use their own scoreboard context control to feedback the reception status of MPDUs on the link. The common scoreboard records parameter information of the scoreboards on other links, such as the start sequence number and / or end sequence number of the scoreboards on each link, or information that aggregates the scoreboards of all links (e.g., WinStart B ) may be used to record

[0080] Below, the methods provided in the embodiments of this application are described with reference to specific scoreboard context control operations.

[0081] For example, the SN ranges from 0 to 4095. When the SN is 4095, if the SN is increased by 1, the value of 4096 becomes 0. Therefore, the numerical values ​​of the SN in the examples given below in this application are obtained by performing modulo arithmetic on 4096. For example, the receiver may perform arithmetic on the SN by using modulo 4096, and each of the SN spaces may be represented by a modulo 4096 counter.

[0082] In the schematic diagram shown in Figure 3a-3c, the transmitter may communicate with the receiver through two links, for example, a first link and a second link. For ease of explanation, hereinafter, the STA associated with the receiver and on the first link is referred to as the first STA, and the STA associated with the receiver and on the second link is referred to as the second STA. In other words, the first STA and the second STA are associated with the same MLD.

[0083] First type of scoreboard context control behavior: The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R +2 11 ≦SN <WinStart R Meet WinStart B +2 11 ≦SN <WinStart B Receiving an MPDU with an SN that does not satisfy If is true, then STA is WinEnd R <SN<WinStart R +2 11 The STA may update its scoreboard context as if an MPDU having a SN satisfying:

[0084] FIG. 3a is a schematic diagram of a scoreboard context control operation according to an embodiment of this application. For example, the same TID corresponds to four A-MPDUs, and the aggregate length of each A-MPDU is 1024, in other words, each A-MPDU contains 1024 MPDUs, and the acknowledgement policy of each A-MPDU is immediate block acknowledgement. A first STA receives a first A-MPDU (e.g., A-MPDU1 shown in FIG. 3a) with a SN of 0-1023. A second STA receives a second A-MPDU (e.g., A-MPDU2 shown in FIG. 3a) with a SN of 1024-2047, and a third A-MPDU (e.g., A-MPDU3 shown in FIG. 3a) with a SN of 2048-3071. A first STA receives a fourth A-MPDU (e.g., A-MPDU4 shown in FIG. 3a) with a SN of 3072-4095. It can be understood that the description of the relationship between the A-MPDU and the SN shown in Fig. 3b can be referred to Fig. 3a, and the details will not be described one by one below.

[0085] After the first STA updates the scoreboard context of the first STA based on the SN of the first A-MPDU, the scoreboard of the first STA (which may be referred to as the scoreboard of the first link) displays WinStart R =0 and WinEnd R = 1023. After the second STA updates the scoreboard context of the second STA based on the SN of the second A-MPDU and the SN of the third A-MPDU, the scoreboard of the second STA (which may be referred to as the scoreboard of the second link) shows WinStart R = 2048, WinEnd R = 3071. Furthermore, in the scoreboard of the first STA and the scoreboard of the second STA, B =3072.

[0086] According to the first type scoreboard context control operation, when the SN of the fourth A-MPDU received by the first STA satisfies 0+2048≦SN<0 and the SN does not satisfy 1024 (obtained by performing a modulo operation on the sum of 3072 and 2048 based on 4096)≦SN<3072, the first STA may update the scoreboard context of the first STA based on the SN of the fourth A-MPDU. Since the SN of the fourth A-MPDU is 3072 to 4095, if the first STA successfully receives all MPDUs in the fourth A-MPDU, the scoreboard of the first STA may update the scoreboard context of the first STA based on the WinStart R =3072 and WinEnd R =4095.

[0087] However, when the A-MPDUs received by the first STA and the second STA are as shown in Figure 3b, when the first STA receives the fifth A-MPDU (A-MPDU5 shown in Figure 3b) having a SN from 0 to 1023 based on the first type of scoreboard context control operation, the first STA cannot correctly feed back the reception status of all MPDUs in the fifth A-MPDU.

[0088] To solve the above problem, the embodiment of this application further provides a second type of scoreboard context control operation. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinEnd R receiving an MPDU having an SN that satisfies Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B The MPDU with SN satisfying If is true, then A STA may refresh (or flush) and update the STA's scoreboard context.

[0089] The receiving MLD shown above has separate scoreboard context control on each link, which can also be understood as each STA associated with the receiving MLD maintaining its own scoreboard context control.

[0090] It should be noted that in this embodiment of this application, a STA refreshing its scoreboard context means that the STA initializes its scoreboard context, zeroes its scoreboard context, clears the contents already recorded in the scoreboard context, clears the cache of the scoreboard context, etc. Updating a STA's scoreboard context means that the STA may perform updates based on the existing contents in the scoreboard context.

[0091] FIG. 3b is used as an example. The SN of the fifth A-MPDU received by the first STA satisfies 0≦SN<1023. The SN of the MPDU received by the scoreboard context of the second STA (i.e., the scoreboard of the other STA) satisfies 3072≦SN<4096. Therefore, the first STA may refresh the scoreboard of the first STA and update the scoreboard context of the first STA. In other words, the first STA may clear the record before receiving the fifth A-MPDU and update the scoreboard context initialized by using the SN of the fifth A-MPDU. Therefore, when the first STA successfully receives all MPDUs in the fifth A-MPDU, the scoreboard of the first STA may refresh the scoreboard of the first STA and update the scoreboard context of the first STA. R =0 and WinEnd R =1023 will be refreshed and updated.

[0092] In yet another scenario, when the A-MPDUs received by the first STA and the second STA are as shown in FIG. 3c, the WinStart R =0 and WinEnd R = 1023. When the receiver receives the sixth A-MPDU, the SN is between 1024 and 1500, so the SN of the sixth A-MPDU does not belong to the above first type of scoreboard context control operation, nor does it belong to the above second type of scoreboard context control operation. Therefore, the first STA cannot know how to update the scoreboard context of the first STA. This can also be understood as follows: When the receiver receives the sixth A-MPDU, the SN of the MPDU received by the first STA is between WinEnd R ≦SN <WinStart R +2 11 If the scoreboard of the first STA falls within the range of WinEnd, it is not considered in the second type of scoreboard context control operation described above. Ris moved directly to the 1500 position, and WinStart R is 477 (ie, 1500-1023), when the BA frame is fed back, the state information of 477 to 1023 in the previous round is erroneously fed back.

[0093] To solve the above problems, an embodiment of this application provides a third type of scoreboard context control operation. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2 11 receiving an MPDU having an SN that satisfies Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B The MPDU with SN satisfying If is true, then A STA may refresh and update its scoreboard context (if the following conditions are true: a recipient MLD has a separate scoreboard context control in each link; the STA affiliated with the MLD is capable of using reordering buffer information to update its scoreboard context; a STA affiliated with the MLD receives a frame with SN that is WinStartR≦SN <WinStartR+211; the other STA affiliated with the MLD receives a frame with SN that is WinStartB-WinSizeR≦SN<WinStartB; the STA shall flush the scoreboard context and update the scoreboard context.)。

[0094] Based on the above third type of scoreboard context control operation, for example, FIG. 3c is used as an example, and before the first STA does not receive the sixth A-MPDU, the first STA has a scoreboard context that is set to WinStart R =0 and WinEnd R When the first STA receives the sixth A-MPDU, the SN of the sixth A-MPDU is 0≦SN<0+2. 11 Therefore, the SN of the A-MPDU already received by another STA (the second STA shown in Figure 3c) is equal to or smaller than WinStart B -WinSize R ≦SN <WinStart B (WinStart B= 1024). Therefore, the first STA may refresh the scoreboard context of the first STA and update the scoreboard context. In the updated scoreboard context, R =477, WinEnd R =1500.

[0095] In combination with the above first type scoreboard context control operation and second type scoreboard context control operation, the STA associated with the receiving MLD may refresh the scoreboard context every time an MPDU is acquired. This method has a problem of inappropriately flushing the local scoreboard.

[0096] Suppose a STA receives an A-MPDU. The A-MPDU includes a first MPDU and a second MPDU, and the local scoreboard context may be flushed once based on the SN of the first MPDU. When the local scoreboard context is flushed based on the second MPDU, the scoreboard context of the BA frame that is not fed back, which is related to the SN of the first MPDU, is flushed. After the STA flushes the local scoreboard context based on the SN1 of the first MPDU, the STA does not feed back the BA frame. In this case, when the local scoreboard context is next flushed based on the second MPDU, the STA cannot feed back the BA frame correctly.

[0097] To solve the above problems, an embodiment of this application provides a fourth type of scoreboard context control operation. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStartR ≦SN <WinEnd R receiving an MPDU having an SN that satisfies Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B and receiving an MPDU having an SN that satisfies Either there is no other frame with an SN in current A-MPDU that already fulfills all above conditions, or it is the first frame with an SN in current A-MPDU that fulfills all above conditions, or the scoreboard of the STA is not flushed based on a frame in current A-MPDU. If is true, then A STA may refresh and update its scoreboard context (if the following conditions are true: a recipient MLD has a separate scoreboard context control in each link, the STA affiliated with the MLD is capable of using reordering buffer information to update its scoreboard context; a STA affiliated with the MLD receives a frame with SN that is WinStart R ≦SN <WinEnd R; the other STA affiliated with the MLD receives a frame with SN that is WinStart B -WinSize R ≦SN <WinStart B ; no other frame with an SN in current A-MPDU that already fulfills all above conditions; the STA shall flush the scoreboard context and update the scoreboard context.).

[0098] In other words, in the fourth type of scoreboard context control operation, the receiver acquires an A-MPDU, the multiple MPDUs contained in the A-MPDU are all transmitted to the STA, and the SNs of the multiple MPDUs are all WinStart R ≦SN <WinEnd R When all conditions are satisfied, the STA may refresh its scoreboard context based on the SN of the first MPDU in the A-MPDU that satisfies all conditions except the last condition. It may also be said that the STA cannot refresh its scoreboard context based on the SN of an MPDU that is not the first in the A-MPDU that satisfies all conditions except the last condition.

[0099] The schematic diagram shown in FIG. 3d is used as an example. After the first STA receives two A-MPDUs with SNs of 500-1023 and two A-MPDUs with SNs of 0-499, the first STA performs flushing twice separately because both of the two A-MPDUs satisfy the above second type of scoreboard context control operation. For example, when the local scoreboard context is flushed after the A-MPDUs with SNs of 0-499 are received, the BA records of the unreplied BA frames with SNs of 500-1023 are also flushed. It can be understood that the first ACK policy shown in FIG. 3d indicates that the first STA does not need to feed back the BA frame temporarily, and the second ACK policy shown in FIG. 3d (which may be called implicit BAR) indicates that the first STA needs to feed back the BA frame.

[0100] To solve the above problem, the embodiment of this application further provides a fifth type of scoreboard context control operation. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinEnd R receiving an MPDU having an SN that satisfies Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B and receiving an MPDU having an SN that satisfies no frame that is carried in any A-MPDU that received before current A-MPDU is not responded by a BA; or all frames that are carried in the A-MPDUs that received before current A-MPDU has been responded by BAs. If is true, then A STA may refresh and update its scoreboard context (If the following conditions are true: a recipient MLD has a separate scoreboard context control in each link, the STA affiliated with the MLD is capable of using reordering buffer information to update its scoreboard context. A STA affiliated with the MLD receives a frame with SN that is WinStart R ≦SN <WinEnd R ; the other STA affiliated with the MLD receives a frame with SN that is WinStart B -WinSize R ≦SN <WinStart B; no any frame that is carried in any A-MPDU that received before current A-MPDU is not responded by a BA; the STA shall flush the scoreboard context and update the scoreboard context.).

[0101] In other words, in the fifth type of scoreboard context control operation, when a STA receives two A-MPDUs consecutively, and the SN of the MPDU in the first A-MPDU is WinStart R ≦SN <WinEnd R When the STA does not feed back the BA frame of the first A-MPDU, even if the SN of the MPDU in the second A-MPDU meets the above condition, the STA does not refresh the scoreboard context of the STA, but may update the scoreboard context of the STA.

[0102] The schematic diagram shown in Fig. 3e is used as an example. After the first STA receives an A-MPDU with a SN of 200-299, the A-MPDU satisfies the above second type of scoreboard context control operation, and the scoreboard context in the first STA is refreshed. However, in the scenario shown in Fig. 3e, according to the SN relationship between the first A-MPDU, the third A-MPDU, and the fourth A-MPDU, the first STA does not need to perform flushing.

[0103] To solve the above problems, an embodiment of this application provides a sixth type of scoreboard context control operation. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinEnd R receiving an MPDU having an SN that satisfies WinStart B -WinSize R ≦SN <WinStart B No MPDU with SN that is WinStart is received by the STA (none of a frame with SN that is WinStart B -WinSize R ≦SN <WinStart B is (was) received by the STA), or WinStart B -WinSize R ≦SN <WinStart B All frames with SN that are WinStart B -WinSize R ≦SN <WinStart B are (were) received by the other STA(s), where WinStart B -WinSize R ≦SN <WinStart B The MPDU with SN that satisfies the WinStart B SN is WinStart B -WinSize R ≦SN <WinStart B It should be noted that the range satisfying (i) is not considered, but the MPDU is the MPDU received in the previous round or earlier in the reordering buffer. If is true, then A STA may refresh and update its scoreboard context (if the following conditions are true: a recipient MLD has a separate scoreboard context control in each link, the STA affiliated with the MLD is capable of using reordering buffer information to update its scoreboard context; a STA affiliated with the MLD receives a frame with SN that is WinStart R ≦SN <WinEnd R ; none of a frame with SN that is WinStart B -WinSize R ≦SN <WinStart B is (was) received by the STA; the STA shall flush the scoreboard context and update the scoreboard context.).

[0104] In other words, in the sixth type of scoreboard context control operation, the STA R ≦SN <WinEnd R and receiving an A-MPDU having a SN that satisfies B -WinSize R ≦SN <WinStart B When an MPDU having a SN that satisfies SN ≠ 0 is not received by a STA, the STA may refresh the STA's scoreboard context.

[0105] FIG. 3e is used as an example. Before the first STA does not receive the second A-MPDU and the third A-MPDU, the WinStart R=199-1023+4096=3272, and WinEnd R =199 and WinStart B = 200. When the first STA receives the third A-MPDU, the SN of the third A-MPDU is between 300 and 399, and the above condition is not met, so the scoreboard context of the first STA is not updated. The same applies to the fourth A-MPDU. It is not enumerated one by one.

[0106] It may be understood that the above scoreboard context control actions of the third type to the sixth type may be realized separately or may be combined with each other. For example, the scoreboard context control action of the third type and the scoreboard context control action of the fourth type may be combined to obtain, for example, a scoreboard context control action of the seventh type. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2 11 receiving an MPDU having an SN that satisfies Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B and receiving an MPDU having an SN that satisfies Either another MPDU with the SN in the currently received A-MPDU has not yet satisfied all the above conditions, or the one that satisfies all the above conditions is the first MPDU with the SN in the A-MPDU received by the STA, or the scoreboard context of the STA has not been refreshed based on the MPDU in the currently received A-MPDU. If is true, then The STA may refresh and update the STA's scoreboard context.

[0107] Thus, the seventh type of scoreboard context control operation can solve both the problem shown in FIG. 3c above and the problem of refreshing the scoreboard context for each MPDU shown above.

[0108] For example, a scoreboard contextual control action of the third type and a scoreboard contextual control action of the fifth type may be combined to obtain, for example, a scoreboard contextual control action of an eighth type. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2 11 receiving an MPDU having an SN that satisfies Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B and receiving an MPDU having an SN that satisfies No MPDU in any other A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, no MPDU in any A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, or all MPDUs carried in any A-MPDU received before the currently received A-MPDU have been acknowledged by the BA. If is true, then The STA may refresh and update the STA's scoreboard context.

[0109] In this way, the eighth type of scoreboard context control action can solve the problems illustrated in Figures 3c and 3d above.

[0110] It can be understood that the fourth type scoreboard context control operation and the fifth type scoreboard context control operation shown in this embodiment of the present application may also be combined, and the details will not be described again one by one here.

[0111] For example, a third type scoreboard context control action, a fourth type scoreboard context control action, and a fifth type scoreboard context control action may be combined to obtain, for example, a ninth type scoreboard context control action. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2 11 receiving an MPDU having an SN that satisfies Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B receiving an MPDU having an SN that satisfies Another MPDU having the SN in the currently received A-MPDU has not yet satisfied all the above conditions, or the one that satisfies all the above conditions is the first MPDU having the SN in the currently received A-MPDU received by the STA, or the scoreboard context of the STA has not been refreshed based on the MPDU in the currently received A-MPDU; No MPDU in any other A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, no MPDU in any A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, or all MPDUs carried in any A-MPDU received before the currently received A-MPDU have been acknowledged by the BA. If is true, then The STA may refresh and update the STA's scoreboard context.

[0112] In this way, the ninth type of scoreboard context control action can effectively solve the problems illustrated in Figures 3c and 3d above.

[0113] For example, a third type scoreboard context control action, a fourth type scoreboard context control action, a fifth type scoreboard context control action, and a sixth type scoreboard context control action may be combined to obtain, for example, a tenth type scoreboard context control action. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2 11 receiving an MPDU having an SN that satisfies WinStart B -WinSize R ≦SN <WinStart B If an MPDU with a SN satisfying B -WinSize R ≦SN <WinStart BAn MPDU having an SN that satisfies the following is received by another STA associated with the receiving MLD; no MPDU in any other A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, no MPDU in any A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, or all MPDUs carried in any A-MPDU received before the currently received A-MPDU have been acknowledged by the BA, Here, it can be understood that the sequence of executing the above conditions by the STA is not limited. Either another MPDU with the SN in the currently received A-MPDU has not yet satisfied all the above conditions, or the one that satisfies all the above conditions is the first MPDU with the SN in the A-MPDU received by the STA, or the scoreboard context of the STA has not been refreshed based on the MPDU in the currently received A-MPDU. If is true, then The STA may refresh and update the STA's scoreboard context.

[0114] In this way, the tenth type of scoreboard context control operation can effectively solve the problems illustrated in Figures 3c to 3e above.

[0115] For example, the above tenth type of scoreboard context control action can be further understood as follows. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; A STA associated with the MLD may use the reordering buffer information to update its scoreboard context; STA, which works with MLD, is WinStart R ≦SN <WinStart R +2 11 receiving a frame having a SN which is WinStart B -WinSize R ≦SN <WinStart B None of the frames with SN=1 have been received by the STA (not received), Any frames carried in other A-MPDUs received before the current A-MPDU have not been acknowledged by the BA, There is no other frame with the SN in the current A-MPDU that already satisfies all of the above conditions. If is true, then The STA shall flush the scoreboard context and update the scoreboard context. (if the following conditions are true: a recipient MLD has a separate scoreboard context control in each link; the STA affiliated with the MLD is capable of using reordering buffer information to update its scoreboard context; a STA affiliated with the MLD receives a frame with SN that is WinStart R ≦SN <WinStart R +2 11 ; none of a frame with SN that is WinStart B -WinSize R ≦SN <WinStart B is (was) received by the STA; no any frame that is carried in another A-MPDU that received before current A-MPDU is not responded by a BA; and no other frame with an SN in current A-MPDU that already fulfills all above conditions, the STA shall flush the scoreboard context and update the scoreboard context.).

[0116] It can be understood that Figures 3a to 3e are all illustrated by using an example in which one A-MPDU includes multiple MPDUs and each SN may correspond to one MPDU. It can be understood that in this application, the SNs of the A-MPDUs illustrated above are all illustrated by using an example in which the SNs belong to the same TID.

[0117] With reference to the above third to tenth types of scoreboard context control operations, an embodiment of this application provides a multi-link communication method. For the description of the transmitter and receiver in the method, please refer to the above description. The details will not be described one by one again here. As shown in Figure 4, the multi-link communication method includes the following steps:

[0118] 401: A transmitter transmits a first A-MPDU to a receiver, and the receiver receives the first A-MPDU.

[0119] Optionally, there may be one link between the transmitter and the receiver.

[0120] Optionally, there may be at least two links between the transmitter and the receiver.

[0121] Optionally, the first A-MPDU may include one MPDU. Optionally, the first A-MPDU may include at least two MPDUs.

[0122] It can be understood that the A-MPDU is carried in the PPDU. Generally, for a receiving station, one PPDU carries only one A-MPDU. Therefore, the A-MPDU in this embodiment of the present application can be further understood as a PPDU, which is not limited in this embodiment of the present application.

[0123] 402: The receiver obtains a locally recorded scoreboard context, and refreshes the scoreboard context based on the SN of the first A-MPDU when the first A-MPDU satisfies any one or more of the following conditions:

[0124] It may be understood that the locally recorded scoreboard context in this embodiment of the application may be an initialized scoreboard context, a scoreboard context updated by the receiver based on A-MPDUs received by the receiver before the first A-MPDU is received, a scoreboard context refreshed by the receiver based on A-MPDUs received by the receiver before the first A-MPDU is received, etc., which are not enumerated one by one here.

[0125] The conditions that the first A-MPDU satisfies include the following: First condition: The STA associated with the receiver is WinStart R ≦SN <WinStart R +2 11 Receive an MPDU having an SN that satisfies Second condition: WinStart B -WinSize R ≦SN <WinStart B Any MPDU with a SN satisfying B -WinSize R ≦SN <WinStart B All MPDUs with SNs that satisfy Third condition: no MPDU in any other A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, no MPDU in any A-MPDU received before the first A-MPDU has not been acknowledged by the BA, or all MPDUs carried in any A-MPDU received before the first A-MPDU have been acknowledged by the BA. Fourth condition: another MPDU having the SN in the first A-MPDU has not yet satisfied the above conditions (the above first to third conditions), the MPDU having the SN received by the STA associated with the receiver is the first MPDU in the first A-MPDU that satisfies the above conditions, or the scoreboard context of the STA associated with the receiver has not been refreshed based on the MPDU in the first A-MPDU.

[0126] It can be understood that the sequence in which the STA executes the first to third conditions is not limited to this embodiment of the application.

[0127] Optionally, when the first A-MPDU satisfies any one of the above first to fourth conditions, for other conditions satisfied by the first A-MPDU, refer to the relevant descriptions of the above third type scoreboard context control operation to sixth type scoreboard context control operation.

[0128] Optionally, when the first A-MPDU satisfies any two of the above first to fourth conditions, for other conditions satisfied by the first A-MPDU, refer to the relevant descriptions of the above sixth type scoreboard context control operation to ninth type context control operation.

[0129] Optionally, when the first A-MPDU satisfies the above first to fourth conditions, for other conditions satisfied by the first A-MPDU, refer to the relevant description of the above tenth type scoreboard context control operation.

[0130] It can be understood that the conditions satisfied by the first A-MPDU can be referred to the above description of the third type scoreboard context control operation to the tenth type context control operation, and the details will not be described one by one again here.

[0131] 403: The receiver sends a BA frame to the transmitter, where the BA frame is used to acknowledge the reception status of the MPDU in the first A-MPDU.

[0132] For the description of the ADDBA request frame, the ADDBA response frame and the BAR frame not shown in this embodiment of the present application, it can be understood that the description can be made by referring to Fig. 2 shown above. The details will not be described again one by one here.

[0133] According to the method provided in this embodiment of the present application, the receiver can properly and efficiently refresh the local scoreboard context.

[0134] In the multi-link communication method shown in Fig. 4, the receiver may refresh or update the local scoreboard context based on the third type scoreboard context control operation to the tenth type scoreboard context control operation. An embodiment of this application further provides a multi-link communication method, in which the transmitter may indicate whether the receiver refreshes the local scoreboard context by using the indication information, thereby effectively reducing the complexity of the receiver.

[0135] Figure 5 is a schematic flow chart of another multi-link communication method according to an embodiment of this application. The transmitter and receiver in this method are described above. Details are not described here again one by one. As shown in Figure 5, the multi-link communication method includes the following steps:

[0136] 501: A transmitter sends a second A-MPDU to a receiver, the second A-MPDU including indication information, the indication information instructing the receiver whether to refresh a scoreboard context of the receiver. In response, the receiver receives the second A-MPDU.

[0137] It can be seen that in the method shown in Figure 4, the STAs at the receiver can use the reordering buffer information to update the scoreboard context. In the method shown in Figure 5, the STAs at the receiver may or may not be able to update the scoreboard context by using the reordering buffer information.

[0138] For example, when the indication information is set to 0, it may indicate that the receiver does not need to refresh the local scoreboard context. In another example, when the indication information is set to 1, it may indicate that the receiver needs to refresh the local scoreboard context, or it may implicitly indicate that the receiver is capable of refreshing the local scoreboard context. Generally, the second A-MPDU is transmitted through a link, and the STA that receives the A-MPDU on the link is unique. Therefore, the STA corresponding to the link used to transmit the second A-MPDU may determine whether to refresh the local scoreboard context based on the indication information.

[0139] 6a is a schematic diagram of an MPDU subframe structure according to an embodiment of this application. As shown in FIG. 6a, the indication information may be carried in a reserved field in the MPDU delimiter, or may be carried in a high throughput (HT) control field.

[0140] The HT control field may be carried in MPDUs (e.g., quality of service (QoS) data frames, quality of service null (QoS) frames, and management frames) to carry some control information. The length of the HT control field is 4 bytes. There are three types of HT control fields, which are distinguished by the B0 and B1 bits. As shown in Table 1, when B0=0, the corresponding HT control field is a high throughput (HT) type HT control field. When B0=1 and B1=0, the corresponding HT control field is a very high throughput (VHT) type HT control field. When B0=1 and B1=1, the corresponding HT control field is a high efficiency (HE) type HT control field. [Table 1]

[0141] B2-B31 in the HT control field of HE type are called aggregation control (A-control) subfields. FIG. 6b is a schematic diagram of the format of the aggregation control field according to an embodiment of this application. The aggregation control field includes a control list and a padding part. The bit length of the control list is variable, and the control list may include one or more control subfields. The padding part includes zero or more bits. FIG. 6c is a schematic diagram of the format of the control subfield in the aggregation control field according to an embodiment of this application. One control subfield includes a 4-bit control ID and control information. The control ID is used to identify the control information. The control ID and the corresponding length of the control information are shown in Table 2. [Table 2]

[0142] It may be understood that for the description of other fields shown in Fig. 6a, such as an end of frame (EOF) field, a reversed field, an MPDU length field, a cyclic redundancy check (CRC) field, and a delimiter signature field included in the MPDU delimiter, as well as a frame control field, a duration / ID field, an address 1 field to an address 4 field, a sequence control field, a QoS control field, an HT control field, a padding field, etc. included in the MPDU, reference may be made to related standards or protocols. Details will not be described again one by one here.

[0143] Based on the above description, this embodiment of the application provides two HE types of HT control fields that can carry indication information.

[0144] The first method is to realize the indication information by using a reserved bit in the CAS type control information. The frame structure of the CAS type control information is shown in Fig. 6d. As shown in Fig. 6d, the CAS type control information may include an access category (AC) constraint field, a reverse direct grant (RDG) field, a parameterized spatial reuse transmission (PSRT) PPDU field, and a reserved field. It can be understood that for the relevant description of other fields in Fig. 6d, refer to the relevant standard or protocol. The details will not be described again one by one here.

[0145] The second method is to establish a new control type (as shown in FIG. 6c) by using a currently reserved control ID, and indicate the new control type by using control information of the new control type. For example, the bit length of the indication information may be 1 bit.

[0146] 502: The receiver refreshes the scoreboard context based on the instruction information.

[0147] It may be appreciated that the receiver may alternatively not refresh the scoreboard context based on the indication information, for example, the receiver may update the scoreboard context.

[0148] 503: The receiver transmits a BA frame to the transmitter, and the transmitter receives the BA frame.

[0149] For the description of the ADDBA request frame, the ADDBA response frame and the BAR frame not shown in this embodiment of the present application, it can be understood that the description can be made by referring to Fig. 2 shown above. The details will not be described again one by one here.

[0150] According to the method provided in this embodiment of this application, the transmitter adds indication information to the A-MPDU to instruct the receiver to refresh the scoreboard context, which can effectively reduce the complexity of the receiver and improve the efficiency of refreshing the scoreboard context by the receiver.

[0151] An embodiment of this application further provides a multi-link communication method, in which the STA in the receiver may be able to update the scoreboard context by using the reordering buffer information, or may not be able to update the scoreboard context by using the reordering buffer information.

[0152] In this embodiment of the application, the transmitter includes a first field in the transmitted data frame (i.e., A-MPDU), where the first field indicates a round of transmission of the current SN. The first field may be called a Round of SN subfield, and the initial value of the field is set to 0. When the SN of the data frame is returned to 0 again after exceeding the maximum SN value (4095), the value of the SN round subfield is increased by 1. For example, assuming that the SN round subfield includes 5 bits, the value of the SN round subfield may be 0 to 31. For example, if the value of the SN round subfield is set to 31, the value is returned to 0 when the value is increased by 1.

[0153] Therefore, after receiving a data frame, the receiver satisfies the following conditions: If the local scoreboard context is updated based on the SN of the data frame, the updated local scoreboard context at least partially covers the range before the update; The value of the SN Round subfield is different from the value of the SN Round subfield carried in the last received data frame. is satisfied, the local scoreboard context may be refreshed before updating the local scoreboard context.

[0154] For example, the SN round subfield may be included in the newly created HT control type of the HE type shown in Figure 5 (as shown in Figure 6c, a new control type is newly created by using an unused ID in the first column shown in Table 2). The bit length of the SN round subfield is not limited in this embodiment of the application and may be, for example, 5 bits. For example, the SN round subfield may be carried by using the newly created A-control type, or may be carried in the reserved bits of the CAS control type. For example, see the bearer position of the indication information shown in Figure 5.

[0155] It may be understood that if the length of the SN round subfield is limited (e.g., 5 bits), the original value may be restored after the value is increased 32 times. In this case, the receiver may not be able to determine whether the value of the SN round subfield changes or not. However, if the length of the SN round subfield is long enough, the probability of occurrence of this situation is very low, and this may be ignored as a low-probability event.

[0156] Embodiments of this application further provide certain types of scoreboard context control operations, as described below. If the STA associated with the receiving MLD is not able to use the reordering buffer information to update the STA's scoreboard context and the receiving MLD has separate scoreboard context control on each link, the STA will implement partial state operation (meaning partial state operation of the BA mechanism) and will update the reordering buffer information for the following defined periods: After sending the BA if the BA and the acknowledged A-MPDU are within one transmission opportunity (TXOP), and before processing the scoreboard context of the next QoS data frame associated with the same TID and received from the initiator MLD on the same link; If the BA is not sent at the end of the current TXOP, after the next QoS data frame is received from the initiator MLD on the same link in a new TXOP and before the scoreboard context is updated. If a STA affiliated with a recipient MLD in a link is not capable of using reordering buffer information to update its scoreboard context and the recipient MLD has a separate scoreboard context control in each link, the STA shall implement the partial-state operation and should discard the temporary record in the following defined time periods: After sending a BA where the BA and the acknowledged A-MPDU(s) are in one TXOP and before processing the scoreboard context of the next received the QoS Data frame of the TID from the initiator MLD in the link if BA is transmitted; and immediate before processing the scoreboard context of the next received the QoS Data frame of the TID from the initiator MLD in the link in a new TXOP if BA is not transmitted at the end of the current TXOP.

[0157] In the above embodiments, it can be understood that for implementation methods not described in detail in one embodiment, reference can be made to other embodiments.

[0158] As mentioned above, the scoreboard window size may be 64, 128, 256, 512, 1024, etc. Therefore, the two types of scoreboard context control operations involved in the above third type to tenth type scoreboard context control operations are 11 For example, WinSize R All are shown using =1024.

[0159] When the scoreboard window size is not 1024, the scoreboard context control operation of at least one of the above-mentioned third type to tenth type scoreboard context control operations is performed. 11 may vary accordingly.

[0160] For example, the third type of scoreboard context control operation is used as an example. R≦SN <WinStart R +Q*WinSize R When a frame within the range of Q is received, the frame scoreboard needs to be flushed. For example, Q may be equal to 2, or Q may be equal to 3. For ease of explanation, the following uses Q=2 as an example to explain the method provided in this application.

[0161] When Q=2, WinStart R +2*WinSize R ≦SN <WinStart R +2 11 When the first STA is R and WinEnd R Update the scoreboard (new WinStart R ,WinEnd R ]) range and scoreboard range before update (old [WinStart R ,WinEnd R ]), so records of receiving old data frames are not kept in the scoreboard. In other words, records of old data are not fed back to the transmitting station by using BA.

[0162] When critical points are considered, WinStart R ≦SN <WinStart R +2 11 Also, WinStart R ≦SN <WinStart R +2 11 It can be understood that the following WinStart R ≦SN <WinStart R +2*WinSize R Also, WinStart R ≦SN <WinStart R +2*WinSize R -1 or WinStart R ≦SN <WinEnd R +WinSize RIn other words, when rounding of values, simplicity of formulas, etc. are taken into consideration, the range satisfied by SN in this application may be adjusted based on a specific range (e.g., a range of -2 to +2), which is not listed one by one here.

[0163] For ease of explanation, the following is an example of WinStart R ≦SN <WinStart R +2*WinSize R Use -1.

[0164] Using Q=2 as an example, the third type of scoreboard context control operation can be further understood as follows. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2*WinSize R receiving an MPDU having a SN equal to -1; Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B The MPDU with SN satisfying If is true, then A STA may refresh and update its scoreboard context (if the following conditions are true: a recipient MLD has a separate scoreboard context control in each link; the STA affiliated with the MLD is capable of using reordering buffer information to update its scoreboard context; a STA affiliated with the MLD receives a frame with SN that is WinStart R <=SN< WinEnd R +WinSize R ; the other STA affiliated with the MLD receives a frame with SN that is WinStart B -WinSize R ≦SN <WinStart B ; the STA shall flush the scoreboard context and update the scoreboard context.).

[0165] For the third type of context control operation, Figure 10a shows the WinSize R = 256 is used as an example procedure. Before the first STA does not receive the sixth A-MPDU (e.g., A-MPDU6 shown in FIG. 10a), the WinStart R =0 and WinEnd R= 255. When the receiver receives the sixth A-MPDU, the SN is between 256 and 400, so the SN of the sixth A-MPDU does not belong to the above first type scoreboard context control operation, nor does it belong to the above second type scoreboard context control operation. Therefore, the first STA cannot know how to update the scoreboard context of the first STA. This can also be understood as follows: When the receiver receives the sixth A-MPDU, the SN of the MPDU received by the first STA is between WinEnd R ≦SN <WinStart R +2*WinSize R If it falls within the range of -1, it is not taken into account in the second type of scoreboard context control operation described above. R is moved directly to the 400 position, and WinStart R is 145 (ie, 400-255), when the BA frame is fed back, the state information of 145 to 255 in the previous round is erroneously fed back.

[0166] However, in FIG. 10b, the first STA does not receive the sixth A-MPDU (e.g., A-MPDU6 shown in FIG. 10b) before the first STA receives the WinStart R =0 and WinEnd R = 255. When the receiver receives the sixth A-MPDU, the SN is between 512 and 767, so the SN of the sixth A-MPDU does not belong to the above first type scoreboard context control operation, nor does it belong to the above second type scoreboard context control operation. Therefore, the first STA cannot know how to update the scoreboard context of the first STA. This can also be understood as follows: When the receiver receives the sixth A-MPDU, the receiver updates the WinEnd of the scoreboard of the first STA. R Move directly to position 767 and WinStart Ris at 512. When the BA frame is fed back, the status information of any frame in the range of 0 to 255 in the previous round is not fed back erroneously. Therefore, the scoreboard does not need to be flushed for the sixth A-MPDU. In the example shown in Figure 10b, it can be understood that the ellipsis omits other A-MPDUs that are not shown.

[0167] Using Q=2 as an example, the seventh type of scoreboard context control operation can be further understood as follows. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2*WinSize R- receiving an MPDU having an SN that satisfies 1; Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B and receiving an MPDU having an SN that satisfies Either another MPDU with the SN in the currently received A-MPDU has not yet satisfied all the above conditions, or the one that satisfies all the above conditions is the first MPDU with the SN in the A-MPDU received by the STA, or the scoreboard context of the STA has not been refreshed based on the MPDU in the currently received A-MPDU. If is true, then The STA may refresh and update the STA's scoreboard context.

[0168] Using Q=2 as an example, the eighth type of scoreboard context control operation can be further understood as follows. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2*WinSize R- receiving an MPDU having an SN that satisfies 1; Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B and receiving an MPDU having an SN that satisfies No MPDU in any other A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, no MPDU in any A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, or all MPDUs carried in any A-MPDU received before the currently received A-MPDU have been acknowledged by the BA. If is true, then The STA may refresh and update the STA's scoreboard context.

[0169] Using Q=2 as an example, the ninth type of scoreboard context control operation can be further understood as follows. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2*WinSizeR- receiving an MPDU having an SN that satisfies 1; Other STAs associated with the receiving MLD B -WinSize R ≦SN <WinStart B and receiving an MPDU having an SN that satisfies Another MPDU having the SN in the currently received A-MPDU has not yet satisfied all the above conditions, or the one that satisfies all the above conditions is the first MPDU having the SN in the currently received A-MPDU received by the STA, or the scoreboard context of the STA has not been refreshed based on the MPDU in the currently received A-MPDU; No MPDU in any other A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, no MPDU in any A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, or all MPDUs carried in any A-MPDU received before the currently received A-MPDU have been acknowledged by the BA. If is true, then The STA may refresh and update the STA's scoreboard context.

[0170] Using Q=2 as an example, the tenth type of scoreboard context control operation can be further understood as follows. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2*WinSize R- receiving an MPDU having an SN that satisfies 1; WinStart B -WinSize R ≦SN <WinStart B There is no MPDU with an SN that satisfies the WinStart B -WinSize R ≦SN <WinStart B An MPDU having an SN that satisfies the following is received by another STA associated with the receiving MLD; no MPDU in any other A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, no MPDU in any A-MPDU received before the currently received A-MPDU has not been acknowledged by the BA, or all MPDUs carried in any A-MPDU received before the currently received A-MPDU have been acknowledged by the BA, Here, it can be understood that the sequence of executing the above conditions by the STA is not limited. Either another MPDU with the SN in the currently received A-MPDU has not yet satisfied all the above conditions, or the one that satisfies all the above conditions is the first MPDU with the SN in the A-MPDU received by the STA, or the scoreboard context of the STA has not been refreshed based on the MPDU in the currently received A-MPDU. If is true, then The STA may refresh and update the STA's scoreboard context.

[0171] The above description of the scoreboard context control operation is merely an example, and the above description of this application 11 It can be understood that the relationship between the scoreboard window and the scoreboard window will not be described in detail one by one again here. For example, when the condition that the SN satisfies is combined with the scoreboard window size, all the 2 11 is 2*WinSize R may be replaced with.

[0172] In combination with the above third type scoreboard context control action and sixth type scoreboard context control action, the present application further provides an eleventh type scoreboard context control action. The following conditions are met: the receiving MLD has separate scoreboard context control for each link; All STAs associated with the receiving MLD can use the reordering buffer information to update their scoreboard context; The STA that cooperates with the receiving MLD is WinStart R ≦SN <WinStart R +2*WinSize R- receiving an MPDU having an SN that satisfies 1; Any MPDU with SN in the MPDU received by the STA is WinStart B -WinSize R ≦SN <WinStart B or the MPDU with the SN received by another STA associated with the receiving MLD does not satisfy WinStart B -WinSize R ≦SN <WinStart B To fulfill If is true, then The STA may refresh and update the STA's scoreboard context.

[0173] The following describes a communication device provided in an embodiment of this application.

[0174] In this application, the communication device may be divided into functional modules based on the above method embodiment. For example, the functional modules may be obtained through division based on the corresponding functions, or two or more functions may be integrated into one processing module. The integrated module may be realized in the form of hardware, or in the form of a software functional module. It should be noted that in this application, the module division is used as an example and is merely a logical function division. In the actual implementation, other division methods may be used. Hereinafter, the communication device in the embodiment of this application will be described in detail with reference to Figs. 7 to 9.

[0175] 7 is a schematic diagram of the structure of a communication device according to an embodiment of this application. As shown in FIG. 7, the communication device includes: a processing unit 701 and a transceiver unit 702.

[0176] In some embodiments of this application, the communication device may be the transmitter described above. In other words, the communication device shown in Figure 7 may be configured to perform the steps, functions, etc. performed by the transmitter in the method embodiments described above.

[0177] For example, the transceiver unit 702 is configured to transmit ADDBA request frames and receive ADDBA response frames.

[0178] In another example, the transceiver unit 702 is further configured to transmit the first A-MPDU.

[0179] In another example, the transceiver unit 702 is further configured to transmit BAR frames and receive BA frames.

[0180] In another example, the transceiver unit 702 is further configured to transmit a second A-MPDU.

[0181] It can be understood that the specific description of the transceiver unit and the processing unit in this embodiment of this application is merely an example. For the specific functions or steps performed by the transceiver unit and the processing unit, please refer to the above method embodiments (including, for example, FIG. 4 and FIG. 5). Details will not be described again here.

[0182] FIG. 7 is reused. In some other embodiments of this application, the communication device may be the receiver described above. In other words, the communication device shown in FIG. 7 may be configured to perform the steps, functions, etc. performed by the receiver in the above method embodiments.

[0183] For example, the transceiver unit 702 is configured to receive ADDBA request frames and transmit ADDBA response frames.

[0184] In another example, the transceiver unit 702 is further configured to receive a first A-MPDU.

[0185] In another example, the processing unit 701 is configured to obtain a locally recorded scoreboard context, and refresh the scoreboard context based on the SN of the first A-MPDU when the first A-MPDU satisfies at least one of the third type scoreboard context control operation to the tenth type scoreboard context control operation shown in the embodiments of this application.

[0186] In another example, the transceiver unit 702 is further configured to receive a BAR frame and transmit a BA frame.

[0187] In another example, the transceiver unit 702 is further configured to receive a second A-MPDU. The processing unit 701 is further configured to refresh the scoreboard context based on the indication information in the second A-MPDU.

[0188] It can be understood that the specific description of the third type scoreboard context control operation to the tenth type scoreboard context control operation can be referred to the above method embodiments, and the details will not be described again one by one here.

[0189] It can be understood that the specific description of the transceiver unit and the processing unit in this embodiment of this application is merely an example. For the specific functions or steps performed by the transceiver unit and the processing unit, please refer to the above method embodiments (including, for example, FIG. 4 and FIG. 5). Details will not be described again here.

[0190] Above is a description of the transmitter and receiver in the embodiment of this application. Below is a description of possible product forms of the transmitter and receiver. It should be understood that any type of product having the function of the transmitter in Fig. 7 or any type of product having the function of the receiver in Fig. 7 falls within the protection scope of the embodiment of this application. It should be further understood that the following description is merely an example, and the product forms of the transmitter and receiver in the embodiment of this application are not limited thereto.

[0191] In the communication device shown in Fig. 7, the processing unit 701 may be one or more processors. The transceiver unit 702 may be a transceiver, or the transceiver unit 702 may be a transmitting unit and a receiving unit. The transmitting unit may be a transmitter, and the receiving unit may be a receiver. The transmitting unit and the receiving unit are integrated into one component, for example, a transceiver. In this embodiment of the application, the processor and the transceiver may be combined, and the connection manner between the processor and the transceiver is not limited in this embodiment of the application.

[0192] As shown in FIG. 8, the communications device 80 includes one or more processors 820 and a transceiver 810 .

[0193] For example, when the communication device is configured to perform the steps, methods, or functions performed by a transmitter, for example, the transceiver 810 is configured to transmit an ADDBA request frame and receive an ADDBA response frame. In another example, the transceiver 810 is further configured to transmit a first A-MPDU. In another example, the transceiver 810 is further configured to transmit a BAR frame and receive a BA frame. In another example, the transceiver 810 is further configured to transmit a second A-MPDU.

[0194] For example, when the communication device is configured to execute the steps, methods, or functions executed by the receiver, for example, the transceiver 810 is configured to receive an ADDBA request frame and transmit an ADDBA response frame. In another example, the transceiver 810 is further configured to receive a first A-MPDU. In another example, the processor 820 is configured to obtain a locally recorded scoreboard context and refresh the scoreboard context based on the SN of the first A-MPDU when the first A-MPDU satisfies at least one of the third type scoreboard context control operation to the tenth type scoreboard context control operation shown in the embodiment of this application. In another example, the transceiver 810 is further configured to receive a BAR frame and transmit a BA frame. In another example, the transceiver 810 is further configured to receive a second A-MPDU. The processor 820 is further configured to refresh the scoreboard context based on the indication information in the second A-MPDU.

[0195] It can be understood that for a specific description of the processor and the transceiver, reference can be made to the description of the processing unit and the transceiver unit shown in Figure 7. The details will not be described again here.

[0196] In each implementation of the communication apparatus shown in Figure 8, the transceiver may include a receiver and a transmitter. The receiver is configured to perform a function (or operation) of receiving, and the transmitter is configured to perform a function (or operation) of transmitting. The transceiver is configured to communicate with other devices / apparatuses by using a transmission medium.

[0197] Optionally, the communication device 80 may further include one or more memories 830 configured to store program instructions and / or data. The memory 830 is coupled to the processor 820. The coupling in the embodiments of this application may be an indirect coupling or communication connection between devices, units or modules in an electrical, mechanical or other form, and is used for information exchange between the devices, units or modules. The processor 820 may cooperate with the memory 830. The processor 820 may execute the program instructions stored in the memory 830. Optionally, at least one of the one or more memories may be included in the processor.

[0198] The specific connection medium between the transceiver 810, the processor 820, and the memory 830 is not limited in this embodiment of the application. In this embodiment of the application, the memory 830, the processor 820, and the transceiver 810 are connected to each other through a bus 840 in FIG. 8. The bus is represented by using a thick line in FIG. 8. The connection manner between the other components is merely an example for explanation and is not limited thereto. The bus may be classified into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used for representation in FIG. 8, but this does not mean that there is only one bus or only one type of bus.

[0199] In the embodiments of this application, the processor may be a general-purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application may be directly executed by a hardware processor, or may be executed by using a combination of hardware modules and software modules in the processor.

[0200] In this embodiment of the application, the memory may include, but is not limited to, a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), a random access memory (RAM), an erasable programmable read-only memory (EPROM), a read-only memory (ROM) or a compact disc read-only memory (CD-ROM). The memory is, but is not limited to, any other medium capable of carrying or storing program code in the form of instructions or data structures and capable of being read and / or written by a computer (e.g., a communication device as shown in this application). The memory in this embodiment of the application may alternatively be a circuit or any other device capable of implementing a storage function and configured to store program instructions and / or data.

[0201] The processor 820 is mainly configured to process communication protocols and communication data, control the entire communication device, execute software programs, and process data of the software programs. The memory 830 is mainly configured to store software programs and data. The transceiver 810 may include a control circuit and an antenna. The control circuit is mainly configured to perform conversion between baseband signals and radio frequency signals, and process the radio frequency signals. The antenna is mainly configured to transmit and receive the radio frequency signals in the form of electromagnetic waves. The input / output device, such as a touch screen, a display, a keyboard, etc., is mainly configured to receive data input by a user and output data to a user.

[0202] After the communication device is powered on, the processor 820 may read the software program in the memory 830, interpret and execute the instructions of the software program, and process data of the software program. When data needs to be transmitted wirelessly, the processor 820 outputs a baseband signal to the radio frequency circuit after performing baseband processing on the data to be transmitted. After performing radio frequency processing on the baseband signal, the radio frequency circuit transmits the radio frequency signal in the form of electromagnetic waves through an antenna. When data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 820. The processor 820 converts the baseband signal into data and processes the data.

[0203] In other implementations, the radio frequency circuitry and antenna may be located independently of the processor performing the baseband processing, for example in a distributed scenario, the radio frequency circuitry and antenna may be located independently and remotely from the communication device.

[0204] It can be understood that the communication device shown in this embodiment of the present application may further include more components than those in FIG. 8. This is not limited in this embodiment of the present application. The above method performed by the processor and the transceiver is merely an example. For specific steps performed by the processor and the transceiver, please refer to the above method.

[0205] In another possible implementation manner, in the communication device shown in FIG. 7, the processing unit 701 may be one or more logic circuits, and the transceiver unit 702 may be an input / output interface, or may be called a communication interface, an interface circuit, an interface, etc. Alternatively, the transceiver unit 702 may be a transmitting unit and a receiving unit. The transmitting unit may be an output interface, and the receiving unit may be an input interface. The transmitting unit and the receiving unit are integrated into one unit, for example, an input / output interface. As shown in FIG. 9, the communication device shown in FIG. 9 includes a logic circuit 901 and an interface 902. Specifically, the processing unit 701 may be realized by using the logic circuit 901, and the transceiver unit 702 may be realized by using the interface 902. The logic circuit 901 may be a chip, a processing circuit, an integrated circuit, a system on chip (SoC) chip, etc. The interface 902 may be a communication interface, an input / output interface, a pin, etc. 9 shows an example in which the above-mentioned communication device is used as a chip. The chip includes a logic circuit 901 and an interface 902.

[0206] In this embodiment of the present application, the logic circuit and the interface may further be coupled to each other, and the specific connection manner of the logic circuit and the interface is not limited to this embodiment of the present application.

[0207] For example, when the communication device is configured to perform the method, function, or step performed by a transmitter, the interface 902 is configured to transmit an ADDBA request frame and receive an ADDBA response frame, for example. In another example, the interface 902 is further configured to transmit a first A-MPDU. In another example, the interface 902 is further configured to transmit a BAR frame and receive a BA frame. In another example, the interface 902 is further configured to transmit a second A-MPDU.

[0208] For example, when the communication device is configured to execute the method, function, or step executed by the receiver, for example, the interface 902 is configured to receive an ADDBA request frame and transmit an ADDBA response frame. In another example, the interface 902 is further configured to receive a first A-MPDU. In another example, the logic circuit 901 is configured to obtain a locally recorded scoreboard context and refresh the scoreboard context based on the SN of the first A-MPDU when the first A-MPDU satisfies at least one of the third type scoreboard context control operation to the tenth type scoreboard context control operation shown in the embodiment of this application. In another example, the interface 902 is further configured to receive a BAR frame and transmit a BA frame. In another example, the interface 902 is further configured to receive a second A-MPDU. The logic circuit 901 is further configured to refresh the scoreboard context based on the indication information in the second A-MPDU.

[0209] It can be understood that the communication device shown in the embodiments of this application may implement the methods provided in the embodiments of this application in the form of hardware, or may implement the methods provided in the embodiments of this application in the form of software, which is not limited to the embodiments of this application.

[0210] For the specific implementation of the embodiment shown in Figure 9, please refer to the above embodiment, and the details will not be described again here.

[0211] An embodiment of the present application further provides a wireless communication system. The wireless communication system includes a transmitter and a receiver. The transmitter and the receiver may be configured to perform the method in any one of the above embodiments (such as shown in FIG. 4, FIG. 5, etc.).

[0212] Additionally, this application further provides a computer program, which can be used to implement the operations and / or processes performed by the transmitter in the methods provided in this application.

[0213] This application further provides a computer program, which can be used to implement the operations and / or processes performed by the receiver in the methods provided in this application.

[0214] This application further provides a computer-readable storage medium, which stores computer code that, when executed on a computer, enables the computer to perform the actions and / or processes performed by the transmitter in the methods provided in this application.

[0215] This application further provides a computer-readable storage medium, which stores computer code that, when executed on a computer, enables the computer to perform the operations and / or processes performed by the receiver in the methods provided in this application.

[0216] This application further provides a computer program product, which includes computer code or a computer program that, when executed on a computer, enables the operations and / or processes performed by the transmitter in the methods provided in this application to be performed.

[0217] This application further provides a computer program product, which includes computer code or a computer program that, when executed on a computer, enables the operations and / or processes performed by the receiver in the methods provided in this application to be performed.

[0218] In some embodiments provided in this application, it should be understood that the disclosed system, device, and method may be realized in other ways. For example, the described device embodiment is merely an example. For example, the division into units is merely a logical division of functions, and may be divided in other ways in actual implementation. For example, multiple units or components may be combined or integrated into other systems, or some features may be ignored or not implemented. Furthermore, the shown or discussed mutual couplings or direct couplings or communication connections may be realized through some interfaces. Indirect couplings or communication connections between devices or units may be realized in electrical, mechanical, or other forms.

[0219] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units, and may be located in one place or distributed among multiple network units. Some or all of the units may be selected based on the actual requirements for achieving the technical effects of the solutions provided in the embodiments of this application.

[0220] Furthermore, the functional units in the embodiments of this application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be realized in the form of hardware or in the form of a software functional unit.

[0221] When the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on such understanding, the technical solutions of the embodiments of this application may be essentially, or the part contributing to the prior art, or all or part of the technical solutions may be realized in the form of a software product. The computer software product is stored in a readable storage medium and includes some instructions for instructing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of this application. The above readable storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

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

Claims

1. 1. A multi-link communication method, comprising: receiving, by a receiver, a first aggregate medium access control protocol data unit (A-MPDU); obtaining, by the receiver, a locally recorded scoreboard context, and refreshing the scoreboard context based on a sequence number (SN) of the first A-MPDU when the first A-MPDU satisfies any one or more of the following conditions: Including, The first condition is that the STA associated with the receiver is WinStart R ≦SN <WinStart R +2 11 receiving an MPDU having a SN satisfying The second condition is WinStart B -WinSize R ≦SN <WinStart B Any MPDU with a SN satisfying B -WinSize R ≦SN <WinStart B all MPDUs having a SN satisfying The method, wherein a third condition includes that no MPDU in another A-MPDU received before the first A-MPDU has not been acknowledged by a BA, any MPDU in any A-MPDU received before the first A-MPDU has been acknowledged by a BA, or all MPDUs carried in any A-MPDU received before the first A-MPDU have been acknowledged by a BA.

2. The first A-MPDU further satisfies the following fourth condition:

2. The method of claim 1 , wherein the fourth condition includes that another MPDU having an SN in the first A-MPDU has not yet satisfied the first condition, the second condition, and the third condition, that an MPDU having an SN received by a STA associated with the receiver is the first MPDU in the first A-MPDU that satisfies the first condition, the second condition, and the third condition, or that a scoreboard context of a STA associated with the receiver has not been refreshed based on an MPDU in the first A-MPDU.

3. The method of claim 1 or 2, wherein the receiver has separate scoreboard context control for each link, the links being between the receiver and a transmitter.

4. The method of claim 1 , wherein the STA associated with the receiver is capable of using reordering buffer information to update the scoreboard context.

5. The method according to claim 1 , wherein the SNs in the first A-MPDU belong to the same Traffic Identifier (TID).

6. A communication device, comprising: a transceiver unit configured to receive a first aggregate medium access control protocol data unit (A-MPDU); a processing unit configured to obtain a locally recorded scoreboard context and refresh the scoreboard context based on a sequence number (SN) of the first A-MPDU when the first A-MPDU satisfies any one or more of the following conditions: Including, The first condition is that the STA associated with the communication device is WinStart R ≦SN <WinStart R +2 11 receiving an MPDU having a SN satisfying The second condition is WinStart B -WinSize R ≦SN <WinStart B Any MPDU with a SN satisfying B -WinSize R ≦SN <WinStart B All MPDUs having an SN satisfying the following are received by other STAs associated with the communication device; The apparatus, wherein a third condition includes that no MPDU in another A-MPDU received before the first A-MPDU has not been acknowledged by a BA, that no MPDU in any A-MPDU received before the first A-MPDU has been acknowledged by a BA, or that all MPDUs carried in any A-MPDU received before the first A-MPDU have been acknowledged by a BA.

7. The first A-MPDU further satisfies the following fourth condition: The device of claim 6, wherein the fourth condition includes that another MPDU having an SN in the first A-MPDU has not yet satisfied the first condition, the second condition, and the third condition, that an MPDU having an SN received by a STA associated with the communication device is the first MPDU in the first A-MPDU that satisfies the first condition, the second condition, and the third condition, or that a scoreboard context of a STA associated with the communication device has not been refreshed based on an MPDU in the first A-MPDU.

8. 8. Apparatus according to claim 6 or 7, wherein the communication device has separate scoreboard context control for each link, the links being between the communication device and a transmitter.

9. The apparatus of claim 6 , wherein the STAs associated with the communication device are capable of using reordering buffer information to update the scoreboard context.

10. The apparatus according to claim 6 , wherein the SNs in the first A-MPDU belong to the same Traffic Identifier (TID).

11. A communication device including a processor and a memory, The memory is configured to store instructions; A communications device, wherein the processor is configured to execute the instructions to enable the method of any one of claims 1 to 5 to be performed.

12. A communication device including a logic circuit and an interface, the logic circuit is coupled to the interface; A communications device, wherein the interface is configured to input and / or output code instructions and the logic circuit is configured to execute the code instructions to enable a method according to any one of claims 1 to 5 to be performed.

13. 1. A computer-readable storage medium, comprising: The computer readable storage medium is configured to store a computer program, the computer program being operable, when executed, to perform the method of any one of claims 1 to 5.

14. A computer program comprising: A computer program which, when executed, performs the method according to any one of claims 1 to 5.

Images