A multi-link based communication method and apparatus

Abstract

The application provides a multi-link-based communication method and device, which is used to solve the unreasonable switching operation in MLO. The application is applied to a wireless local area network system supporting IEEE 802.11ax next-generation Wi-Fi protocol, such as 802.11be, Wi-Fi 7 or EHT, for example, 802.11be next-generation, Wi-Fi 8, Wi-Fi AI and other 802.11 series protocols, and can also be applied to a wireless personal area network system based on UWB, a perception system. The method adds related conditions of other multicast frames except trigger frames, multi-user block acknowledgement frames and dataless PPDU declaration frames in the condition set, so that the non-AP STA can determine whether to switch to the listening operation mode according to the information of the other multicast frames when performing the switching operation.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method and apparatus based on multiple links. Background Technology

[0002] To achieve extremely high throughput, multi-link operation (MLO) technology has been introduced. In MLO, a non-access point multi-link device (non-AP MLD) only has single-chain radio transmission and reception capabilities, but it can simultaneously enter listening operation on multiple links. During listening operation, the non-AP MLD uses one radio chain to receive signals on each link. Once the access point multi-link device (AP MLD) successfully sends an initial control frame to the non-AP MLD on any link i, the non-AP MLD switches all radio chains to link i to interact with the AP MLD, and after the frame interaction is complete, switches back to the individual links to continue listening operation.

[0003] If a non-AP MLD receives a multicast frame during frame interaction with the AP, it will switch back to each link to perform listening operations. This will cause any subsequent frames sent to the on-AP MLD from that multicast frame to be unreceived. Summary of the Invention

[0004] This application provides a multi-link-based communication method and apparatus to solve the problem of unreasonable handover operations in MLO.

[0005] Firstly, this application provides a multi-link-based communication method. The executing entity of this method can be a receiving-side device, such as a non-AP MLD, specifically a non-AP STA within the non-AP MLD, or a chip, circuit, or other component used to implement the functions of the receiving-side device. Taking a non-AP STA as an example, the method includes: receiving a first physical layer protocol data unit (PPDU) within a first duration, the first PPDU including a first frame; if the first frame does not satisfy all conditions in a condition set, switching to a listening operation mode; wherein, at least one condition in the condition set is frame information of a multicast frame, and the multicast frame is different from a trigger frame, a multi-user block acknowledgment frame, and a no-data PPDU claim frame.

[0006] In this embodiment, by adding conditions related to multicast frames other than trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames to the condition set, a non-AP STA can determine whether to switch to listen mode based on information from other multicast frames during handover. Compared to the prior art, which directly switches to listen mode upon receiving a multicast frame, this embodiment can determine whether to switch to listen mode based on the information of the multicast frame. For example, it can switch to listen mode if the received multicast frame does not meet all the conditions in the condition set, and conversely, it will not switch to listen mode if the received multicast frame meets any of the conditions in the condition set. This improves flexibility and ensures that multicast frames and subsequent frames are received in a timely manner, thus enhancing the rationality of the handover operation.

[0007] In one possible design, the at least one condition includes: the frame type is a multicast frame, which is different from a broadcast frame; in other words, the multicast frame is not a broadcast frame, and the receiving device indicated by the multicast frame includes the site.

[0008] If the above conditions are not met, the non-AP STA switches to listen mode. Conversely, if the conditions are met, the non-AP STA will not switch to listen mode. That is, the non-AP STA can determine not to switch to listen mode upon receiving a multicast frame intended for it, thus ensuring that the multicast frame and subsequent frames are received in a timely manner. Furthermore, these conditions allow the non-AP STA to switch to listen mode promptly when receiving a multicast frame not intended for it, thereby reducing latency when communicating with the access point using other links.

[0009] In one possible design, the at least one condition includes: the frame type is a broadcast frame, and the broadcast frame carries a sending address that is the address of the access point associated with the site; or, the frame type is a broadcast frame, and the receiving device indicated by the broadcast frame includes the site.

[0010] If the above conditions are not met, the non-AP STA will switch to listening mode. Conversely, if the above conditions are met, the non-AP STA will not switch to listening mode. That is, the non-AP STA can determine not to switch to listening mode when it receives a broadcast frame sent to itself or a broadcast frame sent by its associated access point, thus ensuring that multicast frames and subsequent frames can be received in a timely manner.

[0011] Furthermore, the above conditions can cover trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames. Therefore, the conditions for trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames do not need to be listed separately in the condition set. Thus, the above conditions can simplify the protocol description and reduce the implementation complexity.

[0012] In one possible design, the broadcast frame is different from the trigger frame, multi-user block acknowledgment frame, and no-data PPDU claim frame. This approach avoids logical conflicts or duplication with current handover rules.

[0013] In one possible design, the set of conditions also includes at least one of the following five conditions:

[0014] The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the site;

[0015] The frame type is a trigger frame, and the trigger frame includes a first field for indicating user information, the first field indicating the site;

[0016] The frame type is a clear send frame, and the receiving address carried by the clear send frame is the address of the access point site associated with the site.

[0017] The frame type is a multi-user block acknowledgment frame, and the multi-user block acknowledgment frame includes a second field for indicating site information, the second field indicating the site;

[0018] The frame type is a no-data PPDU claim frame, and the no-data PPDU claim frame includes a third field for indicating site information, the third field indicating the site.

[0019] Secondly, this application provides a multi-link-based communication method. The execution entity of this method can be a receiving-side device, such as a non-AP MLD, specifically a non-AP STA within the non-AP MLD, or a chip, circuit, or other component used to implement the functions of the receiving-side device. Taking a non-AP STA as an example, the method includes: receiving a first PPDU within a first duration, the first PPDU including a first frame; if the first frame satisfies any condition in a set of conditions, switching to a listening operation mode; wherein, the set of conditions includes a frame type range corresponding to at least one condition that includes multicast frames, and the multicast frames are different from trigger frames, multi-user block acknowledgment frames, and dataless physical layer protocol data unit (PPDU) claim frames.

[0020] In this embodiment, by adding conditions to the condition set that can cover multicast frames other than trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames, a non-AP STA can determine whether to switch to listen operation mode based on information from other multicast frames during handover. Compared to the prior art that directly switches to listen operation mode after receiving a multicast frame, this embodiment can determine whether to switch to listen operation mode based on the information of the multicast frame after receiving it. For example, the above method switches to listen operation mode when any condition in the condition set is met, and does not switch to listen operation mode when none of the conditions in the condition set are met. This improves flexibility and ensures that multicast frames and subsequent frames are received in a timely manner, thus improving the rationality of the handover operation.

[0021] In one possible design, the at least one condition includes at least one of the following three conditions:

[0022] The frame was sent from an address that is not the address of the access point site associated with the site.

[0023] The frame type is a broadcast frame, and the target receiving device indicated by the broadcast frame does not include the station;

[0024] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the site.

[0025] With the above design, if one of the above conditions is met, the non-AP STA switches to the listening operation mode. In other words, if the above conditions are not met, it means that the first frame is a multicast frame sent to itself. The non-AP STA can determine not to switch to the listening operation mode when it receives a multicast frame sent to itself, thereby ensuring that the multicast frame and subsequent frames can be received in a timely manner.

[0026] In one possible design, the at least one condition includes at least one of the following two conditions:

[0027] The frame was sent from an address that is not the address of the access point site associated with the site.

[0028] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the site.

[0029] This approach simplifies the protocol description and reduces implementation complexity. Furthermore, it allows non-AP STAs to determine whether to switch to listen mode upon receiving a multicast frame, thus ensuring that the multicast frame and subsequent frames are received promptly.

[0030] In one possible design, the set of conditions also includes at least one of the following five conditions:

[0031] The frame type is a unicast frame, and the receiving address carried by the unicast frame is not the address of the site;

[0032] The frame type is a trigger frame, and the first field included in the trigger frame does not indicate the site; the first field is used to indicate user information.

[0033] The frame type is a clear send frame, and the receiving address carried by the clear send frame is not the address of the access point site associated with the site.

[0034] The frame type is a multi-user block acknowledgment frame, and the second field included in the multi-user block acknowledgment frame does not indicate the site; the second field is used to indicate site information.

[0035] The frame type is a no-data PPDU claim frame, and the third field included in the no-data PPDU claim frame does not indicate the site, the third field being used to indicate site information.

[0036] This method allows non-AP STAs to determine whether to switch to listening mode when they receive multicast frames sent to them, thus ensuring that multicast frames and subsequent frames can be received in a timely manner.

[0037] Thirdly, this application provides a multi-link-based communication method. The executing entity of this method can be a receiving-side device, such as a non-AP MLD, specifically a non-AP STA within the non-AP MLD, or a chip, circuit, or other component used to implement the functions of the receiving-side device. Taking a non-AP STA as an example, the method includes: receiving a PPDU; if the basic service set indicated by the PPDU is an external basic service set, switching to a listening operation.

[0038] Currently, most rules for switching to listen mode are based on MAC layer information, carried in the data portion. However, inter-BSS PPDUs can be identified through the physical layer SIG field. The SIG field is located before the data portion in the PPDU. Therefore, in the above method, by switching to listen mode when an inter-BSS PPDU is detected, it is not necessary to continue parsing the MAC content located in the data portion of the PPDU. This allows for timely switching and helps reduce latency when communicating with the AP using other links.

[0039] Fourthly, this application provides a multi-link-based communication method. The executing entity of this method can be a receiving-side device, such as a non-AP MLD, specifically a station (non-AP STA) within the non-AP MLD, or a chip, circuit, or other component used to implement the functions of the receiving-side device. Taking a non-AP STA as an example, the method includes: determining that any condition in a set of conditions is met; switching to a listening operation mode; wherein the set of conditions includes the following conditions: receiving a multicast frame, the multicast frame being different from a broadcast frame, and the receiving device indicated by the multicast frame not including the station.

[0040] This application embodiment adds a condition that can cover multicast frames other than trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames. This allows non-AP STAs to determine whether to switch to listen mode based on information from other multicast frames during handover operations. Compared to the prior art, which directly switches to listen mode upon receiving a multicast frame, this application embodiment can determine whether to switch to listen mode based on the information of the multicast frame after receiving it. This improves flexibility and ensures that multicast frames and subsequent frames are received in a timely manner, thus enhancing the rationality of the handover operation.

[0041] In one possible design, the set of conditions also includes at least one of the following three conditions:

[0042] A trigger frame is received, wherein the first field included in the trigger frame does not indicate the site, and the first field is used to indicate user information;

[0043] A multi-user block acknowledgment frame is received, and the second field included in the multi-user block acknowledgment frame does not indicate the site, wherein the second field is used to indicate site information;

[0044] A no-data PPDU claim frame is received, and the third field included in the no-data PPDU claim frame does not indicate the site, the third field being used to indicate site information.

[0045] In one possible design, the set of conditions includes the following conditions:

[0046] A broadcast frame is received, and the target receiving device indicated by the broadcast frame does not include the station.

[0047] By adding conditions that can cover multicast frames other than trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames, non-AP STAs can determine whether to switch to listen operation mode based on information from other multicast frames when performing handover operations.

