Communication method and apparatus

Abstract

This application provides a communication method and apparatus, relating to the field of communication technology, for ensuring fairness between an ML entity and an SL entity in channel contention. The communication method is applied to an ML entity, which supports a master link and at least one slave link. A backoff counter is configured on the master link, while no backoff counter is configured on the slave links. The communication method includes: the ML entity executing a backoff procedure for the master link based on the backoff counter; when the backoff counter value is 0, the ML entity transmits a first PPDU on each of K first links, where the K first links include the master link and K-1 first slave links, and the first slave links are in an idle state during a first inter-frame interval before the backoff counter value reaches 0. This application is applicable to multi-link channel access processes.

Description

[0001] This application is a divisional application. The original application has the application number 201910606607.7 and the original application date is July 5, 2019. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communication technology, and in particular to communication methods and apparatus. Background Technology

[0003] To achieve the technical goal of extremely high throughput, the Institute of Electrical and Electronics Engineers (IEEE) 802.11be standard includes multi-link (ML) as one of its key technologies. ML entities supporting ML technology have the ability to transmit and receive across multiple frequency bands, allowing them to utilize greater bandwidth for data transmission and significantly improving throughput. The spatial path through which an ML entity transmits data within a single frequency band can be called a link.

[0004] Currently, for any one of the multiple links supported by an ML entity, the ML entity can access the channel on that link in two ways. Method 1: When the backoff counter of the link decrements to 0, the ML entity can access the channel on that link. Method 2: When the backoff counter of another link decrements to 0, if that link was idle during the previous PI FS, the ML entity can access the channel on that link.

[0005] Since a single-link (SL) entity only supports data transmission on one link, the SL entity can only access the channel on that link when the backoff counter value of the link it supports decreases to 0.

[0006] Therefore, for a given link, the probability of an ML entity winning the channel contention is greater than that of an SL entity. In other words, when both ML and SL entities are deployed simultaneously in a WLAN, the SL entity is at a disadvantage in channel contention, thus affecting its normal communication. Summary of the Invention

[0007] This application provides a communication method and apparatus for ensuring fairness of SL entities in channel contention.

[0008] Firstly, a communication method is provided, which is applied to an ML entity. The ML entity supports a master link and at least one slave link. A backoff counter is set on the master link, and no backoff counter is set on the slave link. The method includes: the ML entity executing a backoff procedure for the master link based on the backoff counter; when the count value of the backoff counter is reduced to 0, the ML entity transmits a first physical layer protocol data unit (PPDU) on each of the K first links, including the master link and K-1 first slave links. The first slave links are in an idle state during the first inter-frame interval before the count value of the backoff counter is reduced to 0, where K is a positive integer.

[0009] Based on the above technical solution, since the ML entity only sets a backoff counter on the main link, it only executes the backoff procedure on the main link when accessing the channel. In this way, the ML entity cannot compete for the channel before the backoff procedure on the main link ends, thus ensuring that the probability of the ML entity competing for the channel on the main channel is equal to the probability of the SL entity competing for the channel on its supported links. Therefore, the technical solution provided in this application can guarantee the fairness of the SL entity in channel contention, thereby ensuring that the SL entity can communicate normally.

[0010] Furthermore, based on the above technical solution, when the link supported by the SL entity and the main link of the ML entity are the same link, the SL entity and the ML entity actually compete for the channel on the same link. In this way, if the ML entity successfully competes for the channel on the main link, the SL entity will not send PPDUs on the main link, thus ensuring that the ML entity will not experience asynchronous reception and transmission on multiple links. For example, with link #1 as the main link, when the backoff counter of the ML AP entity on link #1 is 0, the ML AP entity sends PPDUs on both link #1 and link #2, and the SL entity will not send PPDUs to the ML AP entity on link #1. Therefore, the ML AP entity can synchronously receive signals or synchronously transmit signals on link #1 and link #2.

[0011] In one possible design, the ML entity transmits a first PPDU on each of the K first links, including: the ML entity transmits the first PPDU on the available channel of each of the K first links, the available channel of the master link includes the master channel of the master link, and the available channel of the first slave link includes the master channel of the first slave link.

[0012] In one possible design, the ML entity executes the backoff process of the main link based on a backoff counter, including: the ML entity waits for the main channel of the main link to be idle for the second inter-frame interval; after the main channel of the main link is idle for the second inter-frame interval, the ML entity decrements the backoff counter value by 1 whenever the main channel of the main link is idle in a time slot; when the backoff counter value is reduced to 0, the ML entity ends the backoff process of the main link.

[0013] In one possible design, the first slave link is in an idle state during the first inter-frame interval before the end of the backoff process of the master link, including: the master channel of the first slave link is in an idle state during the first inter-frame interval before the backoff counter count value is reduced to 0.

[0014] In one possible design, the master channel of the first slave link is the lowest 20MHz sub-channel in the frequency band corresponding to the first slave link; or, the master channel of the first slave link is the highest 20MHz sub-channel in the frequency band corresponding to the first slave link. That is, the master channel of the first slave link is configured implicitly, which helps to save signaling overhead.

[0015] In one possible design, the first PPDU contains: a first type of media access control (MAC) frame, which does not require a response.

[0016] In one possible design, the first PPDU includes a second type MAC frame, which requires a response. The method further includes: the ML entity receiving a response frame of the second type MAC frame on one or more first links; if one or more first links do not include the primary link, the ML entity determines that the transmission opportunity (TXOP) establishment has failed; if one or more first links include the primary link, the ML entity determines that the TXOP establishment has succeeded.

[0017] In one possible design, the method further includes: an ML entity determining N second links corresponding to the TXOP, the N second links including a primary link and N-1 second slave links, the second slave links being first slave links that meet preset conditions, the preset conditions including: the ML entity sending a first PPDU containing a first type MAC frame on the first slave link; or, the ML entity sending a first PPDU containing a second type MAC frame on the first slave link and receiving a response frame of the second type MAC frame on the first slave link. The ML entity sends a second PPDU on each of the N second links.

[0018] In one possible design, the method further includes: if one or more second slave links fail to transmit the second PPDU, the ML entity stops sending the second PPDU on the second link where the transmission of the second PPDU failed, and continues to send the second PPDU on the second link where the transmission of the second PPDU succeeded, until the TXOP ends.

[0019] In one possible design, the method further includes: if the transmission of a second PPDU fails on one or more second links, the ML entity stops transmitting the second PPDU on N second links; the ML entity waits for the idle time of the main link to reach the first inter-frame interval; after the idle time of the main link reaches the first inter-frame interval, the ML entity transmits the second PPDU on each of P third links, the P third links including the main link and P-1 third slave links, the third slave links being the second slave links that were idle in the first inter-frame interval before the first moment, the first moment being the moment when the idle time of the main link reaches the first inter-frame interval, and P being a positive integer less than or equal to N.

[0020] In one possible design, the method further includes: if the transmission of a second PPDU fails on one or more second links, the ML entity stops transmitting the second PPDU on N second links; the ML entity performs a backoff procedure on the main link; after the backoff procedure on the main link ends, the ML entity transmits the second PPDU on each of P third links, the P third links including the main link and P-1 third slave links, the third slave links being second slave links that are idle in the first inter-frame interval before the end of the backoff procedure on the main link, where P is a positive integer less than or equal to N.

[0021] Secondly, a communication method is provided, which is applied to an ML entity that supports K first links. The method includes: the ML entity executing a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2; when the backoff procedure of the target link ends, the ML entity transmits a first PPDU on each of N second links, where the second link is an idle link in a first inter-frame interval before the end of the backoff procedure of the target link, and the target link is the first link among the K first links to end its backoff procedure, where N is a positive integer less than or equal to K; if the transmission of the first PPDU fails on one or more second links, the ML entity does not transmit a second PPDU on the second links where the transmission of the first PPDU failed within a preset time, or the ML entity does not transmit a second PPDU on any of the N second links within a preset time.

[0022] Based on the above technical solution, if the ML entity fails to transmit the first PPDU on one or more second links, the ML entity is prohibited from transmitting a second PPDU on the second link where the PPDU transmission failed for a preset time, or the ML entity is prohibited from transmitting a second PPDU on N second links for a preset time. In this way, the ML entity cannot use multiple links within the preset time. If one of the multiple links that the ML entity cannot use is supported by the SL entity, then within the preset time, because the ML entity cannot compete for the channel on the link supported by the SL entity, the probability of the SL entity winning the channel competition increases, thus ensuring the fairness of the SL entity in channel competition and guaranteeing the normal communication of the SL entity.

[0023] Thirdly, a communication method is provided, which is applied to an ML entity that supports K first links. The method further includes: the ML entity performing a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2; the ML entity sending a first PPDU on each of N second links, where the second link is a first link whose backoff procedure has ended and which was idle during the first inter-frame interval before the first moment, where N is a positive integer less than or equal to M.

[0024] Based on the above technical solution, although the ML performs the backoff procedure on all K first links, the second link used to transmit the first PPDU needs to meet the condition that the backoff procedure has ended. In other words, on a single link, the ML entity must at least complete the backoff procedure on that link in order to potentially compete for the channel. Compared to existing technologies where the ML entity can compete for the channel even without completing the backoff procedure on a single link, the technical solution of this application reduces the probability of the ML entity competing for the channel on a single link, thereby ensuring fairness in channel competition for the SL entities and ensuring that the SL entities can communicate normally.

