Method for setting media synchronization delay timer and related devices

Abstract

This application relates to the field of wireless communication and is applied to wireless local area networks supporting the 802.11 series standards. In particular, it relates to a method and related apparatus for setting a medium synchronization delay timer. The method includes: a station on an NSTR link pair in an MLD starts a medium synchronization delay timer and sets an initial value (not 0) when another station's transmission ends; this station receives a PPDU carrying an MPDU, the MPDU containing an RTS frame; if the RTS frame is sent by an access point associated with the station, and the link of this access point is not a link on any NSTR link pair of the MLD to which this access point belongs, then this station resets the count value of the medium synchronization delay timer to 0. Using the embodiments of this application, the impact of unnecessary restrictions on the performance of stations that have lost medium synchronization can be reduced, thereby improving station performance.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to a method and apparatus for setting a medium synchronization delay timer. Background Technology

[0002] The ongoing technological goal in the evolution of wireless local area networks (WLANs) or cellular networks is to continuously improve throughput. WLAN system protocols are primarily discussed and researched within the IEEE (Institute of Electrical and Electronics Engineers) standards group. Based on previous standards such as 802.11a / b / g / n / ac / ax, the next-generation standard 802.11be aims for extremely high throughput (EHT). One key technology of 802.11be is multi-link (ML) communication to enhance throughput. The core idea of ​​multi-link communication is that WLAN devices supporting the next-generation 802.11be standard, i.e., EHT devices, possess the ability to transmit and receive across multiple frequency bands, thereby utilizing greater bandwidth for data transmission and significantly improving throughput. These multiple frequency bands include, but are not limited to, the 2.4GHz Wi-Fi band, the 5GHz Wi-Fi band, and the 6GHz Wi-Fi band. In 802.11be, WLAN devices that support multi-link communication are called multi-link devices (MLDs). Obviously, multi-link devices can use multiple links (or multiple frequency bands) to communicate in parallel, which greatly improves the transmission rate.

[0003] When the frequency spacing between multiple frequency bands supported by a multi-link device (MLD) is close, transmitting a signal on one frequency band can affect receiving a signal on another. For example, if a MLD transmits a signal on link 1, the signal transmitted on link 1 will cause channel interference to link 2 due to the small frequency spacing between link 1 and link 2, affecting channel access and information reception on link 2. Therefore, to avoid mutual interference, this device cannot independently perform transmission and reception operations simultaneously on multiple frequency bands. Based on the current progress of the 802.11TGbe standard group, MLDs are defined to have both Simultaneous Transmitting and Receiving (STR) capability and Non-Simultaneous Transmitting and Receiving (NSTR) capability. Two links of an MLD with STR capability are called an STR link pair, and two links without STR capability are called an NSTR link pair.

[0004] For an NSTR link pair, due to signal interference between links, while transmitting a signal on one link (e.g., link 1), it may be unable to receive a signal on another link (e.g., link 2). If there are data packets to receive on link 2 at this time, they may not be received, resulting in packet loss and missing network allocation vector (NAV) updates. Therefore, if a station on link 2 directly participates in channel contention (e.g., enhanced distributed channel access (EDCA) contention), it will create fairness issues for other stations. This technical problem urgently needs to be solved. Summary of the Invention

[0005] This application provides a method and related apparatus for setting a medium synchronization delay timer. By reasonably setting the value of the medium synchronization delay timer, the fairness problem caused to other stations by a station that has lost medium synchronization participating in channel contention can be solved, and the impact of unnecessary restrictions on station performance can be reduced, thereby improving station performance.

[0006] The present application is described below from different aspects. It should be understood that the different implementation methods and beneficial effects described below can be referenced from each other.

[0007] Firstly, this application provides a method for setting a medium synchronization delay timer. The method includes: a first station in a non-access point station (non-AP STA) multi-link device (non-AP MLD) starts a medium synchronization delay timer and sets an initial value when the transmission of a second station in the non-AP MLD ends; the first station in the non-AP MLD receives a physical layer protocol data unit (PPDU) carrying a medium access control protocol data unit (MPDU), the MPDU containing a request-to-send (RTS) frame; if the RTS frame is sent by the first access point, and the link operated by the first access point does not belong to any NSTR link pair of the AP MLD to which the first access point belongs, then the first station in the non-AP MLD resets the count value of the medium synchronization delay timer to 0. The link pair formed by the link operated by the first station and the link operated by the second station is an NSTR link pair, meaning that both the first and second stations in the non-AP MLD have NSTR capabilities. The first access point can be an access point associated with the first site, or it can be another access point in the multiple basic service set identifier (BSSID) of the access point associated with the first site. It should be understood that the first site here can be referred to as a site that has lost media synchronization or a site in a blind state.

[0008] Optionally, the above initial values ​​are either set by the AP or are default values ​​specified by the standard.

[0009] As can be seen, in this scheme, after the first station receives the RTS frame, it determines whether the MediumSyncDelay timer needs to be set to 0 by judging whether the link operated by the station sending the RTS frame belongs to the NSTR link pair. The MediumSyncDelay timer can be processed differently depending on the station sending the RTS frame. Implementing this technical solution can solve the fairness problem caused to other stations by stations that have lost medium synchronization participating in channel contention, thereby reducing the probability of collisions and improving the fairness of channel contention; it can also reduce the impact of unnecessary restrictions on station performance, thus improving station performance.

[0010] In conjunction with the first aspect, in one possible implementation, since the current 802.11be standard only defines that when an AP MLD is a Mobile AP MLD, its link pairs can be NSTR; otherwise, all link pairs of the AP MLD must be STR. Furthermore, since an NSTR Mobile AP MLD only has two links, and these two links are NSTR, the statement that the links operating at the first access point do not belong to any NSTR link pair of the AP MLD to which the first access point belongs can also be understood as: the AP MLD to which the first access point belongs is not an NSTR Mobile AP MLD, and any two links included in that NSTR Mobile AP MLD are NSTR.

[0011] Optionally, the above method further includes: if the RTS frame is sent by the first access point and the AP MLD to which the first access point belongs is an NSTR Mobile AP MLD, then the first station in the non-AP MLD does not reset the count value of the medium synchronization delay timer to 0.

[0012] As can be seen, this solution provides a method for setting a media synchronization delay timer that is compatible with the existing 802.11be standard.

[0013] In conjunction with the first aspect, in one possible implementation, the above method further includes: if the RTS frame is sent by the first access point, and the link in which the first access point operates belongs to any NSTR link pair of the AP MLD to which the first access point belongs, then the first station in the non-AP MLD does not reset the count value of the media synchronization delay timer to 0.

[0014] As can be seen, by restricting the MediumSyncDelay timer from being reset to 0 when the RTS frame sending station is in a blind state or has lost medium synchronization, this scheme can avoid the fairness problem caused to other stations by the station that has lost medium synchronization directly participating in channel contention, thereby reducing the probability of collisions and improving the fairness of channel contention.

[0015] Secondly, this application provides a communication device, which can be a chip in a non-AP MLD, such as a Wi-Fi chip. The communication device includes: a processing unit configured to start a medium synchronization delay timer and set an initial value when the transmission of a second station in the non-AP MLD ends, wherein the link pair formed by the link operating the communication device and the link operating the second station is an NSTR link pair; a transceiver unit configured to receive a PPDU carrying an MPDU containing an RTS frame; the processing unit is further configured to reset the count value of the medium synchronization delay timer to 0 when the RTS frame is sent by a first access point and the link operating the first access point does not belong to any NSTR link pair of the AP MLD to which the first access point belongs. The first access point is an access point associated with the communication device, or the first access point is another access point in a multi-BSSID where the access point associated with the communication device is located.

[0016] Optionally, the above initial values ​​are either set by the AP or are default values ​​specified by the standard.

[0017] In conjunction with the second aspect, in one possible implementation, the link in which the first access point operates does not belong to any NSTR link pair of the AP MLD to which the first access point belongs. This can also be understood as: the AP MLD to which the first access point belongs is not an NSTR Mobile AP MLD, and any two links included in the NSTR Mobile AP MLD are NSTRs.

[0018] Optionally, the processing unit is further configured to not reset the count value of the medium synchronization delay timer to 0 when the RTS frame is sent by the first access point and the AP MLD to which the first access point belongs is an NSTR Mobile AP MLD.