[0048] In one possible design, the set of conditions also includes the following conditions:

[0049] A Very High Throughput Multi-User Block (PPDU) is received, wherein the basic service set indicated by the PPDU is the same as the basic service set of the cell where the site is located, the PPDU does not indicate that the site is a receiving device, and the value of the basic service set prohibition field carried in the most recently received high efficiency operation field of the site is 0.

[0050] The above design improves the rationality of switching operations by refining the set of conditions.

[0051] In one possible design, the set of conditions further includes at least one of the following conditions:

[0052] A unicast frame is received, the destination address carried by the unicast frame is different from the address of the site;

[0053] A frame is received, and the sending address carried by the frame is different from the sending address carried by the frame that initiated the current transmission opportunity;

[0054] A frame is received, and the basic service set corresponding to the frame is different from the basic service set of the cell where the site is located;

[0055] Upon receiving an Efficient Multi-User Block (PPDU), the Basic Service Set (PSS) indicated by the Efficient Multi-User Block (PPDU) differs from the PSS of the cell where the station is located. The Efficient Multi-User Block (PPDU) does not indicate that the station is a receiving device. The value of the PSS prohibition field carried in the most recently received Efficient Operation Field of the station is 0.

[0056] The carrier sensing mechanism indicates that the channel has been idle for a preset duration.

[0057] Fifthly, this application provides a multi-link-based communication method. The executing entity of this method can be a receiving-side device, such as a non-AP MLD, specifically a non-AP STA within the non-AP MLD, or a chip, circuit, or other component used to implement the functions of the receiving-side device. Taking a non-AP STA as an example, the method includes: within a first time period, determining whether to switch to a listening operation mode according to a first rule, wherein the start time of the first time period is a preset time or the reception time of a first beacon frame, and the first time period is used to receive multicast frames; and within a second time period, determining whether to switch to a listening operation mode according to a second rule, wherein the start time of the second time period is the reception time of an initial control frame.

[0058] In this embodiment of the application, multicast frames are sent to non-AP STAs in a concentrated manner during a specific time period (i.e., the first time period), and this time period adopts different switching rules from the second time period. This ensures that multicast frames and subsequent frames can be received in a timely manner, and also reduces the loss of subsequent transmission opportunities.

[0059] In one possible design, determining whether to switch to the listening operation mode according to the first rule includes:

[0060] If any condition in the first set of conditions is met, switch to the listening operation mode;

[0061] The first set of conditions includes at least one of the following:

[0062] A multicast frame indicating that transmission is complete has been received;

[0063] If the timer times out, the start time of the timer is the start time of the first time period;

[0064] The total transmission duration of the first access point site associated with the site, starting from the start time of the first time period, reaches a preset duration.

[0065] The above design allows for timely switching to the listening operation mode, enabling timely communication with the access point via other links.

[0066] In one possible design, the preset time is the transmission time of the first beacon frame that has been acquired in advance.

[0067] In one possible design, the first beacon frame is a transmission service indication map beacon frame.

[0068] In one possible design, the initiation of the first time period and the second time period may depend on the reception time of the first beacon frame (or a preset time) and the initial control frame.

[0069] In one possible design, if a non-AP STA receives a multicast frame within the first time period, and the multicast frame indicates "transmission not complete", then it will continue to receive multicast frames on that link.

[0070] In one possible design, determining whether to switch to the listening operation mode according to the second rule includes:

[0071] The first frame is received within the first duration of the second time period;

[0072] If the first frame does not satisfy all the conditions in the second condition set, then switch to the listening operation mode.

[0073] In one possible design, the second set of conditions includes at least one of the following conditions:

[0074] The frame type is a broadcast frame, which is different from trigger frames, multi-user block acknowledgment frames and no-data PPDU claim frames. The broadcast frame carries the address of the access point site associated with the site.

[0075] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame includes the station;

[0076] The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the station;

[0077] The frame type is a trigger frame, and the trigger frame includes a first field for indicating user information, the first field indicating the site;

[0078] The frame type is a clear send frame, and the receiving address carried by the clear send frame is the address of the access point site associated with the site;

[0079] The frame type is a multi-user block acknowledgment frame, and the multi-user block acknowledgment frame includes a second field for indicating site information, the second field indicating the site;

[0080] The frame type is a no-data PPDU claim frame, which includes a third field for indicating site information, the third field indicating the site.

[0081] By adding two conditions for multicast frames, non-AP STAs can switch to listen mode when they receive multicast frames that do not meet the aforementioned condition set, and conversely, they will not switch to listen mode when they receive multicast frames that meet the aforementioned condition set. This ensures that multicast frames and subsequent frames are received in a timely manner. Furthermore, these two conditions allow non-AP STAs to switch to listen mode promptly when they receive multicast frames that are not addressed to them, thereby reducing latency when communicating with access points using other links.

[0082] In one possible design, the second set of conditions includes at least one of the following conditions:

[0083] The frame type is a broadcast frame, and the broadcast frame carries the address of the access point site associated with the site;

[0084] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame includes the station;

[0085] The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the site;

[0086] The frame type is a clear send frame, and the receiving address carried by the clear send frame is the address of the access point site associated with the site.

[0087] The above conditions can cover trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames, as well as other multicast frames. This eliminates the need to list the conditions for trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames separately in the second set of conditions, thereby simplifying the protocol description and reducing implementation complexity. It also allows non-AP STAs to determine not to switch to listen mode upon receiving a multicast frame sent to them, ensuring that multicast frames and subsequent frames are received in a timely manner.

[0088] In one possible design, the second set of conditions includes at least one of the following conditions:

[0089] The frame type is a broadcast frame, and the receiving device indicated by the broadcast frame includes the station;

[0090] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame includes the site.

[0091] The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the station;

[0092] The frame type is a clear send frame, and the receiving address carried by the clear send frame is the address of the access point site associated with the site.

[0093] The above conditions can cover trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames, as well as other multicast frames. This eliminates the need to list the conditions for trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames separately in the second set of conditions, thereby simplifying the protocol description and reducing implementation complexity. It also allows non-AP STAs to determine not to switch to listen mode upon receiving a multicast frame sent to them, ensuring that multicast frames and subsequent frames are received in a timely manner.

[0094] In one possible design, determining whether to switch to the listening operation mode according to the second rule includes:

[0095] Receive the second frame;

[0096] If the second frame satisfies any condition in the third set of conditions, then switch to the listening operation mode.

[0097] In one possible design, the third set of conditions includes at least one of the following conditions:

[0098] The frame was sent from an address that is not the address of the access point site associated with the site.

[0099] The frame type is a broadcast frame, which is different from trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames. The target receiving device indicated by the broadcast frame does not include the station.

[0100] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the station;

[0101] The frame type is a unicast frame, and the receiving address carried by the unicast frame is not the address of the site;

[0102] The frame type is a trigger frame, and the first field included in the trigger frame does not indicate the site; the first field is used to indicate user information.

[0103] The frame type is a clear send frame, and the receiving address carried by the clear send frame is not the address of the access point site associated with the site.

[0104] The frame type is a multi-user block acknowledgment frame, and the second field included in the multi-user block acknowledgment frame does not indicate the site; the second field is used to indicate site information.

[0105] The frame type is a no-data PPDU claim frame, and the third field included in the no-data PPDU claim frame does not indicate the site. The third field is used to indicate site information.

[0106] By adding a condition that can cover other multicast frames, non-AP STAs can determine to switch to listen mode when they receive multicast frames that were not sent to them, and determine not to switch to listen mode when they receive multicast frames sent to them. This ensures that multicast frames and subsequent frames can be received in a timely manner.

[0107] In one possible design, the third set of conditions includes at least one of the following conditions:

[0108] The frame was sent from an address that is not the address of the access point site associated with the site.

[0109] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the station;

[0110] The frame type is a unicast frame, and the receiving address carried by the unicast frame is not the address of the site;

[0111] The frame type is a trigger frame, and the first field included in the trigger frame does not indicate the site; the first field is used to indicate user information.

[0112] The frame type is a clear send frame, and the receiving address carried by the clear send frame is not the address of the access point site associated with the site.

[0113] The frame type is a multi-user block acknowledgment frame, and the second field included in the multi-user block acknowledgment frame does not indicate the site; the second field is used to indicate site information.

[0114] The frame type is a no-data PPDU claim frame, and the third field included in the no-data PPDU claim frame does not indicate the site. The third field is used to indicate site information.

[0115] This example demonstrates how a non-AP STA can determine whether to switch to listen mode when it receives a multicast frame that was not intended for it, and whether to switch to listen mode when it receives a multicast frame intended for it, thus ensuring that multicast frames and subsequent frames are received in a timely manner.

[0116] In one possible design, the third set of conditions includes at least one of the following conditions:

[0117] The frame was sent from an address that is not the address of the access point site associated with the site.

[0118] The frame type is a multicast frame, and the receiving device indicated by the multicast frame does not include the site;

[0119] The frame type is a unicast frame, and the receiving address carried by the unicast frame is not the address of the site;

[0120] The frame type is a clear send frame, and the receiving address carried by the clear send frame is not the address of the access point site associated with the site.

[0121] The above conditions can cover trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames, as well as other multicast frames. This eliminates the need to list the conditions for trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames separately in the third condition set, thus simplifying the protocol description and reducing implementation complexity. Furthermore, it allows non-AP STAs to determine whether to switch to listen mode when receiving a multicast frame not intended for them, and not to switch to listen mode when receiving a multicast frame intended for them, thereby ensuring that multicast frames and subsequent frames are received in a timely manner.

[0122] In one possible design, the third set of conditions includes at least one of the following conditions:

[0123] A multicast frame is received, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the site;

[0124] A trigger frame is received, wherein the first field included in the trigger frame does not indicate the site, and the first field is used to indicate user information;

[0125] A multi-user block acknowledgment frame is received, and the second field included in the multi-user block acknowledgment frame does not indicate the site, wherein the second field is used to indicate site information;

[0126] A no-data PPDU claim frame is received, and the third field included in the no-data PPDU claim frame does not indicate the site, the third field being used to indicate site information;

[0127] A unicast frame is received, the destination address carried by the unicast frame is different from the address of the site;

[0128] A frame is received, and the sending address carried by the frame is different from the sending address carried by the frame that initiated the current transmission opportunity;

[0129] A frame is received, and the basic service set corresponding to the frame is different from the basic service set of the cell where the site is located;

[0130] A PPDU is received, which is an efficient multi-user block PPDU or an ultra-high throughput multi-user block PPDU. The basic service set indicated by the PPDU is the same as the basic service set of the cell where the station is located. The PPDU does not indicate that the station is a receiving device. The value of the basic service set prohibition field carried in the efficient operation field most recently received by the station is 0.

[0131] The carrier sensing mechanism indicates that the channel has been idle for a preset duration.

