Communication method and device
By performing specific monitoring operations on multi-link devices, the problem that the prior art cannot normally receive multicast frames in special scenarios is solved, and higher reception capacity and stability are achieved.
Patent Information
- Application Number
- CN202510270808.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-04-29
- Publication Date
- 2025-06-06
AI Technical Summary
The prior art cannot receive multicast frames normally in some special scenarios, mainly due to the limitations of the frame reception ability.
Multicast frames are received using higher reception capabilities by performing specific monitoring operations on multilink devices (MLDs). The specific method includes the first multilink device performing a first monitoring operation to receive a multicast frame and causing the second multilink device to perform a corresponding monitoring operation by sending information.
It realizes that multicast frames can be received normally in more scenarios, improves reception capabilities, and ensures stable reception performance in special scenarios.
Smart Images

Figure CN120111534A_ABST
Abstract
Description
[0001] This application is a divisional application of the patent application filed on April 29, 2022, with application number 202280093616.0 and application name “Communication Method and Device”. Technical Field
[0002] The present application relates to the field of communications, and more specifically, to a communication method and device. Background Art
[0003] Currently, relevant protocols define multi-link devices (MLD), such as the monitoring operation of non-access point (non-AP) MLD on the EMLSR link. However, the existing monitoring operation is limited by the frame receiving capability and may fail to receive frames normally in some special scenarios. Summary of the invention
[0004] The embodiments of the present application provide a communication method and device, which can realize the reception of multicast frames in more scenarios.
[0005] The present application provides a communication method, including:
[0006] The first multi-link device MLD performs a first monitoring operation, wherein the first monitoring operation is used for a first station on the first MLD to receive a multicast frame using a first receiving capability.
[0007] The present application provides a communication method, including:
[0008] The second multi-link device MLD sends first information, where the first information is used by the first multi-link device MLD to perform a first monitoring operation, where the first monitoring operation is used by a first station on the first MLD to receive a multicast frame using a first receiving capability.
[0009] An embodiment of the present application provides a first multi-link device, including:
[0010] The processing unit is configured to perform a first monitoring operation, wherein the first monitoring operation is used for a first station on the first multi-link device MLD to receive a multicast frame using a first receiving capability.
[0011] An embodiment of the present application provides a second multi-link device, including:
[0012] The sending unit is configured to send first information, where the first information is used for a first multi-link device MLD to perform a first monitoring operation, where the first monitoring operation is used for a first station on the first MLD to receive a multicast frame using a first receiving capability.
[0013] The embodiment of the present application provides a first multi-link device, including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the first multi-link device executes the above method applied to the first multi-link device.
[0014] The embodiment of the present application provides a second multi-link device, including a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the second multi-link device executes the method applied to the second multi-link device.
[0015] An embodiment of the present application provides a chip for implementing the above method applied to the first multi-link device.
[0016] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method applied to the first multi-link device.
[0017] The embodiment of the present application provides a chip for implementing the above method applied to the second multi-link device.
[0018] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method applied to the second multi-link device.
[0019] The embodiment of the present application provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a device, the device executes the method applied to the first multi-link device; or executes the method applied to the second multi-link device.
[0020] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the method applied to a first multi-link device; or execute the method applied to a second multi-link device.
[0021] The embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above method applied to the first multi-link device; or execute the above method applied to the second multi-link device.
[0022] The present application provides a communication system, including:
[0023] A first multi-link device, configured to perform the method as applied to the first multi-link device;
[0024] The second multi-link device is configured to execute the method as applied to the second multi-link device.
[0025] In the embodiment of the present application, the first multi-link device MLD performs the first monitoring operation, so as to achieve reception of multicast frames in more scenarios. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] Figure 1 It is a schematic diagram of an application scenario according to an embodiment of the present application.
[0027] FIG2(A) is a schematic diagram of frame exchange triggered by a MU-RTS trigger frame in the EMLSR mode.
[0028] FIG2(B) is an example of frame exchange triggered by a BSR trigger frame in EMLSR mode.
[0029] Figure 3 It is a schematic flow chart of a communication method 300 according to an embodiment of the present application.
[0030] Figure 4 is a schematic flow chart of a communication method 400 according to another embodiment of the present application.
[0031] Figure 5 It is a schematic block diagram of a first multi-link device 500 according to an embodiment of the present application.
[0032] Figure 6 is a schematic block diagram of a second multi-link device 600 according to an embodiment of the present application.
[0033] Figure 7(A) to Figure 7(F) This is a schematic diagram of the implementation process of the communication method according to the embodiment of the present application in a specific example. Figures 1 to 6 .
[0034] Figure 8 It is a schematic block diagram of a communication device according to an embodiment of the present application.
[0035] Fig. 9 is a schematic block diagram of a chip according to an embodiment of the present application.
[0036] Fig.10 It is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION
[0037] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.
[0038] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless local area network (WLAN), wireless fidelity (WiFi) or other communication systems.
[0039] For example, the communication system 100 used in the embodiment of the present application is as follows: Figure 1 The communication system 100 may include an access point (AP) 110 and a station (STA) 120 accessing the network through the access point 110 .
[0040] In some scenarios, AP is also called AP STA, that is, in a sense, AP is also a STA.
[0041] In some scenarios, STA is also called non-AP STA.
[0042] The communication in the communication system 100 may be communication between an AP and a non-AP STA, communication between a non-AP STA and a non-AP STA, or communication between a STA and a peer STA, wherein a peer STA may refer to a device that communicates with the STA peer, for example, a peer STA may be an AP or a non-AP STA.
[0043] AP is equivalent to a bridge connecting wired network and wireless network. Its main function is to connect various wireless network clients together and then connect the wireless network to Ethernet. AP device can be a terminal device (such as a mobile phone) or a network device (such as a router). The terminal device or network device has a chip that realizes the communication function, such as a WLAN or WiFi chip.
[0044] It should be understood that the role of STA in the communication system is not absolute. For example, in some scenarios, when a mobile phone is connected to a router, the mobile phone is a non-AP STA. When the mobile phone serves as a hotspot for other mobile phones, the mobile phone plays the role of an AP.
[0045] APs and non-AP STAs can be devices used in the Internet of Vehicles, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.
[0046] In some embodiments, the non-AP STA may support the 802.11be standard. The non-AP STA may also support various current and future 802.11 family wireless local area network (WLAN) standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.
[0047] In some embodiments, the AP may be a device supporting the 802.11be standard. The AP may also be a device supporting various current and future 802.11 family WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a.
[0048] In an embodiment of the present application, STA may be a mobile phone, a tablet computer, a computer, a virtual reality (VR) device, an augmented reality (AR) device, a wireless device in industrial control, a set-top box, a wireless device in self-driving, an in-vehicle communication device, a wireless device in remote medical, a wireless device in a smart grid, a wireless device in transportation safety, a wireless device in a smart city or a wireless device in a smart home, a wireless communication chip / ASIC / SOC / etc. that supports WLAN / WiFi technology.
[0049] The frequency bands supported by WLAN technology may include but are not limited to: low frequency bands (eg, 2.4 GHz, 5 GHz, 6 GHz) and high frequency bands (eg, 45 GHz, 60 GHz).
[0050] Figure 1 An AP STA and two non-AP STAs are exemplarily shown. Optionally, the communication system 100 may include multiple AP STAs and other numbers of non-AP STAs, which is not limited in the embodiments of the present application.
[0051] It should be understood that the terms "system" and "network" are often used interchangeably in this article. The term "and / or" in this article is only a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.
[0052] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.
[0053] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.
[0054] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following related technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all belong to the protection scope of the embodiments of the present application.
[0055] First, Enhanced Multi-link Single Radio (EMLSR);
[0056] Related protocols standardize EMLSR operations and provide clearer process specifications for EMLSR operations: non-AP MLD can work in EMLSR mode on a specific subset of the established link set. The links in this specific subset are called EMLSR links.
[0057] The non-AP MLD can monitor the channel status of the EMLSR link through an affiliated station in an awake state working on the EMLSR link. Here, the monitoring operation (referred to as the second monitoring operation in the present application scheme) includes performing a clear channel assessment (CCA) and receiving an initial control frame of a frame exchange sequence sent by the AP MLD, and the initial control frame is sent using a non-high throughput (duplicate) physical layer protocol data unit (non-HT (duplicate) PPDU) with one spatial stream.
[0058] The AP (also referred to as the subordinate AP) attached to the AP MLD initializes frame exchange with the non-AP MLD on one of the EMLSR links, and may transmit an initial control frame to the non-AP MLD to start the frame exchange process. The initial control frame may be a Multiple User Request-To-Send (MU-RTS) trigger frame or a Buffer Status Report Poll (BSRP) trigger frame. For example, as shown in FIG2(A), for the MU-RTS trigger frame, the subordinate AP1 of the AP MLD transmits MU-RTS, and the subordinate STA1 of the non-AP MLD sends CTS after a short interframe space (SIFS) at the end of the transmission. Accordingly, the subordinate AP1 of the AP MLD sends an A-MPDU after a SIFS at the end of the transmission. Finally, the subordinate STA1 of the non-AP MLD sends a block acknowledgment (BlockAck); here, the AP MLD and the non-AP MLD are both in EMLSR mode. As shown in FIG2(B), for the BSRP trigger frame, the subordinate AP1 of the APMLD transmits the BSRP trigger (Trigger) to the subordinate STA1 of the non-AP MLD1, the subordinate STA1 of the non-AP MLD2 to the subordinate STA 1 of the non-AP MLD n, respectively. Correspondingly, the subordinate STA1 of the non-AP MLD, the subordinate STA1 of the non-AP MLD2 to the subordinate STA 1 of the non-AP MLD n respectively perform the frame exchange process until the subordinate STA1 of the non-AP MLD, the subordinate STA1 of the non-AP MLD2 to the subordinate STA 1 of the non-AP MLD n respectively send the EHT TB PPDU 1 with acknowledgement, the EHT TB PPDU 2 with acknowledgement to the EHT TB PPDU n with acknowledgement. Here, the AP MLD and the non-AP MLD are both in the EMLSR mode.
[0059] Here, for the non-AP MLD in EMLSR mode, it is necessary to receive a MU-RTS trigger frame or a BSRP trigger frame, and after receiving the initial control frame of the frame exchange sequence (such as a MU-RTS trigger frame or a BSRP trigger frame), the non-AP MLD can send or receive frames on the link receiving the initial control frame, and shall not send or receive on other links in the EMLSR link until the frame exchange sequence ends. In addition, affected by the spatial stream capability, operation mode, and link switching delay, the non-AP MLD should be able to receive a physical layer protocol data unit (PPDU) sent using multiple spatial streams after a short interframe space (SIFS) after the transmission of the response frame to the initial control frame request ends. During the frame exchange sequence, the AP MLD should not send frames to the non-AP MLD on other links in the EMLSR link. After the frame exchange sequence ends, the non-AP MLD switches back (for example, immediately switches back) to the listening operation on the enabled link.
[0060] Second, the sending and transmission of multilink multicast frames;
[0061] Each subordinate AP attached to the AP MLD (also referred to as the subordinate AP corresponding to the AP MLD, or the AP corresponding to the AP MLD) needs to schedule the sending (i.e., schedule and send) of the cached multicast frame immediately after receiving the Delivery Traffic Indication Map (DTIM) beacon frame, except for the following case, that is, a subordinate TWT scheduling AP (Target Wake Time scheduling AP, TWT scheduling AP) of the AP MLD schedules the sending of the cached multicast frame within the broadcast target wake time (Target Wake Time, TWT) service period within the beacon interval of sending the DTIM beacon frame.
[0062] The subordinate STA (also known as the subordinate station) of the Non-AP MLD needs to follow the following operating rules and receive the multicast buffer unit (BU) sent by the subordinate AP corresponding to the AP MLD associated with the Non-AP MLD on the corresponding link:
[0063] When dot11FMSActivated is false (i.e., Flexible Multicast Service (FMS) is not activated) and ReceiveDTIMs is true (i.e., the attached STA should wake up to receive all DTIM frames), the attached STA needs to wake up in advance so that it can receive every non-STBC DTIM or every STBC DTIM sent by the AP of the Basic Service Set (BSS);
[0064] When dot11FMSActivated is true (i.e., FMS is activated) and ReceiveDTIMs is true (i.e., the attached STA should wake up to receive all DTIM frames), and the attached STA has been authorized by the AP for the alternate delivery interval for the multicast stream, the attached STA needs to wake up before a non-STBC DTIM or STBC DTIM with an FMS Counter field for the specific FMS stream and a current count value of zero.
[0065] If the cached multicast frame indication of a subordinate AP of the AP MLD in the Traffic Indication Map (TIM) element is received by any station to which the non-AP MLD is attached (that is, received by any subordinate station), then the subordinate stations to which the non-AP MLD is attached that are associated with the subordinate AP and remain awake to receive multicast frames need to select to receive all multicast frames scheduled for transmission on the link where the subordinate AP is located.
[0066] Based on the above, it can be known that the monitoring operation of the non-AP MLD working in EMLSR mode on the EMLSR link is defined (referred to as the second monitoring operation in this application scheme). The second monitoring operation includes performing CCA and receiving the initial control frame sent by the AP MLD for initiating frame exchange, for example, including a MU-RTS trigger frame or a BSRP trigger frame.
[0067] The characteristics of the second monitoring operation are: the affiliated sites corresponding to all links in the EMLSR link that are in the awake state of the non-AP MLD are in the monitoring state; and the capability of the second monitoring operation is limited. Except for CCA and the ability to receive initial control frames such as MU-RTS trigger frames or BSRP trigger frames, other types of frames cannot be received normally due to limitations on the modulation and coding scheme (MCS) / rate / spatial stream (SS) / bandwidth (Bandwidth, BW) capabilities.
[0068] Therefore, when the AP MLD supports the EMLSR mode and there is a Non-AP MLD associated with itself and working in the EMLSR mode, if the AP MLD is on the EMLSR link, the subordinate AP directly sends the multicast frame of the video service data with a higher order or more SSs on the corresponding link without sending the MU-RTS control frame first, and the subordinate site (such as subordinate site A) of the non-AP MLD on the link (that is, the link where the subordinate AP sends the multicast frame of the video service data with a higher order or more SSs) is the target receiving site of the multicast frame. At this time, if the Non-AP MLD is in the second listening operation, the subordinate site A cannot correctly receive the multicast frame of the video service data with a higher order or more SSs due to the limitation of the coding rate / MCS / SS / BW processing capability of the received frame.
[0069] Based on this, in order to solve the frame processing problem of non-AP MLD in EMLSR mode, when a station on the EMLSR link directly receives (for example, directly receives without receiving the MU-RTS trigger frame in advance) multicast frames with higher order or more SSs, the present application scheme provides a mechanism for receiving multicast frames. This mechanism can support AP MLD in EMLSR mode to send multicast frames, while ensuring that non-AP MLD can normally receive multicast frames with higher order or more SSs in EMLSR mode. In addition, the present application scheme also proposes the monitoring operation of non-AP MLD in the EMLSR link to meet the reception of multicast frames in special scenarios.
[0070] Figure 3 is a schematic flow chart of a communication method 300 according to an embodiment of the present application. The method may optionally be applied to Figure 1 The system shown in the figure is not limited thereto. The method includes at least part of the following contents.
[0071] S310: A first multi-link device MLD performs a first monitoring operation, wherein the first monitoring operation is used for a first station on the first MLD to receive a multicast frame using a first receiving capability.
[0072] In one embodiment, the first site is a subsidiary site of the first MLD. Specifically, the first site is a site on the first MLD corresponding to the first link, and the first site is used to monitor the first link, that is, the first monitoring operation is used for the first site to be in a monitoring state to monitor the channel state of the first link. Here, the first site can also be called a monitoring site. The first link is a link for sending the multicast frame.
[0073] In one implementation, the first MLD is an MLD operating in an enhanced multi-link single radio EMLSR mode, and accordingly, the first link is a link in an EMLSR link.
[0074] In one implementation, the first MLD is a non-AP MLD. For example, the first MLD is a non-AP MLD operating in EMLSR mode and associated with an AP MLD (such as a second MLD).
[0075] That is to say, S310 specifically means: the non-access point non-AP MLD working in the EMLSR mode performs a first monitoring operation, wherein the first monitoring operation is used for the first station (i.e., the monitoring station) on the non-AP MLD to monitor the first link in the EMLSR link, so that the first station can receive multicast frames through the first link and adopt the first receiving capability. Here, the first link can be a link for sending multicast frames to the AP MLD associated with the non-AP MLD. Here, the AP MLD also works in the EMLSR mode. Furthermore, the access point AP (i.e., the attached AP) on the AP MLD can send multicast frames to the first station attached to the non-AP MLD through the first link.
[0076] For example, the two ends of the link in the EMLSR link correspond to the site on the non-AP MLD and the subordinate AP on the AP MLD respectively; the subordinate AP sends multicast frames through the link, and correspondingly, the site receives multicast frames through the link. In other words, for a site, one site corresponds to one link, and at the same time, it also corresponds to one AP. The AP sends multicast frames through its corresponding link, and correspondingly, the site receives multicast frames through its corresponding link. That is, the site, link, and AP can correspond one to one.
[0077] In one implementation, the first receiving capability is greater than or equal to a second receiving capability; the second receiving capability is a receiving capability used by the first station when the first MLD performs a second monitoring operation. The first receiving capability may be greater than the second receiving capability.
[0078] In a specific example, the first receiving capability is the receiving capability under the EMLSR mode, that is, the first receiving capability is the receiving capability of the first site affiliated with the first MLD under the EMLSR mode, and accordingly, the second receiving capability is also the receiving capability under the EMLSR mode, that is, the second receiving capability is the receiving capability of the first site affiliated with the first MLD under the EMLSR mode.
[0079] In one implementation, the first receiving capability includes at least one of the following: a first rate, a first modulation and coding strategy MCS, a first spatial stream SS, and a first bandwidth BW.
[0080] In another embodiment, the second receiving capability includes at least one of the following: a second rate, a second modulation and coding strategy MCS, a second spatial stream SS and a second bandwidth BW; the second receiving capability is the receiving capability of the first station under the second monitoring operation.
[0081] Here, the first rate is greater than or equal to the second rate; the first MCS is better than or equal to the second MCS; the first SS is greater than or equal to the second SS; and the first BW is greater than or equal to the second BW.
[0082] It should be noted that the present application does not limit the number of parameters included in the first receiving capability (or the second receiving capability), for example, it can be one, two, or more of the above parameters. Accordingly, the parameters included in the first receiving capability and the parameters included in the second receiving capability can be the same or different; the number of parameters included in the first receiving capability and the number of parameters included in the second receiving capability can be the same or different, and the present application does not limit this.
[0083] It can be understood that if at least one parameter in the first receiving capability (at least one of the above parameters) is greater than the parameter corresponding to the second receiving capability, the first receiving capability can be considered to be greater than the second receiving capability. For example, the first rate included in the first receiving capability is greater than the second rate included in the second receiving capability. At this time, if the first receiving capability also includes other parameters, even if the other parameters included in the first receiving capability are equal to the corresponding parameters included in the second receiving capability, the first receiving capability can be considered to be greater than or superior to the second receiving capability. For example, the first SS included in the first receiving capability is equal to the second SS included in the second receiving capability. At this time, since the first rate included in the first receiving capability is greater than the second rate included in the second receiving capability, the first receiving capability can still be considered to be greater than the second receiving capability.
[0084] In one embodiment, all parameters included in the first receiving capability are greater than (or better than) the parameters corresponding to the second receiving capability. In this way, it is ensured that multicast frames in more scenarios can be received. Specifically, since the first station on the first MLD has the first receiving capability (or is called a better first receiving capability), even without receiving the initial control frame in advance, such as the MU-RTS trigger frame, it is still possible to receive multicast frames sent with higher capabilities, for example, it is still possible to receive multicast frames sent by the second MLD with a higher rate, or a higher MCS (also called a better MCS), or a higher BW, or more SS.
[0085] In one implementation, in the first monitoring operation, only the first station on the first MLD is in a monitoring state, and other stations on the first MLD cannot enter the monitoring state, that is, do not have the ability to receive or send frames.
[0086] Alternatively, in another embodiment, the first MLD also includes a second site; the first monitoring operation is also used for the second site to monitor the second link in the EMLSR link (that is, the second site is in a monitoring state), and the second link is a link in the EMLSR link other than the first link; further, the second site also has the first receiving capability. That is to say, when the first site has the first receiving capability under the first monitoring operation, the second site on the first MLD can also be in a monitoring state to monitor other links except the first link; at this time, the second site can also have the first receiving capability.
[0087] Specifically, when the first multi-link device MLD performs the first listening operation and the first multi-link device MLD maintains to perform the first listening operation, the first listening operation is also used for the second site to listen to the second link in the EMLSR link, the second site is a site on the first MLD, and the second link is a link in the EMLSR link other than the first link; or, when the first multi-link device MLD performs the first listening operation and the first multi-link device switches from the second listening operation to the first listening operation, the first listening operation makes it impossible for the second site to listen.
[0088] It is understandable that, in this implementation, when the first site has the first receiving capability under the first listening operation, the second site in the awake state on the first MLD may be one or more, and the present application does not impose any restrictions on this. For example, when the first site has the first receiving capability under the first listening operation, all second sites in the awake state on the first MLD may be in the listening state, and all second sites have the first receiving capability. It is understandable that, in this case, the receiving capabilities of the first site and the second site may also be different, for example, the second site has the second receiving capability, or other receiving capabilities, and the present application does not impose any restrictions on this. As long as the first site is in the first receiving capability and can normally receive multicast frames, it falls within the protection scope of the present application.
[0089] For example, the first monitoring operation (that is, the first monitoring operation in the EMLSR mode) may specifically refer to: on the non-AP MLD working in the EMLSR mode, the affiliated site (referred to as the monitoring site, such as the first site) corresponding to a specific link (such as the first link) in the EMLSR link can receive multicast frames sent at a higher rate / higher MCS / more SSs / higher BW.
[0090] It is worth noting that the higher rate / higher MCS / more SS / higher BW described in the present application solution refers to: at least one or more of higher rate, higher MCS, more SS and higher BW; that is, at least one of them.
[0091] Furthermore, there are two situations in which the non-AP MLD enters the first monitoring operation in the EMLSR mode:
[0092] Case 1: Under the first monitoring operation, the subsidiary site (such as the first site) can enter the monitoring state corresponding to the frame exchange processing of the specific link (such as the first link) in the EMLSR link; that is, under the first monitoring operation, the frame receiving capability (also referred to as the frame processing capability) of the subsidiary site (such as the first site) corresponding to the specific link (such as the first link) is consistent with the ability of the specific link to perform frame exchange processing, that is, it can receive multicast frames sent with a higher rate / higher MCS / more SS / higher BW. Moreover, in this state, other links in the EMLSR link except the specific link (such as the first link) cannot be monitored, that is, other links except the specific link cannot send or receive frames. For example, in this case, the transceiver capability in the EMLSR link (such as the transceiver capability of other sites in the EMLSR link) can be merged into the first site by switching and merging the links, so that the first site has a stronger first receiving capability.
[0093] Case 2: Under the first monitoring operation, the subsidiary site (such as the first site) where the specific link (such as the first link) in the EMLSR mode is located has the ability to receive multicast frames sent at a higher rate / higher MCS / higher BW / more SSs, so all the subsidiary sites (such as the second site) in the EMLSR link that are in an awake state can be kept in a listening state. At this time, the subsidiary site (such as the second site) in the awake state may have the same receiving capability as the first site, or it may be different. The present application does not impose any restrictions on this. As long as the first site has the ability to receive multicast frames sent at a higher rate / higher MCS / higher BW / more SSs, it belongs to the protection scope of the present application. It can be understood that since the link is not switched and merged in this case, the receiving capability of the first site at this time may be weaker than the receiving capability after the link is switched and merged.
[0094] In one embodiment, the second monitoring operation is used for the target site on the first MLD (that is, the subsidiary site of the first MLD) to monitor the link corresponding to the target site, wherein the target site is a site in an awake state on the first MLD, and the target site has the second receiving capability, such as the second receiving capability includes at least one of the following: performing a clear channel assessment CCA, and receiving an initial control frame for initiating a frame exchange. For another example, when there are two or more target sites in an awake state on the first MLD, at this time, the second monitoring operation can enable the two or more target sites on the first MLD to have the second receiving capability. That is to say, under the second monitoring operation, the subsidiary sites in an awake state on the first MLD, such as one, or more, or all the subsidiary sites in an awake state, can be in a monitoring state, and the subsidiary sites in the monitoring state have a second receiving capability, such as a lower second receiving capability relative to the first receiving capability.
[0095] For example, the second listening operation (that is, the first listening operation in EMLSR mode) may specifically refer to: on the non-AP MLD working in EMLSR mode, all affiliated sites (that is, target sites) in the awake state corresponding to the EMLSR link are in the listening state; wherein, the receiving capability of each site corresponding to the EMLSR link, that is, the second receiving capability, is limited. Except for being able to receive initial control frames such as CCA or MU-RTS trigger frames, other types of frames cannot be received correctly due to limitations on capabilities such as rate / MCS / SS / BW.
[0096] In one embodiment, the first MLD receives the multicast frame through the first station using the first receiving capability. Further, the multicast frame received using the first receiving capability is carried by a physical layer protocol data unit PPDU, and the PPDU includes at least one of the following:
[0097] Orthogonal frequency division multiplexing OFDM physical layer protocol data unit PPDU;
[0098] Non-HT duplicate DUP PPDU;
[0099] Very high throughput VHT PPDU;
[0100] High throughput HT PPDU;
[0101] High efficiency HE single user SU PPDU;
[0102] PPDUs supported by very high throughput EHT site STAs including very high throughput EHT multi-user MU PPDU.
[0103] For example, a non-AP MLD working in EMLSR mode can receive a PPDU sent with a higher rate / higher MCS / more spatial streams (SS) / higher BW at an affiliated site (such as the first site) corresponding to a specific link (i.e., the first link) in the EMLSR link. Here, the PPDU can be at least one of the following: OFDM PPDU, non-HT DUP PPDU, VHTPPDU, HT PPDU, HE SU PPDU, and a PPDU supported by an EHT STA including EHT MU PPDU. In this way, it is ensured that the non-AP MLD can correctly receive a PPDU that uses at least one of the following parameters and carries a multicast frame. The parameters include: higher rate, higher MCS, more SS, and higher BW.
[0104] In one embodiment, when the multicast frame is received, the first MLD switches from the first listening operation to the second listening operation. For example, when the multicast frame is received, the non-AP MLD confirms the completion of the multicast frame reception based on the indication, or when the multicast frame is sent in the broadcast TWT service period or the multicast with retries (Groupcast With Retries, GCR) service period, the non-AP MLD switches from the first listening operation in the EMLSR mode to the second listening operation in the EMLSR mode when the end time point of the broadcast TWT service period or the GCR service period SP is reached and there is no multicast frame being received.
[0105] In the solution of the present application, the first multi-link device MLD may perform the first monitoring operation in the following ways:
[0106] Mode 1: The first MLD performs the first monitoring operation based on the first information; that is, S310 is specifically: the first MLD performs the first monitoring operation based on the first information. Further, the first information is used by the first MLD to perform the first monitoring operation at a target time or before a target time. That is, S310 is specifically: the first MLD performs the first monitoring operation at a target time or before a target time based on the first information.
[0107] It can be understood that, in one example, the first information includes a target time, in which case the first information is used for the first MLD to perform the first monitoring operation at the target time or before the target time included in the first information. Alternatively, in another example, the first information does not include a target time, in which case the target time is pre-received by the first MLD, in which case the first information is used for the first MLD to perform the first monitoring operation at the pre-acquired target time or before the target time. The present application does not impose any restriction on whether the target time is carried in the first information, as long as the first information enables the first MLD to perform the first monitoring operation at the target time or before the target time, it falls within the protection scope of the present application.
[0108] In one embodiment, step S310 specifically includes: the first multi-link device MLD switches from the second listening operation to the first listening operation; or, the first multi-link device MLD maintains executing the first listening operation. Further, step S310 specifically includes: the first multi-link device MLD switches from the second listening operation to the first listening operation based on the first information; or, the first multi-link device MLD maintains executing the first listening operation based on the first information.
[0109] In one implementation, the target time in the first embodiment includes a first time point, and the first time point may specifically include at least one of the following:
[0110] (1) Expected multicast frame sending time point. At this time, the first MLD performs the first monitoring operation at the expected multicast frame sending time point, or at a time point before the expected multicast frame sending time point; here, the expected multicast frame sending time point can be any pre-agreed time point, and the present application scheme does not limit this.
[0111] (2) Target Beacon Transmission Time (TBTT) of the expected transmission traffic indication DTIM beacon frame; Here, the expected multicast frame transmission time point is later than the TBTT of the DTIM beacon frame. At this time, the first MLD performs the first monitoring operation at the TBTT of the expected DTIM beacon frame or at a time point before the TBTT of the expected DTIM beacon frame.
[0112] (3) The start time of the broadcast target wake-up time TWT service period SP for sending the expected multicast frame; Here, the expected multicast frame sending time point is within the TWT service period SP. At this time, the first MLD performs the first monitoring operation at the start time of the broadcast target wake-up time TWT service period SP for sending the expected multicast frame, or at a time point before the start time.
[0113] (4) The TBTT of a non-STBC DTIM beacon frame whose current count value of the FMS counter field of a specific flexible multicast service FMS stream is zero; here, the expected multicast frame sending time point is later than the TBTT of a non-STBC DTIM beacon frame whose current count value of the FMS counter field of the FMS stream is zero. At this time, the first MLD performs the first monitoring operation at the TBTT of a non-STBC DTIM beacon frame whose current count value of the FMS counter field of the specific FMS stream is zero, or at a time point before the TBTT of a non-STBC DTIM beacon frame whose current count value of the FMS counter field of the specific FMS stream is zero.
[0114] (5) the start time of the multicast GCR service period with retry for sending multicast frames; here, the expected multicast frame sending time point is within the GCR service period. At this time, the first MLD performs the first monitoring operation at the start time of the multicast GCR service period with retry for sending multicast frames, or at a time point before the start time.
[0115] For example, a non-AP MLD operating in the EMLSR mode performs a first listening operation at the expected multicast frame sending time point, or before the expected multicast frame sending time point, to monitor the link (i.e., the first link) where the multicast frame is scheduled to be sent in the EMLSR link. For example, a non-AP MLD operating in the EMLSR mode performs a first listening operation in advance before the expected multicast frame sending time point, to monitor the link (i.e., the first link) where the multicast frame is scheduled to be sent in the EMLSR link. Furthermore, a non-AP MLD operating in the EMLSR mode can receive multicast frames through the first link while performing the first listening operation, and switch to the second listening operation after confirming that the multicast frame has been received. That is, when the non-AP MLD is associated with an AP MLD that supports the EMLSR mode, and the non-AP MLD operates in the EMLSR mode on the EMLSR link, if a multicast frame is scheduled to be transmitted on a link (for example, the first link) in the EMLSR link corresponding to the non-AP MLD, and a site (set as site A, i.e., the first site) on the link (for example, the first link) on the non-AP MLD is ready to receive the multicast frame, the non-AP MLD needs to ensure that it enters the first listening operation in advance at or before the expected multicast frame sending time point, so that site A listens to the link (i.e., the first link) that transmits the multicast frame, so as to correctly receive the multicast frame.
[0116] Further, for the sender of the multicast frame, the method for the AP MLD's subordinate AP to schedule the sending of the cached multicast frame may adopt at least one of the following:
[0117] (1) The AP affiliated with the AP MLD schedules the sending of the cached multicast frame at the expected multicast frame sending time point; here, the expected multicast frame sending time point may be any pre-agreed time point, and the present application solution does not impose any limitation on this.
[0118] (2) The AP affiliated with the AP MLD schedules the sending of the buffered multicast frame after sending the DTIM beacon frame (beacon); for example, the AP schedules the sending of the buffered multicast frame after each DTIM beacon frame (beacon).
[0119] (3) The subordinate APs of the AP MLD schedule the sending of multicast frames within the broadcast TWT service period SP; for example, one of the subordinate APs of the AP MLD is a TWT scheduling AP (TWT scheduling AP), and the TWT scheduling AP schedules the sending of cached multicast frames within the broadcast TWT service period SP during the beacon interval where the DTIM beacon frame is sent.
[0120] (4) Using a specific flexible multicast service FMS to send the cached multicast frame; for example, scheduling the sending of the cached multicast frame at a time point after the TBTT of a non-STBC DTIM beacon frame whose current count value in the FMS counter field of the specific flexible multicast service FMS flow is zero.
[0121] (5) Using GCR to send cached multicast frames. For example, within the GCR service period, the cached multicast frames are scheduled to be sent.
[0122] For example, when the AP MLD schedules the sending of the cached multicast frame through a certain link (such as the first link) in the EMLSR link after the DTIM beacon frame, the non-AP MLD working in the EMLSR mode will first enter the first monitoring operation of the link where the multicast frame is scheduled to be sent (such as the first link) at or before the expected DTIM beacon frame TBTT, that is, perform the first monitoring operation at or before the expected DTIM beacon frame TBTT to monitor the link where the multicast frame is scheduled to be sent (that is, the first link). Subsequently, after receiving the DTIM beacon frame, the non-AP MLD working in the EMLSR mode maintains the first monitoring operation for the link where the multicast frame is scheduled to be sent (such as the first link) (that is, maintains the frame exchange operation state), that is, maintains the first monitoring operation to maintain monitoring of the link where the multicast frame is scheduled to be sent (such as the first link) until the reception of the multicast frame is completed. Furthermore, when the non-AP MLD receives an indication, for example, the More Data subfield of the multicast frame sent by the AP of the first link is 0, it confirms that there are no more multicast frames. At this time, it returns from the first monitoring operation (also called frame exchange operation) to the second monitoring operation in EMLSR mode.
[0123] For another example, when the AP MLD schedules the sending of cached multicast frames within the broadcast TWT service period or the GCR service period, the non-AP MLD working in the EMLSR mode will first enter the first listening operation of the link where the multicast frame is scheduled to be sent (such as the first link) in advance at or before the start time of the expected broadcast TWT service period or the GCR service period for the scheduled sending of the multicast frame, that is, enter the first listening operation in advance to monitor the link where the multicast frame is scheduled to be sent (such as the first link). Subsequently, after receiving the DTIM beacon frame, the non-AP MLD working in the EMLSR mode maintains the first listening operation for the link where the multicast frame is scheduled to be sent (such as the first link) (that is, maintains the frame exchange operation state), that is, maintains the first listening operation to maintain monitoring of the link where the multicast frame is scheduled to be sent (such as the first link) until the reception of the multicast frame is completed. Further, when the non-AP MLD receives an indication confirming that there is no multicast frame (i.e., the multicast frame has been received), the non-AP MLD returns from the first listening operation (i.e., the frame exchange operation) to the second listening operation under the EMLSR mode; or, when the end time point of the broadcast TWT service period or the GCR service period (SP) is reached and there is no multicast frame being received, it returns from the first listening operation to the second listening operation under the EMLSR mode.
[0124] In one embodiment, the first time point is pre-received by the first MLD; specifically, the first time point is pre-received by the first MLD from the associated second MLD; more specifically, the first time point is pre-received by the non-AP MLD from the associated AP MLD, for example, received before S310, to ensure that the first MLD performs the first monitoring operation in advance before the expected multicast frame is sent, so that the first site monitors the link where the multicast frame is scheduled to be sent in the EMLSR link.
[0125] Method 2: The first information is a transmission traffic indication map DTIM beacon frame, and the DTIM beacon frame is used by the first MLD to perform the first monitoring operation at a target time or before a target time. Further, the difference from method 1 is that in method 2, the target time includes a second time point, that is, the DTIM beacon frame is used by the first MLD to perform the first monitoring operation at a second time point or before the second time point.
[0126] It can be understood that, in one example, the DTIM beacon frame may include a target time (such as a second time point), that is, carry the target time. In this case, the DTIM beacon frame is used for the first MLD to perform the first listening operation at the target time or before the target time carried by the DTIM beacon frame. Alternatively, in another example, the DTIM beacon frame does not include a target time, that is, does not carry a target time; in this case, the target time is pre-received by the first MLD, and further, the DTIM beacon frame is used for the first MLD to perform the first listening operation at the pre-acquired target time or before the target time. The present application scheme does not impose any restrictions on whether the target time is carried in the DTIM beacon frame. As long as the DTIM beacon frame enables the first MLD to perform the first listening operation at the target time or before the target time, it belongs to the protection scope of the present application scheme.
[0127] In one embodiment, the first MLD performs the second listening operation before the TBTT of the DTIM beacon frame to be transmitted, that is, the second listening operation is performed by the first MLD before the target beacon sending time TBTT of the DTIM beacon frame to be transmitted. Furthermore, the first MLD performs the first listening operation based on the first information, which may specifically include: the first MLD switches from the second listening operation to the first listening operation at or before the second time point. That is to say, in the second method, the first MLD first performs the second listening operation before the TBTT of the DTIM beacon frame to be transmitted, receives the DTIM beacon frame in the case of the second listening operation, and then switches from the second listening operation to the first listening operation at or before the second time point, so that the first site of the first MLD switches from having a lower second receiving capability to having a higher first receiving capability, thereby ensuring that the first site of the first MLD can normally receive multicast frames.
[0128] Further, the second time point includes: an expected multicast frame sending time point after receiving the DTIM beacon frame; here, the DTIM beacon frame is received by the first MLD under the second monitoring operation. That is to say, the expected multicast frame sending time point is after the time point of sending the DTIM beacon frame. At this time, the first MLD first receives the DTIM beacon frame and performs the first monitoring operation at the expected multicast frame sending time point after receiving the DTIM beacon frame, or before the expected multicast frame sending time point after receiving the DTIM beacon frame. It can be understood that the first monitoring operation can be performed at the time point when the first MLD receives the DTIM beacon frame.
[0129] For example, when a non-AP MLD working in EMLSR mode is preparing to receive a multicast frame on a link in the EMLSR link, it can first enter the second listening operation before the TBTT of the DTIM beacon frame. And after receiving the DTIM beacon frame and before the expected time point of the multicast frame scheduling and sending, it switches from the second listening operation to the first listening operation, so that the first site of the first MLD monitors the link (such as the first link) where the multicast frame is scheduled to be sent in the EMLSR link. Here, under the first listening operation, the first site has the first receiving capability, so that it is ensured that the multicast frame can be received normally. Further, under the first listening operation, the non-AP MLD receives the multicast frame through the first site until the reception of the multicast frame is completed. If the non-AP MLD receives an indication to confirm that there are no more multicast frames, it can be considered that the reception is complete. Subsequently, the first listening operation (that is, the frame exchange operation) is returned to the second listening operation.
[0130] It can be understood that after the AP MLD sends the DTIM beacon frame on the EMLSR link and before the starting time point for scheduling the sending of the multicast frame, it is necessary to reserve sufficient time. In this way, it can be ensured that the non-AP MLD associated with the AP MLD working in the EMLSR mode switches to the first listening operation of the link (such as the first link) where the multicast frame is scheduled to be sent in the EMLSR link after receiving the DTIM beacon frame and at the time point when the multicast frame is sent or before the time point when the multicast frame is sent.
[0131] Mode three: The first information is determined based on the first indication; the first indication is used to indicate whether to perform the first listening operation when a multicast frame needs to be received. For example, the first indication is specifically used to indicate whether to perform the first listening operation when a multicast frame needs to be received, or to indicate that the first listening operation does not need to be performed when a multicast frame needs to be received. Furthermore, in this mode three, the first indication can be expressed in the following two ways, including:
[0132] First way:
[0133] The first indication is used to uniformly indicate whether the first MLD corresponding to the access point AP performs the first monitoring operation when it needs to receive a multicast frame; here, the access point AP is the AP corresponding to the second MLD associated with the first MLD; the AP corresponding to the second MLD includes at least one of the following: an affiliated AP of the second MLD, an AP referred to by a BSSID in a multiple Basic Service Set Identifier set (multiple BSSID set) in which the affiliated AP of the second MLD is located.
[0134] For example, the first MLD corresponding to the access point AP can be specifically: the first MLD corresponding to the first site corresponding to the access point AP; it can be understood that the link, such as the two ends of the link in the EMLSR link, respectively correspond to the first site on the first MLD and the access point AP corresponding to the second MLD, and the site, link and AP can correspond one to one. Based on this, the site corresponds to the access point AP, and the site corresponds to the first MLD.
[0135] It should be noted that the first indication does not carry a target time, for example, does not carry a first time point, and the purpose of the first indication is to indicate whether a first listening operation needs to be performed when multicast needs to be received. Based on this, the first time point may be acquired in advance by the first MLD through other means, and the present application does not impose specific restrictions on this. Alternatively, in another case, the first indication not only indicates whether a first listening operation needs to be performed when multicast needs to be received, but also carries a target time, such as the first time point. In this case, the first MLD does not need to acquire the first time point in advance. In actual applications, the above two methods can be executed one by one, and the present application does not impose any restrictions.
[0136] In one implementation, when the value of the first indication is a first value (such as 1), it is used to uniformly indicate the first MLD corresponding to the access point AP to perform the first monitoring operation when a multicast frame needs to be received;
[0137] Alternatively, when the value of the first indication is a second value (such as 0), it is used to uniformly indicate that the first MLD corresponding to the access point AP does not need to perform the first monitoring operation when a multicast frame needs to be received.
[0138] In one implementation, the first indication is carried by an EMLSR operation indication element. Further, the first indication is carried by a first field in the EMLSR operation indication element.
[0139] In one implementation, the first field includes a second indication; when the value of the second indication is a third value (for example, 1), the first field includes the first indication.
[0140] In one embodiment, the first field is an EMLSR operation indication bitmap control. The first indication is an EMLSR operation unified indication. Further, the second indication is an EMLSR operation unified indication existence; wherein the EMLSR operation unified indication existence is used to indicate whether the first field (i.e., the EMLSR operation indication bitmap control) includes an EMLSR operation unified indication.
[0141] It can be understood that, in actual applications, the EMLSR operation indication element may also include other fields, and the present application does not impose any specific restrictions on the included fields.
[0142] For example, Table 1 is an example of the fields (also referred to as fields) included in the EMLSR operation indication element in the first case; Table 2 is an example of the indications included in the EMLSR operation indication bitmap control in the first case.
[0143]
[0144] Table 1
[0145]
[0146] Table 2
[0147] As shown in Table 1, the EMLSR operation indication element includes an element ID, a length, and an element ID extension; here, the element ID, length, and element ID extension all occupy 1 byte, and the specific definition may be similar to that in the relevant standards.
[0148] Furthermore, the EMLSR operation indication element also includes an EMLSR operation indication bitmap control (EMLSROperation Indicator Bitmap Control), which also occupies 1 byte.
[0149] As shown in Table 2, the EMLSR operation indication bitmap control includes the presence of an EMLSR unified operation indication (EMLSROperation for ALL Indicator Present). When the value of the EMLSR unified operation indication present is 1, the EMLSR operation indication bitmap control also includes: an EMLSR unified operation indication (EMLSR Operation for ALL Indicator) and a reservation (Reserved). Here, the EMLSR unified operation indication present, the EMLSR unified operation indication and the reservation occupy 1 bit, 1 bit and 6 bits respectively. Based on this, the EMLSR unified operation indication present, the EMLSR unified operation indication and the reservation included in the EMLSR operation indication bitmap control occupy a total of one byte.
[0150] Here, the unified indication of EMLSR operation (or the unified indication domain of EMLSR operation, i.e., the first indication) is used to uniformly indicate whether the non-AP MLD corresponding to the AP and working in the EMLSR mode performs a first monitoring operation when a multicast frame needs to be received, and the first monitoring operation is used for the first station corresponding to the AP on the non-AP MLD to have a first receiving capability, so that the first station monitors the link where the AP is located. That is, the unified indication of EMLSR operation is used to uniformly indicate whether the non-AP MLD corresponding to the AP and working in the EMLSR mode performs a first monitoring operation with a receiving capability of a higher rate / higher MCS / more SSs / higher BW (i.e., the first receiving capability) and the link where the AP is located (e.g., the first link) when a multicast frame needs to be received.
[0151] The AP is at least one of the following: an AP affiliated with the AP MLD, an AP indicated by a BSSID in a multiple BSSID set where the AP affiliated with the AP MLD is located. The non-AP MLD is associated with the AP MLD.
[0152] It can be understood that the non-AP MLD corresponding to the AP working in the EMLSR mode can specifically be: the non-AP MLD working in the EMLSR mode corresponding to the site (such as the first site) corresponding to the AP.
[0153] Furthermore, when the EMLSR operation unified indication value is 1, it indicates that the non-AP MLD corresponding to the AP working in the EMLSR mode, when it is necessary to receive multicast frames, performs the first listening operation with a receiving capability of higher rate / higher MCS / more spatial streams (SS) / higher BW (that is, the first receiving capability) and the link where the AP is located (such as the first link).
[0154] When the EMLSR operation unified indication value is 0, it means that the non-AP MLD corresponding to the AP working in the EMLSR mode does not need to perform the first listening operation of the link where the AP is located (such as the first link) with a higher rate / higher MCS / more spatial streams (SS) / higher BW receiving capability (that is, the first receiving capability) when receiving multicast frames.
[0155] In one embodiment, the EMLSR operation indication element is carried by a management frame. In this case, the first information may be specifically a management frame. Further, the first MLD receives the management frame. Specifically, before S310, the first MLD receives the management frame. For example, the first MLD receives the management frame sent by the second MLD, so that it is convenient to perform the first monitoring operation based on the management frame; here, in one example, the management frame includes a traffic indication map TIM beacon frame.
[0156] Second way:
[0157] The position of each bit in the first indication is used to indicate an access point AP;
[0158] The value of each bit in the first indication is used to indicate whether the first MLD corresponding to the access point AP performs the first monitoring operation when a multicast frame needs to be received.
[0159] Here, the access point AP is the AP corresponding to the second MLD associated with the first MLD; the AP corresponding to the second MLD includes at least one of the following: an affiliated AP of the second MLD, and an AP indicated by a BSSID in a multi-BSSID set where the affiliated AP of the second MLD is located.
[0160] For example, the first MLD corresponding to the access point AP can be specifically: the first MLD corresponding to the first site corresponding to the access point AP; it can be understood that the link, such as the two ends of the link in the EMLSR link, respectively correspond to the first site on the first MLD and the access point AP corresponding to the second MLD, and the site, link and AP can correspond one to one. Based on this, the site corresponds to the access point AP, and the site corresponds to the first MLD.
[0161] It should be noted that the first indication does not carry a target time, for example, does not carry a first time point, and the purpose of the first indication is to indicate whether a first listening operation needs to be performed when multicast needs to be received. Based on this, the first time point may be acquired in advance by the first MLD through other means, and the present application does not impose specific restrictions on this. Alternatively, in another case, the first indication not only indicates whether a first listening operation needs to be performed when multicast needs to be received, but also carries a target time, such as the first time point. In this case, the first MLD does not need to acquire the first time point in advance. In actual applications, the above two methods can be executed one by one, and the present application does not impose any restrictions.
[0162] In one implementation, when the value of each bit in the first indication is a fourth value (such as 1), it is used to instruct the first MLD corresponding to the access point AP to perform the first monitoring operation when a multicast frame needs to be received;
[0163] Alternatively, when the value of each bit in the first indication is the fifth value (such as 0), it is used to indicate that the first MLD corresponding to the access point AP does not need to perform the first monitoring operation when it needs to receive a multicast frame.
[0164] In one implementation, the first indication is carried by an EMLSR operation indication element. Further, the first indication is carried by a second field in the EMLSR operation indication element.
[0165] In one implementation, the second field is a partial EMLSR operation indication bitmap; the partial EMLSR operation indication bitmap is formed by intercepting a portion of continuous bits in the EMLSR operation indication bitmap.
[0166] In one embodiment, the EMLSR operation indication element includes a first field; wherein, when the value of the second indication in the first field is a sixth value (for example, 0), the first field includes a third indication; the third indication is used to indicate the position of a portion of continuous bits intercepted from the EMLSR operation indication bitmap. In one embodiment, the third indication is a bitmap offset, so that the portion of the EMLSR operation indication bitmap can be intercepted from the EMLSR operation indication bitmap based on the bitmap offset.
[0167] In one embodiment, the first field is an EMLSR operation indication bitmap control. The first indication is an EMLSR operation unified indication. Further, the second indication is the existence of an EMLSR operation unified indication; wherein the existence of the EMLSR operation unified indication is used to indicate whether the first field (i.e., the EMLSR operation indication bitmap control) includes an EMLSR operation unified indication. For example, when the value of the EMLSR operation unified indication existence is a third value (such as 1), the EMLSR operation indication bitmap control includes the EMLSR operation unified indication, and at this time, it may also include a reservation. In this case, the EMLSR operation unified indication is used to uniformly indicate whether the corresponding first MLD needs to perform the first listening operation. Further, when the value of the EMLSR operation unified indication existence is a sixth value (such as 0), the EMLSR operation indication bitmap control includes the bitmap offset. At this time, the EMLSR operation indication element also needs to include a partial EMLSR operation indication bitmap, and then the partial EMLSR operation indication bitmap is used to indicate whether the corresponding first MLD needs to perform the first listening operation.
[0168] It can be understood that, in actual applications, the EMLSR operation indication element may also include other fields, and the present application does not impose any specific restrictions on the included fields.
[0169] It can be understood that the above-mentioned first value and second value to sixth value are only specific examples. In actual applications, the first value and second value to sixth value can also take other values, such as 2, 3 or 10, etc., and the present application scheme does not limit this.
[0170] For example, Table 3 is an example of the fields (also referred to as domains) included in the EMLSR operation indication element in the second case; Table 4 is an example of the indications included in the EMLSR operation indication bitmap control in the second case.
[0171]
[0172] Table 3
[0173]
[0174] Table 4
[0175] As shown in Table 3, the EMLSR operation indication element includes an element ID, a length, and an element ID extension; here, the element ID, length, and element ID extension all occupy 1 byte, and the specific definition may be similar to that in the relevant standards.
[0176] Furthermore, the EMLSR operation indication element also includes an EMLSR operation indication bitmap control (EMLSROperation Indicator Bitmap Control) and a partial EMLSR operation indication bitmap (Partial EMLSROperation Indicator Bitmap); wherein the EMLSR operation indication bitmap control occupies 1 byte. The partial EMLSR operation indication bitmap occupies any number of bytes between 1 and 251. Here, it can be understood that, for the first method described above, it can be understood that the number of bytes occupied by the partial EMLSR operation indication bitmap is 0.
[0177] As shown in Table 4, the EMLSR operation indication bitmap control includes EMLSR operation unified indication present (EMLSROperation for ALL Indicator Present). When the value of the EMLSR operation unified indication present is 0, the EMLSR operation indication bitmap control also includes: bitmap offset (Bitmap Offset). Here, the EMLSR operation unified indication present and the bitmap offset occupy 1 bit and 7 bits respectively. Based on this, the EMLSR operation unified indication present and the bitmap offset included in the EMLSR operation indication bitmap control occupy a total of one byte.
[0178] Here, the bitmap offset may be similar to the definition of the bitmap offset (Bitmap Offset) field of the TIM element in the relevant standard. The difference is that the bitmap offset (Bitmap Offset) field of the TIM element in the relevant standard corresponds to the traffic indication virtual bitmap (traffic indication virtual bitmap), while the bitmap offset in the present application scheme corresponds to the EMLSR operation indication bitmap.
[0179] Furthermore, a partial EMLSR operation indication bitmap (also referred to as a partial EMLSR operation indication bitmap domain, or field) is formed by intercepting a meaningful portion of continuous bits in the EMLSR operation indication bitmap, and the interception method is consistent with the method of forming a partial traffic marking virtual bitmap of the TIM element in the relevant standards. The partial traffic marking virtual bitmap is formed by intercepting bits at partial continuous positions of the traffic marking virtual bitmap; the difference lies in the different definitions of the bit values of the two.
[0180] Specifically, in the scheme of the present application, the position of each bit in the EMLSR operation indication bitmap corresponds to an AP, where the AP is at least one of the following: an AP affiliated with an AP MLD, and an AP indicated by a BSSID in a multi-BSSID set where the AP affiliated with the AP MLD is located. In the scheme of the present application, the definition of the bit positions in the EMLSR operation indication bitmap is consistent with the definition of the correspondence between the AP and the bit position when there is a multicast frame buffer in the traffic indication virtual bitmap of the TIM element in the relevant standard.
[0181] Further, the value of each bit in the EMLSR operation indication bitmap indicates: when there is a multicast frame cache, the AP corresponding to the bit and the non-AP MLD corresponding to the AP working in the EMLSR mode perform a first monitoring operation, wherein the first monitoring operation is used for the first station corresponding to the non-AP MLD and the AP to have a first receiving capability, thereby enabling the first station to monitor the link where the AP is located. Alternatively, the value of each bit in the EMLSR operation indication bitmap indicates: when the non-AP MLD corresponding to the AP corresponding to the bit and working in the EMLSR mode needs to receive a multicast frame, whether the first monitoring operation is performed, wherein the first monitoring operation is used for the first station corresponding to the AP and the non-AP MLD to have a first receiving capability, thereby enabling the first station to monitor the link where the AP is located.
[0182] That is to say, the value of each bit in the EMLSR operation indication bitmap indicates: when there is a multicast frame cache, whether the AP corresponding to the bit needs the non-AP MLD working in the EMLSR mode corresponding to the AP to perform the first listening operation with a higher rate / higher MCS / more SS / higher BW receiving capability (that is, the first receiving capability) and being in the link where the AP is located (such as the first link). In other words, the value of each bit in the EMLSR operation indication bitmap indicates: when the non-AP MLD working in the EMLSR mode corresponding to the AP corresponding to the bit needs to perform the first listening operation with a higher rate / higher MCS / more SS / higher BW receiving capability (that is, the first receiving capability) and being in the link where the AP is located (such as the first link) when it needs to receive multicast frames.
[0183] It is understandable that the non-AP MLD corresponding to the AP working in the EMLSR mode may specifically be: the non-AP MLD corresponding to the site (such as the first site) corresponding to the AP working in the EMLSR mode. The non-AP MLD is associated with the AP MLD.
[0184] Further, when the value of a certain bit in the EMLSR operation indication bitmap is 1, it indicates that the AP corresponding to the bit, when there is a multicast frame buffer, needs the non-AP MLD corresponding to the AP working in the EMLSR mode to perform the first monitoring operation with a higher rate / higher MCS / more SS / higher BW receiving capability and in the link where the AP is located;
[0185] When the value of a bit in the EMLSR operation indication bitmap is 0, it means that the AP corresponding to the bit, when there is a multicast frame cache, does not need the non-AP MLD corresponding to the AP working in the EMLSR mode to perform the first listening operation with a higher rate / higher MCS / more SS / higher BW receiving capability and is in the link where the AP is located.
[0186] In one embodiment, the EMLSR operation indication element is carried by a management frame. In this case, the first information may be specifically a management frame. Further, the first MLD receives the management frame. Specifically, before S310, the first MLD receives the management frame. For example, the first MLD receives the management frame sent by the second MLD, so that it is convenient to perform the first monitoring operation based on the management frame; here, in an example, the management frame may also specifically include a traffic indication map TIM beacon frame.
[0187] Mode 4: The first information is a target initial control frame, which is used to notify that a multicast frame is sent after the target initial control frame. In a specific example, the target initial control frame does not need to be replied.
[0188] In one embodiment, before step S310, the first MLD receives the target initial control frame. It can be understood that the target initial control frame is sent by the second MLD when the first MLD needs to perform the first monitoring operation. Here, the second MLD is an MLD associated with the first MLD. For example, when the second MLD is expected to use a higher rate / higher MCS / more SS / higher BW to send a multicast frame, it can send the target initial control frame to the first MLD in advance to inform the first MLD to send a multicast frame after the target initial control frame, so that the first MLD performs the first monitoring operation to normally receive the multicast frame sent using a higher rate / higher MCS / more SS / higher BW.
[0189] In one case, the first multi-link device MLD performs the first listening operation, specifically: the first MLD switches from the second listening operation to the first listening operation, more specifically, after receiving the target initial control frame, the first MLD switches from the second listening operation to the first listening operation; or, in another case, the first MLD is currently (i.e., when or before receiving the target initial control frame) in the first listening operation, and at this time, there is no need to switch, and only needs to continue to maintain the first listening operation, that is, continue to perform the first listening operation. In this way, the multicast frame sent with a higher rate / higher MCS / more SS / higher BW can be normally received.
[0190] In one embodiment, the target initial control frame includes an indication duration, and the indication duration is the maximum available duration for the first MLD to switch to the first listening operation. That is, in the case where switching is required, the first MLD needs to switch to the first listening operation within the maximum available duration, so as to facilitate normal reception of multicast frames. Further, the first multi-link device MLD performs the first listening operation, specifically: the first MLD switches from the second listening operation to the first listening operation, more specifically, the first MLD switches from the second listening operation to the first listening operation within the indication duration; or, in another case, the first MLD is currently in the first listening operation, and there is no need to switch at this time, and it is only necessary to continue to maintain the first listening operation, that is, to continue to execute the first listening operation.
[0191] In one embodiment, the target initial control frame is a variant multi-user request to send MU-RTS trigger frame. Further, the value of the trigger type subfield of the variant MU-RTS trigger frame is different from the value of the trigger type subfield of the MU-RTS trigger frame.
[0192] In one embodiment, the target initial control frame, such as a variant MU-RTS trigger frame, is used to notify that a multicast frame is sent after the MU-RTS trigger frame. It can be understood that the purpose of the variant MU-RTS trigger frame is to inform the first MLD to send a multicast frame after the MU-RTS trigger frame, and the sent multicast frame uses a higher rate / higher MCS / more SS / higher BW. Therefore, after receiving the variant MU-RTS trigger frame, the first MLD does not need to reply, but only needs to switch to the first listening operation within the indicated duration carried by the variant MU-RTS trigger frame. Alternatively, when the first MLD receives the variant MU-RTS trigger frame, it is in the first listening operation. At this time, there is no need to reply, and it only needs to continue to perform the first listening operation.
[0193] For example, when an AP MLD working in EMLSR mode expects to send a multicast frame at a higher rate / higher MCS / more SSs / higher BW, before sending the multicast frame, it can send a target initial control frame that does not require a reply, such as a variant MU-RTS trigger frame, to inform (such as informing the non-APMLD associated with the AP MLD working in EMLSR mode, which also works in EMLSR mode) to send a multicast frame after the target initial control frame, and the sent multicast frame uses a higher rate / higher MCS / more SSs / higher BW; at the same time, the target initial control frame can carry a specified padding duration (i.e., an indication duration) to ensure that the non-AP MLD working in EMLSR mode has enough time to switch to the first listening operation in advance on a specific link in the EMLSR link (i.e., the link that sends the multicast frame, such as the first link) to facilitate the normal reception of the multicast frame.
[0194] Figure 4 is a schematic flow chart of a communication method 400 according to an embodiment of the present application. The method may optionally be applied to Figure 1 The system shown in the figure is not limited thereto. The method includes at least part of the following contents.
[0195] S410: The second multi-link device MLD sends first information, where the first information is used by the first multi-link device MLD to perform a first monitoring operation, where the first monitoring operation is used by a first station on the first MLD to receive a multicast frame using a first receiving capability.
[0196] In one implementation, both the first MLD and the second MLD are MLDs operating in the EMLSR mode.
[0197] In one implementation, the second MLD is an access point AP MLD, and the first MLD is a non-access point non-AP MLD corresponding to the AP MLD. Further, the second MLD is an MLD operating in EMLSR mode, and the first MLD is a non-access point non-AP MLD operating in EMLSR mode and associated with the AP MLD (i.e., the second MLD).
[0198] In one embodiment, the first site is a subsidiary site of the first MLD. Specifically, the first site is a site on the first MLD corresponding to the first link, and the first site is used to monitor the first link, that is, the first monitoring operation is used for the first site to be in a monitoring state to monitor the channel state of the first link. Here, the first site can also be called a monitoring site. The first link is a link for sending the multicast frame.
[0199] In one implementation, the first link is a link in an EMLSR link.
[0200] That is to say, S410 specifically includes: the access point AP MLD working in the EMLSR mode sends the first information, and the first information is used for the non-access point non-AP MLD to perform a first monitoring operation, wherein the first monitoring operation is used for the first station (that is, the monitoring station) on the non-AP MLD to monitor the first link in the EMLSR link, so that the first station can receive multicast frames through the first link and adopt the first receiving capability. Here, the first link can be a link for sending multicast frames by the AP MLD associated with the non-AP MLD. For example, the access point AP (that is, the attached AP) on the AP MLD can send multicast frames through the first link. The non-AP MLD also works in the EMLSR mode.
[0201] For example, the two ends of the link in the EMLSR link correspond to the site on the non-AP MLD and the subordinate AP on the AP MLD respectively; the subordinate AP sends multicast frames through the link, and correspondingly, the site receives multicast frames through the link. In other words, for an AP, one AP corresponds to one link, and at the same time, it also corresponds to one site. The AP sends multicast frames through its corresponding link, and correspondingly, the site receives the multicast frames through its corresponding link. That is, the site, link, and AP can correspond one to one.
[0202] In one implementation, the first receiving capability is greater than or equal to the second receiving capability; the second receiving capability is the receiving capability used by the first station when the first MLD performs the second monitoring operation. For example, the first receiving capability may be greater than the second receiving capability.
[0203] In a specific example, the first receiving capability is the receiving capability under the EMLSR mode, that is, the first receiving capability is the receiving capability of the first site affiliated with the first MLD under the EMLSR mode, and accordingly, the second receiving capability is also the receiving capability under the EMLSR mode, that is, the second receiving capability is the receiving capability of the first site affiliated with the first MLD under the EMLSR mode.
[0204] In one implementation, the first receiving capability includes at least one of the following: a first rate, a first modulation and coding strategy MCS, a first spatial stream SS, and a first bandwidth BW.
[0205] In another embodiment, the second receiving capability includes at least one of the following: a second rate, a second modulation and coding strategy MCS, a second spatial stream SS and a second bandwidth BW; the second receiving capability is the receiving capability of the first site under the second monitoring operation.
[0206] Here, the first rate is greater than or equal to the second rate; the first MCS is better than or equal to the second MCS; the first SS is greater than or equal to the second SS; and the first BW is greater than or equal to the second BW.
[0207] It should be noted that the present application does not limit the number of parameters included in the first receiving capability (or the second receiving capability), for example, it can be one, two, or more of the above parameters. Accordingly, the parameters included in the first receiving capability and the parameters included in the second receiving capability can be the same or different; the number of parameters included in the first receiving capability and the number of parameters included in the second receiving capability can be the same or different, and the present application does not limit this.
[0208] It can be understood that if at least one parameter in the first receiving capability (at least one of the above parameters) is greater than the parameter corresponding to the second receiving capability, the first receiving capability can be considered to be greater than the second receiving capability. For example, the first rate included in the first receiving capability is greater than the second rate included in the second receiving capability. At this time, if the first receiving capability also includes other parameters, even if the other parameters included in the first receiving capability are equal to the corresponding parameters included in the second receiving capability, the first receiving capability can be considered to be greater than or superior to the second receiving capability. For example, the first SS included in the first receiving capability is equal to the second SS included in the second receiving capability. At this time, since the first rate included in the first receiving capability is greater than the second rate included in the second receiving capability, the first receiving capability can still be considered to be greater than the second receiving capability.
[0209] In one embodiment, all parameters included in the first receiving capability are greater than (or better than) the parameters corresponding to the second receiving capability. In this way, it is ensured that multicast frames in more scenarios can be received. Specifically, since the first station on the first MLD has the first receiving capability (or is called a better first receiving capability), even without receiving the initial control frame in advance, such as the MU-RTS trigger frame, it is still possible to receive multicast frames sent with higher capabilities, for example, it is still possible to receive multicast frames sent by the second MLD with a higher rate, or a higher MCS, or a higher BW, or more SSs.
[0210] In one implementation, in the first monitoring operation, only the first station on the first MLD is in a monitoring state, and other stations on the first MLD cannot enter the monitoring state, that is, do not have the ability to receive or send frames.
[0211] Alternatively, in another embodiment, the first MLD also includes a second site; the first monitoring operation is also used for the second site to monitor the second link in the EMLSR link (that is, the second site is in a monitoring state), and the second link is a link in the EMLSR link other than the first link; further, the second site also has the first receiving capability. That is to say, when the first site has the first receiving capability under the first monitoring operation, the second site on the first MLD can also be in a monitoring state to monitor other links except the first link; at this time, the second site can also have the first receiving capability.
[0212] Specifically, when the first multi-link device MLD performs the first listening operation and the first multi-link device MLD maintains to perform the first listening operation, the first listening operation is also used for the second site to listen to the second link in the EMLSR link, the second site is a site on the first MLD, and the second link is a link in the EMLSR link other than the first link; or, when the first multi-link device MLD performs the first listening operation and the first multi-link device switches from the second listening operation to the first listening operation, the first listening operation makes it impossible for the second site to listen.
[0213] It can be understood that, in this implementation, when the first site has the first receiving capability under the first monitoring operation, the second site in the awake state on the first MLD can be one or more, and the present application scheme does not limit this. For example, when the first site has the first receiving capability under the first monitoring operation, all second sites in the awake state on the first MLD can be in the monitoring state, and all second sites have the first receiving capability.
[0214] For example, the first monitoring operation (i.e., the first monitoring operation in EMLSR mode) may specifically refer to: on the non-AP MLD working in EMLSR mode, the affiliated site (referred to as the monitoring site, such as the first site) corresponding to a specific link (such as the first link) in the EMLSR link can receive multicast frames sent at a higher rate / higher MCS / more SS / higher BW. Furthermore, there are two situations in which the non-AP MLD enters the first monitoring operation in EMLSR mode:
[0215] Case 1: Under the first monitoring operation, the subsidiary site (such as the first site) can enter the monitoring state corresponding to the frame exchange processing of the specific link (such as the first link) in the EMLSR link; that is, under the first monitoring operation, the frame receiving capability (also referred to as the frame processing capability) of the subsidiary site (such as the first site) corresponding to the specific link (such as the first link) is consistent with the ability of the specific link to perform frame exchange processing, that is, it can receive multicast frames sent with a higher rate / higher MCS / more SS / higher BW. Moreover, in this state, other links in the EMLSR link except the specific link (such as the first link) cannot be monitored, that is, other links except the specific link cannot send or receive frames. For example, in this case, the transceiver capability in the EMLSR link (such as the transceiver capability of other sites in the EMLSR link) can be merged into the first site by switching and merging the links, so that the first site has a stronger first receiving capability.
[0216] Case 2: Under the first monitoring operation, the subsidiary site (such as the first site) where the specific link (such as the first link) in the EMLSR mode is located has the ability to receive multicast frames sent at a higher rate / higher MCS / higher BW / more SSs, so all the subsidiary sites (such as the second site) in the EMLSR link that are in an awake state can be kept in a listening state. At this time, the subsidiary site (such as the second site) in the awake state may have the same receiving capability as the first site, or it may be different. The present application does not impose any restrictions on this. As long as the first site has the ability to receive multicast frames sent at a higher rate / higher MCS / higher BW / more SSs, it belongs to the protection scope of the present application. It can be understood that since the link is not switched and merged in this case, the receiving capability of the first site at this time may be weaker than the receiving capability after the link is switched and merged.
[0217] In one embodiment, the second monitoring operation is used for the target site on the first MLD (that is, the subsidiary site of the first MLD) to monitor the link corresponding to the target site, wherein the target site is a site in an awake state on the first MLD, and the target site has the second receiving capability, such as the second receiving capability includes at least one of the following: performing a clear channel assessment CCA, and receiving an initial control frame for initiating a frame exchange. For another example, when there are two or more target sites in an awake state on the first MLD, at this time, the second monitoring operation can enable the two or more target sites on the first MLD to have the second receiving capability. That is to say, under the second monitoring operation, the subsidiary sites in an awake state on the first MLD, such as one, or more, or all the subsidiary sites in an awake state, can be in a monitoring state, and the subsidiary sites in the monitoring state have a second receiving capability, such as a lower second receiving capability relative to the first receiving capability.
[0218] For example, the second listening operation (that is, the first listening operation in EMLSR mode) may specifically refer to: on the non-AP MLD working in EMLSR mode, all affiliated sites (that is, target sites) in the awake state corresponding to the EMLSR link are in the listening state; wherein, the receiving capability of each site corresponding to the EMLSR link, that is, the second receiving capability, is limited. Except for being able to receive initial control frames such as CCA or MU-RTS trigger frames, other types of frames cannot be received correctly due to limitations on capabilities such as rate / MCS / SS / BW.
[0219] In one embodiment, the second MLD sends the multicast frame. Specifically, the second MLD sends the multicast frame on the first link monitored by the first MLD when performing the first monitoring operation. More specifically, the subordinate AP of the second MLD sends the multicast frame on the first link monitored by the first MLD when performing the first monitoring operation. Accordingly, the first MLD receives the multicast frame by using the first station that monitors the first link and has the first receiving capability.
[0220] In one implementation, the multicast frame sent by the second MLD is carried by a physical layer protocol data unit PPDU, and the PPDU includes at least one of the following:
[0221] Orthogonal frequency division multiplexing OFDM physical layer protocol data unit PPDU;
[0222] Non-HT duplicate DUP PPDU;
[0223] Very high throughput VHT PPDU;
[0224] High throughput HT PPDU;
[0225] High efficiency HE single user SU PPDU;
[0226] PPDUs supported by very high throughput EHT site STAs including very high throughput EHT multi-user MU PPDU.
[0227] Accordingly, the first MLD receives the multicast frame by using the first site with the first receiving capability. For example, the subordinate AP of the AP MLD operating in the EMLSR mode uses at least one of the following parameters to send a PPDU carrying a multicast frame on a specific link (i.e., the first link) in the EMLSR link; accordingly, the non-AP MLD operating in the EMLSR mode, the subordinate site (e.g., the first site with the first receiving capability) corresponding to the specific link (i.e., the first link) in the EMLSR link, can normally receive the PPDU sent by the subordinate AP of the AP MLD; here, the parameters include: higher rate, higher MCS, more SS and higher BW.
[0228] In one implementation, the second MLD sends the multicast frame at the following time points, that is, the second MLD sends the multicast frame through the attached AP at the following time points; the specific time points include:
[0229] (1) Expected multicast frame sending time point; Here, the expected multicast frame sending time point may be any pre-agreed time point, and the present application scheme does not limit this. For example, the AP affiliated with the AP MLD schedules the sending of the cached multicast frame at the expected multicast frame sending time point.
[0230] (2) A time point after sending a DTIM beacon frame; that is, the expected multicast frame sending time point is later than the TBTT of sending the DTIM beacon frame. For example, the AP affiliated with the AP MLD schedules the sending of the cached multicast frame after sending the DTIM beacon frame; for example, the sending of the cached multicast frame is scheduled after each DTIM beacon frame.
[0231] (3) A time point within the broadcast target wake-up time TWT service period SP; that is, the expected multicast frame sending time point is within the broadcast TWT service period SP. For example, an AP subordinate to the AP MLD schedules the sending of multicast frames within the broadcast TWT service period SP; for example, an AP subordinate to the AP MLD is a TWT scheduling AP (TWT scheduling AP), and the TWT scheduling AP schedules the sending of cached multicast frames within the broadcast TWT service period SP during the beacon interval where the DTIM beacon frame is sent.
[0232] (4) A time point after the TBTT of a non-STBC DTIM beacon frame whose current count value in the FMS counter field of a specific flexible multicast service FMS stream is zero; that is, the expected multicast frame sending time point is later than the TBTT of a non-STBC DTIM beacon frame whose current count value in the FMS counter field of the FMS stream is zero. For example, the cached multicast frame is scheduled to be sent at a time point after the TBTT of a non-STBC DTIM beacon frame whose current count value in the FMS counter field of a specific flexible multicast service FMS stream is zero.
[0233] (5) Within the multicast GCR service period with retry. That is, the expected multicast frame sending time point is within the GCR service period. For example, within the GCR service period, the multicast frame buffered is scheduled to be sent.
[0234] In one implementation, the first information sent by the second MLD and used to enable the first multi-link device MLD to perform the first monitoring operation can be obtained in the following ways:
[0235] Mode 1: The first information is used for the first MLD to perform the first monitoring operation at a target time or before a target time. That is, the first MLD can perform the first monitoring operation at a target time or before a target time based on the first information.
[0236] It can be understood that, in one example, the first information includes a target time, in which case the first information is used for the first MLD to perform the first monitoring operation at the target time or before the target time included in the first information. Alternatively, in another example, the first information does not include a target time, in which case the target time is sent in advance by the second MLD to the first MLD, that is, is received in advance by the first MLD, in which case the first information is used for the first MLD to perform the first monitoring operation at the pre-acquired target time or before the target time. The present application does not impose any restriction on whether the target time is carried in the first information, as long as the first information enables the first MLD to perform the first monitoring operation at the target time or before the target time, it falls within the protection scope of the present application.
[0237] In one implementation, the first information is used by the first MLD to perform the first listening operation at a target time or before a target time, and may specifically include: the first information is used by the first MLD to switch from a second listening operation to the first listening operation at a target time or before a target time, or, upon receiving the first information, the first MLD is in the first listening operation, and at this time, it is only necessary to continue to perform the first listening operation.
[0238] In one implementation, the target time in the first embodiment includes a first time point, and the first time point may specifically include at least one of the following:
[0239] (1) Expected multicast frame sending time point. At this time, the first MLD performs the first monitoring operation at the expected multicast frame sending time point, or at a time point before the expected multicast frame sending time point; here, the expected multicast frame sending time point can be any pre-agreed time point, and the present application scheme does not limit this.
[0240] (2) Expected target beacon sending time TBTT of the transmission traffic indication diagram DTIM beacon frame; Here, the expected multicast frame sending time point is later than the TBTT of the DTIM beacon frame. At this time, the first MLD performs the first monitoring operation at the TBTT of the expected DTIM beacon frame or at a time point before the TBTT of the expected DTIM beacon frame.
[0241] (3) The start time of the broadcast target wake-up time TWT service period SP for sending the expected multicast frame; Here, the expected multicast frame sending time point is within the broadcast TWT service period SP. At this time, the first MLD performs the first monitoring operation at the start time of the broadcast target wake-up time TWT service period SP for sending the expected multicast frame, or at a time point before the start time.
[0242] (4) The TBTT of a non-STBC DTIM beacon frame whose current count value of the FMS counter field of a specific flexible multicast service FMS stream is zero; here, the expected multicast frame sending time point is later than the TBTT of a non-STBC DTIM beacon frame whose current count value of the FMS counter field of the FMS stream is zero. At this time, the first MLD performs the first monitoring operation at the TBTT of a non-STBC DTIM beacon frame whose current count value of the FMS counter field of the specific FMS stream is zero, or at a time point before the TBTT of a non-STBC DTIM beacon frame whose current count value of the FMS counter field of the specific FMS stream is zero.
[0243] (5) the start time of the multicast GCR service period with retry for sending multicast frames; here, the expected multicast frame sending time point is within the GCR service period. At this time, the first MLD performs the first monitoring operation at the start time of the multicast GCR service period with retry for sending multicast frames, or at a time point before the start time.
[0244] It can be understood that, for a specific example of the receiving end, that is, the first MLD end, reference can be made to the above description, which will not be repeated here.
[0245] In one embodiment, the first time point is determined by the second MLD; further, the first time point is sent in advance by the second MLD to the first MLD; for example, before step S410, the second MLD sends the first time point to the first MLD to ensure that the first MLD performs a first monitoring operation in advance before the expected multicast frame is sent, so that the first site monitors the link where the multicast frame is scheduled to be sent in the EMLSR link.
[0246] Mode 2: the first information is a DTIM beacon frame, that is, step S410 specifically includes: the second MLD sends a DTIM beacon frame, and the DTIM beacon frame is used for the first MLD to perform the first monitoring operation at a target time or before the target time.
[0247] It can be understood that, in one example, the DTIM beacon frame may include a target time (such as a second time point), that is, it carries a target time. In this case, the DTIM beacon frame is used for the first MLD to perform the first listening operation at the target time or before the target time carried by the DTIM beacon frame. Alternatively, in another example, the DTIM beacon frame does not include a target time, that is, it does not carry a target time; in this case, the target time is sent in advance by the second MLD to the first MLD, that is, it is received in advance by the first MLD. Further, the DTIM beacon frame is used for the first MLD to perform the first listening operation at the pre-acquired target time or before the target time. The present application scheme does not impose any restrictions on whether the target time is carried in the DTIM beacon frame. As long as the DTIM beacon frame enables the first MLD to perform the first listening operation at the target time or before the target time, it belongs to the protection scope of the present application scheme.
[0248] In one implementation, different from the first approach, the target time in the second approach includes a second time point; further, the DTIM beacon frame is used for the first MLD to switch from the second listening operation to the first listening operation at or before the second time point.
[0249] Further, the second time point includes: an expected multicast frame sending time point after the first MLD receives the DTIM beacon frame; here, the DTIM beacon frame is received by the first MLD under the second monitoring operation. That is to say, the expected multicast frame sending time point is after the time point of sending the DTIM beacon frame. At this time, the first MLD first receives the DTIM beacon frame and performs the first monitoring operation at the expected multicast frame sending time point after receiving the DTIM beacon frame, or before the expected multicast frame sending time point after receiving the DTIM beacon frame. It can be understood that the first monitoring operation can be performed at the time point when the first MLD receives the DTIM beacon frame.
[0250] For example, an AP MLD working in EMLSR mode sends a DTIM beacon frame on a specific link (such as the first link) in the EMLSR link; at this time, a non-AP MLD working in EMLSR mode (associated with the AP MLD) is preparing to receive a multicast frame on the link (such as the first link) in the EMLSR link. It can first enter the second listening operation before the TBTT of the DTIM beacon frame, and after receiving the DTIM beacon frame and before the expected time point for the multicast frame to be scheduled to be sent, switch from the second listening operation to the first listening operation, so that the first site of the first MLD monitors the link (such as the first link) where the multicast frame is scheduled to be sent in the EMLSR link. Here, under the first listening operation, the first site has a first receiving capability, thereby ensuring that the multicast frame can be received normally.
[0251] It can be understood that after the AP MLD sends the DTIM beacon frame on the EMLSR link and before the starting time point for scheduling the sending of the multicast frame, it is necessary to reserve sufficient time. In this way, it can be ensured that the non-AP MLD associated with the AP MLD working in the EMLSR mode switches to the first listening operation of the link (such as the first link) where the multicast frame is scheduled to be sent in the EMLSR link after receiving the DTIM beacon frame and at the time point when the multicast frame is sent or before the time point when the multicast frame is sent.
[0252] Mode three: The first information is determined based on the first indication; the first indication is used to indicate whether to perform the first listening operation when a multicast frame needs to be received. For example, the first indication is specifically used to indicate whether to perform the first listening operation when a multicast frame needs to be received, or to indicate that the first listening operation does not need to be performed when a multicast frame needs to be received. Furthermore, in this mode three, the first indication can be expressed in the following two ways, including:
[0253] First way:
[0254] The first indication is used to uniformly indicate whether the first MLD corresponding to the access point AP performs the first monitoring operation when it needs to receive a multicast frame; here, the access point AP is the AP corresponding to the second MLD associated with the first MLD; the AP corresponding to the second MLD includes at least one of the following: an affiliated AP of the second MLD, an AP indicated by the BSSID in the multi-BSSID set where the affiliated AP of the second MLD is located.
[0255] For example, the first MLD corresponding to the access point AP can be specifically: the first MLD corresponding to the first site corresponding to the access point AP; it can be understood that the link, such as the two ends of the link in the EMLSR link, respectively correspond to the first site on the first MLD and the access point AP corresponding to the second MLD, and the site, link and AP can correspond one to one. Based on this, the site corresponds to the access point AP, and the site corresponds to the first MLD.
[0256] It should be noted that the first indication does not carry a target time, for example, does not carry a first time point, and the purpose of the first indication is to indicate whether a first listening operation needs to be performed when multicast needs to be received. Based on this, the first time point may be acquired in advance by the first MLD through other means, and the present application does not impose specific restrictions on this. Alternatively, in another case, the first indication not only indicates whether a first listening operation needs to be performed when multicast needs to be received, but also carries a target time, such as the first time point. In this case, the first MLD does not need to acquire the first time point in advance. In actual applications, the above two methods can be executed one by one, and the present application does not impose any restrictions.
[0257] In one implementation, when the value of the first indication is a first value (such as 1), it is used to uniformly indicate the first MLD corresponding to the access point AP to perform the first monitoring operation when a multicast frame needs to be received;
[0258] Alternatively, when the value of the first indication is a second value (such as 0), it is used to uniformly indicate that the first MLD corresponding to the access point AP does not need to perform the first monitoring operation when a multicast frame needs to be received.
[0259] In one implementation, the first indication is carried by an EMLSR operation indication element. Further, the first indication is carried by a first field in the EMLSR operation indication element.
[0260] In one implementation, the first field includes a second indication; when the value of the second indication is a third value (for example, 1), the first field includes the first indication.
[0261] In one embodiment, the first field is an EMLSR operation indication bitmap control. The first indication is an EMLSR operation unified indication. Further, the second indication is an EMLSR operation unified indication existence; wherein the EMLSR operation unified indication existence is used to indicate whether the first field (i.e., the EMLSR operation indication bitmap control) includes an EMLSR operation unified indication.
[0262] It can be understood that, in actual applications, the EMLSR operation indication element may also include other fields, and the present application does not impose any specific restrictions on the included fields.
[0263] In one embodiment, the EMLSR operation indication element is carried by a management frame. In this case, the first information may be specifically a management frame. Further, the first MLD receives the management frame. Specifically, before S310, the first MLD receives the management frame. For example, the first MLD receives the management frame sent by the second MLD, so that it is convenient to perform the first monitoring operation based on the management frame; here, in one example, the management frame includes a traffic indication map TIM beacon frame.
[0264] Second way:
[0265] The position of each bit in the first indication is used to indicate an access point AP;
[0266] The value of each bit in the first indication is used to indicate whether the first MLD corresponding to the access point AP performs the first monitoring operation when a multicast frame needs to be received.
[0267] Here, the access point AP is the AP corresponding to the second MLD associated with the first MLD; the AP corresponding to the second MLD includes at least one of the following: an affiliated AP of the second MLD, and an AP indicated by a BSSID in a multi-BSSID set where the affiliated AP of the second MLD is located.
[0268] For example, the first MLD corresponding to the access point AP can be specifically: the first MLD corresponding to the first site corresponding to the access point AP; it can be understood that the link, such as the two ends of the link in the EMLSR link, respectively correspond to the first site on the first MLD and the access point AP corresponding to the second MLD, and the site, link and AP can correspond one to one. Based on this, the site corresponds to the access point AP, and the site corresponds to the first MLD.
[0269] It should be noted that the first indication does not carry a target time, for example, does not carry a first time point, and the purpose of the first indication is to indicate whether a first listening operation needs to be performed when multicast needs to be received. Based on this, the first time point may be acquired in advance by the first MLD through other means, and the present application does not impose specific restrictions on this. Alternatively, in another case, the first indication not only indicates whether a first listening operation needs to be performed when multicast needs to be received, but also carries a target time, such as the first time point. In this case, the first MLD does not need to acquire the first time point in advance. In actual applications, the above two methods can be executed one by one, and the present application does not impose any restrictions.
[0270] In one implementation, when the value of each bit in the first indication is a fourth value (such as 1), it is used to instruct the first MLD corresponding to the access point AP to perform the first monitoring operation when a multicast frame needs to be received;
[0271] Alternatively, when the value of each bit in the first indication is the fifth value (such as 0), it is used to indicate that the first MLD corresponding to the access point AP does not need to perform the first monitoring operation when it needs to receive a multicast frame.
[0272] In one implementation, the first indication is carried by an EMLSR operation indication element. Further, the first indication is carried by a second field in the EMLSR operation indication element.
[0273] In one implementation, the second field is a partial EMLSR operation indication bitmap; the partial EMLSR operation indication bitmap is formed by intercepting a portion of continuous bits in the EMLSR operation indication bitmap.
[0274] In one embodiment, the EMLSR operation indication element includes a first field; wherein, when the value of the second indication in the first field is a sixth value (for example, 0), the first field includes a third indication; the third indication is used to indicate the position of a portion of continuous bits intercepted from the EMLSR operation indication bitmap. In one embodiment, the third indication is a bitmap offset, so that the portion of the EMLSR operation indication bitmap can be intercepted from the EMLSR operation indication bitmap based on the bitmap offset.
[0275] In one embodiment, the first field is an EMLSR operation indication bitmap control. The first indication is an EMLSR operation unified indication. Further, the second indication is the existence of an EMLSR operation unified indication; wherein the existence of the EMLSR operation unified indication is used to indicate whether the first field (i.e., the EMLSR operation indication bitmap control) includes an EMLSR operation unified indication. For example, when the value of the EMLSR operation unified indication existence is a third value (such as 1), the EMLSR operation indication bitmap control includes the EMLSR operation unified indication, and at this time, it may also include a reservation. In this case, the EMLSR operation unified indication is used to uniformly indicate whether the corresponding first MLD needs to perform the first listening operation. Further, when the value of the EMLSR operation unified indication existence is a sixth value (such as 0), the EMLSR operation indication bitmap control includes the bitmap offset. At this time, the EMLSR operation indication element also needs to include a partial EMLSR operation indication bitmap, and then the partial EMLSR operation indication bitmap is used to indicate whether the corresponding first MLD needs to perform the first listening operation.
[0276] It can be understood that, in actual applications, the EMLSR operation indication element may also include other fields, and the present application does not impose any specific restrictions on the included fields.
[0277] In one embodiment, the EMLSR operation indication element is carried by a management frame. In this case, the first information may be specifically a management frame. Further, the first MLD receives the management frame. Specifically, before S310, the first MLD receives the management frame. For example, the first MLD receives the management frame sent by the second MLD, so that it is convenient to perform the first monitoring operation based on the management frame; here, in an example, the management frame may also specifically include a traffic indication map TIM beacon frame.
[0278] It can be understood that specific examples of the first method and the second method can be found in the examples related to the first MLD, which will not be described in detail here.
[0279] Mode 4: The first information is a target initial control frame, which is used to notify that a multicast frame is sent after the target initial control frame. In a specific example, the target initial control frame does not need to be replied.
[0280] In one embodiment, the target initial control frame is sent by the second MLD when the first MLD needs to perform the first listening operation, where the second MLD is an MLD associated with the first MLD. For example, when the second MLD is expected to use a higher rate / higher MCS / more SS / higher BW to send multicast frames, it can send the target initial control frame to the first MLD in advance to inform the first MLD to send multicast frames after the target initial control frame, so that the first MLD performs the first listening operation to normally receive multicast frames sent using a higher rate / higher MCS / more SS / higher BW.
[0281] In one case, the first multi-link device MLD performs the first listening operation, specifically: the first MLD switches from the second listening operation to the first listening operation, more specifically, after receiving the target initial control frame, the first MLD switches from the second listening operation to the first listening operation; or, in another case, the first MLD is currently (i.e., when or before receiving the target initial control frame) in the first listening operation, and at this time, there is no need to switch, and only needs to continue to maintain the first listening operation, that is, continue to perform the first listening operation. In this way, the multicast frame sent with a higher rate / higher MCS / more SS / higher BW can be normally received.
[0282] In one embodiment, the target initial control frame includes an indication duration, and the indication duration is the maximum available duration for the first MLD to switch to the first listening operation. For example, when the first MLD needs to perform the first listening operation, the second MLD sends the target initial control frame so that the first MLD switches to the first listening operation within the maximum available duration when switching is required, so that the first MLD can normally receive multicast frames.
[0283] In one embodiment, the target initial control frame is a variant multi-user request to send MU-RTS trigger frame. Further, the value of the trigger type subfield of the variant MU-RTS trigger frame is different from the value of the trigger type subfield of the MU-RTS trigger frame.
[0284] In one embodiment, the target initial control frame, such as a variant MU-RTS trigger frame, is used to notify that a multicast frame is sent after the MU-RTS trigger frame. It can be understood that the purpose of the variant MU-RTS trigger frame is to inform the first MLD to send a multicast frame after the MU-RTS trigger frame, and the sent multicast frame uses a higher rate / higher MCS / more SS / higher BW. Therefore, after receiving the variant MU-RTS trigger frame, the first MLD does not need to reply, but only needs to switch to the first listening operation within the indicated duration carried by the variant MU-RTS trigger frame. Alternatively, when the first MLD receives the variant MU-RTS trigger frame, it is in the first listening operation. At this time, there is no need to reply, and it only needs to continue to perform the first listening operation.
[0285] For example, when an AP MLD working in EMLSR mode expects to send a multicast frame at a higher rate / higher MCS / more SSs / higher BW, before sending the multicast frame, it can send a target initial control frame that does not require a reply, such as a variant MU-RTS trigger frame, to inform (such as informing the non-APMLD associated with the AP MLD working in EMLSR mode, which also works in EMLSR mode) to send a multicast frame after the target initial control frame, and the sent multicast frame uses a higher rate / higher MCS / more SSs / higher BW; at the same time, the target initial control frame can carry a specified padding duration (i.e., an indication duration) to ensure that the non-AP MLD working in EMLSR mode has enough time to switch to the first listening operation in advance on a specific link in the EMLSR link (i.e., the link that sends the multicast frame, such as the first link) to facilitate the normal reception of the multicast frame.
[0286] The present application also provides a first multi-link device, such as Figure 5As shown, the first multi-link device 500 includes:
[0287] The processing unit 510 is configured to perform a first monitoring operation, wherein the first monitoring operation is used for a first station on the first MLD to receive a multicast frame using a first receiving capability.
[0288] In one embodiment, wherein
[0289] The first receiving capability is greater than or equal to a second receiving capability, and the second receiving capability is a receiving capability adopted by the first station when the first MLD performs a second monitoring operation.
[0290] In one implementation, the processing unit is specifically configured to perform a first monitoring operation based on the first information.
[0291] In one implementation, the first information is used by the first MLD to perform the first monitoring operation at a target time or before a target time.
[0292] In one embodiment, the target time includes a first time point, and the first time point includes at least one of the following:
[0293] The expected time when the multicast frame is sent;
[0294] Expected transmission traffic indication diagram DTIM beacon frame target beacon transmission time TBTT;
[0295] The start time of the broadcast target wake-up time TWT service period SP for sending multicast frames is expected;
[0296] The TBTT of the non-STBC DTIM beacon frame whose current count value of the FMS counter field of a specific FMS flow is zero;
[0297] The start time of the multicast GCR service period with retries for sending multicast frames is expected.
[0298] In one implementation, the first time point is received in advance by the first MLD.
[0299] In one implementation, the first information is a transmission traffic indication map (DTIM) beacon frame, and the DTIM beacon frame is used for the first MLD to perform the first monitoring operation at a target time or before a target time.
[0300] In one implementation, the target time includes a second time point, and the second time point includes: an expected multicast frame sending time point after receiving a transmission traffic indication map DTIM beacon frame; the DTIM beacon frame is received by the first MLD in the second monitoring operation.
[0301] In one embodiment, the processing unit 510 is specifically configured to switch from the second monitoring operation to the first monitoring operation at or before the second time point; the second monitoring operation is performed by the first MLD before the target beacon sending time TBTT of the expected transmitted DTIM beacon frame.
[0302] In one implementation, the first information is determined based on a first indication; the first indication is used to indicate whether to perform the first monitoring operation when a multicast frame needs to be received.
[0303] In one implementation, the first indication is used to uniformly indicate whether the first MLD corresponding to the access point AP performs the first monitoring operation when a multicast frame needs to be received;
[0304] The access point AP is an AP corresponding to a second MLD associated with the first MLD; the AP corresponding to the second MLD includes at least one of the following:
[0305] The subordinate AP of the second MLD is the AP indicated by the BSSID in the multiple BSSID set where the subordinate AP of the second MLD is located.
[0306] In one implementation, when the value of the first indication is the first value, it is used to uniformly indicate the first MLD corresponding to the access point AP to perform the first monitoring operation when a multicast frame needs to be received;
[0307] Alternatively, when the value of the first indication is the second value, it is used to uniformly indicate that the first MLD corresponding to the access point AP does not need to perform the first monitoring operation when it needs to receive a multicast frame.
[0308] In one implementation, the first indication is carried by an EMLSR operation indication element.
[0309] In one implementation, the first indication is carried by a first field in an EMLSR operation indication element.
[0310] In one embodiment, the first field includes a second indication;
[0311] When the value of the second indication is a third value, the first field includes the first indication.
[0312] In one implementation, the first indication is an EMLSR operation unified indication.
[0313] In one embodiment, the position of each bit in the first indication is used to indicate an access point AP; the access point AP is an AP corresponding to a second MLD associated with the first MLD; the AP corresponding to the second MLD includes at least one of the following: an AP affiliated with the second MLD, an AP indicated by a BSSID in a multi-BSSID set where the AP affiliated with the second MLD is located;
[0314] The value of each bit in the first indication is used to indicate whether the first MLD corresponding to the access point AP performs the first monitoring operation when a multicast frame needs to be received.
[0315] In one implementation, when the value of each bit in the first indication is the fourth value, it is used to instruct the first MLD corresponding to the access point AP to perform the first monitoring operation when a multicast frame needs to be received;
[0316] Alternatively, when the value of each bit in the first indication is the fifth value, it is used to indicate that the first MLD corresponding to the access point AP does not need to perform the first monitoring operation when it needs to receive a multicast frame.
[0317] In one implementation, the first indication is carried by an EMLSR operation indication element.
[0318] In one implementation, the first indication is carried by a second field in the EMLSR operation indication element.
[0319] In one implementation, the second field is a partial EMLSR operation indication bitmap; the partial EMLSR operation indication bitmap is formed by intercepting a portion of continuous bits in the EMLSR operation indication bitmap.
[0320] In one embodiment, the EMLSR operation indication element includes a first field;
[0321] When the value of the second indication in the first field is the sixth value, the first field includes a third indication; the third indication is used to indicate the position of a portion of continuous bits intercepted from the EMLSR operation indication bitmap.
[0322] In one implementation, the third indication is a bitmap offset.
[0323] In one implementation, the second indication is the existence of an EMLSR operation unified indication; wherein the existence of the EMLSR operation unified indication is used to indicate whether the first field includes an EMLSR operation unified indication.
[0324] In one implementation, the first field is an EMLSR operation indication bitmap control.
[0325] In one implementation, the EMLSR operation indication element is carried by a management frame.
[0326] In one implementation, the management frame includes a traffic indication map TIM beacon frame.
[0327] In one embodiment, it further includes:
[0328] The first receiving unit is used to receive the management frame.
[0329] In one implementation, the first information is a target initial control frame, which is used to notify that a multicast frame is sent after the target initial control frame.
[0330] In one implementation, the target initial control frame includes an indication duration, where the indication duration is a maximum available duration for the first MLD to switch to the first listening operation.
[0331] In one implementation, the target initial control frame is a variant of a multi-user request to send MU-RTS trigger frame.
[0332] In one implementation, a value of the trigger type subfield of the variant MU-RTS trigger frame is different from a value of the trigger type subfield of the MU-RTS trigger frame.
[0333] In one embodiment, it further includes:
[0334] The second receiving unit is configured to receive the target initial control frame, where the target initial control frame is sent by the second MLD when the first MLD is required to perform the first monitoring operation, and the second MLD is an MLD associated with the first MLD.
[0335] In one implementation, the processing unit is specifically configured to: switch from the second monitoring operation to the first monitoring operation; or, maintain executing the first monitoring operation.
[0336] In one embodiment, the first receiving capability includes at least one of the following: a first rate, a first modulation and coding strategy MCS, a first spatial stream SS, and a first bandwidth BW;
[0337] And / or, the second receiving capability includes at least one of the following: a second rate, a second modulation and coding strategy MCS, a second spatial stream SS, and a second bandwidth BW; the second receiving capability is the receiving capability of the first station under the second monitoring operation;
[0338] Among them, the first rate is greater than or equal to the second rate; the first MCS is better than or equal to the second MCS; the first SS is greater than or equal to the second SS; and the first BW is greater than or equal to the second BW.
[0339] In one embodiment, the second monitoring operation is used for the target site on the first MLD to monitor the link corresponding to the target site, wherein the target site is a site in an awake state on the first MLD, and the target site has the second receiving capability; the second receiving capability includes at least one of the following: performing a clear channel assessment CCA, and receiving an initial control frame for initiating a frame exchange.
[0340] In one embodiment, it further includes:
[0341] The third receiving unit is configured to receive the multicast frame through the first station using the first receiving capability.
[0342] In one implementation, the multicast frame received using the first receiving capability is carried by a physical layer protocol data unit PPDU, and the PPDU includes at least one of the following:
[0343] Orthogonal frequency division multiplexing OFDM physical layer protocol data unit PPDU;
[0344] Non-HT duplicate DUP PPDU;
[0345] Very high throughput VHT PPDU;
[0346] High throughput HT PPDU;
[0347] High efficiency HE single user SU PPDU;
[0348] PPDUs supported by very high throughput EHT site STAs including very high throughput EHT multi-user MU PPDU.
[0349] In one embodiment, it further includes:
[0350] The processing unit is further configured to switch from the first monitoring operation to the second monitoring operation when the multicast frame reception is completed.
[0351] In one implementation, the first site is a site on the first MLD corresponding to the first link, and the first site is used to monitor the first link; the first link is a link for sending the multicast frame.
[0352] In one implementation, the first MLD is an MLD operating in an enhanced multi-link single radio EMLSR mode, and the first link is a link in an EMLSR link.
[0353] In one implementation, the first MLD is a non-AP MLD.
[0354] In one implementation, the first multi-link device MLD performs the first monitoring operation when the first multi-link device MLD maintains performing the first monitoring operation, and the first monitoring operation is further used for a second site to monitor a second link in the EMLSR link, the second site is a site on the first MLD, and the second link is a link in the EMLSR link other than the first link;
[0355] or,
[0356] When the first multi-link device MLD performs the first listening operation, which is a switch from the second listening operation to the first listening operation, the first listening operation makes it impossible for the second station to perform listening.
[0357] The first multi-link device 500 of the embodiment of the present application can implement the corresponding functions of the first multi-link device in the aforementioned method embodiment. The corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the first multi-link device 500 can be found in the corresponding description in the aforementioned method embodiment, and will not be repeated here. It should be noted that the functions described by each module (sub-module, unit or component, etc.) in the first multi-link device 500 of the embodiment of the application can be implemented by different modules (sub-module, unit or component, etc.) or by the same module (sub-module, unit or component, etc.).
[0358] The present application also provides a second multi-link device, such as Figure 6 As shown, the second multi-link device 600 includes:
[0359] The sending unit 610 is configured to send first information, where the first information is used for a first multi-link device MLD to perform a first monitoring operation, where the first monitoring operation is used for a first station on the first MLD to receive a multicast frame using a first receiving capability.
[0360] In one implementation, the first receiving capability is greater than or equal to a second receiving capability, the second receiving capability is a receiving capability adopted by the first station on the first MLD indicated by a second monitoring operation, and the second monitoring operation is a monitoring operation that can be performed by the first MLD.
[0361] In one implementation, the first information is used by the first MLD to perform the first monitoring operation at a target time or before a target time.
[0362] In one embodiment, the target time includes a first time point, and the first time point includes at least one of the following:
[0363] The expected time when the multicast frame is sent;
[0364] Expected transmission traffic indication diagram DTIM beacon frame target beacon transmission time TBTT;
[0365] The start time of the broadcast target wake-up time TWT service period SP for sending multicast frames is expected;
[0366] The TBTT of the non-STBC DTIM beacon frame whose current count value of the FMS counter field of a specific FMS flow is zero;
[0367] The start time of the multicast GCR service period with retries for sending multicast frames is expected.
[0368] In one embodiment, the first time point is determined by the second MLD.
[0369] In one implementation, the first information is a transmission traffic indication map (DTIM) beacon frame, and the DTIM beacon frame is used for the first MLD to perform the first monitoring operation at a target time or before a target time.
[0370] In one implementation, the target time includes a second time point, and the second time point includes: an expected multicast frame sending time point after the first MLD receives a DTIM beacon frame; the DTIM beacon frame is received by the first MLD in the second listening operation.
[0371] In one implementation, the DTIM beacon frame is used for the first MLD to switch from the second listening operation to the first listening operation at or before the second time point.
[0372] In one implementation, the first information is determined based on a first indication; the first indication is used to indicate whether to perform the first monitoring operation when a multicast frame needs to be received.
[0373] In one implementation, the first indication is used to uniformly indicate whether the first MLD corresponding to the access point AP performs the first monitoring operation when a multicast frame needs to be received;
[0374] The access point AP is an AP corresponding to a second MLD associated with the first MLD; the AP corresponding to the second MLD includes at least one of the following:
[0375] The subordinate AP of the second MLD is the AP indicated by the BSSID in the multiple BSSID set where the subordinate AP of the second MLD is located.
[0376] In one implementation, when the value of the first indication is the first value, it is used to uniformly indicate the first MLD corresponding to the access point AP to perform the first monitoring operation when a multicast frame needs to be received;
[0377] Alternatively, when the value of the first indication is the second value, it is used to uniformly indicate that the first MLD corresponding to the access point AP does not need to perform the first monitoring operation when it needs to receive a multicast frame.
[0378] In one implementation, the first indication is carried by an EMLSR operation indication element.
[0379] In one implementation, the first indication is carried by a first field in an EMLSR operation indication element.
[0380] In one embodiment, the first field includes a second indication;
[0381] When the value of the second indication is a third value, the first field includes the first indication.
[0382] In one implementation, the first indication is an EMLSR operation unified indication.
[0383] In one embodiment, the position of each bit in the first indication is used to indicate an access point AP; the access point AP is an AP corresponding to a second MLD associated with the first MLD; the AP corresponding to the second MLD includes at least one of the following: an AP affiliated with the second MLD, an AP indicated by a BSSID in a multi-BSSID set where the AP affiliated with the second MLD is located;
[0384] The value of each bit in the first indication is used to indicate whether the first MLD corresponding to the access point AP performs the first monitoring operation when a multicast frame needs to be received.
[0385] In one implementation, when the value of each bit in the first indication is the fourth value, it is used to instruct the first MLD corresponding to the access point AP to perform the first monitoring operation when a multicast frame needs to be received;
[0386] Alternatively, when the value of each bit in the first indication is the fifth value, it is used to indicate that the first MLD corresponding to the access point AP does not need to perform the first monitoring operation when it needs to receive a multicast frame.
[0387] In one implementation, the first indication is carried by an EMLSR operation indication element.
[0388] In one implementation, the first indication is carried by a second field in an MLSR operation indication element.
[0389] In one implementation, the second field is a partial EMLSR operation indication bitmap; the partial EMLSR operation indication bitmap is formed by intercepting a portion of continuous bits in the EMLSR operation indication bitmap.
[0390] In one embodiment, the MLSR operation indication element includes a first field;
[0391] When the value of the second indication in the first field is the sixth value, the first field includes a third indication; the third indication is used to indicate the position of a portion of continuous bits intercepted from the EMLSR operation indication bitmap.
[0392] In one implementation, the third indication is a bitmap offset.
[0393] In one implementation, the second indication is the existence of an EMLSR operation unified indication; the existence of the EMLSR operation unified indication is used to indicate whether the first field includes an EMLSR operation unified indication.
[0394] In one implementation, the first field is an EMLSR operation indication bitmap control.
[0395] In one implementation, the EMLSR operation indication element is carried by a management frame.
[0396] In one implementation, the management frame includes a traffic indication map TIM beacon frame.
[0397] In one implementation, the first information is a target initial control frame, which is used to notify that a multicast frame is sent after the target initial control frame.
[0398] In one implementation, the target initial control frame includes an indication duration, where the indication duration is a maximum available duration for the first MLD to switch to the first listening operation.
[0399] In one implementation, the target initial control frame is a variant of a multi-user request to send MU-RTS trigger frame.
[0400] In one implementation, a value of the trigger type subfield of the variant MU-RTS trigger frame is different from a value of the trigger type subfield of the MU-RTS trigger frame.
[0401] In one embodiment, the first receiving capability includes at least one of the following: a first rate, a first modulation and coding strategy MCS, a first spatial stream SS, and a first bandwidth BW;
[0402] And / or, the second receiving capability includes at least one of the following: a second rate, a second modulation and coding strategy MCS, a second spatial stream SS, and a second bandwidth BW; the second receiving capability is the receiving capability of the first station under the second monitoring operation;
[0403] Among them, the first rate is greater than or equal to the second rate; the first MCS is better than or equal to the second MCS; the first SS is greater than or equal to the second SS; and the first BW is greater than or equal to the second BW.
[0404] In one embodiment, the second monitoring operation is used for the target site on the first MLD to monitor the link corresponding to the target site, wherein the target site is a site in an awake state on the first MLD, and the target site has the second receiving capability; the second receiving capability includes at least one of the following: performing a clear channel assessment CCA, and receiving an initial control frame for initiating a frame exchange.
[0405] In one implementation, the sending unit is further configured to send the multicast frame at the following time points:
[0406] The expected time when the multicast frame is sent;
[0407] A time point after a transmission traffic indication map DTIM beacon frame is sent;
[0408] A time point within the broadcast target wake-up time TWT service period SP;
[0409] The time point after the TBTT of the non-STBC DTIM beacon frame where the current count value of the FMS counter field of the specific FMS flow is zero;
[0410] The multicast GCR service period with retry.
[0411] In one implementation, the multicast frame is carried by a physical layer protocol data unit PPDU, and the PPDU includes at least one of the following:
[0412] Orthogonal frequency division multiplexing OFDM physical layer protocol data unit PPDU;
[0413] Non-HT duplicate DUP PPDU;
[0414] Very high throughput VHT PPDU;
[0415] High throughput HT PPDU;
[0416] High efficiency HE single user SU PPDU;
[0417] PPDUs supported by very high throughput EHT site STAs including very high throughput EHT multi-user MU PPDU.
[0418] In one implementation, the first site is a site on the first MLD corresponding to the first link, and the first site is used to monitor the first link; the first link is a link for sending the multicast frame.
[0419] In one implementation, the first MLD and the second MLD are MLDs operating in an enhanced multi-link single radio EMLSR mode, and the first link is a link in an EMLSR link.
[0420] In one implementation, the second MLD is an access point AP MLD, and the first MLD is a non-access point non-AP MLD corresponding to the AP MLD.
[0421] In one implementation, the first multi-link device MLD performs the first monitoring operation when the first multi-link device MLD maintains performing the first monitoring operation, and the first monitoring operation is further used for a second site to monitor a second link in the EMLSR link, the second site is a site on the first MLD, and the second link is a link in the EMLSR link other than the first link;
[0422] or,
[0423] When the first multi-link device MLD performs the first listening operation, which is a switch from the second listening operation to the first listening operation, the first listening operation makes it impossible for the second station to perform listening.
[0424] The second multi-link device 600 of the embodiment of the present application can implement the corresponding functions of the second multi-link device in the aforementioned method embodiment. The corresponding processes, functions, implementation methods and beneficial effects of each module (sub-module, unit or component, etc.) in the second multi-link device 600 can be found in the corresponding description in the aforementioned method embodiment, and will not be repeated here. It should be noted that the functions described by each module (sub-module, unit or component, etc.) in the second multi-link device 600 of the embodiment of the application can be implemented by different modules (sub-module, unit or component, etc.) or by the same module (sub-module, unit or component, etc.).
[0425] The present application scheme is further described in detail below with reference to specific examples. Specifically,
[0426] The present application scheme is mainly aimed at the station (also referred to as the station corresponding to the EMLSR link) on the EMLSR link in the EMLSR mode of the non-AP MLD, and the frame processing problems that may exist when directly receiving multicast frames of higher order or more SSs without receiving the MU-RTS trigger frame in advance. It defines the mechanism for the AP MLD supporting the EMLSR mode (that is, the AP MLD working in the EMLSR mode) to send multicast frames, and defines the mechanism for the non-AP MLD to receive multicast frames in the EMLSR mode; at the same time, it also expands the definition of the monitoring operation of the non-AP MLD on the EMLSR link to meet the reception of multicast frames in special scenarios.
[0427] Here, before specifically introducing the present application solution, the specific definitions of the first listening operation in the EMLSR mode and the second listening operation in the EMLSR mode are first clarified, including:
[0428] The first monitoring operation, i.e., the first monitoring operation in the EMLSR mode, specifically refers to: on the non-AP MLD working in the EMLSR mode, the affiliated station (referred to as the monitoring station, such as the first station) corresponding to a specific link (such as the first link) in the EMLSR link can receive the PPDU sent with a higher rate / higher MCS / more SSs / higher BW;
[0429] Here, the PPDU may be at least one of the following: OFDM PPDU, non-HT DUP PPDU, VHT PPDU, HTPPDU, HE SU PPDU, and PPDU supported by EHT STA including EHT MU PPDU, so as to ensure that the non-AP MLD can correctly receive the PPDU using at least one of the following parameters and carrying the multicast frame. The parameters include: higher rate, higher MCS, more SS and higher BW.
[0430] There are two ways for non-AP MLD to enter the first listening operation in EMLSR mode:
[0431] (1) Under the first monitoring operation, the subsidiary station (such as the first station) can enter the monitoring state corresponding to the frame exchange processing of the specific link (such as the first link) in the EMLSR link; that is, under the first monitoring operation, the frame receiving capability (also referred to as the frame processing capability) of the subsidiary station (such as the first station) corresponding to the specific link (such as the first link) is consistent with the frame exchange processing capability of the specific link; that is, under the first monitoring operation, the subsidiary station corresponding to the specific link (such as the first link) can receive multicast frames sent with a higher rate / higher MCS / more SS / higher BW. Moreover, in this state, other links in the EMLSR link except the specific link (such as the first link) cannot be monitored, that is, other links except the specific link cannot send or receive frames.
[0432] (2) Under the first monitoring operation, the subsidiary site (such as the first site) where the specific link (such as the first link) in the EMLSR mode is located has the ability to receive PPDU (carrying multicast frames) sent with a higher rate / higher MCS / higher BW / more SSs. Therefore, all the subsidiary sites (such as the second site) in the EMLSR link that are in the awake state can be kept in the monitoring state.
[0433] Correspondingly, the second listening operation in the EMLSR mode, that is, the non-AP MLD enters the second listening operation in the EMLSR mode, specifically refers to: on the non-AP MLD working in the EMLSR mode, all the affiliated sites in the awake state (also referred to as listening sites, such as the target site) corresponding to the EMLSR link are in the listening state; wherein, the receiving capability (that is, the second receiving capability) of each site corresponding to the EMLSR link is limited, except for the reception of initial control frames such as CCA or MU-RTS trigger frames, other types of frames cannot be correctly received due to limitations on capabilities such as rate / MCS / SS / BW.
[0434] On the basis of clarifying the first monitoring operation and the second monitoring operation, four specific methods for implementing the first monitoring operation are given, which are:
[0435] Method 1: The non-AP MLD working in the EMLSR mode performs a first listening operation at the expected multicast frame sending time point, or before the expected multicast frame sending time point, to monitor the link (that is, the first link) where the multicast frame is scheduled to be sent in the EMLSR link. For example, the non-AP MLD working in the EMLSR mode enters the first listening operation of the link where the multicast frame is scheduled to be sent in the EMLSR link before the expected multicast frame sending time point, that is, performs the first listening operation in advance to monitor the link (that is, the first link) where the multicast frame is scheduled to be sent in the EMLSR link. Furthermore, the non-AP MLD working in the EMLSR mode can receive multicast frames through the first link when performing the first listening operation, and switch to the second listening operation after confirming that the multicast frame has been received. That is, when the non-AP MLD is associated with an AP MLD that supports the EMLSR mode, and the non-AP MLD operates in the EMLSR mode on the EMLSR link, if a multicast frame is scheduled to be transmitted on a link (for example, the first link) in the EMLSR link corresponding to the non-AP MLD, and a site (set as site A, i.e., the first site) on the link (for example, the first link) on the non-AP MLD is ready to receive the multicast frame, the non-AP MLD needs to ensure that it enters the first listening operation in advance at or before the expected multicast frame sending time point, so that site A listens to the link (i.e., the first link) that transmits the multicast frame, so as to correctly receive the multicast frame.
[0436] Here, for the transmitter of the multicast frame, the method for the AP MLD's subordinate AP to schedule the sending of the cached multicast frame may adopt at least one of the following:
[0437] (1) The AP affiliated with the AP MLD schedules the sending of the cached multicast frame at the expected multicast frame sending time point; here, the expected multicast frame sending time point may be any pre-agreed time point, and the present application solution does not impose any limitation on this.
[0438] (2) The AP affiliated with the AP MLD schedules the sending of the buffered multicast frame after sending the DTIM beacon frame (beacon); for example, the AP schedules the sending of the buffered multicast frame after each DTIM beacon frame (beacon).
[0439] (3) The subordinate APs of AP MLD schedule the sending of multicast frames within the broadcast TWT service period SP; for example, an subordinate AP of AP MLD is a TWT scheduling AP, and the TWT scheduling AP schedules the sending of cached multicast frames within the broadcast TWT service period SP during the beacon interval (beaconinterval) during which the DTIM beacon frame is sent.
[0440] (4) Using a specific flexible multicast service FMS to send the cached multicast frame; for example, scheduling the sending of the cached multicast frame at a time point after the TBTT of a non-STBC DTIM beacon frame whose current count value in the FMS counter field of the specific flexible multicast service FMS flow is zero.
[0441] (5) Using GCR to send cached multicast frames. For example, within the GCR service period, the cached multicast frames are scheduled to be sent.
[0442] Accordingly, in the method for scheduling the sending of cached multicast frames by the subordinate AP based on AP MLD, the expected multicast frame sending time point may be any pre-agreed time point, and may also be obtained based on the following method:
[0443] First, the target beacon sending time TBTT of the expected transmission traffic indication diagram DTIM beacon frame; at this time, the expected multicast frame sending time point is later than the TBTT of the DTIM beacon frame. At this time, the non-AP MLD performs the first monitoring operation at the TBTT of the expected DTIM beacon frame, or at a time point before the TBTT of the expected DTIM beacon frame.
[0444] Second, the start time of the broadcast target wake-up time TWT service period SP for sending the expected multicast frame; at this time, the expected multicast frame sending time point is within the broadcast TWT service period SP. At this time, the non-AP MLD performs the first monitoring operation at the start time of the broadcast target wake-up time TWT service period SP for sending the expected multicast frame, or at a time point before the start time.
[0445] Third, the TBTT of the non-STBC DTIM beacon frame of the FMS counter field of the specific flexible multicast service FMS stream whose current count value is zero; at this time, the expected multicast frame sending time point is later than the TBTT of the non-STBC DTIM beacon frame of the FMS counter field of the FMS stream whose current count value is zero. At this time, the non-AP MLD performs the first monitoring operation at the TBTT of the non-STBC DTIM beacon frame of the FMS counter field of the specific FMS stream whose current count value is zero, or at a time point before the TBTT of the non-STBC DTIM beacon frame of the FMS counter field of the specific FMS stream whose current count value is zero.
[0446] Fourth, the start time of the multicast GCR service period with retry for sending multicast frames is expected; at this time, the expected multicast frame sending time point is within the GCR service period. At this time, the non-AP MLD performs the first monitoring operation at the start time of the multicast GCR service period with retry for sending multicast frames, or at a time point before the start time.
[0447] For example, when the AP MLD schedules the sending of the cached multicast frame through a certain link (such as the first link) in the EMLSR link after the DTIM beacon frame, the non-AP MLD working in the EMLSR mode will first enter the first monitoring operation of the link where the multicast frame is scheduled to be sent (such as the first link) at or before the expected DTIM beacon frame TBTT, that is, perform the first monitoring operation at or before the expected DTIM beacon frame TBTT to monitor the link where the multicast frame is scheduled to be sent (that is, the first link). Subsequently, after receiving the DTIM beacon frame, the non-AP MLD working in the EMLSR mode maintains the first monitoring operation for the link where the multicast frame is scheduled to be sent (such as the first link) (that is, maintains the frame exchange operation state), that is, maintains the first monitoring operation to maintain monitoring of the link where the multicast frame is scheduled to be sent (such as the first link) until the reception of the multicast frame is completed. Furthermore, when the non-AP MLD receives an indication, for example, the More Data subfield of the multicast frame sent by the AP of the first link is 0, it confirms that there are no more multicast frames and returns from the first monitoring operation (also called frame exchange operation) to the second monitoring operation in the EMLSR mode.
[0448] For another example, when the AP MLD schedules the sending of cached multicast frames within the broadcast TWT service period or the GCR service period, the non-AP MLD working in the EMLSR mode will first enter the first listening operation of the link where the multicast frame is scheduled to be sent (such as the first link) in advance at or before the start time of the expected broadcast TWT service period or the GCR service period for the scheduled sending of the multicast frame, that is, enter the first listening operation in advance to monitor the link where the multicast frame is scheduled to be sent (such as the first link). Subsequently, after receiving the DTIM beacon frame, the non-AP MLD working in the EMLSR mode maintains the first listening operation for the link where the multicast frame is scheduled to be sent (such as the first link) (that is, maintains the frame exchange operation state), that is, maintains the first listening operation to maintain monitoring of the link where the multicast frame is scheduled to be sent (such as the first link) until the reception of the multicast frame is completed. Further, when the non-AP MLD receives an indication confirming that there is no multicast frame (i.e., the multicast frame has been received), the non-AP MLD returns from the first listening operation (i.e., the frame exchange operation) to the second listening operation under the EMLSR mode; or, when the end time point of the broadcast TWT service period or the GCR service period (SP) is reached and there is no multicast frame being received, it returns from the first listening operation to the second listening operation under the EMLSR mode.
[0449] Method 2: When a non-AP MLD working in the EMLSR mode is preparing to receive a multicast frame on a link in the EMLSR link, it can first enter the second listening operation before the TBTT of the DTIM beacon frame, and after receiving the DTIM beacon frame and before the expected time point of the multicast frame scheduling and sending, switch from the second listening operation to the first listening operation, so that the first site of the first MLD monitors the link (such as the first link) where the multicast frame is scheduled to be sent in the EMLSR link, and receives the multicast frame through the link until the reception of the multicast frame is completed. If the non-AP MLD receives an indication confirming that there are no more multicast frames, it can be considered that the reception is completed, and then return from the first listening operation (that is, the frame exchange operation) to the second listening operation.
[0450] It can be understood that after the AP MLD sends the DTIM beacon frame on the EMLSR link and before the starting time point of scheduling the sending of the multicast frame, it is necessary to reserve sufficient time. In this way, it can be ensured that the non-AP MLD associated with the AP MLD working in the EMLSR mode switches to the first listening operation of the link (such as the first link) where the multicast frame is scheduled to be sent in the EMLSR link after receiving the DTIM beacon frame and before the time point of sending the multicast frame.
[0451] Furthermore, when the non-AP MLD receives an indication, for example, the More Data subfield of the multicast frame sent by the AP of the first link is 0, it confirms that there are no more multicast frames and returns from the first monitoring operation (also called frame exchange operation) to the second monitoring operation in the EMLSR mode.
[0452] Method three: AP MLD sends a management frame (such as a TIM beacon frame) carrying an EMLSR operation indication element, wherein the EMLSR operation indication element can indicate whether the non-AP MLD (associated with the AP MLD corresponding to the AP) working in EMLSR mode corresponding to the AP needs to perform a first listening operation with a higher rate / higher MCS / more SS / higher BW receiving capability (that is, the first receiving capability) and located in the link where the AP is located (such as the first link) when the AP has a multicast frame cache (that is, when the site corresponding to the AP needs to receive the multicast frame). Furthermore, after obtaining the EMLSR operation indication element, the non-APMLD working in the EMLSR mode determines whether to perform the first listening operation in advance when intending to receive the multicast frame (that is, it needs to receive it) according to the value meaning of the EMLSR operation indication element, for example, determines whether to perform the first listening operation at or before the expected multicast frame sending time point.
[0453] Furthermore, when the non-AP MLD receives an indication, for example, the More Data subfield of the multicast frame sent by the AP of the first link is 0, it confirms that there are no more multicast frames and returns from the first monitoring operation (also called frame exchange operation) to the second monitoring operation in the EMLSR mode.
[0454] Mode 4: When an AP MLD working in the EMLSR mode is expected to send a multicast frame at a higher rate / higher MCS / more SSs / higher BW, before sending the multicast frame, a target initial control frame that does not require a reply, such as a variant MU-RTS trigger frame, can be sent in advance to inform (such as informing the non-APMLD associated with the AP MLD working in the EMLSR mode, and the non-AP MLD also works in the EMLSR mode) to send a multicast frame after the target initial control frame, and the sent multicast frame uses a higher rate / higher MCS / more SSs / higher BW; at the same time, the target initial control frame can carry a specified padding (bit filling) duration (that is, an indication duration) to ensure that the non-AP MLD working in the EMLSR mode has enough time to switch to the first listening operation in advance on a specific link in the EMLSR link (that is, the link that sends the multicast frame, such as the first link), so as to receive the multicast frame normally.
[0455] Furthermore, when the non-AP MLD receives an indication, for example, the More Data subfield of the multicast frame sent by the AP of the first link is 0, it confirms that there are no more multicast frames and returns from the first monitoring operation (also called frame exchange operation) to the second monitoring operation in the EMLSR mode.
[0456] The present application scheme is further described in detail below with reference to specific examples. Specifically,
[0457] FIG. 7(A) is a schematic diagram of an implementation process of a communication method according to an embodiment of the present application in a specific example Figure 1 ; As shown in FIG. 7(A), the non-AP MLD enters the first listening operation before the TBTT of the DTIM beacon frame, specifically:
[0458] After the multi-link establishment process, non-AP MLD is associated with AP MLD, and the two associated links are Link 1 (Link1) and Link 2 (Link2). The two ends of Link1 are AP MLD's subordinate AP1 and non-AP MLD's station 1 (STA1), that is, the link between AP1 and STA1 is Link1.
[0459] The two ends of Link2 are AP2, an AP MLD subsidiary, and STA2, a non-AP MLD. That is, the link between AP2 and STA3 is Link2.
[0460] Here, the AP MLD supports the EMLSR mode, and the non-AP MLD operates in the EMLSR mode on the EMLSR links (eg, Link1 and Link2).
[0461] When AP MLD is expected to schedule the sending of a cached multicast frame (Groupcast) after sending a DTIM beacon frame through Link1 in the EMLSR link, the non-AP MLD working in the EMLSR mode first enters the first listening operation of the link (i.e., Link1) where the multicast frame is scheduled to be sent before the TBTT of the expected DTIM beacon frame, so that the STA1 has a stronger first receiving capability and enables the STA1 to monitor Link1; after receiving the DTIM beacon frame, the non-AP MLD working in the EMLSR mode maintains the first listening operation (also called maintaining the frame exchange operation) of the link (i.e., Link1) where the multicast frame is scheduled to be sent until the reception of the multicast frame is completed; here, the APMLD sends the multicast frame on Link1 through AP1.
[0462] Further, when the non-AP MLD receives the indication confirmation that there are no more multicast frames, it switches from the first monitoring operation to the second monitoring operation of Link 1 and Link 2 in the EMLSR mode after the EMLSR switching delay.
[0463] Here, in the first monitoring operation, that is, the first monitoring operation in the EMLSR mode, the non-AP MLD working in the EMLSR mode, the STA1 corresponding to the specific link in the EMLSR link (Link1 in this example) can receive the PPDU carrying multicast frames sent with a higher rate / higher MCS / more SSs / higher BW.
[0464] Here, the non-AP MLD enters the first monitoring operation of a specific link (Link 1 in this example) in EMLSR mode in two ways:
[0465] (1) Entering the monitoring operation state corresponding to the frame exchange processing of a specific link in the EMLSR link (Link1 in this example), at this time, the affiliated station (STA1 in this example) corresponding to the specific link (Link1 in this example) can receive PPDUs sent with a higher rate / higher MCS / more SS / higher BW, and the receiving capability at this time (that is, the first receiving capability) is consistent with the ability of the specific link to perform frame exchange processing. In this state, other links in the EMLSR link except the specific link (for this example, it can be Link2) cannot perform monitoring operations, that is, cannot send or receive frames.
[0466] (2) In the EMLSR mode, the subsidiary station (STA1 in this example) where the specific link (Link1 in this example) is located has the ability to receive PPDUs sent at a higher rate / higher MCS / more SS / higher BW. Therefore, all subsidiary stations in the EMLSR link that are in the awake state (such as STA2) can be kept in the listening state. At this time, the subsidiary station in the awake state (such as STA2) can have the same or different receiving capability as STA1. This application does not limit this. As long as STA1 has the ability to receive multicast frames sent at a higher rate / higher MCS / higher BW / more SS, it falls within the protection scope of this application.
[0467] The second listening operation in the EMLSR mode means that for the non-AP MLD working in the EMLSR mode, all the affiliated stations in the awake state (referred to as listening stations, such as Link1 and Link2) in the EMLSR link are in the listening state; wherein, the listening operation capability of each station in the EMLSR link, such as Link1 and Link2, is limited. Except for the reception of initial control frames such as CCA and MU-RTS, other types of frames may not be correctly received due to the limitation of rate / MCS / SS / BW capabilities.
[0468] Here, the first monitoring operation and the second monitoring operation can refer to the above description, which will not be repeated here.
[0469] The EMLSR first switching delay refers to the switching time length for the non-AP MLD operating in the EMLSR mode to switch from a first monitoring operation in the EMLSR link to a second monitoring operation on the EMLSR link (including multiple links).
[0470] FIG. 7(B) is a second schematic diagram of an implementation flow of a communication method according to an embodiment of the present application in a specific example; as shown in FIG. 7(B), the non-AP MLD performs a first monitoring operation after receiving a DTIM beacon frame and before scheduling a multicast frame to be sent, specifically:
[0471] After the multi-link establishment process, non-AP MLD is associated with AP MLD. The two associated links are Link 1 (Link1) and Link 2 (Link2). The two ends of Link1 are AP1, which is an AP MLD subsidiary, and STA1 (STA1) of non-AP MLD, that is, the link between AP1 and STA1 is Link1. The two ends of Link2 are AP2, which is an AP MLD subsidiary, and STA2 (STA2) of non-AP MLD, that is, the link between AP2 and STA3 is Link2.
[0472] Here, the AP MLD supports the EMLSR mode, and the non-AP MLD operates in the EMLSR mode on the EMLSR links (eg, Link1 and Link2).
[0473] When AP MLD expects to schedule the sending of multicast frames on Link1 and after sending the DTIM beacon frame, sufficient time is reserved between the end time point of sending the DTIM beacon frame and the start time point of sending the multicast frame, that is, the time length between the end time point of sending the DTIM beacon frame and the start time point of sending the multicast frame is greater than or equal to the EMLSR second switching delay, so as to ensure that the non-AP MLD working in EMLSR mode switches to the first listening operation of the link where the multicast frame is scheduled to be sent in the EMLSR link (Link1 in this example) after receiving the DTIM beacon frame and before the start time point of sending the multicast frame.
[0474] Here, the second switching delay refers to the switching time length for the non-AP MLD working in the EMLSR mode to switch from the second monitoring operation in the EMLSR link to the first monitoring operation.
[0475] Specifically, when the non-AP MLD working in the EMLSR mode is expected to receive a cached multicast frame scheduled to be sent after the DTIM beacon frame on Link1, it first enters the second listening operation of the multilinks (i.e., Link1 and Link2) on the EMLSR link at or before the TBTT of the expected DTIM beacon frame, and then enters the first listening operation on Link1 at or before the time point when the multicast frame starts to be sent after receiving the DTIM beacon frame, and maintains the first listening operation on Link1 to receive the multicast frame on Link1 until the reception of the multicast frame is completed. When the non-AP MLD receives an indication confirming that there are no more multicast frames, it switches from the first listening operation to the second listening operation of the multilinks (Link1 and Link2) in the EMLSR mode after the first switching delay of EMLSR.
[0476] Here, the first monitoring operation, the second monitoring operation and the EMLSR first conversion delay can refer to the above description and will not be repeated here.
[0477] FIG. 7(C) is a schematic diagram of an implementation process of a communication method according to an embodiment of the present application in a specific example Figure 3 As shown in FIG. 7(C), the non-AP MLD enters the first monitoring operation before / at the start time of the broadcast TWT service period, specifically:
[0478] After the multi-link establishment process, non-AP MLD is associated with AP MLD. The two associated links are Link 1 (Link1) and Link 2 (Link2). The two ends of Link1 are AP1, which is an AP MLD subsidiary, and STA1 (STA1) of non-AP MLD, that is, the link between AP1 and STA1 is Link1. The two ends of Link2 are AP2, which is an AP MLD subsidiary, and STA2 (STA2) of non-AP MLD, that is, the link between AP2 and STA3 is Link2.
[0479] Here, AP MLD supports EMLSR mode, and non-AP MLD operates in EMLSR mode on EMLSR links (such as Link1 and Link2). A station such as STA1 on the EMLSR link on the non-AP MLD establishes a broadcast TWT with an AP such as AP1 associated with the AP MLD, and STA1 is the scheduled station for the broadcast TWT service period. AP1 schedules the sending of cached multicast frames during the broadcast TWT service period.
[0480] When the AP MLD, through the link Link1 in the EMLSR link, is expected to schedule the sending of cached multicast frames during the broadcast TWT service period within the beacon interval of sending DTIM beacon frames, the non-AP MLD working in the EMLSR mode first enters the first listening operation of the link (i.e., Link1) where the multicast frame is scheduled to be sent before / at the start time of the broadcast TWT service period; then, the first listening operation is maintained during the broadcast TWT service period, and the multicast frame is received until the reception of the multicast frame is completed. Further, when the non-AP MLD receives an indication confirming that there are no more multicast frames or reaches the end time point of the broadcast TWT service period, the non-AP MLD switches to the second listening operation of the multiple links (i.e., Link1 and Link2) in the EMLSR mode after the first conversion delay of the EMLSR.
[0481] Here, the first monitoring operation, the second monitoring operation and the EMLSR first conversion delay can refer to the above description and will not be repeated here.
[0482] FIG. 7(D) is a schematic diagram of an implementation process of a communication method according to an embodiment of the present application in a specific example Figure 4 ; As shown in FIG. 7(D), the non-AP MLD operates based on the EMLSR indication element and enters the first listening operation after the DTIM beacon frame.
[0483] First, the EMLSR operation indication elements are explained; the details are as follows:
[0484]
[0485] Table 5
[0486]
[0487] Table 6(A)
[0488]
[0489] Table 6(B)
[0490] As shown in Table 5, the EMLSR operation indication element includes an element ID, a length, and an element ID extension; here, the element ID, the length, and the element ID extension all occupy 1 byte, and the specific definition may be similar to the definition in the relevant standard. Further, the EMLSR operation indication element also includes an EMLSR operation indication bitmap control, which also occupies 1 byte.
[0491] In this example, based on the structures shown in Table 5, Table 6 (A) and Table 6 (B), two methods can be used to indicate whether to perform the first monitoring operation when a multicast frame needs to be received, specifically:
[0492] First way:
[0493] As shown in Table 6 (B), the EMLSR operation indication bitmap control includes: EMLSR operation unified indication exists (EMLSR Operation for ALL Indicator Present). When the value of the EMLSR operation unified indication exists is 1, the EMLSR operation indication bitmap control also includes: EMLSR operation unified indication (EMLSR Operation for ALL Indicator) and reserved (Reserved). Here, the EMLSR operation unified indication exists, the EMLSR operation unified indication and the reserved occupy 1 bit, 1 bit and 6 bits respectively. Based on this, the EMLSR operation unified indication exists, the EMLSR operation unified indication and the reserved included in the EMLSR operation indication bitmap control occupy a total of one byte.
[0494] As shown in Table 6(A), when the value of the EMLSR operation unified indication existence is 0, the EMLSR operation indication bitmap control also includes: a bitmap offset (Bitmap Offset). Here, the EMLSR operation unified indication existence and the bitmap offset occupy 1 bit and 7 bits respectively. Based on this, the EMLSR operation unified indication existence and the bitmap offset included in the EMLSR operation indication bitmap control occupy a total of one byte.
[0495] Further, the unified indication of EMLSR operation (or the unified indication domain of EMLSR operation) is used to uniformly indicate whether the non-AP MLD corresponding to the AP and working in the EMLSR mode performs a first monitoring operation when a multicast frame needs to be received, and the first monitoring operation is used for the first station corresponding to the AP on the non-AP MLD to have a first receiving capability, so that the first station monitors the link where the AP is located. That is, the unified indication of EMLSR operation is used to uniformly indicate whether the non-AP MLD corresponding to the AP and working in the EMLSR mode performs a first monitoring operation with a receiving capability of a higher rate / higher MCS / more SSs / higher BW (that is, the first receiving capability) and the link where the AP is located (such as the first link) when a multicast frame needs to be received.
[0496] The AP is at least one of the following: an AP affiliated with the AP MLD, an AP indicated by a BSSID in a multiple BSSID set where the AP affiliated with the AP MLD is located. The non-AP MLD is associated with the AP MLD.
[0497] It can be understood that the non-AP MLD corresponding to the AP working in the EMLSR mode can be specifically: the non-AP MLD corresponding to the site (such as the first site) working in the EMLSR mode corresponding to the AP. For example, the non-AP MLD corresponding to AP1 working in the EMLSR mode can be specifically the non-AP MLD corresponding to SAT1 corresponding to AP1.
[0498] Furthermore, when the EMLSR operation unified indication value is 1, it indicates that the non-AP MLD corresponding to the AP working in the EMLSR mode, when it is necessary to receive multicast frames, performs the first listening operation with a receiving capability of higher rate / higher MCS / more spatial streams (SS) / higher BW (that is, the first receiving capability) and the link where the AP is located (such as the first link).
[0499] When the EMLSR operation unified indication value is 0, it means that the non-AP MLD corresponding to the AP working in the EMLSR mode does not need to perform the first listening operation of the link where the AP is located (such as the first link) with a higher rate / higher MCS / more spatial streams (SS) / higher BW receiving capability (that is, the first receiving capability) when receiving multicast frames.
[0500] That is to say, in this method, the EMLSR operation unified indication is used to indicate whether to perform the first listening operation when a multicast frame needs to be received. At this time, the number of bytes of the partial EMLSR operation indication bitmap contained in the EMLSR operation indication element is 0; that is, in this method, the structure of the EMLSR operation indication element is as shown in Table 5 and Table 6 (B). At this time, the number of bytes of the partial EMLSR operation indication bitmap in Table 5 is 0.
[0501] Second way:
[0502] As shown in Table 5, the EMLSR operation indication element also includes a partial EMLSR operation indication bitmap (PartialEMLSR Operation Indicator Bitmap); different from the first method, in this method, the partial EMLSR operation indication bitmap is used to indicate whether to perform the first monitoring operation when a multicast frame needs to be received. That is, in this method, the structure of the EMLSR operation indication element is shown in Table 5 and Table 6 (A), and at this time, the number of bytes of the partial EMLSR operation indication bitmap in Table 5 is any value between 1 and 251.
[0503] Here, the bitmap offset may be similar to the definition of the bitmap offset (Bitmap Offset) field of the TIM element in the relevant standard. The difference is that the bitmap offset (Bitmap Offset) field of the TIM element in the relevant standard corresponds to the traffic indication virtual bitmap (traffic indication virtual bitmap), while the bitmap offset in the present application scheme corresponds to the EMLSR operation indication bitmap.
[0504] Furthermore, a partial EMLSR operation indication bitmap (also referred to as a partial EMLSR operation indication bitmap domain, or field) is formed by intercepting a meaningful portion of continuous bits in the EMLSR operation indication bitmap, and the interception method is consistent with the method of forming a partial traffic marking virtual bitmap of the TIM element in the relevant standards. The partial traffic marking virtual bitmap is formed by intercepting bits at partial continuous positions of the traffic marking virtual bitmap; the difference lies in the different definitions of the bit values of the two.
[0505] Specifically, in the present application, the position of each bit in the EMLSR operation indication bitmap corresponds to an AP, where the AP is at least one of the following: an AP affiliated with an AP MLD, and an AP indicated by a BSSID in a multi-BSSID set where the AP affiliated with the AP MLD is located. In the present application, the definition of the bit positions in the EMLSR operation indication bitmap is consistent with the definition of the correspondence between the AP and the bit position when there is a multicast frame buffer in the traffic marking virtual bitmap of the TIM element in the relevant standard.
[0506] Further, the value of each bit in the EMLSR operation indication bitmap indicates: when there is a multicast frame cache, whether the AP corresponding to the bit needs the non-AP MLD working in the EMLSR mode corresponding to the AP to perform a first listening operation with a higher rate / higher MCS / more SS / higher BW receiving capability (that is, the first receiving capability) and being in the link where the AP is located (such as the first link). In other words, the value of each bit in the EMLSR operation indication bitmap indicates: when the non-AP MLD working in the EMLSR mode corresponding to the AP corresponding to the bit needs to perform a first listening operation with a higher rate / higher MCS / more SS / higher BW receiving capability (that is, the first receiving capability) and being in the link where the AP is located (such as the first link) when receiving multicast frames.
[0507] It is understandable that the non-AP MLD corresponding to the AP working in the EMLSR mode may specifically be: the non-AP MLD corresponding to the site (such as the first site) corresponding to the AP working in the EMLSR mode. The non-AP MLD is associated with the AP MLD.
[0508] Further, when the value of a certain bit in the EMLSR operation indication bitmap is 1, it indicates that the AP corresponding to the bit, when there is a multicast frame buffer, needs the non-AP MLD corresponding to the AP working in the EMLSR mode to perform the first monitoring operation with a higher rate / higher MCS / more SS / higher BW receiving capability and in the link where the AP is located;
[0509] When the value of a bit in the EMLSR operation indication bitmap is 0, it means that the AP corresponding to the bit, when there is a multicast frame cache, does not need the non-AP MLD corresponding to the AP working in the EMLSR mode to perform the first listening operation with a higher rate / higher MCS / more SS / higher BW receiving capability and is in the link where the AP is located.
[0510] Moreover, the EMLSR operation indication element can be carried by a management frame, such as a TIM beacon frame; for example, the EMLSR operation indication element can be added to the frame body of the TIM beacon frame. When the TIM beacon frame carries the EMLSR operation indication element, it indicates that the multicast frame sent by the indicated AP needs to work in the non-AP MLD in the EMLSR mode. When preparing to receive the multicast frame, the operation indicated in the EMLSR operation indication element is performed, so that the multicast frame can be received normally.
[0511] As shown in FIG. 7(D), the non-AP MLD is based on the EMLSR operation indication element and enters the first listening operation after the DTIM beacon frame, specifically including:
[0512] After the multi-link establishment process, non-AP MLD is associated with AP MLD. The two associated links are Link 1 (Link1) and Link 2 (Link2). The two ends of Link1 are AP1, which is an AP MLD subsidiary, and STA1 (STA1) of non-AP MLD, that is, the link between AP1 and STA1 is Link1. The two ends of Link2 are AP2, which is an AP MLD subsidiary, and STA2 (STA2) of non-AP MLD, that is, the link between AP2 and STA3 is Link2.
[0513] Here, the AP MLD supports the EMLSR mode, and the non-AP MLD operates in the EMLSR mode on the EMLSR links (eg, Link1 and Link2).
[0514] When AP1 of AP MLD carries the EMLSR operation indication element in the sent TIM beacon frame, and the EMLSR operation indication element indicates that AP1, when there is a multicast frame cache, needs to work in the non-AP MLD under the EMLSR model and enter the first listening operation with a higher rate / higher MCS / more SS / higher BW receiving capability (ie, the first receiving capability) and is in the link where AP1 is located (ie, Link1).
[0515] Furthermore, when the AP MLD schedules the sending of the cached multicast frame after the DTIM beacon frame through Link1 in the EMLSR link, the non-AP MLD operating in the EMLSR mode first enters the first listening operation of the link (i.e., Link1) where the multicast frame is scheduled to be sent before or before the expected DTIM beacon frame TBTT, and then maintains the first listening operation of the link (i.e., Link1) where the multicast frame is scheduled to be sent after receiving the DTIM beacon frame until the reception of the multicast frame is completed; further, when the non-AP MLD receives an indication confirming that there are no more multicast frames, it switches from the first listening operation to the second listening operation of the multiple links (Link1 and Link2) in the EMLSR mode after the first conversion delay of the EMLSR.
[0516] Furthermore, the AP MLD attached to AP1 carries the EMLSR operation indication element in the TIM beacon frame sent, and indicates that when there is a multicast frame cache, the non-AP MLD working in the EMLSR mode does not need to enter the first listening operation in the link (Link1) where AP1 is located. Further, when the AP MLD schedules to send the cached multicast frame after the subsequent DTIM beacon frame through the link Link1 in the EMLSR link, the non-AP MLD working in the EMLSR mode first enters the second listening operation of the multilink (Link1 and Link1) before or before the TBTT of the expected DTIM beacon frame, and receives the DTIM beacon frame and the multicast frame in the second listening operation until the multicast frame is received.
[0517] Here, the first monitoring operation, the second monitoring operation and the EMLSR first conversion delay can refer to the above description and will not be repeated here.
[0518] FIG. 7(E) is a schematic diagram of an implementation process of a communication method according to an embodiment of the present application in a specific example Figure 5 As shown in FIG. 7 (E), the non-AP MLD enters the first monitoring operation before / at the start time of the broadcast TWT service period, specifically:
[0519] After the multi-link establishment process, non-AP MLD is associated with AP MLD, and the two associated links are Link 1 (Link1) and Link 2 (Link2). The two ends of Link1 are AP MLD's subordinate AP1 and non-AP MLD's station 1 (STA1), that is, the link between AP1 and STA1 is Link1.
[0520] The two ends of Link2 are AP2, an AP MLD subsidiary, and STA2, a non-AP MLD. That is, the link between AP2 and STA3 is Link2.
[0521] Here, AP MLD supports EMLSR mode, and non-AP MLD operates in EMLSR mode on EMLSR links (such as Link1 and Link2). A station such as STA1 on the EMLSR link on the non-AP MLD establishes a broadcast TWT with the AP such as AP1 corresponding to (that is, associated with) the STA1 on the AP MLD, and STA1 is the scheduled station for the broadcast TWT service period. AP1 schedules the sending of cached multicast frames during the broadcast TWT service period.
[0522] AP1, which is affiliated with AP MLD, carries an EMLSR operation indication element in the DTIM beacon frame it sends. The EMLSR operation indication element indicates that when there is a multicast frame cache, non-AP MLD working in EMLSR mode needs to enter the first listening operation with a receiving capability of higher rate / higher MCS / more spatial streams (SS) / higher BW and on the link (Link1) where AP1 is located.
[0523] When the AP MLD schedules the sending of cached multicast frames through the link Link1 in the EMLSR link, which is expected to be located within the beacon interval of sending the DTIM beacon frame and during the broadcast TWT service cycle (the first broadcast TWT service cycle as shown in Figure 7 (E)), the non-AP MLD working in the EMLSR mode first enters the first listening operation of the link (i.e., Link1) where the multicast frame is scheduled to be sent before / at the start time of the broadcast TWT service cycle; then, the first listening operation is maintained during the broadcast TWT service cycle, and the multicast frame is received until the reception of the multicast frame is completed. Further, when the non-AP MLD receives an indication confirming that there are no more multicast frames or reaches the end time point of the broadcast TWT service cycle, the non-AP MLD switches to the second listening operation of the multiple links (Link1 and Link2) in the EMLSR mode after the first conversion delay of the EMLSR.
[0524] Further, the AP MLD attached to AP1 carries an EMLSR operation indication element in the sent DTIM beacon frame, and the EMLSR operation indication element indicates that when there is a multicast frame cache in AP1, the non-AP MLD working in the EMLSR mode does not need to enter the first listening operation in the link (Link1) where AP1 is located. Further, when the AP MLD is expected to schedule the sending of cached multicast frames during the broadcast TWT service cycle (the second broadcast TWT service cycle as shown in Figure 7 (E)) through the link Link1 in the EMLSR link, the non-AP MLD working in the EMLSR mode enters the second listening operation of the multilink (Link1 and Link1) before / at the start time of the broadcast TWT service cycle, and under the second listening operation, receives the multicast frame within the broadcast TWT service cycle until the reception of the multicast frame is completed.
[0525] Here, the first monitoring operation, the second monitoring operation and the EMLSR first conversion delay can refer to the above description and will not be repeated here.
[0526] FIG. 7(F) is a schematic diagram of an implementation process of a communication method according to an embodiment of the present application in a specific example Figure 6 ; As shown in FIG. 7(F), the non-AP MLD performs a first monitoring operation based on the variant MU-RTS trigger frame, specifically:
[0527] Based on the definition of the 802.11be trigger frame format, a variant type of the MU-RTS Variant trigger frame is added, namely, "MU-RTS without Clear To Send (CTS) reply", as shown in Table 7. The MU-RTS Variant trigger frame, that is, the variant MU-RTS trigger frame, is consistent with the MU-RTS except that the trigger type subfield value of the trigger frame variant is different from that of the MU-RTS.
[0528]
[0529] Table 7
[0530] The MU-RTS Variant trigger frame is used to be sent before sending a specific multicast frame (for example, a multicast frame sent using a higher rate / higher MCS / more SS / higher BW), and is used to inform the MU-RTS Variant trigger frame that a multicast frame will be sent after the multicast frame. In addition, according to the requirements of the EMLSR conversion delay (for example, the EMLSR second conversion delay from the second listening operation to the first listening operation), an appropriate padding duration may be added to ensure that the non-APMLD working in the EMLSR operation has sufficient time to switch to the first listening operation in advance on the corresponding link in the EMLSR link, so as to receive the specific multicast frame sent after the MU-RTS Variant trigger frame.
[0531] Specifically, non-AP MLD is associated with AP MLD after the multi-link establishment process, and the two associated links are Link 1 (Link1) and Link 2 (Link2). The two ends of Link1 are AP1, an AP MLD subsidiary, and STA1, a non-APMLD station, that is, Link1 is the link between AP1 and STA1. The two ends of Link2 are AP2, an AP MLD subsidiary, and STA2, a non-AP MLD station, that is, Link2 is the link between AP2 and STA3.
[0532] Here, the AP MLD supports the EMLSR mode, and the non-AP MLD operates in the EMLSR mode on the EMLSR links (eg, Link1 and Link2).
[0533] When AP MLD is attached to AP1 and uses a higher rate / higher MCS / more SSs / higher BW to send a multicast frame, it first sends a target initial control frame that does not require a reply, such as a MU-RTS Variant trigger frame, before sending the multicast frame, to inform the target initial control frame that the multicast frame after the target initial control frame uses a higher rate / higher MCS / more SSs / higher BW. At the same time, the target initial control frame uses a specified padding (bit filling) duration to ensure that the non-AP MLD working in the EMLSR mode has enough time to switch to the first listening operation in advance on a specific link in the EMLSR link, so as to normally receive the multicast frame.
[0534] As shown in FIG7(F), after the first DTIM beacon frame, the MU-RTS variant trigger frame is sent first, and then the multicast frame sent with a higher rate / higher MCS / more SSs / higher BW is sent.
[0535] Regarding the reception of the multicast frame after the first DTIM beacon frame in Figure 7 (F), when the non-AP MLD is preparing to receive the cached multicast frame scheduled to be sent on Link1 after the DTIM beacon frame, it first enters the second listening operation of the multilinks (Link1 and Link2) on the EMLSR link before the expected DTIM beacon frame TBTT; then, after receiving the DTIM beacon frame, it receives the MU-RTS variant trigger frame, and then switches from the second listening operation to the first listening operation of Link1 within the indicated duration of the MU-RTS variant trigger frame, and maintains the first listening operation of Link1 to receive the multicast frame until the reception of the multicast frame is completed; further, when the non-AP MLD receives the indication confirming that there are no more multicast frames, it switches to the second listening operation of the multilinks (Link1 and Link2) in the EMLSR mode after the EMLSR first conversion delay.
[0536] For the reception of the multicast frame after the second DTIM beacon frame in 7(F), when the non-AP MLD is preparing to receive the multicast frame scheduled to be sent after the DTIM beacon frame on Link1, it enters the second listening operation of the multilinks (Link1 and Link2) on the EMLSR link before the expected DTIM beacon frame TBTT, and then receives the DTIM beacon frame and the multicast frame until the multicast frame is received.
[0537] Here, the first monitoring operation, the second monitoring operation and the EMLSR first conversion delay can refer to the above description and will not be repeated here.
[0538] Based on this, the present application scheme defines a mechanism for AP MLD supporting EMLSR mode to send multicast frames, and defines a mechanism for non-AP MLD to receive multicast frames in EMLSR mode. At the same time, the definition of the monitoring operation of non-AP MLD in the EMLSR link is extended to meet the reception of multicast frames in special scenarios.
[0539] It can be understood that the solution of the present application is also applicable to the operation method of the enhanced multi-link multi-radio mode.
[0540] Figure 8 8 is a schematic structural diagram of a communication device 800 according to an embodiment of the present application. The communication device 800 includes a processor 810, and the processor 810 can call and run a computer program from a memory to enable the communication device 800 to implement the method in the embodiment of the present application.
[0541] In a possible implementation, the communication device 800 may further include a memory 820. The processor 810 may call and run a computer program from the memory 820, so that the communication device 800 implements the method in the embodiment of the present application.
[0542] The memory 820 may be a separate device independent of the processor 810 , or may be integrated into the processor 810 .
[0543] In a possible implementation, the communication device 800 may further include a transceiver 830, and the processor 810 may control the transceiver 830 to communicate with other devices, specifically, may send information or data to other devices, or receive information or data sent by other devices.
[0544] The transceiver 830 may include a transmitter and a receiver. The transceiver 830 may further include an antenna, and the number of the antennas may be one or more.
[0545] In a possible implementation, the communication device 800 may be the second multi-link device of the embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the second multi-link device in each method of the embodiment of the present application, which will not be described in detail for the sake of brevity.
[0546] In a possible implementation, the communication device 800 may be the first multi-link device of the embodiment of the present application, and the communication device 800 may implement the corresponding processes implemented by the first multi-link device in each method of the embodiment of the present application, which will not be described in detail for the sake of brevity.
[0547] Fig. 9 9 is a schematic structural diagram of a chip 900 according to an embodiment of the present application. The chip 900 includes a processor 910, and the processor 910 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
[0548] In a possible implementation, the chip 900 may further include a memory 920. The processor 910 may call and run a computer program from the memory 920 to implement the method performed by the first multi-link device or the second multi-link device in the embodiment of the present application.
[0549] The memory 920 may be a separate device independent of the processor 910 , or may be integrated into the processor 910 .
[0550] In a possible implementation, the chip 900 may further include an input interface 930. The processor 910 may control the input interface 930 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.
[0551] In a possible implementation, the chip 900 may further include an output interface 940. The processor 910 may control the output interface 940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.
[0552] In a possible implementation, the chip can be applied to the second multi-link device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the second multi-link device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
[0553] In a possible implementation, the chip can be applied to the first multi-link device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first multi-link device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.
[0554] The chips applied to the second multi-link device and the first multi-link device may be the same chip or different chips.
[0555] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.
[0556] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.
[0557] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM) or a flash memory. The volatile memory may be a random access memory (RAM).
[0558] It should be understood that the above-mentioned memory is exemplary but not restrictive. For example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memory in the embodiments of the present application is intended to include but not limited to these and any other suitable types of memory.
[0559] Fig.10 1 is a schematic block diagram of a communication system 1000 according to an embodiment of the present application. The communication system 1000 includes a first multi-link device 1010 and a second multi-link device 1020. Specifically, it includes:
[0560] A first multi-link device 1010, configured to perform a first monitoring operation, wherein the first monitoring operation is used for a first station on the first multi-link device to receive a multicast frame using a first receiving capability;
[0561] The first multi-link device 1020 is used to send first information, where the first information is used for the first multi-link device to perform a first monitoring operation, where the first monitoring operation is used for a first station on the first multi-link device to receive a multicast frame using a first receiving capability.
[0562] The first multi-link device 1010 can be used to implement the corresponding functions implemented by the first multi-link device in the above method, and the second multi-link device 1020 can be used to implement the corresponding functions implemented by the second multi-link device in the above method. For the sake of brevity, they will not be described in detail here.
[0563] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function in accordance with the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).
[0564] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0565] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0566] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A communication method, include: The first multi-link device MLD performs a first monitoring operation, wherein the first monitoring operation is used for a first station on the first MLD to receive a multicast frame using a first receiving capability.
2. The method according to claim 1, in, The first receiving capability is greater than or equal to a second receiving capability, and the second receiving capability is a receiving capability adopted by the first station when the first MLD performs a second monitoring operation.
3. The method according to claim 1 or 2, in, The first multi-link device MLD performs a first monitoring operation, including: The first MLD performs a first monitoring operation based on the first information.
4. The method according to claim 3, in, The first information is used by the first MLD to perform the first monitoring operation at a target time or before a target time.
5. The method according to claim 4, in, The target time includes a first time point, and the first time point includes at least one of the following: The expected time when the multicast frame is sent; Expected transmission traffic indication diagram DTIM beacon frame target beacon transmission time TBTT; The start time of the broadcast target wake-up time TWT service period SP for sending multicast frames is expected; The TBTT of the non-STBCDTIM beacon frame with the current count value of the FMS counter field of the specific flexible multicast service FMS flow being zero; The start time of the multicast GCR service period with retries for sending multicast frames is expected.
6. The method according to claim 5, in, The first time point is received in advance by the first MLD.
7. The method according to any one of claims 3 to 6, in, The first information is determined based on a first indication; the first indication is used to indicate whether to perform the first monitoring operation when a multicast frame needs to be received.
8. The method according to any one of claims 1 to 7, in, The first receiving capability includes at least one of the following: a first rate, a first modulation and coding strategy MCS, a first spatial stream SS, and a first bandwidth BW; And / or, the second receiving capability includes at least one of the following: a second rate, a second modulation and coding strategy MCS, a second spatial stream SS, and a second bandwidth BW; the second receiving capability is the receiving capability of the first station under the second monitoring operation; Among them, the first rate is greater than or equal to the second rate; the first MCS is better than or equal to the second MCS; the first SS is greater than or equal to the second SS; and the first BW is greater than or equal to the second BW.
9. The method according to any one of claims 1 to 8, in, The first site is a site on the first MLD corresponding to the first link, and the first site is used to monitor the first link; the first link is a link for sending the multicast frame; The first MLD is an MLD working in an enhanced multi-link single-radio EMLSR mode, the first link is a link in an EMLSR link; and the first MLD is a non-access point non-AP MLD.
10. The method according to claim 9, in, When the first multi-link device MLD performs the first monitoring operation, the first monitoring operation is further used for a second site to monitor a second link in the EMLSR link, the second site is a site on the first MLD, and the second link is a link in the EMLSR link other than the first link; or, When the first multi-link device MLD performs the first listening operation, which is a switch from the second listening operation to the first listening operation, the first listening operation makes it impossible for the second station to perform listening.
11. A communication method, include: The second multi-link device MLD sends first information, where the first information is used by the first multi-link device MLD to perform a first monitoring operation, where the first monitoring operation is used by a first station on the first MLD to receive a multicast frame using a first receiving capability.
12. A first multi-link device, include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the first multi-link device executes the method according to any one of claims 1 to 10.
13. A second multi-link device, include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the second multi-link device executes the method according to claim 11.