Relay communication method and wireless communication device

Abstract

Embodiments of the present application provide a relay communication method and a wireless communication device. The relay communication method is performed on a relay communication device, and comprises: sending a capability parameter of the relay communication device to an access point (AP) and / or a non-AP station (STA), wherein the capability parameter includes one or more of the following: cached information used for indicating that the relay communication device is available for relay; information indicating whether a battery state of the relay communication device supports a relay service; multi-link relay operation configuration information, used for indicating whether the relay communication device supports a multi-link relay operation and / or indicating a link that can support relay reception or transmission; cached information used for indicating that the relay communication device serves as an AP or a non-AP STA; information used for indicating the maximum number of service devices supported by the relay communication device; and information used for indicating the number of service devices that the relay communication device can currently support.

Description

Relay communication method and wireless communication device Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technology, and more particularly to a relay communication method and a wireless communication device. Background Art

[0002] The existing 802.11 standards typically consider direct communication between one access point (AP) and one or more associated non-AP stations (STAs). However, when the STA is far from the AP, high path loss or severe interference can lead to poor link quality (SNR or SINR), thus affecting the communication rate. Therefore, in 802.11bn, improving the throughput of distant users through relays has become a research focus. Designing a highly reliable and low-latency relay mechanism is an urgent issue. Existing technologies do not substantially address the issue of fast / low-latency relay link switching after a relay failure is detected, nor do they discuss or design methods for enhancing relay reliability. Therefore, a relay communication method and wireless communication device are needed to improve existing technologies.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a relay communication method and a wireless communication device to improve the problems of the prior art and other problems.

[0005] A relay communication method provided in an embodiment of the present application is executed on a relay communication device, wherein the relay communication method includes: sending capability parameters of the relay communication device to an access point AP and / or a non-AP station STA, wherein the capability parameters include one or more of the following: cache information indicating that the relay communication device can be used for relaying; information on whether the power status of the relay communication device can be used for relay service; multi-link relay operation configuration information, indicating whether the relay communication device supports multi-link relay operation and / or indicates links that can support relay reception or transmission; cache information indicating that the relay communication device acts as an AP or a non-AP STA; information indicating the maximum number of service devices supported by the relay communication device; and information indicating the number of service devices that the relay communication device can currently support.

[0006] Through the above technical solution, a relay communication device sends its capability parameters to APs and / or non-AP STAs. This allows surrounding access point multi-link devices (AP MLDs) and non-AP MLDs to understand the relay communication device's capabilities and select a relay communication device accordingly. Relaying can extend Wi-Fi signal coverage and transmission distance, improve data rates for users at the cell edge, reduce latency, and enhance user experience.

[0007] An embodiment of the present application provides a relay communication method, wherein the relay communication method includes: confirmation during multi-relay transmission, wherein the confirmation during multi-relay transmission includes confirmation when multiple links of a relay are used to provide relay transmission services to the same non-AP station STA or access point AP, or confirmation when different links of multiple relays are used to provide relay transmission services to the same non-AP STA or AP.

[0008] The above technical solution confirms when multiple links of a single relay are used to provide relay transmission services to the same non-AP STA, or when different links of multiple relays are used to provide relay transmission services to the same non-AP STA. This allows access point multi-link devices (AP MLDs) and non-AP multi-link devices (non-AP MLDs) surrounding the relay communication device to understand the capabilities of the relay communication device and select a relay communication device accordingly. Relays can extend Wi-Fi signal coverage and transmission distance, improve data rates for users at the cell edge, reduce latency, and enhance the user experience.

[0009] A relay communication method provided by an embodiment of the present application is executed on a first node, wherein the relay communication method includes: receiving capability parameters of the relay communication device sent by the relay communication device, wherein the capability parameters include one or more of the following: cache information indicating that the relay communication device can be used for relaying; information on whether the power status of the relay communication device can be used for relay service; multi-link relay operation configuration information, indicating whether the relay communication device supports multi-link relay operation and / or indicates links that can support relay reception or transmission; cache information indicating that the relay communication device acts as an AP or a non-AP STA; information indicating the maximum number of service devices supported by the relay communication device; and information indicating the number of service devices that the relay communication device can currently support.

[0010] Through the above technical solution, the first node receives the capability parameters of the relay communication device sent by the relay communication device. This allows the access point multi-link devices (AP MLDs) and non-AP MLDs surrounding the relay communication device to understand the capabilities of the relay communication device and select a relay communication device accordingly. Relaying can extend Wi-Fi signal coverage and transmission distance, improve data rates for users at the cell edge, reduce latency, and enhance the user experience.

[0011] A wireless communication device provided in an embodiment of the present application includes: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the above-mentioned relay communication method.

[0012] The relay communication device provided in the embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned relay communication method.

[0013] The first node provided in an embodiment of the present application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the above-mentioned relay communication method.

[0014] The chip provided in the embodiment of the present application is used to implement the above-mentioned relay communication method.

[0015] Specifically, the chip includes: a processor for calling and running a computer program from a memory, so that a device equipped with the chip executes the above-mentioned relay communication method.

[0016] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, which enables a computer to execute the above-mentioned relay communication method.

[0017] The computer program product provided in an embodiment of the present application includes computer program instructions, which enable a computer to execute the above-mentioned relay communication method.

[0018] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned method for relay communication.

[0019] Through the above technical solution, the relay communication device sends its capability parameters to the AP and / or non-AP STA. This allows the access point multi-link devices (AP MLDs) and non-AP MLDs surrounding the relay communication device to understand the relay communication device's capability information and select a relay communication device accordingly. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0021] FIG1A is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0022] FIG1B is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0023] FIG1C is a schematic diagram of an ultra-high reliability (UHR) relay capability unit;

[0024] FIG2A is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0025] FIG2B is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0026] FIG2C is a flow chart of a method for detecting a relay link failure and notifying a relay status according to an embodiment of the present application;

[0027] FIG2D is a flow chart of a method for detecting a relay link failure and notifying a relay status according to an embodiment of the present application;

[0028] FIG2E is a schematic diagram of a relay status notification frame provided in an embodiment of the present application;

[0029] FIG3A is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0030] FIG3B is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0031] FIG3C is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0032] FIG4A is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0033] FIG4B is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0034] FIG5 is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0035] FIG6A is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0036] FIG6B is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0037] FIG6C is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0038] FIG7A is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0039] FIG7B is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0040] FIG8 is a schematic diagram of a low-latency relay mechanism provided in an embodiment of the present application;

[0041] FIG9A is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0042] FIG9B is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0043] FIG9C is a schematic diagram of a flow chart of a relay communication method provided in an embodiment of the present application;

[0044] FIG10 is a schematic structural diagram of a wireless communication device provided in an embodiment of the present application;

[0045] FIG11 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0046] FIG12 is a schematic block diagram of a wireless communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0048] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0049] In some embodiments of the present application, "AP" may represent an AP STA or an AP MLD. This means that the terms "AP" and "AP STA" may be used interchangeably. "STA" may represent an AP STA or a non-AP STA or an AP MLD or a non-AP MLD. This means that the terms "STA" and "AP STA" may be used interchangeably. "non-AP STA" may represent a non-AP MLD. This means that the terms "non-AP STA" and "non-AP MLD" may be used interchangeably.

[0050] In some embodiments of the present application, an AP can be either an AP STA that does not support multilink or an AP MLD that supports multilink; a relay can be either a Relay STA that does not support multilink or a Relay MLD that supports multilink; and a STA can be either a non-AP STA that does not support multilink or a non-AP MLD that supports multilink. Some embodiments of the present application may use related names interchangeably.

[0051] Table 1: Definitions of Abbreviations

[0052] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions related to the embodiments of the present application are described below.

[0053] FIG1A is a flow chart of a relay communication method provided in an embodiment of the present application. As shown in FIG1A , the relay communication method, executed on a relay communication device, includes at least one of the following operations: Operation 101A: Sending capability parameters of the relay communication device to an access point (AP) and / or a non-AP station (STA). The capability parameters include one or more of the following: cache information indicating whether the relay communication device can be used for relaying; information indicating whether the power status of the relay communication device can be used for relay services; multi-link relay operation configuration information indicating whether the relay communication device supports multi-link relay operations and / or indicating links that can support relay reception or transmission; cache information indicating whether the relay communication device functions as an AP or a non-AP STA; information indicating the maximum number of service devices supported by the relay communication device; and information indicating the number of service devices that the relay communication device can currently support.

[0054] Through the above technical solution, a relay communication device sends its capability parameters to APs and / or non-AP STAs. This allows access point multi-link devices (AP MLDs) and non-AP MLDs surrounding the relay communication device to understand the relay communication device's capability information and select a relay communication device accordingly. This relay can extend Wi-Fi signal coverage and transmission distance, improve speeds for users at the cell edge, reduce latency, and enhance user experience.

[0055] FIG1B is a flow chart of a relay communication method provided in an embodiment of the present application. As shown in FIG1B , a relay communication method is executed on a first node and includes at least one of the following operations: Operation 101B: Receive capability parameters of the relay communication device sent by the relay communication device. The capability parameters include one or more of the following: cache information indicating that the relay communication device can be used for relaying; information indicating whether the power status of the relay communication device can be used for relay service; multi-link relay operation configuration information indicating whether the relay communication device supports multi-link relay operation and / or indicates the links that can support relay reception or transmission; cache information indicating that the relay communication device acts as an AP or a non-AP STA; information indicating the maximum number of service devices supported by the relay communication device; and information indicating the number of service devices that the relay communication device can currently support. The first node can act as an AP and / or a non-AP STA.

[0056] Through the above technical solution, the first node receives the capability parameters of the relay communication device sent by the relay communication device. This allows the access point multi-link devices (AP MLDs) and non-AP MLDs surrounding the relay communication device to understand the capabilities of the relay communication device and select a relay communication device accordingly. This relay can extend Wi-Fi signal coverage and transmission distance, improve data rates for users at the cell edge, reduce latency, and enhance user experience.

[0057] In some embodiments of the present application, the relay communication device sending the capability parameter to the AP and / or the non-AP STA includes: sending a first frame to the AP and / or the non-AP STA. The first frame carries an ultra-high reliability (UHR) relay capability unit, and the UHR relay capability unit includes one or more of the following fields: a relay operation buffer status field, a power status field, a multi-link device (MLD) relay description field, a relay STA buffer status field, a maximum supported STA field, and an available supported STA field. The relay operation buffer status field indicates buffer information available for relaying by the relay communication device, the power status field indicates whether the power status of the relay communication device is available for relay service, the MLD relay description field indicates the multi-link relay operation configuration information, the relay STA buffer status field indicates buffer information of the relay communication device as an AP or a non-AP STA, the maximum supported STA field indicates the maximum number of service devices supported by the relay communication device, and the available supported STA field indicates the number of service devices currently supported by the relay communication device.

[0058] Some embodiments of the present application regarding the capability parameters of the relay communication device will be described in detail below.

[0059] Example: Capability parameters / unit design of relay communication equipment

[0060] The primary function of a relay communication device is to receive (data) frames from the previous node, buffer them, and then send them to the next node during the next transmission opportunity (non-TXOP). Therefore, the relay communication device's capability parameters should at least include a buffer status indicator, an indication of the maximum number of service devices supported by the relay communication device, and an indication of the relay communication device's battery level. Furthermore, the relay communication device itself may also be an AP / non-AP STA, so the relay communication device's buffer status indicator may indicate both the buffer status of the relay communication device and the buffer status of its own AP / non-AP STA.

[0061] The design of the UHR relay capability unit is shown in Figure 1C, which mainly includes one or more of the following fields:

[0062] Buffer Status for Relay Operation field: Indicates the relay communication device's buffer information available for relaying, including the buffer value, scaling factor, and type (and / or priority) of the buffered service. When the buffer value is set to 0 (i.e., all bits indicating the buffer value are set to 0), the relay communication device's buffer is full and cannot receive and buffer new relay data.

[0063] Buffer Status of Relay STA field: Indicates the cache information of the relay as an AP / non-AP STA, including the cache value, scaling factor, cache service type (priority), and other information. This field is optional because it can be replaced by the QoS Control field or BSR Control field in the relevant frame structure.

[0064] Maximum Supported STAs field: indicates the maximum number of nodes (AP / non-AP STA) that the relay communication device can provide relay services to as a relay.