[0132] By adding conditions that can cover multicast frames other than trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames, non-AP STAs can determine whether to switch to listen mode based on information from other multicast frames during handover operations. Compared to existing technologies that directly switch to listen mode upon receiving a multicast frame, this approach determines whether to switch to listen mode based on the information within the received multicast frame. This improves flexibility and ensures that multicast frames and subsequent frames are received promptly, enhancing the rationality of the handover operation.

[0133] In one possible design, the third set of conditions includes at least one of the following conditions:

[0134] A multicast frame is received, wherein the receiving device indicated by the multicast frame does not include the site;

[0135] A unicast frame is received, the destination address carried by the unicast frame is different from the address of the site;

[0136] A frame is received, and the sending address carried by the frame is different from the sending address carried by the frame that initiated the current transmission opportunity;

[0137] A frame is received, and the basic service set corresponding to the frame is different from the basic service set of the cell where the site is located;

[0138] A PPDU is received, which is an efficient multi-user block PPDU or an ultra-high throughput multi-user block PPDU. The basic service set indicated by the PPDU is different from the basic service set of the cell where the station is located. The PPDU does not indicate that the station is a receiving device. The value of the basic service set prohibition field carried in the efficient operation field most recently received by the station is 0.

[0139] The carrier sensing mechanism indicates that the channel has been idle for a preset duration.

[0140] The above conditions can cover trigger frames, multi-user block acknowledgment frames, no-data PPDU claim frames, and other multicast frames. This eliminates the need to list the conditions for trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames separately in the third condition set, thus simplifying the protocol description and reducing implementation complexity. Furthermore, it allows non-AP STAs to determine whether to switch to listen mode upon receiving a multicast frame, ensuring that multicast frames and subsequent frames are received in a timely manner.

[0141] In one possible design, the third set of conditions includes at least one of the following conditions:

[0142] A multicast frame is received, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the site;

[0143] A broadcast frame is received, and the target receiving device indicated by the broadcast frame does not include the station;

[0144] A frame is received, and the sending address carried by the frame is different from the sending address carried by the frame that initiated the current transmission opportunity;

[0145] A frame is received, and the basic service set corresponding to the frame is different from the basic service set of the cell where the site is located;

[0146] A PPDU is received, which is an efficient multi-user block PPDU or an ultra-high throughput multi-user block PPDU. The basic service set indicated by the PPDU is different from the basic service set of the cell where the station is located. The PPDU does not indicate that the station is a receiving device. The value of the basic service set prohibition field carried in the efficient operation field most recently received by the station is 0.

[0147] The carrier sensing mechanism indicates that the channel has been idle for a preset duration.

[0148] The above conditions can cover trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames, as well as other multicast frames. This eliminates the need to list the conditions for trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames separately in the third condition set, thereby simplifying the protocol description and reducing implementation complexity. Furthermore, it allows non-AP STAs to determine whether to switch to listen mode upon receiving a multicast frame, ensuring that multicast frames and subsequent frames are received in a timely manner.

[0149] In one possible design, if the initial control frame indicates that the second time period includes multicast frames, it is determined whether to switch to the listening operation mode based on the second condition set or the third condition set.

[0150] In one possible design, if the initial control frame indicates that the second time period does not include multicast frames, determining whether to switch to the listening operation mode according to the second rule may include:

[0151] Receive the third frame;

[0152] If the third frame does not satisfy all the conditions in the fourth condition set, then switch to the listening operation mode.

[0153] The fourth set of conditions includes at least one of the following conditions:

[0154] The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the site;

[0155] The frame type is a trigger frame, and the trigger frame includes a first field for indicating user information, the first field indicating the site;

[0156] The frame type is a clear send frame, and the receiving address carried by the clear send frame is the address of the access point site associated with the site.

[0157] The frame type is a multi-user block acknowledgment frame, and the multi-user block acknowledgment frame includes a second field for indicating site information, the second field indicating the site;

[0158] The frame type is a no-data PPDU claim frame, and the no-data PPDU claim frame includes a third field for indicating site information, the third field indicating the site.

[0159] Sixthly, this application also provides a multi-link-based communication device, which implements any of the methods provided in any of the first to fifth aspects described above. This communication device can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functions described above.

[0160] In one possible design, the communication device includes a processor configured to support the communication device in performing the corresponding functions of the non-AP STA described above. The communication device may also include a memory coupled to the processor, which stores necessary program instructions and data for the communication device. Optionally, the communication device further includes interface circuitry for supporting communication between the communication device and other devices.

[0161] In one possible design, the communication device includes corresponding functional modules, each used to implement the steps in the above method. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

[0162] In one possible design, the communication device includes a processing module and a communication module, which can perform the corresponding functions in the above method examples, as described in the methods provided in any of the first to fifth aspects, and will not be repeated here.

[0163] In a seventh aspect, a multi-link communication device is provided, including a processor and an interface circuit. The interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor, or to send signals from the processor to other communication devices outside the communication device. The processor is used to implement any one of the first to fifth aspects and any possible design methods through logic circuits or execution code instructions.

[0164] Eighthly, a computer-readable storage medium is provided that stores a computer program or instructions which, when executed by a processor, implement the methods of any one of the first to fifth aspects and any possible design described above.

[0165] Ninthly, a computer program product storing instructions is provided, which, when executed by a processor, implement the methods of any one of the first to fifth aspects and any possible design.

[0166] In a tenth aspect, a chip system is provided, comprising a processor and potentially a memory, for implementing methods of any of the first to fifth aspects and any possible designs described above. The chip system may be composed of chips or may include chips and other discrete devices.

[0167] Eleventhly, a communication system is provided, the system including the device described in the first aspect (such as non-APMLD or non-AP STA), and may further include AP MLD or access point.

[0168] In a twelfth aspect, a communication system is provided, the system including the apparatus described in the second aspect (such as non-APMLD or non-AP STA), and may further include AP MLD or access point.

[0169] In a thirteenth aspect, a communication system is provided, the system including the apparatus described in the third aspect (such as non-APMLD or non-AP STA), and may further include AP MLD or access point.

[0170] In a fourteenth aspect, a communication system is provided, the system including the apparatus described in the fourth aspect (such as non-APMLD or non-AP STA), and may further include AP MLD or access point.

[0171] In a fifteenth aspect, a communication system is provided, the system comprising the apparatus described in the fifth aspect (such as non-APMLD or non-AP STA), and may further comprise AP MLD or access point. Attached Figure Description

[0172] Figure 1 This is a schematic diagram of an MLO applicable to an embodiment of this application;

[0173] Figure 2 This is a schematic diagram of a switching operation applicable to an embodiment of this application;

[0174] Figure 3 This is a schematic diagram of the architecture of a communication system applicable to the embodiments of this application;

[0175] Figure 4 This is a flowchart illustrating an MLO communication method applicable to an embodiment of this application;

[0176] Figure 5 This is a flowchart illustrating an MLO communication method applicable to an embodiment of this application;

[0177] Figure 6 This is a flowchart illustrating an MLO communication method applicable to an embodiment of this application;

[0178] Figure 7 This is a flowchart illustrating an MLO communication method applicable to an embodiment of this application;

[0179] Figure 8 This is a schematic diagram illustrating a first time period and a second time period to which embodiments of this application apply;

[0180] Figure 9 This is a schematic diagram of the structure of an MLO communication device applicable to the embodiments of this application;

[0181] Figure 10 This is a schematic diagram of the structure of an MLO communication device applicable to the embodiments of this application. Detailed Implementation

[0182] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings.

[0183] The following explanations of some terms used in the embodiments of this application are provided to facilitate understanding by those skilled in the art.

[0184] 1. Multi-link operation (MLO)

[0185] MLO supports wireless local area network (WLAN) devices in having the ability to transmit and receive on multiple frequency bands. Multiple frequency bands can include, but are not limited to, the 2.4GHz Wireless-Fidelity (Wi-Fi) band, the 5GHz Wi-Fi band, and the 6GHz Wi-Fi band. Access and transmission on each frequency band can be called a link, or access and transmission within a frequency range of the same frequency band can be called a link. Access and transmission consisting of multiple links can be called MLO. A device that simultaneously supports multiple links is called a multi-link device (MLD), and the internal entity within an MLD responsible for any one link is called a station (STA). If all STAs within an MLD are wireless access points (APs), the MLD can be further called an AP MLD; if all STAs within an MLD are non-AP STAs, it can be further called a non-AP MLD. Figure 1 The example shown contains two MLDs: MLD A and MLD B. Each MLD has N links.

[0186] 2. Enhanced multi-link single radio (EMLSR)

[0187] like Figure 2 As shown, a non-access point multi-link device (non-AP MLD) only has single-chain transceiver capability, but it can simultaneously enter listening operation on multiple links. During listening operation, the non-AP MLD uses one radio chain to receive signals on each link. When the AP MLD successfully sends an initial control frame to this non-AP MLD on any link i, this non-AP MLD switches all radio chains to link i to interact with the AP MLD using frames. After the frame interaction is complete, it switches the radio chains back to the respective links to return to listening operation.

[0188] 3. Radio chain

[0189] A radio chain is a physical entity that can serve as a receive chain and / or a transmit chain.

[0190] The receive chain is the physical entity that implements signal processing to provide the received signal to the digital baseband. Signal processing includes filtering, amplification, down-conversion, and sampling.

[0191] The transmit chain is the physical entity that performs signal processing to generate the transmitted signal from the digital baseband. Signal processing includes digital-to-analog conversion, filtering, amplification, and up-conversion.

[0192] For example, a radio chain can be wireless or radio-based.

[0193] 4. Multicast frames and broadcast frames

[0194] In one exemplary illustration, a multicast frame is a frame addressed to multiple sites, and the MAC address of the multicast frame corresponds to multiple sites. A broadcast frame is a type of multicast frame where the MAC address indicates a broadcast address. That is, multicast frames include broadcast frames, and a broadcast frame is a special type of multicast frame.

[0195] In another exemplary illustration, a multicast frame is a frame directed to a group of sites, and a broadcast frame is a frame directed to all sites; multicast frames and broadcast frames are two different frame types.

[0196] It should be noted that, for ease of description, this application uses the example of multicast frames including broadcast frames to introduce the solution provided by this application. It should be understood that this application also describes the solution as if multicast frames and broadcast frames are two different frame types. For example, one description of the solution as multicast frames including broadcast frames is "The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame includes the site." If the solution is described as if multicast frames and broadcast frames are two different frame types, it would be "The frame type is a multicast frame, and the receiving device indicated by the multicast frame includes the site."

[0197] In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.

[0198] Furthermore, unless otherwise stated, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of multiple objects. For example, the first time period and the second time period are only used to distinguish different time periods, and do not indicate that the two time periods are different in priority, time sequence, or importance.

[0199] For ease of description, this application uses a site in an MLD as an example. In one example, the site described in this application embodiment can be a STA in an MLD that supports EMLSR. A site in a non-AP MLD can be referred to as a non-AP STA, and a site in an AP MLD can be referred to as an AP.

[0200] The technical features involved in the embodiments of this application are described below.

[0201] The IEEE 802.11be standards working group proposed an EMLSR operating mechanism: when a non-AP MLD meets one of the following conditions, it must immediately switch the antenna back to the respective link to perform listening operations:

[0202] Scenario 1: At the start of the non-AP STA responding to the most recent frame from the AP, or at the start of the non-AP STA receiving the most recent frame from the AP that does not require an immediate response from the non-AP STA, the non-AP STA does not receive a physical layer start reception indication (PHY-RXSTART.indication) within the timeout period. The timeout period is calculated as: short inter-frame space (SIFS) duration (aSIFSTime) + slot duration (aSlotTime) + physical layer start reception delay (aRxPHYStartDelay). (The MAC of the STA affiliated with the non-AP MLD that received the initial Control frame does not receive a PHY-RXSTART.indication primitive during a timeout interval of aSIFSTime+aSlotTime+aRxPHYStartDelay starting at the end of the PPDU transmitted by the STA of the non-AP MLD as a response to the most recently received frame from the AP affiliated with the AP MLD or starting at the end of the reception of the PPDU containing a frame for the STA from the AP affiliated with the AP MLD that does not require immediate acknowledgment).

[0203] In scenario two, n begins when the non-AP STA replies to the most recent frame from the AP, or when the non-AP STA receives the most recent frame from the AP that does not require an immediate reply from the non-AP STA, and the non-AP STA receives an instruction from the physical layer to enable reception within the timeout period. However, during the process of receiving the PPDU corresponding to the physical layer's indication of enabled reception, the non-AP STA did not detect any of the following frames: (The MAC of the STA affiliated with the non-AP MLD that received the initial control frame receives a PHY-RXSTART.indicationprimitive during a timeout interval of aSIFSTime+aSlotTime+aRxPHYStartDelay starting at the end of the PPDU transmitted by the STA of the non-AP MLD as a response to the most recently received frame from the AP affiliated with the AP MLD, or starting at the end of the reception of the PPDU containing a frame for the STA from the AP affiliated with the AP MLD that does not require immediate acknowledgement and the STA affiliated with the non-AP MLD does not detect, within the PPDU corresponding to the PHY-RXSTART.indication any of the following frames):

[0204] An individually addressed frame, wherein the receiving address (RA) in the frame is equal to the MAC address of the STA affiliated with the non-AP MLD;

[0205] A trigger frame that contains a User Info field indicating the non-AP STA.

[0206] A CTS-to-self frame with the RA address equal to the MAC address of the AP associated with the AP MLD;

[0207] A Multi-STA BlockAck frame that has one of the Per AID TID Info fields addressed to the STA affiliated with the non-AP MLD;

[0208] A No Data PPDU Announcement (NDPA) frame that contains one of the STA Info fields addressing the STA affiliated with the non-AP MLD.

[0209] Scenario 3: The non-AP STA does not respond to the most recently received frame from the AP that requires an immediate response from the non-AP STA.

[0210] According to the above rules, if a non-AP STA receives a broadcast frame or a multicast frame during frame interaction with the AP after receiving the initial control frame, it will match situation two above. As a result, it needs to immediately switch the radio chain back to each link to perform listening operations, causing subsequent frames to be unreceived.

[0211] Based on this, one possible solution is to not send broadcast or multicast frames to avoid antenna switching by non-AP STAs, but this would prevent multicast and broadcast frames from being sent to non-AP STAs.

[0212] Another possible solution is to send broadcast or multicast frames only after all unicast frames have been sent. However, this results in only one broadcast or multicast frame being successfully sent at most, limiting flexibility. Furthermore, broadcast or multicast frames often take precedence over unicast frames, meaning this method could lead to broadcast or multicast frames not being sent in a timely manner.

[0213] Therefore, resolving the issue of unreasonable switching operations in MLO is an urgent problem to be solved.

[0214] Based on this, embodiments of this application provide a multi-link communication method and apparatus to solve the problem of unreasonable handover operations in MLO. The method and apparatus are based on the same concept. Since the principles by which the method and apparatus solve the problem are similar, the implementations of the apparatus and method can be mutually referred to, and repeated details will not be elaborated further.

[0215] This application is applicable to wireless LAN systems that support IEEE 802.11ax next-generation Wi-Fi protocols, such as 802.11be, Wi-Fi 7, or EHT, as well as 802.11be next-generation, Wi-Fi 8, Wi-Fi AI, and other 802.11 series protocols. It can also be applied to wireless personal area network systems and sensing systems based on ultra-wideband (UWB).

[0216] The communication method provided in this application can also be applied to various other communication systems, such as the Internet of Things (IoT), narrowband Internet of Things (NB-IoT), long term evolution (LTE), fifth-generation (5G) communication systems, hybrid LTE and 5G architectures, 5G new radio (NR) systems, and new communication systems emerging in 6G or future communication developments. The communication system described in this application can also be a machine-to-machine (M2M) network, a non-terrestrial network (NTN) network, or other networks.

[0217] The application scenarios of this application embodiment can be communication between an AP MLD and one or more non-AP MLDs, and it is also applicable to communication between AP MLDs, as well as communication between non-AP MLDs. For example, please refer to... Figure 3 This illustrates a network architecture diagram applicable to embodiments of this application. Figure 3 Taking a network comprising one AP MLD and two associated non-AP MLDs, non-AP MLD 1 and non-AP MLD 2, as an example. The AP MLD can communicate with non-AP MLD 1 and non-AP MLD 2, and non-AP MLD 1 and non-AP MLD 2 can communicate with each other. It should be understood that... Figure 3 The number of AP MLDs and non-AP MLDs listed is just an example; there could be more or fewer.

[0218] The non-AP MLD involved in the embodiments of this application can be any user terminal, user equipment, access device, subscriber station, subscriber unit, mobile station, user agent, user equipment, or other names with wireless communication capabilities. The user terminal can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities, as well as various forms of user equipment (UE), mobile station (MS), terminal, terminal equipment, portable communication devices, handheld devices, portable computing devices, entertainment devices, gaming devices or systems, global positioning system devices, or any other suitable device configured for network communication via wireless media. For ease of description, the devices mentioned above are collectively referred to as non-AP MLDs.

[0219] The AP MLD involved in this application embodiment is a device deployed in a wireless communication network to provide wireless communication functions. The AP MLD can serve as the central hub of the communication system and can be a base station, router, gateway, repeater, communication server, switch, or bridge, etc. The base station can include various forms of macro base stations, micro base stations, repeater stations, etc. For ease of description, the devices mentioned above are collectively referred to as AP MLDs.

[0220] Specifically, the AP MLD and non-AP MLD involved in this application can be AP MLD and non-AP MLD applicable to the IEEE 802.11be system standard, AP MLD and non-AP MLD applicable to the IEEE 802.11 system standard, or AP MLD and non-AP MLD applicable to other standards, such as AP MLD and non-APMLD applicable to future standards.

[0221] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0222] In the embodiments of this application, "if..." can also be described as "under the circumstances of...", "if", or "when...", etc. For example, "if the first frame does not satisfy all the conditions in the condition set, switch to the listening operation mode" can also be described as "if the first frame does not satisfy all the conditions in the condition set, switch to the listening operation mode", or "when the first frame does not satisfy all the conditions in the condition set, switch to the listening operation mode", or "when the first frame does not satisfy all the conditions in the condition set, switch to the listening operation mode", etc.

[0223] This application uses a non-AP STA in a non-AP MLD as an example for illustration.

[0224] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0225] Example 1:

[0226] like Figure 4 The diagram shown is a flowchart illustrating a communication method provided in an embodiment of this application.

[0227] S401, the AP sends the first PPDU. Correspondingly, the non-AP STA receives the first PPDU within the first duration.

[0228] The first PPDU includes the first frame.

[0229] For example, the first duration can be a preset duration starting from the time the non-AP STA replies to the most recent frame from the AP, or a preset duration starting from the time the non-AP STA receives the most recent frame from the AP that does not require an immediate reply from the non-AP STA. Wherein, the preset duration = short inter-frame space (SIFS) duration (aSIFSTime) + slot duration (aSlotTime) + physical layer start reception delay (aRxPHYStartDelay).

[0230] In one possible implementation, the non-AP STA receives the first PPDU within a first duration, which can be achieved as follows: the non-AP STA receives an indication to enable reception from the physical layer within the first duration, and detects the first PPDU during the process of receiving the PPDU corresponding to the indication.

[0231] S402, if the first frame does not satisfy all the conditions in the condition set, the non-AP STA switches to the listening operation mode.

[0232] Wherein, at least one condition in the set of conditions is the frame information of a multicast frame, which is different from the trigger frame, the multi-user block acknowledgment frame and the no-data PPDU claim frame. In other words, the multicast frame is different from (or is not) the existing definition of the trigger frame, the multi-user block acknowledgment frame and the no-data PPDU claim frame.

[0233] The following provides an example illustrating at least one of these conditions.

[0234] Example 1.1, the at least one condition may include at least one of the following conditions:

[0235] The frame type is a broadcast frame, which is different from trigger frames, multi-user block acknowledgment frames, and no-data PPDU announcement frames. The broadcast frame carries the address of the AP associated with the non-AP STA (a broadcast frame with the TA equal to the MAC address of the AP affiliated with the AP MLD, except that the frame is a TF, a Multi-STA BlockAck frame, or an NDPAnnouncement frame).

[0236] The frame type is a multicast frame, which differs from a broadcast frame. The receiving device indicated by this multicast frame includes the non-AP STA (a group-addressed frame, and the STA is a member of this group). The difference between this multicast frame and a broadcast frame can be understood as the multicast address not being a broadcast address, or the multicast frame not being a broadcast frame. This interpretation will be used in the following text and will not be elaborated further.

[0237] For example 1.2, the at least one condition may also include at least one of the following conditions:

[0238] The frame type is a broadcast frame, and the broadcast frame carries the address of the AP associated with the non-AP STA (abroadcast frame with the TA equal to the MAC address of the AP affiliated with the AP MLD);

[0239] The frame type is a multicast frame, which is different from a broadcast frame. The receiving device indicated by this multicast frame includes the non-AP STA (a group addressed frame and the STA is a member of this group).

[0240] For example 1.3, the at least one condition may also include at least one of the following conditions:

[0241] The frame type is a broadcast frame, and the receiving device indicated by the broadcast frame includes the non-AP STA (a broadcast frame and the STA affiliated with the non-AP MLD is one of the target receivers of this broadcast frame);

[0242] The frame type is a multicast frame, which is different from a broadcast frame. The receiving device indicated by this multicast frame includes the non-AP STA (a group addressed frame and the STA is a member of this group).

[0243] Optionally, in addition to at least one of the above conditions, the set of conditions may also include at least one of the following five conditions:

[0244] The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the non-AP STA;

[0245] The frame type is a trigger frame, and the trigger frame includes a first field for indicating user information, which indicates the non-AP STA. For example, the first field may be a user information field.

[0246] The frame type is a clear send frame, and the receiving address carried by the clear send frame is the address of the AP associated with the non-AP STA;

[0247] The frame type is a multi-user block acknowledgment frame, and the multi-user block acknowledgment frame includes a second field for indicating site information, which indicates the non-AP STA. For example, the second field may be Per AID TID Info.