[0025] In one possible design, the first moment is the end of the backoff process of the target link, which is the last of the N second links to end its backoff process.

[0026] Fourthly, a communication method is provided, which is applied to an ML entity that supports K first links. The method further includes: the ML entity executing a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2; and, if the sum of the backoff counters of the K first links is less than or equal to 0, or the sum of the backoff counters of the N second links is less than or equal to 0, the ML entity transmitting a first PPDU on each of the N second links, where the second link is a first link that was idle during the second inter-frame interval prior to the current time, and N is a positive integer less than or equal to M.

[0027] Based on the above technical solution, although the ML entity executes a backoff procedure on each of the K first links, the ML entity can only successfully compete for the channel if the sum of the backoff counters on the K first links is less than or equal to 0, or the sum of the backoff counters on the N second links is less than or equal to 0. In other words, the backoff counter count of the ML entity on one or more first links needs to be less than 0. This requires a relatively long period of idle time on one or more first links, reducing the probability of the ML entity competing for the channel. This reduced probability weakens the ML entity's advantage over the SL entity in channel competition, ensuring fairness for the SL entity in channel competition and thus guaranteeing normal communication for the SL entity.

[0028] In one possible design, the ML entity performs a backoff procedure on each of the K first links, including: for each of the K first links, the ML entity waits for the idle time of the first link to reach the second inter-frame interval; after the idle time of the first link reaches the second inter-frame interval, whenever the first link is idle in a time slot, the ML entity decrements the count value of the backoff counter of the first link by 1.

[0029] In one possible design, the backoff counter value of the first link includes negative integers.

[0030] In one possible design, the method further includes: for each of the K first links, after the idle time of the first link reaches the second inter-frame interval, whenever the first link is idle in a time slot, the ML entity decrements the count value of the target counter by 1. The target counter is used to record the sum of the count values ​​of the backoff counters of the K first links. In this way, the ML entity can directly obtain the sum of the count values ​​of the backoff counters of the K first links through the target counter.

[0031] Fifthly, a communication method is provided, which is applied to an ML entity. The ML entity supports multiple links, and the multiple links take turns serving as the first link according to a preset cyclical order. The method further includes: the ML entity executing a backoff procedure on the first link; after the backoff procedure of the first link ends, the ML entity sends a first PPDU on each of N second links, where the N second links include the first link and N-1 available links. The available links are in an idle state during the first inter-frame interval before the end of the backoff procedure of the first link, and N is a positive integer.

[0032] Based on the above technical solution, during each channel access attempt, the ML entity only executes the backoff procedure on the first link. That is, the ML entity only competes for the channel on one link. The probability of the ML entity successfully competing for the channel on one link is equal to the probability of the SL entity successfully competing for the channel on one link. This ensures fairness for the SL entity in channel competition, thereby guaranteeing normal communication for the SL entity.

[0033] Sixthly, a ML entity is provided, which may include modules corresponding to each of the methods / operations / steps / actions described in any of the designs in the first to fifth aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0034] A seventh aspect provides an ML entity, the ML entity including a processor and a transceiver, the processor being configured to perform processing operations in the communication method according to any one of the designs in the first to fifth aspects described above. The transceiver is configured to accept control from the processor and perform transmit and receive operations in the communication method according to any one of the designs in the first to fifth aspects described above.

[0035] Eighthly, a computer-readable storage medium is provided for storing instructions that, when read by a computer, enable the computer to execute the communication method involved in any of the designs of the first to fifth aspects described above.

[0036] A ninth aspect provides a computer program product comprising instructions. When a computer reads the instructions, the computer executes the communication method involved in any of the possible designs of the first to fourth aspects described above.

[0037] In a tenth aspect, a chip is provided, comprising processing circuitry and transceiver pins. The chip supports a master link and at least one slave link, wherein a backoff counter is provided on the master link, and no backoff counter is provided on the slave links. The processing circuitry is used by an ML entity to execute a backoff procedure for the master link based on the backoff counter. The transceiver pins are used to transmit a first PPDU on each of K first links when the backoff counter count value is reduced to 0, wherein the K first links include a master link and K-1 first slave links, and the first slave links are in an idle state during a first inter-frame interval before the backoff counter count value is reduced to 0, where K is a positive integer.

[0038] Eleventhly, a chip is provided, comprising a processing circuit and transceiver pins. The chip supports K first links. The processing circuit is configured to execute a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2. The transceiver pins are configured to transmit a first PPDU on each of N second links when the backoff procedure of the target link ends, wherein the second link is a first link that is idle for a first inter-frame interval before the end of the backoff procedure of the target link, and the target link is the first first link among the K first links to end its backoff procedure, where N is a positive integer less than or equal to K. The transceiver pins are also configured to, if the transmission of the first PPDU fails on one or more second links, not transmit a second PPDU on the second link where the transmission of the first PPDU failed within a preset time, or not transmit a second PPDU on any of the N second links within a preset time.

[0039] In a twelfth aspect, a chip is provided, comprising processing circuitry and transceiver pins. The chip supports K first links. The processing circuitry is configured to execute a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2. The transceiver pins are configured to transmit a first PPDU on each of N second links, where the second link is a first link whose backoff procedure has ended and which was idle during a first inter-frame interval prior to the first moment, where N is a positive integer less than or equal to M.

[0040] In a thirteenth aspect, a chip is provided, comprising processing circuitry and transceiver pins. The chip supports K first links. The processing circuitry is used to execute a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2. The transceiver pins are used to transmit a first PPDU on each of the N second links when the sum of the backoff counters of the K first links is less than or equal to 0, or when the sum of the backoff counters of the N second links is less than or equal to 0. The second links are the first links that were idle during the second inter-frame interval prior to the current time, where N is a positive integer less than or equal to M.

[0041] In a fourteenth aspect, a chip is provided, comprising a processing circuit and transceiver pins. The chip supports multiple links, which take turns serving as the first link according to a preset cyclical order. The processing circuit is used to execute a backoff procedure on the first link. The transceiver pins are used to transmit a first PPDU on each of N second links after the backoff procedure of the first link ends. The N second links include the first link and N-1 available links. The available links are idle for a first inter-frame interval before the end of the backoff procedure of the first link, where N is a positive integer.

[0042] The technical effects of any of the designs in aspects six through fourteen can be found in the beneficial effects of the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0043] Figure 1 A schematic diagram of a backoff process provided for an embodiment of this application;

[0044] Figure 2 A schematic diagram of a PPDU frame structure provided in an embodiment of this application;

[0045] Figure 3 A schematic diagram of an ML communication scenario provided in an embodiment of this application;

[0046] Figure 4 A schematic diagram illustrating another ML communication scenario provided in an embodiment of this application;

[0047] Figure 5 A flowchart illustrating a communication method provided in an embodiment of this application;

[0048] Figure 6 A flowchart illustrating another communication method provided in an embodiment of this application;

[0049] Figure 7 A schematic diagram illustrating another ML communication scenario provided in an embodiment of this application;

[0050] Figure 8 A schematic diagram illustrating another ML communication scenario provided in an embodiment of this application;

[0051] Figure 9(a) is a flowchart of another communication method provided in an embodiment of this application;

[0052] Figure 9(b) is a flowchart of another communication method provided in an embodiment of this application;

[0053] Figure 10 A flowchart illustrating another communication method provided in an embodiment of this application;

[0054] Figure 11(a) is a flowchart of another communication method provided in an embodiment of this application;

[0055] Figure 11(b) is a flowchart of another communication method provided in an embodiment of this application;

[0056] Figure 12 A flowchart illustrating another communication method provided in an embodiment of this application;

[0057] Figure 13 A flowchart illustrating another communication method provided in an embodiment of this application;

[0058] Figure 14 A schematic diagram of the structure of an ML entity provided in an embodiment of this application;

[0059] Figure 15 This is a schematic diagram of the structure of an ML entity provided in an embodiment of this application. Detailed Implementation

[0060] In the description of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. The "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. The terms "first," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., do not necessarily imply differences.

[0061] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0062] To facilitate understanding, the technical terms involved in the embodiments of this application will be briefly introduced below.

[0063] 1. Basic Service Set (BSS)

[0064] A Basic Service Set Identifier (BSS) is used to describe a group of devices in a wireless local area network (WLAN) that are able to communicate with each other. A WLAN can include multiple BSSs. Each BSS has a unique identifier called a Basic Service Set Identifier (BSSID).

[0065] A BSS can include multiple stations (STAs). A station can be an access point (AP) or a non-access point station (non-AP STA). Optionally, a BSS can include one AP and multiple non-AP STAs associated with that AP.

[0066] An AP, also known as a wireless access point or hotspot, can be a wireless router, wireless transceiver, wireless switch, etc.

[0067] Non-AP STAs can have different names, such as user unit, access terminal, mobile station, mobile station, mobile device, terminal, user equipment, etc. In practical applications, non-AP STAs can be cellular phones, smartphones, wireless local loops (WLLs), and other handheld devices and computer devices with wireless LAN communication capabilities.

[0068] 2. Retreat Mechanism

[0069] The IEEE 802.11 standard supports multiple users sharing the same transmission medium, with the sender performing a medium availability check before transmitting data. The IEEE 802.11 standard uses Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) to handle channel contention. Specifically, CSMA / CA employs a backoff mechanism to avoid collisions.