[0019] In conjunction with the second aspect, in one possible implementation, the aforementioned processing unit is further configured to not reset the count value of the medium synchronization delay timer to 0 when the aforementioned RTS frame is sent by the first access point and the link in which the first access point operates belongs to any NSTR link pair of the AP MLD to which the first access point belongs.

[0020] Thirdly, this application provides a method for setting a media synchronization delay timer. The method includes: a first access point in an AP MLD starts a media synchronization delay timer and sets an initial value when the transmission of a second access point in the AP MLD ends; the first access point in the AP MLD receives a PPDU carrying an MPDU, the MPDU containing an RTS frame; if the RTS frame is sent by a first site associated with the first access point, and the link operated by the first site does not belong to any NSTR link pair of the non-APMLD to which the first site belongs, then the first access point in the AP MLD resets the count value of the media synchronization delay timer to 0. Here, the link pair consisting of the link operated by the first access point and the link operated by the second access point is an NSTR link pair, meaning that the first and second access points in the AP MLD have NSTR capability. The AP MLD here can be an NSTR Mobile AP MLD. At least one link pair in the link pair of this NSTR Mobile AP MLD is NSTR. It should be understood that the first access point here can be referred to as an AP that has lost media synchronization or an AP in a blind state.

[0021] Optionally, the above initial values ​​are either set by the AP or are default values ​​specified by the standard.

[0022] As can be seen, this solution extends the setting method of the MediumSyncDelay timer on the site side to the AP side. When the first access point loses medium synchronization, the MediumSyncDelay timer is only reset to 0 if the RTS frame received by that first access point comes from a site that is not in a blind state or has not lost medium synchronization. Implementing this technical solution can solve the fairness problem caused to other sites by the AP directly participating in channel contention due to lost medium synchronization, reducing the probability of collisions and improving the fairness of channel contention; it can also reduce the impact of unnecessary restrictions on AP performance, thus improving performance.

[0023] In conjunction with the third aspect, in one possible implementation, the above method further includes: if the RTS frame is sent by a first site associated with the first access point, and the link in which the first site operates belongs to an NSTR link pair of a non-AP MLD to which the first site belongs, then the first access point in the AP MLD does not reset the count value of the medium synchronization delay timer to 0.

[0024] Fourthly, this application provides a communication device, which can be an AP MLD or a chip in the AP MLD, such as a Wi-Fi chip. The communication device includes: a processing unit, configured to start a medium synchronization delay timer and set an initial value when transmission from a second access point in the AP MLD ends, wherein the link pair formed by the link operating on the communication device and the link operating on the second access point is an NSTR link pair; a transceiver unit, configured to receive a PPDU carrying an MPDU containing an RTS frame; the processing unit is further configured to reset the count value of the medium synchronization delay timer to 0 when the RTS frame is sent by a first station associated with the communication device, and the link operating on the first station does not belong to any NSTR link pair of the non-AP MLD to which the first station belongs.

[0025] Optionally, the above initial values ​​are either set by the AP or are default values ​​specified by the standard.

[0026] In conjunction with the fourth aspect, in one possible implementation, the aforementioned processing unit is further configured to not reset the count value of the medium synchronization delay timer to 0 when the aforementioned RTS frame is sent by a first station associated with the communication device, and the link in which the first station operates belongs to an NSTR link pair of a non-AP MLD to which the first station belongs.

[0027] Fifthly, this application provides a communication device, specifically a non-AP MLD, including a processor and a transceiver. The processor is configured to start a medium synchronization delay timer and set an initial value when the transmission at a second station in the non-AP MLD ends, wherein the link pair formed by the link operating in the communication device and the link operating in the second station is a non-simultaneous transmission and reception NSTR link pair; the transceiver is configured to receive a PPDU carrying an MPDU containing an RTS frame; the processor is further configured to reset the count value of the medium synchronization delay timer to 0 when the RTS frame is transmitted by a first access point, and the link operating in the first access point does not belong to any NSTR link pair of the access point multi-link device (AP MLD) to which the first access point belongs; the first access point is an access point associated with the communication device, or the first access point is another access point in a multi-BSSID where the access point associated with the communication device is located.

[0028] Sixthly, this application provides a communication device, specifically an AP MLD, including a processor and a transceiver. The processor is configured to start a medium synchronization delay timer and set an initial value when the transmission of a second access point in the AP MLD ends, wherein the link pair formed by the link operating in the communication device and the link operating in the second access point is an NSTR link pair; the transceiver is configured to receive a PPDU carrying an MPDU containing an RTS frame; the processor is further configured to reset the count value of the medium synchronization delay timer to 0 when the RTS frame is sent by a first station associated with the communication device, and the link operating in the first station does not belong to any NSTR link pair of the non-AP MLD to which the first station belongs.

[0029] In a seventh aspect, this application provides an apparatus implemented in the form of a chip, including an input / output interface and a processing circuit. The apparatus is a chip within a non-AP MLD. The processing circuit is used to start a medium synchronization delay timer and set an initial value when the transmission at the second station in the non-AP MLD ends. The link pair consisting of the link operating at the first station and the link operating at the second station is a non-simultaneous transmission and reception NSTR link pair. The input / output interface is used to input a PPDU received through an antenna and radio frequency circuit. The PPDU carries an MPDU, and the MPDU contains an RTS frame. The processing circuit is further used to reset the count value of the medium synchronization delay timer to 0 when the RTS frame is transmitted by a first access point, and the link operating at the first access point does not belong to any NSTR link pair of the APMLD to which the first access point belongs. The first access point is an access point associated with the first station, or the first access point is another access point in a multi-BSSID where the access point associated with the first station is located.

[0030] Eighthly, this application provides an apparatus implemented in the form of a chip, including an input / output interface and a processing circuit. The apparatus is a chip within an AP MLD. The processing circuit is configured to start a medium synchronization delay timer and set an initial value when transmission at a second access point in the AP MLD ends, wherein the link pair formed by the link operating at the first access point and the link operating at the second access point is an NSTR link pair; the input / output interface is configured to input a PPDU received through an antenna and radio frequency circuit, the PPDU carrying an MPDU containing an RTS frame; the processing circuit is further configured to reset the count value of the medium synchronization delay timer to 0 when the RTS frame is transmitted by a first station associated with the first access point, and the link operating at the first station does not belong to any NSTR link pair of the non-AP MLD to which the first station belongs.

[0031] Ninthly, this application provides a computer-readable storage medium storing program instructions that, when executed on a computer, cause the computer to perform the media synchronization delay timer setting method described in the first aspect or the third aspect.

[0032] In a tenth aspect, this application provides a computer program product containing program instructions, which, when run on a computer, causes the computer to execute the media synchronization delay timer setting method described in the first aspect or the third aspect above.

[0033] Implementing the embodiments of this application can, on the one hand, solve the fairness problem caused to other stations by stations participating in channel contention due to lost medium synchronization, and on the other hand, reduce the impact of unnecessary restrictions on station performance, thereby improving station performance. Attached Figure Description

[0034] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0035] Figure 1 This is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application;

[0036] Figure 2 This is a schematic diagram of multi-link communication provided in an embodiment of this application;

[0037] Figure 3a This is a schematic diagram of the structure of a multi-link device provided in an embodiment of this application;

[0038] Figure 3b This is another structural schematic diagram of the multi-link device provided in the embodiments of this application;

[0039] Figure 4 This is a schematic flowchart of a media synchronization delay timer setting method provided in an embodiment of this application;

[0040] Figure 5 This is another schematic flowchart of the medium synchronization delay timer setting method provided in the embodiments of this application;

[0041] Figure 6 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application;

[0042] Figure 7 This is a schematic diagram of the structure of the communication device 1000 provided in the embodiments of this application. Detailed Implementation

[0043] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0044] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can represent: a, b, c; a and b; a and c; b and c; or a and b and c. Where a, b, and c can be single or multiple.

[0045] In the description of this application, the words "first" and "second" do not limit the quantity or the order of execution, and the words "first" and "second" do not necessarily imply that they are different.

[0046] In this application, the words "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design described as "exemplary," "for example," or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Rather, the use of the words "exemplary," "for example," or "for example" is intended to present the relevant concepts in a specific manner.

[0047] It should be understood that in this application, "when," "if," and "if" all refer to the device making a corresponding action under certain objective circumstances, and are not time-limited, nor do they require the device to make a judgment when it is implemented, nor do they imply any other limitations.