[0248] The frame type is a no-data PPDU claim frame, and the no-data PPDU claim frame includes a third field for indicating site information, which indicates the non-AP STA. For example, the third field may be the STA information field.

[0249] The above five conditions can be found in the relevant explanation of situation two above, and will not be repeated here.

[0250] The following examples illustrate three specific instances of the condition set, using at least one of the above conditions as examples.

[0251] Example 1.1:

[0252] Based on Example 1.1 above, the condition set can include the following conditions:

[0253] The frame type is a broadcast frame, which is different from trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames. The broadcast frame carries the address of the AP associated with the non-AP STA.

[0254] The frame type is a multicast frame, which is different from a broadcast frame. In other words, the multicast frame is not a broadcast frame, and the receiving device indicated by the multicast frame includes the non-AP STA.

[0255] The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the non-AP STA;

[0256] The frame type is a trigger frame, and the trigger frame includes a first field for indicating user information, which indicates the non-AP STA. For example, the first field may be a user information field.

[0257] The frame type is a clear send frame, and the receiving address carried by the clear send frame is the address of the AP associated with the non-AP STA;

[0258] The frame type is a multi-user block acknowledgment frame, and the multi-user block acknowledgment frame includes a second field for indicating site information, which indicates the non-AP STA. For example, the second field may be Per AID TID Info.

[0259] The frame type is a no-data PPDU claim frame, and the no-data PPDU claim frame includes a third field for indicating site information, which indicates the non-AP STA. For example, the third field may be the STA information field.

[0260] This example adds two conditions to the multicast frame scenario described above (Scenario 2), allowing the non-AP STA to determine whether to switch to listen mode upon receiving a multicast frame intended for it. For example, it switches to listen mode if the received multicast frame does not meet all the conditions in the condition set; conversely, it does not switch to listen mode if the received multicast frame meets any of the conditions. This ensures that multicast frames and subsequent frames are received promptly. Furthermore, these two conditions allow the non-AP STA to switch to listen mode promptly when receiving a multicast frame not intended for it, thereby reducing latency when communicating with the AP using other links.

[0261] Example 1.2:

[0262] Based on Example 1.2 above, the condition set can include the following conditions:

[0263] The frame type is a broadcast frame, and the broadcast frame carries the address of the AP associated with the non-AP STA;

[0264] The frame type is a multicast frame, which is different from a broadcast frame. The receiving device indicated by this multicast frame includes the non-AP STA.

[0265] The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the non-AP STA;

[0266] The frame type is a clear send frame, and the receive address carried by the clear send frame is the address of the AP associated with the non-AP STA.

[0267] The above conditions can cover trigger frames, multi-user block acknowledgment frames, no-data PPDU claim frames, and other multicast frames. Therefore, the conditions for trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames do not need to be listed separately in the condition set, thus simplifying the protocol description and reducing implementation complexity. It also allows non-AP STAs to determine whether to switch to listen mode upon receiving a multicast frame. For example, they can switch to listen mode if the received multicast frame does not meet all the conditions in the condition set, and conversely, not switch to listen mode if the received multicast frame meets any of the conditions in the condition set. This improves flexibility and ensures that multicast frames and subsequent frames are received in a timely manner.

[0268] Example 1.3:

[0269] Based on Example 1.3 above, the condition set can include the following conditions:

[0270] The frame type is a broadcast frame, and the receiving device indicated by the broadcast frame includes the non-AP STA;

[0271] The frame type is a multicast frame, which is different from a broadcast frame. The receiving device indicated by this multicast frame includes the non-AP STA.

[0272] The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the non-AP STA;

[0273] The frame type is a clear send frame, and the receive address carried by the clear send frame is the address of the AP associated with the non-AP STA.

[0274] The above conditions can cover trigger frames, multi-user block acknowledgment frames, no-data PPDU claim frames, and other multicast frames. Therefore, the conditions for trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames do not need to be listed separately in the condition set, thus simplifying the protocol description and reducing implementation complexity. It also allows non-AP STAs to determine whether to switch to listen mode upon receiving a multicast frame. For example, they can switch to listen mode if the received multicast frame does not meet all the conditions in the condition set, and conversely, not switch to listen mode if the received multicast frame meets any of the conditions in the condition set. This improves flexibility and ensures that multicast frames and subsequent frames are received in a timely manner.

[0275] The above describes a method for a non-AP STA to determine whether to switch to listening operation mode based on a set of conditions. Optionally, a non-AP STA can also switch to listening operation mode in the following scenarios (or situations or conditions): receiving a second PPDU; if the basic service set (BSS) indicated by the second PPDU is an inter-BSS, then switching to listening operation mode (The STA affiliated with the non-AP MLD receives a PPDU and classifies the PPDU as an inter-BSS PPDU). It should be noted that this method can also be implemented independently of the method described in Embodiment 1.

[0276] In one possible implementation, if it is determined that the BSS indicated by the first PPDU is an inter-BSS before step S402, then it can be determined to switch to the listening operation mode. In this implementation, step S402 may not be executed.

[0277] Currently, most rules for switching to listen mode are based on MAC layer information, carried in the data portion. However, inter-BSS PPDUs can be identified through the physical layer SIG field. The SIG field is located before the data portion in the PPDU. Therefore, in the above method, by switching to listen mode when an inter-BSS PPDU is detected, it is not necessary to continue parsing the MAC content located in the data portion of the PPDU. This allows for timely switching and helps reduce latency when communicating with the AP using other links.

[0278] Optionally, the non-AP STA can also switch to listening operation mode in other scenarios (situations or conditions), such as situation one or situation three mentioned above. For details, please refer to the relevant descriptions in the background introduction above, which will not be repeated here.

[0279] In this embodiment, by adding conditions related to multicast frames other than trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames to the condition set, a non-AP STA can determine whether to switch to listen operation mode based on information from other multicast frames during handover. Compared to the prior art, which directly switches to listen operation mode upon receiving a multicast frame, this embodiment can determine whether to switch to listen operation mode based on the information of the multicast frame. For example, it can switch to listen operation mode if the received multicast frame does not meet all the conditions in the condition set, and conversely, it will not switch to listen operation mode if the received multicast frame meets any of the conditions in the condition set. This improves flexibility and ensures that multicast frames and subsequent frames are received in a timely manner.

[0280] Furthermore, Embodiment 1 of this application adopts the handover rule logic in the current IEEE 802.11be standard document, which can improve the rationality and flexibility of handover operations while reducing changes to the protocol.

[0281] Example 1 introduces a technical solution for determining whether to perform a handover operation based on whether conditions in a condition set are met, to ensure that multicast frames and subsequent frames can be received in a timely manner. Example 2 below introduces another method, which also uses the condition set to determine whether to perform a handover operation, to ensure that multicast frames and subsequent frames can be received in a timely manner.

[0282] Example 2:

[0283] like Figure 5 The diagram shown is a flowchart illustrating a communication method provided in an embodiment of this application.

[0284] S501, the AP sends the first PPDU. Correspondingly, the non-AP STA receives the first PPDU within the first duration.

[0285] The first PPDU includes the first frame. Specifically, it can be... Figure 4 The relevant description of S401 in the method will not be repeated here.

[0286] S502, if the first frame satisfies any condition in the condition set, the non-AP STA switches to the listening operation mode.

[0287] Among them, at least one of the conditions in the set of conditions corresponds to a range of frame types including multicast frames, which are different from trigger frames, multi-user block acknowledgment frames, and dataless physical layer protocol data unit (PPDU) claim frames.

[0288] The following provides an example illustrating at least one of these conditions.

[0289] Example 2.1, the at least one condition may include at least one of the following conditions:

[0290] The frame was sent from an address that is not the address of the AP to which the non-AP STA is associated (a frame with the TA that differs from the MAC address of the AP affiliated with the AP MLD);

[0291] The frame type is a broadcast frame, and the target receiving device indicated by the broadcast frame does not include the non-AP STA (abroadcast frame but the STA affiliated with the non-AP MLD is not one of the target receiver STA). Optionally, the broadcast frame may be different from the trigger frame, multi-user block acknowledgment frame, and no-data PPDU claim frame. In other words, the multicast frame is different from (or not) the currently defined trigger frame, multi-user block acknowledgment frame, and no-data PPDU claim frame.

[0292] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the non-AP STA (a group addressed frame, but the STA is not a member of this group). Here, "different from a broadcast frame" can be understood as the multicast address of the multicast frame not being a broadcast address, or the multicast frame not being a broadcast frame. This interpretation will be used in the following text and will not be elaborated further.

[0293] Example 2.2, the at least one condition may include at least one of the following conditions:

[0294] The frame was sent from an address that is not the address of the AP to which the non-AP STA is associated (a frame with the TA that differs from the MAC address of the AP affiliated with the AP MLD);

[0295] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the non-AP STA (a group addressed frame, but the STA is not a member of this group).

[0296] Optionally, in addition to at least one of the above conditions, the condition set may also include at least one of the following five conditions:

[0297] The frame type is a unicast frame, and the receive address carried by the unicast frame is not the address of the non-AP STA (an individually addressed frame, addressed to another STA that is not affiliated with the non-AP MLD). This condition can also be described as the frame type being a unicast frame, and the receive address carried by the unicast frame indicating another non-AP STA.

[0298] The frame type is a trigger frame, and the first field included in the trigger frame does not indicate the non-AP STA. The first field is used to indicate user information (a trigger frame that has none of the User Info fields addressed to the STA affiliated with the non-AP MLD). For example, the first field can be a user information field.

[0299] The frame type is a clear send frame, and the receive address carried by the clear send frame is not the address of the AP associated with the non-AP STA (a CTS-to-self frame with the RA not equal to the MAC address of the AP affiliated with the AP MLD);

[0300] The frame type is a multi-user block acknowledgment frame, and the second field included in the multi-user block acknowledgment frame does not indicate the non-APSTA. The second field is used to indicate non-AP STA information (a Multi-STA BlockAck frame that has one of the Per AID TID Info fields addressed to the STA affiliated with the non-AP MLD). For example, the second field can be Per AID TID Info.

[0301] The frame type is a no-data PPDU announcement frame, and the third field included in the no-data PPDU announcement frame does not indicate the non-AP STA. The third field is used to indicate non-AP STA information (a NDP Announcement frame that has none of the STA Info fields addressed to the STA affiliated with the non-AP MLD). For example, the third field can be the STA Information field.

[0302] The following examples illustrate three specific instances of the condition set, using at least one of the above conditions as examples.

[0303] Example 2.1:

[0304] Based on Example 2.1 above, the condition set can include the following conditions:

[0305] The frame was sent to an address that is not the address of the AP associated with this non-AP STA;

[0306] The frame type is a broadcast frame, which is different from trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames, and the target receiving device indicated by the broadcast frame does not include the non-AP STA;

[0307] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the non-AP STA;

[0308] The frame type is a unicast frame, and the receiving address carried by the unicast frame is not the address of the non-AP STA;

[0309] The frame type is a trigger frame, and the first field included in the trigger frame does not indicate the non-AP STA; the first field is used to indicate user information.