[0070] The backoff mechanism on a single channel is described below. Before sending a message, the device can select a random number between 0 and the contention window (CW), and use this random number as the initial value of the backoff counter. After the channel's idle time reaches the arbitration inter-frame space (AIFS), the backoff counter count is decremented by 1 for each idle time lot. If the channel is busy in a certain time lot before the backoff counter count reaches 0, the backoff counter pauses counting. Afterwards, if the channel transitions from a busy state to an idle state, and the idle time reaches the AIFS, the backoff counter resumes counting. When the backoff counter count reaches 0, the backoff process ends, and the device can begin data transmission.

[0071] Combination Figure 1 To illustrate, suppose the initial value of the backoff counter is 5. After the channel's idle time reaches AIFS, the backoff counter begins to back off. Each time the channel is idle in a time slot, the backoff counter value is decremented by 1 until it reaches 0. Once the backoff counter value is 0, the device successfully acquires the channel and can then transmit PPDUs on that channel.

[0072] 3. PPDU

[0073] like Figure 2The diagram shows the frame structure of a PPDU in the 802.11ax standard. A PPDU includes: a legacy-short training field (L-STF), a legacy-long training field (L-LTF), a legacy signaling field (L-SIG), a repeated legacy signaling field (RL-SIG), a high-efficiency signaling field A (HE-SIG A), a high-efficiency signaling field B (HE-SIG B), a high-efficiency-short training field (HE-STF), a high-efficiency-long training field (HE-LTF), data, and packet extension (PE).

[0074] 4. TXOP

[0075] A TXOP is the basic unit of wireless channel access. A TXOP consists of an initial time and a maximum duration of TXOP_limit. A station that acquires a TXOP can continuously use the channel to transmit multiple data frames without re-competing for the channel during the TXOP_limit time.

[0076] 5. Request to send (RTS) / Clear to send (CTS) mechanism

[0077] The RTS / CTS mechanism is used to solve the problem of hidden sites in order to avoid signal conflicts between multiple sites.

[0078] Before sending a data frame, the sending end first broadcasts an RTS frame to instruct the sending end to send a data frame to the designated receiving end within a specified time. Upon receiving the RTS frame, the receiving end broadcasts a CTS frame to acknowledge the sending end's transmission. Other stations that receive the RTS or CTS frame do not send radio frames until the specified time has elapsed.

[0079] 6. ML entities

[0080] ML entities have the capability to transmit and receive on multiple frequency bands. For example, these multiple frequency bands include, but are not limited to, the 2.4 GHz band, the 5 GHz band, and the 6 GHz band. The spatial path for an ML entity to transmit data on a single frequency band can be referred to as a link. In other words, ML entities support multi-link communication.

[0081] It should be understood that for an ML entity, each link supported by the ML entity corresponds to a frequency band.

[0082] An ML entity can also be called an ML STA entity. An ML entity consists of multiple STAs. Multiple STAs in an ML entity can have the same MAC address or different MAC addresses. Multiple STAs in an ML entity can be located in the same physical location or in different physical locations.

[0083] Each STA in an ML entity can establish a link for communication. For example... Figure 3 As shown, ML entity A contains stations A1 to AN, and ML entity B contains stations B1 to BN. Stations A1 and B1 communicate via link 1, stations A2 and B2 communicate via link 2, and so on. Stations AN and BN communicate via link N.

[0084] When the frequency spacing between multiple frequency bands supported by an ML entity is close, transmitting a signal on one frequency band will severely affect receiving a signal on another. Therefore, to ensure normal communication, when an ML entity uses multiple links for communication simultaneously, it needs to receive signals on multiple links simultaneously, or transmit signals on multiple links simultaneously. Figure 4 As shown, ML entity A simultaneously sends PPDU on the first link and the second link; then, ML entity A simultaneously receives block acknowledgment (BA) frames fed back by ML entity B on the first link and the second link.

[0085] In this embodiment of the application, the PPDUs sent simultaneously by the ML entity on different links may be the same or different.

[0086] In the embodiments of this application, when an ML entity communicates using multiple links simultaneously, the traffic identifiers (TIDs) corresponding to the multiple links may be the same or different.

[0087] If the STA in an ML entity is an AP, then the ML entity can be called an ML AP entity. If the STA in an ML entity is a non-AP STA, then the ML entity can be called an ML non-AP STA entity, or an ML non-AP entity. In the embodiments of this application, unless otherwise specified, an ML entity can be either an ML AP entity or an ML non-AP entity.

[0088] A non-AP STA on a link in an ML non-AP entity can be associated with an AP on the same link in an ML AP entity, so that a non-AP STA on a link in an ML non-AP entity can communicate with an AP on the same link in an ML AP entity.

[0089] It should be understood that associations can be established between ML AP entities and ML non-AP entities to ensure normal communication between them.

[0090] It should be noted that the association between ML AP entities and ML non-AP entities includes the association between sites of an ML AP entity on one link and sites of an ML non-AP entity on the same link.

[0091] This application does not limit the implementation method of establishing association between ML non-AP entities and ML AP entities. For example, ML non-AP entities and ML AP entities establish an association on a single link; or, ML non-AP entities and ML AP entities establish associations on multiple links on a single link.

[0092] An association is established between an ML non-AP entity and an ML AP entity. The specific implementation method can refer to the implementation method of establishing an association between AP and non-AP STA in the existing technology, which will not be repeated here.

[0093] 7. SL entity

[0094] An SL entity refers to a STA that supports only one link. An SL entity can be a legacy STA, that is, a STA that only supports the existing 802.11 standard and does not support the next generation of 802.11 standards.

[0095] The above is a brief introduction to the technical terms used in this application, which will not be repeated below.

[0096] The technical solution of this application is applied to WLAN, and the standard adopted by WLAN can be the IEEE 802.11 standard, such as the 802.11ax standard, and the next-generation 802.11 standard. The technical solution of this application is applicable to the following scenarios: communication scenarios between ML entities and communication scenarios between ML entities and SL entities.

[0097] For example, the communication scenarios between ML entities can be: communication scenarios between ML non-AP entities and ML AP entities; or, communication scenarios between ML non-AP entities and ML non-AP entities; or, communication scenarios between ML AP entities and ML AP entities.

[0098] For example, the communication scenarios between ML entities and SL entities can be: communication scenarios between ML non-AP entities and traditional APs; or, communication scenarios between ML AP entities and traditional non-AP STAs; or, communication scenarios between ML AP entities and traditional APs; or, communication scenarios between ML non-AP entities and traditional non-AP STAs.

[0099] The technical solutions provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0100] like Figure 5 The image shows a communication method provided in an embodiment of this application. The method includes the following steps:

[0101] S101 and ML entities execute the backoff process of the main link based on the backoff counter of the main link.

[0102] The ML entity supports a primary link and at least one secondary link. A backoff counter is set on the primary link, but not on the secondary links. It should be understood that because the backoff counter is only set on the primary link, the ML entity can only execute the backoff procedure on the primary link.

[0103] It should be understood that when an ML entity supports a primary link and at least one secondary link, it supports two channel access methods: a single-link channel access method, where the ML entity only uses the primary link for channel access; and a multi-link channel access method, where the ML entity uses both the primary and secondary links for channel access. In practical applications, the ML entity can select the channel access method based on factors such as channel conditions, power, and service load. For example, to save power, the ML entity may use a single-link channel access method; to improve throughput, the ML entity may use a multi-link channel access method. This application primarily describes the multi-link channel access method.

[0104] Optionally, the main link of an ML entity can be configured explicitly. It should be understood that configuring the main link of an ML entity explicitly offers greater flexibility.

[0105] For example, an ML AP entity can send indication information to its associated ML non-AP entity to indicate the main link information. The main link information may include: the main link's identifier / index, the frequency band corresponding to the main link, etc.

[0106] Optionally, the main link of an ML entity can be configured implicitly. It should be understood that configuring the main link of an ML entity implicitly helps to save signaling overhead.

[0107] For example, the protocol can define a link corresponding to a specific frequency band as the main link. For instance, the protocol might define a link corresponding to the 2.4 GHz frequency band as the main link.

[0108] For example, the protocol can define that among the multiple links supported by the ML entity, the link corresponding to the lowest frequency band is the primary link, or the link corresponding to the highest frequency band is the primary link. For instance, the ML entity supports the 2.4GHz band, the 5GHz band, and the 6GHz band. If the link corresponding to the lowest frequency band is the primary link, the ML entity uses the link corresponding to the 2.4GHz band as the primary link. If the link corresponding to the highest frequency band is the primary link, the ML entity uses the link corresponding to the 6GHz band as the primary link.

[0109] In the embodiments of this application, within the same BSS, the main link of the ML AP entity, the main link of the SL entity, and the main link of the ML non-SP entity are all the same link.

[0110] It is understandable that, for an ML entity, all links other than the primary link are considered secondary links among the multiple links supported by the ML entity.

[0111] As one implementation, the ML entity waits for the main channel of the main link to be idle for the second inter-frame interval. After the main channel of the main link has been idle for the second inter-frame interval, the ML entity decrements the backoff counter value by 1 whenever the main channel of the main link is idle in a time slot. When the backoff counter value is 0, the ML entity ends the backoff process of the main link.

[0112] It should be noted that if the main channel of the main link is busy within a time slot, the ML entity freezes the backoff counter until the idle time of the main channel reaches the second inter-frame interval again.

[0113] Optionally, the second inter-frame interval can be AI FS, and this embodiment of the application does not limit this.

[0114] Optionally, the aforementioned main channel may refer to the main 20MHz channel, but the embodiments of this application are not limited thereto.