[0048] In this application, the use of singular designations for elements is intended to represent "one or more" rather than "one and only one," unless otherwise specified.

[0049] To facilitate understanding of the methods provided in the embodiments of this application, the system architecture of the methods provided in the embodiments of this application will be described below. It is understood that the system architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application and does not constitute a limitation on the technical solutions provided in the embodiments of this application.

[0050] This application refers to next-generation 802.11 standard station equipment that simultaneously supports communication across multiple links as a multi-link device, where the internal entity responsible for any one link is called a station (STA). If all stations within an MLD are access points (APs), it can be further called an AP MLD; if all stations within an MLD are non-access point stations (non-AP STAs), it can be further called a non-AP MLD. In other words, a multi-link device includes one or more affiliated STAs. An affiliated station is a logical station that can operate on a single link, a single frequency band, or a single channel. The affiliated station can be an access point (AP) or a non-access point station (non-AP STA). 802.11be refers to multi-link devices belonging to AP sites as AP multi-link devices (APMLD), and multi-link devices belonging to non-AP STA sites as non-AP multi-link devices (non-AP MLD).

[0051] Optionally, a multi-link device may include multiple logical stations, each operating on a single link, but multiple logical stations are allowed to operate on the same link. During data transmission, AP MLDs and non-AP MLDs can use link identifiers to identify a link or stations on a link. Before communication, AP MLDs and non-AP MLDs can negotiate or communicate the correspondence between link identifiers and a link or stations on a link. Therefore, during data transmission, it is unnecessary to transmit a large amount of signaling information to indicate the link or stations on the link; carrying the link identifier is sufficient, reducing signaling overhead and improving transmission efficiency.

[0052] Optionally, multi-link devices can implement wireless communication by conforming to the IEEE 802.11 series of protocols. For example, they can follow a site with extremely high throughput, or follow a site based on or compatible with IEEE 802.11be, to communicate with other devices. Of course, other devices may or may not be multi-link devices.

[0053] The technical solutions provided in this application can be applied to scenarios where one node communicates with one or more nodes; they can also be applied to single-user uplink / downlink communication scenarios, multi-user uplink / downlink communication scenarios, and device-to-device (D2D) communication scenarios. In the embodiments of this application, the term "communication" can also be described as "data transmission," "information transmission," or "transmission." The term "transmission" can refer to sending and receiving in general.

[0054] In this context, any of the aforementioned nodes can be either an AP MLD or a non-AP MLD. For example, it could be a scenario where one AP MLD communicates with one or more non-AP MLDs, or a scenario where one non-AP MLD communicates with one or more AP MLDs; or a scenario where AP MLDs communicate with each other, or a scenario where non-AP MLDs communicate with each other. This embodiment of the application does not limit this. Optionally, the aforementioned communication scenarios may also include traditional sites that support transmission on a single link only.

[0055] Optionally, in any of the above scenarios, at least one node has the ability to not send and receive simultaneously, i.e., it has NSTR capability.

[0056] The technical solution provided in this application is mainly applied in WLAN. See also... Figure 1 , Figure 1 This is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of this application. Figure 1 As shown, the wireless communication system includes at least one AP MLD (such as...) Figure 1 AP MLD100 and at least one non-AP MLD (such as Figure 1 (The non-AP MLD200 and non-AP MLD300 are optional). Figure 1 It also includes legacy sites that support transmission over a single link only (such as...). Figure 1 The single-link non-AP STA400 (also known as STA400) is used in this context. The AP MLD is a device that provides services to the non-AP MLD. Multiple links can be used between the non-AP MLD and the AP MLD to improve throughput. A STA within a non-AP MLD can also communicate with an AP within an AP MLD via a single link. Understandably... Figure 1 The number of AP MLDs and non-AP MLDs is merely exemplary. Optionally, the wireless communication system may include at least one MLD with NSTR capability.

[0057] Optional, see Figure 2 , Figure 2 This is a schematic diagram of multi-link communication provided in an embodiment of this application. For example... Figure 2 As shown, the APMLD includes n stations, namely AP1, AP2, ..., APn; the non-AP MLD also includes n stations, namely STA1, STA2, ..., STAn. Communication between MLDs is multi-link communication. Figure 2 Links 1 through n in the network constitute multiple links. In other words, AP MLDs and non-AP MLDs can communicate in parallel using links 1, 2, ..., n. Within an AP MLD, one AP can establish an association with one STA in a non-AP MLD. For example, STA1 in a non-AP MLD can be associated with AP1 in an AP MLD, STA2 in a non-AP MLD can be associated with AP2 in an AP MLD, STAn in a non-AP MLD can be associated with APn in an AP MLD, and so on.

[0058] Optional, see Figure 3a , Figure 3a This is a schematic diagram of a multi-link device provided in an embodiment of this application. The 802.11 standard focuses on the 802.11 physical layer (PHY) and medium access control (MAC) layer portions of the multi-link device. For example... Figure 3a As shown, the multiple STAs in a multi-link device are independent of each other at the low MAC and PHY layers, and also independent at the high MAC layer. See also Figure 3b , Figure 3b This is another structural schematic diagram of the multi-link device provided in the embodiments of this application. For example... Figure 3b As shown, the multiple STAs included in the multi-link device are independent at the low MAC and PHY layers, but share the high MAC layer. Of course, during multi-link communication, the non-AP MLD can adopt an independent high MAC layer structure, while the AP MLD adopts a shared high MAC layer structure; alternatively, the non-AP MLD can adopt a shared high MAC layer structure, while the AP MLD adopts an independent high MAC layer structure; or both the non-AP MLD and AP MLD can adopt a shared high MAC layer structure; or both the non-AP MLD and AP MLD can adopt an independent high MAC layer structure. This application does not limit the internal structure diagram of the multi-link device. Figure 3a and Figure 3bThis is merely an illustrative example. For instance, either the high MAC layer or the low MAC layer can be implemented by a processor in the chip system of a multi-link device, or they can be implemented by different processing modules in a single chip system.

[0059] For example, the multi-link device in the embodiments of this application can be a single-antenna device or a multi-antenna device. For instance, it can be a device with two or more antennas. The embodiments of this application do not limit the number of antennas included in the multi-link device.

[0060] For example, a multi-link device (which can be either a non-AP MLD or an AP MLD) is a device with wireless communication capabilities. This device can be a complete device or a chip or processing system installed in a complete device. Devices with these chips or processing systems installed can implement the methods and functions of the embodiments of this application under the control of these chips or processing systems. For example, the non-AP MLD in the embodiments of this application has wireless transceiver capabilities, can support the 802.11 series protocols, and can communicate with AP MLDs, single-link devices, or other non-AP MLDs. For example, a non-AP MLD is any user communication device that allows users to communicate with an AP and thus with a WLAN. For example, a non-AP MLD can be a user device that can connect to the Internet, such as a tablet, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), or mobile phone, or an IoT node in the Internet of Things, or an in-vehicle communication device in the Internet of Vehicles; a non-AP MLD can also be a chip and processing system in the above-mentioned terminals. An AP MLD is a device that can provide services to a non-AP MLD and can support the 802.11 series of protocols. For example, an AP MLD can be a communication server, router, switch, bridge, or other communication entity. Alternatively, an AP MLD can include various forms of macro base stations, micro base stations, relay stations, etc. Of course, an AP MLD can also be the chip and processing system within these various types of devices, thereby implementing the methods and functions of the embodiments of this application. The 802.11 protocol can be a protocol that supports or is compatible with 802.11be.

[0061] Understandably, multi-link devices can support high-speed, low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can be applied to even more scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-checkout machines, self-ordering machines, etc.). In this application embodiment, the specific forms of non-AP MLD and AP MLD are not limited; they are merely illustrative examples.

[0062] The above briefly describes the system structure of the embodiments of this application. The following is a brief introduction to the blindness problem in multi-link systems.