[0310] The frame type is a clear send frame, and the receiving address carried by the clear send frame is not the address of the AP associated with the non-AP STA;

[0311] The frame type is a multi-user block acknowledgment frame, and the second field included in the multi-user block acknowledgment frame does not indicate the non-APSTA, the second field being used to indicate non-APSTA information;

[0312] The frame type is a no-data PPDU claim frame, and the third field included in the no-data PPDU claim frame does not indicate the non-AP STA, which is used to indicate non-AP STA information.

[0313] This example adds conditions that can override other multicast frames, allowing a non-AP STA to determine whether to switch to listen mode when it receives a multicast frame. For example, it will not switch to listen mode if the received multicast frame meets any of the conditions in the condition set, and conversely, it will not switch to listen mode if the received multicast frame does not meet all the conditions in the condition set. This ensures that multicast frames and subsequent frames can be received in a timely manner.

[0314] Example 2.2:

[0315] Based on Example 2.2 above, the condition set can include the following conditions:

[0316] The frame was sent to an address that is not the address of the AP associated with this non-AP STA;

[0317] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the non-AP STA;

[0318] The frame type is a unicast frame, and the receiving address carried by the unicast frame is not the address of the non-AP STA;

[0319] The frame type is a clear send frame, and the receive address carried by the clear send frame is not the address of the AP associated with the non-AP STA.

[0320] The above conditions can cover trigger frames, multi-user block acknowledgment frames, no-data PPDU claim frames, and other multicast frames. Therefore, the conditions for trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames do not need to be listed separately in the condition set, thus simplifying the protocol description and reducing implementation complexity. It also allows non-AP STAs to determine whether to switch to listen mode upon receiving a multicast frame. For example, they can choose not to switch to listen mode if the received multicast frame meets any of the conditions in the condition set, and switch to listen mode if the received multicast frame does not meet all the conditions in the condition set. This improves flexibility and ensures that multicast frames and subsequent frames are received in a timely manner.

[0321] Example 2.3:

[0322] Based on Example 2.2 above, the condition set can also include the following conditions:

[0323] The frame was sent to an address that is not the address of the AP associated with this non-AP STA;

[0324] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the non-AP STA;

[0325] The frame type is a unicast frame, and the receiving address carried by the unicast frame is not the address of the non-AP STA;

[0326] The frame type is a trigger frame, and the first field included in the trigger frame does not indicate the non-AP STA; the first field is used to indicate user information.

[0327] The frame type is a clear send frame, and the receiving address carried by the clear send frame is not the address of the AP associated with the non-AP STA;

[0328] The frame type is a multi-user block acknowledgment frame, and the second field included in the multi-user block acknowledgment frame does not indicate the non-APSTA, the second field being used to indicate non-APSTA information;

[0329] The frame type is a no-data PPDU claim frame, and the third field included in the no-data PPDU claim frame does not indicate the non-AP STA, which is used to indicate non-AP STA information.

[0330] This example allows a non-AP STA to switch to listen mode when it receives a multicast frame that meets any of the conditions in the above set of conditions, and conversely, not to switch to listen mode when it receives a multicast frame that does not meet all of the conditions in the above set of conditions, thus ensuring that multicast frames and subsequent frames can be received in a timely manner.

[0331] Example 2.4:

[0332] Based on Example 2.1 above, the condition set can include the following conditions:

[0333] The frame was sent to an address that is not the address of the AP associated with this non-AP STA;

[0334] The frame type is a broadcast frame, and the target receiving device indicated by the broadcast frame does not include the non-AP STA;

[0335] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the non-AP STA;

[0336] The frame type is a unicast frame, and the receiving address carried by the unicast frame is not the address of the non-AP STA;

[0337] The frame type is a clear send frame, and the receive address carried by the clear send frame is not the address of the AP associated with the non-AP STA.

[0338] This example adds a condition that can cover other multicast frames, allowing a non-AP STA to determine whether to switch to listen mode upon receiving a multicast frame sent to it, thus ensuring that multicast frames and subsequent frames are received in a timely manner.

[0339] The above describes a method for a non-AP STA to determine whether to switch to listening operation mode based on a set of conditions. Optionally, a non-AP STA can also switch to listening operation mode in the following scenarios (or situations or conditions): receiving a second PPDU; if the BSS indicated by the second PPDU is inter-BSS, then switching to listening operation mode (The STA affiliated with the non-AP MLD receives a PPDU and classifies the PPDU as inter-BSSPPDU). It should be noted that this method can also be implemented independently of the method described in Embodiment 1.

[0340] In one possible implementation, if it is determined that the BSS indicated by the first PPDU is an inter-BSS before step S502, then it can be determined to switch to the listening operation mode. In this implementation, step S502 may not be executed.

[0341] Currently, most rules for switching to listen mode are based on MAC layer information, carried in the data portion. However, inter-BSS PPDUs can be identified through the physical layer SIG field. The SIG field is located before the data portion in the PPDU. Therefore, in the above method, by switching to listen mode when an inter-BSS PPDU is detected, it is not necessary to continue parsing the MAC content located in the data portion of the PPDU. This allows for timely switching and helps reduce latency when communicating with the AP using other links.

[0342] Optionally, the non-AP STA can also switch to listening mode in other scenarios (situations or conditions), such as situation one or situation three mentioned above. For details, please refer to the relevant descriptions in the background introduction above, which will not be repeated here.

[0343] In this embodiment, by adding conditions to the condition set that can cover multicast frames other than trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames, a non-AP STA can determine whether to switch to listen mode based on information from other multicast frames during handover. Compared to the prior art, which directly switches to listen mode upon receiving a multicast frame, this embodiment can determine whether to switch to listen mode based on the information of the multicast frame. For example, it switches to listen mode when the received multicast frame meets any condition in the condition set, and does not switch to listen mode when the received multicast frame does not meet all the conditions in the condition set. This improves flexibility and ensures that multicast frames and subsequent frames are received in a timely manner, thus enhancing the rationality of the handover operation.

[0344] Example 1 introduces a technical solution for determining whether to perform a handover operation based on whether conditions in a condition set are met, to ensure that multicast frames and subsequent frames can be received in a timely manner. Example 2 introduces a technical solution for determining whether to perform a handover operation based on whether conditions in a condition set are met, to ensure that multicast frames and subsequent frames can be received in a timely manner. Example 3 introduces another method, which combines the handover rules of SMPS and EMLSR to determine whether to switch to the listening operation mode, to ensure that multicast frames and subsequent frames can be received in a timely manner.

[0345] Example 3:

[0346] like Figure 6 The diagram shown is a flowchart illustrating a communication method provided in an embodiment of this application.

[0347] S601, non-AP STA determines that any condition in the condition set is satisfied.

[0348] The set of conditions includes the following: a multicast frame is received, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the non-AP STA (It receives a group addressed frame but the STA is not a member of this group).

[0349] In one possible implementation, the set of conditions may further include at least one of the following three conditions:

[0350] A trigger frame is received, in which the first field does not indicate the non-AP STA. The first field is used to indicate user information. For example, the first field may be a user information field.

[0351] A multi-user block acknowledgment frame is received, and the second field included in the multi-user block acknowledgment frame does not indicate the non-APSTA. The second field is used to indicate non-APSTA information. For example, the second field can be Per AID TID Info (It receives a Multi-STA BlockAck frame that has none of the Per AID TID Info fields addressed to it);

[0352] A no-data PPDU announcement frame is received, and the third field included in the no-data PPDU announcement frame does not indicate the non-AP STA. The third field is used to indicate non-AP STA information. For example, the third field can be the STA information field.

[0353] In another possible implementation, the set of conditions may further include: receiving a broadcast frame, and the target receiving device indicated by the broadcast frame does not include the non-AP STA.

[0354] The above conditions are the switching rules applicable to EMLSR.

[0355] In addition to the conditions mentioned above, the set of conditions may also include one of the following indicators:

[0356] A unicast frame is received, and the destination address carried by the unicast frame is different from the address of the non-AP STA.

[0357] A frame is received that carries a different transmission address than the frame that initiated the current transmission opportunity (TXOP). Some individually addressed control frames are exclusive, such as BA and BFR.

[0358] The received frame corresponds to a basic service set that is different from the basic service set of the cell where the non-AP STA is located (It receives a PPDU and classifies the PPDU as an inter-BSS PPDU (see 26.2.2 (Intra-BSS and inter-BSS PPDU classification))).

[0359] A multi-user block PPDU is received. This multi-user block PPDU is either an Efficient Multi-User Block PPDU or an Extremely High Throughput Multi-User Block PPDU. The basic service set indicated by this multi-user block PPDU is the same as the basic service set of the cell where the non-AP STA is located. This multi-user block PPDU does not indicate that the non-AP STA is a receiving device. The basic service set disabled subfield carried in the most recently received Efficient Operation element from the AP with which the STA is associated is 0.

[0360] The carrier sense mechanism (see 10.3.2.1 (CS mechanism)) indicates that the medium is idle at the TxPIFS slot boundary (defined in 10.3.7 (DCF timing relations)).

[0361] The above conditions apply to the handover rules for SM PS. By using the above method, the condition set includes both SM PS-based handover rules and EMLSR-based handover rules, thus unifying the rules for EMLSR and SM PS.

[0362] S602, non-AP STA switches to listening operation mode.

[0363] To facilitate understanding of the scheme, three specific examples of condition sets are explained below.

[0364] Example 3.1: A set of conditions may include the following conditions:

[0365] A unicast frame is received, and the destination address carried by the unicast frame is different from the address of the non-AP STA;

[0366] A frame is received, and the sending address carried by this frame is different from the sending address carried by the frame that initiated the current transmission opportunity;

[0367] A frame is received, and the basic service set corresponding to this frame is different from the basic service set of the cell where the non-AP STA is located;

[0368] A multi-user block PPDU is received. This multi-user block PPDU is either an efficient multi-user block PPDU or an ultra-high throughput multi-user block PPDU. The basic service set indicated by this multi-user block PPDU is the same as the basic service set of the cell where the non-AP STA is located. This multi-user block PPDU does not indicate that the non-AP STA is a receiving device. The value of the basic service set prohibition field carried in the efficient operation field most recently received by the non-AP STA is 0.

[0369] A multicast frame was received, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the non-AP STA;

[0370] A trigger frame is received, in which the first field does not indicate the non-AP STA; the first field is used to indicate user information.

[0371] A multi-user block acknowledgment frame is received, and the second field included in the multi-user block acknowledgment frame does not indicate the non-APSTA, the second field being used to indicate non-APSTA information;

[0372] A no-data PPDU claim frame is received, and the third field included in the no-data PPDU claim frame does not indicate the non-AP STA, the third field being used to indicate non-AP STA information;

[0373] The carrier sensing mechanism indicates that the channel has been idle for a preset duration.

[0374] Example 3.2: A set of conditions may include the following conditions:

[0375] A unicast frame is received, and the destination address carried by the unicast frame is different from the address of the non-AP STA;

[0376] A frame is received, and the sending address carried by this frame is different from the sending address carried by the frame that initiated the current transmission opportunity;