[0115] Optionally, the primary channel of the main link can be configured explicitly. It should be understood that configuring the primary channel of the main link explicitly offers greater flexibility.

[0116] For example, the ML entity can receive a MAC frame from another device, which indicates the frequency domain location of the main channel of the main link in the corresponding frequency band of the main link. Optionally, the MAC frame can be a management frame such as a beacon frame or an association response frame.

[0117] Optionally, the primary channel of the main link can be configured implicitly. It should be understood that configuring the primary channel of the main link implicitly helps to save signaling overhead.

[0118] For example, the protocol can define the preset frequency domain position of the main channel of the main link within the frequency band corresponding to the main link. For instance, the highest frequency sub-channel (20MHz) in the frequency band corresponding to the main link can be used as the main channel. Alternatively, the lowest frequency sub-channel (20MHz) in the frequency band corresponding to the main link can be used as the main channel.

[0119] S102. When the backoff counter count is 0, the ML entity sends the first PPDU on each of the K first links.

[0120] Among them, the K first links include the main links and K-1 first slave links, where K is a positive integer.

[0121] In this embodiment, the first slave link is idle during the first inter-frame interval before the backoff counter value reaches 0. It should be understood that the moment the master link's backoff counter value reaches 0 corresponds to the end of the master link's backoff process.

[0122] In other words, for any slave link, if a slave link is idle during the first inter-frame interval before the end of the backoff process of the primary link, then the slave link is the first slave link; otherwise, the slave link is not the first slave link. Optionally, the aforementioned first inter-frame interval is PI FS, but the embodiments of this application are not limited to this.

[0123] Optionally, the busy / idle status of the slave link can be determined by the busy / idle status of the slave link's master channel. That is, if the slave link's master channel is busy, it means the slave link is busy. If the slave link's master channel is idle, it means the slave link is idle.

[0124] Optionally, the primary channel of the slave link is a primary 20MHz channel, but this application embodiment is not limited to this.

[0125] It should be understood that when the busy / idle state of a slave link is determined by the busy / idle state of the master channel of the slave link, the master channel of the first slave link is in an idle state during the first inter-frame interval before the backoff counter count value is reduced to 0.

[0126] Optionally, the master channel of the slave link can be configured explicitly. It should be understood that configuring the master channel of the slave link explicitly offers greater flexibility.

[0127] For example, an ML entity can receive a MAC frame from another device, which indicates the frequency domain location of the master channel of the slave link in the corresponding frequency band of the slave link. Optionally, the MAC frame can be a management frame such as a beacon frame or an association response frame.

[0128] Optionally, the master channel of the slave link can be configured implicitly. It should be understood that configuring the master channel of the slave link implicitly helps to save signaling overhead.

[0129] For example, the protocol can define a preset frequency domain position of the master channel of the slave link within the corresponding frequency band. For instance, the highest frequency 20MHz sub-channel in the corresponding frequency band of the slave link can be used as the master channel of that slave link. Alternatively, the lowest frequency 20MHz sub-channel in the corresponding frequency band of the slave link can be used as the master channel of that slave link.

[0130] As an optional implementation, the ML entity transmits the first PPDU on the first available channel of each of the K first links. The first available channel of the master link includes the master channel of the master link. The first available channel of the first slave link includes the master channel of the first slave link.

[0131] In other words, for each of the K first links, before sending the first PPDU, the ML entity will determine the first available bandwidth of the first link based on the idle status of each sub-channel in the frequency band corresponding to the first link and its own bandwidth requirements, so as to make full use of the bandwidth resources of the first link.

[0132] It should be noted that the first PPDU refers to the first PPDU sent by the ML entity on the first link. The first PPDU can be used to establish a TXOP.

[0133] It should be understood that the first PPDU transmitted on different first links can be different. That is, the ML entity can send different first PPDUs on different first links.

[0134] Optionally, the first PPDU includes one of the following two cases:

[0135] Scenario 1: The first PPDU contains a first type of MAC frame but does not contain a second type of MAC frame.

[0136] In this embodiment, the first type of MAC frame does not require a response frame from the receiving end. In other words, the first type of MAC frame does not require a response.

[0137] For example, the first type of MAC frame is a CTS-to-self frame, but the embodiments of this application are not limited thereto.

[0138] In this embodiment, the second type of MAC frame requires the receiving end to send back a response frame. In other words, the second type of MAC frame requires a response.

[0139] For example, the second type of MAC frame can be an RTS frame. In the case that the second type of MAC frame is an RTS frame, the response frame of the second type of MAC frame is a CTS frame.

[0140] For example, the second type of MAC frame can be a data frame. When the second type of MAC frame is a data frame, the response frame for the second type of MAC frame is an acknowledgement (ACK) frame.

[0141] It should be understood that if the ML entity sends the first PPDU corresponding to scenario one on the main link, the ML entity assumes that the TXOP has been successfully established.

[0142] Scenario 2: The first PPDU contains a second type of MAC frame but does not contain a first type of MAC frame.

[0143] Scenario 3: The first PPDU contains a first type MAC frame and a second type MAC frame.

[0144] For scenario two or three, if the ML entity sends a first PPDU containing a second-type MAC frame on the main link, and if the ML entity receives a response frame of the second-type MAC frame on the main link, the ML entity determines that the TXOP establishment was successful. If the ML entity does not receive a response frame of the second-type MAC frame on the main link, the ML entity determines that the TXOP establishment failed.

[0145] The following section describes the scenario where an ML entity sends a first PPDU on K first links, taking into account various situations of the first PPDU.

[0146] Scenario 1: The ML entity sends the first PPDU containing the first type of MAC frame on K first links.

[0147] Scenario 2: The ML entity sends a first PPDU containing a first type of MAC frame on the main link and a portion of the first slave links, and sends a PPDU containing a second type of MAC frame on another portion of the first slave links.

[0148] Based on scenario one or scenario two, the ML entity TXOP is successfully created by default.

[0149] Scenario 3: The ML entity sends a first PPDU containing a second type of MAC frame on each of the K first links.

[0150] Scenario 4: The ML entity sends a first PPDU containing a second type of MAC frame on the main link and a portion of the first slave link, and sends a PPDU containing a first type of MAC frame on another portion of the first slave link.

[0151] Based on scenario three or four, the ML entity receives a response frame of type 2 MAC frame on one or more first links. If the one or more first links do not include the main link, the ML entity determines that TXOP establishment has failed. If the one or more first links include the main link, the ML entity determines that TXOP establishment has succeeded.

[0152] In this embodiment of the application, if a TXOP is successfully established, the maximum duration of the TXOP can be determined based on the duration field of the first PPDU transmitted on the main link.

[0153] based on Figure 5 The technical solution shown in this application, because the ML entity only sets a backoff counter on the main link, executes the backoff procedure only on the main link during channel access. This ensures that the ML entity cannot compete for the channel before the backoff procedure on the main link ends, thus guaranteeing that the probability of the ML entity competing for the channel on the main channel is equal to the probability of the SL entity competing for the channel on its supported links. Therefore, the technical solution provided in this application can guarantee the fairness of the SL entity in channel contention, thereby ensuring that the SL entity can communicate normally.

[0154] In addition, based on Figure 5The illustrated technical solution, when the link supported by the SL entity and the main link of the ML entity are the same link, means that the SL entity and the ML entity actually compete for the channel on the same link. This ensures that if the ML entity successfully acquires the channel on the main link, the SL entity will not send PPDUs on the main link, thus preventing the ML entity from experiencing asynchronous reception and transmission across multiple links. For example, with link #1 as the main link, when the backoff counter of the ML AP entity on link #1 is 0, the ML AP entity sends PPDUs on both link #1 and link #2, and the SL entity will not send PPDUs to that ML AP entity on link #1. Therefore, the ML AP entity can synchronously receive or transmit signals on both link #1 and link #2.

[0155] As an optional embodiment, based on Figure 5 The communication method shown is as follows: Figure 6 As shown, if the ML entity successfully establishes a TXOP, the communication method further includes steps S103-S104.

[0156] S103, ML entity determines N second links corresponding to TXOP from K first links.

[0157] Among them, the N second links include the main link and N-1 second slave links, where N is a positive integer less than or equal to K.

[0158] In this embodiment of the application, the second slave link is the first slave link that meets the preset conditions.

[0159] Optional, the preset conditions include one of the following:

[0160] Condition 1: The ML entity sends a first PPDU containing a first type of MAC frame on the first slave link.

[0161] Condition 2: The ML entity sends a first PPDU containing a second type MAC frame on the first slave link and receives a response frame containing a second type MAC frame on the same first slave link.

[0162] S104 and ML entities respectively send the second PPDU on each of the N second links.

[0163] The second PPDU is different from the first PPDU. In other words, the second PPDU is any PPDU other than the first PPDU.

[0164] It should be understood that the second PPDU sent by the ML entity on different second links can be different PPDUs to achieve extremely high throughput.

[0165] In this embodiment, the ML entity sends a second PPDU on a second link; subsequently, if the ML entity does not receive a response frame on the second link within a certain period of time, it indicates that the transmission of the second PPDU on the second link has failed. For example, the response frame may be a BA frame, but this embodiment is not limited to this.

[0166] It should be understood that in the scenario where the transmission of the second PPDU fails on the second link, if the ML entity does not take appropriate action on the second link where the transmission of the second PPDU fails, but continues to send the second PPDU on the second link where the transmission of the second PPDU fails, the second PPDU sent by the ML may continue to fail to be transmitted, thereby affecting the normal communication of the ML entity.

