Communication method and device

Abstract

The invention provides a communication method, first equipment and second equipment. The communication method comprises the following steps: under the condition that first equipment establishes direct communication with second equipment working on the same link, performing frame transmission between the first equipment and the second equipment by adopting enhanced multilink operation; wherein at least one of the first device and the second device is a device supporting the enhanced multi-link operation or a device working in the enhanced multi-link operation. According to the embodiment of the invention, the enhanced multi-link operation can be used under the condition that direct communication is established among a plurality of pieces of equipment, so that the link communication capacity is improved through the enhanced multi-link operation, and the frame transmission efficiency is improved.

Description

Communication method and device Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a communication method and device. Background Art

[0002] Enhanced multi-link operation enables devices to switch spatial streams between different links, improving link communication capacity through spatial multiplexing. This method is achieved by switching available spatial streams on other links to a specific link, enabling multi-spatial stream transmission on the specified link, thereby increasing the communication capacity of a single link. However, this enhanced multi-link operation is not currently effectively used in direct transmission.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a communication method and device that can effectively use enhanced multi-link operation in direct transmission.

[0005] An embodiment of the present application provides a communication method, applied to a first device, the method comprising:

[0006] When the first device establishes direct communication with a second device operating on the same link, frame transmission is performed between the first device and the second device using enhanced multi-link operation;

[0007] At least one of the first device and the second device is a device that supports the enhanced multi-link operation or a device that operates in the enhanced multi-link operation.

[0008] An embodiment of the present application provides a communication method, applied to a second device, the method comprising:

[0009] The second device switches the mode of the enhanced multi-link operation after interacting with the first device for executing any of the above methods with the first capability information.

[0010] An embodiment of the present application provides a communication method, applied to a first device, the method comprising:

[0011] Establishing a direct communication relationship between a first STA attached to the first device and a second STA attached to the second device;

[0012] Performing frame transmission using an enhanced multi-link operation between a first STA attached to the first device and a second STA attached to the second device according to the direct communication relationship;

[0013] The first STA to which the first device is attached sends the sixth frame to the second STA to which the second device is attached in the form of a single link and a single spatial stream.

[0014] An embodiment of the present application provides a communication method, applied to a second device, the method comprising:

[0015] Establishing a direct communication relationship between a first STA attached to the first device and a second STA attached to the second device;

[0016] Performing frame transmission using an enhanced multi-link operation between a first STA attached to the first device and a second STA attached to the second device according to the direct communication relationship;

[0017] The second STA to which the second device is attached receives the sixth frame, which is sent by the first STA to which the first device is attached in the form of a single-link single spatial stream.

[0018] An embodiment of the present application provides a first device, comprising:

[0019] A first transmission unit is configured to, when establishing direct communication with a second device operating on the same link, perform frame transmission between the first device and the second device using an enhanced multi-link operation;

[0020] At least one of the first device and the second device is a device that supports the enhanced multi-link operation or a device that operates in the enhanced multi-link operation.

[0021] An embodiment of the present application provides a second device, comprising:

[0022] The first switching unit is configured to perform mode switching of the enhanced multi-link operation with a first device configured to execute any of the above devices after interacting with the first capability information.

[0023] An embodiment of the present application provides a first device, comprising:

[0024] A first communication unit is configured to establish a direct communication relationship between a first STA attached to the first device and a second STA attached to the second device;

[0025] A sixth transmission unit, configured to perform frame transmission by using an enhanced multi-link operation between the first STA attached to the first device and the second STA attached to the second device according to the direct communication relationship;

[0026] The first STA to which the first device is attached sends the sixth frame to the second STA to which the second device is attached in the form of a single link and a single spatial stream.

[0027] An embodiment of the present application provides a second device, comprising:

[0028] A second communication unit is configured to establish a direct communication relationship between a first STA attached to the first device and a second STA attached to the second device;

[0029] A seventh transmission unit, configured to perform frame transmission by using an enhanced multi-link operation between the first STA attached to the first device and the second STA attached to the second device according to the direct communication relationship;

[0030] The second STA to which the second device is attached receives the sixth frame, which is sent by the first STA to which the first device is attached in the form of a single-link single spatial stream.

[0031] An embodiment of the present application provides a chip for implementing the above-mentioned communication method.

[0032] 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-mentioned communication method.

[0033] An embodiment of the present application provides a computer-readable storage medium for storing a computer program, which enables a device to perform the above-mentioned communication method when the computer program is executed by the device.

[0034] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the above-mentioned communication method.

[0035] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute the above-mentioned communication method.

[0036] In an embodiment of the present application, when a first device establishes direct communication with a second device operating on the same link, enhanced multi-link operation is used to perform frame transmission between the first device and the second device, so that the enhanced multi-link operation can be effectively used in direct transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0038] FIG2 is a schematic diagram of an interaction process of a triggered TXOP sharing mechanism according to an embodiment of the present application.

[0039] FIG3 is a schematic diagram of data transmission between a concurrent dual-radio STA and an AP according to an embodiment of the present application.

[0040] FIG4 is another schematic diagram of concurrent data transmission between a dual-radio STA and an AP according to an embodiment of the present application.

[0041] FIG. 5 is a schematic diagram of data transmission under enhanced multi-link single radio operation according to an embodiment of the present application.

[0042] FIG6 is a schematic diagram of a basic multi-link element structure according to an embodiment of the present application.

[0043] FIG7 is a schematic diagram of the EML capability subfield structure according to an embodiment of the present application.

[0044] FIG8 is a schematic diagram of the EML Control field structure according to an embodiment of the present application.

[0045] FIG9 is a schematic flowchart of a communication method 900 according to an embodiment of the present application.

[0046] FIG10 is a schematic flowchart of a communication method 1000 according to an embodiment of the present application.

[0047] FIG11 is a schematic flowchart of a communication method 1100 according to an embodiment of the present application.

[0048] FIG12 is a schematic flowchart of a communication method 1200 according to an embodiment of the present application.

[0049] FIG13 is a schematic diagram of an interaction scenario taking two links as an example according to an embodiment of the present application.

[0050] FIG14 is a schematic diagram of another interaction scenario taking two links as an example according to an embodiment of the present application.

[0051] FIG. 15 is a schematic diagram of a P2P variant multilink element of the enhanced multilink capability subfield structure according to an embodiment of the present application.

[0052] FIG16 is a schematic diagram of enhanced multi-link capability information interaction according to an embodiment of the present application.

[0053] FIG17 is a schematic diagram of another enhanced multi-link capability information interaction according to an embodiment of the present application.

[0054] FIG18 is a schematic diagram of yet another enhanced multi-link capability information interaction according to an embodiment of the present application.

[0055] FIG19 is a schematic diagram of yet another enhanced multi-link capability information interaction according to an embodiment of the present application.

[0056] FIG20 is a schematic diagram of a control field structure of a multi-link element according to an embodiment of the present application.

[0057] FIG. 21 is a schematic diagram of a P2P variant multi-link element structure according to an embodiment of the present application.

[0058] FIG. 22 is a schematic diagram of an interaction of an EML operation mode declaration according to an embodiment of the present application.

[0059] FIG. 23 is a schematic diagram of another interaction of an EML operation mode declaration according to an embodiment of the present application.

[0060] FIG24 is a schematic diagram of the structure of an MLD EML OM Info list according to an embodiment of the present application.

[0061] 25-27 are schematic diagrams of the MLD Info structure according to an embodiment of the present application.

[0062] FIG. 28 is a schematic diagram of another interaction of an EML operation mode declaration according to an embodiment of the present application.

[0063] FIG29 is a schematic diagram of another interaction of EML operation mode declaration according to an embodiment of the present application.

[0064] FIG30 is a schematic diagram of the structure of a PeerMLD EML OM Info list according to an embodiment of the present application.

[0065] FIG31 is a schematic diagram of another interaction of EML operation mode declaration according to an embodiment of the present application.

[0066] FIG32 is a schematic diagram of another interaction of EML operation mode declaration according to an embodiment of the present application.

[0067] FIG33 is an interactive diagram of an EML link switching according to an embodiment of the present application.

[0068] Figure 34 is a schematic diagram of a trigger frame structure according to an embodiment of the present application.

[0069] FIG35 is a schematic diagram of the structure of the common information field of an EHT variant-trigger frame according to an embodiment of the present application.

[0070] FIG36 is a schematic diagram of the HE MU-RTS TXS user information field structure according to an embodiment of the present application.

[0071] FIG37 is a schematic diagram of the structure of the EHT MU-RTS TXS user information field according to an embodiment of the present application.

[0072] FIG38 is a schematic diagram of using Allocation Duration in User Info to identify a P2P receiver according to an embodiment of the present application.

[0073] FIG39 is a schematic diagram of the Common Info field of the trigger frame of the newly defined EHT variant according to an embodiment of the present application.

[0074] FIG40 is a schematic diagram of using a newly defined field in User Info to identify a P2P receiver according to an embodiment of the present application.

[0075] FIG41 is a schematic diagram of allocating multiple TXOPs at one time based on the OPT1 method according to an embodiment of the present application.

[0076] FIG42 is a schematic diagram of allocating multiple TXOPs at one time based on the OPT2 method according to an embodiment of the present application.

[0077] Figure 43 is an interactive schematic diagram of another EML link switching according to an embodiment of the present application.

[0078] FIG44 is a schematic diagram of the Common Info structure of the MU-RTS frame of the EML variant according to an embodiment of the present application.

[0079] Figure 45 is another interactive schematic diagram of EML link switching according to an embodiment of the present application.

[0080] Figure 46 is a structural diagram of a first device 4600 according to an embodiment of the present application.

[0081] Figure 47 is a structural diagram of a second device 4700 according to an embodiment of the present application.

[0082] Figure 48 is a structural diagram of a first device 4800 according to an embodiment of the present application.

[0083] Figure 49 is a structural diagram of a second device 4900 according to an embodiment of the present application.

[0084] Figure 50 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0085] Figure 51 is a schematic block diagram of a chip according to an embodiment of the present application.

[0086] Figure 52 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

[0087] 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.

[0088] 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.

[0089] For example, a communication system 100 used in an embodiment of the present application is shown in FIG1 . The communication system 100 may include an access point (AP) 110 and a station (STA) 120 that accesses a network through the access point 110 .

[0090] In some scenarios, an AP is also called an AP STA. In a sense, an AP is also a STA.

[0091] In some scenarios, a STA is also called a non-AP STA.

[0092] The communication in the communication system 100 can 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, where a peer STA may refer to a device that communicates with the STA peer, for example, the peer STA may be an AP or a non-AP STA.

[0093] An AP acts as a bridge between wired and wireless networks, connecting wireless network clients and then connecting the wireless network to the Ethernet. An AP can be a terminal device (such as a mobile phone) or a network device (such as a router). This terminal device or network device contains a chip that enables communication, such as a WLAN or WiFi chip.

[0094] 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 AP.

[0095] 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.

[0096] In some embodiments, a non-AP STA may support 802.11be. A 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.

[0097] 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.

[0098] In the embodiment of the present application, the STA may be a mobile phone, tablet computer, computer, virtual reality (VR) device, augmented reality (AR) device, wireless device in industrial control, set-top box, wireless device in self-driving, in-vehicle communication device, wireless device in remote medical, wireless device in smart grid, wireless device in transportation safety, wireless device in smart city or smart home, wireless communication chip / ASIC / SOC / etc. that supports WLAN / WiFi technology.

[0099] The frequency bands supported by WLAN technology may include but are not limited to: low frequency bands (such as 2.4 GHz, 5 GHz, and 6 GHz) and high frequency bands (such as 45 GHz and 60 GHz).

[0100] FIG1 exemplarily shows one AP STA and two non-AP STAs. 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.

[0101] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0102] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" 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 between A and B.

[0103] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0104] 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 relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0105] Wireless LANs (WLANs) are widely used in businesses and homes due to their low cost, flexibility, and scalability. WLAN standardization organizations and vendors have designed and promoted various peer-to-peer (P2P) communication technologies for Wi-Fi networks, such as Wireless Direct (Wi-Fi Direct) and Tunneled Direct-Link Setup (TDLS). These technologies enable Wi-Fi devices to communicate directly, bypassing access points (APs), thereby reducing wireless resource usage and channel overhead.

[0106] Compared to stations (STAs) directly competing for transmission opportunities and performing P2P transmission, requiring APs to assist STAs in competing for channels for P2P transmission increases the probability of the AP successfully acquiring channel access. This can potentially make P2P transmission more timely and facilitates the AP's management of the wireless medium (WM) within its Basic Service Set (BSS). Therefore, a triggered transmission opportunity (TXOP) sharing mechanism, implemented using MU-RTS TXS trigger frames, is designed to support AP-assisted P2P transmission.

[0107] For multi-link operation characteristics, a multi-link device (MLD) is also defined accordingly. An MLD can support multi-band communication and can simultaneously use different channel resources in the same or different frequency bands for communication. These different channel resources are called links or wireless medium links. For example, an MLD can simultaneously use a 20 MHz channel in the 2.4 GHz band, an 80 MHz channel in the 5 GHz band, and a 160 MHz channel in the 6 GHz band. It can be said that the MLD has (or operates) three links.

[0108] To address implementation complexity and cost, a non-AP MLD is permitted to be a single-radio multi-link device (Single Radio MLD). Specifically, although a Single Radio MLD can operate on multiple links, it can only transmit or receive frames on one link at a time. A Single Radio MLD is permitted to operate in Multi-Link Single Radio (MLSR) mode. From the perspective of an AP MLD, this non-AP MLD is active on only one link at a time and is dormant on all other links.

[0109] For enhanced multi-link operation, devices using enhanced multi-link operation do not need to have the ability to transmit multiple spatial streams on each link they operate. Instead, they can implement multi-spatial stream transmission on a designated link by switching available spatial streams on other links to the designated link through a "switching" operation after detecting a specific frame.

[0110] Enhanced multi-link operation is divided into Enhanced Multi-Link Single Radio (EMLSR) and Enhanced Multi-Link Multiple Radio (EMLMR). EMLSR operation can be applied to Single Radio MLDs with multiple available spatial streams (including transmit and / or receive chains). Specifically, a Single Radio MLD with EMLSR mode enabled listens on multiple links simultaneously. When data needs to be received or sent, the spatial streams used for listening on other links are switched to the designated link for reception or transmission in the form of multiple spatial streams. EMLSR enables Single Radio MLDs to obtain more channel access opportunities, thereby improving their throughput and latency performance.

[0111] As shown in Figure 2, STA1, as the P2P initiator, first informs the AP of its P2P transmission requirements. After the AP successfully accesses and obtains a TXOP, it can share part of the TXOP with STA1 by sending a MU-RTS TXS frame. After receiving the MU-RTS TXS frame, STA1 sends a CTS response back if conditions permit, and can then use the allocated time for P2P or uplink transmission.

[0112] Figure 3 illustrates concurrent data transmission between a dual-radio STA and an AP under ideal conditions. Channels 1 and 2 are both available for data transmission, leaving them idle and with no data overlap. However, as the network becomes more busy, as shown in Figure 4, channels 1 and 2 become busy, and data transmission on channels 1 and 2 overlap. This effectively equates to single-link operation, meaning a STA can only transmit data on one link at a time.