[0065] Available Supported STAs field: Indicates how many nodes (AP / non-AP STA) the relay communication device can provide relay services to as a relay. When the number of nodes served by the relay reaches the value indicated by the Maximum Supported STAs field, the Available Supported STAs field is set to 0, indicating that the current relay cannot provide relay services to new nodes.

[0066] Power Status field: Contains at least two status indications: one status (e.g., High Power) indicates that the relay has sufficient power and can continue to provide relay services; the other status (e.g., Low Power) indicates that the relay has insufficient power and cannot continue to provide relay services;

[0067] MLD Relay Profile field (MLD relay description field): The MLD relay description field is used to indicate the multi-link relay operation configuration information. Indicates whether the relay communication device supports multi-link relay operation, and specifically may also include the link IDs (Link ID)s that the relay communication device supports relay operation, such as which links (link) support reception in relay operation, which links support transmission in relay operation, etc. For specific content, please refer to the definition of Available Link ID 1~m field (Available Link ID 1~m field) and / or Peer STA ID of Available Link ID 1~m field (Peer STA ID field of Available Link ID 1~m) below.

[0068] In some embodiments of the present application, the first frame is a probe request frame, a probe response frame, a multilink (ML) probe request frame, an ML probe response frame, an association request frame, or an association response frame. In other words, a UHR Relay Capabilities element may be carried in a probe request frame, a probe response frame, an ML probe request frame, an ML probe response frame, an association request frame, an association response frame, etc., sent by a relay communication device to inform the AP and / or non-AP STA of the relay-related capability information possessed by the relay communication device.

[0069] In some embodiments of the present application, the above design takes the UHR Relay Capabilities element carrying the capability parameters of the relay communication equipment as an example. It is also possible to use reserved bits (bits) in the frame or redefine certain bits to indicate the above fields. This application does not impose any restrictions.

[0070] The effect achieved by this embodiment is that the relay communication device sends its capability parameters / units to the surrounding AP MLDs and non-AP MLDs, allowing the surrounding AP MLDs and non-AP MLDs to understand the capabilities and status information of the relay communication device. The AP MLDs and non-AP MLDs can give priority to relay communication devices with more remaining buffer, more remaining power, and more devices that can be supported, thereby ensuring more stable and fast relay transmission.

[0071] FIG2A is a flow chart illustrating a relay communication method according to an embodiment of the present application. As shown in FIG2A , the relay communication method, executed on a relay communication device, includes at least one of the following operations: Operation 201A: Sending capability parameters of the relay communication device to an AP and / or a non-AP STA. Operation 202A: Sending relay status notification information to the AP and / or the non-AP STA, wherein the relay status notification information indicates the current status of the relay communication device.

[0072] Through the above technical solution, the relay communication device sends relay status notification information to the AP and / or non-AP STA. In response to the relay status notification information, operations such as stopping relay operations, initiating relay switching, and switching relay links can be promptly implemented. In the above embodiment, the relay link fault detection and relay status notification methods are implemented in conjunction with the relay communication device's capability parameter / unit design.

[0073] Figure 2B is a schematic flow diagram of a relay communication method provided in an embodiment of the present application. As shown in Figure 2B, a relay communication method, executed at a first node, includes at least one of the following operations: Operation 201B: Receive capability parameters of the relay communication device sent by the relay communication device. Operation 202B: Receive relay status information, wherein the relay status information indicates the current status of the relay communication device. The first node may be an AP or a non-AP STA (e.g., an AP or a non-AP MLD).

[0074] Through the above technical solution, the first node receives relay status information. In response to the relay status notification information, it can promptly stop relay operations, initiate relay switching, switch relay links, and perform other operations. In the above embodiment, the relay link fault detection and relay status notification methods are implemented in conjunction with the capability parameters / unit design of the relay communication device.

[0075] In some embodiments of the present application, a relay communication method is performed on a relay communication device, comprising the following operations: sending relay status notification information to the AP and / or the non-AP STA, wherein the relay status notification information is used to indicate the current status of the relay communication device. In some embodiments of the present application, a relay communication method is performed on a first node, comprising the following operations: receiving relay status information, wherein the relay status information is used to indicate the current status of the relay communication device. In the above embodiments, the schemes of the relay link fault detection and relay status notification methods are implemented independently of the capability parameters / unit design scheme of the relay communication device.

[0076] In some embodiments of the present application, sending the relay state information to the AP and / or the non-AP STA includes sending a relay state notification frame to the AP and / or the non-AP STA, wherein the relay state notification frame indicates a relay link failure or status information of the relay communication device. In some embodiments of the present application, the relay state information is sent to the AP and / or the non-AP STA periodically or quasi-periodically. In some embodiments of the present application, when a link failure occurs in relay transmission between the relay communication device and one of the AP and the non-AP STA, the relay state information is sent to other devices participating in the relay transmission.

[0077] In some embodiments of the present application, other devices participating in relay transmission include other AP MLDs or non-AP MLDs. Optionally, other devices participating in relay transmission include other AP MLDs (e.g., AP MLD a) or non-AP MLDs (e.g., Relay MLD b) in Figures 3A, 3B, and 3C. Specifically, if the relay link between AP MLD 1 and Relay MLD 1 fails, the relay status information sent by AP MLD 1 may be sent to the other AP MLD (e.g., AP MLD a), the non-AP MLD, or Relay MLD b.

[0078] In some embodiments of the present application, receiving the relay state information includes: when a link failure occurs in the relay transmission between the relay communication device and the second node, the first node receives the relay state information sent by the relay communication device; and in response to the relay state information, the first node performs relay switching or relay link switching. In some embodiments of the present application, receiving the relay state information includes: when a link failure occurs in the relay transmission between the relay communication device and the second node, the first node receives the relay state information sent by the second node; and in response to the relay state information, the first node cooperates with the second node to perform relay switching or relay link switching.

[0079] In some embodiments of the present application, the relay link fault detection and relay status notification methods may be implemented in conjunction with or independently of the relay communication device capability parameter / unit design. For example, the relay communication device capability may be transmitted via other means / frame fields, which may also be used in conjunction with the relay link fault detection and relay status notification methods described below.

[0080] Some embodiments of the present application regarding relay status information will be described in detail below.

[0081] Example: Relay link fault detection and relay status notification method

[0082] In some embodiments of the present application, the link failure determination method is that no response is received within a timeout, that is, if a node sends a frame (such as a request frame, a data frame, etc.) that requires a response to a relay communication device or the relay communication device sends a frame to the next node for more than the timer 1 (Timer1) (Timer1 is set to a time length greater than SIFS) and no response is received, then the relay link is considered to be faulty.

[0083] Relay link failures are divided into two categories, as shown in Figure 2C and Figure 2D:

[0084] Figure 2C is a flow chart of the relay link fault detection and relay status notification method provided in an embodiment of the present application. As shown in Figure 2C, Option 1: If the relay communication device sends a frame to the next node for more than Timer1 time and does not receive a corresponding response frame, the relay communication device considers that the link between it and the next node is faulty.

[0085] In this case, the relay communication device can send a Relay Status Notification frame (for example, to the AP) to inform the AP of the link failure between the relay communication device and the STA. Then, the AP that receives the Relay Status Notification frame may stop using a certain link / links of the current relay communication device to relay data to the STA, or reselect a relay communication device to relay data to the STA, or use the current relay communication device to relay data to other STAs, or use other available links of the current relay communication device to relay data to the STA.

[0086] Figure 2D is a flow chart of the relay link fault detection and relay status notification method provided in an embodiment of the present application. As shown in Figure 2D, option 2: If the previous node sends a frame to the relay communication device for more than Timer1 time and does not receive a corresponding response frame, the previous node of the relay communication device considers that the link between it and the relay communication device is faulty.

[0087] In this case, the AP may send a Relay Status Notification frame (for example, to the STA) to inform the STA of the link failure information between the AP and the relay communication device. Then, the STA that receives the Relay Status Notification frame may stop using the relay to relay data to the AP, or reselect a relay to relay data to the AP, or use the current relay communication device to relay data to other APs, or use other available links of the current relay communication device to relay data to the AP; in this case, the AP may also not send the Relay Status Notification frame, and the AP may reselect other relay communication devices to relay data to the STA.

[0088] In some embodiments of the present application, the feature of the above design is that if the sender completes sending a frame that requires a response once and fails to receive a response frame after exceeding Timer1, it is considered a link failure.

[0089] In some embodiments of the present application, it can also be designed that a link failure is only determined when no response frame is received after multiple retransmissions. Specifically: the sender does not receive a response frame after sending the frame that requires a response for more than PIFS (or DIFS or a time length less than Timer1), and then sends the frame that requires a response again, waits for the response from the receiver, and repeats this x (x is a positive integer) times. It is determined that a link failure is not received when no response from the receiver is received; if the sender receives a response from the receiver before repeatedly sending the frame that requires a response x times, it is not determined to be a link failure.

[0090] In some embodiments of the present application, in addition to the status notification after the relay link failure mentioned above, the relay communication device can also notify the previous node and / or the next node of this status information through the Relay Status Notification frame at any time based on its own status (such as the remaining buffer size, the remaining power, how many devices can be relayed, which links are faulty, which links can be relayed, etc.), so that these nodes can make decisions on other operations. It is worth noting that the relay communication device may also send the Relay Status Notification frame periodically or quasi-periodically to allow surrounding nodes to quickly understand the status of the relay communication device, thereby assisting in the selection of relays or relay links. The period can be determined by the relay communication device itself, or it can be set by the AP MLD during the association process between individual AP MLDs. Among them, quasi-periodic transmission refers to irregular periodic transmission. Quasi-periodic behavior is a repetitive pattern that is unpredictable and cannot be accurately measured. Quasi-periodic refers to having properties similar to a period but not meeting a strict period. In some embodiments of the present application, quasi-periodic refers to one or more periods that do not change significantly within adjacent periods but change over a longer period.

[0091] In some embodiments of the present application, the relay status notification frame includes one or more of the following fields: a relay identifier ID field, used to indicate the status information of the relay communication device corresponding to the relay ID field; a relay operation buffer status field, used to indicate the cache information that the relay communication device can use for relaying; an available supported STA field, used to indicate the number of service devices that the relay communication device can currently support; the power status field, used to indicate whether the power status of the relay communication device can be used for relay service; and an available time length field, used to indicate the continuous working time of the relay communication device corresponding to the relay ID field as a relay.

[0092] In some embodiments of the present application, the relay status notification information also includes the following fields: an available link ID 1~m field, used to indicate the status of the link that can be used for relay transmission of the relay communication device corresponding to the relay ID field, where m is a positive integer; and an opposite-end STA ID field of available link ID 1~m, used to indicate that the available link ID 1~m field corresponds to a link between MLDs.

[0093] In some embodiments of the present application, the relay status notification information also includes the following fields: an unavailable link ID 1~n field, used to indicate the status of the unavailable relay transmission link of the relay communication device corresponding to the relay ID field, where n is a positive integer; and an unavailable link ID 1~n peer STA ID field, used to indicate the link between the MLDs corresponding to the unavailable link ID 1~n fields.

[0094] In some embodiments of the present application, the relay status notification information also includes the following fields: a switching MLD ID field, used to indicate the MLD used by the relay communication device to perform link switching / recovery; and a switching link ID field, used to indicate the link used by the relay communication device to perform link switching / recovery.

[0095] Some embodiments of the relay status notification frame of the present application will be described in detail below.

[0096] FIG2E is a schematic diagram of a relay status notification frame provided in an embodiment of the present application. As shown in FIG2E , the Relay Status Notification frame format is designed as follows:

[0097] Relay ID field: This field indicates which relay status information the current Relay Status Notification frame carries. If the frame is sent by an AP or non-AP STA, the Relay ID field is present. If the frame is sent by a relay, the Relay ID field is not required and can be replaced by the TA field of the frame, as the frame carries the status information of the current relay. The Relay ID field is a bit long, where a is a positive integer. It may be 11, 12, or 13 bits corresponding to the relay's AP-assigned AID, or 48 bits corresponding to the relay's MAC address.

[0098] Buffer Status for Relay Operation field: (consistent with the design in the UHR Relay Capabilities element) This field indicates the cache information available for relaying on the relay corresponding to the Relay ID field. When the cache value is 0 (i.e., all bits indicating the cache value are set to 0), the relay's buffer is full and cannot receive and cache new relay data. The length of the Buffer Status for Relay Operation field is b bits, where b is a positive integer.