[0167] The following describes the handling method adopted by the ML entity in the scenario where the transmission of the second PPDU fails on one or more second links.

[0168] Processing Method 1: If the transmission of the second PPDU is successful on the primary link, but the transmission of the second PPDU fails on one or more secondary links, the ML entity stops sending the second PPDU on the secondary links where the transmission of the second PPDU failed, and continues to send the second PPDU on the secondary links where the transmission of the second PPDU was successful, until the TXOP ends.

[0169] For example, the ML entity sends the second PPDU on slave link #1, slave link #2, slave link #3, and the main link, respectively. If the transmission of the second PPDU on slave link #2 fails, the ML entity stops sending the second PPDU on slave link #2 and continues to send the second PPDU on slave link #1, slave link #3, and the main link.

[0170] Method 2: If the transmission of a second PPDU fails on one or more second links, the ML entity stops transmitting second PPDUs on N second links. Then, the ML entity waits for the idle time of the main link to reach the first inter-frame interval. When the idle time of the main link reaches the first inter-frame interval, the ML entity transmits the second PPDU on each of the P third links.

[0171] Among them, P third links include the main link and P-1 third slave links, where P is a positive integer less than or equal to N. The third slave link is the second slave link that is idle during the first inter-frame interval before the first moment, and the first moment is the moment when the idle time of the main link reaches the first inter-frame interval.

[0172] Combination Figure 7For example, the ML entity transmits the second PPDU #1 on slave link #1, slave link #2, and the main link. Since the ML entity does not receive a BA frame on slave link #1, it determines that the transmission of the second PPDU #1 on slave link #1 has failed. In this case, the ML entity suspends further transmission of the second PPDU on slave link #1, slave link #2, and the main link. After one PI FS (Personal Link Frame 1), since slave link #1 and the main link are idle during that PI FS, while slave link #2 is busy, the ML entity can determine that slave link #1 and the main link are the third links. In this case, the ML entity transmits the second PPDU #2 on slave link #1 and the main link, but not on slave link #2.

[0173] Method 3: If the transmission of the second PPDU fails on one or more second links, the ML entity stops transmitting the second PPDU on N second links. Then, the ML entity executes a backoff procedure on the main link. When the backoff procedure on the main link ends, the ML entity transmits the second PPDU on each of the P third links.

[0174] Among them, P third links include the main link and P-1 third slave links, where P is a positive integer less than or equal to N. The third slave link is the second slave link that is idle during the first inter-frame interval before the end of the backoff process of the main link.

[0175] It should be understood that the ML entity executes the backoff process on the main link, which can be referred to in the description of step S101 above, and will not be repeated here.

[0176] Combination Figure 8 For example, the ML entity transmits the second PPDU #1 on slave link #1, slave link #2, and the main link. Since the ML entity does not receive a BA frame on slave link #1, it determines that the transmission of the second PPDU #1 on slave link #1 has failed. In this case, the ML entity suspends further transmission of the second PPDU on slave link #1, slave link #2, and the main link. The ML entity sets the backoff counter value on the main link. During the PI FS before the backoff counter on the main link reaches 0, slave link #1 and the main link are idle, while slave link #2 is busy. Therefore, the ML entity can determine that slave link #1 and the main link are the third link. In this case, the ML entity transmits the second PPDU #2 on slave link #1 and the main link, but not on slave link #2.

[0177] It should be understood that in the above processing method two or three, for each of the P third links, the ML entity transmitting the second PPDU on the third link includes: the ML entity transmitting the second PPDU on the second available channel of the third link. For a link, the second available channel is a subset of the first available channel. The second available channel also includes the primary channel.

[0178] It should be understood that in the above processing method two or three, the failure to transmit the second PPDU on one or more second links specifically refers to the failure to transmit the second PPDU on the main link and / or the failure to transmit the second PPDU on one or more second slave links.

[0179] Based on any of the above processing methods, the ML entity can guarantee normal communication in the event that the transmission of the second PPDU fails on one or more second links.

[0180] As shown in Figure 9(a), a communication method provided in an embodiment of this application is included in the following steps:

[0181] S201 and ML entities respectively execute the backoff procedure on each of the K first links.

[0182] The ML entity supports K first links, where K is a positive integer greater than or equal to 2. Each of the K first links is equipped with a backoff counter.

[0183] For each of the K first links, the backoff procedure includes the following steps: The ML entity waits for the idle time of the first link to reach the second inter-frame interval. After the idle time of the first link reaches the second inter-frame interval, whenever the first link is idle within a time slot, the ML entity decrements the backoff counter value of the first link by 1. When the backoff counter value of the first link reaches 0, the ML entity terminates the backoff procedure of the first link.

[0184] In this embodiment, if the first link is busy in a time slot, the ML entity will freeze the backoff counter of the first link until the idle time of the first link reaches the second inter-frame interval again. It should be understood that freezing the backoff counter of the first link is equivalent to suspending the backoff process of the first link.

[0185] The aforementioned second inter-frame interval can be AI FS, and this application embodiment does not limit this.

[0186] The busy / idle status of the first link can be determined by the busy / idle status of the primary channel of the first link. That is, if the primary channel of the first link is busy, it means that the first link is busy. If the primary channel of the first link is idle, it means that the first link is idle.

[0187] Optionally, the primary channel of the first link mentioned above can refer to the primary 20MHz channel.

[0188] Optionally, the primary channel of the first link can be configured explicitly. It should be understood that configuring the primary channel of the first link explicitly offers greater flexibility.

[0189] For example, the ML entity can receive a MAC frame from another device, which indicates the frequency domain location of the primary channel of the first link in the corresponding frequency band of the first link. Optionally, the MAC frame can be a management frame such as a beacon frame or an association response frame.

[0190] Optionally, the primary channel of the first link can be configured implicitly. It should be understood that configuring the primary channel of the first link implicitly helps to save signaling overhead.

[0191] For example, the protocol can define a preset frequency domain position of the primary channel of the first link within the frequency band corresponding to the first link. For instance, the highest frequency sub-channel (20MHz) in the frequency band corresponding to the first link can be used as the primary channel of the first link. Alternatively, the lowest frequency sub-channel (20MHz) in the frequency band corresponding to the first link can be used as the primary channel of the first link.

[0192] In this embodiment of the application, when the ML entity executes the backoff process of K first links respectively, if the backoff process of a certain link ends first, the ML entity executes step S202.

[0193] S202. When the backoff process of the target link ends, the ML entity sends the first PPDU on each of the N second links.

[0194] The target link is the first link among the K first links to end the backoff process. That is, the target link is the first link among the K first links whose backoff counter value is reduced to 0.

[0195] The N secondary links include the target link and N-1 available links, where N is a positive integer less than or equal to K.

[0196] In this embodiment, an available link is a first link that is idle during the first inter-frame interval before the end of the target link's backoff procedure. Alternatively, an available link is a first link whose main channel is idle during the first inter-frame interval before the end of the target link's backoff procedure.

[0197] It should be understood that if a first link (or the primary channel of the first link) is busy during the first inter-frame interval before the end of the backoff procedure of the target link, then the first link is not an available link.

[0198] In this embodiment of the application, after the backoff process of the target link ends, the ML entity stops the backoff process of the other first links among the K first links except the target link until TXOP ends.

[0199] It should be understood that the first PPDU transmitted on different second links can be different. That is, the ML entity can send different first PPDUs on different second links.

[0200] S203. If the transmission of the first PPDU fails on one or more second links, the ML entity will not send the second PPDU on the second link where the transmission of the first PPDU failed within a preset time.

[0201] The second PPDU is different from the first PPDU. In other words, the second PPDU is any PPDU that comes before the first PPDU.

[0202] For example, the failure to transmit the first PPDU on the second link could mean that the ML entity did not receive the response frame corresponding to the first PPDU on the second link. It should be understood that the response frame corresponding to the first PPDU is used to respond to the MAC frame carried in the first PPDU. For example, if the first PPDU carries an RTS frame, then the response frame of the first PPDU could be a CTS frame.

[0203] Optionally, the preset time can be pre-configured or defined in the protocol, and the embodiments of this application are not limited thereto.

[0204] For example, if the ML entity transmits the first PPDU on links #1, #3, and #4 respectively, and the ML entity does not receive a response frame corresponding to the first PPDU on link #1, then the ML entity can determine that the transmission of the first PPDU on link #1 has failed. Therefore, the ML entity will not send a second PPDU on link #1 within a preset time.

[0205] Optionally, as shown in Figure 9(b), step S203 in Figure 9(a) can be replaced by step S204.

[0206] S204. If the transmission of the first PPDU fails on one or more second links, the ML entity will not send the second PPDU on N second links within a preset time.

[0207] For example, if the ML entity transmits the first PPDU on links #1, #3, and #4 respectively, and the ML entity does not receive a response frame corresponding to the first PPDU on link #1, then the ML entity can determine that the transmission of the first PPDU on link #1 failed. Therefore, the ML entity will not send the second PPDU on links #1, #3, and #4 within a preset time.