[0113] For the scenario shown in Figure 4, Enhanced Multi-Link Single-Radio (EMLSR) operation is proposed for single-radio devices (which can only send or receive data on one link at a time). As shown in Figure 5, a single-radio non-AP MLD (STA) configures its 2x2 transmission module to 1x1 on channel 1 and 1x1 on channel 2, allowing it to listen on both channels simultaneously. Before transmitting downlink data on an idle channel, the AP MLD sends a control frame (such as an RTS frame or MU-RTS frame). Upon receiving the control frame, the non-AP MLD responds with a CTS frame and switches to a 2x2 mode on the link where the initial control frame was received to receive data.

[0114] It should be noted that the non-AP MLD switches from 1x1 listening mode on each link to 2x2 transmission mode on a specific link to implement spatial multiplexing. A device with NxN antenna capability has N spatial streams. Switching from 1x1 listening mode on each link to 2x2 transmission mode on a specific link means switching one spatial stream on one link to another link, allowing the other link to use two spatial streams for data reception.

[0115] For EMLSR listening, non-AP MLD can operate in EMLSR mode on a specific subset of the enabled linkset. Links in this subset are called EMLSR links. Non-AP MLD can listen to EMLSR links by ensuring that the attached STAs operating on the EMLSR links are awake.

[0116] When EMLSR link switching is required, the state switches from the listening operation state to the single-link multi-spatial stream frame exchange operation state.

[0117] For single-link multi-spatial stream frame exchange operation, an AP attached to an AP MLD that initiates a frame exchange with a non-AP MLD on one of the EMLSR links MUST transmit an initial control frame to the non-AP MLD to initiate the frame exchange. The initial control frame MUST be a MU-RTS trigger frame or a BSRP trigger frame. A non-AP MLD in EMLSR mode MUST receive MU-RTS and BSRP trigger frames. After receiving the initial control frame of a frame exchange sequence and transmitting an immediate response to the initial control frame, the non-AP MLD MUST be able to send or receive frames on the link on which the initial control frame was received and MUST NOT send or receive frames on other EMLSR links until the frame exchange sequence completes. Subject to its spatial stream capabilities, operating mode, and link switching latency, the non-AP MLD SHOULD be able to receive Physical Layer Protocol Data Units (PPDUs) sent using multiple spatial streams one SIFS interval after the completion of the transmission of the response frame to the initial control frame request. During the frame exchange sequence, the AP MLD SHOULD NOT send frames to the non-AP MLD on other EMLSR links. After the frame exchange sequence is complete, non-AP MLD switches back to listening operation on the enabled link according to certain rules.

[0118] EML Capabilities information is carried in the Common Info of the Basic Multi-Link Element, as shown in Figure 6. The design of the Enhanced Multi-Link Capabilities subfield is shown in Figure 7. Frames carrying Basic Multi-Link elements can be used for EML capability information exchange, such as Beacon frames, Probe Response frames, Association Request frames, and Association Response frames. It is generally believed that the exchange of capability information occurs during association (Multi-Link Setup).

[0119] After the capability information is exchanged, EMLSR mode is disabled by default. A mechanism is required to notify the other party to enable EMLSR mode and to confirm the notification. This notification is implemented through the EML Operating Mode Notification (OMN) frame. The EML Control field structure in the EML OMN frame is shown in Figure 8.

[0120] If the non-AP MLD changes its EML operation mode, such as enabling EMLSR mode, it sends an EML OMN frame with EMLSR Mode = 1 in the EML Control field to the AP MLD. Upon receiving this frame, the AP MLD can choose to use an EML OMN frame with the same field settings to respond to the EML OMN frame sent by the non-AP MLD. Upon receiving this feedback, the non-AP MLD can immediately proceed and complete the EML operation mode switch. Otherwise, if the non-AP MLD has not received any feedback from the AP MLD on the EML OMN frame, it must wait for the Transition Timeout period negotiated during the capability information exchange before the EML operation mode switch can be performed.

[0121] In summary, enhanced multi-link operation can increase the communication capacity of a single link by temporarily switching available spatial streams (including transmit and / or receive chains) through spatial multiplexing to transmit or receive frames. However, this mechanism cannot currently be effectively used for direct transmission, such as P2P transmission. On the one hand, the standard lacks a detailed description of how this mechanism applies to P2P transmission, and only specifies uplink or downlink transmission for non-AP MLD and AP MLD, without describing the situation specifically for P2P transmission. On the other hand, the switching of available spatial streams (including transmit and / or receive chains) will cause some links to be unavailable during that time period, and the P2P peer device may initiate transmission without being aware of this situation, resulting in a waste of channel resources.

[0122] This application combines a triggered transmission opportunity sharing mechanism with enhanced multi-link operation, and proposes a method for effectively applying the enhanced multi-link operation to P2P communication.

[0123] FIG9 is a schematic flow chart of a communication method 900 according to an embodiment of the present application. The method may optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents:

[0124] S910: When the first device establishes direct communication with a second device operating on the same link, use enhanced multi-link operation to perform frame transmission between the first device and the second device;

[0125] At least one of the first device and the second device is a device that supports the enhanced multi-link operation or a device that operates in the enhanced multi-link operation.

[0126] In some examples, direct communication includes: P2P communication, end-to-end communication, etc.

[0127] In some examples, the first device may be non-AP Device1. Optionally, non-AP Device1 may provide services for a non-AP MLD (such as non-AP MLD2) operating in EMLSR mode. Non-AP Device1 itself may also use EMLSR mode, that is, non-AP Device1 acts as non-AP MLD1 to perform P2P interaction with a peer P2P device (such as non-AP MLD2).

[0128] In some examples, the second device may be a peer P2P device (eg, non-AP MLD2) that performs P2P communication with the first device.

[0129] Using an embodiment of the present application, when a first device establishes direct communication with a second device operating on the same link, enhanced multi-link operation is used to perform frame transmission between the first device and the second device, so that the enhanced multi-link operation can be effectively used in direct transmission (such as P2P transmission).

[0130] In one embodiment, the method further includes: the first device applying for a TXOP from a third device; the third device is configured to share the TXOP with the first device and the second device for the direct communication, and uniformly schedule frame transmission between the first device and the second device within the TXOP sharing time.

[0131] In some examples, the third device may be an AP MLD. The first device, as the initiator of P2P transmission, applies for TXOP from the AP MLD. The AP MLD may share TXOP, use TXOP sharing time for P2P transmission, and uniformly schedule P2P transmission within its BSS.

[0132] In one embodiment, the use of enhanced multi-link operation to perform frame transmission between the first device and the second device includes: when the enhanced multi-link operation is an EMLSR operation, the first device performs single-link multi-spatial stream frame exchange with the second device on one link among multiple links of the second device.

[0133] In some examples, the multiple links include: multiple EMLSR links. In addition, when applied to EMLMR scenarios, the multiple links may also include: multiple EMLMR links.

[0134] In one embodiment, the first device is configured to provide services for the second device operating in the EMLSR mode; the second device is configured to support the EMLSR operation and operate in the EMLSR mode.

[0135] In some examples, at least one of the first device and the second device can use EMLSR mode, where the first device can only provide service capabilities to the peer device, and the second device can only use EMLSR mode. For example, the first device can be non-AP Device 1, which can only provide services to a non-AP MLD (such as non-AP MLD2) operating in EMLSR mode; the second device can be a peer P2P device (such as non-AP MLD2) that performs P2P communication with the first device, where only non-AP MLD2 operates in EMLSR mode.

[0136] In one embodiment, the first device is used to provide services for the second device operating in EMLSR mode, and / or support the EMLSR operation and operate in EMLSR mode; the second device is used to provide services for the first device operating in EMLSR mode, and / or support the EMLSR operation and operate in EMLSR mode.

[0137] In some examples, either the first device or the second device can use the EMLSR mode and can also provide service capabilities to the peer device. For example, the first device can be non-AP Device1, which can provide services to a non-AP MLD (such as non-AP MLD2) operating in EMLSR mode. Non-AP Device1 itself can also use the EMLSR mode, that is, non-AP Device1 acts as non-AP MLD1 and performs P2P interaction with a peer P2P device (such as non-AP MLD2). The second device can be a peer P2P device (such as non-AP MLD2) that performs P2P communication with the first device. Similarly, non-AP MLD2 itself can use the EMLSR mode and can also provide services to the peer P2P device (such as non-AP MLD1).

[0138] In one embodiment, the method further includes: interacting with the first device and the second device to perform first capability information when establishing the direct communication, wherein the first capability is: the ability to support EMLSR operation and provide services to devices operating in EMLSR mode or the ability to operate in EMLSR mode. Optionally, in the EMLSR scenario, switching of the EMLSR mode (such as switching from the default off state of the EMLSR mode to the on state, or switching from the on state to the off state) and switching of the EMLSR link (from the listening operation state to the single-link multi-spatial stream frame exchange operation state) can be performed only after the interaction of the first capability information.

[0139] In one embodiment, the first capability information is carried in a multilink element. The first capability information may be EML capability information, which may be carried in the multilink element when establishing a P2P relationship. In other words, establishing a P2P relationship may include exchanging the EML capability information.

[0140] In some examples, the multi-link element includes at least one of the following methods:

[0141] 1) Method 1: When the multilink element is a basic multilink element, the first capability information is carried through the common information field in the basic multilink element; wherein the subfield of the first capability information includes: a first subfield for indicating the EMLSR mode, and a second subfield for indicating that EMLSR operation is supported in the direct communication; for example, in the subfield of the first capability information (such as EML capability information), the first subfield is the "EMLSR Support" subfield, and the reserved second subfield is the "P2P Support" subfield.

[0142] 2) Method 2: When the multi-link element is a P2P variant multi-link element, the first capability information is carried through the common information field in the P2P variant multi-link element; wherein, the P2P variant multi-link element also includes: a multi-link control field carrying a third subfield, and the third subfield is used to indicate the type of the multi-link element. For example, in the subfield of the first capability information (such as EML capability information), the third subfield is a "Type" subfield.

[0143] Taking the first capability information as EML capability information as an example, the interaction of the EML capability information includes at least various hardware entity interaction scenarios such as between non-AP MLD and AP MLD, between non-AP MLD and non-AP MLD, and between non-AP MLD and EHT non-AP STA.

[0144] In some examples, the first device (e.g., non-AP MLD1) sends a first frame (e.g., an association request frame) to the third device (e.g., AP MLD); the first frame carries a subfield of the first capability information (e.g., EML capability information) so that the third device knows that the first device supports EMLSR operation and can provide services to the second device operating in EMLSR mode.

[0145] In some examples, the first device (e.g., non-AP MLD1) sends a first frame (e.g., an association request frame) to the second device (e.g., non-AP MLD2), in which the first frame carries a subfield of the first capability information (e.g., EML capability information), so that the second device knows that the first device supports EMLSR operation and can provide services to the second device operating in EMLSR mode.

[0146] In some examples, the first device (such as non-AP MLD1) receives a first response frame (such as an association response frame) fed back by the second device (such as non-AP MLD2), and the first response frame carries a subfield of the first capability information (such as EML capability information).

[0147] In one embodiment, the first device provides services for at least one device operating in the EMLSR mode, and / or operates in the EMLSR mode after declaring that the EMLSR mode is enabled.

[0148] In some examples, the first device may be non-AP Device1. Optionally, non-AP Device1 may provide services for a non-AP MLD (such as non-AP MLD2) operating in EMLSR mode. Non-AP Device1 itself may also use EMLSR mode, that is, non-AP Device1 acts as non-AP MLD1 and performs P2P interaction with the peer P2P device (such as non-AP MLD2). After the EMLSR mode is enabled, non-AP Device1 may also operate in EMLSR mode.

[0149] FIG10 is a schematic flow chart of a communication method 1000 according to an embodiment of the present application. The method may optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents:

[0150] S1010: The second device switches the mode of enhanced multi-link operation with the first device for executing any of the above implementation modes after exchanging first capability information.

[0151] In one embodiment, the second device is configured to support mode switching of the enhanced multi-link operation, wherein the enhanced multi-link operation is an EMLSR operation.

[0152] In some examples, the second device can perform the mode switching of the enhanced multi-link operation through the operation mode declaration after interacting with the first device through the first capability information (such as EML capability information). Among the multiple devices of P2P transmission, as long as they can operate in the EMLSR mode after turning on the EMLSR mode, they can all serve as the second device. For example, the first device is non-AP MLD1, and the second device is non-AP MLD2. After interacting with the EML capability information, non-AP MLD2 implements the switching of the EMLSR mode through the operation mode declaration. Optionally, if non-AP MLD1 also supports EMLSR mode switching, non-AP MLD1 can also implement the switching of the EMLSR mode through the operation mode declaration.

[0153] In one embodiment, performing mode switching for enhanced multi-link operation includes: when the second device (e.g., non-AP MLD2) needs to switch to EMLSR mode, sending a second frame (e.g., an EML OMN frame) to the first device (non-AP MLD1), wherein the second frame carries a control field for announcing the EMLSR mode switch; wherein the control field includes the EMLSR mode subfield (e.g., operating mode information). When the second device receives a second response frame fed back by the first device, the EMLSR mode switch is completed, thereby directly announcing the EMLSR mode change between the peer devices (non-AP MLD2 and non-AP MLD1) using an existing mechanism.

[0154] In one embodiment, performing mode switching for enhanced multi-link operation includes: when the second device (e.g., non-AP MLD2) needs to switch to EMLSR mode, sending a second frame (e.g., an EML OMN frame) to the third device (e.g., AP MLD), wherein the second frame carries a control field (e.g., operation mode information) for announcing the EMLSR mode switch; wherein the control field includes the EMLSR mode subfield. When the second device receives a second response frame fed back by the third device, the EMLSR mode switch is completed, so that after receiving the second frame, the AP MLD can proactively announce the EMLSR mode change to its peer device (the peer device of non-AP MLD2 is non-AP MLD1).

[0155] In some examples, the third device (eg, AP MLD) is configured to use a third frame (eg, peer MLD EML operation mode announcement frame) at a first time to announce switching information to other devices associated with the third device and supporting the direct communication with the second device.

[0156] In some examples, the first time is any time after the EMLSR mode switching is completed and before the shared TXOP is triggered to perform the direct communication.

[0157] In one embodiment, the method further includes: when the second device (e.g., non-AP MLD2) needs to switch to EMLSR mode, sending a fourth frame (e.g., a peer MLD EML operation mode request frame) to the third device (e.g., AP MLD), requesting the third device to announce the EML operation mode of other devices performing direct communication with the second device. The third device is configured to respond to the request by using a third frame (e.g., a peer MLD EML operation mode announcement frame) to announce the switching information to other devices associated with the third device and supporting direct communication with the second device. Thus, after receiving the fourth frame, the AP MLD can passively announce the EMLSR mode change to the peer device (the peer device of non-AP MLD2 is non-AP MLD1).

[0158] In one embodiment, the third frame carries first information; wherein the first information includes: a fourth subfield for indicating the corresponding identity information of the device with peer EML capability, and a fifth subfield for indicating the corresponding EMLSR mode of the device with peer EML capability.

[0159] In some examples, the third frame may be a peer MLD EML operation mode announcement frame; the first information may be a Peer MLD EML OM Info list; the fourth subfield may be an MLD Info subfield (specifically used to indicate the identity information of a certain MLD); and the fifth subfield may be an EML Control field (specifically used to indicate the EML operation mode corresponding to the non-AP MLD in the Peer MLD EML OM Info list).

