Communication protection method and device
By updating the target network allocation vector and managing the backoff counter, the problem of asynchronous signal reception and transmission by ML entities on multiple links is solved, achieving synchronous communication and efficient utilization of multiple links.
Patent Information
- Application Number
- CN201910606221.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2019-07-05
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2039-07-05
AI Technical Summary
The problem of ML entities receiving and sending signals out of sync on multiple links leads to signal interference and communication anomalies.
By updating and managing the Target Network Allocation Vector (NAV) and backoff counter, ML entities are ensured to send and receive signals synchronously on multiple links, thus avoiding signal interference.
It enables synchronous communication of ML entities across multiple links, improving communication efficiency and link utilization, and avoiding signal interference and delays.
Smart Images

Figure CN112188640B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a communication protection method and device. Background Art
[0002] In order to achieve the technical goal of extremely high throughput, the Institute of Electrical and Electronics Engineers (IEEE) 802.11be standard uses multi-link (ML) as one of the key technologies. ML entities that support ML technology have the ability to send and receive in multiple frequency bands, so that ML entities can use a larger bandwidth for data transmission, which is conducive to significantly improving throughput. Among them, the spatial path for ML entities to transmit data on a frequency band can be called a link.
[0003] When the frequency intervals between multiple frequency bands supported by the ML entity are close, the ML entity sending a signal on one frequency band will affect the ML entity receiving a signal on another frequency band, affecting the normal communication of the ML entity. Currently, the industry has not yet proposed a corresponding solution to the problem of asynchronous reception and transmission of the ML entity on multiple links. Summary of the invention
[0004] The present application provides a communication protection method and device for solving the problem of asynchronous reception and transmission of an ML entity on multiple links.
[0005] In a first aspect, a communication protection method is provided, which is applied to an ML entity, and the ML entity supports multiple links. The method includes: the ML entity intercepts a first physical layer protocol data unit (PPDU) on a first link; if the first PPDU is an intra-BSS PPDU, and the value of the duration field of the first PPDU is greater than the value of the target NAV of the second link, the ML entity updates the value of the target network allocation vector (NAV) of the second link to the value of the duration field of the first PPDU, and the second link is any one of the multiple links supported by the ML entity except the first link.
[0006] Based on the above technical solution, if the ML entity intercepts the first PPDU sent by other sites in the intra-BSS on the first link, and the value of the duration field of the first PPDU is greater than the value of the target NAV of the second link, the ML entity updates the value of the target NAV of the second link to the value of the duration field of the first PPDU, thereby ensuring that after the first PPDU is transmitted, the ML entity will not send the PPDU within the duration indicated by the duration field of the first PPDU, thereby preventing other ML entities in the same BSS from receiving a PPDU on one link and sending a PPDU on another link at the same time, that is, it can ensure that other ML entities can send / receive signals synchronously on multiple links.
[0007] In one possible design, the method also includes: if the first PPDU is an inter-BSS PPDU, the ML entity does not update the value of the target NAV of the second link; or, if the first PPDU is an intra-BSS PPDU and the value of the duration field of the first PPDU is less than or equal to the value of the target NAV of the second link, the ML entity does not update the value of the target NAV of the second link.
[0008] In a possible design, the method further includes: the ML entity detects a contention-free end (CF-End) frame on the first link; if the CF-end frame is an intra-BSS PPDU, and the value of the target NAV of the second link is updated according to the value of the duration field of the first PPDU, the ML entity sets the value of the target NAV of the second link to 0. It should be understood that the target NAV of the second link of the ML entity is updated according to the value of the duration field of the first PPDU detected on the first link to ensure that the ML entity does not send data on the second link, so as to avoid affecting the communication of other ML entities in the same BSS on the first link. In this case, if the ML entity detects a CF-End frame in the same BSS on the first link, it means that the communication of other ML entities in the same BSS on the first link has ended, so the ML entity can set the value of the target NAV to 0, so that the virtual carrier monitoring of the ML entity on the second link is not affected by the communication on the first link, avoiding delays in the channel contention of the ML entity on the second link, which is conducive to improving the utilization rate of the ML entity on the second link.
[0009] In a possible design, the method further includes: if the ML entity does not detect the second PPDU on the first link within a preset time length, and the value of the target NAV of the second link is updated according to the value of the duration field of the first PPDU, the ML entity resets the target NAV of the second link, and the second PPDU and the first PPDU come from the same site. It should be understood that if the ML entity does not detect the second PPDU sent by the sender of the first PPDU on the first link within the preset time length, it means that the sender of the first PPDU may not occupy the channel on the first link, so the ML entity can initiate channel competition on the first link to send the first PPDU on the first link. In this case, if the target NAV is updated according to the value of the duration field of the first PPDU, the ML entity resets the target NAV so that the virtual carrier monitoring of the ML entity on the second link is not affected by the communication on the first link, avoiding delays in the channel competition of the ML entity on the second link, which is conducive to improving the utilization rate of the second link by the ML entity.
[0010] In one possible design, the ML entity resets the target NAV of the second link, including: the ML entity sets the value of the target NAV of the second link to 0; or, the ML entity sets the value of the target NAV of the second link to a first value, the end time determined by the first value is the same as the end time determined by the second value, and the second value is the value of the target NAV before the target NAV is updated according to the value of the duration field of the first PPDU.
[0011] In one possible design, the preset duration = (2×aSIFSTime) + (first PPDU response frame transmission duration) + aRxPHYStartDelay + (2×aSlotTime), where aSIFSTime represents the duration of the short inter-frame space (SIFS), aRxPHYStartDelay represents the duration of the preset delay, and aSlotTime represents the duration of a time slot.
[0012] In one possible design, the first PPDU carries a request to send (RTS) frame, and the response frame is a clear to send (CTS) frame.
[0013] In one possible design, if the ML entity is an ML non-access point (non-AP) entity, the target NAV includes one of the following situations: (1) if the ML non-AP entity is configured with intra-BSS NAV and basic NAV on the second link, the target NAV is the intra-BSS NAV; (2) if the ML non-AP entity is configured with intra-BSS NAV, basic NAV, and a first NAV on the second link, the target NAV is the first NAV.
[0014] In a possible design, if the ML entity is an ML access point (AP) entity, the target NAV includes one of the following situations: (1) if the ML AP entity is configured with intra-BSS NAV and basic NAV on the second link, the target NAV is the intra-BSS NAV; (2) if the ML AP entity is configured with only intra-BSS NAV, basicNAV and the first NAV on the second link, the target NAV is the first NAV; (3) if the ML AP entity is configured with the first NAV and the second NAV on the second link, the target NAV is the first NAV.
[0015] In a second aspect, a communication protection method is provided, which is applied to an ML entity, and the ML entity supports multiple links. The method includes: the ML entity sends a first PPDU on a first link, the first PPDU includes a duration field, and the duration field included in the first PPDU is used to indicate the duration of a first time period; the ML entity sends a MAC frame on a second link, the media access control (MAC) frame is used to indicate the duration of a second time period, the end time of the first time period is the same as the end time of the second time period, and the intra-BSS station on the second link is prohibited from sending a second PPDU during the second time period, and the second link is any one of the multiple links supported by the ML entity except the first link.
[0016] Based on the above technical solution, when the ML entity sends a PPDU on the first link, the ML entity sends a MAC frame on the second link, so that other stations in the same BSS on the second link will not send a PPDU before the end of the first time period. In this way, it is ensured that the ML entity will not send a PPDU on the first link and receive a PPDU on the second link, and it is ensured that the ML entity can send / receive signals synchronously on multiple links.
[0017] In a possible design, the MAC frame is an announcement frame or a quiet time period (QTP) frame.
[0018] In one possible design, the value of the duration field of the announcement frame is equal to the length of the second time period. The duration field of the announcement frame is used to set the value of the NAV maintained by the sites of the intra-BSS. The duration field of the announcement frame is not used to set the value of the NAV maintained by the sites of the overlapping basic service set (OBSS).
[0019] In one possible design, the announcement frame includes a duration field and a length field. The length field is used to set the value of the NAV maintained by the intra-BSS site. The value of the duration field is 0, and the value of the length field is equal to the length of the second time period.
[0020] In a third aspect, a communication protection method is provided, which is applied to an ML entity, and the ML entity supports multiple links. The method includes: the ML entity detects the start of a PPDU on a first link; the ML entity stops counting a first backoff counter on a second link, and the second link is any one of the multiple links supported by the ML entity except the first link; the ML entity determines whether the PPDU is an intra-BSS PPDU or an inter-BSS PPDU; if the PPDU is an intra-BSS PPDU, the ML entity continues to back off on the second link after the PPDU transmission is completed; if the PPDU is an inter-BSS PPDU, the ML entity continues to back off on the second link.
[0021] Based on the above technical solution, after the ML entity detects the start of the PPDU on the first link, the ML entity suspends the counting of the first backoff counter on the second link. In the case where the PPDU is an intra-BSS PPDU, the ML entity continues to back off after the PPDU is transmitted. Therefore, during the PPDU transmission process on the first link, the ML entity will not send the PPDU on the second link, thereby avoiding the situation where other ML entities in the same BSS receive signals on the first link and send signals on another link. In addition, when the ML entity determines that the PPDU is an inter-BSS PPDU, the ML entity immediately continues to back off, thereby ensuring that the ML entity can perform channel access normally on the second link.
[0022] In one possible design, the ML entity continues to back off on the second link after the PPDU transmission is completed, including: the ML entity continues to back off on the second link after a first moment, and the first moment is the end moment of the transmission of the PPDU; or, the ML entity continues to back off on the second link after a second moment, and the second moment is the end moment of the transmission of the response frame corresponding to the PPDU; or, the ML entity continues to back off on the second link after a third moment, and the third moment is the end moment determined by the duration field of the PPDU.
[0023] In one possible design, after the ML entity stops counting the first backoff counter on the second link, the method also includes: the ML entity configures a second backoff counter on the second link, and the initial value of the second backoff counter is the current value of the first backoff counter; if the second link is in an idle state at the current moment, then whenever the second link is in an idle state within a time slot, the ML entity subtracts 1 from the count value of the second backoff counter; if the second link is in a busy state at the current moment, the ML entity waits for the idle time of the second link to reach a second inter-frame interval; after the idle time of the second link reaches the second inter-frame interval, then whenever the second link is in an idle state within a time slot, the ML entity subtracts 1 from the count value of the second backoff counter.
[0024] In one possible design, the method further includes: after the count value of the second backoff counter is reduced to 0, the ML entity maintains the count value of the second backoff counter as 0.
[0025] In one possible design, the method further includes: when the count value of the second backoff counter decreases to 0, the ML entity resets the count value of the second backoff counter.
[0026] In one possible design, the ML entity resets the count value of the second backoff counter, including: the ML entity resets the count value of the second backoff counter according to the doubled contention window; or, the ML entity resets the count value of the second backoff counter according to the contention window; or, the ML entity resets the count value of the second backoff counter according to the minimum value of the contention window.
[0027] In one possible design, if the PPDU is an inter-BSS PPDU, the ML entity continues to back off on the second link, including: if the PPDU is an inter-BSS PPDU, the ML entity updates the count value of the first backoff counter with the count value of the second backoff counter, and continues to back off on the second link based on the first backoff counter. Based on this design, when the ML entity determines that the PPDU is an inter-PPDU, the ML entity sets the count value of the first backoff counter with the count value of the second backoff counter, so that the first backoff counter is not affected by the previous suspension. In this way, in the case where the PPDU is an inter-BSS PPDU, the backoff process of the ML entity on the second link is not affected, thereby avoiding the ML entity from being at a disadvantage in channel competition and ensuring the ML entity's use of the second link.
[0028] In a fourth aspect, a communication protection method is provided, which is applied to an ML non-AP entity, and the ML non-AP entity supports multiple links. The method includes: the ML non-AP entity detects a first PPDU on a first link; if the receiving end of the first PPDU is an ML AP entity associated with the ML non-AP entity, the ML non-AP entity sends a second PPDU on a second link, the second link is any one of the multiple links supported by the ML non-AP entity except the first link, and the end time of the first PPDU is the same as the end time of the second PPDU.
[0029] Based on the above technical solution, if the ML non-AP entity detects the first PPDU on the first link, and the first PPDU is sent to the ML AP entity associated with the ML non-AP entity, the ML non-AP entity sends the second PPDU on the second link. Since the end time of the second PPDU is the same as the end time of the first PPDU, the ML AP entity can send the block ack (BA) frame of the second PPDU and the BA frame of the first PPDU at the same time. In this way, on the one hand, it avoids the situation where the ML AP entity sends a signal on one link and receives a signal on another link. On the other hand, the ML non-AP entity sends the second PPDU on the second link, which is conducive to improving the utilization rate of the second link.
[0030] In one possible design, the ML non-AP entity sends a second PPDU on the second link, including: the ML non-AP entity performs a backoff procedure on the second link; after the backoff procedure on the second link ends, the ML non-AP entity sends the second PPDU on the second link.
[0031] In a fifth aspect, an ML entity is provided, which may include a module for executing a method / operation / step / action described in any one of the designs of the first aspect to the fourth aspect. The above module may be a hardware circuit, or software, or implemented in combination with a hardware circuit and software.
[0032] In a sixth aspect, an ML entity is provided, the ML entity comprising a processor and a transceiver, the processor being used to perform the processing operation in the communication protection method involved in any one of the designs of the first to fourth aspects. The transceiver is used to accept the control of the processor and perform the transceiver operation in the communication protection method involved in any one of the designs of the first to fourth aspects.
[0033] In the seventh aspect, a computer-readable storage medium is provided, which is used to store instructions. When the instructions are read by a computer, the computer is used to execute the communication protection method involved in any one of the designs in the first to fourth aspects above.
[0034] In an eighth aspect, a computer program product is provided, the computer program product comprising instructions. When a computer reads the instructions, the computer executes the communication protection method involved in any possible design of the first to fourth aspects.
[0035] In a ninth aspect, a chip is provided, the chip comprising a processing circuit and a transceiver pin. The chip supports multiple links. The transceiver pin is used to detect a first PPDU on a first link. The processing circuit is used to update the value of the target NAV of the second link to the value of the duration field of the first PPDU when the first PPDU is an intra-BSSPPDU and the value of the duration field of the first PPDU is greater than the value of the target NAV of the second link, and the second link is any one of the multiple links supported by the ML entity except the first link.
[0036] In a tenth aspect, a chip is provided, which includes a processing circuit and a transceiver pin. The chip supports multiple links. The transceiver pin is used to send a first PPDU on a first link, and the first PPDU includes a duration field. The duration field included in the first PPDU is used to indicate the duration of a first time period. The transceiver pin is also used to send a MAC frame on a second link, and the MAC frame is used to indicate the duration of a second time period. The end time of the first time period is the same as the end time of the second time period. The intra-BSS station on the second link is prohibited from sending a second PPDU during the second time period. The second link is any one of the multiple links supported by the ML entity except the first link.
[0037] In the eleventh aspect, a chip is provided, which includes a processing circuit and a transceiver pin. The chip supports multiple links. The transceiver pin is used to detect the start of the PPDU on the first link. The processing circuit is used to stop the counting of the first backoff counter on the second link and determine whether the PPDU is an intra-BSS PPDU or an inter-BSS PPDU; if the PPDU is an intra-BSS PPDU, after the PPDU transmission is completed, continue to back off on the second link; if the PPDU is an inter-BSS PPDU, continue to back off on the second link. The second link is any one of the multiple links supported by the chip except the first link.
[0038] In a twelfth aspect, a chip is provided, the chip comprising a processing circuit and a transceiver pin. The chip supports multiple links, and the transceiver pin is used to detect a first PPDU on a first link. The transceiver pin is also used to send a second PPDU on a second link when the receiving end of the first PPDU is an associated ML AP entity, the second link is any one of the multiple links supported by the ML non-AP entity except the first link, and the end time of the first PPDU is the same as the end time of the second PPDU.
[0039] Among them, the technical effects brought about by any design in the fifth to twelfth aspects can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0040] Figure 1 A schematic diagram of a backoff process provided in an embodiment of the present application;
[0041] Figure 2 A schematic diagram of a PPDU frame structure provided in an embodiment of the present application;
[0042] Figure 3 A schematic diagram of a communication scenario between ML entities provided in an embodiment of the present application;
[0043] Figure 4 A schematic diagram of an ML communication scenario provided in an embodiment of the present application;
[0044] Figure 5 A schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0045] Figure 6 A flow chart of a communication protection method provided in an embodiment of the present application;
[0046] Figure 7 A schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0047] Figure 8 A flowchart of another communication protection method provided in an embodiment of the present application;
[0048] Fig. 9 A flowchart of another communication protection method provided in an embodiment of the present application;
[0049] Fig.10 A flowchart of another communication protection method provided in an embodiment of the present application;
[0050] Fig.11 A schematic diagram of a frame structure of an announcement frame provided in an embodiment of the present application;
[0051] Fig.12 A schematic diagram of a frame structure of an announcement frame provided in an embodiment of the present application;
[0052] Fig.13 A schematic diagram of a frame structure of a frame announcement frame provided in an embodiment of the present application;
[0053] Fig.14 A schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0054] Fig.15 A flowchart of another communication protection method provided in an embodiment of the present application;
[0055] FIG16( a ) is a schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0056] FIG16( b ) is a schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0057] FIG16( c ) is a schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0058] FIG16( d ) is a schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0059] FIG16( e) is a schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0060] FIG16( f) is a schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0061] FIG16( g) is a schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0062] Fig.17 A flowchart of another communication protection method provided in an embodiment of the present application;
[0063] Fig.18 A flowchart of another communication protection method provided in an embodiment of the present application;
[0064] Fig.19 A flow chart of a communication protection method provided in an embodiment of the present application;
[0065] Fig. 20 A schematic diagram of another ML communication scenario provided in an embodiment of the present application;
[0066] Fig.21 A schematic diagram of the structure of an ML entity provided in an embodiment of the present application;
[0067] Fig. 22 A schematic diagram of the structure of an ML entity provided in an embodiment of the present application. DETAILED DESCRIPTION
[0068] In the description of this application, unless otherwise specified, " / " means "or", for example, A / B can mean A or B. "And / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, "at least one" means one or more, and "plurality" means two or more. The words "first", "second", etc. do not limit the quantity and execution order, and the words "first", "second", etc. do not limit them to be different.
[0069] It should be noted that, in this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in this application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.
[0070] In order to facilitate understanding of the technical solution of the present application, the following is a brief introduction to the terms involved in the present application.
[0071] 1. Basic service set (BSS)
[0072] BSS is used to describe a group of devices that can communicate with each other in a wireless local area network (WLAN). A WLAN can include multiple BSSs. Each BSS has a unique identifier, called a basic service set identifier (BSSID).
[0073] A BSS may include multiple stations (STAs). Stations include APs and non-access point stations (non-AP STAs). Optionally, a BSS may include an AP and multiple non-AP STAs associated with the AP.
[0074] AP is also called wireless access point or hotspot. AP can be a wireless router, wireless transceiver, wireless switch, etc.
[0075] Non-AP STA can have different names, such as user unit, access terminal, mobile station, mobile station, mobile device, terminal, user equipment, etc. In practical applications, STA can be a cellular phone, smart phone, wireless local loop (WLL), and other handheld devices and computer devices with wireless LAN communication function.
[0076] 2. Backoff mechanism
[0077] The IEEE 802.11 standard supports multiple users sharing the same transmission medium, and the sender detects the availability of the transmission medium before sending data. The IEEE 802.11 standard uses carrier sense multiple access with collision avoidance (CSMA / CA) to implement channel competition. In order to avoid collisions, CSMA / CA uses a backoff mechanism.
[0078] The backoff mechanism on a single channel is described below. Before a device sends a message, it can select a random number from 0 to the contention window (CW) and use the random number as the initial value of the backoff counter. After the idle time of the channel reaches the arbitration interframe space (AIFS), the count value of the backoff counter is reduced by 1 each time the channel is idle for a timeslot. Before the count value of the backoff counter is reduced to 0, if the channel is busy in a timeslot, the backoff counter will pause counting. Afterwards, if the channel changes from a busy state to an idle state, and the idle time of the channel reaches AIFS, the backoff counter will resume counting. When the count value of the backoff counter reaches 0, the backoff process ends and the device can start data transmission.
[0079] Combination Figure 1For example, assume that the initial value of the backoff counter is 5. After the idle time of the channel reaches AIFS, the backoff counter starts to back off. Whenever the channel is idle in a time slot, the count value of the backoff counter is reduced by 1 until the count value of the backoff counter is 0. After the count value of the backoff counter is 0, the device can send PPDU on the channel.
[0080] 3. NAV
[0081] NAV is used in virtual carrier sensing. NAV is equivalent to a counter that records the time a station occupies a channel. The value of NAV will decrease over time, but before the value of NAV decreases to zero, the station always considers the channel busy and stops channel contention and data transmission.
[0082] Currently, non-AP STA has two NAVs, namely intra-NAV and basic NAV. Intra-NAV is updated according to intra-BSS PPDU. Basic NAV is updated according to inter-BSS PPDU, or according to PPDU that cannot be classified as intra-BSS or inter-BSS.
[0083] An AP may have two NAVs or only one AP. When an AP is configured with two NAVs, the two NAVs of the AP are intra-NAV and basic NAV.
[0084] It should be understood that in a densely deployed scenario, it is beneficial for a station to maintain two NAVs. By maintaining two NAVs, a station can protect frames sent by intra-BSS stations and avoid interference from frames sent by inter-BSS stations.
[0085] 4. PPDU
[0086] like Figure 2Figure 1 is a schematic diagram of the frame structure of the PPDU in the 802.11ax standard. The PPDU includes: legacy-short training field (L-STF), legacy-long training field (L-LTF), legacy signaling field (L-SIG), repeated legacy signaling field (RL-SIG), high efficient-signal field A (HE-SIG A), high efficient-signal field B (HE-SIG B), high efficient-short training field (HE-STF), high efficient-long training field (HE-LTF), data, and packet extension (PE).
[0087] Among them, L-STF is used for automatic gain control, sequence synchronization and coarse frequency offset estimation.
[0088] 5. intra-BSS PPDU, inter-BSS PPDU
[0089] For a station, if the BSS to which the PPDU intercepted by the station belongs is the same BSS as the BSS associated with the station, or the receiver / transmitter of the PPDU intercepted by the station belongs to the same BSS as the station, then the PPDU is an intra-BSS PPDU. Exemplarily, if the BSS color / BSSID in the PPDU intercepted by the station is the same as the BSS color / BSSID of the BSS associated with the station, then the PPDU is an intra-BSS PPDU.
[0090] For a station, if the BSS to which the PPDU intercepted by the station belongs is not the same BSS as the BSS associated with the station, or the receiver / sender of the PPDU intercepted by the station does not belong to the same BSS as the station, then the PPDU is an inter-BSS PPDU. Exemplarily, if the BSS color / BSSID in the PPDU intercepted by the station is different from the BSS color / BSSID of the BSS associated with the station, then the PPDU is an inter-BSS PPDU.
[0091] The method for the above-mentioned station to determine whether the PPDU is an intra-BSS PPDU or an inter-BSS PPDU is only an example, and a detailed description can be referred to the prior art.
[0092] 6. ML Entities
[0093] The ML entity has the ability to send and receive on multiple frequency bands. Exemplarily, the multiple frequency bands include but are not limited to: 2.4 GHz frequency band, 5 GHz frequency band, and 6 GHz frequency band. The spatial path for the ML entity to perform data transmission on a frequency band can be called a link. In other words, the ML entity supports multi-link communication.
[0094] It should be understood that, for an ML entity, each link supported by the ML entity corresponds to a frequency band.
[0095] The ML entity may also be referred to as an ML STA entity. The ML entity includes multiple STAs. Each STA in the ML entity may establish a link for communication. Figure 3 As shown, ML entity A includes site A1-site AN, and ML entity B includes site B1-site BN. Site A1 and site B1 communicate via link 1, site A2 and site B2 communicate via link 2, and so on, site AN and site BN communicate via link N.
[0096] It should be noted that multiple STAs in the ML entity may have the same MAC address or different MAC addresses. Multiple STAs in the ML entity may be located in the same physical location or in different physical locations.
[0097] If the STA in the ML entity is an AP, the ML entity can be called an ML AP entity. If the STA in the ML entity is a non-AP STA, the ML entity can be called an ML non-AP STA entity, or an ML non-AP entity. In the embodiments of the present application, unless otherwise specified, the ML entity can be either an ML AP entity or an ML non-AP entity.
[0098] A non-AP STA on a link in the ML non-AP entity may be associated with an AP on the same link in the ML AP entity, so that a non-AP STA on a link in the ML non-AP entity may communicate with an AP on the same link in the ML AP entity.
[0099] It should be understood that an association relationship may be established between the ML AP entity and the ML non-AP entity to ensure normal communication between the ML AP entity and the ML non-AP entity.
[0100] It should be noted that the association relationship between the ML AP entity and the ML non-AP entity includes: an association relationship between a station of the ML AP entity on a link and a station of the ML non-AP entity on the same link.
[0101] The embodiment of the present application does not limit the implementation method of establishing an association relationship between the ML non-AP entity and the ML AP entity. For example, the ML non-AP entity and the ML AP entity establish an association relationship on one link; or, the ML non-AP entity and the ML AP entity establish an association relationship between the ML non-AP entity and the ML AP entity on multiple links on one link.
[0102] The ML non-AP entity establishes an association relationship on a link with the ML AP entity. The specific implementation method thereof may refer to the implementation method of establishing an association relationship between an AP and a non-AP STA in the prior art, which will not be described in detail herein.
[0103] 7. SL Entity
[0104] The SL entity refers to a STA that supports only one link. The SL entity may be a legacy STA, that is, a STA that only supports the existing 802.11 standard but not the next generation 802.11 standard.
[0105] The above is a brief introduction to the technical terms involved in this application, which will not be repeated below.
[0106] The following uses an example to illustrate the situation where the ML entity receives and sends asynchronously on multiple links.
[0107] Combination Figure 4 For example, the ML AP entity sends PPDU#1 to the ML non-AP entity 1 on the first link. Since the ML non-AP entity 2 does not know that the ML AP entity is sending PPDU#1 on the first link, the ML non-AP entity 2 may send PPDU#2 to the ML AP entity on the second link. In this case, the ML AP entity sending PPDU#1 on the first link will affect the ML AP entity receiving PPDU#2 on the second link, resulting in the failure of PPDU#2 transmission.
[0108] Combination Figure 5For example, ML non-AP entity 1 sends PPDU to ML AP entity on the first link. Since ML non-AP entity 2 does not know that ML non-AP entity 1 is sending PPDU#1 on the first link, ML non-AP entity 2 may send PPDU#2 to ML AP entity on the second link. The transmission time of PPDU#2 is shorter than the transmission time of PPDU#1. If ML AP entity sends BA frame on the second link, it will affect ML entity's reception of PPDU#1 on the first link, resulting in PPDU#1 transmission failure. If ML AP does not send BA frame on the second link, ML non-AP entity 2 will think that PPDU#2 transmission failed because it did not receive BA frame.
[0109] It should be understood that the ML entity receives and sends signals asynchronously on multiple links, which specifically means that the ML entity sends signals on some links while receiving signals on another part of the links.
[0110] Since the ML entity sending a signal on one link will affect the ML entity receiving a signal on another link, it is necessary to avoid the ML entity receiving and sending asynchronously on multiple links. To address this technical problem, the embodiment of the present application provides the following technical solution, the specific content of which can be found below.
[0111] The technical solution of the present application is applied to WLAN, and the standard adopted by WLAN may be the IEEE 802.11 standard, such as the 802.11ax standard, and the next generation 802.11 standard, etc. The technical solution of the present application is applicable to the following scenarios: communication scenarios between ML entities and ML entities, and communication scenarios between ML entities and SL entities.
[0112] Exemplarily, the communication scenario between ML entities may be: a communication scenario between an ML non-AP entity and an ML AP entity; or a communication scenario between an ML non-AP entity and an ML non-AP entity; or a communication scenario between an ML AP entity and an ML AP entity.
[0113] Exemplarily, the communication scenario between the ML entity and the SL entity may be: a communication scenario between the ML non-AP entity and a traditional AP; or, a communication scenario between the ML AP entity and a traditional non-AP STA; or, a communication scenario between the ML AP entity and a traditional AP; or, a communication scenario between the ML non-AP entity and a traditional non-AP STA.
[0114] The technical solution provided in the embodiments of the present application is described in detail below in conjunction with the accompanying drawings.
[0115] like Figure 6 As shown, a communication protection method provided in an embodiment of the present application comprises the following steps:
[0116] S101. An ML entity detects a first PPDU on a first link.
[0117] The ML entity may support multiple links. The first link is any one of the multiple links supported by the ML entity.
[0118] As an implementation manner, a station of a first link of the ML entity detects a first PPDU on the first link.
[0119] S102. The ML entity determines whether the first PPDU is an intra-BSS PPDU or an inter-BSS PPDU.
[0120] As an implementation method, the station of the first link of the ML entity determines whether the first PPDU is an intra-BSS PPDU or an inter-BSS PPDU. The method for determining whether the first PPDU is an intra-BSS PPDU or an inter-BSS PPDU can refer to the prior art and will not be repeated here.
[0121] In the case where the first PPDU is an intra-BSS PPDU, the ML entity performs the following step S103. In the case where the first PPDU is an inter-BSS PPDU, the ML entity performs the following step S105.
[0122] S103: When the first PPDU is an intra-BSS PPDU, the ML entity determines whether a value of a duration field of the first PPDU is greater than a current value of a target NAV of the second link.
[0123] The second link is a link other than the first link among the multiple links supported by the ML entity. That is, the first link and the second link are two different links.
[0124] It should be noted that the value of the duration field of the first PPDU is used to indicate the time that the transmitter of the first PPDU occupies the channel on the first link.
[0125] In the embodiment of the present application, the target NAV of the second link can be used to record the time when the station is prohibited from actively initiating contention on the second link. The target NAV of the second link can reuse the NAV in the current standard, or can be a newly configured NAV.
[0126] Optionally, when the ML entity is an ML non-AP entity, the target NAV of the second link may adopt one of the following situations:
[0127] Scenario 1: The target NAV of the second link multiplexes the intra-NAV of the second link. In this case, on the second link, the ML non-AP entity includes: intra-NAV and basic NAV.
[0128] Scenario 2: The target NAV of the second link is a newly configured NAV. In this case, on the second link, the MLnon-AP entity includes: intra-NAV, basic NAV, and first NAV. The first NAV is the target NAV, and the first NAV can also be called ML NAV.
[0129] Optionally, when the ML entity is an ML AP entity, the target NAV of the second link may adopt one of the following situations:
[0130] Scenario 1: The target NAV of the second link multiplexes the intra-NAV of the second link. In this case, on the second link, the ML AP entity includes: intra-NAV and basic NAV.
[0131] Scenario 2: The target NAV of the second link is a newly configured NAV. In this case, on the second link, the ML AP entity includes: intra-NAV, basic NAV, and the first NAV; or, the ML AP entity includes: the first NAV and the second NAV. The first NAV is the target NAV. The second NAV is the NAV configured by the AP in the scenario where the AP is only configured with one NAV in the current standard.
[0132] It should be noted that on a link, if the ML entity is configured with multiple NAVs, and the value of any of the multiple NAVs is not 0, the result of the virtual carrier sensing is that the link is busy, so the backoff process of the ML entity on the link is suspended, and the ML entity cannot send PPDU on the link.
[0133] As an implementation method, the station of the second link of the ML entity obtains the judgment result of the station of the first link of the ML entity on whether the first PPDU is an intra-BSS PPDU. In the case that the first PPDU is an intra-BSS PPDU, the station of the second link of the ML entity further obtains the value of the duration field of the first PPDU from the station of the first link of the ML entity. Afterwards, the station of the second link of the ML entity determines whether the value of the duration field of the first PPDU is greater than the current value of the target NAV of the second link.
[0134] If the value of the duration field of the first PPDU is greater than the current value of the target NAV of the second link, the ML entity performs the following step S104. If the value of the duration field of the PPDU is less than or equal to the current value of the target NAV of the second link, the ML entity performs the following step S105.
[0135] S104: When the value of the duration field of the first PPDU is greater than the value of the target NAV of the second link, the ML entity updates the value of the target NAV of the second link to the value of the duration field of the first PPDU.
[0136] As an implementation method, the station of the second link of the ML entity updates the value of the target NAV of the second link to the value of the duration field of the first PPDU. For example, if the current value of the target NAV of the second link is 10 and the value of the duration field of the first PPDU is 12, the station of the second link of the ML entity updates the value of the target NAV of the second link to 12.
[0137] S105. The ML entity does not update the value of the target NAV of the second link.
[0138] As an implementation manner, the station of the second link of the ML entity does not update the value of the target NAV of the second link.
[0139] based on Figure 6 In the technical solution shown, if the ML entity intercepts the first PPDU sent by other sites in the intra-BSS on the first link, and the value of the duration field of the first PPDU is greater than the value of the target NAV of the second link, the ML entity updates the value of the target NAV of the second link to the value of the duration field of the first PPDU, thereby ensuring that after the transmission of the first PPDU is completed, the ML entity will not send the PPDU within the duration indicated by the duration field of the first PPDU, thereby preventing other ML entities in the same BSS from receiving a PPDU on one link and sending a PPDU on another link at the same time, thereby ensuring normal communication of other ML entities in the same BSS.
[0140] Combination Figure 7For example, ML non-AP entity 1 detects PPDU#1 on the first link, and PPDU#1 is sent by MLAP to ML non-AP entity 2. The station of the first link of ML non-AP entity 1, the station of the first link of ML non-AP entity 2, and the station of the first link of ML AP entity belong to the same BSS. In this case, ML non-AP entity 1 sets the target NAV of the second link according to the value of the duration field of PPDU#1. Therefore, before the value of the target NAV reaches 0, ML non-AP entity 1 will not send PPDU to ML AP entity on the second link. Therefore, when ML AP entity sends PPDU#1 to ML non-AP entity 2 on the first link, ML AP entity does not need to receive PPDU#2 on the second link. In this way, normal communication of ML AP entity is guaranteed. It should be noted that the target NAV of the second link is not necessarily set after the transmission of PPDU#1 is completed using the value of the duration field of PPDU#1. If the value of the duration field can be obtained during the transmission of PPDU#1, the target NAV of the second link can be set immediately after the value of the duration is obtained. For example, when PPDU#1 carries an A-MPDU, the value of the duration can be obtained after the first MPDU is received; for example, if the SIG field of PPDU1 carries a TXOP Duration field, the value of the duration field can be obtained through the TXOP Duration field after the SIG field is received.
[0141] As an optional embodiment, based on Figure 6 The technical solution shown, such as Figure 8 As shown, after step S104, the communication protection method further includes steps S106-S107.
[0142] S106. The ML entity detects a CF-End frame on the first link.
[0143] The CF-End frame is used to indicate the end of the contention-free period. When the contention-free period ends, stations in the same BSS can initiate channel contention to access the channel.
[0144] As an implementation manner, a station of a first link of the ML entity detects a CF-End frame on the first link.
[0145] After hearing the CF-End frame, the station of the first link of the ML entity determines whether the CF-End frame is an intra-BSS PPDU. If the CF-End frame is an intra-BSS PPDU, the station in the intra-BSS does not occupy the channel on the first link, so the station of the first link of the ML entity can access the channel on the first link.
[0146] It can be understood that the CF-End frame is an intra-BSS PPDU, which indicates that the CF-End frame belongs to the BSS associated with the site of the first link of the ML entity.
[0147] Exemplarily, the site of the first link of the ML entity determines whether the CF-End frame is an intra-BSS PPDU, including: if the BSSID carried by the CF-End frame is the same as the BSSID of the BSS associated with the site of the first link of the ML entity, then the site of the first link of the ML entity can determine that the CF-End frame is an intra-BSS PPDU; otherwise, the site of the first link of the ML entity can determine that the CF-End frame is not an intra-BSS PPDU. It should be understood that there are other implementation methods for determining whether the CF-End frame is an intra-BSS PPDU, and the embodiments of the present application are not limited thereto.
[0148] S107: If the CF-End frame is an intra-BSS PPDU, and the value of the target NAV is updated according to the value of the duration field of the first PPDU, the ML entity sets the value of the target NAV of the second link to 0.
[0149] As an implementation manner, in the case where the CF-End frame is an intra-BSS PPDU, the station of the second link of the ML entity sets the value of the target NAV of the second link to 0.
[0150] based on Figure 8 In the technical solution shown, the target NAV of the second link of the ML entity is updated according to the value of the duration field of the first PPDU intercepted on the first link to ensure that the ML entity does not send data on the second link, so as to avoid affecting the communication of other ML entities in the same BSS on the first link. In this case, if the ML entity intercepts the CF-End frame in the same BSS on the first link, it means that the communication of other ML entities in the same BSS on the first link has ended, so the ML entity can set the value of the target NAV to 0, so that the virtual carrier monitoring of the ML entity on the second link is not affected by the communication on the first link, avoiding delays in the channel competition of the ML entity on the second link, which is conducive to improving the utilization rate of the second link by the ML entity.
[0151] As an optional embodiment, based on Figure 6 The technical solution shown, such as Fig. 9 As shown, after step S104, the communication protection method further includes step S108.
[0152] S108. If the ML entity does not detect the second PPDU on the first link within a preset duration, and the value of the target NAV of the second link is updated according to the value of the duration field of the first PPDU, the ML entity resets the target NAV of the second link.
[0153] The second PPDU and the first PPDU come from the same site.
[0154] In a specific implementation, if the ML entity does not detect any PPDU on the first link within a preset time, the ML entity determines that the second PPDU is not detected on the first link within the preset time. If the ML entity detects one or more PPDUs on the first link within the preset time, if the sending site of the one or more PPDUs is different from the sending site of the first PPDU, the ML entity determines that the first PPDU and the one or more PPDUs are from different sites, and then the ML entity determines that the second PPDU is not detected on the first link within the preset time.
[0155] Optionally, the preset duration=(2×aSIFSTime)+(transmission duration of the first PPDU response frame)+aRxPHYStartDelay+(2×aSlotTime).
[0156] Here, aSIFSTime indicates the duration of SIFS.
[0157] aSlotTime indicates the duration of a time slot. aSlotTime is usually 9 microseconds.
[0158] It should be understood that in the case where the first PPDU carries an RTS frame, the first PPDU response frame may be a CTS frame, in which case the transmission duration of the first PPDU response frame is the transmission duration of the CTS frame, usually recorded as CTS_Time. It should be noted that the transmission duration of the CTS frame may be determined based on the length of the CTS frame and the data transmission rate of the most recently received RTS frame used to update the NAV.
[0159] aRxPHYStartDelay indicates the duration of the preset delay, where the preset delay refers to the delay between the start of receiving the PPDU at the receiving antenna and the release of the primitive PHY-RXSTART.indication.
[0160] It should be noted that in different standards, aRxPHYStartDelay corresponds to different values. For example, in the IEEE802.11a standard, aRxPHYStartDelay is 20 microseconds. In the IEEE 802.11n standard, aRxPHYStartDelay is 28 microseconds. In the IEEE 802.11ax standard, aRxPHYStartDelay is 40 microseconds.
[0161] In the embodiment of the present application, the ML entity resets the target NAV of the second link by any of the following implementation methods:
[0162] Method 1: The ML entity sets the value of the target NAV of the second link to 0.
[0163] Method 2: The ML entity sets the value of the target NAV of the second link to the first value, the end time determined by the first value is the same as the end time determined by the second value, and the second value is the value of the target NAV before the target NAV is updated according to the value of the duration field of the first PPDU.
[0164] For example, at time T1, assuming that the value of the duration field of the first PPDU is L1, the current value of the target NAV of the second link is L2, and L1 is greater than L2, the ML entity updates the value of the target NAV of the second link to L1. In this case, the second value of the target NAV is L2, and the end time determined by the second value is the time T1+L2. After L3 time, at time T1+L3, if the ML entity sets the value of the target NAV of the second link to the first value, since the end time of the first value is also the time T1+L2, the first value is L2-L3.
[0165] based on Fig. 9 In the technical solution shown, if the ML entity does not detect the second PPDU sent by the sender of the first PPDU on the first link within the preset time, it means that the sender of the first PPDU may not occupy the channel on the first link, so the ML entity can initiate channel competition on the first link to send the first PPDU on the first link. In this case, if the target NAV is updated according to the value of the duration field of the first PPDU, the ML entity resets the target NAV so that the virtual carrier monitoring of the ML entity on the second link is not affected by the communication on the first link, avoiding delays in the channel competition of the ML entity on the second link, which is conducive to improving the utilization rate of the second link by the ML entity.
[0166] like Fig.10 As shown, a communication protection method provided in an embodiment of the present application comprises the following steps:
[0167] S201. An ML entity sends a first PPDU on a first link.
[0168] The ML entity may support multiple links. The first link may be any one of the multiple links supported by the ML entity.
[0169] It should be noted that the first PPDU includes a duration field. The duration field of the first PPDU is used to indicate the duration of the first time period. The first time period is the time period during which the ML entity occupies a channel on the first link. The start time of the first time period is the end time of transmission of the PPDU.
[0170] As an implementation manner, a station of a first link of the ML entity sends a PPDU on the first link.
[0171] S202. The ML entity sends a MAC frame on the second link.
[0172] The second link is a link other than the first link among the multiple links supported by the ML entity. That is, the first link and the second link are two different links.
[0173] The MAC frame is used to indicate the duration of the second time period. During the second time period, the intra-BSS station on the second link is prohibited from sending a second PPDU, and the second PPDU is different from the first PPDU. The start time of the second time period is the end time of the transmission of the MAC frame. The end time of the second time period is the same as the end time of the first time period.
[0174] In addition, the transmission start time and transmission end time of the MAC frame are both before the transmission end time of the first PPDU, so as to ensure that the intra-BSS station on the second link can receive the MAC frame before the transmission of the PPDU is completed, so that the intra-BSS station on the second link will not send the second PPDU within the first time period.
[0175] As an implementation manner, when the station of the second link of the ML entity learns that the station of the first link of the ML entity sends the first PPDU on the first link, the station of the second link of the ML entity sends a MAC frame on the second link.
[0176] In the embodiment of the present application, the MAC frame may be an announcement frame or a QTP frame. It should be noted that the announcement frame is a new type of control frame defined in the embodiment of the present application.
[0177] When the MAC frame is an announcement frame, the announcement frame has the following two implementation methods:
[0178] Method 1: The announcement frame includes a duration field and a length field.
[0179] The duration field of the announcement frame is used to set the value of the NAV maintained by the intra-BSS station on the second link. The duration field of the announcement frame is not used to set the value of the NAV maintained by the OBSS station on the second link.
[0180] That is, the intra-BSS station on the second link will read the duration field included in the announcement frame, and set the value of the NAV maintained by itself according to the value of the duration field included in the announcement frame. However, the OBSS station on the second link will not set the value of the NAV maintained by itself according to the value of the duration field of the announcement frame.
[0181] It should be noted that the site sets the value of the NAV maintained by itself according to the value of the duration field included in the announcement frame. Specifically, when the value of the duration field included in the announcement frame is greater than the value of the NAV maintained by the site itself, the site updates the value of the NAV to the value of the duration field. Otherwise, the site does not update the value of the NAV.
[0182] The intra-BSS site on the second link is a site that belongs to the same BSS as the site on the second link of the ML entity. The OBSS site on the second link is a site that does not belong to the same BSS as the site on the second link of the ML entity.
[0183] In an embodiment of the present application, the value of the duration field of the announcement frame is equal to the time length of the second time period, so that the intra-BSS station on the second link cannot access the channel at least during the second time period, so as to avoid the intra-BSS station on the second link interfering with the communication of the ML entity.
[0184] For example, Fig.11 A schematic diagram of an announcement frame provided in an embodiment of the present application. The announcement frame includes at least the following fields: frame control, duration, receiving address (RA), transmitting address (TA), ML transmission time, and frame check sequence (FCS).
[0185] Fig.11 The ML transmission duration field in the announcement frame shown is the duration field of the announcement frame mentioned above. That is, Fig.11The ML transmission duration field in the shown announcement frame is used to set the value of the NAV maintained by the station of the intra-BSS on the second link.
[0186] The frame control field also includes the following fields: protocol version, type, and subtype.
[0187] Optionally, in an embodiment of the present application, when the type field and the subtype field in a control frame take preset values, the control frame is the announcement frame provided in the embodiment of the present application.
[0188] Exemplarily, Table 1 shows the meanings of the type field and the subtype field under different values. As shown in Table 1, if the value of the type field of a control frame is 01 and the value of the subtype field is 0001, the control frame is an announcement frame.
[0189] Table 1
[0190] Type field value Type Description Subtype field value Subtype Description 01 control 0000 reserve 01 control 0001 ML Announcement 01 control 0010 Trigger …… …… …… ……
[0191] For example, Fig.12 A schematic diagram of an announcement frame provided in an embodiment of the present application. The announcement frame is a frame containing a new type of high throughput (HT) control field defined in the present application. Fig.11 As shown, the announcement frame includes one of the following fields: frame control, duration / identification, address 1, address 2, address 3, sequence control, address 4, quality of service (QoS) control, HT control, frame body, and FCS.
[0192] in, Fig.12 The duration / identification field of the announcement frame shown is equivalent to the duration field of the announcement frame mentioned above.
[0193] The HT control field includes one of the following fields: a control ID and control information. The value of the control ID field is a preset value to indicate that the HT control frame is an announcement frame. Fig.12 The control information field in the announcement frame shown is equivalent to the duration field of the announcement frame mentioned above. That is, Fig.12 The control information field in the announcement frame shown is used to indicate the duration of the second period. Optionally, the control information field may be 16 bits.
[0194] For example, Fig.13A schematic diagram of an announcement frame provided in an embodiment of the present application. The announcement frame is a frame containing a new type of extremely high throughput (EHT) control field defined in the present application. Fig.11 As shown, the announcement frame includes one of the following fields: frame control, duration / identification, address 1, address 2, address 3, sequence control, address 4, quality of service control, EHT control, frame body, and FCS.
[0195] in, Fig.13 The duration / identification field in the shown announcement frame is equivalent to the duration field of the announcement frame mentioned above.
[0196] The EHT control field includes one of the following fields: control ID, and control information.
[0197] The value of the control ID field is a preset value to indicate that the EHT control frame is an announcement frame. Exemplarily, the preset value may be 7.
[0198] Fig.13 The control information field in the announcement frame shown is equivalent to the duration field in the announcement frame mentioned above. That is, Fig.13 The control information field in the announcement frame shown is used to indicate the duration of the second period. Optionally, the control information field may be 16 bits.
[0199] Mode 2: The announcement frame includes a duration field. The duration field is used to enable the intra-BSS station on the second link to set the NAV. That is, the intra-BSS station on the second link will read the duration field included in the announcement frame, and set the NAV maintained by itself according to the value of the duration field included in the announcement frame. However, the OBSS station on the second link will not set the NAV maintained by itself according to the value of the duration field included in the announcement frame.
[0200] In the embodiment of the present application, the value of the duration field included in the announcement frame is equal to the time length of the second period to ensure normal communication of the ML entity.
[0201] based on Fig.10 In the technical solution shown, when the ML entity sends a PPDU on the first link, the ML entity sends a MAC frame on the second link, so that other stations in the same BSS on the second link will not send a PPDU before the end of the first period. In this way, it is ensured that the ML entity will not send a PPDU on the first link and receive a PPDU on the second link, thereby ensuring normal communication of the ML entity.
[0202] Combination Fig.14 For example, the ML AP entity sends a PPDU to the ML non-AP entity 1 on the first link, and at the same time, the ML AP entity sends a MAC frame on the second link, so that the non-AP STA in the same BSS on the second link will not send a PPDU to the ML AP. Therefore, the ML AP entity will not send a PPDU on the first link and receive a PPDU on the second link, ensuring the normal communication of the ML AP entity.
[0203] like Fig.15 As shown, a communication protection method provided in an embodiment of the present application comprises the following steps:
[0204] S301: The ML entity detects the start of a PPDU on a first link.
[0205] The ML entity may support multiple links. The first link may be any one of the multiple links supported by the ML entity.
[0206] Optionally, the start of the PPDU may refer to the L-STF of the PPDU. The L-STF is used to synchronize the stations to receive the PPDU.
[0207] As an implementation manner, a station of a first link of the ML entity detects the start of a PPDU on the first link.
[0208] S302: The ML entity suspends counting of a first backoff counter on the second link.
[0209] The second link is a link other than the first link among the multiple links supported by the ML entity. That is, the first link and the second link are two different links.
[0210] As an implementation, when the station of the second link of the ML entity learns that the station of the first link of the ML entity detects the start of the PPDU, the station of the second link of the ML entity suspends the counting of the first backoff counter, thereby suspending the backoff process of the ML entity on the second link.
[0211] It can be understood that after the first backoff counter pauses counting, the count value of the first backoff counter remains at the current value.
[0212] S303. The ML entity determines whether the PPDU is an intra-BSS PPDU or an inter-BSS PPDU.
[0213] As an implementation method, the station of the first link of the ML entity determines whether the PPDU is an intra-BSS PPDU or an inter-BSS PPDU. The method for determining whether the PPDU is an intra-BSS PPDU or an inter-BSS PPDU can refer to the prior art and will not be repeated here.
[0214] In case the PPDU is an intra-BSS PPDU, the ML entity performs the following step S304.
[0215] In case the PPDU is an inter-BSS PPDU, the ML entity performs the following step S305.
[0216] S304: In the case where the PPDU is an intra-BSS PPDU, the ML entity continues to back off on the second link after the PPDU transmission is completed.
[0217] As an implementation, if the PPDU is an intar-BSS PPDU, after the PPDU is transmitted, the station of the second link of the ML entity resumes the counting function of the first backoff counter. Thus, the station of the second link of the ML entity can continue to perform the backoff process.
[0218] In the embodiment of the present application, the ML entity continues to roll back after the PPDU transmission is completed, including one of the following situations:
[0219] Scenario 1: The ML entity continues to roll back after the first moment. The first moment is the PPDU transmission end moment.
[0220] As an implementation manner, after the first moment, the ML entity waits for the idle time of the second link to reach the second interframe interval. After the idle time of the second link reaches the second interframe interval, each time the second link is in an idle state within a time slot, the count value of the first backoff counter of the second link is reduced by 1 until the count value of the first backoff counter of the second link is 0.
[0221] As an example, in conjunction with FIG. 16( a ), ML entity 1 sends PPDU#1 on the first link. When ML entity 2 detects the start of PPDU#1 on the first link, ML entity 2 suspends the counting of the first backoff counter on the second link. At this time, the count value of the first backoff counter is 5. Afterwards, after ML entity 2 detects the physical header of PPDU#1 on the second link, based on the information in the physical header, ML entity 2 determines that PPDU#1 is an intra-BSS PPDU. Thus, at the end of PPDU#1 transmission, ML entity 2 resumes the counting function of the first backoff counter on the second link and continues to back off. Specifically, ML entity 2 waits for the idle time of the second link to reach the second interframe interval. After the idle time of the second link reaches the second interframe interval, the first backoff counter of the second link starts to back off from 5. When the count value of the backoff counter is reduced to 0, ML entity 2 sends PPDU#2 on the second link.
[0222] Scenario 2: The ML entity continues to roll back after the second time. The second time is the time when the transmission of the response frame corresponding to the PPDU ends.
[0223] As an implementation manner, after the first moment, the ML entity waits for the idle time of the second link to reach the second interframe interval. After the idle time of the second link reaches the second interframe interval, each time the second link is in an idle state within a time slot, the count value of the first backoff counter of the second link is reduced by 1 until the count value of the first backoff counter of the second link is 0.
[0224] Optionally, the second time may be determined according to the PPDU transmission end time, the first interframe interval, and the maximum transmission duration of the BA frame. Exemplarily, the first interframe interval may be SIFS, but the embodiments of the present application are not limited thereto.
[0225] As shown in FIG. 16( b ), ML entity 1 sends PPDU#1 on the first link. When ML entity 2 detects the start of PPDU#1 on the first link, ML entity 2 suspends the counting of the first backoff counter on the second link. At this time, the count value of the first backoff counter is 5. After that, after ML entity 2 detects the physical header of PPDU#1 on the second link, based on the information in the physical header, ML entity 2 determines that PPDU#1 is an intra-BSS PPDU. Thus, after PPDU#1 is transmitted, ML entity 2 determines the second time according to the end time of PPDU#1 transmission, the first inter-frame interval, and the maximum transmission time of the response frame. When the time reaches the second time, ML entity 2 resumes the counting function of the first backoff counter on the second link and continues to back off. Specifically, ML entity 2 waits for the idle time of the second link to reach the second inter-frame interval. After the idle time of the second link reaches the second inter-frame interval, the first backoff counter of the second link starts to back off from 5. When the count value of the first backoff counter is reduced to 0, the ML entity 2 sends PPDU#2 on the second link.
[0226] Scenario 3: The ML entity continues to roll back after the third moment. The third moment is the end moment determined by the duration field of the PPDU. Specifically, the time interval between the third moment and the end moment of the PPDU transmission is equal to the value of the duration field of the PPDU.
[0227] As an implementation manner, after the first moment, the ML entity waits for the idle time of the second link to reach the second interframe interval. After the idle time of the second link reaches the second interframe interval, each time the second link is in an idle state within a time slot, the count value of the first backoff counter of the second link is reduced by 1 until the count value of the first backoff counter of the second link is 0.
[0228] As an example, in conjunction with FIG. 16( c ), ML entity 1 sends PPDU#1 on the first link. When ML entity 2 detects the start of PPDU#1 on the first link, ML entity 2 suspends the counting of the first backoff counter on the second link. At this time, the count value of the first backoff counter is 5. Afterwards, after ML entity 2 detects the physical header of PPDU#1 on the second link, based on the information in the physical header, ML entity 2 determines that PPDU#1 is an intra-BSS PPDU. Thus, after PPDU#1 is transmitted, ML entity 2 determines a third time according to the end time of PPDU#1 transmission and the value of the duration field of PPDU#1. When the time reaches the third time, ML entity 2 resumes the counting function of the first backoff counter on the second link and continues to back off. Specifically, ML entity 2 waits for the idle time of the second link to reach the second interframe interval. After the idle time of the second link reaches the second interframe interval, the first backoff counter of the second link starts to back off from 5. When the count value of the first backoff counter is reduced to 0, the ML entity 2 sends PPDU#2 on the second link.
[0229] S305: When the PPDU is an inter-BSS PPDU, the ML entity continues to back off on the second link.
[0230] As an implementation manner, if the PPDU is an inter-BSS PPDU, the station of the second link of the ML entity resumes the counting function of the first backoff counter. Thus, the station of the second link of the ML entity can continue to perform the backoff process.
[0231] Optionally, after the fourth moment, whenever the second link is in an idle state within a time slot, the count value of the first backoff counter of the second link is reduced by 1 until the count value of the first backoff counter of the second link is 0.
[0232] Alternatively, after the fourth moment, the ML entity waits for the idle time of the second link to reach the second interframe interval. After the idle time of the second link reaches the second interframe interval, each time the second link is in an idle state within a time slot, the count value of the first backoff counter of the second link is reduced by 1 until the count value of the first backoff counter of the second link is 0.
[0233] The fourth moment is the moment when the ML entity determines that the PPDU is an inter-BSS PPDU.
[0234] As shown in FIG. 16( d ), ML entity 1 sends PPDU#1 on the first link. When ML entity 2 detects the start of PPDU#1 on the first link, ML entity 2 suspends the counting of the first backoff counter on the second link. At this time, the count value of the first backoff counter is 5. After that, after ML entity 2 detects the physical header of PPDU#1 on the second link, ML entity 2 determines that PPDU#1 is an inter-BSS PPDU. In this case, ML entity 2 immediately resumes the counting function of the first backoff counter on the second link and continues to back off. After the back off is completed, ML entity 2 sends PPDU#2 on the second link.
[0235] based on Fig.15 In the technical solution shown, after the ML entity detects the start of the PPDU on the first link, the ML entity suspends the counting of the first backoff counter on the second link. In the case where the PPDU is an intra-BSS PPDU, the ML entity continues to back off after the transmission of the PPDU is completed. Therefore, during the PPDU transmission process on the first link, the ML entity will not send the PPDU on the second link, thereby avoiding the situation where other ML entities in the same BSS receive signals on the first link and send signals on another link. In addition, when the ML entity determines that the PPDU is an inter-BSS PPDU, the ML entity immediately continues to back off, thereby ensuring that the ML entity can perform channel access normally on the second link.
[0236] As an optional embodiment, based on Fig.15 The technical solution shown, such as Fig.17 As shown, the communication protection method further includes steps S306-S307 after step S302. In addition, step S305 can be replaced by steps S305a-S305b.
[0237] S306: The ML entity configures a second backoff counter on the second link.
[0238] As an implementation manner, a station of the second link of the ML entity configures a second backoff counter, and an initial value of the second backoff counter is the current value of the first backoff counter.
[0239] For example, assuming that when the ML entity freezes the first backoff counter, the current value of the first backoff counter is 15, then the initial value of the second backoff counter is also 15.
[0240] S307: The ML entity performs a virtual backoff based on the second backoff counter.
[0241] The virtual backoff means that: if the second link is in an idle state at the current moment, then whenever the second link is in an idle state within a time slot, the ML entity reduces the count value of the second backoff counter by 1. If the second link is in a busy state at the current moment, the ML entity waits for the idle time of the second link to reach the second interframe interval; after the idle time of the second link reaches the second interframe interval, then whenever the second link is in an idle state within a time slot, the ML entity reduces the count value of the second backoff counter by 1.
[0242] It should be understood that the above current moment refers to the moment when the ML entity completes configuring the second backoff counter.
[0243] Optionally, the second inter-frame interval may be AIFS, or other inter-frame intervals, but the embodiments of the present application are not limited thereto.
[0244] It is understandable that if the second link is busy in a certain time slot, the ML entity needs to wait for the idle time of the second link to reach the second interframe interval. After the idle time of the second link reaches the second interframe interval, the ML entity counts the second backoff counter again.
[0245] Optionally, the busy / idle state of the second link can be determined based on the busy / idle state of the main channel of the second link. That is, if the main channel of the second link is in a busy state, it means that the second link is in a busy state. If the main channel of the second link is in an idle state, it means that the second link is in an idle state. Among them, the main channel of the second link can be pre-configured or defined in the standard, and the embodiments of the present application are not limited to this. For example, the main channel of the second link can be the 20 MHz channel with the highest frequency in the frequency band corresponding to the second link. For another example, the main channel of the second link can be the 20 MHz channel with the lowest frequency in the frequency band corresponding to the second link.
[0246] In the embodiment of the present application, before the ML entity determines whether the PPDU is an intra-BSS PPDU or an inter-BSS PPDU, if the count value of the second backoff counter decreases to 0, the ML entity may maintain the second backoff counter in any one of the following ways.
[0247] Method 1: The ML entity maintains the count value of the second backoff counter as 0.
[0248] That is, the station of the second link of the ML entity keeps the count value of the second backoff counter at 0.
[0249] Mode 2: The ML entity resets the count value of the second backoff counter. It should be understood that after the second backoff counter resets the count value, the ML entity continues to back off based on the second backoff counter.
[0250] It should be noted that the ML entity resets the count value of the second backoff counter, including: the ML entity resets the count value of the second backoff counter according to the doubled contention window. Alternatively, the ML entity resets the count value of the second backoff counter according to the minimum value of the contention window. Alternatively, the ML entity resets the count value of the second backoff counter according to the contention window.
[0251] The above doubling specifically means that if the contention window CW does not reach CWmax, CW is updated to 2*CW+1; if the contention window CW is CWmax, CW remains unchanged.
[0252] It should be noted that steps S306-S307 and step S303 are executed simultaneously.
[0253] S305a: When the PPDU is an inter-BSS PPDU, the ML entity sets the count value of the first backoff counter to the count value of the second backoff counter.
[0254] As an implementation manner, the station of the second link of the ML entity sets the count value of the first backoff counter to the count value of the second backoff counter.
[0255] For example, assume that when the ML entity freezes the first backoff counter, the current value of the first backoff counter is 15. Afterwards, when the ML entity determines that the PPDU is an inter-BSS PPDU, if the count value of the second backoff counter is 10, the count value of the first backoff counter is updated to 10.
[0256] S305b: The ML entity continues to back off on the second link based on the first back off counter.
[0257] As an implementation manner, the station of the second link of the ML entity restores the counting function of the first backoff counter on the second link and continues to back off.
[0258] Optionally, after the fourth moment, whenever the second link is in an idle state in a time slot, the count value of the first backoff counter of the second link is reduced by 1 until the count value of the first backoff counter of the second link is 0. The fourth moment is the moment when the ML entity determines that the PPDU is an inter-BSS PPDU.
[0259] Optionally, regardless of whether the second link has been in an idle state in the second inter-frame interval before the fourth moment, as long as the second link is in an idle state at the fourth moment, each time the second link is in an idle state in a time slot, the count value of the first backoff counter of the second link is reduced by 1 until the count value of the first backoff counter of the second link is 0.
[0260] Combined with Figure 16(e) Fig.17 The technical solution shown in the figure is illustrated by an example. As shown in Figure 16(e), ML entity 1 sends PPDU#1 on the first link. When ML entity 2 detects the start of PPDU#1 on the first link, ML entity 2 suspends the counting of the first backoff counter on the second link. At this time, the count value of the first backoff counter is 5. At the same time, ML entity 2 configures the second backoff counter on the second link, and the count value of the second backoff counter is 5.
[0261] During the two time slots in which the ML entity 2 listens to the physical header of PPDU#1 on the first link, the second link is in an idle state, so the count value of the second backoff counter is reduced to 3. After the ML entity 2 listens to the physical header of PPDU#1 on the second link, the ML entity 2 determines that the PPDU#1 is an inter-BSS PPDU. In this case, the ML entity 2 updates the count value of the first backoff counter to 3 and continues to back off. After the count value of the first backoff counter is reduced to 0, the ML entity 2 sends PPDU#2 on the second link.
[0262] Combined with Figure 16(f) Fig.17 The technical solution shown in the figure is illustrated by way of example. As shown in FIG. 16( f), ML entity 1 sends PPDU#1 on the first link. When ML entity 2 detects the start of PPDU#1 on the first link, ML entity 2 suspends the count of the first backoff counter on the second link, and at this time, the count value of the first backoff counter is 5. At the same time, ML entity 2 configures a second backoff counter on the second link, and the count value of the second backoff counter is 5. In the two time slots in which ML entity 2 detects the physical header of PPDU#1 on the first link, the second link is in an idle state, so the count value of the second backoff counter is reduced to 3. After ML entity 2 detects the physical header of PPDU#1 on the second link, ML entity 2 determines that PPDU#1 is an intra-BSS PPDU. In this case, ML entity 2 does not update the count value of the first backoff counter, so ML entity 2 continues to back off based on the first backoff counter with a count value of 5. After the count value of the first backoff counter is reduced to 0, ML entity 2 sends PPDU#2 on the second link.
[0263] based on Fig.17In the technical solution shown, after the ML entity detects the start of the PPDU on the first link, the ML entity suspends the counting of the first backoff counter on the second link. At the same time, the ML entity configures the second backoff counter, and the initial value of the second backoff counter is the current value of the first backoff counter. Thus, the ML entity performs a virtual backoff based on the second backoff counter. When the ML entity determines that the PPDU is an inter-PPDU, the ML entity sets the count value of the first backoff counter with the count value of the second backoff counter, so that the first backoff counter is not affected by the previous suspension. In this way, in the case where the PPDU is an inter-BSS PPDU, the backoff process of the ML entity on the second link is not affected, thereby avoiding the ML entity from being at a disadvantage in channel competition and ensuring the use of the second link by the ML entity.
[0264] As an optional embodiment, based on Fig.15 The technical solution shown, such as Fig.18 As shown, the communication protection method further includes steps S308-S309 after step S302. In addition, step S305 can be replaced by steps S305c-S305d.
[0265] S308: The ML entity sets a third counter on the second link.
[0266] The third counter is used to record the idle time of the second link. The initial value of the third counter may be 0.
[0267] S309: The ML entity updates the count value of the third counter according to the idle time of the second link.
[0268] As an implementation manner, whenever the second link is in an idle state within a time slot, the ML entity increases the count value of the third counter by 1.
[0269] S305c: When the PPDU is an inter-BSS PPDU, the ML entity sets the count value of the first backoff counter according to the count value of the third counter.
[0270] Optionally, if the current value of the first backoff counter minus the count value of the third counter is greater than or equal to 0, the count value of the first backoff counter is equal to the current value of the first backoff counter minus the count value of the third counter. If the current value of the first backoff counter minus the count value of the third counter is less than 0, the count value of the first backoff counter is 0.
[0271] For example, it is assumed that when the ML entity suspends the counting of the first backoff counter, the current value of the first backoff counter is 10. If the idle time of the second link reaches 9 time slots during the process of the ML entity determining whether the PPDU is an inter-BSS PPDU, the count value of the third counter is 9. In this way, when determining that the PPDU is an inter-BSS PPDU, the ML entity can set the count value of the first backoff counter to 1.
[0272] For another example, assume that when the ML entity suspends the counting of the first backoff counter, the current value of the first backoff counter is 10. If the idle time of the second link reaches 12 time slots during the process of the ML entity determining whether the PPDU is an inter-BSS PPDU, the count value of the third counter is 12. In this way, when determining that the PPDU is an inter-BSS PPDU, the ML entity can set the count value of the first backoff counter to 0.
[0273] S305d: The ML entity continues to back off on the second link based on the first back off counter.
[0274] As an implementation manner, the station of the second link of the ML entity restores the counting function of the first backoff counter on the second link and continues to back off.
[0275] Optionally, after the fourth moment, whenever the second link is in an idle state within a time slot, the count value of the first backoff counter of the second link is reduced by 1 until the count value of the first backoff counter of the second link is 0.
[0276] The fourth moment is the moment when the ML entity determines that the PPDU is an inter-BSS PPDU.
[0277] Optionally, regardless of whether the second link has been in an idle state in the second inter-frame interval before the fourth moment, as long as the second link is in an idle state at the fourth moment, each time the second link is in an idle state in a time slot, the count value of the first backoff counter of the second link is reduced by 1 until the count value of the first backoff counter of the second link is 0.
[0278] Combined with Figure 16(g) Fig.18The technical solution shown in the figure is illustrated by way of example. As shown in FIG. 16( g), ML entity 1 sends PPDU#1 on the first link. When ML entity 2 detects the start of PPDU#1 on the first link, ML entity 2 suspends the count of the first backoff counter on the second link, and at this time, the count value of the first backoff counter is 5. At the same time, ML entity 2 configures a third counter on the second link. In the two time slots in which ML entity 2 detects the physical header of PPDU#1 on the first link, the second link is in an idle state, so the count value of the third counter is updated to 2. After ML entity 2 detects the physical header of PPDU#1 on the second link, ML entity 2 determines that PPDU#1 is an inter-BSS PPDU. In this case, ML entity 2 updates the count value of the first backoff counter to 3 according to the count value of the third backoff counter. ML entity 2 continues to back off based on the first backoff counter with a count value of 3. After the count value of the first backoff counter is reduced to 0, ML entity 2 sends PPDU#2 on the second link.
[0279] based on Fig.18 In the technical solution shown, after the ML entity detects the start of the PPDU on the first link, the ML entity suspends the counting of the first backoff counter on the second link. At the same time, the ML entity configures a third counter and records the idle time of the second link with the third counter. When the ML entity determines that the PPDU is an inter-PPDU, the ML entity updates the count value of the first backoff counter according to the counter of the third counter, so that the first backoff counter is not affected by the previous suspension. In this way, in the case where the PPDU is an inter-BSS PPDU, the backoff process of the ML entity on the second link is not affected, thereby avoiding the ML entity from being at a disadvantage in channel competition and ensuring the use of the second link by the ML entity.
[0280] like Fig.19 As shown, a communication protection method provided in an embodiment of the present application comprises the following steps:
[0281] S401: An ML non-AP entity detects a first PPDU on a first link.
[0282] The ML non-AP supports multiple links. The first link is any one of the multiple links supported by the ML non-AP entity.
[0283] Optionally, the first PPDU may be any one of a single user (SU) PPDU, an extended range (ER) SU PPDU, a trigger based (TB) PPDU, or an uplink multiple user (MU) PPDU.
[0284] As an implementation manner, a station of a first link of the ML non-AP entity detects a first PPDU on the first link.
[0285] After listening to the first PPDU, the ML non-AP station determines whether the receiving end of the first PPDU is the ML AP entity associated with the MLnon-AP entity. For example, if the BBS color in the SIG field of the first PPDU is the same as the BSS color of the BSS to which the station of the first link of the MLnon-BSS entity belongs, and the UL / DL parameter in the SIG field of the first PPDU is used to indicate that the first PPDU is uplink transmission, then the receiving end of the first PPDU is the ML AP entity associated with the MLnon-AP entity.
[0286] S402: If the receiving end of the first PPDU is the ML AP entity associated with the ML non-AP entity, the ML non-AP entity sends a second PPDU on a second link.
[0287] The second link is other links among the multiple links supported by the ML non-AP except the first link.
[0288] In the embodiment of the present application, the end time of the second PPDU is the same as the end time of the first PPDU, so as to ensure that the ML AP entity associated with the ML non-AP entity can simultaneously receive the PPDU and send the BA frame on the first link and the second link.
[0289] In order to ensure that the end of the second PPDU is the same as the end time of the first PPDU, the ML non-AP entity can determine the transmission duration of the second PPDU based on the transmission duration of the first PPDU. Specifically, the ML non-AP entity determines the transmission duration of the second PPDU based on the start time of the first PPDU, the transmission duration of the first PPDU, and the start time of the second PPDU. Among them, the start time of the first PPDU is the moment when the ML non-AP entity detects the L-STF of the first PPDU on the first link. The start time of the second PPDU is determined by the ML non-AP entity itself. The transmission duration of the first PPDU can be determined based on the L-SIG field of the first PPDU.
[0290] Exemplarily, the L-SIG field of the first PPDU includes a RATE field and a LENGTH field. The RATE field is used to indicate the transmission rate of the first PPDU. The LENGTH field is used to indicate the data length of the first PPDU. Based on the RATE field and the LENGTH field, it can be calculated that the end time of the L-SIG field is the duration between the end time of the first PPDU and the end time of the first PPDU. The specific calculation method can refer to the prior art.
[0291] It should be understood that the transmission duration of the first PPDU includes: the duration between the start time of the first PPDU and the end time of the L-SIG field of the first PPDU, and the duration between the end time of the L-SIG field and the end time of the first PPDU.
[0292] It should be understood that, based on the end time of the first PPDU being the same as the end time of the second PPDU, the ML non-AP entity can determine the start time of the second PPDU and the values of the RATE field and the LENGTH field in the second PPDU according to the transmission duration of the second PPDU.
[0293] As an implementation manner, the station of the second link of the ML non-AP entity learns from the station of the first link that the receiving end of the first PPDU is the ML AP entity associated with the ML non-AP entity; thereafter, the station of the second link of the ML non-AP entity sends a second PPDU on the second link.
[0294] Optionally, the ML non-AP entity sends the second PPDU on the second link, further comprising: the ML non-AP entity performs a backoff process on the second link; after the backoff process ends, the ML non-AP entity sends the second PPDU on the second link. The backoff process can refer to the prior art and will not be described in detail herein.
[0295] Combination Fig. 20For example, after the backoff process ends, ML non-AP entity 1 sends an RTS frame on the first link to establish a TXOP. Afterwards, ML non-AP entity 1 sends PPDU#1 to ML AP entity on the first link. ML non-AP entity 2 intercepts PPDU#1. After ML non-AP entity 2 determines that PPDU#1 is sent to the ML AP entity associated with ML non-AP entity 2, ML non-AP entity 2 sends PPDU#2 on the second link. The end time of PPDU#2 is the same as the end time of PPDU#1. Therefore, the ML AP entity can send a BA frame of PPDU#1 on the first link and a BA frame of PPDU#2 on the second link at the same time.
[0296] based on Fig.19 In the technical solution shown, if the ML non-AP entity detects the first PPDU on the first link, and the first PPDU is sent to the ML AP entity associated with the ML non-AP entity, the ML non-AP entity sends the second PPDU on the second link. Since the end time of the second PPDU is the same as the end time of the first PPDU, the ML AP entity can send the BA frame of the second PPDU and the BA frame of the first PPDU at the same time. In this way, on the one hand, it avoids the situation where the ML AP entity sends a signal on one link and receives a signal on another link. On the other hand, the ML non-AP entity sends the second PPDU on the second link, which is conducive to improving the utilization rate of the second link.
[0297] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the ML entity. It is understandable that, in order to realize the above functions, the ML entity includes a hardware structure and / or software module corresponding to each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.
[0298] The embodiment of the present application can divide the functional modules of the device according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function:
[0299] Fig.21 A schematic diagram of the structure of an ML entity provided in an embodiment of the present application. Fig.21 As shown, the ML entity includes a first unit 101 and a second unit 102 .
[0300] Solution 1:
[0301] The first unit 101 is configured to detect a first PPDU on a first link. The second unit 102 is configured to update the value of the target NAV of the second link to the value of the duration field of the first PPDU if the first PPDU is an intra-BSS PPDU and the value of the duration field of the first PPDU is greater than the value of the target NAV of the second link, and the second link is any one of the multiple links supported by the ML entity except the first link.
[0302] In one possible design, the second unit 102 is used to not update the value of the target NAV of the second link if the first PPDU is an inter-BSS PPDU; or, if the first PPDU is an intra-BSS PPDU and the value of the duration field of the first PPDU is less than or equal to the value of the target NAV of the second link, not update the value of the target NAV of the second link.
[0303] In one possible design, the first unit 101 is further configured to detect a CF-end frame on the first link. The second unit 102 is configured to set the value of the target NAV of the second link to 0 when the CF-end frame is an intra-BSS PPDU and the value of the target NAV of the second link is updated according to the value of the duration field of the first PPDU.
[0304] In one possible design, the second unit 102 is used to reset the target NAV of the second link when the first unit 101 does not detect the second PPDU on the first link within a preset time period, and the value of the target NAV of the second link is updated according to the value of the duration field of the first PPDU, and the second PPDU and the first PPDU come from the same site.
[0305] In one possible design, the second unit 102 is specifically used to set the value of the target NAV of the second link to 0; or, to set the value of the target NAV of the second link to a first value, the end time determined by the first value is the same as the end time determined by the second value, and the second value is the value of the target NAV before the target NAV is updated according to the value of the duration field of the first PPDU.
[0306] In a possible design, the preset duration = (2×aSIFSTime) + (first PPDU response frame transmission duration) + aRxPHYStartDelay + (2×aSlotTime), where aSIFSTime represents the duration of SIFS, aRxPHYStartDelay represents the duration of the preset delay, and aSlotTime represents the duration of a time slot.
[0307] In one possible design, the first PPDU carries an RTS frame, and the response frame is a CTS frame.
[0308] In one possible design, if the ML entity is an ML non-AP entity, the target NAV includes one of the following situations: (1) if the ML non-AP entity is configured with intra-BSS NAV and basic NAV on the second link, the target NAV is intra-BSS NAV; (2) if the ML non-AP entity is configured with intra-BSS NAV, basic NAV, and first NAV on the second link, the target NAV is the first NAV.
[0309] In a possible design, if the ML entity is an ML AP entity, the target NAV includes one of the following situations: (1) if the ML AP entity is configured with intra-BSS NAV and basic NAV on the second link, the target NAV is the intra-BSS NAV; (2) if the ML AP entity is configured with only intra-BSS NAV, basic NAV and the first NAV on the second link, the target NAV is the first NAV; (3) if the ML AP entity is configured with the first NAV and the second NAV on the second link, the target NAV is the first NAV.
[0310] Option 2:
[0311] The first unit 101 is used to send a first PPDU on a first link, the first PPDU includes a duration field, and the duration field included in the first PPDU is used to indicate the duration of a first time period. The second unit 102 is used to send a MAC frame on a second link, the MAC frame is used to indicate the duration of a second time period, the end time of the first time period is the same as the end time of the second time period, and the intra-BSS station on the second link is prohibited from sending the second PPDU during the second time period, and the second link is any one of the multiple links supported by the ML entity except the first link.
[0312] In one possible design, the MAC frame is an announcement frame or a QTP frame.
[0313] In one possible design, the value of the duration field of the announcement frame is equal to the duration of the second time period. The duration field of the announcement frame is used to set the value of the NAV maintained by the intra-BSS site, and the duration field of the announcement frame is not used to set the value of the NAV maintained by the OBSS site.
[0314] In one possible design, the announcement frame includes a duration field and a length field. The length field is used to set the value of the NAV maintained by the intra-BSS site. The value of the duration field is 0, and the value of the length field is equal to the length of the second time period.
[0315] Option 3:
[0316] The first unit 101 is used to detect the start of a PPDU on a first link. The second unit 102 is used to stop counting of a first backoff counter on a second link, where the second link is any link other than the first link among multiple links supported by the ML entity. The first unit 101 is also used to determine whether the PPDU is an intra-BSS PPDU or an inter-BSS PPDU. The second unit 102 is also used to continue backing off on the second link after the PPDU transmission is completed if the PPDU is an intra-BSS PPDU; and continue backing off on the second link if the PPDU is an inter-BSS PPDU.
[0317] In one possible design, the second unit 102 is specifically used to continue to back off on the second link after a first moment, where the first moment is the end moment of transmission of the PPDU; or, to continue to back off on the second link after a second moment, where the second moment is the end moment of transmission of a response frame corresponding to the PPDU; or, to continue to back off on the second link after a third moment, where the third moment is the end moment determined by the duration field of the PPDU.
[0318] In one possible design, the second unit 102 is also used to configure a second backoff counter on the second link, and the initial value of the second backoff counter is the current value of the first backoff counter; if the second link is in an idle state at the current moment, then each time the second link is in an idle state within a time slot, the count value of the second backoff counter is reduced by 1; if the second link is in a busy state at the current moment, then wait for the idle time of the second link to reach the second inter-frame interval; after the idle time of the second link reaches the second inter-frame interval, each time the second link is in an idle state within a time slot, the count value of the second backoff counter is reduced by 1.
[0319] In a possible design, the second unit 102 is further configured to keep the count value of the second backoff counter at 0 after the count value of the second backoff counter is reduced to 0.
[0320] In a possible design, the second unit 102 is further configured to reset the count value of the second backoff counter when the count value of the second backoff counter decreases to 0.
[0321] In one possible design, the second unit 102 is further used to reset the count value of the second backoff counter according to the doubled contention window; or, the ML entity resets the count value of the second backoff counter according to the contention window; or, the ML entity resets the count value of the second backoff counter according to the minimum value of the contention window.
[0322] In one possible design, the second unit 102 is specifically configured to update the count value of the first backoff counter with the count value of the second backoff counter when the PPDU is an inter-BSS PPDU, and continue to back off on the second link based on the first backoff counter.
[0323] Option 4:
[0324] The first unit 101 is configured to detect a first PPDU on a first link. The second unit 102 is configured to send a second PPDU on a second link when the receiving end of the first PPDU is an ML AP entity associated with the ML entity, the second link being any one of a plurality of links supported by the ML non-AP entity except the first link, and the end time of the first PPDU is the same as the end time of the second PPDU.
[0325] In one possible design, the second unit 102 is specifically configured to perform a backoff procedure on the second link; after the backoff procedure on the second link is completed, the ML non-AP entity sends a second PPDU on the second link.
[0326] The ML entity provided in the above-mentioned embodiment of the present application can be implemented in a variety of product forms. For example, the ML entity can be configured as a general processing system; for another example, the ML entity can be implemented by a general bus architecture; for another example, the ML entity can be implemented by an application specific integrated circuit (ASIC), etc. The following provides several possible product forms of the ML entity described in the embodiment of the present application. It should be understood that the following product forms are only examples and do not limit the possible product forms of the ML entity described in the embodiment of the present application.
[0327] Fig. 22 It is a result diagram of possible product forms of the ML entity described in the embodiment of the present application.
[0328] As a possible product form, the ML entity described in the embodiment of the present application may be a communication device, and the communication device 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 6 Steps S102, S103, S104, S105 in Figure 8 Step S107 in Fig. 9 Step S108 in Fig.15 Steps S302-S305 in Fig.17 Steps S306, S307, S305a and S305b in Fig.18 The transceiver 202 is used to perform steps S308, S309, S305c and S305d. Figure 6 In step S101, Figure 8 Step S106 in Fig.10 Steps S201 and S202 in Fig.15 Step S301 in Fig.19 Steps S401 and S402 in .
[0330] As another possible product form, the ML entity described in the embodiment of the present application can also be implemented by a general-purpose processor or a dedicated processor, that is, a so-called chip. The chip includes: a processing circuit 201 and a transceiver pin 202. Optionally, the chip can also include a storage medium 203.
[0331] The processing circuit 201 is used to execute Figure 6 Steps S102, S103, S104, S105 in Figure 8 Step S107 in Fig. 9 Step S108 in Fig.15Steps S302-S305 in Fig.17 Steps S306, S307, S305a and S305b in Fig.18 Steps S308, S309, S305c and S305d in the above embodiment. The transceiver pin 202 is used to perform Figure 6 In step S101, Figure 8 Step S106 in Fig.10 Steps S201 and S202 in Fig.15 Step S301 in Fig.19 Steps S401 and S402 in .
[0332] The embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions; when the computer-readable storage medium is run on an ML entity, the ML entity executes the following Figure 6 , Figure 8 , Fig. 9 , Fig.10 , Fig.15 , Fig.17 , Fig.18 ,or Fig.19 The method shown. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes one or more available media integrated therein. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium, or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
[0333] The present application also provides a computer program product including computer instructions, which, when executed on an ML entity, enables the ML entity to execute Figure 6 , Figure 8 , Fig. 9 , Fig.10 , Fig.15 , Fig.17 , Fig.18 ,or Fig.19 The method shown.
[0334] Although the present application is described herein in conjunction with various embodiments, in the process of implementing the claimed application, those skilled in the art may understand and implement other variations of the disclosed embodiments by viewing the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other components or steps, and "one" or "an" does not exclude multiple situations. A single processor or other unit may implement several functions listed in a claim. Certain measures are recorded in different dependent claims, but this does not mean that these measures cannot be combined to produce good results.
[0335] Although the present application has been described in conjunction with specific features and embodiments thereof, it is obvious that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.
Claims
1. A communication protection method, characterized in that: The method is applied to a multi-link ML entity, the ML entity supports multiple links, and the method includes: The ML entity detects a first physical layer protocol data unit PPDU on a first link; If the first PPDU is an intra-BSS PPDU in a basic service set, and the value of the duration field of the first PPDU is greater than the value of the target network allocation vector NAV of the second link, the ML entity updates the value of the target NAV of the second link to the value of the duration field of the first PPDU, and the second link is any one of the multiple links supported by the ML entity except the first link.
2. The communication protection method according to claim 1, characterized in that: The method further comprises: If the first PPDU is an inter-BSS PPDU, the ML entity does not update the value of the target NAV of the second link; or, If the first PPDU is an intra-BSS PPDU and the value of the duration field of the first PPDU is less than or equal to the value of the target NAV of the second link, the ML entity does not update the value of the target NAV of the second link.
3. The communication protection method according to claim 1, characterized in that: The method further comprises: The ML entity detects a contention-free end CF-end frame on the first link; If the CF-end frame is an intra-BSS PPDU, and the value of the target NAV of the second link is updated according to the value of the duration field of the first PPDU, the ML entity sets the value of the target NAV of the second link to 0.
4. The communication protection method according to claim 1, characterized in that: The method further comprises: If the ML entity does not detect the second PPDU on the first link within a preset time period, and the value of the target NAV of the second link is updated according to the value of the duration field of the first PPDU, the ML entity resets the target NAV of the second link, and the second PPDU and the first PPDU come from the same site.
5. The communication protection method according to claim 4, characterized in that: The ML entity resetting the target NAV of the second link includes: The ML entity sets the target NAV value of the second link to 0; or, The ML entity sets the value of the target NAV of the second link to a first value, the end time determined by the first value is the same as the end time determined by the second value, and the second value is the value of the target NAV before the target NAV is updated according to the value of the duration field of the first PPDU.
6. The communication protection method according to claim 4 or 5, characterized in that: Preset duration = (2×aSIFSTime) + (first PPDU response frame transmission duration) + aRxPHYStartDelay + (2×aSlotTime); Wherein, aSIFSTime represents the duration of the short interframe space SIFS, aRxPHYStartDelay represents the duration of the preset delay, and aSlotTime represents the duration of a time slot.
7. The communication protection method according to claim 6, characterized in that: The first PPDU carries a request to send RTS frame, and the response frame is a clear to send CTS frame.
8. The communication protection method according to any one of claims 1 to 5, characterized in that: If the ML entity is a ML non-access point non-AP entity, the target NAV includes one of the following situations: If the ML non-AP entity is configured with intra-BSS NAV and basic NAV on the second link, the target NAV is the intra-BSS NAV; If the ML non-AP entity is configured with an intra-BSS NAV, a basic NAV, and a first NAV on the second link, the target NAV is the first NAV.
9. The communication protection method according to any one of claims 1 to 5, characterized in that: If the ML entity is an ML access point AP entity, the target NAV includes one of the following situations: If the ML AP entity is configured with an intra-BSS NAV and a basic NAV on the second link, the target NAV is the intra-BSS NAV; If the ML AP entity is configured with only the intra-BSS NAV, the basic NAV and the first NAV on the second link, the target NAV is the first NAV; If the ML AP entity configures a first NAV and a second NAV on the second link, the target NAV is the first NAV.
10. A communication protection method, characterized in that: The method is applied to a multi-link ML entity, the ML entity supports multiple links, and the method includes: The ML entity sends a first physical layer protocol data unit PPDU on a first link, wherein a duration field of the first PPDU is used to indicate a duration of a first time period; The ML entity sends a media access control MAC frame on the second link, where the MAC frame is used to indicate the duration of a second time period, the end time of the first time period is the same as the end time of the second time period, and the intra-BSS station in the basic service set on the second link during the second time period is prohibited from sending a second PPDU, and the second link is any one of the multiple links supported by the ML entity except the first link.
11. The communication protection method according to claim 10, characterized in that: The MAC frame is an announcement frame or a quiet time period QTP frame.
12. The communication protection method according to claim 11, characterized in that: The value of the duration field of the announcement frame is equal to the duration of the second time period. The duration field of the announcement frame is used to set the value of the network allocation vector NAV maintained by the site of the intra-BSS. The duration field of the announcement frame is not used to set the value of the NAV maintained by the site of the overlapping basic service set OBSS.
13. The communication protection method according to claim 11, characterized in that: The announcement frame includes a duration field and a length field, the length field is used to set the value of the network allocation vector NAV maintained by the intra-BSS site, the duration field has a value of 0, and the length field has a value equal to the length of the second period.
14. A communication protection method, characterized in that: The method is applied to a multi-link ML entity, the ML entity supports multiple links, and the method includes: The ML entity detects the start of a physical layer protocol data unit PPDU on the first link; The ML entity stops counting of a first backoff counter on a second link, where the second link is any one of a plurality of links supported by the ML entity except the first link; The ML entity determines whether the PPDU is an intra-BSS PPDU within a basic service set or an inter-BSS PPDU between basic service sets; If the PPDU is an intra-BSS PPDU, the ML entity continues to fallback on the second link after the PPDU is transmitted; If the PPDU is an inter-BSS PPDU, the ML entity continues to fallback on the second link.
15. The communication protection method according to claim 14, characterized in that: After the PPDU transmission is completed, the ML entity continues to fall back on the second link, including: The ML entity continues to fallback on the second link after a first time, where the first time is a transmission end time of the PPDU; or The ML entity continues to fallback on the second link after the second time, where the second time is the transmission end time of the response frame corresponding to the PPDU; or The ML entity continues to back off on the second link after a third time instant, where the third time instant is an end time instant determined by a duration field of the PPDU.
16. The communication protection method according to claim 14 or 15, characterized in that: After the ML entity stops counting of the first backoff counter on the second link, the method further includes: The ML entity configures a second backoff counter on the second link, where an initial value of the second backoff counter is a current value of the first backoff counter; If the second link is in an idle state at the current moment, the ML entity reduces the count value of the second backoff counter by 1 whenever the second link is in an idle state in a time slot; If the second link is in a busy state at the current moment, the ML entity waits for the idle time of the second link to reach the second inter-frame interval; after the idle time of the second link reaches the second inter-frame interval, each time the second link is in an idle state within a time slot, the ML entity reduces the count value of the second backoff counter by 1.
17. The communication protection method according to claim 16, characterized in that: The method further comprises: After the count value of the second backoff counter is reduced to 0, the ML entity maintains the count value of the second backoff counter as 0.
18. The communication protection method according to claim 16, characterized in that: The method further comprises: When the count value of the second backoff counter decreases to 0, the ML entity resets the count value of the second backoff counter.
19. The communication protection method according to claim 18, characterized in that: The ML entity resetting the count value of the second backoff counter includes: The ML entity resets the count value of the second backoff counter according to the doubled contention window; or, The ML entity resets the count value of the second backoff counter according to the contention window; or, The ML entity resets the count value of the second backoff counter according to the minimum value of the contention window.
20. The communication protection method according to claim 16, characterized in that: If the PPDU is an inter-BSS PPDU, the ML entity continues to fallback on the second link, including: If the PPDU is an inter-BSS PPDU, the ML entity updates the count value of the first backoff counter with the count value of the second backoff counter, and continues to back off on the second link based on the first backoff counter.
21. A communication protection method, characterized in that: The method is applied to a multi-link ML non-access point non-AP entity, the ML non-AP entity supports multiple links, and the method includes: The ML non-AP entity detects a first physical layer protocol data unit PPDU on a first link; If the receiving end of the first PPDU is the ML access point AP entity associated with the ML non-AP entity, the ML non-AP entity sends a second PPDU on a second link, where the second link is any one of the multiple links supported by the ML non-AP entity except the first link, and the end time of the first PPDU is the same as the end time of the second PPDU.
22. The communication protection method according to claim 21, characterized in that: The ML non-AP entity sends a second PPDU on a second link, including: The ML non-AP entity performs a backoff procedure on the second link; After the backoff procedure on the second link ends, the ML non-AP entity sends the second PPDU on the second link.
23. A multi-link ML entity, characterized in that The ML entity includes a unit for executing each step of the communication protection method according to any one of claims 1 to 22.
24. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes computer instructions, and when the computer instructions are executed on a computer, the computer executes the communication protection method according to any one of claims 1 to 22.
25. A chip, characterized in that: The chip supports multiple links, and the chip includes a processing circuit and a transceiver pin; The transceiver pin is used to detect a first physical layer protocol data unit PPDU on the first link; The processing circuit is used to update the value of the target NAV of the second link to the value of the duration field of the first PPDU when the first PPDU is an intra-BSS PPDU in a basic service set and the value of the duration field of the first PPDU is greater than the value of the target network allocation vector NAV of the second link, and the second link is any one of the multiple links supported by the chip except the first link.
Citation Information
Patent Citations
Method and device for updating or modifying NAV (network allocation vector)
CN106912108A
Method for setting NAV in wireless communication system, and related device
CN108353429A
System and Methods for Differentiated Association Service Provisioning in WiFi Networks
US20130229995A1
Method and apparatus for performing uplink transmission in wireless LAN system
US20170230981A1
Cited By
Communication protection method and apparatus
WO2021004404A1