[0099] Available Supported STAs field: (consistent with the design in the UHR Relay Capabilities element) indicates how many nodes (APs / non-AP STAs) the relay corresponding to the Relay ID field can provide relay services to. When the Available Supported STAs field is set to 0, it means that the current relay cannot provide relay services to new nodes. The length of the Available Supported STAs field is c bits, where c is a positive integer.

[0100] Power Status field: (consistent with the design in the UHR Relay Capabilities element) indicates the power status of the relay corresponding to the Relay ID field, and contains at least two status indications. For example, if the Power Status field is set to 1, it indicates that the relay corresponding to the Relay ID field has sufficient power and can continue to provide relay services; if the Power Status field is set to 0, it indicates that the relay corresponding to the Relay ID field has insufficient power and cannot continue to provide relay services.

[0101] Available Time Duration field: Indicates how long the relay corresponding to the Relay ID field can continue to work as a relay. d is a positive integer indicating the specific duration. When the Available Time Duration field is set to 0, it means that the current relay can no longer provide relay services.

[0102] Available Link ID 1-m field: Indicates which links of the relay corresponding to the Relay ID field are available for relay transmission. This field recommends that nodes receiving this Relay Status Notification frame switch to the links indicated by the Available Link ID 1-m field for relay operation upon learning of a failure in the original relay link. m is a positive integer.

[0103] Peer STA ID of Available Link ID 1-m field: indicates the MLD to which the Available Link ID 1-m field corresponds, where m is a positive integer. For example, if Relay MLD 1 sends the Relay Status Notification frame with Available Link ID 1 set to 1 and Peer STA ID of Available Link ID 1 set to non-AP MLD 1, then Available Link ID 1 and Available Link ID 1 are used together to indicate that Link 1 between Relay MLD 1 and non-AP MLD 1 is available. For another example, if Relay MLD 1 sends the Relay Status Notification frame with Available Link ID 2 set to 2 and Peer STA ID of Available Link ID 2 set to AP MLD 1, then Available Link ID 2 and Available Link ID 2 are used together to indicate that Link 2 between Relay MLD 1 and AP MLD 1 is available. It is worth noting that the Peer STA ID of Available Link ID 1 to m fields are required only when the Relay Status Notification frame is sent in broadcast / multicast mode. The Peer STA ID of Available Link ID 1 to m fields are not required when the Relay Status Notification frame is sent in unicast mode. 1~m field, because the receiver of this unicast frame is "Peer STA ID of Available Link ID 1~m".

[0104] Unavailable Link ID 1-n field: Indicates which links of the relay corresponding to the Relay ID field are unavailable for relay transmission. This field may not exist. If the Relay Status Notification frame is sent on a link, it indicates that the link is faulty. n is a positive integer.

[0105] Peer STA ID of Unavailable Link ID 1~n field: indicates the MLD to which the Unavailable Link ID 1~n field corresponds, where n is a positive integer. For example, if Relay MLD 1 sends the Relay Status Notification frame with Unavailable Link ID 1 set to 1 and Peer STA ID of Unavailable Link ID 1 set to non-AP MLD 1, then Unavailable Link ID 1 and Unavailable Link ID 1 are used together to indicate that Link 1 between Relay MLD 1 and non-AP MLD 1 is unavailable. For another example, if Relay MLD 1 sends the Relay Status Notification frame with Unavailable Link ID 2 set to 2 and Peer STA ID of Unavailable Link ID 2 set to AP MLD 1, then Unavailable Link ID 2 and Unavailable Link ID 2 are used together to indicate that Link 2 between Relay MLD 1 and AP MLD 1 is unavailable. It is worth noting that the Peer STA ID of Unavailable Link ID 1~n field is required only when the Relay Status Notification frame is sent in broadcast / multicast mode. The Peer STA ID of Unavailable Link ID 1~n field is not required when the Relay Status Notification frame is sent in unicast mode. 1~n field, because the receiver of this unicast frame is "Peer STA ID of Unavailable Link ID 1~n".

[0106] The Switch MLD ID field indicates which MLD the device sending the Relay Status Notification frame will attempt to use for link switching / recovery. This includes using the current Relay MLD (or another link), using another Relay MLD, or directly recovering the direct link with the non-AP MLD. If the device sending the Relay Status Notification frame uses the current relay (or another link) to recover the link, the Switch MLD ID field may not be present because the current relay is indicated by the Relay ID. If the device sending the Relay Status Notification frame uses another relay to recover the link, the Switch MLD ID field is present and indicates the ID of the Relay MLD to be used. If the device sending the Relay Status Notification frame uses the direct link with the non-AP MLD to recover the link, the Switch MLD ID field is present and indicates the ID of the target non-AP MLD. The Switch MLD ID field is also a bits long, where a is a positive integer. It can be 11, 12, or 13 bits corresponding to the AID assigned by the AP, or 48 bits corresponding to the MAC Address.

[0107] Switch Link ID field: Used to indicate which link of the device corresponding to the Recovery MLD ID field the device sending the Relay Status Notification frame will attempt to use for link switching / recovery. If the device sending the Relay Status Notification frame uses the current relay to recover the link, and the Switch MLD ID field does not exist, the Switch Link ID field indicates the link of the relay corresponding to the Relay ID field. n is a positive integer.

[0108] In some embodiments of the present application, the format of the relay status notification information is an action frame format including a status code. The action field format of the relay status notification information includes one or more sequences and information corresponding to the one or more sequences, and the information includes one or more of the following information: category, used to indicate the category of the current frame; public action, used to indicate that the current frame is the relay status notification frame; status code, used to indicate the status code carried by the current frame; relay ID, used to indicate the status information of the relay communication device corresponding to the relay ID; available time length, used to indicate the continuous working time that the relay communication device corresponding to the relay ID can still serve as a relay; available link ID, used to indicate the status of the link that can be used for relay transmission of the relay communication device corresponding to the relay ID; the opposite STA ID of the available link ID, used to indicate that the available link ID corresponds to a link between MLDs; unavailable link ID, used to indicate the status of the link that is unavailable for relay transmission of the relay communication device corresponding to the relay ID; the opposite STA ID of the unavailable link ID, used to indicate the link between MLDs corresponding to the unavailable link ID; switching MLD ID, used to indicate the MLD used by the relay communication device to perform link switching / recovery; and switching link ID, used to indicate the link used by the relay communication device to perform link switching / recovery.

[0109] In some embodiments of the present application, the relay status information is sent by the relay communication device, and the relay status information indicates that a link failure occurs in the transmission on the first link between the relay communication device and the second node; the method also includes: in response to the relay status information, executing: relay transmission to the second node through another relay communication device; or transmission through a direct link between the second node.

[0110] In some embodiments of the present application, the relay communication method further includes: determining whether a transmission failure occurs with the relay communication device on the first link; and when a failure is determined to occur, executing: relay transmission to the second node via another relay communication device; or transmission via a direct link with the second node; or relay transmission via a second link with the relay communication device. In some embodiments of the present application, the relay communication method further includes: sending relay status information, including: sending the relay status information to the second node; or broadcasting the relay status information; or multicasting the relay status information.

[0111] In some embodiments of the present application, the status code includes one or more of the following codes: a code for indicating success; a code for indicating an unspecified failure; a code for indicating that the buffer of the relay communication device used for the relay function is full and the relay service cannot be continued; a code for indicating that the number of devices currently served by the relay communication device has reached the upper limit and the relay service cannot be provided to new devices; a code for indicating that the number of links currently used for the relay function of the relay communication device has reached the upper limit and there are no more links to provide relay services; a code for indicating that the battery of the relay communication device is insufficient and the relay service cannot be continued; and a code for indicating reservation.

[0112] The following describes in detail some embodiments of the present application regarding the format of the relay status notification information, which is an action frame format including a status code.

[0113] In some embodiments of the present application, the relay status notification frame format may be designed as follows:

[0114] Table 2: Relay Status Notification frame Action field format

[0115] The Status Code in Order 3 above is detailed in Table 3 below:

[0116] Table 3: Status codes

[0117] In some embodiments of the present application, the following effects can be achieved through the above operations:

[0118] 1) When a relay link fails, the previous node or relay communication device sends a Relay Status Notification frame to inform other nodes of the relay link failure and promptly stop the relay operation / start switching the relay / switching the relay link;

[0119] 2) When the relay communication device is low on battery power, the buffer is full, the number of supported devices reaches the maximum, or some links fail, the relay communication device proactively sends a Relay Status Notification frame to inform other nodes to promptly suspend the relay operation, switch relays, switch to other links recommended by the Relay Status Notification frame, or retry the relay operation later.

[0120] In some embodiments of the present application, the relay communication method further includes, when the link between the relay communication device and the AP or the non-AP STA is disconnected, the relay communication device performing relay switching or relay link switching. In some embodiments of the present application, the relay communication method further includes, when the relay communication device determines that the first link between the relay communication device and one of the AP and the non-AP STA is disconnected, the relay communication device sending a relay status notification to notify other devices participating in relay transmission that the first link is unavailable. In some embodiments of the present application, the other devices participating in relay transmission are, for example, other AP MLDs or non-AP MLDs. Optionally, the other devices participating in relay transmission are, for example, other AP MLDs (e.g., AP MLD a) or non-AP MLDs (e.g., Relay MLD b) in Figures 3A, 3B, and 3C. Specifically, the relay link between AP MLD 1 and Relay MLD 1 fails. The relay status information sent by AP MLD 1 may be sent to other AP MLDs (eg, AP MLD a), non-AP MLDs, or Relay MLD b. In some embodiments of the present application, the relay communication method also includes: the relay communication device sends a request to one of the AP and the non-AP STA on a second link between the relay communication device and one of the AP and the non-AP STA, and the relay communication device receives a response sent by one of the AP and the non-AP STA on the second link; the relay communication device responds to the response sent by one of the AP and the non-AP STA on the second link; the relay communication device sends data to one of the AP and the non-AP STA on the second link, and the relay communication device receives a confirmation sent by one of the AP and the non-AP STA on the second link; and the relay communication device sends a confirmation to the other of the AP and the non-AP STA on the second link.

[0121] In some embodiments of the present application, receiving the relay state information includes: when a link failure occurs in the relay transmission between the relay communication device and the second node, the first node receives the relay state information sent by the relay communication device; and in response to the relay state information, the first node performs relay switching or relay link switching. In some embodiments of the present application, receiving the relay state information includes: when a link failure occurs in the relay transmission between the relay communication device and the second node, the first node receives the relay state information sent by the second node; and in response to the relay state information, the first node cooperates with the second node to perform relay switching or relay link switching.

[0122] In some embodiments of the present application, the relay communication method also includes, when the AP determines that the first link between the relay communication device and one of the AP and the non-AP STA is interrupted, the AP sends a relay status notification to the node on the first link to notify that the first link is unavailable, and performs relay switching or relay link switching. In some embodiments of the present application, the relay communication method also includes: the AP sends a request to the relay communication device and one of the non-AP STA on a second link between the relay communication device and one of the AP and the non-AP STA, and the AP receives a response sent by the relay communication device and one of the non-AP STA on the second link; the AP responds to the response sent by the relay communication device and one of the non-AP STA on the second link; the AP sends data to the relay communication device and one of the non-AP STA on the second link, and the AP receives a confirmation sent by the relay communication device and one of the non-AP STA on the second link; and the AP performs relay switching or relay link switching in response to the confirmation sent by the relay communication device and one of the non-AP STA on the second link.

[0123] In some embodiments of the present application, the relay communication method further includes, when the non-AP STA determines that the first link between the relay communication device and one of the AP and the non-AP STA is interrupted, the non-AP STA sending a relay status notification to a node on the first link to notify that the first link is unavailable, and performing relay switching or relay link switching. In some embodiments of the present application, the relay communication method further includes: the non-AP STA sends a request to the relay communication device and one of the AP on a second link between the relay communication device and one of the AP and the non-AP STA, and the non-AP STA receives a response sent by the relay communication device and one of the AP on the second link; the non-AP STA responds to the response sent by the relay communication device and one of the AP on the second link; the non-AP STA sends data to the relay communication device and one of the AP on the second link, and the non-AP STA receives a confirmation sent by the relay communication device and one of the AP on the second link; and the non-AP STA performs relay switching or relay link switching in response to the confirmation sent by the relay communication device and one of the AP on the second link.