[0160] In some examples, the corresponding identity information of the device with peer EML capability includes: a MAC address, and / or an AID assigned when associated with the third device.

[0161] In one embodiment, the fourth frame is a frame of a different type from the third frame. In other words, the fourth frame is a peer MLD EML operation mode request frame, and the third frame is a peer MLD EML operation mode announcement frame. The fourth frame carries a field indicating that the current frame belongs to a request frame of a device with peer EML capabilities. In this case, the fourth frame is only a peer MLD EML operation mode request frame.

[0162] In one embodiment, the fourth frame may also be a frame of the same type as the third frame. In other words, the fourth frame may function as either a peer-to-peer MLD EML operation mode request frame or a peer-to-peer MLD EML operation mode announcement frame, using an indication field. The fourth frame may include a field indicating whether the current frame belongs to a request frame or an announcement frame of a device with peer EML capabilities. In this case, depending on the indication field, the fourth frame may function as either a peer-to-peer MLD EML operation mode request frame or a peer-to-peer MLD EML operation mode announcement frame.

[0163] In one embodiment, the fourth frame includes: a first value and first information.

[0164] In some examples, the first value is used to identify the interaction of the EML capability information. For example, the first value may be the value of the Dialog Token field. The value of the Dialog Token field is selected as a "non-zero value" to identify the interaction.

[0165] In some examples, the first information includes: a fourth subfield for indicating identity information corresponding to a device with peer EML capabilities, and a fifth subfield for indicating an EMLSR mode corresponding to a device with peer EML capabilities.

[0166] In some examples, the first information may be a Peer MLD EML OM Info list; the fourth subfield may be an MLD Info subfield (specifically used to indicate the identity information of a certain MLD); and the fifth subfield may be an EML Control field (specifically used to indicate the EML operation mode corresponding to the non-AP MLD in the Peer MLD EML OM Info list).

[0167] In some examples, the corresponding identity information of the device with peer EML capability includes: a MAC address, and / or an AID assigned when associated with the third device.

[0168] FIG11 is a schematic flow chart of a communication method 1100 according to an embodiment of the present application. The method may optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents:

[0169] S1110: Establish a direct communication relationship between a first STA attached to a first device and a second STA attached to a second device;

[0170] S1120: Perform frame transmission using enhanced multi-link operation between a first STA attached to the first device and a second STA attached to the second device according to the direct communication relationship.

[0171] In some examples, the first STA (STA11) attached to the first device (eg, non-AP MLD1) sends a sixth frame to the second STA (STA21) attached to the second device (eg, non-AP MLD2) in the form of a single link and a single spatial stream.

[0172] In some examples, a first STA attached to the first device (eg, non-AP MLD1) and a second STA attached to the second device (eg, non-AP MLD2) operate on the same link.

[0173] The first STA to which the first device is attached may be STA11, and the second STA to which the second device is attached may be STA21. STA11 sends a sixth frame (eg, MU-RTS) to STA21 in the form of a single-link single spatial stream.

[0174] In the following description, the first device (such as non-AP MLD1), the second device (such as non-AP MLD2), the first STA attached to the first device (such as STA11), the second STA attached to the second device (such as STA21), the third device (such as AP MLD), the fifth frame can be a trigger frame such as a MU-RTS TXS frame, the sixth frame can be an initial control frame such as MU-RTS, and the feedback frame can be CTS. Examples are described and no further details are given.

[0175] It should be noted that both the fifth and sixth frames are control frames. The fifth frame, as a trigger frame, is actually also a type of control frame. CTS can be used as a feedback frame for the fifth frame or the sixth frame. In this application, CTS is used as an example of a feedback frame.

[0176] It should be noted that the transmission and parsing of interactive information, such as frames, are specifically performed by the device's affiliated STAs (e.g., STA11 or STA21), while the processing or actions to complete the operation (e.g., link switching) are performed by the device itself. For example, if at least one of non-AP MLD1 and non-AP MLD2 operates in EMLSR mode, link switching is performed by non-AP MLD1 or non-AP MLD2.

[0177] The P2P initiator is the first device, and the EMLSR operation scenario for sending the initial control frame is as follows:

[0178] In one embodiment, the method further includes: a first STA attached to the first device requests a required TXOP time from the third device; the first STA attached to the first device receives a fifth frame sent by the third device, wherein the third device is configured to share the TXOP time with the first STA attached to the first device in TXOP sharing mode 2. Regarding TXOP sharing mode 2, a triggered TXOP sharing mechanism has two operating modes: TXOP sharing mode 1 only allows a non-AP STA that obtains a TXOP to use the TXOP for uplink transmission, while TXOP sharing mode 2, in addition to mode 1, also allows a non-AP STA to use the TXOP for P2P transmission with other peer non-AP STAs.

[0179] In one embodiment, the method further includes: a first STA attached to the first device and a second STA attached to the second device are both capable of receiving and parsing the fifth frame on their respective working EMLSR link sets.

[0180] In one embodiment, the method further includes: while the first STA to which the first device is attached sends the sixth frame to the second STA to which the second device is attached, the first device performs EMLSR link switching.

[0181] In one embodiment, the method further includes: the first device performs EMLSR link switching within the time period corresponding to the reception and feedback of the fifth frame by the first STA attached to the first device, and / or within the time period of sending the sixth frame to the second STA attached to the second device and receiving feedback of the sixth frame.

[0182] In one embodiment, the sixth frame carries padding information, and the padding information satisfies at least one of the following conditions:

[0183] 1) The switching delay requirement of the second device;

[0184] 2) the switching delay requirement of the first device;

[0185] 3) Handover delay requirement between the second device and the first device.

[0186] The EMLSR operation scenario in which the P2P initiator is the first device and sends an initial control frame to perform EMLSR link switching is as follows:

[0187] In one embodiment, the method further includes: a first STA attached to the first device requests a required TXOP time from the third device, and indicates first identity information; wherein the first identity information is identity information of a second STA attached to the second device, and the second STA attached to the second device is associated with the third device and exchanges each other's EML capability information.

[0188] The P2P initiator is the first device, and the EMLSR operation scenario using MU-RTS TXS or a variant of MU-RTS to instruct EMLSR link switching is as follows:

[0189] In one embodiment, the method further includes: a first STA attached to the first device receives a fifth frame or a variant of the fifth frame sent by the third device, wherein the third device is configured to share the TXOP time with at least one of the first STA attached to the first device and the second STA attached to the second device in TXOP sharing mode 2.

[0190] In some examples, the fifth frame or a variant of the fifth frame is used to allocate a TXOP to at least one of a first STA to which the first device is attached and a second STA to which the second device is attached.

[0191] In some examples, the fifth frame or a variant of the fifth frame includes a user information list (User Info List) field; the user information list field is used to request the required TXOP time from the third device.

[0192] In some examples, the user information list field includes: a first indication subfield for indicating the device, a second indication subfield for indicating the roles of the two parties in the direct communication, and a third indication subfield for indicating the TXOP duration. For example, the first indication subfield may be the AID12 subfield, which indicates the AID information of the device that needs to process the frame; the roles of the two parties in the direct communication refer to whether the current device is a P2P initiator or a P2P responder; and the third indication subfield may be the Allocation Duration subfield, which indicates the allocated TXOP duration.

[0193] In some examples, the third indication subfield is a second value, which is used to indicate that the current device is a responder for direct communication with the first STA attached to the first device. For example, when Allocation Duration = 0, it is used to indicate that the current device is a responder for P2P communication with the first STA attached to the first device.

[0194] In one embodiment, the method further includes: determining a variant of the fifth frame based on the values ​​of a first reserved field and a subfield of the first reserved field in common information (Common Info). For example, the reserved field in the common information may be: GI and HE / EHT-LTF type / Triggered TXOP Sharing Mode. Taking Triggered TXOP Sharing Mode as an example, the reserved field Triggered TXOP Sharing Mode is set to 2, and its subfield EML Triggered TXOP sharing mode subfield is set to 1. In this case, the current frame is a variant of the fifth frame, that is, a variant of MU-RTS TXS, such as MU-RTS ETXS.

[0195] In one embodiment, the method further includes: a first STA attached to the first device and a second STA attached to the second device are both capable of receiving and parsing the fifth frame on their respective working EMLSR link sets.

[0196] In one embodiment, the method further includes: when at least one of the first STA attached to the first device and the second STA attached to the second device receives the fifth frame or a variant of the fifth frame, the first device and at least one of the second devices perform EMLSR link switching. In other words, when the second STA attached to the second device receives the fifth frame or a variant of the fifth frame, the second device can perform EMLSR link switching; or, when the first STA attached to the first device also supports EMLSR, that is, when both work under EMLSR, when the first STA attached to the first device receives the fifth frame or a variant of the fifth frame, the first device can also perform EMLSR link switching, and there are also cases where both the first device and the second device can perform EMLSR link switching.

[0197] The P2P initiator is the first device, and the AP MLD instructs the EMLSR link switching and triggered TXOP sharing in the EMLSR operation scenario in steps as follows:

[0198] In one embodiment, the method further includes: a first STA attached to the first device requests a required TXOP time from the third device, and indicates first identity information; wherein the first identity information is identity information of a second STA attached to the second device, and the second STA attached to the second device is associated with the third device and exchanges each other's EML capability information.

[0199] In one embodiment, the method further includes: the first STA attached to the first device receives the fifth frame sent by the third device, and the third device is used to share the TXOP time with at least one of the first STA attached to the first device and the second STA attached to the second device in TXOP sharing mode 2.

[0200] In one embodiment, the method further includes: if the second STA attached to the second device that receives the sixth frame completes link switching, continuing to maintain the single-link multi-spatial stream state until a second time expires. Optionally, the second time may be a time specified by a peer device of the second device (e.g., the first device).

[0201] In one implementation, the second time is obtained according to the fifth frame time sent at the lowest rate, the fifth frame feedback time, and the short interframe space SIFS.

[0202] In one embodiment, the method further includes: triggering feedback of the fifth frame when the fifth frame is sent to a second STA to which the second device is attached.

[0203] In one embodiment, the method further includes: performing single-link multi-spatial stream frame exchange when at least one of the first device and the second device completes EMLSR link switching.

[0204] FIG12 is a schematic flow chart of a communication method 1200 according to an embodiment of the present application. The method may optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents:

[0205] S1210: Establish a direct communication relationship between a first STA attached to a first device and a second STA attached to a second device;

[0206] S1220: Perform frame transmission using enhanced multi-link operation between a first STA attached to the first device and a second STA attached to the second device according to the direct communication relationship.

[0207] The second STA to which the second device is attached receives the sixth frame, which is sent by the first STA to which the first device is attached in the form of a single-link single spatial stream.

[0208] In some examples, after a direct communication relationship is established between the first STA (STA11) attached to the first device (such as non-AP MLD1) and the second STA (STA21) attached to the second device (such as non-AP MLD2), enhanced multi-link operation can be used to perform frame transmission between the first STA attached to the first device and the second STA attached to the second device.

[0209] In some examples, a first STA attached to the first device (eg, non-AP MLD1) and a second STA attached to the second device (eg, non-AP MLD2) operate on the same link.

[0210] The first STA to which the first device is attached may be STA11, and the second STA to which the second device is attached may be STA21.

[0211] In the following description, the first device (such as non-AP MLD1), the second device (such as non-AP MLD2), the first STA attached to the first device (such as STA11), the second STA attached to the second device (such as STA21), the third device (such as AP MLD), the fifth frame can be a trigger frame such as a MU-RTS TXS frame, the sixth frame can be an initial control frame such as MU-RTS, and the feedback frame can be CTS. Examples are described and no further details are given.

[0212] It should be noted that both the fifth and sixth frames are control frames. The fifth frame, as a trigger frame, is actually also a type of control frame. CTS can be used as a feedback frame for the fifth frame or the sixth frame. In this application, CTS is used as an example of a feedback frame.

[0213] It should be noted that the transmission and parsing of interactive information, such as frames, are specifically performed by the device's affiliated STAs (e.g., STA11 or STA21), while the processing or actions to complete the operation (e.g., link switching) are performed by the device itself. For example, if at least one of non-AP MLD1 and non-AP MLD2 operates in EMLSR mode, link switching is performed by non-AP MLD1 or non-AP MLD2.

[0214] In one embodiment, the method further includes: the second device performing EMLSR link switching.

[0215] In one embodiment, the method further includes: performing frame exchange of single-link multiple spatial streams when the second device completes the EMLSR link switching.

[0216] The communication method provided in the above-mentioned embodiment of the present application is described in detail below.

[0217] There are two non-AP MLDs operating on the same link. A direct communication relationship is established between the two in some way, and P2P transmission can be carried out without AP relay. At least one of the two non-AP MLDs supports EMLSR operation, that is, different operation mode parameters can be used at different stages of communication, such as switching available spatial streams (including transmit chains and / or receive chains) distributed on different links to the same link to send or receive frames. The operation mode parameter can be at least one of the number of spatial streams, bandwidth, decoding capability, maximum media access control protocol data unit length, maximum aggregate media access control service data unit length, or maximum aggregate media access control protocol data unit length index.

[0218] It should be noted that the non-AP MLD (or its affiliated STA) can exchange traffic information indications with the AP MLD (or its affiliated AP) through an SCS negotiation mechanism to request the AP MLD (or its affiliated AP) to share a TXOP segment with the non-AP MLD (or its affiliated STA) for P2P transmission. The following implementations of the embodiments of the present application do not limit the above information interaction process. In the subsequent description, the transmission opportunity request (TXOP Request) is used to refer to the above information interaction process.

[0219] The implementation method is described using the example of a non-AP MLD with two links. As shown in Figure 13, non-AP Device 1 is capable of providing services to a non-AP MLD operating in EMLSR mode. Non-AP MLD 2 has two working links and can use EMLSR mode to switch available spatial streams to a single link, implementing single-link multi-spatial stream frame exchange. Non-AP Device 1 can exchange single-link multi-spatial stream frames with non-AP MLD 2 operating in EMLSR mode over one of its links.

[0220] As shown in Figure 14, non-AP Device 1 can also be non-AP MLD1, which has two working links and can use EMLSR mode to switch available spatial streams to a single link, implementing single-link multi-spatial stream frame switching. Non-AP MLD2 can also provide services to non-AP MLDs operating in EMLSR mode. In this case, both non-AP MLD1 and non-AP MLD2 have two attached STAs: STA11 and STA12 are attached to non-AP MLD1, and STA21 and STA22 are attached to non-AP MLD2. STA11 and STA21 operate on the same link, designated Link 1, and STA12 and STA22 operate on the same link, designated Link 2.

[0221] The various implementation methods and examples of this application mainly include the following three aspects:

[0222] In a first aspect, a method for exchanging enhanced multi-link operation capability information between devices capable of multi-link operation (MLO) is provided, specifically including the following contents:

[0223] There are two MLO-capable devices working on the same link. A direct communication relationship is established between the two devices in some way, and P2P transmission can be performed without AP relay.