[0377] A frame is received, and the basic service set corresponding to this frame is different from the basic service set of the cell where the non-AP STA is located;

[0378] A multi-user block PPDU is received. This multi-user block PPDU is either an efficient multi-user block PPDU or an ultra-high throughput multi-user block PPDU. The basic service set indicated by this multi-user block PPDU is the same as the basic service set of the cell where the non-AP STA is located. This multi-user block PPDU does not indicate that the non-AP STA is a receiving device. The value of the basic service set prohibition field carried in the efficient operation field most recently received by the non-AP STA is 0.

[0379] A multicast frame was received, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the non-AP STA;

[0380] The carrier sensing mechanism indicates that the channel has been idle for a preset duration.

[0381] Example 3.3: A set of conditions may include the following conditions:

[0382] A unicast frame is received, and the destination address carried by the unicast frame is different from the address of the non-AP STA;

[0383] A frame is received, and the sending address carried by this frame is different from the sending address carried by the frame that initiated the current transmission opportunity;

[0384] A frame is received, and the basic service set corresponding to this frame is different from the basic service set of the cell where the non-AP STA is located;

[0385] A multi-user block PPDU is received. This multi-user block PPDU is either an efficient multi-user block PPDU or an ultra-high throughput multi-user block PPDU. The basic service set indicated by this multi-user block PPDU is the same as the basic service set of the cell where the non-AP STA is located. This multi-user block PPDU does not indicate that the non-AP STA is a receiving device. The value of the basic service set prohibition field carried in the efficient operation field most recently received by the non-AP STA is 0.

[0386] A multicast frame was received, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the non-AP STA;

[0387] A broadcast frame is received, and the target receiving device indicated by the broadcast frame does not include the non-AP STA;

[0388] The carrier sensing mechanism indicates that the channel has been idle for a preset duration.

[0389] In the three examples above, the first four conditions and the last condition in the above condition set are switching rules applicable to SM PS, and the remaining conditions are switching rules applicable to EMLSR. In this way, the condition set includes both switching rules based on SM PS and switching rules based on EMLSR, thus unifying the rules of EMLSR and SM PS.

[0390] In this embodiment, by adding SMPS-based handover rules to EMLSR-based handover rules, or vice versa, the EMLSR and SMPS rules can be unified. Furthermore, by adding conditions to the EMLSR-based handover rules that can cover multicast frames other than trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames, non-AP STAs can determine whether to switch to listen mode based on information from other multicast frames during handover operations. Compared to the prior art that directly switches to listen mode upon receiving a multicast frame, this embodiment can determine whether not to switch to listen mode based on the information of the multicast frame. This improves flexibility and ensures that multicast frames and subsequent frames are received promptly, enhancing the rationality of the handover operation.

[0391] The above three embodiments cover multicast frames other than trigger frames, multi-user block acknowledgment frames, and PPDU claim frames without data from the perspective of switching rules, so as to ensure that multicast frames and subsequent frames can be received in a timely manner. The following embodiment four transmits multicast frames in a concentrated time period, which adopts a different switching rule than the time period for transmitting unicast frames, to ensure that multicast frames and subsequent frames can be received in a timely manner.

[0392] Example 4:

[0393] like Figure 7 The diagram shown is a flowchart illustrating a communication method provided in an embodiment of this application.

[0394] S701, non-AP STA, within the first time period, determines whether to switch to listening operation mode according to the first rule.

[0395] The start time of the first time period is either a preset time or the reception time of the first beacon frame, and this first time period is used to receive multicast frames. As an example, the reception time of the first beacon frame can refer to the time when the first beacon frame is completed.

[0396] For example, the preset time can be the transmission time of the first beacon frame that has been acquired in advance. For instance, a non-AP STA can acquire the transmission time of the first beacon frame in the received frame, and thus enter the first time period when that transmission time arrives.

[0397] For example, the first beacon frame may be a transmission service indication beacon frame.

[0398] The AP's behavior during the first time period can be: only allow the transmission of multicast frames.

[0399] As an optional approach, the AP can indicate "transmission incomplete" in every multicast frame before the last multicast frame within the first time period, and indicate "transmission complete" in the last multicast frame within the first time period. For example, the AP can set the "more data" field of the last multicast frame within the first time period to a first value, and set the "more data" field of other multicast frames within the first time period to a second value. The first value can be 0, and the second value can be 1. Alternatively, the first value can be 1, and the second value can be 0.

[0400] Accordingly, the behavior of a non-AP STA during the first time period could be: if the received multicast frame indicates "transmission not complete", continue operating on the link, for example, continue receiving multicast frames on the link; or, determine to switch to listen operation mode according to the first rule.

[0401] The non-AP STA determines whether to switch to listening operation mode based on the first rule, which can be determined in the following way:

[0402] If any condition in the first set of conditions is met, switch to the listening operation mode;

[0403] The first set of conditions includes at least one of the following:

[0404] A multicast frame indicating that transmission is complete has been received.

[0405] If the timer times out, the start time of the timer is the start time of the first time period.

[0406] The total transmission duration of the first AP associated with the non-AP STA, starting from the start time of the first time period, reaches the preset duration.

[0407] S702, during the second time period, the non-AP STA determines whether to switch to the listening operation mode according to the second rule. The start time of this second time period is the reception time of the initial control frame.

[0408] As an example, the reception time of the initial control frame can refer to the time when the initial control frame is completed.

[0409] The AP's behavior during the second time period can be either to allow only unicast frames to be sent, or to allow both unicast and multicast frames to be sent.

[0410] In one possible implementation, the non-AP STA determines to switch to the listening operation mode according to the second rule, specifically according to the method described in Embodiment 1 above. See [link to relevant documentation] for details. Figure 4 The relevant descriptions of the method will not be repeated here.

[0411] In another possible implementation, the non-AP STA determines to switch to the listening operation mode according to the second rule, specifically according to the method described in Embodiment 2 above. For details, please refer to... Figure 5 The relevant descriptions of the method will not be repeated here.

[0412] In another possible implementation, the non-AP STA determines to switch to the listening operation mode according to the second rule, specifically according to the method described in Embodiment 3 above. For details, please refer to... Figure 6 The relevant descriptions of the method will not be repeated here.

[0413] In another possible implementation, the non-AP STA determines to switch to the listening operation mode according to the second rule, such as cases one to three described in the background above.

[0414] As an alternative, the initial control frame can indicate whether the AP will send multicast frames in the second time period.

[0415] One possible implementation of this scheme is that if the initial control frame indicates that the AP will send a multicast frame in the second time period, the non-AP STA can determine to switch to the listening operation mode according to the method described in Embodiment 1, Embodiment 2, or Embodiment 3 above.

[0416] If the initial control frame indicates that the AP will not send multicast frames in the second time period, the non-AP STA can determine whether to switch to listen mode according to the rules for switching to listen mode in the current IEEE 802.11be standard document.

[0417] It should be noted that the first and second time periods have no fixed order; their specific sequence depends on the preset time (or the reception time of the first beacon frame) and the reception time of the initial control frame. Optionally, the first and second time periods can alternate. Figure 8 As shown.

[0418] Optionally, the AP can trigger a non-AP STA to enter the first time period via the first beacon frame. The AP can also trigger a non-AP STA to enter the second time period via the initial control frame.

[0419] In this embodiment of the application, multicast frames are sent to non-AP STAs in a concentrated manner during a specific time period (i.e., the first time period), and this time period adopts different switching rules from the second time period. This ensures that multicast frames and subsequent frames can be received in a timely manner, and also reduces the loss of subsequent transmission opportunities.

[0420] The above embodiments one through four describe a method for switching to a listening operation mode from the perspective of a non-AP STA. In embodiments one through four, the AP can trigger the switch by sending certain frames. For example, in embodiment one, the AP can trigger the non-AP STA to switch to a listening operation mode by sending a frame that does not satisfy any condition of the condition set described in embodiment one. As another example, in embodiment two, the AP can trigger the non-AP STA to switch to a listening operation mode by sending a frame that satisfies any condition of the condition set described in embodiment two. As another example, in embodiment three, the AP can trigger the non-AP STA to switch to a listening operation mode by sending a frame that satisfies any condition of the condition set described in embodiment three. As yet another example, in embodiment four, the AP can trigger the non-AP STA to switch to a listening operation mode by sending a frame that satisfies the first rule in embodiment four during a first time period, and by sending a frame that satisfies the second rule in embodiment four during a second time period.

[0421] Based on the same inventive concept as the method embodiments, this application provides a communication device, the structure of which can be as follows: Figure 9 As shown, it includes a communication module 901 and a processing module 902.

[0422] In one embodiment, the communication device can specifically be used to implement Figure 4 In the embodiments, the method is executed by a non-AP STA. The device can be the non-AP STA itself, or a chip or chipset within the non-AP STA, or a part of the chip used to perform the relevant method functions. The communication module 901 is configured to receive a first PPDU within a first duration, the first PPDU including a first frame. The processing module 902 is configured to: switch to a listening operation mode if the first frame does not satisfy any condition in the condition set; wherein at least one condition in the condition set is frame information of a multicast frame, and the multicast frame is different from a trigger frame, a multi-user block acknowledgment frame, and a no-data PPDU claim frame.

[0423] For example, the at least one condition includes: the frame type is a multicast frame, the multicast frame is different from a broadcast frame, and the receiving device indicated by the multicast frame includes the site.

[0424] For example, the at least one condition includes: the frame type is a broadcast frame, and the broadcast frame carries a sending address that is the address of the access point site associated with the site; or, the frame type is a broadcast frame, and the receiving device indicated by the broadcast frame includes the site.

[0425] Optionally, the broadcast frame is different from the trigger frame, the multi-user block acknowledgment frame, and the no-data PPDU claim frame.

[0426] For example, the set of conditions also includes at least one of the following five conditions:

[0427] The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the site;

[0428] The frame type is a trigger frame, and the trigger frame includes a first field for indicating user information, the first field indicating the site;

[0429] The frame type is a clear send frame, and the receiving address carried by the clear send frame is the address of the access point site associated with the site.

[0430] The frame type is a multi-user block acknowledgment frame, and the multi-user block acknowledgment frame includes a second field for indicating site information, the second field indicating the site;

[0431] The frame type is a no-data PPDU claim frame, and the no-data PPDU claim frame includes a third field for indicating site information, the third field indicating the site.

[0432] Optionally, the communication module 901 is further configured to: receive PPDU; the processing module 902 is further configured to: switch to listening operation if the basic service set indicated by the PPDU is an external basic service set.

[0433] In one embodiment, the communication device can specifically be used to implement Figure 5 In the embodiments, the method is executed by a non-AP STA. The device can be the non-AP STA itself, or a chip or chipset within the non-AP STA, or a part of the chip used to perform the relevant method functions. The communication module 901 is configured to receive a first PPDU within a first duration, the first PPDU including a first frame; the processing module is configured to switch to a listening operation mode if the first frame satisfies any condition in a condition set; wherein the frame type range corresponding to at least one condition in the condition set includes multicast frames, and the multicast frames are different from trigger frames, multi-user block acknowledgment frames, and no-data PPDU claim frames.