[0124] Some embodiments of the low-latency relay mechanism of the present application will be described in detail below.

[0125] In some embodiments of the present application, the low-latency relay mechanism focuses on promptly notifying the relay device and / or its previous node and / or its next node upon detecting a relay link failure, and executing relay handover / relay link handover. The specific link recovery method varies depending on whether the link is interrupted between the AP and the relay device or between the relay device and the STA, as described below.

[0126] In some embodiments of the present application, the relay communication method further includes: determining whether a transmission failure occurs with the relay communication device on the first link; when a failure is determined to occur, executing: relay transmission to the second node via another relay communication device; or transmission via a direct link with the second node; or relay transmission via a second link with the relay communication device. In some embodiments of the present application, the relay communication method further includes: sending relay status information, including: sending the relay status information to the second node; or broadcasting the relay status information; or multicasting the relay status information. As shown in Figures 3A, 3B, and 3C, the second node is, for example, an AP.

[0127] Example: The link between AP and Relay is interrupted, and the AP initiates a Relay (or Link) switch.

[0128] As shown in Figures 3A, 3B, and 3C, Relay MLD 1's upstream node (i.e., AP MLD 1) sends a frame (e.g., a Data frame) to Relay MLD 1 on Link 1. If it does not receive a reply (e.g., an Ack frame / BlockAck frame) from Relay MLD 1 within Timer 1, AP MLD 1 considers Link 1 between it and Relay MLD 1 to be disconnected and cannot continue to use Link 1 between AP MLD 1 and Relay MLD 1 to provide relay services to non-AP MLD 1. For details, refer to the designs of some of the above embodiments.

[0129] At this point, AP MLD 1 may send a Relay Status Notification frame on Link 1 to achieve the following functions:

[0130] 1) After receiving the Relay Status Notification frame, other AP MLDs (for example, AP MLD a) operating on Link 1 are informed that Link 1 of Relay MLD 1 cannot provide relay services. Other AP MLDs should avoid using Link 1 of Relay MLD 1 to provide relay services to non-AP MLDs.

[0131] 2) After the non-AP MLD operating on Link 1 receives the Relay Status Notification frame, it will be informed that Link 1 of Relay MLD 1 cannot provide relay service. The non-AP MLD should avoid using Link 1 of Relay MLD 1 to perform relay service. In addition, AP MLD 1 may also use the Relay Status Notification frame to inform the Recovery MLD ID and corresponding Recovery Link ID of the link it will attempt to recover. If the Recovery MLD ID field indicates the ID of the non-AP MLD, the non-AP MLD indicated by the Recovery MLD ID field can switch to the Link indicated by the Recovery Link ID field to prepare to receive the Request frame sent by AP MLD 1.

[0132] 3) After the Relay MLD working on Link 1 receives the Relay Status Notification frame, if the frame contains the Recovery MLD ID field and the Recovery Link ID field, and the Recovery MLD ID field indicates the relay's MLD ID, then the relay corresponding to the Recovery MLD ID field can know which link AP MLD 1 will try to use for link recovery with the Relay MLD. The Relay MLD can then switch to the link indicated by the Recovery Link ID field to prepare to receive (the Request frame sent by AP MLD 1).

[0133] In some embodiments of the present application, AP MLD 1 may not send a Relay Status Notification frame on Link 1.

[0134] This embodiment then designs the following three methods initiated by AP MLD 1 to restore data transmission between AP MLD 1 and non-AP MLD 1:

[0135] Option 1: As shown in Figure 3A, AP MLD 1 attempts to use another Relay MLD to provide relay services to non-AP MLD 1.

[0136] Step 1-1: AP MLD 1 sends a request frame to Relay MLD b on Link 1. If it receives a response frame from Relay MLD b after a SIFS interval, AP MLD 1 assumes that Relay MLD b is functioning normally on Link 1.

[0137] In some embodiments of the present application, AP MLD 1 may select Relay MLD b to use Link 1 to provide relay service to non-AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0138] Step 1-2: AP MLD 1 sends a Data frame to Relay MLD b on Link 1. After a SIFS period, Relay MLD b responds with an Ack / BlockAck frame on Link 1 to AP MLD 1.

[0139] Step 1-3: Relay MLD b sends a relayed Data frame to non-AP MLD 1 on Link 1. After a SIFS, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 1 to Relay MLD b.

[0140] Step 1-4: After receiving the Ack / BlockAck frame from non-AP MLD 1 on Link 1, Relay MLD b sends a relayed Ack / BlockAck frame to AP MLD 1 on Link 1. This completes the relay service provided by AP MLD 1 to non-AP MLD 1 using another Relay MLD (Relay MLD b).

[0141] Option 2: As shown in Figure 3B, AP MLD 1 attempts to restore the direct link with non-AP MLD 1.

[0142] Step 2-1: AP MLD 1 sends a request frame directly to non-AP MLD 1 on Link 1. If AP MLD 1 receives a response frame from non-AP MLD 1 after a SIFS interval, AP MLD 1 considers non-AP MLD 1 to be normal on Link 1.

[0143] In some embodiments of the present application, AP MLD 1 may decide to use Link 1 to directly transmit data to non-AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0144] Step 2-2: AP MLD 1 sends a Data frame to non-AP MLD 1 on Link 1. After a SIFS, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 1. AP MLD 1 thus restores its direct link with non-AP MLD 1.

[0145] Option 3: As shown in Figure 3C, AP MLD 1 attempts to provide relay services to non-AP MLD 1 through other links of the current Relay MLD.

[0146] Step 3-1: AP MLD 1 sends a request frame to Relay MLD 1 on Link 2. If AP MLD 1 receives a response frame from Relay MLD 1 after a SIFS interval, AP MLD 1 assumes that Relay MLD 1 is functioning normally on Link 2.

[0147] In some embodiments of the present application, AP MLD 1 may select Link 2 of Relay MLD 1 to provide relay service to non-AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0148] Step 3-2: AP MLD 1 sends a Data frame to Relay MLD 1 on Link 2. After a SIFS period, Relay MLD 1 responds with an Ack / BlockAck frame on Link 2 to AP MLD 1.

[0149] Step 3-3: Relay MLD 1 sends a relayed Data frame to non-AP MLD 1 on Link 2. After a SIFS period, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 2 to Relay MLD 1.

[0150] Step 3-4: After receiving the Ack / BlockAck frame from non-AP MLD 1 on Link 2, Relay MLD 1 sends a relayed Ack / BlockAck frame to AP MLD 1 on Link 2. This completes the relay service provided by AP MLD 1 to non-AP MLD 1 through other links of the current Relay MLD.

[0151] It is worth noting that the above request frame and response frame are just a nickname. In actual communication, the request frame and response frame can be the following combinations:

[0152] Combination 1: The request frame is an RTS frame, and the response frame is a CTS frame.

[0153] The RTS frame and CTS frame are sent and received one-to-one. If a CTS frame is received after an RTS frame is sent, the link is normal and data can be transmitted and received using the current link. Furthermore, the device receiving the CTS frame can use the RSSI of the CTS frame to determine whether to use the current link for data transmission. The RTS frame and CTS frame also reserve channel usage, preventing unrelated devices from occupying the channel and ensuring that the current link is available for data transmission.

[0154] Combination 2: The request frame is a MU-RTS frame, and the response frame is a CTS frame.

[0155] The MU-RTS frame is multicast / broadcasted to multiple destination nodes. Each destination node that receives the MU-RTS frame responds with a CTS frame. Receiving a CTS frame after sending an MU-RTS frame indicates that the current link is functioning properly and that data can be transmitted and received using the current link. Furthermore, the device receiving the CTS frame can determine whether to use the current link for data transmission based on the RSSI of the CTS frame. The MU-RTS frame combined with the CTS frame also reserves channel usage, preventing unrelated devices from occupying the channel and ensuring that the current link is available for data transmission.

[0156] Combination 3: The Request frame is a BFRP Trigger frame, and the Response frame is an NDP frame.

[0157] The BFRP Trigger frame is multicast / broadcasted to multiple destination nodes. Each destination node that receives the BFRP Trigger frame responds with an NDP frame using the specified parameters on the corresponding resource, as instructed in the BFRP Trigger frame. Receiving an NDP frame after sending a BFRP Trigger frame indicates that the current link is functioning properly and data transmission and reception can be attempted on the current link. Furthermore, the device receiving the NDP frame can use the CSI measured by the NDP frame to determine whether to use the current link for data transmission and reception.

[0158] Combination 4: The Request frame is a Trigger frame of another subtype, and the Response frame is the corresponding response frame.

[0159] For example, a Request frame is a (Basic) Trigger frame, and a Response frame is a Data frame; a Request frame is a BSRP Trigger frame, and a Response frame carries a Buffer Status Report; a Request frame is an NFRP Trigger frame, and a Response frame is an NDP feedback report. The formats and functions of these frames are completely consistent with those in the IEEE 802.11 standard and are not described in detail in the embodiments of this application.

[0160] The effect achieved by this embodiment is that after the previous node of the relay discovers a relay link failure, it can quickly perform relay switching, or relay link switching, or attempt to restore the direct link between the previous node of the relay and the next node of the relay, thereby reducing the data transmission delay between the previous node of the relay and the next node of the relay.

[0161] In some embodiments of the present application, the example of the combination of Request frame and Response frame is applicable to subsequent embodiments and will not be repeated in the subsequent embodiments.

[0162] In some embodiments of the present application, the relay state information is sent by the relay communication device, and the relay state information indicates that a link failure has occurred in transmission on a first link between the relay communication device and a second node; the method further includes, in response to the relay state information, performing: relay transmission to the second node via another relay communication device; or transmitting via a direct link to the second node. As shown in Figures 4A and 4B, the second node is, for example, an AP.

[0163] Example: The AP<->Relay link is interrupted, and the STA initiates a Relay switch.

[0164] As shown in Figures 4A and 4B, Relay MLD 1 sends a frame (e.g., a Data frame) to the next node (i.e., AP MLD 1) on Link 1. If it does not receive a response (e.g., an Ack frame / BlockAck frame) from AP MLD 1 within Timer 1, Relay MLD 1 considers Link 1 between it and AP MLD 1 to be disconnected and cannot continue to use Link 1 between AP MLD 1 and Relay MLD 1 to provide relay services to non-AP MLD 1. For details, refer to the designs of some of the above embodiments.

[0165] After detecting a link failure, Relay MLD 1 sends a Relay Status Notification frame on Link 1. Upon receiving this frame, the non-AP MLD operating on Link 1 is informed that Link 1 between Relay MLD 1 and AP MLD 1 cannot provide relay services. Therefore, the non-AP MLD should avoid using Link 1 between Relay MLD 1 and AP MLD 1 for relay services.

[0166] This embodiment then designs the following two methods for restoring data transmission between non-AP MLD 1 and AP MLD 1, initiated by non-AP MLD 1:

[0167] Option 1: As shown in Figure 4A, non-AP MLD 1 attempts to use another Relay MLD for relaying.

[0168] Step 1: Non-AP MLD 1 sends a request frame to Relay MLD b on Link 1. If it receives a response frame from Relay MLD b after a SIFS interval, non-AP MLD 1 assumes that the communication between it and Relay MLD b on Link 1 is normal.

[0169] In some embodiments of the present application, non-AP MLD 1 may select Relay MLD b to use Link 1 to provide relay service to non-AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0170] Step 2: Non-AP MLD 1 sends a Data frame to Relay MLD b on Link 1. After a SIFS period, Relay MLD b responds with an Ack / BlockAck frame on Link 1 to non-AP MLD 1.

[0171] Step 3: Relay MLD b sends a relayed Data frame to AP MLD 1 on Link 1. After a SIFS period, AP MLD 1 responds with an Ack / BlockAck frame on Link 1 to Relay MLD b.

[0172] Step 4: After receiving the Ack / BlockAck frame from AP MLD 1 on Link 1, Relay MLD b sends a relayed Ack / BlockAck frame to non-AP MLD 1 on Link 1, thus completing the relay process for non-AP MLD 1 using another Relay MLD (i.e., Relay MLD b).

[0173] Option 2: As shown in Figure 4B, non-AP MLD 1 attempts to restore the direct link with AP MLD 1.

[0174] Step 1: Non-AP MLD 1 sends a request frame directly to AP MLD 1 on Link 1. If it receives a response frame from AP MLD 1 after a SIFS interval, non-AP MLD 1 assumes that the communication between it and AP MLD 1 on Link 1 is normal.