[0224] Among the two devices mentioned above, at least one device supports EMLSR operation, and the other supports providing services for devices operating in EMLSR mode. In one case, the device that supports EMLSR operation is the P2P responder device, and the device that supports providing services for devices in EMLSR mode is the P2P initiator device. In another case, the P2P initiator device may also support EMLSR operation and operate in EMLSR mode, and the P2P responder device may also support providing services for devices in EMLSR mode. It should be pointed out here that if the P2P initiator device supports EMLSR operation and operates in EMLSR mode, the P2P responder device must also support providing services for devices in EMLSR mode.

[0225] Supporting EMLSR operations means that different operating mode parameters can be used at different stages of communication, for example, available spatial streams (including transmit chains and / or receive chains) distributed on different links are switched to the same link to send or receive frames.

[0226] Supporting services for devices operating in EMLSR mode means that when initiating a transmission, the device operating in EMLSR mode may be instructed in some way to switch available spatial streams and reserve corresponding switching time.

[0227] As shown in FIG15 , the new enhanced multi-link capability subfield is used to indicate whether the use of EMLSR in P2P transmission is supported. The subfield is called the “P2P Support” subfield, as shown by the bold underline in FIG15 .

[0228] The P2P Support bit in the Enhanced Multilink Capability subfield sent by AP MLD is reserved and has no meaning. In the Enhanced Multilink Capability subfield sent by non-AP MLD, if P2P Support is set to 1, it indicates that the device has the ability to provide services to devices operating in EMLSR mode. If P2P Support is set to 0, it indicates that the device does not have the ability to provide services to devices operating in EMLSR mode. Table 1 describes the subfields. The bold and underlined characters in Table 1 indicate the corresponding descriptions of P2P Support.

[0229]

[0230] Table 1

[0231] Exemplarily, the interaction process of enhancing multi-link capability information is described as follows.

[0232] 1) Enhanced multi-link capability information interaction example 1:

[0233] In the scenario where the AP MLD and non-AP MLD exchange capability information, the non-AP MLD sends an Association Request frame to the associated AP MLD with the Enhanced Multilink Capabilities (EML Capabilities) subfield set to 1 and P2P Support set to 1. After receiving the Association Request frame, the AP MLD learns that the non-AP MLD supports EMLSR operations and can provide services to devices operating in EMLSR mode. The AP MLD then sends an Association Response frame to the non-AP MLD with the EML Capabilities subfield set to 1.

[0234] After the interaction is complete, the non-AP MLD2 can be declared enabled and use the EMLSR mode.

[0235] Through the above interaction process, the non-AP MLD can use the EML Operation Mode Notification (OMN) frame to announce the activation of EMLSR mode to the AP MLD, and then use EMLSR operation to exchange frames. Optionally, if the AP MLD does not support EMLSR, the non-AP MLD is not allowed to send EML OMN frames with EMLSR Mode = 1.

[0236] 2) Enhanced multi-link capability information interaction example 2:

[0237] In the scenario where non-AP MLD1 and non-AP MLD2 exchange capability information, as shown in Figure 16, when establishing a P2P relationship with non-AP MLD2, non-AP MLD1 includes the exchange of enhanced multilink capability information. For example, when establishing the relationship through TDLS, non-AP MLD1 includes a multilink element (such as a basic multilink element or a P2P variant multilink element) in the TDLS Setup Request frame it sends, which includes the EML Capabilities subfield and sets P2P Support to 1. When non-AP MLD2 responds using a TDLS Setup Response, it includes a multilink element (such as a basic multilink element or a P2P variant multilink element) with the EML Capabilities subfield and sets EMLSR Support to 1.

[0238] After the interaction is complete, the non-AP MLD2 can be declared enabled and use the EMLSR mode.

[0239] 3) Enhanced multi-link capability information interaction example 3:

[0240] In the scenario where non-AP MLD1 and non-AP MLD2 exchange capability information, as shown in Figure 17, when establishing a P2P relationship with non-AP MLD2, non-AP MLD1 also exchanges enhanced multilink capability information. For example, when establishing the relationship through TDLS, non-AP MLD1 includes a multilink element (such as a basic multilink element or a P2P variant multilink element) in the TDLS Setup Request frame it sends, which includes the EML Capabilities subfield and sets EMLSR Support and P2P Support to 1. When non-AP MLD2 responds using a TDLS Setup Response frame, it includes a multilink element (such as a basic multilink element or a P2P variant multilink element) with the EML Capabilities subfield and sets EMLSR Support and P2P Support to 1.

[0241] After the interaction is completed, both devices can declare to start and enter EMLSR mode.

[0242] 4) Enhanced multi-link capability information interaction example 4:

[0243] In the scenario of capability information exchange between the non-AP MLD and the EHT non-AP STA, as shown in Figure 18, when the non-AP MLD establishes a P2P relationship with the EHT non-AP STA on a certain link, it also exchanges enhanced multi-link capability information. For example, when establishing the relationship through TDLS, the non-AP MLD1 includes a multi-link element (such as a basic multi-link element or a P2P variant multi-link element) in the TDLS Setup Request frame it sends, which includes the EML Capabilities subfield and sets the EMLSR Support field to 1. When the EHT non-AP STA responds using the TDLS Setup Response, it includes a multi-link element (such as a basic multi-link element or a P2P variant multi-link element) with the EML Capabilities subfield and sets the P2P Support field to 1.

[0244] After the interaction is complete, non-AP MLD can be enabled and use EMLSR mode.

[0245] 5) Enhanced multi-link capability information interaction example 5:

[0246] In the scenario of capability information exchange between the non-AP MLD and the EHT non-AP STA, as shown in Figure 19, when the non-AP MLD establishes a P2P relationship with the EHT non-AP STA on a certain link, it also exchanges enhanced multi-link capability information. For example, when establishing the relationship through TDLS, the non-AP MLD1 includes a multi-link element (such as a basic multi-link element or a P2P variant multi-link element) in the TDLS Setup Request frame it sends, which includes the EML Capabilities subfield and sets EMLSR Support to 1. When the EHT non-AP STA responds using the TDLS Setup Response frame, it includes a multi-link element (such as a basic multi-link element or a P2P variant multi-link element) with the EML Capabilities subfield and sets P2P Support to 0 or does not include the multi-link element.

[0247] Non-AP MLD must not use EMLSR mode.

[0248] Considering that when establishing a P2P communication relationship between peer devices, frames containing basic multi-link elements may not be exchanged, and some information in the basic multi-link element is not necessary for P2P transmission. For example, a new type of multi-link element (i.e., the P2P variant multi-link element mentioned above) is designed, and the multi-link element is distinguished from other types of multi-link elements by the Type subfield of the Multi-Link Control field in the multi-link element. The structure of the Multi-Link Control field of the multi-link element is shown in FIG20. The Type subfield shown in bold underline in FIG20 is set to a reserved value (e.g., a value of 3). The definition of the Type subfield is shown in bold underline in Table 2 below:

[0249]

[0250] Table 2

[0251] Among them, the public information field of the multi-link element of the P2P variant should include the EML capability subfield. The structure of the P2P variant multi-link element is shown in Figure 21, and the Type subfield is shown in bold and underlined in Figure 21.

[0252] In a second aspect, a method for declaring an EML operation mode is provided, which specifically includes the following contents:

[0253] Announcement Method 1: Peers directly use the existing mechanism (sending EML OMN frames and receiving the same EML OMN frames) to announce the change of EMLSR mode.

[0254] When a device intends to switch the EML operation mode (such as turning off the EMLSR mode), it directly sends an EML OMN frame to all peer devices in a P2P manner and sets the frame accordingly. After the peer device receives the EML OMN frame, it sends EML OMN to the peer device in a P2P manner for feedback.

[0255] The possible interaction processes using this method are shown in Figures 22 and 23, where non-AP MLD1 and non-AP MLD2 are both operating in EMLSR mode and need to exit this mode. The transmission of EML OMN frames must meet the requirements of EMLSR mode.

[0256] Announcement method 2: The AP actively announces the change of EMLSR mode to the peer device

[0257] When a device intends to switch the EML operation mode (such as turning off the EMLSR mode), it exchanges EML OMN frames with the AP MLD and then switches according to the rules. The AP MLD uses the newly designed peer MLD EML operation mode announcement frame at the appropriate time to announce the switching information to other devices. The appropriate time refers to any time after the EML operation mode switch of the P2P responder device is completed and before the process of P2P transmission to the P2P responder device is shared through the triggered transmission opportunity. The peer MLD EML operation mode announcement frame can be a newly designed EHT Action frame, which is sent only in unicast mode. The structure of the peer MLD EML operation mode announcement frame is shown in Table 3, and the Peer MLD EML OM Info list field is shown in bold and underlined in Table 3.

[0258]

[0259] Table 3

[0260] The Category and EHT Action fields are used to indicate that the frame belongs to an EHT Action frame and is a designed peer-to-peer MLD EML operation mode announcement frame, respectively.

[0261] The structure of the Peer MLD EML OM Info list is shown in Figure 24, where Count is the number of EML operation mode information carried, represented by the MLD EML OM Info subfield. The MLD EML OM Info field includes the MLD Info subfield and the EML Control subfield.

[0262] The MLD Info subfield is used to indicate the identity information of a certain MLD, such as the MAC address of the MLD and / or the AID assigned when associated with the AP MLD, and possible structures are shown in Figures 25, 26, and 27.

[0263] The EML Control field is used to indicate the EML operation mode corresponding to the non-AP MLD in the Peer MLD EML OM Info list. The structure is shown in Figure 8.

[0264] It should be noted that the necessary conditions for an MLD's EML operation mode information to be included in this frame include: 1. The MLD and the receiving MLD of the frame have P2P service requirements, and the AP MLD is aware of this situation; 2. The MLD has performed EMLSR operation mode switching.

[0265] Based on the above necessary conditions, if the AP MLD meets the condition that it will share the TXOP for the receiver MLD of the frame for P2P transmission, the MLD can be used as an expected receiver in the shared TXOP. The following describes the possible interaction process carrying this operation mode information.

[0266] Example 1:

[0267] As shown in Figure 28, non-AP MLD2 and non-AP MLD3 each send an EML OMN frame to the AP MLD (e.g., link 1 in the multiple links) with the EMLSR Mode subfield set to 1, announcing the entry into EMLSR mode. The AP MLD then responds with the same EML OMN frame. After receiving the feedback frame, non-AP MLDs 2 and 3 can complete the corresponding operating mode switch, turning on EMLSR mode and exiting power-saving mode to enter the active state. The AP then uses the designed Peer MLD EML OMN frame at a certain time to notify non-AP MLD1 of the peer device's EML operating mode switch.

[0268] Example 2:

[0269] As shown in Figure 29, non-AP MLD2 and non-AP MLD3 each send an EML OMN frame to the AP MLD (e.g., link 1 in the multiple links) with the EMLSR Mode subfield set to 1 to announce entry into EMLSR mode, and the EMLSR Mode subfield set to 0 to announce entry into EMLSR mode. The AP MLD then responds with the same EML OMN frame. After receiving the feedback frame, non-AP MLDs 2 and 3 can switch to the corresponding operating mode, entering and exiting EMLSR mode. The AP then uses the designed Peer MLD EML OMN frame at a certain time to notify non-AP MLD1 of the peer device's EML operating mode switch.

[0270] Announcement Method 3: The AP passively announces the change of EMLSR mode to the peer device

[0271] When a device intends to switch to the EML operation mode (such as shutting down the EMLSR mode), it exchanges EML OMN frames with the AP MLD according to the existing mechanism and then switches according to the rules.

[0272] Any device can use the peer-to-peer MLD EML operation mode request frame to request the AP MLD to inform other devices of their EML operation mode. After receiving the request, the AP MLD uses the newly designed peer-to-peer MLD EML operation mode announcement frame to announce the switching information to other devices.

[0273] The peer-to-peer MLD EML operation mode request frame and the peer-to-peer MLD EML operation mode announcement frame are newly designed frames and can be implemented in the following two ways:

[0274] 1) Implementation method 1 of the peer-to-peer MLD EML operation mode request frame and the peer-to-peer MLD EML operation mode announcement frame is described below. The two may use different types of frames:

[0275] The peer MLD EML operation mode request frame is a newly designed EHT Action frame and is sent only in unicast mode. The structure of the peer MLD EML operation mode request frame is shown in Table 4. The Dialog Token and Peer MLD EML OM Info list fields are shown in bold and underlined in Table 4.

[0276]

[0277] Table 4

[0278] The Category and EHT Action fields are used to indicate that the frame belongs to an EHT Action frame and is a designed peer-to-peer MLD EML operation mode request frame, respectively.

[0279] The Dialog Token field is a non-zero value selected by the non-AP MLD that sends the request to identify this interaction.

[0280] The structure of the Peer MLD EML OM Info list is shown in FIG30 , where Count is the number of MLD Info subfields carried. The MLD corresponding to the carried MLD Info subfield represents the peer non-AP MLD requesting the AP MLD to declare the EML operation mode.

[0281] Each MLD Info subfield is used to indicate the identity information of a certain MLD, such as the MAC address of the MLD and / or the AID assigned when associated with the AP MLD, and possible structures are shown in Figures 25, 26, and 27.

[0282] The peer MLD EML operation mode announcement frame is a newly designed EHT Action frame and is sent only in unicast mode. The structure of the peer MLD EML operation mode announcement frame is shown in Table 5. The Dialog Token and Peer MLD EML OM Info list fields are shown in bold and underlined in Table 5.

[0283]

[0284] Table 5

[0285] The Category and EHT Action fields indicate that the frame is an EHT Action frame and is a designed peer MLD EML operation mode announcement frame. The value of the Dialog Token field is the same as the value of the Dialog Token field in the peer MLD EML operation mode request frame corresponding to the peer MLD EML operation mode announcement. It should be noted that when the Dialog Token value is 0, it indicates that the peer MLD EML operation mode announcement was sent autonomously by the AP MLD without a request from the non-AP MLD.

[0286] The structure of the Peer MLD EML OM Info list is shown in Figure 24, where Count is the number of MLD EML OM Info subfields carried.

[0287] Each EML OM Info contains an MLD Info subfield and an EML Control subfield. The MLD Info subfield is used to indicate the identity information of a certain MLD, such as the MLD's MAC address and / or the AID assigned when associated with the AP MLD. The possible structures are shown in Figures 25, 26, and 27.

[0288] The EML Control field can be used to indicate the EML operation mode of the non-AP MLD in the Peer MLD EML OM Info list.

[0289] 2) Implementation method 2 of the peer-to-peer MLD EML operation mode request frame and the peer-to-peer MLD EML operation mode announcement frame is described below. These two frames can use the same type of frame, and the transmission direction of the frame determines its interpretation method.

[0290] The Peer MLD EML Operation Mode Request frame and the Peer MLD EML Operation Mode Announcement frame are newly designed EHT Action frames and are sent only in unicast mode. The structure of the Peer MLD EML Operation Mode Announcement frame is shown in Table 6. The Dialog Token and Peer MLD EML OM Info List fields are shown in bold and underlined in Table 6.

[0291]

[0292] Table 6

[0293] The Category and EHT Action fields are used to indicate that the frame belongs to an EHT Action frame and is a designed peer-to-peer MLD EML operation mode request / notification frame, respectively.