[0434] For example, the at least one condition includes at least one of the following three conditions:

[0435] The frame was sent from an address that is not the address of the access point site associated with the site.

[0436] The frame type is a broadcast frame, and the target receiving device indicated by the broadcast frame does not include the station;

[0437] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the site.

[0438] For example, the at least one condition includes at least one of the following two conditions:

[0439] The frame was sent from an address that is not the address of the access point site associated with the site.

[0440] The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the site.

[0441] For example, the set of conditions also includes at least one of the following five conditions:

[0442] The frame type is a unicast frame, and the receiving address carried by the unicast frame is not the address of the site;

[0443] The frame type is a trigger frame, and the first field included in the trigger frame does not indicate the site; the first field is used to indicate user information.

[0444] The frame type is a clear send frame, and the receiving address carried by the clear send frame is not the address of the access point site associated with the site.

[0445] The frame type is a multi-user block acknowledgment frame, and the second field included in the multi-user block acknowledgment frame does not indicate the site; the second field is used to indicate site information.

[0446] The frame type is a no-data PPDU claim frame, and the third field included in the no-data PPDU claim frame does not indicate the site, the third field being used to indicate site information.

[0447] Optionally, the communication module 901 is further configured to receive PPDUs; the processing module 902 is further configured to switch to a listening operation if the basic service set indicated by the PPDU is an external basic service set.

[0448] In one embodiment, the communication device can specifically be used to implement Figure 6In the embodiments, the method is executed by a non-AP STA. The device can be the non-AP STA itself, or a chip or chipset within the non-AP STA, or a part of a chip for performing the relevant method functions. The processing module 902 is configured to determine if any condition in a set of conditions is met; and to switch to a listening operation mode; wherein the set of conditions includes the following conditions: a multicast frame is received, the multicast frame being different from a broadcast frame, and the receiving device indicated by the multicast frame does not include the station.

[0449] For example, the set of conditions also includes at least one of the following three conditions:

[0450] A trigger frame is received, wherein the first field included in the trigger frame does not indicate the site, and the first field is used to indicate user information;

[0451] A multi-user block acknowledgment frame is received, and the second field included in the multi-user block acknowledgment frame does not indicate the site, wherein the second field is used to indicate site information;

[0452] A no-data PPDU claim frame is received, and the third field included in the no-data PPDU claim frame does not indicate the site, the third field being used to indicate site information.

[0453] For example, the set of conditions includes the following conditions: a broadcast frame is received, and the target receiving device indicated by the broadcast frame does not include the site.

[0454] For example, the set of conditions also includes the following conditions:

[0455] A Very High Throughput Multi-User Block (PPDU) is received, wherein the basic service set indicated by the PPDU is the same as the basic service set of the cell where the site is located, the PPDU does not indicate that the site is a receiving device, and the value of the basic service set prohibition field carried in the most recently received high efficiency operation field of the site is 0.

[0456] For example, the set of conditions also includes at least one of the following conditions:

[0457] A unicast frame is received, the destination address carried by the unicast frame is different from the address of the site;

[0458] A frame is received, and the sending address carried by the frame is different from the sending address carried by the frame that initiated the current transmission opportunity;

[0459] A frame is received, and the basic service set corresponding to the frame is different from the basic service set of the cell where the site is located;

[0460] Upon receiving an Efficient Multi-User Block (PPDU), the Basic Service Set (PSS) indicated by the Efficient Multi-User Block (PPDU) differs from the PSS of the cell where the station is located. The Efficient Multi-User Block (PPDU) does not indicate that the station is a receiving device. The value of the PSS prohibition field carried in the most recently received Efficient Operation Field of the station is 0.

[0461] The carrier sensing mechanism indicates that the channel has been idle for a preset duration.

[0462] In one embodiment, the communication device can specifically be used to implement Figure 7 In the embodiments, the method is executed by a non-AP STA. The device can be the non-AP STA itself, or a chip or chipset within the non-AP STA, or a part of a chip used to perform the relevant method functions. Specifically, the processing module 902 is configured to, within a first time period, determine whether to switch to a listening operation mode according to a first rule, wherein the start time of the first time period is a preset time or the reception time of a first beacon frame, and the first time period is used to receive multicast frames; and, within a second time period, determine whether to switch to a listening operation mode according to a second rule, wherein the start time of the second time period is the reception time of an initial control frame.

[0463] Processing module 902, when determining whether to switch to listening operation mode according to the first rule, is specifically used for:

[0464] If any condition in the first set of conditions is met, switch to the listening operation mode;

[0465] The first set of conditions includes at least one of the following:

[0466] A multicast frame indicating that transmission is complete has been received;

[0467] If the timer times out, the start time of the timer is the start time of the first time period;

[0468] The total transmission duration of the first access point site associated with the site, starting from the start time of the first time period, reaches a preset duration.

[0469] For example, the first beacon frame is a transmission service indication map beacon frame.

[0470] The module division in this application embodiment is illustrative and represents only one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules. It is understood that the functions or implementations of the modules in the embodiments of this application can be further described in the relevant descriptions of the method embodiments.

[0471] In one possible approach, the communication device can be as follows: Figure 10 As shown, the device can be a communication device or a chip within a communication device, wherein the communication device can be the terminal device in the above embodiments or the network device in the above embodiments. The device includes a processor 1001 and a communication interface 1002, and may also include a memory 1003. The processing module 902 can be the processor 1001. The communication module 901 can be the communication interface 1002. Optionally, the processor 1001 and the memory 1003 can also be integrated together.

[0472] The processor 1001 can be a CPU, a digital processing module, etc. The communication interface 1002 can be a transceiver, an interface circuit such as a transceiver circuit, or a transceiver chip, etc. The device also includes a memory 1003 for storing the program executed by the processor 1001. The memory 1003 can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory 1003 can be any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited to this.

[0473] The processor 1001 is used to execute the program code stored in the memory 1003, specifically to perform the actions of the aforementioned processing module 902, which will not be described in detail here. The communication interface 1002 is specifically used to perform the actions of the aforementioned communication module 901, which will not be described in detail here.

[0474] This application embodiment does not limit the specific connection medium between the communication interface 1002, processor 1001, and memory 1003. This application embodiment... Figure 10 The memory 1003, processor 1001, and communication interface 1002 are connected via a bus 1004. Figure 10The connections between other components are shown in bold lines only and are not intended to be limiting. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, Figure 10 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0475] This invention also provides a computer-readable storage medium for storing computer software instructions required to execute the processor, including a program required to execute the processor.

[0476] This application also provides a communication system, including methods for implementing... Figure 4 In the embodiments, a communication device for transmitting end function and for implementing Figure 4 The embodiment is a communication device with a receiving end function.

[0477] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0478] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0479] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0480] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0481] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A multi-link-based communication method, characterized in that, The method is applied to the non-access point site side, including: A first physical layer protocol data unit (PPDU) is received within a first duration, the first PPDU including a first frame; If the first frame does not meet all the conditions in the condition set, switch to the listening operation mode; Wherein, at least one condition in the set of conditions is the frame information of a multicast frame, and the multicast frame is different from the trigger frame, the multi-user block acknowledgment frame, and the no-data PPDU claim frame.

2. The method as described in claim 1, characterized in that, The at least one condition includes: The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame includes the site.

3. The method as described in claim 1, characterized in that, The at least one condition includes: The frame type is a broadcast frame, and the broadcast frame carries the address of the access point associated with the site; Alternatively, the frame type is a broadcast frame, and the receiving device indicated by the broadcast frame includes the station.

4. The method as described in claim 3, characterized in that, The broadcast frame is different from the trigger frame, the multi-user block acknowledgment frame, and the no-data PPDU claim frame.

5. The method according to any one of claims 2-4, characterized in that, The set of conditions also includes at least one of the following five conditions: The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the site; The frame type is a trigger frame, and the trigger frame includes a first field for indicating user information, the first field indicating the site; The frame type is a clear send frame, and the receiving address carried by the clear send frame is the address of the access point associated with the site; The frame type is a multi-user block acknowledgment frame, and the multi-user block acknowledgment frame includes a second field for indicating site information, the second field indicating the site; The frame type is a no-data PPDU claim frame, and the no-data PPDU claim frame includes a third field for indicating site information, the third field indicating the site.

6. The method as described in claim 1, characterized in that, The method further includes: Receive the second PPDU; If the basic service set indicated by the second PPDU is an external basic service set, switch to the listening operation mode.

7. A multi-link-based communication device, characterized in that, The device is applied to the non-access point site side and includes: The communication module is configured to receive a first physical layer protocol data unit (PPDU) within a first duration, wherein the first PPDU includes a first frame; The processing module is used to: switch to the listening operation mode if the first frame does not meet all the conditions in the condition set; Wherein, at least one condition in the set of conditions is the frame information of a multicast frame, and the multicast frame is different from the trigger frame, the multi-user block acknowledgment frame, and the no-data PPDU claim frame.

8. The apparatus as claimed in claim 7, characterized in that, The at least one condition includes: The frame type is a multicast frame, which is different from a broadcast frame, and the receiving device indicated by the multicast frame includes the site.

9. The apparatus as claimed in claim 7, characterized in that, The at least one condition includes: The frame type is a broadcast frame, and the broadcast frame carries the address of the access point associated with the site; Alternatively, the frame type is a broadcast frame, and the broadcast frame carries the address of the access point associated with the site.

10. The apparatus as claimed in claim 9, characterized in that, The broadcast frame is different from the trigger frame, the multi-user block acknowledgment frame, and the no-data PPDU claim frame.

11. The apparatus according to any one of claims 8-10, characterized in that, The set of conditions also includes at least one of the following five conditions: The frame type is a unicast frame, and the receiving address carried by the unicast frame is the address of the site; The frame type is a trigger frame, and the trigger frame includes a first field for indicating user information, the first field indicating the site; The frame type is a clear send frame, and the receiving address carried by the clear send frame is the address of the access point associated with the site; The frame type is a multi-user block acknowledgment frame, and the multi-user block acknowledgment frame includes a second field for indicating site information, the second field indicating the site; The frame type is a no-data PPDU claim frame, and the no-data PPDU claim frame includes a third field for indicating site information, the third field indicating the site.

12. The apparatus as claimed in claim 7, characterized in that, The communication module is also used to: receive a second PPDU; The processing module is further configured to: if the basic service set indicated by the second PPDU is an external basic service set, switch to a listening operation.

13. A multi-link-based communication device, characterized in that, Includes a processor for running a set of programs to cause the method as described in any one of claims 1 to 6 to be executed.

14. The apparatus as claimed in claim 13, characterized in that, It also includes a memory that stores programs running on the processor.

15. The apparatus as claimed in claim 13 or 14, characterized in that, The device is a chip or integrated circuit.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions that, when executed on a communication device, cause the method described in any one of claims 1 to 6 to be performed.

17. A computer program product, characterized in that, When the computer program product is run on the sending end, it causes the non-access point site to perform the method described in any one of claims 1 to 6.

Images