[0175] In some embodiments of the present application, non-AP MLD 1 may decide to use Link 1 to directly transmit data to AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0176] Step 2: Non-AP MLD 1 sends a Data frame to AP MLD 1 on Link 1. After a SIFS, AP MLD 1 responds with an Ack / BlockAck frame on Link 1. This restores the direct link between non-AP MLD 1 and AP MLD 1.

[0177] The effect achieved by this embodiment is that after the relay detects a relay link failure with the next node, it can quickly notify the previous node (or next node) to perform relay switching, or attempt to restore the direct link between the previous relay node and the next relay node, thereby reducing the data transmission delay between the previous relay node and the next relay node.

[0178] Example: The link between AP and Relay is interrupted, and the Relay initiates a link switch.

[0179] As shown in Figure 5, this scenario is consistent with some embodiments of Figures 4A and 4B, but the method for restoring relay communication is different. The difference is that after Relay MLD 1 determines that Link 1 between it and AP MLD 1 is disconnected, it can send a Relay Status Notification frame to achieve the following functions:

[0180] After receiving the Relay Status Notification frame, other AP MLDs operating on Link 1 are informed that Link 1 of Relay MLD 1 cannot provide relay services. Other AP MLDs should avoid using Link 1 of Relay MLD 1 to provide relay services for non-AP MLDs. In addition, Relay MLD 1 may also use the Relay Status Notification frame to inform the Recovery MLD ID and corresponding Recovery Link ID of the link it will attempt to recover. If the Recovery MLD ID field indicates the ID of an AP MLD, the AP MLD indicated by the Recovery MLD ID field can switch to the Link indicated by the Recovery Link ID field and prepare to receive the Request frame sent by Relay MLD 1.

[0181] Relay MLD 1 restores the relay link as follows:

[0182] Step 1: Relay MLD 1 sends a request frame to AP MLD 1 on Link 2. If it receives a response frame from AP MLD 1 after a SIFS interval, Relay MLD 1 assumes that the communication between it and AP MLD 1 on Link 2 is normal.

[0183] In some embodiments of the present application, Relay MLD 1 may select Link 2 of AP MLD 1 to provide relay service to non-AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0184] Step 2: Relay MLD 1 sends a Data frame to AP MLD 1 on Link 2. After a SIFS period, AP MLD 1 responds with an Ack / BlockAck frame on Link 2 to Relay MLD 1.

[0185] Step 3: Relay MLD 1 sends a relay Ack / BlockAck frame to non-AP MLD 1 on Link 2. This completes the relay service provided by Relay MLD 1 to non-AP MLD 1 by switching to another link (Link 2).

[0186] The effect achieved by this embodiment is that after the relay detects a relay link failure with the next node, the relay link can be quickly switched, thereby reducing the data transmission delay between the previous relay node and the next relay node.

[0187] In some embodiments of the present application, the relay communication method further includes: determining whether a transmission failure occurs with the relay communication device on the first link; when it is determined that a failure occurs, executing: relay transmission to the second node via another relay communication device; or transmission via a direct link with the second node; or relay transmission via a second link with the relay communication device. In some embodiments of the present application, the relay communication method further includes: sending relay status information, including: sending the relay status information to the second node; or broadcasting the relay status information; or multicasting the relay status information. As shown in Figures 6A, 6B, and 6C, the second node is, for example, a relay.

[0188] Example: The link between Relay<->STA is interrupted, and STA initiates Relay (or Link) switching

[0189] As shown in Figures 6A, 6B, and 6C, Relay MLD 1's upstream node (non-AP MLD 1) sends a frame (e.g., a Data frame) to Relay MLD 1 on Link 1. If non-AP MLD 1 does not receive a response (e.g., an Ack frame / BlockAck frame) from Relay MLD 1 after waiting for Timer 1, it assumes that Link 1 between it and Relay MLD 1 is disconnected and cannot continue to use Link 1 between non-AP MLD 1 and Relay MLD 1 for relaying. For details, refer to the designs of some of the above embodiments.

[0190] At this time, non-AP MLD 1 may send a Relay Status Notification frame on Link 1. In this case:

[0191] 1) If other AP MLDs operating on Link 1 (for example, AP MLD a) receive a Relay Status Notification frame and learn that Link 1 between non-AP MLD 1 and Relay MLD 1 cannot provide relay service, other AP MLDs should avoid using Link 1 between non-AP MLD 1 and Relay MLD 1 for relaying.

[0192] 2) After the non-AP MLD operating on Link 1 receives the Relay Status Notification frame, it will be informed that Link 1 of Relay MLD 1 cannot provide relay service. The non-AP MLD should avoid using Link 1 of Relay MLD 1 to perform relay service. In addition, non-AP MLD 1 may also use the Relay Status Notification frame to inform the Recovery MLD ID and corresponding Recovery Link ID of the link it will attempt to recover. If the Recovery MLD ID field indicates the ID of an AP MLD, the AP MLD indicated by the Recovery MLD ID field can switch to the Link indicated by the Recovery Link ID field to prepare to receive the Request frame sent by non-AP MLD 1.

[0193] 3) After the Relay MLD working on Link 1 receives the Relay Status Notification frame, if the frame contains the Recovery MLD ID field and the Recovery Link ID field, and the Recovery MLD ID field indicates the relay's MLD ID, then the relay corresponding to the Recovery MLD ID field can know which link non-AP MLD 1 will try to use for link recovery with the Relay MLD. The Relay MLD can then switch to the link indicated by the Recovery Link ID field to prepare to receive (the Request frame sent by non-AP MLD 1).

[0194] In some embodiments of the present application, non-AP MLD 1 may also not send a Relay Status Notification frame on Link 1 and directly initiate a Relay (or Link) switching operation.

[0195] This embodiment then designs the following three methods for non-AP MLD 1 to initiate and resume data transmission between AP MLD 1 and non-AP MLD 1:

[0196] Option 1: As shown in Figure 6A, non-AP MLD 1 attempts to use another Relay MLD for relaying.

[0197] Step 1: Non-AP MLD 1 sends a request frame to Relay MLD b on Link 1. If it receives a response frame from Relay MLD b after a SIFS interval, non-AP MLD 1 assumes that the communication between it and Relay MLD b on Link 1 is normal.

[0198] In some embodiments of the present application, non-AP MLD 1 may select Relay MLD b to use Link 1 to provide relay service to non-AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0199] Step 2: Non-AP MLD 1 sends a Data frame to Relay MLD b on Link 1. After a SIFS period, Relay MLD b responds with an Ack / BlockAck frame on Link 1 to non-AP MLD 1.

[0200] Step 3: Relay MLD b sends a relayed Data frame to AP MLD 1 on Link 1. After a SIFS period, AP MLD 1 responds with an Ack / BlockAck frame on Link 1 to Relay MLD b.

[0201] Step 4: After receiving the Ack / BlockAck frame from AP MLD 1 on Link 1, Relay MLD b sends a relayed Ack / BlockAck frame to non-AP MLD 1 on Link 1, thus completing the relay process for non-AP MLD 1 using another Relay MLD (i.e., Relay MLD b).

[0202] Option 2: As shown in Figure 6B, non-AP MLD 1 attempts to restore the direct link with AP MLD 1.

[0203] Step 1: Non-AP MLD 1 sends a request frame directly to AP MLD 1 on Link 1. If it receives a response frame from AP MLD 1 after a SIFS interval, non-AP MLD 1 assumes that the communication between it and AP MLD 1 on Link 1 is normal.

[0204] In some embodiments of the present application, non-AP MLD 1 may decide to use Link 1 to directly transmit data to AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0205] Step 2: Non-AP MLD 1 sends a Data frame to AP MLD 1 on Link 1. After a SIFS, AP MLD 1 replies with an Ack / BlockAck frame on Link 1. This completes the restoration of the direct link between non-AP MLD 1 and AP MLD 1.

[0206] Option 3: As shown in Figure 6C, non-AP MLD 1 attempts to relay through other links of the current Relay MLD.

[0207] Step 1: Non-AP MLD 1 sends a request frame to Relay MLD 1 on Link 2. If it receives a response frame from Relay MLD 1 after a SIFS interval, non-AP MLD 1 assumes that the communication between it and Relay MLD 1 on Link 2 is normal.

[0208] In some embodiments of the present application, non-AP MLD 1 may select Link 2 of Relay MLD 1 to provide relay service to non-AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0209] Step 2: Non-AP MLD 1 sends a Data frame to Relay MLD 1 on Link 2. After a SIFS period, Relay MLD 1 responds with an Ack / BlockAck frame on Link 2 to non-AP MLD 1.

[0210] Step 3: Relay MLD 1 sends a relayed Data frame to AP MLD 1 on Link 2. After a SIFS period, AP MLD 1 responds with an Ack / BlockAck frame on Link 2 to Relay MLD 1.

[0211] Step 4: After receiving the Ack / BlockAck frame from AP MLD 1 on Link 2, Relay MLD 1 sends the relayed Ack / BlockAck frame to non-AP MLD 1 on Link 2, thus completing the relay of non-AP MLD 1 through other links of the current Relay MLD.

[0212] The effect achieved by this embodiment is that after the previous node of the relay discovers a relay link failure, it can quickly perform relay switching, or relay link switching, or attempt to restore the direct link between the previous node of the relay and the next node of the relay, thereby reducing the data transmission delay between the previous node of the relay and the next node of the relay.

[0213] In some embodiments of the present application, the relay state information is sent by the relay communication device, and the relay state information indicates that a link failure has occurred in transmission on a first link between the relay communication device and a second node; the method further includes, in response to the relay state information, performing: relay transmission to the second node via another relay communication device; or transmitting via a direct link with the second node. As shown in Figures 7A and 7B, the second node is, for example, a STA.

[0214] Example: The link between Relay<->STA is interrupted, and the AP initiates a Relay switch.

[0215] As shown in Figures 7A and 7B, Relay MLD 1 sends a frame (for example, a Data frame) to the next node (non-AP MLD 1) on Link 1. If it waits for Timer 1 without receiving a response (for example, an Ack frame or BlockAck frame) from non-AP MLD 1, Relay MLD 1 considers Link 1 between it and non-AP MLD 1 to be disconnected and cannot continue to use Link 1 between non-AP MLD 1 and Relay MLD 1 for relaying. For details, refer to the design in Section 5.2.1.

[0216] At this time, Relay MLD 1 sends a Relay Status Notification frame on Link 1. If AP MLD 1 (and other AP MLDs, such as AP MLD 1) working on Link 1 receives the Relay Status Notification frame, they will know that Link 1 between Relay MLD 1 and non-AP MLD 1 cannot provide relay service. AP MLD should avoid using Link 1 between Relay MLD 1 and non-AP MLD 1 to perform relay service.

[0217] This embodiment then designs the following two methods initiated by AP MLD 1 to restore data transmission between AP MLD 1 and non-AP MLD 1:

[0218] Option 1: As shown in Figure 7A, AP MLD 1 attempts to use another Relay MLD for relaying.

[0219] Step 1: AP MLD 1 sends a request frame to Relay MLD b on Link 1. If it receives a response frame from Relay MLD b after a SIFS interval, AP MLD 1 assumes that the communication between it and Relay MLD b on Link 1 is normal.

[0220] In some embodiments of the present application, AP MLD 1 may select Relay MLD b to use Link 1 to provide relay service to AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0221] Step 2: AP MLD 1 sends a Data frame to Relay MLD b on Link 1. After a SIFS period, Relay MLD b responds with an Ack / BlockAck frame to AP MLD 1 on Link 1.

[0222] Step 3: Relay MLD b sends a relayed Data frame to non-AP MLD 1 on Link 1. After a SIFS, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 1 to Relay MLD b.

[0223] Step 4: After receiving the Ack / BlockAck frame from non-AP MLD 1 on Link 1, Relay MLD b sends a relayed Ack / BlockAck frame to AP MLD 1 on Link 1, completing the relay process for AP MLD 1 using another Relay MLD (i.e., Relay MLD b).

[0224] Option 2: As shown in Figure 7B, AP MLD 1 attempts to restore the direct link with non-AP MLD 1.

[0225] Step 1: AP MLD 1 sends a request frame directly to non-AP MLD 1 on Link 1. If it receives a response frame from non-AP MLD 1 after a SIFS interval, AP MLD 1 assumes that the communication between it and non-AP MLD 1 on Link 1 is normal.