[0294] When this frame is sent from a non-AP MLD to an AP MLD, it is a Peer MLD EML Operation Mode Request frame, requesting the AP MLD the EML operation mode of one or more non-AP MLDs contained in the frame. The Dialog Token field is a non-zero value selected by the non-AP MLD sending the frame to identify the request. When this frame is sent from an AP MLD to a non-AP MLD, it is a Peer MLD EML Operation Mode Announcement frame, announcing the EML operation mode of one or more non-AP MLDs to the non-AP MLD. The value of the Dialog Token field is the same as the Dialog Token field value in the Peer MLD EML Operation Mode Request frame corresponding to the Peer MLD EML Operation Mode Announcement. It should be noted that a Dialog Token value of 0 indicates that the Peer MLD EML Operation Mode Announcement was sent autonomously by the AP MLD without a request from the non-AP MLD.

[0295] The structure of the Peer MLD EML OM Info list is shown in Figure 24, where Count is the number of MLD EML OM Info subfields carried.

[0296] Each EML OM Info contains an MLD Info subfield and an EML Control subfield. The MLD Info subfield is used to indicate the identity information of a certain MLD, such as the MLD's MAC address and / or the AID assigned when associated with the AP MLD. The possible structures are shown in Figures 25, 26, and 27.

[0297] When this frame is a peer-to-peer MLD EML operation mode request frame sent by a non-AP device, the EML Control field has no practical meaning and may be absent or set to a reserved value. When this frame is a peer-to-peer MLD EML operation mode announcement frame sent by an AP device, the EML Control field indicates the EML operation mode corresponding to the non-AP MLD in the Peer MLD EML OM Info list. The following describes the possible interaction flow using this operation mode request frame.

[0298] Example 1:

[0299] As shown in Figure 31, non-AP MLD2 and non-AP MLD3 each send an EML OMN frame to the AP MLD (e.g., link 1 in the multiple links), setting the EMLSR Mode subfield to 1 to announce entry into EMLSR mode and the EMLSR Mode subfield to 0 to announce entry into EMLSR mode. The AP MLD then responds with the same EML OMN frame. After receiving the feedback frames, non-AP MLDs 2 and 3 can switch between corresponding operating modes, enabling and disabling EMLSR mode, and exiting and entering energy-saving mode accordingly. At a certain point, non-AP MLD1 uses the designed Peer MLD EML OM Request frame to request the EML operating mode of non-AP MLD2 and 3 from the AP MLD. Upon receiving the request, the AP MLD uses the designed Peer MLD EML OMN frame to announce the EML operating mode switch to non-AP MLD1.

[0300] Example 2:

[0301] As shown in Figure 32, non-AP MLD2 and non-AP MLD3 each send an EML OMN frame to the AP MLD (e.g., link 1 in the multiple links), setting the EMLSR Mode subfield to 1 to announce entry into EMLSR mode and the EMLSR Mode subfield to 0 to announce entry into EMLSR mode. The AP MLD then responds with the same EML OMN frame. After receiving the feedback frame, non-AP MLDs 2 and 3 can switch between corresponding operating modes, enabling and disabling EMLSR mode, and exiting and entering energy-saving mode accordingly. At a certain time, the AP MLD directly uses the designed Peer MLD EML OMN frame to announce the EML operating mode switch of the peer device to non-AP MLD1. In the Peer MLD EML OMN frame, the Dialog Token field is set to 0.

[0302] If one of the two parties does not support the EMLSR function or uses EML operation in P2P, this solution will not continue. At this time, only basic spatial streams (such as a single spatial stream) will be allowed to be used on one link to send and receive frames.

[0303] Thirdly, the interaction process used by EMLSR operations in P2P transmission is designed, which specifically includes the following contents:

[0304] It's important to note that before this interaction begins, the non-AP device initiating P2P transmission has already completed the aforementioned "TXOP Request" interaction with the AP. Through this interaction, the AP has learned from the non-AP device that it has a P2P transmission request and has obtained the responder (or receiver) information for its P2P transmission. This process is not detailed here.

[0305] 1. Implementation Method 1: In the EMLSR operation scenario where the P2P initiator (non-AP MLD) sends the initial control frame, devices must exchange EML capability information and declare the EML operation mode before this interaction begins. The interaction process is shown in Figure 33 and includes the following:

[0306] Step 1. The peer non-AP MLDs exchange EML capability information and EML operation mode announcements.

[0307] It should be noted that the device using this solution can interact with EML capability information and declare EML operation mode through various examples including but not limited to the first and second aspects of the embodiments of this application.

[0308] There are many mechanisms for P2P communication using the WLAN standard. This example does not limit the specific form and process of capability information exchange. In one example, when establishing TDLS, the TDLS Discovery Response frame, TDLS Setup Request Action frame, and TDLS Setup Response Action frame carry multilink elements (such as the basic multilink element and the P2P variant multilink element mentioned above) containing the EML capability information field.

[0309] Step 2: AP MLD shares the TXOP on a link (e.g., link 1) with the attached STA (e.g., STA11) of the P2P initiator non-AP MLD through the triggered TXOP sharing mechanism of Mode 2.

[0310] In some cases, a non-AP MLD operating in EMLSR mode can receive and parse MU-RTS TXS frames on all EMLSR links it operates on. Otherwise, if the P2P initiator non-AP MLD also operates in EMLSR mode, it is necessary to trigger EMLSR switching of the P2P initiator non-AP MLD through existing mechanisms before sending MU-RTS TXS frames.

[0311] Step 3: EMLSR link switching interaction;

[0312] In some examples, after obtaining a TXOP from the AP through a triggered TXOP sharing mechanism (after responding to a CTS to the AP), a subordinate STA (such as STA11) of the P2P initiator non-AP MLD sends an EMLSR initial control frame (such as MU-RTS) to the subordinate STA (such as STA21) of the peer non-AP MLD on the link in the form of a single spatial stream on the link, and performs corresponding padding in it.

[0313] In some examples, when sending the initial control frame, the P2P initiator non-AP MLD (non-AP MLD1) simultaneously performs EMLSR link switching, and the P2P responder non-AP MLD (non-AP MLD2) performs switching according to the existing mechanism. The filling time length of the initial control frame needs to ensure that the EMLSR link switching of both parties can be completed. A natural approach is to select the larger value of the capability information announced by both parties as the filling time. However, considering that in actual implementation, the P2P initiator can start EMLSR link switching earlier, and considering the universality of the mechanism, here we can only consider meeting the switching delay requirement of the P2P responder non-AP MLD.

[0314] In some examples, the P2P initiator non-AP MLD can perform EMLSR link switching within the time period corresponding to the reception and feedback of the MU-RTS TXS sent by the AP MLD and / or within the time period of sending the initial control frame to the P2P responder device and receiving the feedback. The P2P initiator non-AP MLD needs to ensure that it is capable of immediately starting multi-spatial stream transmission after the subordinate STA of the P2P responder non-AP MLD responds to the initial control frame, that is, it is in the EMLSR single-link multi-spatial stream frame exchange operation mode.

[0315] Step 4: Frame exchange.

[0316] In some examples, after the subordinate STA (e.g., STA21) of the P2P responder non-AP MLD completes link switching (responds to a CTS message from the subordinate STA of the P2P initiator non-AP MLD), both parties can exchange single-link multi-spatial stream frames.

[0317] In some examples, if the subordinate STA (e.g., STA21) of the P2P responder non-AP MLD does not respond to the initial control frame (e.g., NAV is set, or other problems occur in the device), the P2P initiator non-AP MLD shall not perform subsequent data transmission.

[0318] In some examples, the timing for the Non-AP MLD to end the link merging state and switch back to the listening operation state follows the prescribed existing mechanism. After the time indicated by the corresponding EMLSR Transition Delay after the end of the allocated TXOP, the AP MLD considers that the corresponding non-AP MLD has ended the link merging state and returned to the listening operation mode.

[0319] Implementation Method 2: In scenarios where MU-RTS TXS or MU-RTS variants are used to indicate handover, it should be noted that during the TXOP Request process, the P2P initiator (non-AP MLD) not only indicates the desired TXOP duration but also the address of the target recipient for P2P communication. This target recipient is associated with the AP MLD and has exchanged EML capability information. Inter-device EML capability information exchange and EML operation mode declaration are not required.

[0320] Before this interaction process begins, devices need to exchange EML capability information and declare EML operation modes, as shown in Figure 43. This includes the following:

[0321] Step 1. AP-triggered TXOP sharing mechanism;

[0322] In some examples, the AP MLD performs channel access on a certain link (such as link 1), obtains a TXOP, and then sends a MU-RTS TXS frame or a variant frame of the MU-RTS with the TXOP sharing mode subfield set to 2 to share the TXOP with the subordinate STA (such as STA11) of the P2P initiator non-AP MLD. At the same time, the MU-RTS TXS frame is also sent to the subordinate STA (such as STA21) of the P2P responder non-AP MLD indicated by the P2P initiator non-AP MLD working on the link.

[0323] In some examples, MU-RTS TXS is implemented by setting the GI and HE / EHT-LTF type / Triggered TXOP Sharing Mode subfield of the common information field in the MU-RTS frame, as shown in Figures 34 and 35. In previous MU-RTS frames, this field is a reserved value. When the reserved value is set to 0, it indicates that it is not a MU-RTS TXS frame.

[0324] The TXOP duration and receiver indication are implemented using the User Information List field of the MU-RTS TXS trigger frame, as shown in Figures 36 and 37. The AID12 subfield indicates the AID information of the device that needs to process the frame, the RU allocation and PS160 subfields in the EHT structure indicate the allocated resource block information, and the Allocation Duration field indicates the allocated TXOP duration in units of 16 microseconds.

[0325] In some examples, Option 1 (Opt 1) may be used, that is, without changing the MU-RTS TXS, the existing MU-RTS TXS frame is directly used, and Allocation Duration = 0 is used to indicate the receiver.

[0326] Specifically, the RA can be set as a broadcast address, and the user information of both the P2P initiator and the P2P responder can be carried in the user information list. The P2P initiator still uses the existing mechanism, except that the Allocation Duration field of the P2P responder is set to 0 to indicate that it is a P2P responder (no available TXOP is allocated to it). It is also specified that the two devices respond to the CTS in different RUs (different 20MHz sub-channels).

[0327] At the same time, according to the EML capability information exchanged during association, the frame is padded so that the non-AP MLDs (non-AP MLD1 and non-AP MLD2) that receive the frame have enough time to switch. An example of Opt1 is shown in Figure 38:

[0328] In some examples, Option 2 (Opt2) may also be adopted, which is implemented through a new MU-RTS variant.

[0329] Specifically, as shown in Figure 39, the LDPC extra symbol segment field used as a reserved field in the common information field in the MU-RTS frame, for example, a 1-bit reservation, starting from B27 to the end of B27 of the common information field) is interpreted as an EML Triggered TXOP sharing mode subfield, as shown by the bold underline in Figure 39.

[0330] It should be noted that in other Trigger frames, this field is still interpreted as an LDPC extra symbol segment. Only in MU-RTS Trigger frames is this field interpreted as the EML Triggered TXOP sharing mode. When using this field, set the Triggered TXOP sharing mode field to 2 and the EML Triggered TXOP sharing mode subfield to 1, indicating that this MU-RTS is a special MU-RTS TXS used in this implementation, called a MU-RTS ETXS.

[0331] MU-RTS ETXS also has the following functions: triggering the receiving device of this frame to perform EMLSR link switching and sharing TXOP for P2P initiator for P2P transmission.

[0332] The User Info field of the MU-RTS ETXS has the same format as the User Info field of the proposed MU-RTS TXS, as shown in Figures 36 and 37. The difference is that the User Info field of the MU-RTS ETXS can indicate in some way that the device corresponding to the User Info is the recipient device of the allocated TXOP. For example, using the above-mentioned Opt1 method, the Allocation Duration can be set to 0 to implement the above function; for another example, using the above-mentioned Opt2 method, a bit in the reserved field can be used to identify whether the device corresponding to the User Info field is the owner (Holder) or responder (Responder) of the allocated TXOP, where the owner of the TXOP is the P2P initiator of the P2P transmission, and the responder of the TXOP is the expected recipient of the TXOP transmission, that is, the recipient of the P2P transmission indicated by Allocation Duration = 0 in the User Info. Furthermore, a device designated as a TXOP Responder should not immediately return to listening mode after completing EMLSR handover. Instead, it must remain in this state for a period of time to receive P2P data transmitted using multiple spatial streams. For example, the decision on when to return to listening mode can be made by referring to the mechanism for determining the end of frame exchange and returning to listening when a non-AP MLD uses EMLSR mode to exchange multiple spatial streams in a single link with an AP MLD.

[0333] In an example using the above-mentioned Opt2 method, a newly defined field is used in User Info to identify the P2P receiver. As shown in FIG40 , for a reserved bit in the User Info field of the newly defined MU-RTS ETXS, taking the User Info field of the HE variant as an example, as shown in Table 7, the newly defined bit is named P2P Role Indication. If this field is equal to 0, it indicates that the device corresponding to the User Info is the owner (holder) of the allocated TXOP; if this field is equal to 1, it indicates that the device corresponding to the User Info is the responder (responder) of the allocated TXOP.

[0334]

[0335] Table 7

[0336] To prevent misinterpretation by devices that do not recognize the EML Triggered TXOP sharing mode subfield, devices that do not support this solution will not be included in the User Info field of the MU-RTS ETXS.

[0337] In some examples, both the Opt1 method and the Opt2 method can support allocating TXOPs to multiple devices using one frame, and the TXOP allocation depends on the order of arrangement of the User Info.

[0338] Specifically, for the Opt1 mode, starting with a User Info with a non-zero Allocation Duration and ending with the next User Info with a non-zero Allocation Duration, all User Infos with an Allocation Duration of 0 are potential responders for the first TXOP. The start time of the next TXOP is after the end time of the previous TXOP. For example, if the Allocation Duration values ​​in the User Info field are t1, 0, t2, 0, 0, t3, 0, respectively, this means that the first TXOP starts at time 0 and ends at time t1, with device 1 as the holder and device 2 as the responder. The second TXOP starts at time t1 and ends at time t1+t2, with device 3 as the holder and devices 4 and 5 as the responders. The third TXOP starts at time t1+t2 and ends at time t1+t2+t3, with device 6 as the holder and device 7 as the responder. The corresponding devices need to switch to EMLSR mode as needed. The possible expansion of allocating multiple TXOPs at once based on the Opt1 mode is shown in Figure 41.

[0339] Specifically, for the Opt2 method, the start and end times of TXOPs are interpreted in pairs according to the value of Direction. The possible extension of allocating multiple TXOPs at one time based on the Opt2 method is shown in FIG42 .

[0340] Step 2: Non-AP MLD performs EMLSR link switchover.

[0341] In some cases, a non-AP MLD operating in EMLSR mode is required to receive and parse MU-RTS TXS frames.

[0342] In some examples, when the subordinate STA (STA21) of the P2P responder non-AP MLD receives the MU-RTS TXS or the designed MU-RTS TXS variant frame (MU-RTS ETXS) sent by the subordinate AP of the AP MLD, the EMLSR link switch is directly performed, and it is ensured that single-link multi-spatial stream frame exchange is possible on the link (link 1) after the CTS response is sent.