[0063] When a station on an NSTR link pair in a non-AP MLD transmits a signal, and another station on the same NSTR link pair fails to receive the signal, 802.11be considers the station that cannot receive the signal due to uplink interference (UL interference) to have lost medium synchronization. In other words, if one link in an NSTR MLD (e.g., link 1) is transmitting while another link (e.g., link 2) fails to receive packets normally, the station on the other link is considered to have lost medium synchronization, or simply, is in a blind state. At this time, the station that has lost medium synchronization (i.e., the station on link 2) may miss NAV updates. If this station directly participates in EDCA contention, it will cause fairness issues for other stations. In other words, other stations have successfully competed for EDCA and have reserved a certain period of time (called the transmission opportunity, TXOP) for communication. However, during this reserved period, the communication of other stations may be interfered with by frames sent by stations that have lost media synchronization (i.e., stations on link 2) (such as collisions).

[0064] It should be understood that the "blind state" mentioned in this application can also be called "self-interference state," "unable to receive state," or "deaf state," etc. The "link pair" mentioned in this application can refer to two different links in an MLD. For example, an MLD may have a total of three links: link1, link2, and link3; where link1 and link2 form one link pair, link2 and link3 form another link pair, and link1 and link3 form yet another link pair. The "NSTR link pair" mentioned in this application refers to an MLD that cannot simultaneously perform transmit and receive operations on this link pair, or an MLD that possesses NSTR capability on this link pair.

[0065] Understandingly, NAV can be viewed as a countdown timer that gradually decreases over time. When the countdown reaches 0, the medium is considered idle. Specifically, when a station receives a frame, if the receiving address of the frame is not that station, the station can update the NAV based on the duration field in the received frame. If the receiving address of the frame is that station, it means that station is the receiving station, and the NAV cannot be updated. Before updating the NAV, it can be determined whether the value of the duration field in the current frame is greater than the station's current NAV value. If it is greater, the NAV is updated; otherwise, if it is less than or equal to, the NAV is not updated. The NAV value is calculated from the end time of the received frame.

[0066] Therefore, to address the blind state problem in multi-link systems, the 802.11be standard requires a station that has lost medium synchronization (e.g., a station on link 2) to maintain a MediumSyncDelay timer. When this timer's count is not zero, the station that lost medium synchronization is restricted from engaging in channel contention. For details, see section 35.3.15.7 (Medium access recovery procedure) of the IEEE 802.11be protocol. A station that has lost medium synchronization due to transmission by another station affiliated with the same MLD should start a MediumSyncDelay timer at the end of that transmission event. In other words, the MediumSyncDelay timer sets its initial frame at the end of the frame transmitted on link 1 and begins its countdown. The initial value of the MediumSyncDelay timer can be set by the AP or a default value specified by the standard.

[0067] If the MediumSyncDelay timer count is not zero, and the site that has lost media synchronization attempts to compete for a TXOP, it must use a Request to Send (RTS) frame as the initial frame. (Anon-APSTA affiliated with non-AP MLD that has a nonzero MediumSyncDelay timer that supports obtaining a TXOP: Shall transmit an RTS frame as the first frame of any attempt to obtain a TXOP.)

[0068] If the MediumSyncDelay timer count is not zero, and the station that lost media synchronization receives a Physical Protocol Data Unit (PPDU) carrying a valid Medium Access Control Protocol Data Unit (MPDU), the MediumSyncDelay timer can be reset to zero. (The MediumSyncDelay timer resets to zero when any of the following events occur: The station receives a PPDU with a valid MPDU.) Generally, because a valid MPDU carries a NAV (Network Access Validation), the station that lost media synchronization will set the NAV upon receiving it. Therefore, the station will not directly participate in EDCA contention, but will only participate after the NAV countdown reaches zero. This avoids fairness issues for other stations or interferes with their communication (on Link 2). Here, a valid MDDU can mean that the station that lost media synchronization can parse the MPDU and that the MPDU contains the corresponding content.

[0069] When the MediumSyncDelay timer count is 0, the station that has lost medium synchronization can compete for the channel normally, meaning that the channel competition is unrestricted.

[0070] It should be understood that although one station (e.g., station 1) on the same NSTR link pair is sending a signal while another station (i.e., the station that has lost medium synchronization, such as station 2) cannot receive it normally, station 2 can receive it normally after station 1 finishes sending (because there is no interference from station 1 to station 2 at this time). In other words, a station that has lost medium synchronization may receive a physical protocol data unit (PPDU) after starting the MediumSyncDelay timer.

[0071] Because RTS frames are also valid MPDUs, according to the current 802.11be protocol, if a station that has lost media synchronization receives an RTS frame from another station, it will reset the MediumSyncDelay timer to 0. However, in some cases, even if a station that has lost media synchronization receives an RTS frame from another station, it should not reset the MediumSyncDelay timer to 0. For example, consider the case where a station that has lost media synchronization (let's call it station 1) receives an RTS frame from another station in a blind state (i.e., another station that has lost media synchronization, let's call it station 2). This means that the other station in a blind state (station 2) uses an RTS frame as its initial frame to attempt to compete for a TXOP, and this RTS frame happens to be received by station 1. This is because station 2 has also lost media synchronization, and its channel contention is likely to fail. If station 2's channel contention fails, it means that the channel is currently busy. Since station 1 received the RTS frame sent by station 2, station 1 will reset the count value of the MediumSyncDelay timer to 0. In other words, station 1 is relieved of the channel contention restriction because it received the RTS frame sent by station 2, so station 1 can engage in normal channel contention. However, at this time the channel is busy (i.e. the channel is occupied by a station or is in a station's TXOP). If station 1 engages in normal channel contention, it will still bring fairness issues to other stations. For example, the data sent by station 1 may collide with the data transmitted by other stations.

[0072] Therefore, this application embodiment considers exceptional handling for RTS frames. In one implementation, this application embodiment restricts a station that has lost media synchronization from resetting the MediumSyncDelay timer count to 0 via an RTS frame. Specifically, if the MediumSyncDelay timer count is not 0, and the station that has lost media synchronization receives a PPDU carrying a valid MPDU that does not contain an RTS frame, then the MediumSyncDelay timer count can be reset to 0. In other words, the MediumSyncDelay timer will be reset to 0 when the following event occurs: The STA receives a PPDU with a valid MPDU that does not contain an RTS frame.

[0073] As can be seen, the embodiments of this application can prevent stations that have lost media synchronization from being relieved of channel contention restrictions by receiving RTS frames sent by other stations, thereby reducing the probability of collisions and improving the fairness of channel contention.

[0074] However, RTS frames received by a station that has lost media synchronization may also be sent by a station that is not in a blind state (or a station that has not lost media synchronization). Therefore, directly restricting a station that has lost media synchronization from resetting the MediumSyncDelay timer to 0 when receiving RTS frames would also limit some RTS frames sent by stations that are not in a blind state (or stations that have not lost media synchronization). In other words, this introduces unnecessary restrictions on RTS frames received by a station that has lost media synchronization from stations that are not in a blind state (or stations that have not lost media synchronization), thus affecting the performance of the station that has lost media synchronization.

[0075] Therefore, this application provides a method for setting a medium synchronization delay timer. By distinguishing the sending stations that send RTS frames, the value of the medium synchronization delay timer can be reasonably set. This can solve the fairness problem caused to other stations by stations that have lost medium synchronization participating in channel contention, thereby reducing the probability of collisions and improving the fairness of channel contention. It can also reduce the impact of unnecessary restrictions on station performance, thus improving station performance.

[0076] The technical solution provided in this application will be described in detail below with reference to more accompanying drawings.

[0077] The technical solutions provided in this application are illustrated through multiple embodiments. Embodiment 1 illustrates a method for setting the media synchronization delay timer when at least one link pair in a non-AP MLD is an NSTR. Embodiment 2 illustrates a method for setting the media synchronization delay timer when at least one link pair in an AP MLD is an NSTR. It should be understood that the technical solutions described in Embodiments 1 and 2 of this application can be combined in any way to form new embodiments, and the same or similar parts of the concepts or solutions involved can be referenced or combined with each other. The various embodiments are described in detail below.

[0078] It should be understood that both the AP MLD and non-AP MLD in this application support the 802.11be protocol (also known as Wi-Fi 7, EHT protocol), and can also support other WLAN communication protocols, such as 802.11ax, 802.11ac, etc. It should also be understood that the AP MLD and non-AP MLD in this application can also support next-generation protocols of 802.11be. In other words, the method provided in this application is not only applicable to the 802.11be protocol, but also to next-generation protocols of 802.11be.