[0208] Based on the technical solution shown in Figure 9(a) or Figure 9(b), if the ML entity fails to transmit the first PPDU on one or more second links, the ML entity is prohibited from transmitting the second PPDU on the second link where the first PPDU transmission failed for a preset time, or the ML entity is prohibited from transmitting the second PPDU on N second links for a preset time. In this way, the ML entity cannot use multiple links (e.g., the second link where the first PPDU transmission failed or N second links) within the preset time. If one of the multiple links that the ML entity cannot use is supported by the SL entity, then within the preset time, since the ML entity cannot compete for the channel on the link supported by the SL entity, the probability of the SL entity winning the channel competition increases, thereby ensuring the fairness of the SL entity in channel competition and guaranteeing the normal communication of the SL entity.

[0209] like Figure 10 The image shows a communication method provided in an embodiment of this application. The method includes the following steps:

[0210] S301, the ML entity executes a backoff procedure on each of the K first links.

[0211] The ML entity supports K first links, where K is an integer greater than or equal to 2. Each of the K first links is equipped with a backoff counter.

[0212] For each of the K first links, the backoff procedure includes the following steps: The ML entity waits for the idle time of the first link to reach the second inter-frame interval. After the idle time of the first link reaches the second inter-frame interval, whenever the first link is idle within a time slot, the ML entity decrements the backoff counter value of the first link by 1. When the backoff counter value of the first link reaches 0, the ML entity terminates the backoff procedure of the first link.

[0213] In this embodiment, if the first link is busy in a time slot, the ML entity will freeze the backoff counter of the first link until the idle time of the first link reaches the second inter-frame interval again. It should be understood that freezing the backoff counter of the first link is equivalent to suspending the backoff process of the first link.

[0214] The aforementioned second inter-frame interval can be AI FS, and this application embodiment does not limit this.

[0215] The busy / idle status of the first link can be determined by the busy / idle status of the primary channel of the first link. That is, if the primary channel of the first link is busy, it means that the first link is busy. If the primary channel of the first link is idle, it means that the first link is idle.

[0216] Optionally, the aforementioned main channel may refer to the main 20MHz channel. For each first link, the configuration method for the main channel of the first link can be found above and will not be repeated here.

[0217] S302 and ML entities respectively send the first PPDU on each of the N second links.

[0218] Here, the N second links are subsets of the K first links, where N is a positive integer less than or equal to K.

[0219] In this embodiment, the second link is the first link that has completed the backoff process and was in an idle state during the first inter-frame interval before the first moment.

[0220] In other words, if a first link's backoff process has not ended before the first moment, then that first link is not a second link. Or, if a first link is busy during the first inter-frame interval before the first moment, then that first link is not a second link.

[0221] For example, the ML entity executes backoff procedures on links #1, #2, #3, and #4 respectively. Before the first moment, the backoff procedures for links #1, #2, and #4 have all ended. Furthermore, during the first inter-frame interval before the first moment, link #1 is idle, link #2 is busy, and link #4 is idle. Therefore, the ML entity can determine that links #1 and #4 are the second links.

[0222] Optionally, the first moment can be pre-configured or defined in the protocol.

[0223] Optionally, the first moment can be the end of the target link's backoff process.

[0224] For example, the target link can be the last of N second links to end the backoff process.

[0225] For example, the target link can be the kth first link among K first links that ends the backoff process, where k is an integer greater than 1 and less than or equal to K.

[0226] It should be understood that the first PPDU transmitted on different second links can be different. That is, the ML entity can send different first PPDUs on different second links.

[0227] based on Figure 10 The technical solution shown in this application, although the ML performs the backoff procedure on all K first links, requires the second link used to transmit the first PPDU to meet the condition that the backoff procedure has ended. In other words, on a single link, the ML entity must at least complete the backoff procedure on that link in order to potentially compete for the channel. Compared to existing technologies where the ML entity can compete for the channel even without completing the backoff procedure on a single link, the technical solution of this application reduces the probability of the ML entity competing for the channel on a single link, thereby ensuring fairness in channel competition for the SL entities and ensuring that the SL entities can communicate normally.

[0228] As shown in Figure 11(a), a communication method provided in an embodiment of this application is included in the following steps:

[0229] S401, the ML entity executes a backoff procedure on each of the K first links.

[0230] The ML entity supports K first links, where K is an integer greater than or equal to 2. Each of the K first links is equipped with a backoff counter.

[0231] For each of the K first links, the backoff procedure on the first link includes the following steps: The ML entity waits for the idle time of the first link to reach the second inter-frame interval. After the idle time of the first link reaches the second inter-frame interval, whenever the first link is idle within a time slot, the ML entity decrements the count value of the backoff counter of the first link by 1.

[0232] The aforementioned second inter-frame interval can be AI FS, and this application embodiment does not limit this.

[0233] In this embodiment, the backoff counter of the first link has a value range including negative integers. That is, after the ML entity reduces the count value of the backoff counter of the first link to 0, the ML entity does not end the backoff process of the first link, but continues to back off.

[0234] For example, the initial value of the backoff counter for link #1 is 5. After the idle time of link #1 reaches the second inter-frame interval, and link #1 is idle for 6 consecutive time slots, the count value of the backoff counter for link #1 can be -1.

[0235] In this embodiment, if the first link is busy in a time slot, the ML entity will freeze the backoff counter of the first link until the idle time of the first link reaches the second inter-frame interval again. It should be understood that freezing the backoff counter of the first link is equivalent to suspending the backoff process of the first link.

[0236] The busy / idle status of the first link can be determined by the busy / idle status of the primary channel of the first link. That is, if the primary channel of the first link is busy, it means that the first link is busy. If the primary channel of the first link is idle, it means that the first link is idle.

[0237] Optionally, the aforementioned main channel may refer to the main 20MHz channel. For each first link, the configuration method for the main channel of the first link can be found above and will not be repeated here.

[0238] S402. When the sum of the backoff counters of the K first links is less than or equal to 0, the ML entity sends the first PPDU on each of the N second links.

[0239] Here, the N second links are subsets of the K first links, where N is a positive integer less than or equal to K.

[0240] In this embodiment, the second link is the first link that was idle during the second inter-frame interval prior to the current time. Alternatively, the second link is the first link whose backoff counter was not frozen. Or, the second link is the first link whose backoff process was not suspended.

[0241] In step S402, the current time mentioned above refers to the time when the sum of the count values ​​of the backoff counters of the K first links is less than or equal to 0.

[0242] Optionally, within a time slot, the ML entity can count the sum of the backoff counters of the K first links to determine whether the sum of the backoff counters of the K first links is less than or equal to 0.

[0243] Optionally, the ML entity is also configured with a target counter, which records the count values ​​of the K first link backoff counters. In this way, within a time slot, the ML can determine whether the sum of the target counter counts is less than or equal to 0, thereby determining whether the sum of the K first link backoff counter counts is less than or equal to 0.

[0244] In the specific implementation, the ML entity configures a target counter, the initial value of which is equal to the sum of the initial values ​​of the backoff counters of the K first links. For each of the K first links, after the idle time of the first link reaches the second inter-frame interval, whenever the main channel of the first link is idle in a time slot, the ML entity decrements the target counter by 1. That is, whenever the ML entity decrements the backoff counter of a first link by 1, the ML entity also decrements the target counter by 1.

[0245] Optionally, as shown in Figure 11(b), step S402 in Figure 11(a) can be replaced by step S403.

[0246] S403. When the sum of the backoff counters of the N second links is less than or equal to 0, the ML entity sends the first PPDU on each of the N second links.

[0247] In this embodiment, the second link is the first link that was idle during the second inter-frame interval prior to the current time. Alternatively, the second link is the first link whose backoff counter was not frozen. Or, the second link is the first link whose backoff process was not suspended.

[0248] In step S403, the aforementioned current time refers to the moment when the sum of the count values ​​of the backoff counters of the N second links is less than or equal to 0.

[0249] Optionally, within a time slot, the ML entity can sum the counts of the backoff counters of N second links to determine whether the sum of the counts of the backoff counters of N second links is less than or equal to 0.

[0250] It should be understood that in step S403 or step S402, the first PPDU transmitted on different second links can be different. That is, the ML entity can send different first PPDUs on different second links.

[0251] Based on the technical solutions shown in Figure 11(a) or Figure 11(b), although the ML entity executes a backoff procedure on each of the K first links, the ML entity can only successfully compete for the channel if the sum of the backoff counters on the K first links is less than or equal to 0, or the sum of the backoff counters on the N second links is less than or equal to 0. In other words, the backoff counter count of the ML entity on one or more first links needs to be less than 0. This requires a relatively long idle time on one or more first links, reducing the probability of the ML entity competing for the channel. This reduced probability weakens the ML entity's advantage over the SL entity in channel competition, ensuring fairness for the SL entity in channel competition and thus guaranteeing normal communication for the SL entity.

[0252] like Figure 12 The image shows a communication method provided in an embodiment of this application. The method includes the following steps:

[0253] S501, the ML entity executes the backoff procedure on the first link.

[0254] Among them, ML entities support multiple links.

[0255] In this embodiment, each of the multiple links can be configured with a backoff counter. However, each time the ML entity initiates channel access across multiple links, the ML entity only uses the backoff counter of one of the links (i.e., the first link) to perform a backoff.

[0256] Optionally, one of the multiple links may be randomly selected as the first link. Alternatively, multiple links may take turns being the first link in a preset cyclical order.

[0257] Optionally, the above cyclic order can be: the sequence number of multiple links arranged from largest to smallest, or the sequence number of multiple links arranged from smallest to largest, or a pseudo-random order of the sequence numbers of multiple links. The embodiments of this application are not limited to these.