[0343] In some examples, if both parties are non-AP MLDs operating in EMLSR mode, when STA11, the subordinate STA of non-AP MLD1, the P2P initiator, and STA21, the subordinate STA of non-AP MLD, the P2P responder, both receive a MU-RTS TX frame or a designed MU-RTS variant frame sent by the AP MLD's subordinate AP, they directly perform EMLSR link switching and ensure that they are capable of exchanging single-link multiple spatial stream frames on this link (link 1) after the CTS response is sent.

[0344] Step 3: The STAs affiliated with the non-AP MLD use the TXOP shared by the AP to exchange single-link multi-spatial stream frames.

[0345] In some examples, the timing for the Non-AP MLD to end the link merging state and switch back to the listening operation state follows the prescribed existing mechanism, that is, after the time indicated by the corresponding EMLSR Transition Delay after the end of the allocated TXOP, the AP MLD considers that the corresponding non-AP MLD has ended the link merging state and returned to the listening operation mode.

[0346] Implementation Method 3: AP MLD Step-by-Step Instruction of EMLSR Link Switching and Triggered TXOP Sharing: In the TXOP Request process, the P2P initiator (non-AP MLD) not only indicates the required TXOP time but also the address of the target P2P responder with which it intends to communicate. The target P2P responder is associated with the AP MLD and has exchanged EML capability information.

[0347] Before this interaction process begins, devices need to exchange EML capability information and declare EML operation modes, as shown in Figure 45. This includes the following:

[0348] Step 1: AP MLD instructs both devices to perform EMLSR link switching.

[0349] In some examples, after the AP MLD competes for and obtains the TXOP on a link (such as link 1), it sends an initial control frame (such as MU-RTS) to the subordinate STA21 of the P2P responder non-AP MLD working on the link to instruct the two peer non-AP MLDs to perform EMLSR link switching.

[0350] In some examples, if both parties are non-AP MLDs operating in EMLSR mode, the AP sends an initial control frame (such as MU-RTS) to the subordinate STA11 of the P2P initiator non-AP MLD1 and the subordinate STA21 of the P2P responder non-AP MLD, instructing the two peer non-AP MLDs to perform EMLSR link switching. The initial control frame is sent in a broadcast format, and the resource information used for feedback is indicated in the corresponding user information. The length of the padding can ensure that the P2P initiator and the P2P responder non-AP MLD have enough time to complete the EMLSR link switching. (Existing mechanisms can be implemented)

[0351] In some cases, if a non-AP MLD fails to respond to the initial control frame sent by the AP MLD during an exchange, meaning the initial frame exchange is not complete, the AP MLD will deem that the conditions for EMLSR communication are not met and will not proceed further. In this case, the non-AP MLD, which has already undergone EMLSR link handover and is in the link merge state, can refer to the existing mechanism, which determines when to return to listening mode after the non-AP MLD exchanges single-link, multiple spatial stream frames with the AP MLD using EMLSR mode and then returns to listening mode after determining the end of the operation.

[0352] Step 2: AP MLD executes triggered TXOP sharing process;

[0353] In some cases, the existing Triggered TXOP Sharing process can be used

[0354] It should be noted that since the MU-RTS TXS is sent to the subordinate STA (STA11) of the P2P initiator non-AP MLD, according to the existing rules, if the P2P responder non-AP MLD does not receive a frame of the specified type within a period of time after completion, it will perform a reverse EMLSR link switch, that is, switch from the single-link multi-spatial stream frame exchange operation mode back to the listening operation mode. Therefore, the following additional rules need to be added to prevent this situation from occurring:

[0355] 1) Rule 1: After receiving the initial control frame (such as MU-RTS) and completing the handover (the time starts from sending the feedback), the device maintains the single-link multi-spatial stream frame exchange operation state for at least a period of time. After that, the non-AP MLD exchanges single-link multi-spatial stream frames with the AP MLD in EMLSR mode. The non-AP MLD determines the end of the operation and returns to the listening mechanism to determine when to return to the listening mode and complete the corresponding handover operation.

[0356] For the above period of time, this period of time is reserved for the AP to perform the Triggered TXOP Sharing mechanism to the other device. Optionally, this period of time can be: the time of MU-RTS TXS sent at the lowest rate + 2*SIFS + the time of CTS sent at the lowest rate.

[0357] Implementation 1: This rule 1) is used as a predefined rule for the EMLSR part. That is, all devices that have established a P2P relationship and are in EMLSR mode must wait for at least the above time after receiving the initial control frame.

[0358] Implementation method 2: Define a new MU-RTS variant to distinguish different switching time conditions.

[0359] For example, as shown in FIG44 , the reserved Number of HE / EHT-LTF symbols subfield in the MU-RTS frame is used to indicate the minimum time required for the EMLSR link switching indicated by the frame, in units of 32 microseconds.

[0360] It should be noted that in other types of Trigger frames, this field is still interpreted as the Number of HE / EHT-LTF symbols subfield. Only when the Trigger frame is MU-RTS, this field is interpreted as the designed EMLSR hold duration subfield.

[0361] 2) Rule 2: The MU-RTS TXS frame is also sent to the corresponding subordinate STA (such as STA21) of the P2P responder non-AP MLD, and it is required to feedback CTS. The specific implementation method is the same as the relevant description in the above implementation method 2.

[0362] Step 3: The STAs affiliated with the non-AP MLD use the TXOP shared by the AP to exchange single-link multi-spatial stream frames.

[0363] In some examples, the timing for the Non-AP MLD to end the link merging state and switch back to the listening operation state follows the prescribed existing mechanism. After the time indicated by the corresponding EMLSR Transition Delay after the end of the allocated TXOP, the AP MLD considers that the corresponding non-AP MLD has ended the link merging state and returned to the listening operation mode.

[0364] By comparing the three implementation methods of the above-mentioned interaction process, it can be seen that: in implementation method 1, there is no need to modify the existing EMLSR operation and Triggered TXOP Sharing mechanism, and only the method of exchanging EML capability information and declaring the EML operation mode between devices is added; in implementation method 2, it is required to indicate the recipient address information when applying, and the device working in EMLSR listening mode is required to receive and parse MU-RTS TXS frames, and simultaneously implement EMLSR link switching and Triggered TXOP Sharing, with minimal signaling overhead, and there is no need to exchange EML capability information and declare the EML operation mode between devices; in implementation method 3, it is also required to indicate the recipient address information when applying, and the mechanism needs to be modified to prevent a device from returning to the EMLSR listening state prematurely, and there is no need to exchange EML capability information and declare the EML operation mode between devices.

[0365] In summary, by adopting the above-mentioned various implementation methods and examples of the embodiments of the present application, EMLSR operations can be used for P2P transmission between non-AP MLDs, and the AP can schedule P2P transmission within its BSS. Triggered TXOP sharing is used to realize the advantages of using EMLSR operations for P2P transmission between non-AP MLDs. The introduction of this triggered TXOP sharing mechanism enables the AP MLD to manage and schedule all transmissions within its BSS, preventing invalid transmissions from wasting channel resources. Non-AP MLDs operating in EMLSR mode can perform P2P transmission through this triggered TXOP sharing mechanism.

[0366] It should be noted that the above examples can be combined with various possibilities in the above-mentioned embodiments of the present application, which will not be described in detail here.

[0367] FIG46 is a schematic diagram of the structure of a first device 4600 according to an embodiment of the present application. The device can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents:

[0368] The first transmission unit 4610 is used to establish direct communication with a second device working on the same link, and adopt enhanced multi-link operation to perform frame transmission between the first device 4600 and the second device; wherein, at least one of the first device 4600 and the second device is: a device that supports the enhanced multi-link operation or a device that works on the enhanced multi-link operation.

[0369] In one embodiment, the device also includes: a second transmission unit, used to apply for a transmission opportunity TXOP from a third device; the third device is used to share TXOP with the first device 4600 and the second device for the direct communication, and uniformly schedule the frame transmission between the first device 4600 and the second device within the TXOP sharing time.

[0370] In one embodiment, the first transmission unit 4610 is further configured to perform single-link multi-spatial stream frame exchange with the second device over one of the multiple links of the second device when the enhanced multi-link operation is an enhanced multi-link single radio (EMLSR) operation. The multiple links include multiple EMLSR links. Furthermore, in an EMLMR scenario, the multiple links may also include multiple EMLMR links.

[0371] In one embodiment, the first device 4600 is used to provide services for the second device operating in the EMLSR mode; the second device is used to support the EMLSR operation and operate in the EMLSR mode.

[0372] In one embodiment, the first device 4600 is used to provide services for the second device operating in EMLSR mode, and / or support the EMLSR operation and operate in EMLSR mode; the second device is used to provide services for the first device 4600 operating in EMLSR mode, and / or support the EMLSR operation and operate in EMLSR mode.

[0373] In one embodiment, the device also includes: an interaction unit for interacting with the first capability information when establishing the direct communication with the second device, wherein the first capability is: the ability to support EMLSR operation and provide services to devices working in EMLSR mode or the ability to work in EMLSR mode.

[0374] In one implementation, the first capability information is carried in a multilink element.

[0375] In some examples, the multi-link element includes at least one of the following methods:

[0376] Mode 1: When the multilink element is a basic multilink element, the first capability information is carried in a common information field in the basic multilink element; wherein the subfields of the first capability information include: a first subfield for indicating the EMLSR mode, and a second subfield for indicating support for EMLSR operation in the direct communication;

[0377] Method 2: When the multi-link element is a P2P variant multi-link element, the first capability information is carried through the common information field in the P2P variant multi-link element; wherein, the P2P variant multi-link element also includes: a multi-link control field carrying a third subfield, and the third subfield is used to indicate the type of the multi-link element.

[0378] In one embodiment, the device also includes: a third transmission unit, used to send a first frame to the third device; a subfield carrying the first capability information in the first frame, so that the third device knows that the first device 600 supports EMLSR operation and can provide services for the second device operating in EMLSR mode.

[0379] In one embodiment, the device also includes: a fourth transmission unit, used to send a first frame to the second device, carrying a subfield of the first capability information in the first frame, so that the second device knows that the first device 600 supports EMLSR operation and can provide services for the second device operating in EMLSR mode.

[0380] In one embodiment, the device further includes: a first receiving unit, configured to receive a first response frame fed back by the second device, wherein the first response frame carries a subfield of the first capability information.

[0381] In one embodiment, the first device 4600 provides services for at least one device operating in the EMLSR mode, and / or operates in the EMLSR mode after declaring that the EMLSR mode is enabled.

[0382] The first device 4600 of the embodiment of the present application can implement the corresponding functions of the first device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the first device 4600 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the first device 4600 of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0383] FIG47 is a schematic diagram of the structure of a second device 4700 according to an embodiment of the present application. The device can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents:

[0384] The first switching unit 4710 is configured to perform mode switching of the enhanced multi-link operation with a first device configured to execute any of the above devices after interacting with the first capability information.

[0385] In one embodiment, the second device 4700 is used to support mode switching of the enhanced multi-link operation; wherein the enhanced multi-link operation is an EMLSR operation.

[0386] In one embodiment, the switching unit is also used to: when it is necessary to switch the EMLSR mode, send a second frame to the first device, carrying a control field in the second frame to announce the switching of the EMLSR mode; wherein the control field includes the EMLSR mode subfield; and when receiving a second response frame fed back by the first device, complete the switching of the EMLSR mode.

[0387] In one embodiment, the first switching unit 4710 is also used to: when it is necessary to switch the EMLSR mode, send a second frame to the third device, carrying a control field in the second frame to announce the switching of the EMLSR mode; wherein the control field includes the EMLSR mode subfield; and complete the switching of the EMLSR mode when receiving a second response frame fed back by the third device.

[0388] In one embodiment, the third device is configured to use a third frame to announce the switching information to other devices associated with the third device and supporting the direct communication with the second device 4700 at the first time.

[0389] In one implementation, the first time is any time after the EMLSR mode switching is completed and before the shared TXOP is triggered to perform the direct communication.

[0390] In one embodiment, the device also includes: a fifth transmission unit, which is used to send a fourth frame to the third device when it is necessary to switch the EMLSR mode, requesting the third device to declare the EML operation mode of other devices that directly communicate with the second device 4700; wherein the third device is used to respond to the request and use the third frame to declare the switching information to other devices associated with the third device and supporting the direct communication with the second device 4700.

[0391] In one embodiment, the third frame carries first information; wherein the first information includes: a fourth subfield for indicating the corresponding identity information of the device with peer EML capability, and a fifth subfield for indicating the corresponding EMLSR mode of the device with peer EML capability.

[0392] In one embodiment, the corresponding identity information of the device with peer EML capability includes: a MAC address, and / or an AID assigned when associated with the third device.

[0393] In one embodiment, the fourth frame is a frame of a different type from the third frame, or a frame of the same type as the third frame.

[0394] In one embodiment, the fourth frame carries a field for indicating that the current frame belongs to a request frame of a peer EML-capable device.

[0395] In one embodiment, the fourth frame carries a field for indicating that the current frame belongs to a request frame or an announcement frame of a peer EML-capable device.

[0396] In one embodiment, the fourth frame includes: a first value and first information; wherein, the first value is used to identify the interaction of the EML capability information; wherein, the first information includes: a fourth subfield for indicating the corresponding identity information of the device with peer EML capability, and a fifth subfield for indicating the corresponding EMLSR mode of the device with peer EML capability.

[0397] The second device 4700 of the embodiment of the present application can implement the corresponding functions of the second device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the second device 4700 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the second device 4700 of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0398] FIG48 is a schematic diagram of the structure of a first device 4800 according to an embodiment of the present application. The device can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents:

[0399] The first communication unit 4810 is used to establish a direct communication relationship between the first STA attached to the first device 4800 and the second STA attached to the second device; the sixth transmission unit 4820 is used to use enhanced multi-link operation to perform frame transmission between the first STA attached to the first device 4800 and the second STA attached to the second device according to the direct communication relationship; wherein, the first STA attached to the first device 4800 sends the sixth frame to the second STA attached to the second device in the form of a single link single spatial stream.

[0400] In one embodiment, the first STA to which the first device 4800 is attached and the second STA to which the second device is attached operate on the same link.

[0401] In one embodiment, the device further includes: a first requesting unit for requesting the required TXOP time from the third device; a second receiving unit for receiving the fifth frame sent by the third device, wherein the third device is used to share the TXOP time with the first STA attached to the first device 800 in TXOP sharing mode 2.

[0402] In one embodiment, the device further includes: a third receiving unit, configured to enable both the first STA attached to the first device 4800 and the second STA attached to the second device to receive and parse the fifth frame on their respective working EMLSR link sets.

[0403] In one embodiment, the device further includes: a second switching unit, configured to, while the first STA attached to the first device 4800 sends the sixth frame to the second STA attached to the second device, perform EMLSR link switching on the first device 800 .

[0404] In one embodiment, the device also includes: a third switching unit, which is used to cause the first device 4800 to perform EMLSR link switching within the time period corresponding to the first STA attached to the first device 4800 receiving and feeding back the fifth frame, and / or within the time period when the sixth frame is sent to the second STA attached to the second device and feedback of the sixth frame is received.

[0405] In one embodiment, the sixth frame carries padding information, and the padding information satisfies at least one of the following conditions:

[0406] a switching delay requirement of the second device;

[0407] a switching delay requirement of the first device;

[0408] The switching delay requirement between the second device and the first device.