[0226] In some embodiments of the present application, AP MLD 1 may decide to use Link 1 to directly transmit data to non-AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0227] Step 2: AP MLD 1 sends a Data frame to non-AP MLD 1 on Link 1. After a SIFS, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 1. AP MLD 1 thus restores its direct link with non-AP MLD 1.

[0228] The effect achieved by this embodiment is that after the relay detects a relay link failure with the next node, it can quickly notify the previous node (or next node) to perform relay switching, or attempt to restore the direct link between the previous relay node and the next relay node, thereby reducing the data transmission delay between the previous relay node and the next relay node.

[0229] Example: The link between Relay<->STA is interrupted, and the Relay initiates a link switch.

[0230] As shown in Figure 8, this scenario is consistent with some embodiments of Figures 7A and 7B, but the method for restoring relay communication is different. The difference is that after Relay MLD 1 determines that Link 1 between it and non-AP MLD 1 is disconnected, it can send a Relay Status Notification frame to achieve the following functions:

[0231] After receiving the Relay Status Notification frame, other AP MLDs operating on Link 1 will be informed that Link 1 of Relay MLD 1 cannot provide relay services. Other AP MLDs should avoid using Link 1 of Relay MLD 1 to provide relay services for non-AP MLDs. In addition, Relay MLD 1 may also use the Relay Status Notification frame to inform the Recovery MLD ID and corresponding Recovery Link ID of the link it will attempt to recover. If the Recovery MLD ID field indicates the ID of a non-AP MLD, the non-AP MLD indicated by the Recovery MLD ID field can switch to the Link indicated by the Recovery Link ID field and prepare to receive the Request frame sent by Relay MLD 1.

[0232] Relay MLD 1 restores the relay link as follows:

[0233] Step 1: Relay MLD 1 sends a request frame to non-AP MLD 1 on Link 2. If it receives a response frame from non-AP MLD 1 after a SIFS interval, Relay MLD 1 assumes that the communication between it and non-AP MLD 1 on Link 2 is normal.

[0234] In some embodiments of the present application, Relay MLD 1 may select Link 2 of non-AP MLD 1 to provide relay service to AP MLD 1 based on the result (such as RSSI, CSI, etc.) obtained by Request frame+Response frame.

[0235] Step 2: Relay MLD 1 sends a Data frame to non-AP MLD 1 on Link 2. After a SIFS, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 2 to Relay MLD 1.

[0236] Step 3: Relay MLD 1 sends a relay Ack / BlockAck frame to AP MLD 1 on Link 2. This completes the relay service provided by Relay MLD 1 to AP MLD 1 by switching another link (Link 2).

[0237] The effect achieved by this embodiment is that after the relay detects a relay link failure with the next node, the relay link can be quickly switched, thereby reducing the data transmission delay between the previous relay node and the next relay node.

[0238] Figure 9A is a flow chart of the relay communication method provided in an embodiment of the present application. As shown in Figure 9A, the relay communication method includes at least one of the following operations: Operation 901A: Confirmation during multi-relay transmission, and the confirmation during multi-relay transmission includes confirmation when multiple links of a relay are used to provide relay transmission services to the same non-AP station STA or access point AP, or confirmation when different links of multiple relays are used to provide relay transmission services to the same non-AP STA or AP.

[0239] With the above technical solution, the multi-relay transmission confirmation includes confirmation when multiple links of a single relay are used to provide relay transmission services to the same non-AP STA or access point AP, or confirmation when different links of multiple relays are used to provide relay transmission services to the same non-AP STA or AP. In this way, relays can expand Wi-Fi signal coverage and transmission distance, increase data rates for users at the cell edge, reduce latency, and enhance user experience.

[0240] In some embodiments of the present application, the confirmation of using multiple links of a relay to provide relay transmission services to the same non-AP STA or AP includes: a relay communication device uses the multiple different links to send the same data to the same non-AP MLD or AP to provide relay services, and after the same non-AP MLD or AP successfully receives the data on any one of the multiple different links and provides a confirmation, the remaining links of the multiple different links no longer need to perform the same data reception and / or confirmation operations.

[0241] In some embodiments of the present application, the confirmation of using different links of multiple relays to provide relay transmission services to the same non-AP STA or AP includes: multiple relays use the different links to send different data to the same non-AP MLD or AP to provide relay services, and after the same non-AP MLD or AP successfully receives data and gives confirmation on any one of the different links of the multiple relays, the remaining links of the different links of the multiple relays no longer need to perform the same data reception and / or confirmation operations.

[0242] In some embodiments of the present application, the confirmation of using different links of multiple relays to provide relay transmission services to the same non-AP STA or AP includes: multiple relays use the different links to send the same data to the same non-AP MLD or AP to provide relay services, and after the same non-AP MLD or AP successfully receives the data and gives a confirmation on any one of the different links of the multiple relays, the remaining links of the different links of the multiple relays no longer need to perform the same data reception and / or confirmation operations.

[0243] Some embodiments of the present application regarding confirmation during multi-relay transmission will be described in detail below.

[0244] Example: A Relay MLD uses multiple links to transmit data to a non-AP MLD

[0245] As shown in Figure 9B, AP MLD 1 sends Data m to Relay MLD 1 on Link 1, and AP MLD 1 sends Data n to Relay MLD 1 on Link 2. To enhance relay transmission reliability, the contents of Data m and Data n can be identical. When Relay MLD 1 receives Data (m or n) sent by AP MLD 1 on either Link 1 or Link 2, it responds with an Ack / BlockAck frame after a SIFS interval to confirm the receipt. This process can be categorized into the following three operations:

[0246] Option 1: After Relay MLD 1 receives Data m from AP MLD 1 on Link 1, it responds with an Ack / BlockAck frame on Link 1 after a SIFS period. At this point, Relay MLD 1 does not need to respond with an Ack / BlockAck frame on Link 2 for confirmation. This indicates that Relay MLD 1 has successfully received Data m from AP MLD 1.

[0247] Option 2: After Relay MLD 1 receives Data n from AP MLD 1 on Link 2, it sends an Ack / BlockAck frame on Link 2 to confirm the receipt of the data. At this point, Relay MLD 1 does not need to send an Ack / BlockAck frame on Link 1 to confirm the receipt of Data n. This indicates that Relay MLD 1 has successfully received Data n from AP MLD 1.

[0248] Option 3: Relay MLD 1 receives Data m from AP MLD 1 on Link 1 and Data n from AP MLD 1 on Link 2. After a SIFS period, Relay MLD 1 responds with an Ack / BlockAck frame on Link 1 for confirmation. At this time, Relay MLD 1 also responds with an Ack / BlockAck frame on Link 2 for confirmation. This indicates that Relay MLD 1 has successfully received Data m (or Data n, which are identical) from AP MLD 1.

[0249] Then, Relay MLD 1 sends relayed Data m1 to non-AP MLD 1 on Link 1. Relay MLD 1 then sends relayed Data n1 to non-AP MLD 1 on Link 2. Data m1 is part or all of Data m, and Data n1 is part or all of Data n. Furthermore, to enhance relay transmission reliability, the contents of Data m1 and Data n1 can be identical. Upon receiving the relayed Data (m1 or n1) sent by Relay MLD 1 on either Link 1 or Link 2, non-AP MLD 1 responds with an Ack / BlockAck frame after a SIFS interval to confirm the reception. This can be divided into the following three operations:

[0250] Option 1: Non-AP MLD 1 receives Data m1 (relay data m1) sent by Relay MLD 1 on Link 1. After a SIFS period, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 1 for confirmation. At this point, non-AP MLD 1 does not need to respond with an Ack / BlockAck frame on Link 2 for confirmation. This indicates that non-AP MLD 1 has successfully received Data m1 (relay data m1) sent by Relay MLD 1.

[0251] Option 2: Non-AP MLD 1 receives Data n1 (relay data n1) sent by Relay MLD 1 on Link 2. After a SIFS period, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 2 for confirmation. At this point, non-AP MLD 1 does not need to respond with an Ack / BlockAck frame on Link 1 for confirmation. This indicates that non-AP MLD 1 has successfully received Data n1 (relay data n1) sent by Relay MLD 1.

[0252] Option 3: Non-AP MLD 1 receives the relayed Data m1 sent by Relay MLD 1 on Link 1 and the relayed Data n1 sent by Relay MLD 1 on Link 2. After a SIFS period, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 1 for confirmation. At this time, non-AP MLD 1 also responds with an Ack / BlockAck frame on Link 2 for confirmation. This indicates that non-AP MLD 1 has successfully received the relayed Data m1 (or Data n1; the contents of Data m1 and Data n1 are identical) sent by Relay MLD 1.

[0253] Finally, Relay MLD 1 sends a relay Ack / BlockAck frame to AP MLD 1 on Link 1 and / or Link 2, indicating that Relay MLD 1 has successfully forwarded Data m1 (or Data n1) to non-AP MLD 1.

[0254] In some embodiments of the present application, FIG9B illustrates the case where frames sent on Link 1 and Link 2 are fully aligned, and the multi-link devices for transmission and reception have STR or NSTR capabilities. If the multi-link devices for transmission and reception have STR capabilities, frames sent on Link 1 and Link 2 may not be aligned.

[0255] This embodiment can achieve the following effects: a relay uses multiple links to provide relay services to a non-AP MLD. Different data can be sent on different links, thereby improving throughput. Alternatively, if the same data is sent on different links, the receiver can successfully receive the data on any link. The remaining links can continue to receive data or stop receiving data, thereby enhancing the stability of relay transmission.

[0256] Example: Multiple Relay MLDs use different links to transmit data to non-AP MLDs

[0257] As shown in Figure 9C, AP MLD 1 sends Data m to Relay MLD 1 on Link 1, and AP MLD 1 sends Data n to Relay MLD 2 on Link 2. To enhance relay transmission reliability, the contents of Data m and Data n can be identical. Relay MLD 1 on Link 1 and / or Relay MLD 2 on Link 2 receive the Data (m or n) sent by AP MLD 1 and reply with an Ack / BlockAck frame after a SIFS interval to confirm the response. This can be divided into the following three operations:

[0258] Option 1: Relay MLD 1 receives Data m from AP MLD 1 on Link 1. After a SIFS, Relay MLD 1 responds with an Ack / BlockAck frame on Link 1 for confirmation. At this point, Relay MLD 2 does not need to respond with an Ack / BlockAck frame on Link 2 for confirmation. This indicates that Relay MLD 1 has successfully received Data m from AP MLD 1.

[0259] Option 2: After Relay MLD 2 receives Data n from AP MLD 1 on Link 2, it sends an Ack / BlockAck frame on Link 2 to confirm the data transmission after a SIFS period. At this point, Relay MLD 1 does not need to send an Ack / BlockAck frame on Link 1 to confirm the data transmission. This indicates that Relay MLD 2 has successfully received Data n from AP MLD 1.

[0260] Option 3: Relay MLD 1 receives Data m from AP MLD 1 on Link 1, and Relay MLD 2 receives Data n from AP MLD 1 on Link 2. After a SIFS period, Relay MLD 1 responds with an Ack / BlockAck frame on Link 1 for confirmation. At this time, Relay MLD 2 also responds with an Ack / BlockAck frame on Link 2 for confirmation. This indicates that Relay MLD 1 has successfully received Data m from AP MLD 1, and Relay MLD 2 has successfully received Data n from AP MLD 1 (Data m and Data n contain identical contents).

[0261] Then, Relay MLD 1 sends relayed Data m1 to non-AP MLD 1 on Link 1, and Relay MLD 2 sends relayed Data n1 to non-AP MLD 1 on Link 2. Data m1 is part of or all of Data m, and Data n1 is part of or all of Data n. Furthermore, to enhance relay transmission reliability, the contents of Data m1 and Data n1 can be identical. Upon receiving the relayed Data (m1 or n1) sent by Relay MLD 1 and Relay MLD 2 on either Link 1 or Link 2, non-AP MLD 1 responds with an Ack / BlockAck frame after a SIFS interval for confirmation. This can be divided into the following three operations:

[0262] Option 1: Non-AP MLD 1 receives Data m1 (relay data m1) sent by Relay MLD 1 on Link 1. After a SIFS period, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 1 for confirmation. At this point, non-AP MLD 1 does not need to respond with an Ack / BlockAck frame on Link 2 for confirmation. This indicates that non-AP MLD 1 has successfully received Data m1 (relay data m1) sent by Relay MLD 1.