[0079] Optionally, both the AP MLD and the non-AP MLD in this application have at least one link pair, meaning that both the AP MLD and the non-AP MLD in this application include at least two links. Optionally, at least one STA in the non-AP MLD of this application is associated with one AP of the AP MLD.

[0080] Example 1

[0081] Embodiment 1 of this application mainly introduces the method for setting the media synchronization delay timer when the station that loses media synchronization is a non-AP STA.

[0082] See Figure 4 , Figure 4This is a schematic flowchart of a media synchronization delay timer setting method provided in an embodiment of this application. Figure 4 As shown, the method for setting the medium synchronization delay timer includes, but is not limited to, the following steps:

[0083] S101, the first station in the non-AP MLD starts the medium synchronization delay timer and sets the initial value when the transmission of the second station in the non-AP MLD ends. The link pair consisting of the link working at the first station and the link working at the second station is a non-simultaneous transmission and reception NSTR link pair.

[0084] S102, the first station in the non-AP MLD receives a Physical Layer Protocol Data Unit (PPDU) carrying a Medium Access Control Protocol Data Unit (MPDU) containing a request to send an RTS frame.

[0085] S103, if the RTS frame is sent by the first access point, and the link in which the first access point operates does not belong to any NSTR link pair of the AP MLD to which the first access point belongs, then the first station in the non-AP MLD resets the count value of the medium synchronization delay timer to 0.

[0086] Optionally, a non-AP MLD may include multiple stations, and each station of the non-AP MLD operates on a single link (an affiliated STA of the non-AP MLD that operates on a link). In this embodiment, the non-AP MLD includes at least two stations: a first station and a second station. Assume the first station operates on the first link, and the second station operates on the second link. The first and second links form a link pair, and this link pair is an NSTR. That is, while the first station of the non-AP MLD is transmitting signals to the second station, it cannot receive signals. In other words, the first station of the non-AP MLD has lost medium synchronization. The first station of the non-AP MLD can also be referred to as a station that has lost medium synchronization or a station that has experienced medium synchronization loss.

[0087] Optionally, the first station of a non-AP MLD starts a MediumSyncDelay timer and sets its initial value when the transmission by the second station of the non-AP MLD ends. In other words, the station (i.e., the first station) that has lost medium synchronization due to transmission by another station affiliated with the same MLD (i.e., the second station) starts a MediumSyncDelay timer at the end of that transmission event. The initial value of this MediumSyncDelay timer can be set by the AP or a default value specified by the standard.

[0088] Optionally, if the MediumSyncDelay timer count is not zero, the first site in the non-AP MLD (i.e., the site that lost media synchronization) receives a PPDU carrying an MPDU containing an RTS frame. Because the site knows the number of links in its associated AP MLD and whether each link pair in the AP MLD is STR or NSTR, if the RTS frame is sent by the first access point, and the link in which the first access point operates does not belong to any NSTR link pair in the AP MLD to which the first access point belongs, then the first site in the non-AP MLD resets or sets the MediumSyncDelay timer count to 0. Here, "the link in which the first access point operates does not belong to any NSTR link pair in the AP MLD to which the first access point belongs" can be understood as: the first access point is not operating on any NSTR link pair in the AP MLD to which it belongs. Alternatively, it can be understood as follows: any link pair formed between the first link operating at the first access point and any other link in the AP MLD to which the first access point belongs, excluding that first link, is an STR link pair. For example, if the AP MLD to which the first access point belongs has three links, link1 to link3, and assuming the first link operating at the first access point is link1; because link1 and link2 form one link pair, link2 and link3 form another link pair, and link1 and link3 form yet another link pair; therefore, link1 and link2 are STR, and link1 and link3 are also STR. Alternatively, it can also be understood as follows: the link where the first access point is located does not belong to any NSTR link pair in the AP MLD to which the first access point belongs. Or, it can also be understood as follows: the first access point is not on any link in any NSTR link pair.

[0089] Optionally, if the RTS frame is sent by the first access point and the link in which the first access point operates belongs to an NSTR link pair of the AP MLD to which the first access point belongs, then the first station in the non-AP MLD does not reset the MediumSyncDelay timer count to 0.

[0090] In one implementation, the first access point mentioned above is an access point associated with the first site. For ease of description, this document refers to the access point associated with the first site as the associated AP. The above method for setting the medium synchronization delay timer can also be described as follows: After a site that has lost medium synchronization (i.e., the first site) receives an RTS frame, if the RTS frame was sent by the associated AP (i.e., the access point associated with the first site), and the associated AP does not belong to any NSTR link pair, then the MediumSyncDelay timer count can be reset to 0 (based on the RTS frame). Otherwise, resetting the MediumSyncDelay timer count to 0 based on the RTS frame is not allowed.

[0091] Because the 802.11be standard defines that when an AP MLD is a Mobile AP MLD, its link pairs can be NSTR; otherwise, all link pairs of the AP MLD must be STR. Furthermore, since an NSTR Mobile AP MLD has only two links, and these two links are NSTR, the above method for setting the medium synchronization delay timer can also be described as follows: After a station that has lost medium synchronization (i.e., the first station) receives an RTS frame, if the RTS frame is sent by the associated AP (i.e., the access point associated with the first station), and the AP MLD to which the associated AP belongs is not an NSTR Mobile AP MLD, then the MediumSyncDelay timer count can be reset to 0 (based on the RTS frame). Otherwise, resetting the MediumSyncDelay timer count to 0 based on the RTS frame is not allowed. In other words, the MediumSyncDelay timer resets to zero when the following event occurs: The station that lost media synchronization (i.e., the first station) receives a PPDU with a valid MPDU that does not contain an RTS frame; unless the RTS frame is transmitted by the associated AP affiliated with an AP MLD that is not an NSTR mobile AP MLD.

[0092] The NSTR Mobile AP MLD in this application embodiment can be extended to more links, and at least some of the link pairs are NSTR. Here, any two links or all link pairs included in the NSTR Mobile AP MLD are NSTR.

[0093] In another implementation, because the 802.11be standard also supports the multiple basic service set (BSS) identifier feature, multiple APs in a multiple BSSID can share radio frequency and operate on the same channel / frequency band in a time-division manner. Therefore, the AP associated with the first site (called the associated AP) and other APs in the multiple BSSID where the associated AP is located operate on the same link in a time-division manner. Therefore, considering multiple BSSIDs, the first access point can also be another access point in the multiple BSSID where the access point associated with the first site (i.e., the associated AP) is located. The above medium synchronization delay timer setting method can also be described as follows: After the site that has lost medium synchronization (i.e., the first site) receives an RTS frame, if the RTS frame is sent by another AP in the multiple BSSID where the associated AP (i.e., the access point associated with the first site) is located, and the other AP (and / or the associated AP) does not belong to any NSTR link pair, then the MediumSyncDelay timer count value can be reset to 0 (based on the RTS frame). Otherwise, the MediumSyncDelay timer count value cannot be reset to 0 based on this RTS frame.

[0094] Alternatively, the above method for setting the medium synchronization delay timer can be described as follows: After a station that has lost medium synchronization (i.e., the first station) receives an RTS frame, if the RTS frame is sent by the associated AP (i.e., the access point associated with the first station) or by another AP in the multiple BSSID where the associated AP is located, and the AP MLD to which the associated AP belongs is not an NSTR Mobile AP MLD, then the MediumSyncDelay timer count value can be reset to 0 (based on the RTS frame). Otherwise, it is not allowed to reset the MediumSyncDelay timer count value to 0 based on the RTS frame. In other words, the MediumSyncDelay timer (count value) will be reset to 0 when the following events occur: the station that has lost medium synchronization (i.e., the first station) receives a PPDU carrying a valid MPDU, and the valid MPDU does not contain an RTS frame; unless the RTS frame is sent by the associated AP (i.e., the AP associated with the first station) or by another AP in the same multiple BSSID as the associated AP, and the AP MLD to which the associated AP belongs is not an NSTR Mobile AP MLD. (the MediumSyncDelay timerresets to zero when the following event occurs:The STAreceives a PPDU with avalid MPDU that does not contain an RTS frame,except the RTS frame istransmitted by the associated AP or another AP in the same multiple BSSID of the associated AP,and the associated AP affiliated with an AP MLD that is notan NSTR mobile AP MLD.)