[0258] For example, an ML entity supports 7 links, numbered 0, 1, 2, 3, 4, 5, and 6. The default cyclic sequence is "01204465", where each number represents the link number. Thus, during the first channel access, the ML entity uses the link with number 0 as the first link. During the second channel access, it uses the link with number 1 as the first link, and so on, until the tenth channel access, when it uses the link with number 1 as the first link.

[0259] It should be understood that different ML entities can be set with different loop orders, and this application does not limit this.

[0260] In this embodiment, the ML entity executes a backoff procedure on the first link, including the following steps: The ML entity waits for the idle time of the first link to reach the second inter-frame interval. After the idle time of the first link reaches the second inter-frame interval, whenever the first link is idle within a time slot, the ML entity decrements the count value of the backoff counter of the first link by 1. When the count value of the backoff counter of the first link is 0, the ML entity terminates the backoff procedure of the first link.

[0261] In this embodiment, if the first link is busy in a time slot, the ML entity will freeze the backoff counter of the first link until the idle time of the first link reaches the second inter-frame interval again. It should be understood that freezing the backoff counter of the first link is equivalent to suspending the backoff process of the first link.

[0262] The aforementioned second inter-frame interval can be AI FS, and this application embodiment does not limit this.

[0263] The busy / idle status of the first link can be determined by the busy / idle status of its main channel. In other words, if the main channel of the first link is busy, then the first link is in a busy state. If the main channel of the first link is idle, then the first link is in an idle state.

[0264] Optionally, the primary channel of the first link mentioned above can refer to the primary 20MHz channel. The configuration method for the primary channel of the first link can be found above and will not be repeated here.

[0265] S502. When the backoff process of the first link ends, the ML entity sends the first PPDU on each of the N second links.

[0266] The N available links include the first link and N-1 second links, where N is a positive integer.

[0267] It should be understood that the second link and the first link are two different links. The second link is idle during the first inter-frame interval before the end of the backoff process of the first link.

[0268] It should be understood that the first PPDU transmitted on different second links can be different. That is, the ML entity can send different first PPDUs on different second links.

[0269] based on Figure 12The technical solution shown in the diagram involves the ML entity executing a backoff procedure only on the first link during each channel access attempt. That is, the ML entity only competes for the channel on one link. The probability of the ML entity successfully competing for the channel on one link is equal to the probability of the SL entity successfully competing for the channel on one link. This ensures fairness for the SL entity in channel contention, thereby guaranteeing normal communication for the SL entity.

[0270] In Figures 9(a) and 9(b) above Figure 10 Figure 11(a), Figure 11(b) or Figure 12 In the technical solution shown, the first PPDU may include the following two scenarios:

[0271] Scenario 1: The first PPDU contains a first type of MAC frame but does not contain a second type of MAC frame.

[0272] Scenario 2: The first PPDU contains a second type of MAC frame but does not contain a first type of MAC frame.

[0273] Scenario 3: The first PPDU contains a first type MAC frame and a second type MAC frame.

[0274] The detailed descriptions of the first type of MAC frame and the second type of MAC frame can be found in step S102, and will not be repeated here.

[0275] The following section describes the scenario where an ML entity sends a first PPDU on N second links, taking into account various situations of the first PPDU.

[0276] Scenario 1: An ML entity sends a first PPDU containing only first-type MAC frames on N second links.

[0277] Scenario 2: The ML entity sends a first PPDU containing only the first type of MAC frame on one part of the second link, and sends a first PPDU containing the second type of MAC frame on another part of the second link.

[0278] Based on scenario one or scenario two, the ML entity TXOP is successfully created by default.

[0279] Scenario 3: The ML entity sends the first PPDU containing a second type of MAC frame on N second links.

[0280] Based on scenario three, if the ML entity does not receive a response frame of type 2 MAC frame on any of the second links, the ML entity confirms that the TXOP establishment has failed. If the ML entity receives a response frame of type 2 MAC frame on at least one second link, the ML entity confirms that the TXOP establishment has succeeded.

[0281] As an optional embodiment, based on Figures 10 to 12 The technical solution shown is as follows: Figure 13 As shown, if the ML entity successfully establishes a TXOP, the communication method further includes the following steps S601-S602.

[0282] S601, ML entity determines P third links corresponding to TXOP from N second links.

[0283] Here, the P third links are subsets of the N second links, where P is a positive integer less than or equal to N.

[0284] In this embodiment, the third link is the second link that meets the preset conditions.

[0285] Optional, the preset conditions include one of the following:

[0286] Condition 1: The ML entity sends a first PPDU containing a first type MAC frame on the second link.

[0287] Condition 2: The ML entity sends a first PPDU containing a second type of MAC frame on the second link and receives a response frame containing a second type of MAC frame on the second link.

[0288] S602 and ML entities respectively send the second PPDU on each of the P third links.

[0289] It should be understood that the second PPDU transmitted on different third links can be different. That is, the ML entity can send different second PPDUs on different third links.

[0290] Optionally, in the event of a failure to transmit a PPDU on one or more third links, the ML entity may adopt any of the following handling methods.

[0291] Method 1: The ML entity stops sending the second PPDU on the third link where the transmission of the second PPDU failed, and continues to send the second PPDU on the third link where the transmission of the second PPDU was successful, until the TXOP ends.

[0292] Method 2: The ML entity stops sending the second PPDU on the P third links. The ML entity waits until a preset time to determine the L fourth links. Then, the ML entity sends the second PPDU on each of the L fourth links.

[0293] Here, L fourth links are subsets of P third links, where L is a positive integer less than or equal to P. A fourth link is a third link that is idle during the first inter-frame interval before a preset time.

[0294] It should be understood that the preset time can be pre-configured or defined in the protocol.

[0295] Method 3: The ML entity stops sending the second PPDU on each of the P third links. The ML entity executes a backoff procedure on each of the P third links. Upon completion of the backoff procedure on the target third link, the ML entity determines L fourth links. The ML entity then sends the second PPDU on each of the L fourth links.

[0296] Here, L fourth links are subsets of P third links, where L is a positive integer less than or equal to P. A fourth link is a third link that is idle during the first inter-frame interval before the target third link's backoff procedure ends. The target third link can be the first of the P third links to end its backoff procedure.

[0297] Based on any of the above processing methods, the ML entity can guarantee normal communication in the event that the transmission of the second PPDU fails on one or more third links.

[0298] The foregoing primarily describes the solutions provided in the embodiments of this application from the perspective of ML entities. It is understood that, in order to achieve the aforementioned functions, an ML entity includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0299] This application embodiment can divide the device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the example of dividing each functional module according to each function:

[0300] Figure 14 This is a schematic diagram of the structure of an ML entity provided in an embodiment of this application. For example... Figure 14 As shown, the ML entity includes a processing unit 101 and a communication unit 102.

[0301] Optionally, the ML entity can perform any of the following schemes:

[0302] Option 1

[0303] The ML entity supports a master link and at least one slave link. A backoff counter is set on the master link, but not on the slave links. Processing unit 101 is used for the ML entity to execute the backoff procedure of the master link based on the backoff counter. Communication unit 102 is used for transmitting a first PPDU on each of the K first links when the backoff counter count value is reduced to 0. The K first links include the master link and K-1 first slave links. The first slave links are in an idle state during the first inter-frame interval before the backoff counter count value is reduced to 0, where K is a positive integer.

[0304] In one possible design, the communication unit 102 is specifically used to transmit a first PPDU on the available channel of each of the K first links, wherein the available channel of the master link includes the master channel of the master link, and the available channel of the first slave link includes the master channel of the first slave link.

[0305] In one possible design, the processing unit 101 is specifically used to wait for the idle time of the main channel of the main link to reach the second inter-frame interval; after the idle time of the main channel of the main link reaches the second inter-frame interval, whenever the main channel of the main link is in an idle state in a time slot, the count value of the backoff counter is decremented by 1; when the count value of the backoff counter is reduced to 0, the backoff process of the main link ends.

[0306] In one possible design, the first slave link is in an idle state during the first inter-frame interval before the end of the backoff process of the master link, including: the master channel of the first slave link is in an idle state during the first inter-frame interval before the backoff counter count value is reduced to 0.

[0307] In one possible design, the master channel of the first slave link is the lowest 20MHz sub-channel in the frequency band corresponding to the first slave link; or, the master channel of the first slave link is the highest 20MHz sub-channel in the frequency band corresponding to the first slave link.

[0308] In one possible design, the first PPDU contains: a first type MAC frame, which does not require a response.

[0309] In one possible design, the first PPDU includes a second type MAC frame, which requires a response. The communication unit 102 is further configured to receive a response frame of the second type MAC frame on one or more first links. The processing unit 101 is further configured to determine that TXOP establishment has failed if one or more first links do not include the main link, and to determine that TXOP establishment has succeeded if one or more first links include the main link.

[0310] In one possible design, processing unit 101 is further configured to determine N second links corresponding to TXOP, the N second links including a primary link and N-1 second slave links, the second slave links being first slave links that meet preset conditions, the preset conditions including: the ML entity sending a first PPDU containing a first type MAC frame on the first slave link; or, the ML entity sending a first PPDU containing a second type MAC frame on the first slave link and receiving a response frame of the second type MAC frame on the first slave link. Communication unit 102 is further configured to send a second PPDU on each of the N second links.