[0263] Option 2: Non-AP MLD 1 receives Data n1 (relay data n1) sent by Relay MLD 2 on Link 2. After a SIFS period, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 2 for confirmation. At this point, non-AP MLD 1 does not need to respond with an Ack / BlockAck frame on Link 1 for confirmation. This indicates that non-AP MLD 1 has successfully received Data n1 (relay data n1) sent by Relay MLD 2.

[0264] Option 3: Non-AP MLD 1 receives the relayed Data m1 sent by Relay MLD 1 on Link 1 and the relayed Data n1 sent by Relay MLD 2 on Link 2. After a SIFS period, non-AP MLD 1 responds with an Ack / BlockAck frame on Link 1 for confirmation. At this time, non-AP MLD 1 also responds with an Ack / BlockAck frame on Link 2 for confirmation. This indicates that non-AP MLD 1 has successfully received the relayed Data m1 (or Data n1; the contents of Data m1 and Data n1 are identical) sent by Relay MLD 1 and / or Relay MLD 2.

[0265] Finally, Relay MLD 1 sends a relay Ack / BlockAck frame to AP MLD 1 on Link 1, indicating that Relay MLD 1 has successfully forwarded Data m1 to non-AP MLD 1. Alternatively, Relay MLD 2 sends a relay Ack / BlockAck frame to AP MLD 1 on Link 2, indicating that Relay MLD 2 has successfully forwarded Data n1 to non-AP MLD 1.

[0266] In some embodiments of the present application, FIG9C illustrates the case where frames sent on Link 1 and Link 2 are fully aligned, and the multi-link devices for transmission and reception have STR or NSTR capabilities. If the multi-link devices for transmission and reception have STR capabilities, frames sent on Link 1 and Link 2 may not be aligned.

[0267] This embodiment can achieve the following effects: multiple relays use different links to provide relay services to a non-AP MLD. Different data can be sent on different links, thereby improving throughput. Alternatively, if the same data is sent on different links, the receiver can successfully receive the data on any link. The remaining links can continue to receive data or stop receiving data, thereby enhancing the stability of relay transmission.

[0268] In summary, in some embodiments of the present application, in order to achieve high reliability and low latency relay operation of Wi-Fi 8, some embodiments of the present application are designed with the following invention points: Relay capability parameter design, Relay link failure handling mechanism: method for discovering relay link failure, method for notifying relay link failure, Relay switching mechanism: scenario 1: AP<->Relay link interruption, AP initiates Relay (or Link) switching method, scenario 2: AP<->Relay link interruption, STA initiates Relay switching method, scenario 3: AP<->Relay link interruption, Relay initiates Link switching method, scenario 4: Relay<->STA link interruption, STA initiates Relay (or Link) switching method, scenario 5: Relay<->STA link interruption, AP initiates Relay switching method, scenario 6: Relay<->STA link interruption, Relay initiates Link switching method, confirmation mechanism for multi-Relay transmission: confirmation method when multiple links of a relay are used to provide relay transmission services to the same STA, confirmation method when different links of multiple relays are used to provide relay transmission services to the same STA. Some embodiments of the present application design a variety of mechanisms that can improve the reliability of relay transmission and reduce the delay of relay transmission. By designing a relay link fault detection and notification mechanism, faster relay fault identification can be achieved, and a mechanism for fast relay switching is designed based on the identified fault. This is of great help in reducing the delay of relay transmission and reducing the delay caused by the inability to transmit data between the AP and the STA due to relay failure. In addition, the present application designs a confirmation mechanism when multiple relays provide services to the same device. Even if an individual relay cannot complete the relay transmission, the other relays can still serve the target device normally, which improves the reliability of relay transmission to a certain extent. In the process of IEEE802.11bn standardization, it is inevitable to study and discuss the fault handling and reliability improvement of relays. Therefore, the content designed in some embodiments of the present application is likely to become an indispensable technical point of the 802.11bn standard.

[0269] Figure 10 is a schematic structural diagram of a wireless communication device 500 provided in an embodiment of the present application. The wireless communication device can be a relay communication device, an AP, or a STA. The wireless communication device 500 shown in Figure 10 includes a processor 510, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application. In some embodiments of the present application, the AP includes an AP STA or an AP MLD, and the STA includes an AP STA or a non-AP STA or an AP MLD or a non-AP MLD.

[0270] Optionally, as shown in FIG10 , the wireless communication device 500 may further include a memory 520. The processor 510 may call and execute a computer program from the memory 520 to implement the method in the embodiment of the present application. The memory 520 may be a separate device independent of the processor 510 or may be integrated into the processor 510.

[0271] Optionally, as shown in FIG10 , the wireless communication device 500 may further include a transceiver 530. The processor 510 may control the transceiver 530 to communicate with other devices. Specifically, the transceiver 530 may send information or data to other devices or receive information or data sent by other devices. The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include one or more antennas.

[0272] Optionally, the wireless communication device 500 may specifically be a relay communication device in an embodiment of the present application, and the wireless communication device 500 may implement the corresponding processes implemented by the relay communication device in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0273] Optionally, the wireless communication device 500 may specifically be a mobile AP in an embodiment of the present application, and the wireless communication device 500 may implement the corresponding processes implemented by the AP in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0274] Optionally, the wireless communication device 700 may be a STA in an embodiment of the present application, and the wireless communication device 700 may implement the corresponding processes implemented by the STA in each method of the embodiment of the present application. For the sake of brevity, they are not described here. In some embodiments of the present application, the STA includes an AP STA or a non-AP STA or an AP MLD or a non-AP MLD.

[0275] Figure 11 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 600 shown in Figure 11 includes a processor 610, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0276] Optionally, as shown in FIG11 , the chip 600 may further include a memory 620. The processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application. The memory 620 may be a separate device independent of the processor 610 or may be integrated into the processor 610.

[0277] Optionally, the chip 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0278] Optionally, the chip 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0279] Optionally, the chip can be applied to the relay communication device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the relay communication device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0280] Optionally, the chip can be applied to the AP in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the AP in each method in the embodiments of the present application. For the sake of brevity, they are not described here.

[0281] Optionally, the chip can be applied to the STA in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the STA in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0282] Figure 12 is a schematic block diagram of a wireless communication system 700 provided in an embodiment of the present application. As shown in Figure 12, the communication system 700 includes an AP 710, a relay communication device 720, and an STA 730. The AP 710 can be used to implement the corresponding functions implemented by the AP in the above method, the relay communication device 720 can be used to implement the corresponding functions implemented by the relay communication device in the above method, and the STA 730 can be used to implement the corresponding functions implemented by the STA in the above method. For the sake of brevity, these functions are not further described here.

[0283] It should be understood that the processor of the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment may be completed by hardware integrated logic circuits in the processor or software instructions.

[0284] It is understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory. The embodiments of the present application also provide a computer-readable storage medium for storing a computer program.

[0285] Optionally, the computer-readable storage medium may be applied to the relay communication device in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the relay communication device in the various methods of the embodiments of the present application. For the sake of brevity, these processes are not described in detail here. Optionally, the computer-readable storage medium may be applied to the AP in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of the present application. For the sake of brevity, these processes are not described in detail here. Optionally, the computer-readable storage medium may be applied to the STA in the embodiments of the present application, and the computer program causes the computer to execute the corresponding processes implemented by the STA in the various methods of the embodiments of the present application. For the sake of brevity, these processes are not described in detail here.

[0286] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0287] Optionally, the computer program product may be applied to the relay communication device in the embodiments of the present application, and the computer program instructions cause a computer to execute the corresponding processes implemented by the relay communication device in the various methods of the embodiments of the present application. For the sake of brevity, these instructions are not described in detail here. Optionally, the computer program product may be applied to the AP in the embodiments of the present application, and the computer program instructions cause a computer to execute the corresponding processes implemented by the AP in the various methods of the embodiments of the present application. For the sake of brevity, these instructions are not described in detail here. Optionally, the computer program product may be applied to the STA in the embodiments of the present application, and the computer program instructions cause a computer to execute the corresponding processes implemented by the STA in the various methods of the embodiments of the present application. For the sake of brevity, these instructions are not described in detail here.

[0288] The embodiment of the present application also provides a computer program.

[0289] Optionally, the computer program may be applied to the relay communication device in the embodiment of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the relay communication device in the various methods of the embodiment of the present application. For the sake of brevity, no further details are given here. Optionally, the computer program may be applied to the AP in the embodiment of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the AP in the various methods of the embodiment of the present application. For the sake of brevity, no further details are given here. Optionally, the computer program may be applied to the STA in the embodiment of the present application. When the computer program is run on a computer, the computer executes the corresponding processes implemented by the STA in the various methods of the embodiment of the present application. For the sake of brevity, no further details are given here.

[0290] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0291] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A relay communication method, executed in a relay communication device, wherein: The relay communication method includes: Sending capability parameters of the relay communication device to an access point AP and / or a non-AP station STA, wherein the capability parameters include one or more of the following: Cache information used to indicate that the relay communication device can be used for relaying; Information on whether the power status of the relay communication device is sufficient for relay services; Multi-link relay operation configuration information, used to indicate whether the relay communication device supports multi-link relay operation and / or indicate links that can support relay reception or transmission; Cache information for indicating that the relay communication device functions as an AP or a non-AP STA; Information indicating the maximum number of service devices supported by the relay communication device; and Information indicating the number of service devices that the relay communication device can currently support.

2. The method according to claim 1, wherein Sending the capability parameter to the AP and / or the non-AP STA includes: sending a first frame to the AP and / or the non-AP STA, wherein the first frame carries an ultra-high reliability (UHR) relay capability unit, and the UHR relay capability unit includes one or more of the following fields: a relay operation buffer status field, a power status field, a multi-link device (MLD) relay description field, a relay STA buffer status field, a maximum supported STA field, and an available supported STA field, wherein the relay operation buffer status field is used to indicate cache information available for relaying by the relay communication device, the power status field is used to indicate whether the power status of the relay communication device is available for relay service, the MLD relay description field is used to indicate the multi-link relay operation configuration information, the relay STA buffer status field is used to indicate cache information of the relay communication device as an AP or a non-AP STA, the maximum supported STA field is used to indicate the maximum number of service devices supported by the relay communication device, and the available supported STA field is used to indicate the number of service devices that the relay communication device can currently support.

3. The relay communication method according to claim 2, wherein: The first frame is a probe request frame, a probe response frame, a multilink ML probe request frame, an ML probe response frame, an association request frame, or an association response frame.

4. The relay communication method according to any one of claims 1 to 3, wherein: The relay communication method further includes sending relay status notification information to the AP and / or the non-AP STA, wherein the relay status notification information is used to indicate a current status of the relay communication device.

5. The method according to claim 4, wherein Sending the relay status information to the AP and / or the non-AP STA includes: sending a relay status notification frame to the AP and / or the non-AP STA, wherein the relay status notification frame is used to indicate a relay link failure or status information of the relay communication device.

6. The method according to claim 4 or 5, wherein: Sending the relay state information to the AP and / or the non-AP STA includes: sending the relay state information to the AP and / or the non-AP STA periodically or quasi-periodically.

7. The method according to any one of claims 4 to 6, wherein The sending the relay state information to the AP and / or the non-AP STA includes: When a link failure occurs in relay transmission between the relay communication device and one of the AP and the non-AP STA, the relay status information is sent to other devices participating in the relay transmission.

8. The relay communication method according to claim 4, wherein: The relay status notification information includes one or more of the following fields: A relay identifier ID field is used to indicate status information of the relay communication device corresponding to the relay ID field; The relay operation buffer status field is used to indicate the cache information that the relay communication device can use for relaying; The Available Supported STA field is used to indicate the number of service devices that the relay communication device can currently support; The power status field is used to indicate whether the power status of the relay communication device can be used for relay service; and The available time length field is used to indicate the continuous working time of the relay communication device corresponding to the relay ID field as a relay.

9. The relay communication method according to claim 8, wherein: The relay status notification information also The following fields are included: Available Link ID 1 to m fields, which are used to indicate the status of the links available for relay transmission of the relay communication device corresponding to the relay ID field, where m is a positive integer; and The opposite STA ID field of the available link IDs 1 to m is used to indicate that the available link IDs 1 to m correspond to links between MLDs.