[0409] In one embodiment, the device also includes: a second requesting unit, configured to request the required TXOP time from the third device and indicate first identity information; wherein the first identity information is the identity information of the second STA attached to the second device, and the second STA attached to the second device is associated with the third device and exchanges each other's EML capability information.

[0410] In one embodiment, the device also includes: a fourth receiving unit for receiving a fifth frame or a variant of the fifth frame sent by the third device, wherein the third device is used to share the TXOP time with at least one of the first STA attached to the first device 4800 and the second STA attached to the second device in TXOP sharing mode 2.

[0411] In one embodiment, the fifth frame or a variant of the fifth frame is used to allocate a TXOP to at least one of a first STA to which the first device 4800 is attached and a second STA to which the second device is attached.

[0412] In one embodiment, the fifth frame or a variant of the fifth frame includes a user information list field; the user information list field is used to request the required TXOP time from the third device.

[0413] In one embodiment, the user information list field includes: a first indication subfield for indicating a device, a second indication subfield for indicating roles of both parties in direct communication, and a third indication subfield for indicating a TXOP time.

[0414] In one embodiment, the third indication subfield is a second value, and the second value is used to indicate that the current device is a responder for direct communication with the first STA to which the first device 4800 is attached.

[0415] In one embodiment, the device further includes: determining a variant of the fifth frame according to values ​​of the first reserved field and the first reserved field subfield in the public information.

[0416] In one embodiment, the device further includes: a fifth receiving unit, configured to enable both the first STA attached to the first device 4800 and the second STA attached to the second device to receive and parse the fifth frame on their respective working EMLSR link sets.

[0417] In one embodiment, the device also includes: a fourth switching unit, which is used to cause at least one of the first STA attached to the first device 4800 and the second STA attached to the second device to perform EMLSR link switching when at least one of the first device 4800 and the second device receives the fifth frame or a variant of the fifth frame.

[0418] In one embodiment, the device also includes: a third requesting unit, configured to request the required TXOP time from the third device and indicate first identity information; wherein the first identity information is the identity information of the second STA attached to the second device, and the second STA attached to the second device is associated with the third device and exchanges each other's EML capability information.

[0419] In one embodiment, the device also includes: a sixth receiving unit, used to receive the fifth frame sent by the third device, and the third device is used to share the TXOP time with at least one of the first STA attached to the first device 4800 and the second STA attached to the second device in TXOP sharing mode 2.

[0420] In one embodiment, the device further includes: a maintaining unit, configured to continue maintaining the single-link multiple spatial stream state before a second time is reached when the second STA attached to the second device that receives the sixth frame completes link switching.

[0421] In one implementation, the second time is obtained according to the fifth frame time sent at the lowest rate, the fifth frame feedback time, and the short interframe space SIFS.

[0422] In one embodiment, the device further includes: a triggering unit, configured to trigger feedback of the fifth frame when the fifth frame is sent to the second STA to which the second device is attached.

[0423] In one embodiment, the device further includes: a first switching unit, configured to perform single-link multi-spatial stream frame switching when at least one of the first device 4800 and the second device completes EMLSR link switching.

[0424] The first device 4800 of the embodiment of the present application can implement the corresponding functions of the first device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the first device 4800 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the first device 4800 of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0425] FIG49 is a schematic diagram of the structure of a second device 4900 according to an embodiment of the present application. The device can optionally be applied to the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents:

[0426] The second communication unit 4910 is used to establish a direct communication relationship between the first STA attached to the first device and the second STA attached to the second device 4900; the seventh transmission unit 4920 is used to use enhanced multi-link operation to perform frame transmission between the first STA attached to the first device and the second STA attached to the second device 4900 according to the direct communication relationship; wherein, the second STA attached to the second device 4900 receives the sixth frame, which is sent by the first STA attached to the first device in the form of a single-link single spatial stream.

[0427] In one embodiment, the first STA to which the first device is attached and the second STA to which the second device 4900 is attached operate on the same link.

[0428] In one embodiment, the device further includes: a fifth switching unit, configured to perform EMLSR link switching.

[0429] In one embodiment, the device further includes: a second switching unit, configured to perform frame switching of a single link and multiple spatial streams when the second device 4900 completes the EMLSR link switching.

[0430] The second device 4900 of the embodiment of the present application can implement the corresponding functions of the second device in the aforementioned method embodiment. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the second device 4900 can be found in the corresponding descriptions in the above-mentioned method embodiments, which will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the second device 4900 of the application embodiment can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0431] Figure 50 is a schematic structural diagram of a communication device 5000 according to an embodiment of the present application. The communication device 5000 includes a processor 5010, which can call and run a computer program from a memory to enable the communication device 5000 to implement the method in the embodiment of the present application.

[0432] Optionally, the communication device 5000 may further include a memory 5020. The processor 5010 may call and execute a computer program from the memory 5020 to enable the communication device 5000 to implement the method in the embodiment of the present application.

[0433] The memory 5020 may be a separate device independent of the processor 5010 , or may be integrated into the processor 5010 .

[0434] Optionally, the communication device 5000 may further include a transceiver 5030 , and the processor 5010 may control the transceiver 5030 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0435] The transceiver 5030 may include a transmitter and a receiver. The transceiver 5030 may further include an antenna, and the number of antennas may be one or more.

[0436] Optionally, the communication device 5000 may be the first device of the embodiment of the present application, and the communication device 5000 may implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0437] Optionally, the communication device 5000 may be the second device of the embodiment of the present application, and the communication device 5000 may implement the corresponding processes implemented by the second device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0438] 51 is a schematic structural diagram of a chip 5100 according to an embodiment of the present application. The chip 5100 includes a processor 5110, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0439] Optionally, the chip 5100 may further include a memory 5126. The processor 5110 may call and execute a computer program from the memory 5126 to implement the method performed by the first device or the second device in the embodiment of the present application.

[0440] The memory 5126 may be a separate device independent of the processor 5110 or may be integrated into the processor 5110 .

[0441] Optionally, the chip 5100 may further include an input interface 5130. The processor 5110 may control the input interface 5130 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0442] Optionally, the chip 5100 may further include an output interface 5140. The processor 5110 may control the output interface 5140 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0443] Optionally, the chip can be applied to the first device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the first device in each method of the embodiment of the present application. For the sake of brevity, it will not be repeated here.

[0444] Optionally, the chip can be applied to the second device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the second device in the various methods of the embodiments of the present application. For the sake of brevity, it is not described here. The chips applied to the first device and the second device can be the same chip or different chips. 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.

[0445] 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. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0446] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

[0447] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0448] Figure 52 is a schematic block diagram of a communication system 5200 according to an embodiment of the present application. The communication system 5200 includes a first device 5210 and a second device 5220, wherein the first device 5210 may include: a first transmission unit for using enhanced multi-link operation to perform frame transmission between the first device and the second device when establishing direct communication with the second device operating on the same link; wherein at least one of the first device and the second device is: a device that supports the enhanced multi-link operation or a device that operates in the enhanced multi-link operation. The second device 5220 may include: a first switching unit for performing mode switching of the enhanced multi-link operation after interacting with the first device for performing any of the above-mentioned devices with the first capability information. For the sake of brevity, it is not described here.

[0449] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, 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, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, 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 or data center that includes 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)).

[0450] 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.

[0451] Those skilled in the art will 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.

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

Claims

1. A communication method, applied to a first device, comprising: When the first device establishes direct communication with a second device operating on the same link, frame transmission is performed between the first device and the second device using enhanced multi-link operation; At least one of the first device and the second device is a device that supports the enhanced multi-link operation or a device that works in the enhanced multi-link operation.

2. The method according to claim 1, further comprising: The first device applies for a transmission opportunity TXOP from the third device; The third device is used to share a TXOP with the first device and the second device for the direct communication, and uniformly schedule frame transmission between the first device and the second device within a TXOP sharing time.

3. The method according to claim 1 or 2, wherein: The adopting enhanced multi-link operation to perform frame transmission between the first device and the second device includes: When the enhanced multi-link operation is an enhanced multi-link single radio (EMLSR) operation, the first device performs single-link multi-spatial stream frame exchange with the second device on one link among multiple links of the second device.

4. The method according to claim 3, wherein: The multiple links include: multiple EMLSR links.

5. The method according to claim 3, wherein: The first device is used to provide services for the second device operating in the EMLSR mode; the second device is used to support the EMLSR operation and operate in the EMLSR mode.

6. The method according to claim 3, wherein: The first device is configured to provide services for the second device operating in the EMLSR mode, and / or support the EMLSR operation and operate in the EMLSR mode; The second device is configured to provide services for the first device operating in the EMLSR mode, and / or support the EMLSR operation and operate in the EMLSR mode.

7. The method according to any one of claims 3 to 6, further comprising: The first device and the second device interact with each other with first capability information when establishing the direct communication; wherein the first capability is: the ability to support the EMLSR operation and provide services to devices operating in the EMLSR mode or the ability to operate in the EMLSR mode.

8. The method according to claim 7, wherein: The first capability information is carried in a multilink element.

9. The method according to claim 8, wherein The multi-link element includes at least one of the following modes: When the multilink element is a basic multilink element, the first capability information is carried by a common information field in the basic multilink element; wherein the subfield of the first capability information includes: a first subfield for indicating an EMLSR mode, and a second subfield for indicating support for EMLSR operation in the direct communication; or, When the multilink element is a P2P variant multilink element, the first capability information is carried through the common information field in the P2P variant multilink element; wherein the P2P variant multilink element also includes: a multilink control field carrying a third subfield, and the third subfield is used to indicate the type of the multilink element.

10. The method according to claim 9, further comprising: The first device sends a first frame to the third device; The subfield of the first capability information is carried in the first frame, so that the third device knows that the first device supports EMLSR operation and can provide services for the second device operating in EMLSR mode.

11. The method according to claim 9, further comprising: The first device sends a first frame to the second device, and the first frame carries a subfield of the first capability information, so that the second device knows that the first device supports EMLSR operation and can provide services for the second device operating in EMLSR mode.

12. The method according to claim 11, further comprising: The first device receives a first response frame fed back by the second device, where the first response frame carries a subfield of the first capability information.

13. The method according to any one of claims 10 to 12, wherein: The first device provides services for at least one device operating in the EMLSR mode, and / or operates in the EMLSR mode after declaring that the EMLSR mode is enabled.

14. A communication method, applied to a second device, comprising: The second device switches the mode of the enhanced multi-link operation with the first device for executing the method according to any one of claims 1 to 13 after exchanging the first capability information.

15. The method according to claim 14, wherein The second device is configured to support mode switching of the enhanced multi-link operation; The enhanced multi-link operation is an enhanced multi-link single radio (EMLSR) operation.

16. The method according to claim 15, wherein The mode switching of the enhanced multi-link operation includes: When the second device needs to switch to the EMLSR mode, the second device sends a second frame to the first device, where the second frame carries a control field for announcing the switching of the EMLSR mode; wherein the control field includes the EMLSR mode subfield; When the second device receives the second response frame fed back by the first device, the switching of the EMLSR mode is completed.

17. The method according to claim 15, wherein: The mode switching of the enhanced multi-link operation includes: When the second device needs to switch to the EMLSR mode, the second device sends a second frame to the third device, where the second frame carries a control field for announcing the switching of the EMLSR mode; wherein the control field includes the EMLSR mode subfield; When the second device receives the second response frame fed back by the third device, the switching of the EMLSR mode is completed.

18. The method according to claim 17, wherein The third device is configured to use a third frame at a first time to announce switching information to other devices associated with the third device and supporting the direct communication with the second device.

19. The method according to claim 18, wherein the first time is any time after the EMLSR mode switching is completed and before the shared TXOP is triggered to perform the direct communication.

20. The method of claim 15, further comprising: When the second device needs to switch to the EMLSR mode, the second device sends a fourth frame to the third device, requesting the third device to declare the EML operation mode of other devices performing the direct communication with the second device; The third device is configured to use a third frame to announce switching information to other devices associated with the third device and supporting the direct communication with the second device after responding to the request.

21. The method according to claim 20, wherein The third frame carries the first information; The first information includes: a fourth subfield for indicating the identity information corresponding to the device with peer EML capability, and a fifth subfield for indicating the EMLSR mode corresponding to the device with peer EML capability.

22. The method according to claim 21, wherein The corresponding identity information of the device with peer EML capability includes: a MAC address and / or an AID assigned when associated with the third device.

23. The method according to claim 20, wherein The fourth frame is a frame of a different type from the third frame, or a frame of the same type as the third frame.

24. The method according to claim 20, wherein The fourth frame carries a field for indicating that the current frame belongs to a request frame of a peer EML-capable device.

25. The method according to claim 20, wherein The fourth frame carries a field for indicating whether the current frame belongs to a request frame or an announcement frame of a peer EML-capable device.

26. The method according to claim 24 or 25, wherein the fourth frame comprises: a first value and first information; The first value is used to identify the interaction of the EML capability information. The first information includes: a fourth subfield for indicating the identity information corresponding to the device with peer EML capability, and a fifth subfield for indicating the EMLSR mode corresponding to the device with peer EML capability.

27. A communication method, applied to a first device, comprising: Establishing a direct communication relationship between a first STA attached to the first device and a second STA attached to the second device; Transmitting frames using an enhanced multi-link operation between a first STA attached to the first device and a second STA attached to the second device according to the direct communication relationship; The first STA to which the first device is attached sends a sixth frame to the second STA to which the second device is attached in the form of a single link and a single spatial stream.

28. The method according to claim 27, wherein A first STA to which the first device is attached and a second STA to which the second device is attached operate on the same link.

29. The method according to claim 27 or 28, further comprising: A first STA to which the first device is attached requests a required TXOP time from the third device; The first STA to which the first device is attached receives the fifth frame sent by the third device, wherein the third device is configured to share the TXOP time with the first STA to which the first device is attached in TXOP sharing mode 2.

30. The method of claim 27, further comprising: The first STA attached to the first device and the second STA attached to the second device can both receive and parse the fifth frame on their respective working EMLSR link sets.

31. The method of claim 29, further comprising: While a first STA to which the first device is attached sends the sixth frame to a second STA to which the second device is attached, the first device performs EMLSR link switching.

32. The method of claim 29, further comprising: The first device performs EMLSR link switching within the time period when the first STA attached to the first device receives and feeds back the fifth frame, and / or within the time period when the sixth frame is sent to the second STA attached to the second device and feedback of the sixth frame is received.

33. The method according to claim 27 or 28, wherein The sixth frame carries padding information, where the padding information satisfies at least one of the following conditions: a switching delay requirement of the second device; a switching delay requirement of the first device; The switching delay requirement between the second device and the first device.

34. The method according to claim 27 or 28, further comprising: The first STA attached to the first device requests the required TXOP time from the third device and indicates the first identity information; wherein the first identity information is the identity information of the second STA attached to the second device, and the second STA attached to the second device is associated with the third device and exchanges each other's EML capability information.

35. The method of claim 34, further comprising: A first STA to which the first device is attached receives a fifth frame or a variant of the fifth frame sent by the third device, wherein the third device is configured to share the TXOP time with at least one of the first STA to which the first device is attached and the second STA to which the second device is attached in TXOP sharing mode 2.

36. The method according to claim 35, wherein The fifth frame or a variant of the fifth frame is used to allocate a TXOP to at least one of a first STA to which the first device is attached and a second STA to which the second device is attached.