[0311] In one possible design, the communication unit 102 is further configured to, if one or more second slave links fail to transmit the second PPDU, stop transmitting the second PPDU on the second link where the transmission of the second PPDU failed, and continue transmitting the second PPDU on the second link where the transmission of the second PPDU succeeded, until the TXOP ends.

[0312] In one possible design, communication unit 102 is further configured to stop transmitting the second PPDU on N second links if the transmission of the second PPDU fails on one or more second links. Processing unit 101 is further configured to wait for the idle time of the main link to reach the first inter-frame interval. Communication unit 102 is further configured to transmit the second PPDU on each of P third links after the idle time of the main link reaches the first inter-frame interval. The P third links include the main link and P-1 third slave links. The third slave links are the second slave links that are idle during the first inter-frame interval before the first moment. The first moment is the moment when the idle time of the main link reaches the first inter-frame interval, and P is a positive integer less than or equal to N.

[0313] In one possible design, communication unit 102 is further configured to stop transmitting the second PPDU on N second links if the transmission of the second PPDU fails on one or more second links. Processing unit 101 is further configured to execute a backoff procedure on the main link. Communication unit 102 is further configured to transmit the second PPDU on each of P third links after the backoff procedure on the main link has ended. The P third links include the main link and P-1 third slave links. The third slave links are second slave links that are idle in the first inter-frame interval before the end of the backoff procedure on the main link, where P is a positive integer less than or equal to N.

[0314] Option 2

[0315] The ML entity supports K first links. Processing unit 101 is configured to execute a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2. Communication unit 102 is configured to transmit a first PPDU on each of the N second links when the backoff procedure of the target link ends. The second link is the first link that was idle during the first inter-frame interval before the end of the backoff procedure of the target link. The target link is the first link among the K first links to end its backoff procedure, where N is a positive integer less than or equal to K. Communication unit 102 is also configured to, if the transmission of the first PPDU fails on one or more second links, not transmit a second PPDU on the second link where the first PPDU transmission failed, or not transmit a second PPDU on any of the N second links within a preset time.

[0316] Option 3

[0317] The ML entity supports K first links. Processing unit 101 is used to execute a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2. Communication unit 102 is used to send a first PPDU on each of the N second links, where the second link is a first link whose backoff procedure has ended and which was idle during the first inter-frame interval before the first moment, where N is a positive integer less than or equal to M.

[0318] In one possible design, the first moment is the end of the backoff process of the target link, which is the last of the N second links to end its backoff process.

[0319] Option 4

[0320] The ML entity supports K first links. Processing unit 101 is used to execute a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2. Communication unit 102 is used to send a first PPDU on each of the N second links when the sum of the backoff counters of the K first links is less than or equal to 0, or when the sum of the backoff counters of the N second links is less than or equal to 0. The second links are the first links that were idle during the second inter-frame interval before the current time, where N is a positive integer less than or equal to M.

[0321] In one possible design, the processing unit 101 is specifically used to wait for the idle time of each of the K first links to reach the second inter-frame interval; after the idle time of the first link reaches the second inter-frame interval, whenever the first link is in an idle state in a time slot, the count value of the backoff counter of the first link is decremented by 1.

[0322] In one possible design, the backoff counter value of the first link includes negative integers.

[0323] In one possible design, the processing unit 101 is also used to decrement the count value of the target counter by 1 whenever the first link is idle in a time slot after the idle time of the first link reaches the second inter-frame interval. The target counter is used to record the sum of the count values ​​of the backoff counters of the K first links.

[0324] Option 5

[0325] The ML entity supports multiple links, which take turns serving as the first link according to a preset cyclical order. Processing unit 101 is used to execute a backoff procedure on the first link. Communication unit 102 is used to send a first PPDU on each of the N second links after the backoff procedure on the first link ends. The N second links include the first link and N-1 available links. The available links are idle during the first inter-frame interval before the end of the backoff procedure on the first link, where N is a positive integer.

[0326] The ML entity provided in the above embodiments of this application can be implemented in various product forms. For example, the ML entity can be configured as a general-purpose processing system; for another example, the ML entity can be implemented using a general bus architecture; for yet another example, the ML entity can be implemented using an application-specific integrated circuit (ASIC), etc. Several possible product forms of the ML entity described in the embodiments of this application are provided below. It should be understood that the following product forms are merely examples and do not limit the possible product forms of the ML entity described in the embodiments of this application.

[0327] Figure 15 This is a result diagram of the possible product forms of the ML entity described in the embodiments of this application.

[0328] As one possible product form, the ML entity described in this application embodiment can be a communication device, which includes a processor 201 and a transceiver 202. Optionally, the communication device further includes a storage medium 203.

[0329] The processor 201 is used to execute Figure 5 Step S101 in the process, Figure 6 Step S103 in Figure 9(a), and step S201 in Figure 9(a) Figure 10 Step S301 in Figure 11(a), and step S401 in Figure 11(a) Figure 12 Step S501 in the process, Figure 13 Step S601 in the process. Transceiver 202 is used to perform... Figure 5 Step S102 in the process, Figure 6 Step S104 in Figure 9(a), steps S202 and S203 in Figure 9(a), and step S204 in Figure 9(b) Figure 10 Step S302 in Figure 11(a), step S402 in Figure 11(a), and step S403 in Figure 11(b) Figure 12 Step S502 in the process, Figure 13 Step S602 in the process.

[0330] As another possible product form, the ML entity described in this application embodiment can also be implemented by a general-purpose processor or a dedicated processor, that is, a chip. The chip includes a processing circuit 201 and transceiver pins 202. Optionally, the chip may also include a storage medium 203.

[0331] The processing circuit 201 is used to perform... Figure 5 Step S101 in the process, Figure 6 Step S103 in Figure 9(a), and step S201 in Figure 9(a) Figure 10Step S301 in Figure 11(a), and step S401 in Figure 11(a) Figure 12 Step S501 in the process, Figure 13 Step S601 in the process. Transceiver pin 202 is used to perform... Figure 5 Step S102 in the process, Figure 6 Step S104 in Figure 9(a), steps S202 and S203 in Figure 9(a), and step S204 in Figure 9(b) Figure 10 Step S302 in Figure 11(a), step S402 in Figure 11(a), and step S403 in Figure 11(b) Figure 12 Step S502 in the process, Figure 13 Step S602 in the process.

[0332] This application also provides a computer-readable storage medium storing computer instructions; when the computer-readable storage medium is run on an ML entity, the ML entity performs the following... Figure 5 , Figure 6 Figure 9(a), Figure 9(b) Figure 10 Figure 11(a), Figure 11(b) Figure 12 or Figure 13 The method is illustrated. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access, or it can include one or more data storage devices such as servers or data centers that can be integrated with media. The available medium can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media, or semiconductor media (e.g., solid-state drives (SSDs)).

[0333] This application also provides a computer program product containing computer instructions, which, when run on an ML entity, enables the ML entity to execute. Figure 5 , Figure 6 Figure 9(a), Figure 9(b) Figure 10 Figure 11(a), Figure 11(b) Figure 12 or Figure 13 The method shown.

[0334] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce a good effect.

[0335] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A communication method, characterized in that, The method includes: The multi-link ML entity executes a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2; The ML entity transmits a first physical layer protocol data unit (PPDU) on each of the N second links. The second link is a first link whose backoff process ended before the first moment and which was idle during a first interval before the first moment. N is a positive integer less than K. The first moment is the end time of the backoff process of the target link among the K first links. The target link is the last second link among the N second links to end its backoff process.

2. The communication method according to claim 1, characterized in that, The ML entity transmits the first PPDU on each of the N second links, including: The ML entity simultaneously transmits the first PPDU on each of the N second links.

3. The communication method according to claim 1 or 2, characterized in that, Each of the K first links is equipped with a backoff counter.

4. The communication method according to claim 1 or 2, characterized in that, The first PPDU transmitted on different second links among the N second links is different.

5. A multi-link ML entity, characterized in that, The ML entity includes a processing unit and a communication unit; The processing unit is configured to execute a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2. The communication unit is used to send a first physical layer protocol data unit (PPDU) on each of the N second links. The second link is a first link whose backoff process ended before the first moment and which was idle during a first interval before the first moment. N is a positive integer less than K. The first moment is the end time of the backoff process of the target link among the K first links. The target link is the last second link among the N second links to end its backoff process.

6. The ML entity according to claim 5, characterized in that, The communication unit is specifically used to simultaneously transmit the first PPDU on each of the N second links.

7. The ML entity according to claim 5 or 6, characterized in that, Each of the K first links is equipped with a backoff counter.

8. The ML entity according to claim 5 or 6, characterized in that, The first PPDU transmitted on different second links among the N second links is different.

9. The ML entity according to claim 5 or 6, characterized in that, The ML entity is a multi-site STA entity, or the ML entity includes multiple STAs.

10. A chip, characterized in that, The chip includes a processing circuit and transceiver pins; the processing circuit is used to execute a backoff procedure on each of the K first links, where K is a positive integer greater than or equal to 2; the transceiver pins are used to transmit a first physical layer protocol data unit (PPDU) on each of the N second links, where the second link is a first link whose backoff procedure ended before a first time and is in an idle state during a first interval before the first time, where N is a positive integer less than K; the first time is the end time of the backoff procedure of the target link among the K first links, where the target link is the last second link among the N second links to end its backoff procedure.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes computer instructions that, when executed on a computer, cause the computer to perform the communication method as described in any one of claims 1 to 4.

12. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed on a computer, cause the computer to perform the communication method as described in any one of claims 1 to 4.

Images