10. The relay communication method according to claim 8 or 9, wherein: The relay status notification information also The following fields are included: unavailable link ID 1 to n fields, used to indicate the status of the unavailable relay transmission link of the relay communication device corresponding to the relay ID field, where n is a positive integer; and The opposite STA ID field of the unavailable link ID 1-n is used to indicate the link between the MLDs corresponding to the unavailable link ID 1-n fields.

11. The relay communication method according to any one of claims 8 to 10, wherein: The relay status notification information also includes the following fields: A switch MLD ID field is used to indicate the MLD used by the relay communication device to perform link switching / recovery; and The switching link ID field is used to indicate the link used by the relay communication device to perform link switching / recovery.

12. The relay communication method according to any one of claims 5 to 11, wherein: The format of the relay status notification information is an action frame format including a status code. The action field format of the relay status notification information includes one or more sequences and information corresponding to the one or more sequences. The information includes one or more of the following information: Category, used to indicate the category of the current frame; Public action, used to indicate that the current frame is the relay status notification frame; Status code, used to indicate the status code carried by the current frame; Relay ID, used to indicate the status information of the relay communication device corresponding to the relay ID; The available time length is used to indicate the continuous working time of the relay communication device corresponding to the relay ID as a relay; An available link ID, used to indicate the status of a link available for relay transmission of the relay communication device corresponding to the relay ID; The peer STA ID of the available link ID is used to indicate that the available link ID corresponds to a link between MLDs; An unavailable link ID, used to indicate the status of an unavailable relay transmission link of the relay communication device corresponding to the relay ID; The peer STA ID of the unavailable link ID is used to indicate the link between the MLDs corresponding to the unavailable link ID; Switching MLD ID, used to indicate the MLD used by the relay communication device to perform link switching / recovery; and The switching link ID is used to indicate the link used by the relay communication device to perform link switching / recovery.

13. The relay communication method according to claim 12, wherein: The status code includes one or more of the following codes: A code to indicate success; A code used to indicate an unspecified failure; A code for indicating that the relay communication device's buffer for relaying is full and that the relay service cannot be continued; A code for indicating that the number of devices currently served by the relay communication device has reached an upper limit and that the relay service cannot be provided to new devices; A code for indicating that the number of links currently used for the relay function of the relay communication device has reached an upper limit and there are no more links providing relay services; A code for indicating that the relay communication device has insufficient power and cannot continue to provide relay services; and A code indicating a reservation.

14. The relay communication method according to any one of claims 7 to 13, wherein: The relay communication method further includes performing relay switching or relay link switching when a link between the relay communication device and the AP or the non-AP STA is disconnected.

15. The relay communication method according to claim 14, wherein: The relay communication method further includes, when it is determined that the first link between the relay communication device and one of the AP and the non-AP STA is disconnected, sending a relay status notification to notify other devices participating in relay transmission that the first link is unavailable.

16. The relay communication method according to claim 15, wherein: The relay communication method further includes: sending a request to one of the AP and the non-AP STA over a second link between the relay communication device and one of the AP and the non-AP STA, and receiving a response sent by one of the AP and the non-AP STA over the second link; in response to the response sent by one of the AP and the non-AP STA on the second link; sending data to one of the AP and the non-AP STA on the second link, and receiving an acknowledgment sent by one of the AP and the non-AP STA on the second link; and An acknowledgement is sent to the other of the AP and the non-AP STA over the second link.

17. A relay communication method, wherein: The relay communication method includes: Confirmation during multi-relay transmission, wherein the confirmation during multi-relay transmission includes confirmation when multiple links of a relay are used to provide relay transmission services to the same non-AP station STA or access point AP, or confirmation when different links of multiple relays are used to provide relay transmission services to the same non-AP STA or AP.

18. The relay communication method according to claim 17, wherein: The confirmation of using multiple links of a relay to provide relay transmission services to the same non-AP STA or AP includes: A relay communication device uses the multiple different links to send different data to the same non-AP MLD or AP to provide a relay service. After the same non-AP MLD or AP successfully receives the data and provides an acknowledgement on any one of the multiple different links, the remaining links of the multiple different links no longer need to perform the same data reception and / or acknowledgement operations.

19. The relay communication method according to claim 17, wherein: The confirmation of using multiple links of a relay to provide relay transmission services to the same non-AP STA or access point AP includes: A relay communication device uses the multiple different links to send the same data to the same non-AP MLD or AP to provide a relay service. After the same non-AP MLD or AP successfully receives the data and provides an acknowledgement on any one of the multiple different links, the remaining links of the multiple different links no longer need to perform the same data reception and / or acknowledgement operations.

20. The relay communication method according to claim 17, wherein: The confirmation of using different links of multiple relays to provide relay transmission services to the same non-AP STA or AP includes: Multiple relays use the different links to send different data to the same non-AP MLD or AP to provide relay services. After the same non-AP MLD or access point AP successfully receives the data and provides confirmation on any one of the different links of the multiple relays, the remaining links of the different links of the multiple relays no longer need to perform the same data reception and / or confirmation operations.

21. The relay communication method according to claim 17, wherein: The confirmation of using different links of multiple relays to provide relay transmission services to the same non-AP STA or AP includes: Multiple relays use the different links to send the same data to the same non-AP MLD or AP to provide relay services. After the same non-AP MLD or AP successfully receives the data and provides an acknowledgement on any one of the different links of the multiple relays, the remaining links of the different links of the multiple relays no longer need to perform the same data reception and / or acknowledgement operations.

22. A relay communication method, executed at a first node, wherein: The relay communication method includes: Receive capability parameters of the relay communication device sent by the relay communication device, where the capability parameters include one or more of the following: Cache information used to indicate that the relay communication device can be used for relaying; Information on whether the power status of the relay communication device is available for relay services; Multi-link relay operation configuration information, used to indicate whether the relay communication device supports multi-link relay operation and / or indicate links that can support relay reception or transmission; Cache information for indicating whether the relay communication device functions as an AP or a non-AP STA; Information indicating the maximum number of service devices supported by the relay communication device; and Information indicating the number of service devices that the relay communication device can currently support.

23. The method according to claim 22, wherein Receiving the capability parameter sent by the relay communication device includes: receiving a first frame sent by the relay communication device, wherein the first frame carries an ultra-high reliability (UHR) relay capability unit, and the UHR relay capability unit includes one or more of the following fields: a relay operation buffer status field, a power status field, a multi-link device (MLD) relay description field, a relay STA buffer status field, a maximum supported STA field, and an available supported STA field, wherein the relay operation buffer status field is used to indicate cache information that the relay communication device can use for relaying, the power status field is used to indicate whether the power status of the relay communication device can be used for relay service, the MLD relay description field is used to indicate the multi-link relay operation configuration information, the relay STA buffer status field is used to indicate cache information of the relay communication device as an AP or a non-AP STA, the maximum supported STA field is used to indicate the maximum number of service devices supported by the relay communication device, and the available supported STA field is used to indicate the number of service devices that the relay communication device can currently support.

24. The relay communication method according to claim 23, wherein: The first frame is a probe request frame, a probe response frame, a multilink ML probe request frame, an ML probe response frame, an association request frame, or an association response frame.

25. The relay communication method according to any one of claims 22 to 24, wherein: The relay communication method further includes receiving relay status information, wherein the relay status information is used to indicate a current status of the relay communication device.

26. The method according to claim 25, wherein Receiving the relay status information includes: receiving a relay status notification frame, wherein the relay status notification frame is used to indicate a relay link failure or status information of the relay communication device.

27. The method according to claim 25 or 26, wherein Receiving the relay state information includes: periodically or quasi-periodically receiving the relay state information sent by the relay communication device.

28. The method according to any one of claims 25 to 27, wherein Receiving the relay state information includes: When a link failure occurs in the relay transmission between the relay communication device and the second node, the first node receives the relay state information sent by the relay communication device; and In response to the relay state information, the first node performs switching of the relay or switching of the relay link.

29. The method according to any one of claims 25 to 27, wherein Receiving the relay state information includes: When a link failure occurs in the relay transmission between the relay communication device and the second node, the first node receives the relay state information sent by the second node; and In response to the relay state information, the first node cooperates with the second node to perform relay switching or relay link switching.

30. The relay communication method according to any one of claims 26 to 29, wherein: The relay status notification frame includes one or more of the following fields: A relay identifier ID field is used to indicate status information of the relay communication device corresponding to the relay ID field; The relay operation buffer status field is used to indicate the cache information that the relay communication device can use for relaying; The Available Supported STA field is used to indicate the number of service devices that the relay communication device can currently support; The power status field is used to indicate whether the power status of the relay communication device can be used for relay service; and The available time length field is used to indicate the continuous working time of the relay communication device corresponding to the relay ID field as a relay.

31. The relay communication method according to claim 30, wherein: The relay status notification information also includes the following fields: Available Link ID 1-m field, used to indicate the status of the link available for relay transmission of the relay communication device corresponding to the relay ID field, where m is a positive integer; and The opposite STA ID field of the available link IDs 1 to m is used to indicate that the available link IDs 1 to m correspond to links between MLDs.

32. The relay communication method according to claim 30 or 31, wherein: The relay status notification information further includes the following fields: an unavailable link ID 1-n field, used to indicate the status of the unavailable relay transmission link of the relay communication device corresponding to the relay ID field, where n is a positive integer; and The opposite STA ID field of the unavailable link ID 1-n is used to indicate the link between the MLDs corresponding to the unavailable link ID 1-n fields.

33. The relay communication method according to any one of claims 30 to 32, wherein: The relay status notification information also includes the following fields: A switch MLD ID field is used to indicate the MLD used by the relay communication device to perform link switching / recovery; and The switching link ID field is used to indicate the link used by the relay communication device to perform link switching / recovery.

34. The relay communication method according to any one of claims 26 to 33, wherein: The format of the relay status notification information is an action frame format including a status code. The action field format of the relay status notification information includes one or more sequences and information corresponding to the one or more sequences, and the information includes one or more of the following information: Category, used to indicate the category of the current frame; Public action, used to indicate that the current frame is the relay status notification frame; Status code, used to indicate the status code carried by the current frame; Relay ID, used to indicate the status information of the relay communication device corresponding to the relay ID; The available time length is used to indicate the continuous working time of the relay communication device corresponding to the relay ID as a relay; An available link ID, used to indicate the status of a link available for relay transmission of the relay communication device corresponding to the relay ID; The peer STA ID of the available link ID is used to indicate that the available link ID corresponds to a link between MLDs; An unavailable link ID, used to indicate the status of an unavailable relay transmission link of the relay communication device corresponding to the relay ID; The peer STA ID of the unavailable link ID is used to indicate the link between the MLDs corresponding to the unavailable link ID; Switching MLD ID, used to indicate the MLD used by the relay communication device to perform link switching / recovery; and The switching link ID is used to indicate the link used by the relay communication device to perform link switching / recovery.

35. The relay communication method according to claim 34, wherein: The status code includes one or more of the following codes: A code to indicate success; A code used to indicate an unspecified failure; A code for indicating that the relay communication device's buffer for relaying is full and that the relay service cannot be continued; A code for indicating that the number of devices currently served by the relay communication device has reached an upper limit and that the relay service cannot be provided to new devices; A code for indicating that the number of links currently used for the relay function of the relay communication device has reached an upper limit and there are no more links providing relay services; A code for indicating that the relay communication device has insufficient power and cannot continue to provide relay services; and A code indicating a reservation.

36. The relay communication method according to claim 25, wherein: The relay state information is sent by the relay communication device, and the relay state information indicates that a link failure occurs in transmission on a first link between the relay communication device and the second node; The method further comprises: In response to the relay state information, executing: Relay transmission to the second node through another relay communication device; or The transmission is performed through a direct link between the second node and the second node.

37. The relay communication method according to claim 22, wherein: The relay communication method further includes: determining whether a failure occurs in transmission with the relay communication device on the first link; When a fault is detected, execute: Relay transmission to the second node through another relay communication device; or Transmitted via a direct link to the second node; or Relay transmission is performed via a second link with the relay communication device.

38. The relay communication method according to claim 37, wherein: The relay communication method further includes: Send relay status information, including: sending the relay state information to the second node; or broadcasting the relay status information; or The relay status information is multicasted.

39. A wireless communication device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method according to any one of claims 1 to 38.

Images