[0095] As can be seen, in this embodiment, after receiving an RTS frame, the station that has lost medium synchronization (referring to the first station mentioned above) determines whether to set the MediumSyncDelay timer to 0 by judging whether the sending station of the RTS frame and the link that the sending station is operating on belong to an NSTR link pair. The MediumSyncDelay timer can be processed differently depending on the sending station of the RTS frame (in a broad sense, referring to the AP). That is, if the sending station of the RTS frame is in a blind state or has lost medium synchronization, the MediumSyncDelay timer is not allowed to be reset to 0; if the sending station of the RTS frame is not in a blind state or has not lost medium synchronization, the MediumSyncDelay timer is reset to 0. Implementing this embodiment can solve the fairness problem caused to other stations by a station that has lost medium synchronization participating in channel contention, thereby reducing the probability of collisions and improving the fairness of channel contention; it can also reduce the impact of unnecessary restrictions on station performance, thus improving station performance.

[0096] Example 2

[0097] It should be understood that the aforementioned Embodiment 1 mainly considers the station receiving the RTS frame as a non-AP STA, but APs included in the NSTR MobileAP MLD may also lose media synchronization. Therefore, Embodiment 2 of this application mainly introduces a method for setting the media synchronization delay timer when the station losing media synchronization is an AP. Embodiment 2 of this application can be implemented alone or in conjunction with the aforementioned Embodiment 1; this application does not limit its implementation in this regard.

[0098] See Figure 5 , Figure 5 This is another schematic flowchart of the media synchronization delay timer setting method provided in the embodiments of this application. For example... Figure 5 As shown, the method for setting the medium synchronization delay timer includes, but is not limited to, the following steps:

[0099] S201, the first access point in the AP MLD starts the medium synchronization delay timer and sets the initial value when the transmission of the second access point in the AP MLD ends. The link pair formed by the link working at the first access point and the link working at the second access point is an NSTR link pair.

[0100] S202, the first access point in the AP MLD receives a PPDU, which carries an MPDU, and the MPDU contains an RTS frame.

[0101] S203, if the RTS frame is sent by the first site associated with the first access point, and the link in which the first site operates does not belong to any NSTR link pair of the non-AP MLD to which the first site belongs, then the first access point in the AP MLD resets the count value of the medium synchronization delay timer to 0.

[0102] Optionally, the AP MLD in this application embodiment can be an NSTR Mobile AP MLD. Optionally, in this application embodiment, at least one link pair in the NSTR Mobile AP MLD is NSTR. An AP MLD may include multiple APs, and one AP of the AP MLD operates on one link, and one AP can be associated with one STA. The AP MLD in this application embodiment contains at least two access points, namely a first access point and a second access point. Assume that the link on which the first access point operates is the first link, and the link on which the second access point operates is the second link. The first link and the second link form a link pair, and this link pair is NSTR. That is to say, while the first access point of the AP MLD is sending signals to the second access point, it cannot receive signals. Or, in other words, the first access point of the AP MLD has lost medium synchronization. Here, the first access point of the AP MLD can also be called an AP that has lost medium synchronization or an AP that has experienced medium synchronization loss.

[0103] Optionally, the first access point of the AP MLD starts a MediumSyncDelay timer and sets an initial value when the transmission of the second access point of the AP MLD ends. That is, the AP (i.e., the first access point) that lost medium synchronization due to a transmission by another AP (i.e., the second access point) belonging to the same MLD starts the MediumSyncDelay timer when the transmission event ends. The initial value of the MediumSyncDelay timer can be set by the AP or a default value specified by the standard.

[0104] Optionally, if the MediumSyncDelay timer count is not zero, the first access point of the AP MLD (i.e., the AP that lost media synchronization) receives a PPDU carrying an MPDU containing an RTS frame. Because the first access point knows the number of links in its associated non-AP MLD and whether each link pair in the non-AP MLD is STR or NSTR, if the RTS frame is sent by the first site associated with the first access point, and the link operating at the first site does not belong to any NSTR link pair in the non-AP MLD to which the first site belongs, the first access point in the AP MLD resets the medium synchronization delay timer count to 0. For ease of description, this embodiment refers to the first site associated with the first access point as the associated STA. The statement that the link operating at the first site does not belong to any NSTR link pair in the non-AP MLD to which the first site belongs can be understood as: the first site does not operate on any NSTR link pair in the non-AP MLD to which the first site belongs. Alternatively, it can be understood as follows: the link pair formed by the first link operating at the first site and any link in the non-AP MLD to which the first site belongs, excluding the first link itself, is an STR link pair. Alternatively, it can be understood as follows: the link where the first site is located does not belong to any NSTR link pair in the non-AP MLD to which the first site belongs. Alternatively, it can be understood as follows: the first site is not on any link in any NSTR link pair.

[0105] Optionally, if the RTS frame is sent by a first site associated with a first access point, and the link in which the first site operates belongs to an NSTR link pair in a non-AP MLD to which the first site belongs, then the first access point in the AP MLD does not reset the count value of the medium synchronization delay timer to 0.

[0106] In other words, the above method for setting the medium synchronization delay timer can also be described as follows: When an AP (i.e., the first access point) that has lost medium synchronization receives an RTS frame, if the RTS frame is sent by a STA associated with the AP and the link where the STA is located does not belong to any link in any NSTR link pair, then the MediumSyncDelay timer count can be reset to 0 (based on the RTS frame). Otherwise, the MediumSyncDelay timer count cannot be reset to 0 based on the RTS frame. That is, the MediumSyncDelay timer (count value) will be reset to 0 when the following events occur: the site that has lost medium synchronization receives a PPDU carrying a valid MPDU, and the valid MPDU does not contain an RTS frame; unless the site that has lost medium synchronization is an AP (i.e., the first access point) belonging to an NSTR Mobile AP MLD, and the RTS frame is sent by an associated STA belonging to the MLD (i.e., the STA associated with the first access point), and the associated STA is not on any link in any NSTR link pair. (the MediumSyncDelay timer resets to zerowhen the following event occurs:The STA receives a PPDU with a valid MPDU thatdoes not contain an RTS frame,except the STA is an AP affiliated with an NSTRmobile AP MLD,and the RTS is transmitted by an associated STA which isaffiliated with an MLD and the associated STA is not on a link of any NSTRlink pair(s).)

[0107] As can be seen, this application extends the method of setting the MediumSyncDelay timer on the site side to the AP side. When an AP belonging to the NSTR Mobile AP MLD (i.e., the aforementioned first access point) loses media synchronization, the MediumSyncDelay timer is only reset to 0 when the RTS frame received by the AP comes from a site that is not in a blind state or has not lost media synchronization. Implementing this application can solve the fairness problem caused to other sites by the AP directly participating in channel contention due to lost media synchronization, reducing the probability of collisions and improving the fairness of channel contention; it can also reduce the impact of unnecessary restrictions on the performance of the NSTR Mobile AP MLD, thus improving performance.

[0108] As an optional embodiment, the technical solution provided in this application can also be implemented by combining the foregoing Embodiment 1 and Embodiment 2. Specifically, the MediumSyncDelay timer (count value) will be reset to 0 when the following events occur:

[0109] A site that has lost media synchronization receives a PPDU carrying a valid MPDU, but the valid MPDU does not contain an RTS frame; unless the site that has lost media synchronization is a non-AP STA (i.e., the first site), and the RTS frame is sent by an associated AP belonging to an AP MLD (i.e., the AP associated with the first site), and the AP MLD is not an NSTR mobile AP MLD; or the site that has lost media synchronization is an AP belonging to an NSTR mobile AP MLD (i.e., the first access point), and the RTS frame is sent by an associated STA belonging to an MLD (i.e., the STA associated with the first access point), and the associated STA is not on any NSTR link pair. (the MediumSyncDelay timer resets to zero when the following eventoccur:The STA receives a PPDU with a valid MPDU that does not contain an RTS frame,except the STA is a non-AP STA,and the RTS frame is transmitted by the associated AP affiliated with a AP MLD that is not an NSTR mobile AP MLD,or the STA is an AP affiliated with an NSTR mobile AP MLD,and the RTS is transmitted by an associated STA which is affiliated with an MLD and the associated STA is not on a link of any NSTR link pair(s).)

[0110] Optionally, considering multiple BSSIDs, the MediumSyncDelay timer (its count value) will be reset to 0 when the following events occur:

[0111] A station that has lost media synchronization receives a PPDU carrying a valid MPDU, but the valid MPDU does not contain an RTS frame; unless the station that has lost media synchronization is a non-AP STA (i.e., the first station), and the RTS frame is sent by the associated AP (i.e., the access point associated with the first station) or by another AP in the multiple BSSID to which the associated AP belongs, and the AP MLD to which the associated AP belongs is not an NSTR Mobile AP MLD, or the station that has lost media synchronization is an AP (i.e., the first access point) belonging to an NSTR Mobile AP MLD, and the RTS frame is sent by an associated STA (i.e., the STA associated with the first access point) belonging to an MLD, and the associated STA is not on any NSTR link pair link. (the MediumSyncDelaytimer resets to zero when the following event occurs:The STA receives a PPDUwith a valid MPDU that does not contain an RTS frame,except the STA is a non-AP STA,and the RTS frame is transmitted by the associated AP or another AP in the same multiple BSSID of associated AP,and the associated AP affiliatedwith a AP MLD that is not an NSTR mobile AP MLD,or the STAis an AP affiliatedwith an NSTR mobile AP MLD, and the RTS is transmitted by an associatedSTAwhich is affiliated with an MLD and the associated STAis not on a link of any NSTR link pair(s).)

[0112] The foregoing details the method provided in this application. To facilitate the implementation of the above-described solutions in the embodiments of this application, corresponding apparatus or devices are also provided in the embodiments of this application.

[0113] This application embodiment can divide AP MLD and non-AP MLD into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following will combine... Figure 6 and Figure 7 The communication device according to the embodiments of this application is described in detail. The communication device is an AP MLD or a non-AP MLD; further, the communication device can be a device within an AP MLD; or, the communication device can be a device within a non-AP MLD.

[0114] In the case of using integrated units, see Figure 6 , Figure 6 This is a schematic diagram of the communication device provided in an embodiment of this application. Figure 6 As shown, the communication device includes a processing unit 11 and a transceiver unit 12.

[0115] In one design, the communication device can be a non-AP MLD or a chip within a non-AP MLD, such as a Wi-Fi chip. Processing unit 11 is configured to start a media synchronization delay timer and set an initial value when the transmission at the second station in the non-AP MLD ends. The link pair formed by the link operating the communication device and the link operating the second station is an NSTR link pair. Transceiver unit 12 is configured to receive a PPDU carrying an MPDU containing an RTS frame. Processing unit 11 is further configured to reset the count value of the media synchronization delay timer to 0 when the RTS frame is sent by a first access point, and the link operating the first access point does not belong to any NSTR link pair of the AP MLD to which the first access point belongs. The first access point is either an access point associated with the communication device or another access point in a multi-BSSID containing an access point associated with the communication device.

[0116] Optionally, the link in which the first access point operates does not belong to any NSTR link pair of the AP MLD to which the first access point belongs, including: the AP MLD to which the first access point belongs is not an NSTR Mobile AP MLD, and any two links included in the NSTR Mobile AP MLD are NSTRs.

[0117] Optionally, the processing unit 11 is further configured to not reset the count value of the medium synchronization delay timer to 0 when the RTS frame is sent by the first access point and the AP MLD to which the first access point belongs is an NSTR Mobile AP MLD.

[0118] Optionally, the processing unit 11 is further configured to not reset the medium synchronization delay timer to 0 when the RTS frame is sent by the first access point and the link in which the first access point operates belongs to any NSTR link pair of the AP MLD to which the first access point belongs.

[0119] It should be understood that the communication device in this design can perform the aforementioned Embodiment 1, and the above-mentioned operations or functions of each unit in the communication device are respectively to implement the corresponding operations of the non-AP MLD in the aforementioned Embodiment 1. For the sake of brevity, they will not be described in detail here.

[0120] In another design, the aforementioned communication device can be an AP MLD or a chip within the AP MLD, such as a Wi-Fi chip. Processing unit 11 is configured to start a media synchronization delay timer and set an initial value when the transmission from the second access point in the AP MLD ends. The link pair formed by the link operating on the communication device and the link operating on the second access point is an NSTR link pair. Transceiver unit 12 is configured to receive a PPDU carrying an MPDU containing an RTS frame. Processing unit 11 is further configured to reset the count value of the media synchronization delay timer to 0 when the RTS frame is sent by a first station associated with the communication device, and the link operating on the first station does not belong to any NSTR link pair of the non-AP MLD to which the first station belongs.

[0121] Optionally, the processing unit 11 is further configured to not reset the count value of the medium synchronization delay timer to 0 when the RTS frame is sent by a first station associated with the communication device and the link in which the first station operates belongs to an NSTR link pair of a non-AP MLD to which the first station belongs.

[0122] It should be understood that the communication device in this design can perform the aforementioned Embodiment 2, and the above-mentioned operations or functions of each unit in the communication device are respectively to realize the corresponding operations of AP MLD in the aforementioned Embodiment 2. For the sake of brevity, they will not be described in detail here.

[0123] The above describes the AP MLD and non-AP MLD of embodiments of this application. The following describes the possible product forms of the AP MLD and non-AP MLD. It should be understood that any product possessing the above-described features... Figure 6Any product in any form that incorporates the functions of the non-AP MLD or AP MLD described herein falls within the protection scope of the embodiments of this application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the AP MLD and non-AP MLD in the embodiments of this application to these specific examples.

[0124] As a possible product form, the AP MLD and non-AP MLD described in the embodiments of this application can be implemented by a general bus architecture.

[0125] For clarity, see [link to documentation]. Figure 7 , Figure 7 This is a schematic diagram of the structure of the communication device 1000 provided in an embodiment of this application. The communication device 1000 can be an AP MLD or a non-AP MLD, or a chip therein. Figure 7 Only the main components of the communication device 1000 are shown. In addition to the processor 1001 and transceiver 1002, the communication device may further include a memory 1003 and input / output devices (not shown).

[0126] The processor 1001 is mainly used to process communication protocols and communication data, control the entire communication device, execute software programs, and process the data of the software programs. The memory 1003 is mainly used to store software programs and data. The transceiver 1002 may include control circuitry and an antenna. The control circuitry is mainly used for converting baseband signals to radio frequency signals and processing radio frequency signals. The antenna is mainly used for transmitting and receiving radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, and keyboards, are mainly used to receive user input data and output data to the user.

[0127] When the communication device is powered on, the processor 1001 can read the software program in the memory 1003, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be transmitted wirelessly, the processor 1001 performs baseband processing on the data to be transmitted and outputs the baseband signal to the radio frequency (RF) circuit. The RF circuit processes the baseband signal and transmits the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor 1001. The processor 1001 converts the baseband signal into data and processes the data.

[0128] In another implementation, the radio frequency circuitry and antenna can be set up independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antenna can be arranged remotely, independent of the communication device.

[0129] The processor 1001, transceiver 1002, and memory 1003 can be connected via a communication bus.

[0130] In one design, the communication device 1000 can be used to perform the functions of the non-AP MLD in the aforementioned embodiment 1: the processor 1001 can be used to execute Figure 4 Steps S101 and S103, and / or other processes used to perform the techniques described herein; transceiver 1002 can be used to perform Figure 4 Step S102 in the document, and / or other processes used in the techniques described herein.

[0131] In another design, the communication device 1000 can be used to perform the functions of the AP MLD in the aforementioned embodiment two: the processor 1001 can be used to perform... Figure 5 Steps S201 and S203, and / or other processes used to perform the techniques described herein; transceiver 1002 can be used to perform Figure 5 Step S202 in the document, and / or other processes used in the techniques described herein.

[0132] In any of the above designs, the processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0133] In any of the above designs, the processor 1001 may store instructions, which may be computer programs. These computer programs, running on the processor 1001, cause the communication device 1000 to execute the methods described in any of the above method embodiments. The computer program may be embedded in the processor 1001; in this case, the processor 1001 may be implemented in hardware.

[0134] In one implementation, the communication device 1000 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the foregoing method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal-oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal-oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon-germanium (SiGe), gallium arsenide (GaAs), etc.

[0135] The scope of the communication device described in this application is not limited thereto, and the structure of the communication device may vary. Figure 7 The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0136] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0137] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0138] (3) ASIC, such as modem;

[0139] (4) Modules that can be embedded in other devices;

[0140] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.

[0141] (6) Others, etc.