37. The method according to claim 35 or 36, wherein The fifth frame or a variant of the fifth frame includes a user information list field; the user information list field is used to request the required TXOP time from the third device.

38. The method of claim 37, wherein: The user information list field includes: a first indication subfield for indicating a device, a second indication subfield for indicating roles of both parties in direct communication, and a third indication subfield for indicating a TXOP time.

39. The method according to claim 38, wherein The third indication subfield is a second value, and the second value is used to indicate that the current device is a responder for direct communication with the first STA attached to the first device.

40. The method according to any one of claims 35 to 39, further comprising: The variant of the fifth frame is determined according to the values ​​of the first reserved field and the first reserved field subfield in the public information.

41. The method according to any one of claims 35 to 40, further comprising: The first STA attached to the first device and the second STA attached to the second device can both receive and parse the fifth frame on their respective working EMLSR link sets.

42. The method according to any one of claims 35 to 41, further comprising: When at least one of a first STA to which the first device is attached and a second STA to which the second device is attached receives the fifth frame or a variant of the fifth frame, at least one of the first device and the second device performs EMLSR link switching.

43. The method according to claim 27 or 28, further comprising: The first STA attached to the first device requests the required TXOP time from the third device and indicates the first identity information; wherein the first identity information is the identity information of the second STA attached to the second device, and the second STA attached to the second device is associated with the third device and exchanges each other's EML capability information.

44. The method of claim 43, further comprising: The first STA attached to the first device receives the fifth frame sent by the third device, and the third device is configured to share the TXOP time with at least one of the first STA attached to the first device and the second STA attached to the second device in TXOP sharing mode 2.

45. The method of claim 44, further comprising: In a case where the second STA attached to the second device that receives the sixth frame completes link switching, the single-link multi-spatial stream state is maintained before a second time is reached.

46. ​​The method of claim 45, wherein The second time is obtained according to the fifth frame time sent at the lowest rate, the fifth frame feedback time, and the short interframe space SIFS.

47. The method of claim 46, further comprising: When the fifth frame is sent to the second STA to which the second device is attached, feedback of the fifth frame is triggered.

48. The method according to any one of claims 45 to 47, further comprising: When at least one of the first device and the second device completes EMLSR link switching, frame exchange of single-link multiple spatial streams is performed.

49. A communication method, applied to a second device, comprising: Establishing a direct communication relationship between a first STA attached to the first device and a second STA attached to the second device; Transmitting frames using an enhanced multi-link operation between a first STA attached to the first device and a second STA attached to the second device according to the direct communication relationship; The second STA to which the second device is attached receives the sixth frame, and the sixth frame is sent by the first STA to which the first device is attached in the form of a single link and a single spatial stream.

50. The method of claim 49, wherein A first STA to which the first device is attached and a second STA to which the second device is attached operate on the same link.

51. The method according to claim 49 or 50, further comprising: The second device performs EMLSR link switching.

52. The method of claim 51 , further comprising: When the second device completes the EMLSR link switching, frame exchange of single-link multiple spatial streams is performed.

53. A first device, comprising: a first transmission unit, configured to, when establishing direct communication with a second device operating on the same link, perform frame transmission between the first device and the second device using an enhanced multi-link operation; At least one of the first device and the second device is a device that supports the enhanced multi-link operation or a device that works in the enhanced multi-link operation.

54. The apparatus of claim 53, further comprising: The second transmission unit is configured to apply for a transmission opportunity TXOP from the third device; The third device is used to share a TXOP with the first device and the second device for the direct communication, and uniformly schedule frame transmission between the first device and the second device within a TXOP sharing time.

55. Apparatus according to claim 53 or 54, wherein The first transmission unit is further configured to: When the enhanced multi-link operation is an enhanced multi-link single radio (EMLSR) operation, a single-link multi-spatial stream frame exchange is performed with the second device on one of the multiple links of the second device.

56. The apparatus of claim 55, wherein The multiple links include: multiple EMLSR links.

57. The apparatus of claim 55, wherein The first device is used to provide services for the second device operating in the EMLSR mode; the second device is used to support the EMLSR operation and operate in the EMLSR mode.

58. The apparatus of claim 55, wherein The first device is configured to provide services for the second device operating in the EMLSR mode, and / or support the EMLSR operation and operate in the EMLSR mode; The second device is configured to provide services for the first device operating in the EMLSR mode, and / or support the EMLSR operation and operate in the EMLSR mode.

59. The apparatus of any one of claims 55-58, further comprising: An interaction unit is used to interact with the first capability information when establishing the direct communication with the second device; wherein the first capability is: the ability to support the EMLSR operation and provide services for the device working in the EMLSR mode or the ability to work in the EMLSR mode.

60. The apparatus of claim 59, wherein The first capability information is carried in a multilink element.

61. The apparatus of claim 60, wherein The multi-link element includes at least one of the following modes: When the multilink element is a basic multilink element, the first capability information is carried by a common information field in the basic multilink element; wherein the subfield of the first capability information includes: a first subfield for indicating an EMLSR mode, and a second subfield for indicating support for EMLSR operation in the direct communication; or, When the multilink element is a P2P variant multilink element, the first capability information is carried through the common information field in the P2P variant multilink element; wherein the P2P variant multilink element also includes: a multilink control field carrying a third subfield, and the third subfield is used to indicate the type of the multilink element.

62. The apparatus of claim 60, further comprising: a third transmission unit, configured to send the first frame to the third device; The subfield of the first capability information is carried in the first frame, so that the third device knows that the first device supports EMLSR operation and can provide services for the second device operating in EMLSR mode.

63. The apparatus of claim 60, further comprising: The fourth transmission unit is used to send a first frame to the second device, carrying a subfield of the first capability information in the first frame, so that the second device knows that the first device supports EMLSR operation and can provide services for the second device operating in EMLSR mode.

64. The apparatus of claim 63, further comprising: The first receiving unit is configured to receive a first response frame fed back by the second device, where the first response frame carries a subfield of the first capability information.

65. The apparatus according to any one of claims 62 to 64, wherein The first device provides services for at least one device operating in the EMLSR mode, and / or operates in the EMLSR mode after declaring that the EMLSR mode is enabled.

66. A second device, comprising: The first switching unit is configured to perform mode switching of the enhanced multi-link operation with the first device that executes claims 1-13 after interacting with the first capability information.

67. The apparatus of claim 66, wherein The second device is configured to support mode switching of the enhanced multi-link operation; The enhanced multi-link operation is an enhanced multi-link single radio (EMLSR) operation.

68. The apparatus of claim 67, wherein The switching unit is further configured to: When the EMLSR mode needs to be switched, a second frame is sent to the first device, where the second frame carries a control field to announce the switching of the EMLSR mode; wherein the control field includes the EMLSR mode subfield; When the second response frame fed back by the first device is received, the switching of the EMLSR mode is completed.

69. The apparatus of claim 67, wherein The first switching unit is further configured to: When the EMLSR mode needs to be switched, a second frame is sent to the third device, where the second frame carries a control field to announce the switching of the EMLSR mode; wherein the control field includes the EMLSR mode subfield; When the second response frame fed back by the third device is received, the switching of the EMLSR mode is completed.

70. The apparatus of claim 69, wherein The third device is configured to use a third frame at a first time to announce switching information to other devices associated with the third device and supporting the direct communication with the second device.

71. The device according to claim 70, wherein the first time is any time after the EMLSR mode switching is completed and before the shared TXOP is triggered to perform the direct communication.

72. The apparatus of claim 67, further comprising: a fifth transmission unit, configured to, when switching to the EMLSR mode is required, send a fourth frame to the third device, requesting the third device to declare the EML operation mode of other devices performing the direct communication with the second device; The third device is configured to use a third frame to announce switching information to other devices associated with the third device and supporting the direct communication with the second device after responding to the request.

73. The apparatus of claim 72, wherein: The third frame carries the first information; The first information includes: a fourth subfield for indicating the identity information corresponding to the device with peer EML capability, and a fifth subfield for indicating the EMLSR mode corresponding to the device with peer EML capability.

74. The apparatus of claim 73, wherein The corresponding identity information of the device with peer EML capability includes: a MAC address and / or an AID assigned when associated with the third device.

75. The apparatus of claim 72, wherein The fourth frame is a frame of a different type from the third frame, or a frame of the same type as the third frame.

76. The apparatus of claim 72, wherein The fourth frame carries a field for indicating that the current frame belongs to a request frame of a peer EML-capable device.

77. The apparatus of claim 72, wherein The fourth frame carries a field for indicating whether the current frame belongs to a request frame or an announcement frame of a peer EML-capable device.

78. The apparatus of claim 76 or 77, wherein the fourth frame comprises: a first value and first information; The first value is used to identify the interaction of the EML capability information. The first information includes: a fourth subfield for indicating the identity information corresponding to the device with peer EML capability, and a fifth subfield for indicating the EMLSR mode corresponding to the device with peer EML capability.

79. A first device, comprising: A first communication unit is configured to establish a direct communication relationship between a first STA attached to the first device and a second STA attached to the second device; A sixth transmission unit, configured to perform frame transmission by using an enhanced multi-link operation between a first STA attached to the first device and a second STA attached to the second device according to the direct communication relationship; The first STA to which the first device is attached sends a sixth frame to the second STA to which the second device is attached in the form of a single link and a single spatial stream.

80. The apparatus of claim 79, wherein A first STA to which the first device is attached and a second STA to which the second device is attached operate on the same link.

81. The apparatus of claim 79 or 80, further comprising: a first requesting unit, configured to request a required TXOP time from the third device; The second receiving unit is configured to receive a fifth frame sent by the third device, wherein the third device is configured to share the TXOP time with a first STA attached to the first device in TXOP sharing mode 2.

82. The apparatus of claim 79, further comprising: The third receiving unit is configured to enable both the first STA attached to the first device and the second STA attached to the second device to receive and parse the fifth frame on the respective working EMLSR link sets.

83. The apparatus of claim 81 , further comprising: The second switching unit is configured to, while a first STA to which the first device is attached sends the sixth frame to a second STA to which the second device is attached, perform EMLSR link switching on the first device.

84. The apparatus of claim 81 , further comprising: The third switching unit is used to perform EMLSR link switching on the first device within the time period corresponding to the first STA attached to the first device receiving and feeding back the fifth frame, and / or within the time period of sending the sixth frame to the second STA attached to the second device and receiving feedback of the sixth frame.

85. The apparatus of claim 79 or 80, wherein The sixth frame carries padding information, where the padding information satisfies at least one of the following conditions: a switching delay requirement of the second device; a switching delay requirement of the first device; The switching delay requirement between the second device and the first device.

86. The apparatus of claim 79 or 80, further comprising: a second requesting unit, configured to request the required TXOP time from the third device and indicate the first identity information; The first identity information is the identity information of the second STA to which the second device is attached. The second STA to which the second device is attached is associated with the third device and exchanges EML capability information with each other.

87. The apparatus of claim 86, further comprising: The fourth receiving unit is configured to receive a fifth frame or a variant of the fifth frame sent by the third device, wherein the third device is configured to share the TXOP time with at least one of a first STA attached to the first device and a second STA attached to the second device in TXOP sharing mode 2.

88. The apparatus of claim 87, wherein The fifth frame or a variant of the fifth frame is used to allocate a TXOP to at least one of a first STA to which the first device is attached and a second STA to which the second device is attached.

89. The apparatus of claim 87 or 88, wherein The fifth frame or a variant of the fifth frame includes a user information list field; the user information list field is used to request the required TXOP time from the third device.

90. The apparatus of claim 89, wherein The user information list field includes: a first indication subfield for indicating a device, a second indication subfield for indicating roles of both parties in direct communication, and a third indication subfield for indicating a TXOP time.

91. The apparatus of claim 90, wherein The third indication subfield is a second value, and the second value is used to indicate that the current device is a responder for direct communication with the first STA attached to the first device.

92. The apparatus of any one of claims 87-91, further comprising: The variant of the fifth frame is determined according to the values ​​of the first reserved field and the first reserved field subfield in the public information.

93. The apparatus of any one of claims 87-92, further comprising: The fifth receiving unit is configured to enable both the first STA attached to the first device and the second STA attached to the second device to receive and parse the fifth frame on the respective working EMLSR link sets.

94. The apparatus of any one of claims 87-93, further comprising: The fourth switching unit is configured to cause at least one of the first device and the second device to perform EMLSR link switching when at least one of the first STA to which the first device is attached and the second STA to which the second device is attached receives the fifth frame or a variant of the fifth frame.

95. The apparatus of claim 79 or 80, further comprising: A third requesting unit is used to request the required TXOP time from the third device and indicate the first identity information; wherein the first identity information is the identity information of the second STA attached to the second device, and the second STA attached to the second device is associated with the third device and exchanges each other's EML capability information.

96. The apparatus of claim 95, further comprising: The sixth receiving unit is configured to receive a fifth frame sent by the third device, where the third device is configured to share the TXOP time with at least one of a first STA attached to the first device and a second STA attached to the second device in TXOP sharing mode 2.

97. The apparatus of claim 96, further comprising: The maintaining unit is configured to, when the second STA to which the second device is attached that receives the sixth frame completes link switching, continue to maintain the single-link multi-spatial stream state before a second time is reached.

98. The apparatus of claim 97, wherein The second time is obtained according to the fifth frame time sent at the lowest rate, the fifth frame feedback time, and the short interframe space SIFS.

99. The apparatus of claim 98, further comprising: The triggering unit is configured to trigger feedback of the fifth frame when the fifth frame is sent to the second STA to which the second device is attached.

100. The apparatus of any one of claims 97-99, further comprising: The first switching unit is configured to perform single-link multi-spatial stream frame switching when at least one of the first device and the second device completes EMLSR link switching.

101. A second device, comprising: A second communication unit is configured to establish a direct communication relationship between a first STA attached to the first device and a second STA attached to the second device; A seventh transmission unit, configured to perform frame transmission by using an enhanced multi-link operation between a first STA attached to the first device and a second STA attached to the second device according to the direct communication relationship; The second STA to which the second device is attached receives the sixth frame, and the sixth frame is sent by the first STA to which the first device is attached in the form of a single link and a single spatial stream.

102. The apparatus of claim 101, wherein A first STA to which the first device is attached and a second STA to which the second device is attached operate on the same link.

103. The apparatus of claim 101 or 102, further comprising: The fifth switching unit is configured to perform EMLSR link switching.

104. The apparatus of claim 103, further comprising: The second switching unit is configured to perform frame switching of a single link and multiple spatial streams when the second device completes the EMLSR link switching.

105. A chip comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip performs the method according to any one of claims 1 to 13, claims 14 to 26, claims 27 to 48, and claims 49 to 52.

106. A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method of any one of claims 1 to 13, claims 14 to 26, claims 27 to 48, and claims 49 to 52.

107. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 13, claims 14 to 26, claims 27 to 48, and claims 49 to 52.

108. A computer program causing a computer to perform the method of any one of claims 1 to 13, claims 14 to 26, claims 27 to 48, and claims 49 to 52.

109. A communication system comprising: A first device for performing the method according to any one of claims 1 to 13 and claims 27 to 48; A second device is configured to perform the method according to any one of claims 14 to 26 and claims 49 to 52.

Images