[0142] As a possible product form, the AP MLD and non-AP MLD described in the embodiments of this application can be implemented by a general-purpose processor.

[0143] The general-purpose processor for implementing the non-AP MLD includes processing circuitry and input / output interfaces internally connected and communicating with the processing circuitry. This general-purpose processor can be used to execute the functions of the non-AP MLD described in Embodiment 1 above. Specifically, the processing circuitry can be used to execute... Figure 4 Steps S101 and S103, and / or other processes used to perform the techniques described herein; the input / output interface can be used to perform Figure 4 Step S102 in the document, and / or other processes used in the techniques described herein.

[0144] The general-purpose processor implementing the AP MLD includes processing circuitry and input / output interfaces internally connected and communicating with the processing circuitry. This general-purpose processor can be used to execute the functions of the AP MLD described in Embodiment 2 above. Specifically, the processing circuitry can be used to execute... Figure 5 Steps S201 and S203, and / or other processes used to perform the techniques described herein; the input / output interface can be used to perform Figure 5 Step S202 in the document, and / or other processes used in the techniques described herein.

[0145] It should be understood that the communication devices of the various product forms described above have any of the functions of AP MLD or non-APMLD in the above method embodiments, which will not be elaborated here.

[0146] This application also provides a computer-readable storage medium storing computer program code. When the processor executes the computer program code, the electronic device performs the method in any of the foregoing embodiments.

[0147] This application also provides a computer program product that, when run on a computer, causes the computer to perform the methods in any of the foregoing embodiments.

[0148] This application also provides a communication device, which can exist in the form of a chip. The device includes a processor and an interface circuit. The processor is used to communicate with other devices through a receiving circuit, so that the device can execute the method in any of the foregoing embodiments.

[0149] This application also provides a wireless communication system including an AP MLD and a non-AP MLD, which can perform the methods in any of the foregoing embodiments.

[0150] The steps of the methods or algorithms described in this application can be implemented in hardware or by a processor executing software instructions. The software instructions can consist of corresponding software modules, which can be stored in random access memory (RAM), flash memory, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, portable hard disks, CD-ROMs, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside in an ASIC. Alternatively, the ASIC can reside in a core network interface device. Of course, the processor and storage medium can also exist as discrete components in the core network interface device.

[0151] Those skilled in the art will recognize that, in one or more of the examples above, the functions described in this application can be implemented using hardware, software, firmware, or any combination thereof. When implemented in software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer-readable storage media and communication media, wherein communication media include any medium that facilitates the transmission of a computer program from one place to another. Storage media can be any available medium accessible to a general-purpose or special-purpose computer.

[0152] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of this application. It should be understood that the above description is only a specific embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made on the basis of the technical solution of this application should be included within the scope of protection of this application.

Claims

1. A method for setting a medium synchronization delay timer, characterized in that, include: When the transmission of the second site in the non-AP MLD ends, the first site starts a medium synchronization delay timer and sets an initial value. The link pair consisting of the link operated by the first site and the link operated by the second site is a non-simultaneous transmission and reception NSTR link pair, and the initial value is not 0. The first station in the non-AP MLD receives a Physical Layer Protocol Data Unit (PPDU), which carries a Medium Access Control Protocol Data Unit (MPDU) and contains a Request to Send RTS (RTS) frame. If the RTS frame is sent by the first access point, and the link in which the first access point operates does not belong to any NSTR link pair of the access point multi-link device (AP MLD) to which the first access point belongs, then the first station in the non-AP MLD will reset the count value of the medium synchronization delay timer to 0. The first access point is an access point associated with the first site, or the first access point is another access point in the Multiple Basic Service Set Identifier (BSSID) where the access point associated with the first site is located.

2. The method according to claim 1, characterized in that, The link in which the first access point operates does not belong to any NSTR link pair of the access point multi-link device (AP MLD) to which the first access point belongs, including: The AP MLD to which the first access point belongs is not an NSTR mobile AP MLD, and any two links included in the NSTR mobile AP MLD are NSTR.

3. The method according to claim 2, characterized in that, The method further includes: If the RTS frame is sent by the first access point, and the AP MLD to which the first access point belongs is an NSTR mobile AP MLD, then the first station in the non-AP MLD will not reset the count value of the medium synchronization delay timer to 0.

4. The method according to claim 1, characterized in that, The method further includes: If the RTS frame is sent by the first access point, and the link operated by the first access point belongs to an NSTR link pair of the AP MLD to which the first access point belongs, then the first station in the non-AP MLD will not reset the count value of the medium synchronization delay timer to 0.

5. A method for setting a medium synchronization delay timer, characterized in that, include: The first access point in the AP MLD starts a medium synchronization delay timer and sets an initial value when the transmission of the second access point in the AP MLD ends. The link pair formed by the link working at the first access point and the link working at the second access point is an NSTR link pair, and the initial value is not 0. The first access point in the AP MLD receives a PPDU, which carries an MPDU and contains an RTS frame. If the RTS frame is sent by a first site associated with the first access point, and the link operated by the first site does not belong to any NSTR link pair of the non-AP MLD to which the first site belongs, then the first access point in the AP MLD will reset the count value of the medium synchronization delay timer to 0.

6. The method according to claim 5, characterized in that, The method further includes: If the RTS frame is sent by a first site associated with the first access point, and the link operated by the first site belongs to an NSTR link pair of a non-AP MLD to which the first site belongs, then the first access point in the AP MLD will not reset the count value of the medium synchronization delay timer to 0.

7. A communication device, characterized in that, include: The processing unit is used to start a medium synchronization delay timer and set an initial value when the transmission at the second station in the non-AP MLD ends. The link pair consisting of the link working at the first station and the link working at the second station is an NSTR link pair, and the initial value is not 0. A transceiver unit is used to receive a PPDU, wherein the PPDU carries an MPDU, and the MPDU contains an RTS frame. The processing unit is further configured to reset the count value of the medium synchronization delay timer to 0 when the RTS frame is sent by the first access point and the link in which the first access point is working does not belong to any NSTR link pair of the access point multi-link device (AP MLD) to which the first access point belongs. The first access point is an access point associated with the first site, or the first access point is another access point in the Multiple Basic Service Set Identifier (BSSID) where the access point associated with the first site is located.

8. The communication device according to claim 7, characterized in that, The link in which the first access point operates does not belong to any NSTR link pair of the access point multi-link device (AP MLD) to which the first access point belongs, including: The AP MLD to which the first access point belongs is not an NSTR mobile AP MLD, and any two links included in the NSTR mobile AP MLD are NSTR.

9. The communication device according to claim 8, characterized in that, The processing unit is further configured to: When the RTS frame is sent by the first access point and the AP MLD to which the first access point belongs is an NSTR mobile AP MLD, the count value of the medium synchronization delay timer is not reset to 0.

10. The communication device according to claim 7, characterized in that, The processing unit is further configured to: When the RTS frame is sent by the first access point, and the link in which the first access point operates belongs to an NSTR link pair of the AP MLD to which the first access point belongs, the count value of the medium synchronization delay timer is not reset to 0.

11. A communication device, characterized in that, include: The processing unit is used to start a medium synchronization delay timer and set an initial value when the transmission of the second access point in the AP MLD ends. The link pair consisting of the link working at the first access point and the link working at the second access point is an NSTR link pair, and the initial value is not 0. A transceiver unit is used to receive a PPDU, wherein the PPDU carries an MPDU, and the MPDU contains an RTS frame. The processing unit is further configured to reset the count value of the medium synchronization delay timer to 0 when the RTS frame is sent by a first site associated with the first access point, and the link in which the first site operates does not belong to any NSTR link pair of the non-AP MLD to which the first site belongs.

12. The communication device according to claim 11, characterized in that, The processing unit is further configured to: When the RTS frame is sent by a first site associated with the first access point, and the link operated by the first site belongs to an NSTR link pair of a non-AP MLD to which the first site belongs, the count value of the medium synchronization delay timer is not reset to 0.

13. A communication device, characterized in that, The device includes a processor and a transceiver, the transceiver being used to send and receive PPDUs, and the processor, when executing program instructions, causing the communication device to perform the method of any one of claims 1-6.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores program instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-6.

15. A computer program product containing program instructions, characterized in that, When the program instructions are run on a computer, the computer performs the method as described in any one of claims 1-6.

Images