Multi-link communication method and multi-link device

Abstract

Provided in the present application are a multi-link communication method and a multi-link device, which are applied to a wireless local area network system that supports series of protocols, such as IEEE 802.11ax next-generation WiFi protocols, for example, 802.11be and WiFi 7, and 802.11be next-generation protocols, for example, WiFi 8, and can also be applied to a wireless personal area network system based on an ultra wideband. The method comprises: a first multi-link device sending, to a second multi-link device, a radio frame which comprises indication information, wherein the indication information is used for indicating that the first multi-link device supports a cross-link capability, and on the basis of the indication information, the second multi-link device can determine that the first multi-link device supports the cross-link capability, and the first multi-link device and the second multi-link device can thus perform more effective uplink and downlink traffic transmission on a high band on the basis of the fact that the first multi-link device supports the cross-link capability.

Description

Multi-link communication method and multi-link device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on June 21, 2023, with application number 202310748511.0 and application name “Multi-link Communication Method and Multi-link Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more specifically, to a multi-link communication method and a multi-link device. Background Art

[0003] Multi-link devices (MLDs), such as access point (AP) multi-link devices and station (STA) multi-link devices, can support multi-link communications. For example, they can communicate simultaneously on the 2.4 GHz, 5 GHz, and 6 GHz frequency bands, thereby significantly improving throughput.

[0004] Specifically, downlink transmission between AP MLDs and STA MLDs on low-frequency links cannot meet the requirements of low latency and high throughput due to the limited bandwidth. Therefore, AP MLDs and STA MLDs need to use high-frequency links to meet these requirements. The coverage of high-frequency bands is smaller than that of low-frequency bands, so downlink transmission between AP MLDs and STA MLDs is not affected. However, uplink transmission between AP MLDs and STA MLDs is affected. Therefore, how to support more efficient uplink and downlink service transmission between AP MLDs and STA MLDs on high-frequency bands is a pressing technical issue.

[0005] Summary of the Invention

[0006] The present application provides a multi-link communication method and a multi-link device, which can support AP MLD and STA MLD to perform more efficient uplink and downlink service transmission in high frequency bands.

[0007] In a first aspect, a multi-link communication method is provided, comprising: a first multi-link device determining a first radio frame, the first radio frame including first indication information, the first indication information being used to indicate that the first multi-link device supports cross-link capability, the cross-link capability being the ability of the first multi-link device to confirm, on a second link, service transmission between the first multi-link device and a second multi-link device on the first link; and the first multi-link device sending the first radio frame to the second multi-link device.

[0008] Specifically, the first multi-link device may be a STA MLD, and the second multi-link device may be an AP MLD; or, the first multi-link device may be an AP MLD, and the second multi-link device may be a STA MLD, and this is not limited. When the first multi-link device is a STA MLD, the above-mentioned cross-link capability may be a cross-link uplink capability. When the first multi-link device is an AP MLD, the above-mentioned cross-link capability may be a cross-link downlink capability. Among them, the cross-link uplink capability means that the AP MLD sends downlink services to the STA MLD through the second link, and when the STA MLD cannot confirm the downlink services through the second link, the STA MLD confirms the downlink services to the AP MLD through the first link. The cross-link downlink capability means that when the AP MLD cannot send downlink services to the STA MLD through the first link, the AP MLD can send downlink services to the STA MLD through the second link, and the STA MLD can confirm the downlink services to the AP MLD through the first link.

[0009] It should be noted that when the aforementioned service transmission is data service transmission, the first multi-link device may send an acknowledgment frame (which may be understood as an acknowledgment) via the second link to confirm receipt of the data service transmission; when the aforementioned service transmission is control service transmission (e.g., a channel sounding task), the first multi-link device may send a wireless frame (which may be understood as an acknowledgment or feedback) via the second link to provide feedback on the control service transmission. Therefore, this application does not limit the specific meaning of the aforementioned "acknowledgment."

[0010] By carrying indication information in a radio frame that indicates that a multi-link device has cross-link capability, the present application supports interaction between multi-link devices to demonstrate that the multi-link device supports cross-link capability, thereby supporting cross-link communication between multi-link devices. Furthermore, it can support more efficient uplink and downlink service transmission between multi-link devices on high-frequency links. For example, a second multi-link device sends a data frame to a first multi-link device via a high-frequency link, and the first multi-link device replies with an acknowledgment frame corresponding to the data frame to the second multi-link device via a low-frequency link. In this way, complete uplink and downlink service transmission between the first and second multi-link devices can be completed.

[0011] In one possible implementation, the method further includes: the first multi-link device sending a second radio frame to the second multi-link device, where the second radio frame is used to indicate whether the first link enables the cross-link capability; and the first multi-link device receiving a first confirmation frame sent by the second multi-link device, where the first confirmation frame is used to confirm receipt of the second radio frame.

[0012] Specifically, the second radio frame is used to indicate whether the first link enables the cross-link capability, which is only a general reference. That is, the second radio frame can also be used to indicate whether other links enable the cross-link capability, and this is not limited.

[0013] It should be noted that whether the first link enables the cross-link capability may take effect immediately after the first confirmation frame is sent, or may take effect after a first delay after the first confirmation frame is sent, and there is no limitation on this.

[0014] In this way, the interaction of whether to activate the cross-link capability of the link can be completed, thereby supporting more efficient uplink and downlink service transmission between multi-link devices on high-frequency links.

[0015] In one possible implementation, the method further includes: the first multi-link device receiving a third radio frame sent by the second multi-link device, where the third radio frame is used to indicate whether the first link enables the cross-link capability; and the first multi-link device sending a second confirmation frame to the second multi-link device, where the second confirmation frame is used to confirm receipt of the third radio frame.

[0016] In this way, the interaction between the first multi-link device and the second multi-link device on whether to activate the cross-link capability of the link can be completed. Further, the complete interaction between the multi-link devices on whether to enable the cross-link capability of the multi-link devices can be completed.

[0017] In one possible implementation, the second radio frame is used to instruct the first link to enable the cross-link capability. The method further includes: the first multi-link device receives a data frame sent by the second multi-link device through the first link; the first multi-link device receives a request frame sent by the second multi-link device through the second link, where the request frame is used to request the first multi-link device to send a third confirmation frame on the second link, where the third confirmation frame is used to confirm receipt of the data frame; and the first multi-link device sends the third confirmation frame to the second multi-link device through the second link.

[0018] Specifically, when the first link enables the cross-link capability, through the above technical solution, the first multi-link device and the second multi-link device can transmit downlink data services on the high-frequency link, and transmit uplink confirmation services on the low-frequency link. This can fully utilize the large bandwidth capability of the high frequency band and make downlink data transmission more reliable.

[0019] In one possible implementation, the second radio frame is used to instruct the first link to enable the cross-link capability. The method also includes: the first multi-link device receives a null data physical protocol data unit announcement (NDPA) frame sent by the second multi-link device through the first link, the NDPA frame including second indication information, the second indication information being used to instruct the first multi-link device to send a beamforming report (BFR) frame on a non-first link, the BFR frame including channel information of the first link, the channel information of the first link being obtained by the first multi-link device based on a null data physical protocol data unit (NDP) frame; the first multi-link device receives the NDP frame sent by the second multi-link device through the first link; and the first multi-link device sends the BFR frame to the second multi-link device through the second link.

[0020] In this way, the first multi-link device can feed back the BFR frame corresponding to the first link on the non-first link.

[0021] Specifically, when the first link enables the cross-link capability, the first multi-link device and the second multi-link device can better complete the channel detection task through the above technical solution.

[0022] In one possible implementation, the second radio frame is used to indicate that the first link enables the cross-link capability. The method also includes: the first multi-link device receives an NDPA frame sent by the second multi-link device through the first link, the NDPA frame includes identification information of the second link, and the identification information of the second link is used to indicate that the first multi-link device sends a BFR frame on the second link, the BFR frame includes channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on the NDP frame; the first multi-link device receives the NDP frame sent by the second multi-link device through the first link; and the first multi-link device sends the BFR frame to the second multi-link device through the second link.

[0023] In this way, the first multi-link device can feed back the BFR frame corresponding to the first link on the non-first link.

[0024] Specifically, when the first link enables the cross-link capability, the first multi-link device and the second multi-link device can better complete the channel detection task through the above technical solution.

[0025] In one possible implementation, the second radio frame is used to instruct the first link to enable the cross-link capability. The method also includes: the first multi-link device receives an NDPA frame sent by the second multi-link device through the first link; the first multi-link device receives an NDP frame sent by the second multi-link device through the first link; the first multi-link device receives a beamforming report poll (BFRP) frame sent by the second multi-link device through the second link, where the BFRP frame is used to instruct the first multi-link device to send a BFR frame on the second link, where the BFR frame includes channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on the NDP frame; the first multi-link device sends the BFR frame to the second multi-link device through the second link.

[0026] In this way, the first multi-link device can feed back the BFR frame corresponding to the first link on the non-first link.

[0027] Specifically, when the first link enables the cross-link capability, the first multi-link device and the second multi-link device can better complete the channel detection task through the above technical solution.

[0028] In a possible implementation, the BFRP frame includes identification information of the first link, and the identification information of the first link is used to instruct the first multi-link device to send the BFRP frame on the second link.

[0029] In one possible implementation, the second wireless frame is used to indicate that the first link enables the cross-link capability. The method also includes: the first multi-link device receives an NDPA frame sent by the second multi-link device through the first link, the NDPA frame includes a detection dialogue token value, and the detection dialogue token value uniquely corresponds to the first link; the first multi-link device receives an NDP frame sent by the second multi-link device through the first link; the first multi-link device sends a BFR frame to the second multi-link device through the second link, the BFR frame includes the detection dialogue token value, and the BFR frame includes channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on the NDP frame.

[0030] Through the above scheme, this application supports making minor changes to the structure of the NDPA frame.

[0031] In a possible implementation, the method further includes: the first multi-link device receiving a fourth radio frame sent by the second multi-link device, where the fourth radio frame is used to respond to the first radio frame.

[0032] Through the above technical solution, the first multi-link device determines that the second multi-link device has obtained the cross-link capability supported by the first multi-link device. In this way, full interaction between the multi-link devices on the cross-link capability supported by the multi-link devices can be completed.

[0033] In a possible implementation manner, the first radio frame is any one of the following: a probe request frame, an association request frame, or a beacon frame.

[0034] In a second aspect, a multi-link communication method is provided, including: a second multi-link device receiving a first radio frame sent by a first multi-link device, the first radio frame including first indication information, the first indication information being used to indicate that the first multi-link device supports cross-link capability, the cross-link capability being the ability of the first multi-link device to confirm, on a second link, service transmission between the first multi-link device and the second multi-link device on the first link; and the second multi-link device determining, based on the first indication information, that the first multi-link device supports the cross-link capability.

[0035] In one possible implementation, the method further includes: the second multi-link device receiving a second radio frame sent by the first multi-link device, the second radio frame being used to indicate whether the first link enables the cross-link capability; and the second multi-link device sending a first confirmation frame to the first multi-link device, the first confirmation frame being used to confirm receipt of the second radio frame.

[0036] In one possible implementation, the method further includes: the second multi-link device sending a third radio frame to the first multi-link device, where the third radio frame is used to indicate whether the first link enables the cross-link capability; and the second multi-link device receiving a second confirmation frame sent by the first multi-link device, where the second confirmation frame is used to confirm receipt of the third radio frame.

[0037] In one possible implementation, the second radio frame is used to instruct the first link to enable the cross-link capability. The method further includes: the second multi-link device sends a data frame to the first multi-link device through the first link; the second multi-link device sends a request frame to the first multi-link device through the second link, where the request frame is used to request the first multi-link device to send a third confirmation frame through the second link, where the third confirmation frame is used to confirm receipt of the data frame; and the second multi-link device receives the third confirmation frame sent by the first multi-link device through the second link.

[0038] In one possible implementation, the second radio frame is used to instruct the first link to enable the cross-link capability. The method also includes: the second multi-link device sends an NDPA frame to the first multi-link device through the first link, the NDPA frame includes second indication information, and the second indication information is used to instruct the first multi-link device to send a BFR frame on a non-first link, the BFR frame includes channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on the NDP frame; the second multi-link device sends the NDP frame to the first multi-link device through the first link; and the second multi-link device receives the BFR frame sent by the second multi-link device through the second link.

[0039] In one possible implementation, the second radio frame is used to instruct the first link to enable the cross-link capability. The method also includes: the second multi-link device sends an NDPA frame to the first multi-link device through the first link, the NDPA frame includes identification information of the second link, and the identification information of the second link is used to instruct the first multi-link device to send a BFR frame on the second link, the BFR frame includes channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on the NDP frame; the second multi-link device sends the NDP frame to the first multi-link device through the first link; and the second multi-link device receives the BFR frame sent by the first multi-link device through the first link.

[0040] In one possible implementation, the second radio frame is used to instruct the first link to enable the cross-link capability. The method also includes: the second multi-link device sends an NDPA frame to the first multi-link device through the first link; the second multi-link device sends an NDP frame to the first multi-link device through the first link; the second multi-link device sends a BFRP frame to the first multi-link device through the second link, where the BFRP frame is used to instruct the first multi-link device to send a BFR frame on the second link, where the BFR frame includes channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on the NDP frame; the second multi-link device receives the BFR frame sent by the first multi-link device through the second link.

[0041] In a possible implementation, the BFRP frame includes identification information of the first link, and the identification information of the first link is used to instruct the first multi-link device to send the BFRP frame on the second link.

[0042] In one possible implementation, the second wireless frame is used to instruct the first link to enable the cross-link capability, and the method also includes: the second multi-link device sends an NDPA frame to the first multi-link device through the first link, the NDPA frame includes a detection dialogue token value, and the detection dialogue token value uniquely corresponds to the first link; the second multi-link device sends an NDP frame to the first multi-link device through the first link; the second multi-link device receives a BFR frame sent by the first multi-link device through the second link, the BFR frame includes the detection dialogue token value, and the BFR frame includes channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on the NDP frame.

[0043] In a possible implementation, the method further includes: the second multi-link device sending a fourth radio frame to the first multi-link device, where the fourth radio frame is used to respond to the first radio frame.

[0044] In a possible implementation manner, the first radio frame is any one of the following: a probe request frame, an association request frame, or a beacon frame.

[0045] According to a third aspect, a communication apparatus is provided. The communication apparatus may be a first multi-link device, or may be a device or module for executing the first multi-link device.

[0046] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the first aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.

[0047] In one possible implementation, the communication device includes: a processing unit, configured to determine a first radio frame, the first radio frame including first indication information, the first indication information being used to indicate that the communication device supports cross-link uplink capability; and a transceiver unit, configured to send the first radio frame to a second multi-link device.

[0048] The communication device described in the third aspect can also be used to execute any of the methods described in the first aspect.

[0049] In a fourth aspect, a communication apparatus is provided. The communication apparatus may be a second multi-link device, or may be a device or module for executing the second multi-link device.

[0050] In one possible implementation, the communication device may include a module or unit corresponding to each of the methods / operations / steps / actions described in the second aspect. The module or unit may be a hardware circuit, software, or a combination of hardware circuit and software.

[0051] In one possible implementation, the communication device includes: a transceiver unit, configured to receive a first radio frame sent by a first multi-link device, the first radio frame including first indication information, the first indication information being used to indicate that the first multi-link device supports cross-link uplink capability; and a processing unit, configured to determine, based on the first indication information, that the first multi-link device supports cross-link uplink capability.

[0052] The communication device described in the fourth aspect can also be used to execute any of the methods described in the second aspect.

[0053] In a fifth aspect, a communication device is provided, comprising a processor, wherein the processor is configured to, by executing a computer program or instruction, or by a logic circuit, enable the communication device to execute the first aspect and any possible method described in the first aspect; or enable the communication device to execute the second aspect and any possible method described in the second aspect.

[0054] In a possible implementation, the communication device further includes a memory for storing the computer program or instruction.

[0055] In a possible implementation, the communication device further includes a communication interface, which is used to input and / or output signals.

[0056] In the sixth aspect, a communication device is provided, comprising a logic circuit and an input / output interface, the input / output interface being used to input and / or output signals, the logic circuit being used to execute the method described in the first aspect and any possible embodiment of the first aspect; or the logic circuit being used to execute the method described in the second aspect and any possible embodiment of the second aspect.

[0057] In the seventh aspect, a computer-readable storage medium is provided, on which a computer program or instruction is stored. When the computer program or the instruction is run on a computer, the method described in the first aspect and any possible method of the first aspect is executed; or, the method described in the second aspect and any possible method of the second aspect is executed.

[0058] In an eighth aspect, a computer program product is provided, comprising instructions, which, when executed on a computer, cause the method described in the first aspect and any possible method of the first aspect to be executed; or cause the method described in the second aspect and any possible method of the second aspect to be executed.

[0059] The description of the beneficial effects of the second to eighth aspects may correspond to the description of the beneficial effects of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0060] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application.

[0061] FIG2 is a schematic diagram of the association relationship between multi-link devices according to an embodiment of the present application.

[0062] FIG3 is a schematic diagram of an interaction flow of a multi-link communication method 300 according to an embodiment of the present application.

[0063] FIG4 is a schematic diagram of the structure of a wireless frame 1 according to an embodiment of the present application.

[0064] FIG5 is an interactive flow chart of a multi-link communication method 500 according to an embodiment of the present application.

[0065] FIG6 is a schematic diagram of the structure of the wireless frame 3 according to an embodiment of the present application.

[0066] FIG7 is an interactive flow chart of a multi-link communication method 700 according to an embodiment of the present application.

[0067] FIG8 is a schematic diagram of an interaction flow of a multi-link communication method 800 according to an embodiment of the present application.

[0068] FIG9 is a schematic diagram of an interaction flow of a multi-link communication method 900 according to an embodiment of the present application.

[0069] FIG10 is a schematic diagram of the structure of the NDPA frame 1 according to an embodiment of the present application.

[0070] FIG11 is a schematic diagram of an interaction flow of a multi-link communication method 1100 according to an embodiment of the present application.

[0071] FIG12 is a schematic diagram of the structure of a BFRP frame 2 according to an embodiment of the present application.

[0072] FIG13 is a schematic diagram of the interaction flow of clear-to-send and request-to-send between multi-link devices according to an embodiment of the present application.

[0073] FIG14 is a schematic block diagram of a communication device 1400 according to an embodiment of the present application.

[0074] FIG15 is a schematic block diagram of a communication device 1500 according to an embodiment of the present application.

[0075] FIG16 is a schematic block diagram of a communication device 1600 according to an embodiment of the present application.

[0076] FIG17 is a schematic block diagram of a communication device 1700 according to an embodiment of the present application. DETAILED DESCRIPTION

[0077] In order to facilitate understanding of the embodiments of the present application, the following points are first explained.

[0078] 1. In the various embodiments of this application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features of different embodiments can be combined to form new embodiments based on their internal logical relationships.

[0079] 2. The various numerical numbers involved in this application are only used for the convenience of description and are not used to limit the scope of this application. The size of the serial numbers involved in this application does not mean the order of execution. The order of execution of each process should be determined by its function and internal logic. For example, the terms "first", "second", "third", "fourth" and other various terminology labels (if any) in the specification and claims of this application and the drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate so that the embodiments described here can be implemented in an order other than what is illustrated or described here.

[0080] 3. The terms "comprise" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such process, method, product or apparatus.

[0081] 4. In this application, "used to indicate" can be understood as "enabling," and "enabling" can include direct enabling and indirect enabling. When describing that certain information is used to enable A, it can include that the information directly enables A or indirectly enables A, and does not necessarily mean that the information contains A.

[0082] The information enabled by the information is called information to be enabled. In the specific implementation process, there are many ways to enable the enabled information, such as but not limited to, directly enabling the information to be enabled, such as the information to be enabled itself or the index of the information to be enabled. The information to be enabled can also be indirectly enabled by enabling other information, wherein there is an association between the other information and the information to be enabled. It is also possible to enable only a part of the information to be enabled, while the other parts of the information to be enabled are known or agreed in advance. For example, it is also possible to enable specific information with the help of the arrangement order of each piece of information agreed in advance (such as specified in the protocol), thereby reducing the enabling overhead to a certain extent. At the same time, it is also possible to identify the common parts of each piece of information and enable them uniformly to reduce the enabling overhead caused by enabling the same information separately.

[0083] 5. "Storage" or "saving" as used in this application may refer to storage in one or more memories. The one or more memories may be provided separately or integrated into an encoder or decoder, a processor, or a communication device. The one or more memories may also be provided in part separately and in part integrated into a decoder, a processor, or a communication device. The memory may be any type of storage medium and is not limited in this application.

[0084] 6. The “protocol” referred to in this application may refer to a standard protocol in the field of communications, such as the fourth generation (4G) network, the fifth generation (5G) network protocol, the new radio (NR) protocol, the 5.5G network protocol, the sixth generation (6 th generation, 6G) network protocols and related protocols used in future communication systems, which are not limited in this application.

[0085] 7. The arrows or boxes indicated by dotted lines in the schematic diagrams in the accompanying drawings of this application specification represent optional steps or optional modules.

[0086] 8. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0087] 9. In this application, unless otherwise specified, “ / ” indicates that the objects associated with each other are in an “or” relationship. For example, A / B can represent A or B. “And / or” in this application is only a description of the association relationship between associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A and B can be singular or plural.

[0088] The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0089] The technical solutions of the embodiments of the present application can be applied to wireless local area network (WLAN) scenarios, for example, they can be applied to IEEE 802.11 system standards, such as 802.11a / b / g standards, 802.11n standards, 802.11ac standards, 802.11ax standards, or their next generations, such as 802.11be standards or even later generations.

[0090] The technical solutions of the embodiments of the present application can be applied to wireless local area network (WLAN) scenarios, for example, they can be applied to IEEE 802.11 system standards, such as 802.11a / b / g standards, 802.11n standards, 802.11ac standards, 802.11ax standards, or their next generations, such as 802.11be standards or even later generations.

[0091] Although the embodiments of the present application are primarily described using the deployment of a WLAN network, particularly a network using the IEEE 802.11 system standard, as an example, those skilled in the art will readily appreciate that the various aspects of the embodiments of the present application can be extended to other networks using various standards or protocols, such as Bluetooth, high-performance wireless local area networks (HIPERLANs), wide area networks (WANs), personal area networks (PANs), or other networks now known or later developed. Therefore, regardless of the coverage area and wireless access protocol used, the various aspects provided in the embodiments of the present application can be applied to any suitable wireless network.

[0092] The technical solutions of the embodiments of the present application can also be applied to various communication systems, such as: global system for mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), world-wide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or new radio (NR), future sixth generation (6G) system, Internet of Things (IoT) network or vehicle to X (V2X) and other wireless local area network systems, etc.

[0093] The above-mentioned communication system applicable to the present application is only an example, and the communication system applicable to the present application is not limited to this. It is described uniformly here and will not be repeated below.

[0094] The terminal in the embodiments of the present application may refer to user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G network, a terminal in a future 6G network or a terminal in a public land mobile network (PLMN), etc., and the embodiments of the present application are not limited to this.

[0095] The network device in the embodiment of the present application can be a device for communicating with a terminal. The network device can be a base station (base transceiver station, BTS) in a global system of mobile communication (GSM) system or code division multiple access (CDMA), or a base station (nodeB, NB) in a wideband code division multiple access (WCDMA) system, or an evolved base station (eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN) scenario, or the network device can be a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a 5G network, a network device in a 6G network, or a network device in a PLMN network, etc., and the embodiment of the present application is not limited.

[0096] Figure 1 is a schematic diagram of an application scenario of an embodiment of the present application. In Figure 1, an access point (AP) can be a communication server, a router, a switch, or any of the aforementioned network devices, and a station (STA) can be a mobile phone, a computer, or any of the aforementioned terminals, without limitation in the present embodiment.

[0097] The technical solutions of the embodiments of the present application are applicable not only to communication between an AP and one or more STAs, but also to communication between APs and between STAs. For ease of description, the embodiments of the present application only use communication between an AP and one or more STAs as an example. However, this description does not limit the actual scope of application of the technical solutions of the embodiments of the present application. This is described here as a unified description and will not be repeated later.

[0098] An access point can be an access point for a terminal (such as a mobile phone) to enter a wired (or wireless) network. It is mainly deployed in homes, inside buildings, and inside campuses. The typical coverage radius is tens of meters to hundreds of meters. Of course, it can also be deployed outdoors. An access point is equivalent to a bridge connecting a wired network and a wireless network. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet. Specifically, an access point can be a terminal (such as a mobile phone) or a network device (such as a router) with a Wi-Fi chip. An access point can be a device that supports the 802.11be standard. An access point can also be a device that supports multiple WLAN standards of the 802.11 family, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11a, and the next generation of 802.11be. The access point in this application can be a HE AP or an EHT AP, or it can be an access point that applies to a future generation of Wi-Fi standards.

[0099] A station can be a wireless communication chip, wireless sensor, or wireless communication terminal, also known as a user. For example, a station can be a mobile phone that supports Wi-Fi communication, a tablet that supports Wi-Fi communication, a set-top box that supports Wi-Fi communication, a smart TV that supports Wi-Fi communication, a smart wearable device that supports Wi-Fi communication, an in-vehicle communication device that supports Wi-Fi communication, or a computer that supports Wi-Fi communication. Optionally, a station can support the 802.11be standard. Stations can also support 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11a, and 802.11be-next-generation WLAN standards within the 802.11 family.

[0100] For example, access points and sites can be devices used in the Internet of Vehicles, IoT nodes and sensors in the Internet of Things (IoT), smart cameras and remote controls in smart homes, smart water and electricity meters, and sensors in smart cities.

[0101] The wireless communication system of the embodiment of the present application may be a WLAN or a cellular network, and the method may be implemented by a communication device in the wireless communication system or a chip or processor in the communication device. The communication device may be a wireless communication device that supports parallel transmission of multiple links, for example, a multi-link device (MLD). Compared with a device that only supports transmission of a single link, a multi-link device has higher transmission efficiency and higher throughput. The multi-link device includes one or more affiliated stations STA (affiliated STA). An affiliated STA is a logical station that can work on one link. Among them, the affiliated station may be an AP or a non-AP STA. For the convenience of description, in the embodiment of the present application, a multi-link device whose affiliated station is an AP may be referred to as a multi-link AP or a multi-link AP device or an AP multi-link device (AP MLD), and a multi-link device whose affiliated station is a non-AP STA may be referred to as a multi-link STA or a multi-link STA device or a STA multi-link device (non-AP MLD).

[0102] FIG2 is a schematic diagram of the association relationship between multi-link devices in an embodiment of the present application. The AP MLD shown in FIG2 may include multiple APs, and the STA MLD may include multiple STAs. If the AP MLD needs to communicate with the STA MLD, each AP in the AP MLD needs to be associated with the corresponding STA in the STA MLD. As shown in FIG2 , AP1 in the AP MLD is associated with STA1 in the STA MLD and operates on link 1. AP2 in the AP MLD is associated with STA2 in the STA MLD and operates on link 2. APn in the AP MLD is associated with STAn in the STA MLD and operates on link n. This allows each AP in the AP MLD to establish a connection with the corresponding STA in the STA MLD on its respective link, thereby realizing multi-link communication between the two MLDs.

[0103] As described in the background technology, the AP MLD and STA MLD can communicate via multiple links, including at least a low-frequency link (e.g., 2.4 GHz) and a high-frequency link (e.g., 5 GHz). Low-frequency links have limited bandwidth, significant channel interference, and high channel congestion, making it difficult to meet the quality of service (QoS) requirements for uplink and downlink traffic transmission (e.g., high throughput and low latency). Downlink traffic transmission, in particular, has high bandwidth requirements. To address bandwidth issues, the AP MLD and STA MLD can use high-frequency links for uplink and downlink traffic transmission. Because the coverage of signals transmitted on high-frequency links is limited, even if the AP MLD successfully sends downlink traffic to the STA MLD, the STA MLD may not be able to provide uplink feedback on the downlink traffic, potentially impacting the QoS of uplink and downlink traffic transmission between the AP MLD and STA MLD. Therefore, the AP MLD and STA MLD can provide feedback on downlink traffic transmission on the high-frequency link via the low-frequency link. This requires cross-link uplink capability interaction between the AP MLD and STA MLD. However, how to achieve this and thus support more efficient uplink and downlink service transmission by AP MLD and STA MLD in high frequency bands is a technical problem that needs to be solved urgently.

[0104] In view of this, the present application provides a multi-link communication method and a multi-link device, which can support interaction between multi-link devices regarding the cross-link capabilities of the multi-link devices, and thereby support AP MLD and STA MLD to perform more efficient uplink and downlink service transmission in high frequency bands.

[0105] The multi-link communication method according to an embodiment of the present application will be described below with reference to FIG3 .

[0106] Figure 3 is a schematic flow chart of a multi-link communication method 300 according to an embodiment of the present application. Method 300 involves interaction between multi-link device A (e.g., a first multi-link device) and multi-link device B (e.g., a second multi-link device). Multi-link device A and multi-link device B include N links, where N is a positive integer greater than or equal to 2. For ease of description, the embodiment of the present application is described using N=2 as an example, i.e., multi-link device A and multi-link device B include link 1 (e.g., a first link) and link 2 (e.g., a second link). Exemplarily, link 1 is a high-frequency link, and link 2 is a low-frequency link, but is not limited thereto. Method 300 includes:

[0107] S310: Multi-link device A generates a radio frame 1 (eg, a first radio frame). The radio frame 1 includes indication information 1 (eg, first indication information). The indication information 1 is used to indicate that the multi-link device A supports cross-link capability.

[0108] S320: Multi-link device A sends wireless frame 1 to multi-link device B.

[0109] Accordingly, multi-link device B receives wireless frame 1 .

[0110] S330: The multi-link device B determines, according to the indication information 1, that the multi-link device A supports the cross-link capability.

[0111] Specifically, multi-link device A may be a STA MLD, and multi-link device B may be an AP MLD; or, multi-link device A may be an AP MLD, and multi-link device B may be a STA MLD, and this is not limited. When multi-link device A is a STA MLD, the cross-link capability is the cross-link uplink capability. When multi-link device A is an AP MLD, the cross-link capability is the cross-link downlink capability. The cross-link uplink capability means that the AP MLD sends downlink services to the STA MLD through link 1. When the STA MLD cannot confirm the downlink services through link 1, the STA MLD confirms the downlink services to the AP MLD through link 2. The cross-link downlink capability means that when the AP MLD cannot send downlink services to the STA MLD through link 1, the AP MLD can send downlink services to the STA MLD through link 2, and the STA MLD can confirm the downlink services to the AP MLD through link 1 or link 2. This can also be understood as the AP MLD confirming the service transmission between the AP MLD and the STA MLD on link 1 through link 2.

[0112] In summary, cross-link capability refers to the ability of multi-link device A to confirm service transmission between multi-link device A and multi-link device B on link 1 on link 2. For ease of description, the embodiments of the present application use the cross-link uplink capability as an example to describe the cross-link capability. However, the description of the cross-link uplink capability is also applicable to the description of the cross-link downlink capability. Therefore, the description of the cross-link downlink capability can refer to the description of the cross-link uplink capability and will not be repeated below.

[0113] It should be noted that when the above-mentioned service transmission is data service transmission, multi-link device A can send an acknowledgment frame (which can be understood as an acknowledgment) to confirm the reception of the data service transmission through link 2; when the above-mentioned service transmission is control service transmission (such as a channel sounding task), multi-link device A can send a wireless frame (which can be understood as an acknowledgment or feedback) to provide feedback on the control service transmission through link 2. Therefore, this application does not limit the specific meaning of the above-mentioned acknowledgment.

[0114] Specifically, radio frame 1 includes indication information 1, which is used to indicate to multi-link device B that multi-link device A supports (or has) a cross-link uplink capability (cross link UL capability), that is, it is used to indicate that multi-link device A supports cross-link uplink transmission. The cross-link uplink capability is the ability of multi-link device A to confirm (or provide feedback) on link 2 regarding service transmission (including user data service transmission and control data service transmission, etc.) between multi-link device A and multi-link device B on link 1. For details, please refer to the following description.

[0115] Specifically, when multi-link device A and multi-link device B are transmitting data on link 1, multi-link device A confirms (or provides feedback) on link 2 regarding the data transmission between multi-link device A and multi-link device B on link 1; when multi-link device A and multi-link device B are performing a channel detection task on link 1, multi-link device A confirms (or provides feedback) on link 2 regarding the channel detection task between multi-link device A and multi-link device B on link 1.

[0116] When multi-link device A has cross-link uplink capability, a STA (e.g., STA 1) in multi-link device A (e.g., multi-link device A is a STA MLD) can carry indication information 1 (which can also be a cross-link uplink capability indication field) in radio frame 1 sent to an AP (e.g., AP 1) to be associated with in multi-link device B (e.g., multi-link device B is an AP MLD). If the AP MLD also has cross-link uplink capability, indication information 2 can be carried in radio frame 2 (e.g., the fourth radio frame), indicating that multi-link device B also supports cross-link uplink capability.

[0117] In a possible implementation, the radio frame 1 may be a probe request frame. In this way, the multi-link device A and the multi-link device B interact with each other through the probe request frame to confirm that the multi-link device A supports the cross-link uplink capability.

[0118] In a possible implementation, the radio frame 1 may be an association request frame. In this way, the multi-link device A and the multi-link device B interact through the association request frame to indicate that the multi-link device A supports the cross-link uplink capability.

[0119] In a possible implementation, the radio frame 1 may be a beacon frame. In this way, the multi-link device A and the multi-link device B interact through the beacon frame, and the multi-link device A supports the cross-link uplink capability.

[0120] When the multi-link device A and the multi-link device B exchange wireless frames 1, the present application does not limit the specific link between the multi-link device A and the multi-link device B, and it can be any link.

[0121] In the above description, the radio frame 1 includes a multi-link basic element (Multi-Link element), and the multi-link basic element includes indication information 1. For details, please refer to FIG. 4 .

[0122] Figure 4 is a schematic diagram of the structure of radio frame 1 according to an embodiment of the present application. As shown in Figure 4(a), radio frame 1 includes: an element ID field, a length field, an element ID extension field, a multi-link control field, a common information field, and a link information field. The multi-link control field includes a type field and a presence bitmap field. The presence bitmap fields include: link information present field, basic service set (BSS) parameter change count present field, medium synchronization delay information present field, enhanced multiple link capabilities (EML capabilities present field), MLD capabilities and operation present field, AP MLD ID present field, extended MLD capabilities and operation present field, and cross link UL capabilities present field.The common information fields include the common information length field, the MLD MAC address field, the link ID information field, the BSS parameter change count field, the medium synchronization delay information field, the enhanced multiple link capabilities (EML capabilities) field, the MLD capabilities and operation field, the AP MLD ID field, the extended MLD capabilities and operation field, and the cross link UL capabilities field. The cross link UL capabilities field includes the cross link UL support field, the response protection delay field, and the cross link UL transition timeout field. For descriptions of other fields, please refer to existing standards and are not detailed here.

[0123] When the value of the Cross-Link Uplink Capability field is 1, it indicates that the Cross-Link Uplink Capability field exists. When the value of the Cross-Link Uplink Capability field is 0, it indicates that the Cross-Link Uplink Capability field does not exist. The Cross-Link Uplink Support field in the Cross-Link Uplink Capability field is used to indicate whether multi-link device A supports the cross-link uplink capability. A value of 1 indicates that multi-link device A supports the cross-link uplink capability. A value of 0 indicates that multi-link device A does not support the cross-link uplink capability.

[0124] The value of the Cross-Link Uplink Support field is 1. The Response Protection Delay field indicates the minimum duration between the moment a data frame sent by multi-link device B is received on link 1 and the moment a block acknowledgment (BA) frame is replied on link 2. For its values ​​and meanings, see Table 1. In Table 1, a time unit (TU) is 1024 μs.

[0125] Table 1

[0126] As shown in Table 1, different response protection delay domain values ​​correspond to different response protection delay durations. For example, when the response protection delay domain value is 0, it corresponds to 0; when the response protection delay domain value is 1, it corresponds to 32μs; when the response protection delay domain value is 2, it corresponds to 64μ; when the response protection delay domain value is 3, it corresponds to 128μs; when the response protection delay domain value is 4, it corresponds to 256μs; when the response protection delay domain value is 5, it corresponds to 512μs, and so on. The content shown in Table 1 is for illustrative purposes only and is not intended to be a final definition.

[0127] The Cross-link Uplink Switch Timeout field is used to indicate the timeout period of the Cross-link Uplink Mode Notification frame. For its value and meaning, see Table 2.

[0128] Table 2

[0129] As shown in Table 2, different cross-link uplink handover timeout domain values ​​correspond to different timeout durations. For example, when the cross-link uplink handover timeout domain value is 0, it corresponds to 0; when the cross-link uplink handover timeout domain value is 1, it corresponds to 128μs; when the cross-link uplink handover timeout domain value is 2, it corresponds to 256μs; when the cross-link uplink handover timeout domain value is 3, it corresponds to 512μs, and so on. The content shown in Table 2 is for illustrative purposes only and is not intended to be a final limitation.

[0130] As shown in Figure 4(b), radio frame 1 includes an element identifier field, a length field, an element identifier extension field, a multilink control field, a common information field, and a link information field. The multilink control field includes a type field and a presence bitmap field. The presence bitmap field includes a link information presence indication field, a basic service set parameter change count presence field, a media synchronization delay information presence field, an EML capability presence field, an MLD capability and operation presence field, an AP MLD identifier presence field, and an extended MLD capability and operation field. The common information field includes a common information length field, an MLD media access control (MAC) address field, a link identifier information field, a BSS parameter change count field, a media synchronization delay information field, an EML capability field, an MLD capability and operation presence field, an AP MLD identifier field, and an extended MLD capability and operation field. The extended MLD capability and operation field includes a cross-link uplink support (UL) support field, a response protection delay field, a cross-link uplink handover timeout handover delay field, and an operation parameter update support field. For descriptions of other domains, please refer to existing standards and will not be described in detail here.

[0131] Specifically, the presence bitmap contains a one-bit Extended Multi-Link Capability and Operation Presence field. A value of 1 indicates the presence of the Extended Multi-Link Capability and Operation field, and a value of 0 indicates its absence. The Extended Multi-Link Capability and Operation field can be supplemented with the Cross-Link Uplink Support field, the Response Protection Delay field, and the Cross-Link Uplink Handover Timeout field. The Response Protection Delay field and the Cross-Link Uplink Handover Timeout field are effective only when the Cross-Link Uplink Support field is set to 1.

[0132] As can be seen from Figure 4 , Figure 4 (a) and Figure 4 (b) respectively illustrate the structures of two types of wireless frames 1. The above contents are only understood as examples and are not intended to be a final limitation.

[0133] In the embodiment of the present application, wireless frame 1 does not necessarily need to carry the response protection delay field and the cross-link uplink switching timeout field. For example, the value of the response protection delay field and the value of the cross-link uplink switching timeout field can be specified; for example, if the cache data of the two links is shared, the value of the response protection delay field can be 0; for example, when the mode is switched, it is necessary to wait for the AP MLD to send a response frame, and there is no need to carry the cross-link uplink switching timeout field; for another example, the cross-link uplink operation mode notification frame can carry the response protection delay field and the cross-link uplink switching timeout field. For a description of the cross-link uplink operation mode notification frame, please refer to the following.

[0134] To sum up, by carrying indication information for indicating that a multi-link device has cross-link uplink capability in a wireless frame, the present application supports interaction between multi-link devices to ensure that the multi-link device supports cross-link uplink capability, thereby supporting cross-link uplink communication between multi-link devices. Furthermore, it can support more efficient uplink and downlink service transmission between multi-link devices on high-frequency links.

[0135] In one possible implementation, method 300 may further include:

[0136] S340 : Multi-link device B sends wireless frame 2 to multi-link device A. Wireless frame 2 is used to respond to wireless frame 1.

[0137] Correspondingly, multi-link device A receives wireless frame 2 .

[0138] It should be noted that when radio frame 1 is a probe request frame, radio frame 2 is a probe response frame. When radio frame 1 is an association request frame, radio frame 2 is an association response frame. When radio frame 1 is a beacon frame, multi-link device B does not need to send radio frame 2 to multi-link device A.

[0139] Through the above technical solution, multi-link device A determines that multi-link device B has obtained the cross-link uplink capability supported by multi-link device A. In this way, full interaction between multi-link devices regarding the cross-link uplink capability supported by multi-link devices can be completed.

[0140] In method 300, the present embodiment describes how multi-link device A and multi-link device B communicate to each other about multi-link device A's support for cross-link uplink capabilities. After multi-link device A and multi-link device B complete the communication to confirm multi-link device A's support for cross-link uplink capabilities, multi-link device A and multi-link device B still need to communicate whether to enable multi-link device A's cross-link uplink capabilities. For details, see Figures 5 to 7. The following description uses the example of multi-link device A acting as a STA MLD and multi-link device B acting as an AP MLD.

[0141] It should be noted that the following content is described using link 1 enabling cross-link uplink capability as an example, but is not limited to this.

[0142] FIG5 is an interactive flow chart of a multi-link communication method 500 according to an embodiment of the present application. The method 500 includes:

[0143] S510 : The STA MLD sends a radio frame 3 (eg, a second radio frame) to the AP MLD. The radio frame 3 is used to indicate whether the link 1 enables the cross-link uplink capability.

[0144] Accordingly, the AP MLD receives the wireless frame 3.

[0145] S520 : The AP MLD sends an acknowledgment frame 1 (eg, a first acknowledgment frame) to the STA MLD. The acknowledgment frame 1 is used to acknowledge receipt of the wireless frame 3 .

[0146] Accordingly, the STA MLD receives the confirmation frame 1 and determines, based on the confirmation frame 1 , that the AP MLD has received the radio frame 3 .

[0147] It should be noted that radio frame 3 is used to indicate whether link 1 enables the cross-link uplink capability, which is only a general reference. That is, radio frame 3 can also be used to indicate whether other links enable the cross-link uplink capability, and this is not limited.

[0148] Specifically, radio frame 3 may be the aforementioned cross-link uplink operation mode notification frame, which is used to enable / disable (or to indicate whether to enable) the cross-link uplink capability of link 1. For example, when the cross-link uplink capability of link 1 is in the enabled state, STA MLD may indicate through radio frame 3 that the cross-link uplink capability of link 1 is disabled; when the cross-link uplink capability of link 1 is in the disabled state, STA MLD may indicate through radio frame 3 that the cross-link uplink capability of link 1 is enabled. STA MLD may also indicate through radio frame 3 whether to change the cross-link uplink capability parameters of link 1, for example, to change the value of the response protection delay field or the value of the cross-link uplink switching timeout field.

[0149] When the STA MLD decides to switch the cross-link uplink capability enable mode (i.e., switching from cross-link uplink capability disabled to cross-link uplink capability enabled, or switching from cross-link uplink capability enabled to cross-link uplink capability disabled) or modifies the cross-link uplink capability parameters, STA1 belonging to the STA MLD can send radio frame 3 to AP1 associated with the AP MLD after successfully competing for the channel. The structure of radio frame 3 can be seen in Figure 6.

[0150] FIG6 is a schematic diagram of the structure of radio frame 3 according to an embodiment of the present application. As shown in FIG6 , radio frame 3 includes at least a category field, a protected extreme high throughput action field, a dialog token field, and a cross link uplink control field. The cross link uplink control field includes a cross link uplink mode field, a response protection delay field, and a cross link uplink protected link bitmap field.

[0151] Specifically, a value of 1 in the cross-link uplink mode domain indicates that STA MLD enables the cross-link uplink function, and a value of 0 indicates that STA MLD does not enable the cross-link uplink function. If the response protection delay of STA MLD does not change, it is necessary to fill in a value that is exactly the same as the value of the latest update. The cross-link uplink protection link bitmap domain is a link bitmap. The link corresponding to the position with a value of 1 is the protection link (that is, the uplink transmission coverage of the link is insufficient, and the BA frame required to reply to the downlink data of the link needs to be transmitted on other non-protected links). Links other than the protection link are called non-protected links. If at least one link is a protection link, the value of the cross-link uplink mode domain is 1; if all links are not protection links, the value of the cross-link uplink mode domain is 0. Among them, the embodiment of the present application does not limit the length of the cross-link uplink protection link bitmap domain. For example, it can be 16 bits or 8 bits.

[0152] If the unprotected link is flexible, an uplink field is added to indicate which unprotected link the uplink confirmation frame uses. If multiple uplink confirmation frames are available, multiple uplink fields or bitmaps can be used to indicate the unprotected link used by the uplink confirmation frame. For example, if the protected link is a link in the 60 GHz frequency band, the unprotected link can be a link in the 5 GHz frequency band.

[0153] In method 500, the time interval between the effective time of whether link 1 enables the cross-link uplink capability and the moment when the sending of confirmation frame 1 is completed is greater than or equal to the delay corresponding to the value of the aforementioned cross-link uplink switching timeout domain. The delay corresponding to the value of the aforementioned cross-link uplink switching timeout domain can also be referred to as the first delay.

[0154] In one possible implementation, when STA MLD enables the cross-link uplink capability of link 1 through radio frame 3, the cross-link uplink capability of link 1 will be enabled after the first delay. When STA MLD does not enable the cross-link uplink capability of link 1 through radio frame 3, the cross-link uplink capability of link 1 will be shut down after the first delay. In summary, the effective time of whether the cross-link uplink capability of link 1 of STA MLD is enabled is after the first delay (which may also include the first delay). The first delay may be predefined or carried in indication information 1.

[0155] In one possible implementation, when STA MLD enables the cross-link uplink capability of link 1 through radio frame 3, the cross-link uplink capability of link 1 will be enabled after the transmission of confirmation frame 1 is completed. When STA MLD does not enable the cross-link uplink capability of link 1 through radio frame 3, the cross-link uplink capability of link 1 will be disabled after the transmission of confirmation frame 1 is completed. In summary, the time when the cross-link uplink capability of link 1 is enabled takes effect after the transmission of confirmation frame 1 is completed.

[0156] Through the above solution, STA MLD and AP MLD can complete the interaction of whether to enable the cross-link uplink capability of link 1, thereby supporting cross-link uplink communication between multi-link devices. In this way, it can support more efficient uplink and downlink service transmission between multi-link devices on high-frequency links.

[0157] It should be noted that the above content is described using link 1 as an example to enable cross-link uplink capability, that is, the uplink coverage capability of link 1 is weak, and the STA MLD can send BA frames corresponding to downlink data frames transmitted on link 1 to the AP MLD through other links (taking link 2 as an example).

[0158] FIG7 is an interactive flow chart of a multi-link communication method 700 according to an embodiment of the present application. The method 700 includes:

[0159] S710 : The STA MLD sends a radio frame 3 to the AP MLD. The radio frame 3 is used to indicate whether the link 1 enables the cross-link uplink capability.

[0160] Accordingly, the AP MLD receives the wireless frame 3.

[0161] For detailed description, please refer to S510 and will not be repeated here.

[0162] S720 : The AP MLD sends an acknowledgment frame 1 to the STA MLD. The acknowledgment frame 1 is used to acknowledge receipt of the wireless frame 3 .

[0163] Accordingly, the STA MLD receives the confirmation frame 1 and determines, based on the confirmation frame 1 , that the AP MLD has received the radio frame 3 .

[0164] Specifically, after receiving the wireless frame 3 , the AP MLD waits for a short inter-frame space (SIFS) (not shown in FIG. 7 ) to reply with the confirmation frame 2 .

[0165] S730 : The AP MLD sends a radio frame 4 (eg, a third radio frame) to the STA MLD. The radio frame 4 indicates whether the link 1 enables the cross-link uplink capability.

[0166] Correspondingly, STA MLD receives radio frame 4.

[0167] Within the first delay after the AP MLD responds to the confirmation frame 2, it sends the radio frame 4 to the STA MLD in unicast address mode. The content of the cross-link uplink control field in the radio frame 4 is consistent with the content of the cross-link uplink control field in the radio frame 3.

[0168] S740 : The STA MLD sends an acknowledgment frame 2 (eg, a second acknowledgment frame) to the AP MLD. The acknowledgment frame 2 is used to acknowledge receipt of the wireless frame 4 .

[0169] Specifically, after receiving the wireless frame 4 sent by the AP MLD, the STA MLD waits for a SIFS period to reply with an acknowledgment frame 2.

[0170] Through the above process, the time when the cross-link uplink capability of link 1 is enabled is after the transmission of confirmation frame 2 is completed.

[0171] Through the above solution, the STA MLD and AP MLD can complete the interaction on whether to enable the cross-link uplink capability of link 1, thereby supporting cross-link uplink communication between multi-link devices. In this way, the multi-link devices can complete the interaction on whether to enable the cross-link uplink capability of the multi-link devices.

[0172] In methods 500 to 700, the STA MLD and the AP MLD interact to determine whether to enable the cross-link uplink capability of link 1. The STA MLD and the AP MLD may interact to determine whether to enable the cross-link uplink capability of link 1 through any link, and this is not limited.

[0173] It should be noted that method 700 may be a further technical solution of method 500, that is, S710 may be S510, and S720 may be S520.

[0174] After the STA MLD and the AP MLD complete interaction to enable the cross-link uplink capability of link 1, the STA MLD and the AP MLD can perform cross-link user data service transmission and cross-link control data service transmission. For details, see Figures 8 to 12.

[0175] FIG8 is a schematic diagram of an interaction flow of a multi-link communication method 800 according to an embodiment of the present application. The method 800 includes:

[0176] S810 : AP MLD sends data frame 1 to STA MLD through link 1 .

[0177] Correspondingly, STA MLD receives data frame 1 through link 1.

[0178] S820 : AP MLD sends request frame 1 to STA MLD through link 2 .

[0179] Correspondingly, STA MLD receives request frame 1 through link 2. Request frame 1 is used to request sending confirmation frame 3 (such as the third confirmation frame), and confirmation frame 3 is used to confirm receiving data frame 1.

[0180] Specifically, the request frame 1 may be a block acknowledgement request (BA request, BAR) frame or an acknowledgement request frame. When the request frame 1 is a BAR frame, the acknowledgement frame 3 may be a BA frame; when the request frame 1 is an acknowledgement request frame, the acknowledgement frame 3 may be an ACK frame, which is not limited to this.

[0181] S830 : STA MLD sends confirmation frame 3 to AP MLD through link 2 .

[0182] In response, AP MLD receives confirmation frame 3 via link 2.

[0183] Specifically, if the cross-link uplink capability of the STA MLD is enabled (that is, the cross-link uplink mode field is set to 1), the regulations for downlink transmission are as follows:

[0184] AP MLD can send data frame 1 on any protection link (take link 1 as an example) to the device belonging to STA MLD working on the link. The transmission end time (or reception completion time) of data frame 1 is recorded as t DL .

[0185] After sending data frame 1 on any protection link, AP MLD sends request frame 1 on a non-protection link (for example, link 2) to explicitly request the device affiliated with STA MLD working on the non-protection link to reply with acknowledgment frame 3. The start time (or start time) of sending acknowledgment frame 3 is t3.

[0186] t 3- t DL ≥t pro . t pro Indicates the response protection delay time (can also be the second delay, corresponding to the value of the response protection delay domain mentioned above). 3- t DL <t proThis means that the AP MLD cannot determine whether the media access control protocol data unit (MAC protocol data unit, MPDU) with the corresponding bit set to 0 in the confirmation frame 3 fed back before the second delay is received incorrectly or the cross-link information is not transferred in time.

[0187] Specifically, when link 1 enables the cross-link uplink capability, through the above technical solution, the STA MLD and the AP MLD can transmit downlink data services on the high-frequency link, and transmit uplink feedback services on the low-frequency link. This can fully utilize the large bandwidth capability of the high-frequency band and make downlink data transmission more reliable.

[0188] Through the above solution, user data can be transmitted across links between the STA MLD and the AP MLD.

[0189] FIG9 is a schematic diagram of an interaction flow of a multi-link communication method 900 according to an embodiment of the present application. The method 900 includes:

[0190] S910 : AP MLD sends NDPA frame 1 to STA MLD through link 1 .

[0191] Correspondingly, STA MLD receives NDPA frame 1 through link 1.

[0192] Specifically, NDPA frame 1 is used to specify the multi-link device (for example, the STA MLD mentioned above) participating in this channel sounding and related parameters. The STA MLD participating in this channel sounding measures NDP frame 1 and obtains the measurement results.

[0193] S920 : AP MLD sends NDP frame 1 to STA MLD through link 1 .

[0194] Accordingly, STA MLD receives NDP frame 1 through link 1.

[0195] Optionally, in S930 , the AP MLD sends the BFRP frame 1 to the STA MLD through the link 2 .

[0196] Accordingly, the STA MLD receives BFRP frame 1 through link 2 and determines to report BFR frame 1 to the AP MLD based on BFRP frame 1. BFR frame 1 includes channel information of link 1, which is obtained by the STA MLD based on NDP frame 1. The channel information of link 1 may include channel state information (CSI) of link 1, etc.

[0197] S940 : STA MLD sends BFR frame 1 to AP MLD through link 2 .

[0198] Accordingly, AP MLD receives BFR frame 1 through link 2.

[0199] In the above scheme, the STA MLD and AP MLD exchange NDPA frame 1 and NDP frame 1 over link 1, and the AP MLD and STA MLD exchange BFRP frame 1 (optional) and BFR frame 1 over link 2. Accordingly, link 1 is the aforementioned protection link. Specifically, the STA MLD and AP MLD can instruct the STA MLD to report BFR frame 1 over link 2 via NDPA frame 1.

[0200] As a possible implementation, the embodiment of the present application supports modification of NDPA frame 1, see Figure 10 for details.

[0201] Figure 10 is a schematic diagram of the structure of the NDPA frame 1 of an embodiment of the present application. As shown in (a) of Figure 10, the NDPA frame 1 includes: a frame control field, a duration field, a receive address (RA), a transmit address (TA) field, a sounding dialog token field, a station information (STA information) field, and a frame check sequence (FCS) field. Among them, the station information field includes: an 11-bit association identifier (AID 11) field, a partial bandwidth information field, a cross link indication field, a column number (N) field, and a 11-bit association identifier (AID 11) field. c index) field, feedback type and Ng (feedback type and Ng) field, disambiguation field and codebook size field, etc.

[0202] In the structure shown in (a) of Figure 10, a cross link indication field (which can be called indication information 3 (such as second indication information)) is newly added to the site information field. When the value of this field is 1, it indicates that the STA MLD feeds back BFR frame 1 on other links, and the STA MLD needs to select a non-uplink protection link (taking link 2 as an example) to reply to BFR frame 1. When the value of this field is 0, it indicates that the STA MLD replies to the BFR frame on the current link (taking link 1 as an example). The cross link indication field can include one bit, but is not limited to this.

[0203] The structure shown in (b) of Figure 10 is similar to the structure shown in (a) of Figure 10, except that the site information field in the NDPA frame 1 shown in (b) of Figure 10 includes a cross link ID field, and the link corresponding to the value of the cross link ID field is the link to which the STA MLD needs to report the BFR frame 1. This application supports the provision that when the cross link ID field has a value of 15, it indicates that the STA MLD replies to the BFR frame 1 on this link.

[0204] As can be seen from the description of Figure 10, NDPA frame 1 includes a detection dialogue token field, which is used to identify the channel detection process of link 1. The present application supports that the value of the detection dialogue token field in NDPA frame 1 can uniquely correspond to link 1. For example, the value of the detection dialogue token field is 0-10 corresponding to link 1, and the value is 11-20 corresponding to link 2. Then, it can be stipulated that when the value of the detection dialogue token field in NDPA1 is 0-10, the detection dialogue token value in NDPA frame 1 can uniquely correspond to link 1, and it can also correspond to other links if it cannot. Accordingly, when STA MLD determines that it cannot feedback BFR frame 1 on link 1, STA MLD can feedback BFR frame 1 on link 2, and the BFR frame 1 includes the detection dialogue token value included in NDPA frame 1. Accordingly, AP MLD determines that the BFR frame 1 reported by STA MLD through link 2 corresponds to NDPA frame 1. In this way, minor changes can be made to NDPA frame 1 and BRF frame 1.

[0205] It should be noted that when the detection dialogue token in NDPA frame 1 is changed, the embodiment of the present application supports AP MLD not sending BFRP frame 1 to STA MLD. When AP MLD sends BFRP frame 1 to STA MLD, the embodiment of the present application supports AP MLD sending BFRP frame 1 to STA MLD through link 2.

[0206] Specifically, when link 1 enables the cross-link uplink capability, the AP MLD and the STA MLD can better complete the channel detection task through the above technical solution.

[0207] As can be seen from Figure 10, Figure 10 (a) and Figure 10 (b) respectively illustrate the structures of two types of NDPA frames 1. The above content is only understood as an example and is not intended to be a final limitation.

[0208] FIG11 is a schematic diagram of an interaction flow of a multi-link communication method 1100 according to an embodiment of the present application. The method 1100 includes:

[0209] S1110 : AP MLD sends NDPA frame 2 to STA MLD through link 1 .

[0210] Correspondingly, STA MLD receives NDPA frame 2 through link 1.

[0211] S1120 : AP MLD sends NDP frame 2 to STA MLD through link 1 .

[0212] Correspondingly, STA MLD receives NDP frame 2 through link 1.

[0213] Specifically, the description of NDPA frame 2 and NDP frame 2 can be found in the previous text and will not be repeated here.

[0214] S1130 : AP MLD sends BFRP frame 2 to STA MLD through link 2 . BFRP frame 2 is used to instruct STA MLD to send BFR frame 2 on link 2 . BFR frame 2 includes channel information of link 1 . The channel information of link 1 is obtained by STA MLD based on NDP frame 2 .

[0215] Accordingly, STA MLD receives BFRP frame 2 through link 2 and determines to report BFR frame 2 to AP MLD based on BFRP frame 2. For the description of BFR frame 2, refer to the description of BFR frame 1 and will not be repeated here.

[0216] Specifically, this application supports modification of BFRP frame 2, as shown in FIG12 .

[0217] Figure 12 is a schematic diagram of the structure of BFRP frame 2 according to an embodiment of the present application. As shown in (a) of Figure 12, BFRP frame 2 includes: a frame control field, a duration field, a receiving address field, a sending address field, a common information field, a user information list field, a padding field, and a frame detection sequence field. The common information field includes: a trigger frame type field, a link ID present field, and a trigger dependet common information field. The common information field based on the trigger frame type includes a link ID information field. When the link ID present field is set to 1, it indicates that the common information field based on the trigger frame type includes a link ID information field.

[0218] As shown in Figure 12(b), BFRP frame 2 includes: a frame control field, a duration field, a receiving address field, a transmitting address field, a common information field, a user information list field, a padding field, and a frame detection sequence field. The user information list field includes: multiple user information fields. The user information field includes: a 12-bit association identifier (AID12) field, a link identifier existence field, and a trigger frame type-based user information (trigger dependet user information) field. The trigger frame type-based user information field includes a link identifier information field. When the link identifier existence field is set to 1, it indicates that the trigger frame type-based user information field includes a link identifier information field.

[0219] As shown in (c) of FIG12 , BFRP frame 2 includes: a frame control field, a duration field, a receiving address field, a sending address field, a public information field, a user information list field, a padding field, and a frame detection sequence field. The common information fields include: trigger frame type field (which can take a value not currently taken, such as 9), length field, cascade indication field, carrier sense reequired field, bandwidth field, guard interval long training field (GI+LTF) field, multiple user multip input-muptip output LTF mode field, high efficiency (HE)-LTF symbol number field, low density parity check (LDPC) extra symbol segment field, AP TX power field, packet extension field, spatial reuse field, Doppler field, and HE SIG-A reserved field. The user information list field includes: AID association identifier (AID 12) field, resource unit allocation field, coding type field, modulation and coding scheme (MCS) field, dual carrier modulation (DCM) field, spatial stream allocation field, target received signal strength indicator (RSSI) (target RSSI) field, and user information field based on trigger frame type. The user information field based on trigger frame type includes link information identifier field and feedback segment retransmission bitmap field.

[0220] As shown in (d) of Figure 12, BFRP frame 2 includes: AID12 association identifier (AID 12) field, physical layer version identifier (PHY version identifier) ​​field, uplink bandwidth extension (UL bandwidth extension) field, extreme high throughput (EHT) spatial reuse 1 (EHT spatial reuse 1) field, EHT spatial reuse 2 (EHT spatial reuse 2) field, U-SIG disregard and validate field, link identification information presence field, and user information field based on trigger frame type. Among them, the user information field based on trigger frame type includes a link identification information field.

[0221] In Figures 12(a) through 12(d), the BFR frame 2 sent by the STA MLD on link 2 corresponds to the link (using link 1 as an example) corresponding to the value of the link identification information field. The link identification information field instructs the STA MLD to send the BFR frame 2 on link 2.

[0222] As can be seen from Figure 12, Figure 12 (a), Figure 12 (b), Figure 12 (c), and Figure 12 (d) respectively illustrate the structures of four types of BFRP frames 2. The above contents are only to be understood as examples and are not to be construed as final limitations.

[0223] It should also be noted that the frame structures shown in (a) to (d) of FIG. 12 are only understood as examples, and the embodiments of the present application support making corresponding modifications based on the above-mentioned structure to achieve the same purpose.

[0224] S1140 : STA MLD sends BFR frame 2 to AP MLD through link 2 .

[0225] Accordingly, AP MLD receives BFR frame 2 through link 2.

[0226] In the above solution, the AP MLD and STA MLD exchange NDPA frame 2 and NDP frame 2 through link 1, and the AP MLD and STA MLD exchange BFRP frame 2 and BFR frame 2 through link 2. In this way, cross-link control data transmission can be implemented between multi-link devices.

[0227] It should be noted that BFRP frame 2 can be used to instruct the STA MLD to send BFR frame 2 corresponding to link 1 on link 2. The present application supports achieving the above purpose by changing the structure of BFRP frame 2; alternatively, the present application also supports adding indication information 4 to BFRP frame 2, where indication information 4 is used to instruct the STA MLD to send BFR frame 2 corresponding to link 1 on link 2. In summary, BFRP frame 2 is used to instruct the STA MLD to send BFR frame 2 on link 2.

[0228] The present application also provides a multi-link communication method, which can be used to provide channel protection for data transmission between multi-link device A and multi-link device B. For details, see Figure 13. The following description takes multi-link device A as a STA MLD and multi-link device B as an AP MLD as an example.

[0229] Figure 13 is a schematic diagram of the interaction process of clear to send (CTS) and request to send (RTS) between multi-link devices in an embodiment of the present application. It should be noted that the AP MLD and STA MLD can use the aforementioned method to exchange link 1 to enable cross-link uplink capabilities. In this way, the AP MLD and STA MLD exchange RTS / CTS on link 1. See below for details.

[0230] As shown in (a) of Figure 13, when link 1 enables cross-link uplink capability, AP MLD interacts with STA MLD on RTS1 / CTS1 on link 1. The present application supports the assumption that AP MLD can receive CTS1 normally. For example, when AP MLD sends RTS1 to STA MLD via link 1, it starts a timer with a timing duration of 2SIFS+t CTS1 Among them, t CTS1 The transmission duration of CTS1. After this timing duration expires, the AP MLD sends Data Frame 2 to the STA MLD via Link 1. It also sends BAR Frame 2 via Link 2 and receives BA Frame 2, confirming receipt of Data Frame 2, via Link 2. This ensures channel protection for data transmission.

[0231] As shown in Figure 13(b), when link 1 enables cross-link uplink capability, the AP MLD and STA MLD exchange RTS / CTS on link 1. For example, link 1 includes STA1 and STA2. STA1 does not enable or cannot support cross-link uplink capability (i.e., uplink information sent by STA1 on link 1 can be received by the AP MLD), and STA2 enables cross-link uplink capability (i.e., uplink information sent by STA1 on link 1 cannot be received by the AP MLD). The AP MLD can exchange RTS1 / CTS1 with STA1 on link 1. For example, the AP MLD sends RTS1 to STA1 on link 1, and STA1 sends CTS1 to the AP MLD on link 1. Furthermore, the AP MLD sends data frame 2 to STA2 on link 1, and receives BA frame 2 on link 2. In this way, channel protection for data transmission can be achieved.

[0232] As shown in (c) of Figure 13, when link 1 enables cross-link uplink capability, AP MLD and STA MLD perform MU-RTS / CTS interaction on link 1. Exemplarily, AP MLD sends multiple user RTS1 (MU-RTS1) to STA MLD via link 1, which is used to instruct multiple STAs on link 1 (at least one of the multiple STAs does not enable or does not support cross-link uplink capability) to reply to CTS1 at the same time. Exemplarily, AP MLD sends MU-RTS1 via link 1, and STA MLD replies to CTS1 via link 1. Further, AP MLD sends data frame 2 to STA MLD via link 1, AP MLD sends BAR frame 2 via link 2, and AP MLD receives BA frame 2 via link 2. In this way, channel protection for data transmission can be achieved.

[0233] In one possible implementation, the present invention supports disabling the RTS / CTS exchange between the STA MLD and the AP MLD on the protection link. Alternatively, the AP MLD sends a CTS-to-Self frame, thereby also protecting the data transmission channel.

[0234] Through the above content, the embodiment of the present application describes how to provide protection for data transmission between multi-link device A and multi-link device B.

[0235] The above describes the method embodiment of the embodiment of the present application, and the corresponding device embodiment is introduced below.

[0236] Figure 14 is a schematic block diagram of a communication device 1400 according to an embodiment of the present application. Communication device 1400 includes a processor 1401, a memory 1402 (optional), and a communication interface 1403. Processor 1401, memory 1402, and communication interface 1403 are interconnected via a bus 1404. Communication device 1400 can be either multi-link device A or multi-link device B.

[0237] Specifically, the memory 1402 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (CD-ROM), and the memory 1402 is used for related instructions and data.

[0238] The processor 1401 may be one or more central processing units (CPUs). When the processor 1401 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0239] Exemplarily, when the communication apparatus 1400 is a multi-link device A, the processor 1401 is configured to read the program code stored in the memory 1402 and perform the following operations: determining a radio frame 1, where the radio frame 1 includes indication information 1; and sending the radio frame 1.

[0240] Exemplarily, when the communication apparatus 1400 is a multi-link device B, the processor 1401 is configured to read the program code stored in the memory 1402 and perform the following operations: receiving a radio frame 1 from a multi-link device A, the radio frame 1 including indication information 1; and determining, based on the indication information 1, whether the multi-link device A supports cross-link capability.

[0241] It should be noted that the implementation of each operation in FIG14 may also correspond to the corresponding description of the method embodiments shown in FIG3 to FIG13 .

[0242] Figure 15 is a schematic block diagram of a communication device 1500 according to an embodiment of the present application. Communication device 1500 is applicable to multi-link device A or device B, and can be used to implement the methods described in the above method embodiments. Communication device 1500 includes a transceiver unit 1501 and a processing unit 1502. Transceiver unit 1501 and processing unit 1502 are described below.

[0243] Exemplarily, when the communication apparatus 1500 is a multi-link device A, the processing unit 1502 is configured to determine a radio frame 1, where the radio frame 1 includes indication information 1; and the transceiver unit 1501 is configured to send the radio frame 1 to the multi-link device B.

[0244] Exemplarily, when the communication apparatus 1500 is a multi-link device B, the transceiver unit 1501 is configured to receive a radio frame 1 from a multi-link device A, where the radio frame 1 includes indication information 1; and the processing unit 1502 is configured to determine, based on the indication information 1, whether the multi-link device A supports cross-link capability.

[0245] It should be noted that the implementation of each operation in FIG15 can also refer to the corresponding description of the method shown in the above embodiment, which is only understood as an example.

[0246] FIG16 is a schematic block diagram of a communication device 1600 according to an embodiment of the present application. The communication device 1600 may be an AP MLD or a chip. The communication device 1600 may be used to perform the operations performed by the AP MLD in the method embodiments shown in FIG3 to FIG13 .

[0247] When the communication device 1600 is an AP MLD, it is, for example, a base station. Figure 16 shows a simplified schematic diagram of the base station structure. The base station includes a module 1610, a module 1620, and a module 1630. Module 1610 is mainly used for baseband processing, controlling the base station, etc.; module 1610 is usually the control center of the base station, which can usually be called a processor, and is used to control the base station to perform the processing operations on the network device side in the above method embodiment. Module 1620 is mainly used to store computer program code and data. Module 1630 is mainly used for receiving and transmitting radio frequency signals and converting radio frequency signals into baseband signals; module 1630 can usually be called a transceiver module, a transceiver, a transceiver circuit, or a transceiver, etc. The transceiver module of module 1630 can also be called a transceiver or a transceiver, etc., which includes an antenna 1633 and a radio frequency circuit (not shown in Figure 16), wherein the radio frequency circuit is mainly used for radio frequency processing. Alternatively, the device for implementing the receiving function in module 1630 may be considered a receiver, and the device for implementing the transmitting function may be considered a transmitter, that is, module 1630 includes a receiver 1632 and a transmitter 1631. The receiver may also be referred to as a receiving module, a receiver, or a receiving circuit, and the transmitter may be referred to as a transmitting module, a transmitter, or a transmitting circuit.

[0248] Module 1610 and module 1620 may include one or more boards, each of which may include one or more processors and one or more memories. The processor is used to read and execute programs in the memory to implement baseband processing functions and control the base station. If multiple boards are present, the boards may be interconnected to enhance processing capabilities. As an optional implementation, multiple boards may share one or more processors, multiple boards may share one or more memories, or multiple boards may simultaneously share one or more processors.

[0249] For example, in one implementation, the transceiver module of module 1630 is configured to execute the transceiver-related processes performed by the AP MLD in the embodiments shown in Figures 3 to 13. The processor of module 1610 is configured to execute the processing-related processes performed by the AP MLD in the embodiments shown in Figures 3 to 13.

[0250] In another implementation, the processor of module 1610 is used to execute processes related to the processing performed by the communication device in the embodiments shown in Figures 3 to 13.

[0251] In another implementation, the transceiver module of module 1630 is used to execute the transceiver-related processes performed by the communication device in the embodiments shown in Figures 3 to 13.

[0252] It should be understood that FIG16 is merely an example and not a limitation, and the network device including the processor, memory, and transceiver described above may not rely on the structures shown in FIG14 to FIG15 .

[0253] When communication device 1600 is a chip, the chip includes a transceiver, memory, and a processor. The transceiver can be an input / output circuit or a communication interface; the processor can be a processor, microprocessor, or integrated circuit integrated on the chip. The network device's sending operation in the above method embodiment can be understood as the chip's output, and the network device's receiving operation in the above method embodiment can be understood as the chip's input.

[0254] Figure 17 is a schematic block diagram of a communication device 1700 according to an embodiment of the present application. The communication device 1700 may be a STA MLD, a processor of the STA MLD, or a chip. The communication device 1700 may be configured to execute the operations performed by the STA MLD or communication device in the above method embodiments.

[0255] When communication device 1700 is a STA MLD, and the STA MLD is a terminal device, Figure 10 shows a simplified schematic diagram of the terminal device structure. As shown in Figure 17, the terminal device includes a processor 1710, a memory 1720, and a transceiver 1730. The memory 1720 can store computer program code, and the transceiver 1730 includes a transmitter 1731, a receiver 1732, a radio frequency circuit (not shown in Figure 17), an antenna 1733, and input / output devices (not shown in Figure 17).

[0256] Processor 1710 is primarily used to process communication protocols and communication data, control the terminal device, execute software programs, and process software program data. Memory 1720 is primarily used to store software programs and data. The radio frequency circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. Antenna 1733 is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices. For example, touch screens, displays, keyboards, etc. are primarily used to receive user input and output data to the user. It should be noted that some types of terminal devices may not have input / output devices.

[0257] When data needs to be sent, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the RF circuit. The RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna. When data is sent to the terminal device, the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor. The processor converts the baseband signal into data and processes the data. For ease of explanation, Figure 17 shows only one memory, processor, and transceiver. In an actual terminal device product, there may be one or more processors and one or more memories. The memory may also be referred to as a storage medium or a storage device. The memory may be set independently of the processor or integrated with the processor. This is not limited in the embodiments of the present application.

[0258] In the embodiment of the present application, the antenna and radio frequency circuit with transceiver functions can be regarded as the transceiver module of the terminal device, and the processor with processing function can be regarded as the processing module of the terminal device.

[0259] As shown in Figure 17, the terminal device includes a processor 1710, a memory 1720, and a transceiver 1730. The processor 1710 may also be referred to as a processing unit, a processing board, a processing module, a processing device, etc., and the transceiver 1730 may also be referred to as a transceiver unit, a transceiver, a transceiver device, etc.

[0260] Alternatively, the device implementing the receiving function in transceiver 1730 may be considered a receiving module, and the device implementing the transmitting function in transceiver 1730 may be considered a transmitting module. That is, transceiver 1730 includes a receiver and a transmitter. A transceiver may also be sometimes referred to as a transceiver, a transceiver module, or a transceiver circuit. A receiver may also be sometimes referred to as a receiver, a receiving module, or a receiving circuit. A transmitter may also be sometimes referred to as a transmitter, a transmitting module, or a transmitting circuit.

[0261] For example, in one implementation, the processor 1710 is configured to execute the processing actions of the STA MLD in the embodiments shown in FIG. 3 to FIG. 13 , and the transceiver 1730 is configured to execute the transceiver actions of the STA MLD in FIG. 3 to FIG. 13 .

[0262] For example, in one implementation, the processor 1710 is configured to execute the processing actions of the STA MLD in the embodiments shown in FIG. 3 to FIG. 13 , and the transceiver 1730 is configured to execute the transceiver actions of the STA MLD in FIG. 3 to FIG. 13 .

[0263] It should be understood that FIG17 is merely an example and not a limitation, and the above-mentioned terminal device including the transceiver module and the processing module may not rely on the structures shown in FIG14 to FIG15.

[0264] When the communication device 1700 is a chip, the chip includes a processor, memory, and a transceiver. The transceiver can be an input / output circuit or a communication interface; the processor can be a processing module, microprocessor, or integrated circuit integrated on the chip. The sending operation of the terminal device in the above method embodiment can be understood as the chip's output, and the receiving operation of the terminal device in the above method embodiment can be understood as the chip's input.

[0265] An embodiment of the present application also provides a chip, including a processor, for calling and executing instructions stored in a memory, so that a communication device equipped with the chip executes the methods in the above examples.

[0266] An embodiment of the present application also provides another chip, including: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the methods in the above examples.

[0267] An embodiment of the present application further provides a processor, which is coupled to a memory and configured to execute the methods and functions involving a satellite or user equipment in any of the above embodiments.

[0268] In another embodiment of the present application, a computer program product is provided. When the computer program product is run on a computer, the method of the above embodiment is implemented.

[0269] In another embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program. When the computer program is executed by a computer, the method described in the above embodiment is implemented.

[0270] In the description of the embodiments of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit them to be different. At the same time, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions.

[0271] Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0272] In the description of the embodiments of the present application, unless otherwise specified, " / " indicates that the objects associated before and after are in an "or" relationship, for example, A / B can represent A or B; "and / or" in the present application is merely a description of the association relationship of associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.

[0273] It should be understood that reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention.

[0274] Therefore, the phrases "in one embodiment" or "in an embodiment" appearing throughout this specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the various embodiments of the present invention, the sequence numbers of the aforementioned processes do not necessarily indicate a specific order of execution. The order of execution of the processes is determined by their functionality and inherent logic and does not constitute any limitation on the implementation of the embodiments of the present invention.

[0275] It will be understood that reference to "embodiment" throughout this specification means that a particular feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present application.

[0276] Therefore, the various embodiments throughout this specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It is understood that in the various embodiments of the present application, the size of the sequence number of each process 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.

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

[0278] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.

[0279] On the other hand, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, which may be electrical, mechanical or other forms.

[0280] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment. In addition, the functional units in the various embodiments of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0281] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other media that can store program codes.

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

Claims

1. A multi-link communication method, characterized in that: include: A first multi-link device generates a first radio frame, the first radio frame includes first indication information, the first indication information is used to indicate that the first multi-link device supports cross-link capability, the cross-link capability is the ability of the first multi-link device to confirm, on a second link, service transmission between the first multi-link device and a second multi-link device on a first link; The first multi-link device sends the first radio frame to the second multi-link device.

2. The method according to claim 1, characterized in that The method further comprises: The first multi-link device sends a second radio frame to the second multi-link device, where the second radio frame is used to indicate whether the first link enables the cross-link capability; The first multi-link device receives a first confirmation frame sent by the second multi-link device, where the first confirmation frame is used to confirm receipt of the second radio frame.

3. The method according to claim 2, characterized in that The method further comprises: The first multi-link device receives a third radio frame sent by the second multi-link device, where the third radio frame is used to indicate whether the first link enables the cross-link capability; The first multi-link device sends a second confirmation frame to the second multi-link device, where the second confirmation frame is used to confirm receipt of the third radio frame.

4. The method according to claim 2 or 3, characterized in that: The second radio frame is used to indicate that the first link enables the cross-link capability, and the method further includes: The first multi-link device receives a data frame sent by the second multi-link device through the first link; The first multi-link device receives a request frame sent by the second multi-link device through the second link, wherein the request frame is used to request the first multi-link device to send a third confirmation frame on the second link, and the third confirmation frame is used to confirm reception of the data frame; The first multi-link device sends the third confirmation frame to the second multi-link device through the second link.

5. The method according to claim 2 or 3, characterized in that: The second radio frame is used to indicate that the first link enables the cross-link capability, and the method further includes: The first multi-link device receives, through the first link, a null data physical layer protocol data unit declaration NDPA frame sent by the second multi-link device, the NDPA frame including second indication information, the second indication information being used to instruct the first multi-link device to send a beam training report BFR frame on a non-first link, the BFR frame including channel information of the first link, the channel information of the first link being obtained by the first multi-link device based on a null data physical layer protocol data unit NDP frame; The first multi-link device receives the NDP frame sent by the second multi-link device through the first link; The first multi-link device sends the BFR frame to the second multi-link device through the second link.

6. The method according to claim 2 or 3, characterized in that: The second radio frame is used to indicate that the first link enables the cross-link capability, and the method further includes: The first multi-link device receives, through the first link, a null data physical layer protocol data unit declaration NDPA frame sent by the second multi-link device, the NDPA frame including identification information of the second link, the identification information of the second link being used to instruct the first multi-link device to send a beam training report BFR frame on the second link, the BFR frame including channel information of the first link, the channel information of the first link being obtained by the first multi-link device based on a null data physical layer protocol data unit NDP frame; The first multi-link device receives the NDP frame sent by the second multi-link device through the first link; The first multi-link device sends the BFR frame to the second multi-link device through the second link.

7. The method according to claim 2 or 3, characterized in that: The second radio frame is used to indicate that the first link enables the cross-link capability, and the method further includes: The first multi-link device receives, through the first link, a null data physical layer protocol data unit declaration NDPA frame sent by the second multi-link device; The first multi-link device receives, through the first link, a null data physical layer protocol data unit (NDP) frame sent by the second multi-link device; The first multi-link device receives a beam training report inquiry triggering BFRP frame sent by the second multi-link device through the second link, wherein the BFRP frame is used to instruct the first multi-link device to send a beam training report BFR frame on the second link. including channel information of the first link, where the channel information of the first link is obtained by the first multi-link device based on the NDP frame; The first multi-link device sends the BFR frame to the second multi-link device through the second link.

8. The method according to claim 7, characterized in that The BFRP frame includes identification information of the first link, where the identification information of the first link is used to instruct the first multi-link device to send the BFR frame on the second link.

9. The method according to claim 2 or 3, characterized in that: The second radio frame is used to indicate that the first link enables the cross-link capability, and the method further includes: The first multi-link device receives, through the first link, a null data physical layer protocol data unit declaration NDPA frame sent by the second multi-link device, the NDPA frame including a detection dialogue token value, and the detection dialogue token value uniquely corresponds to the first link; The first multi-link device receives, through the first link, a null data physical layer protocol data unit (NDP) frame sent by the second multi-link device; The first multi-link device sends a beam training report BFR frame to the second multi-link device through the second link, the BFR frame includes the detection dialogue token value, the BFR frame includes channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on the NDP frame.

10. The method according to any one of claims 1 to 9, characterized in that The method further comprises: The first multi-link device receives a fourth radio frame sent by the second multi-link device, where the fourth radio frame is used to respond to the first radio frame.

11. A multi-link communication method, characterized in that: include: The second multi-link device receives a first radio frame sent by the first multi-link device, where the first radio frame includes first indication information, where the first indication information is used to indicate that the first multi-link device supports cross-link capability, where the cross-link capability is a capability of the first multi-link device to confirm, on a second link, service transmission between the first multi-link device and the second multi-link device on a first link; The second multi-link device determines, according to the first indication information, that the first multi-link device supports the cross-link capability.

12. The method according to claim 11, characterized in that The method further comprises: The second multi-link device receives a second radio frame sent by the first multi-link device, where the second radio frame is used to indicate whether the first link enables the cross-link capability; The second multi-link device sends a first confirmation frame to the first multi-link device, where the first confirmation frame is used to confirm receipt of the second radio frame.

13. The method according to claim 12, characterized in that The method further comprises: The second multi-link device sends a third radio frame to the first multi-link device, where the third radio frame is used to indicate whether the first link enables the cross-link capability; The second multi-link device receives a second confirmation frame sent by the first multi-link device, where the second confirmation frame is used to confirm reception of the third radio frame.

14. The method according to claim 12 or 13, characterized in that The second radio frame is used to indicate that the first link enables the cross-link capability, and the method further includes: The second multi-link device sends a data frame to the first multi-link device through the first link; The second multi-link device sends a request frame to the first multi-link device through the second link, wherein the request frame is used to request the first multi-link device to send a third confirmation frame on the second link, and the third confirmation frame is used to confirm receipt of the data frame; The second multi-link device receives the third confirmation frame sent by the first multi-link device through the second link.

15. The method according to claim 12 or 13, characterized in that The second radio frame is used to indicate that the first link enables the cross-link capability, and the method further includes: The second multi-link device sends a Null Data Physical Layer Protocol Data Unit Declaration NDPA frame to the first multi-link device through the first link, the NDPA frame includes second indication information, the second indication information is used to instruct the first multi-link device to send a Beam Training Report BFR frame on a non-first link, the BFR frame includes channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on a Null Data Physical Layer Protocol Data Unit NDP frame; The second multi-link device sends the NDP frame to the first multi-link device through the first link; The second multi-link device receives the BFR frame sent by the second multi-link device through the second link.

16. The method according to claim 12 or 13, characterized in that The second radio frame is used to indicate that the first link enables the cross-link capability, and the method further includes: The second multi-link device sends a Null Data Physical Layer Protocol Data Unit Declaration NDPA frame to the first multi-link device through the first link, the NDPA frame includes identification information of the second link, the identification information of the second link is used to instruct the first multi-link device to send a Beam Training Report BFR frame on the second link, the BFR frame includes channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on the Null Data Physical Layer Protocol Data Unit NDP frame; The second multi-link device sends the NDP frame to the first multi-link device through the first link; The second multi-link device receives the BFR frame sent by the first multi-link device through the first link.

17. The method according to claim 12 or 13, characterized in that The second radio frame is used to indicate that the first link enables the cross-link capability, and the method further includes: The second multi-link device sends a null data physical layer protocol data unit declaration NDPA frame to the first multi-link device through the first link; The second multi-link device sends a Null Data Physical Layer Protocol Data Unit (NDP) frame to the first multi-link device through the first link; The second multi-link device sends a beam training report inquiry triggering BFRP frame to the first multi-link device through the second link, where the BFRP frame is used to instruct the first multi-link device to send a beam training report BFR frame on the second link, where the BFR frame includes channel information of the first link, where the channel information of the first link is obtained by the first multi-link device based on the NDP frame; The second multi-link device receives the BFR frame sent by the first multi-link device through the second link.

18. The method according to claim 17, characterized in that The BFRP frame includes identification information of the first link, where the identification information of the first link is used to instruct the first multi-link device to send the BFR frame on the second link.

19. The method according to claim 12 or 13, characterized in that: The second radio frame is used to indicate that the first link enables the cross-link capability, and the method further includes: The second multi-link device sends a null data physical layer protocol data unit declaration NDPA frame to the first multi-link device through the first link, the NDPA frame including a detection dialogue token value, and the detection dialogue token value uniquely corresponds to the first link; The second multi-link device sends a Null Data Physical Layer Protocol Data Unit (NDP) frame to the first multi-link device through the first link; The second multi-link device receives a beam training report BFR frame sent by the first multi-link device through the second link, the BFR frame including the detection dialogue token value, the BFR frame including channel information of the first link, and the channel information of the first link is obtained by the first multi-link device based on the NDP frame.

20. The method according to any one of claims 11 to 19, characterized in that The method further comprises: The second multi-link device sends a fourth radio frame to the first multi-link device, where the fourth radio frame is used to respond to the first radio frame.

21. A communication device, characterized in that: comprising a processor, the processor being configured to: The communication device executes the method according to any one of claims 1 to 20 by executing a computer program or an instruction, or by a logic circuit.

22. The communication device according to claim 21, characterized in that The communication device further comprises a memory for storing the computer program or instructions.

23. The communication device according to claim 21 or 22, characterized in that: The communication device further comprises a communication interface, and the communication interface is used for inputting and / or outputting signals.

24. A communication device, characterized in that: The method comprises a logic circuit and an input / output interface, wherein the input / output interface is used to input and / or output signals, and the logic circuit is used to execute the method according to any one of claims 1 to 20.

25. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program or instructions, and when the computer program or instructions are executed on a computer, the method according to any one of claims 1 to 20 is executed.

26. A computer program product, characterized in that The invention comprises instructions, which, when executed on a computer, enable the method according to any one of claims 1 to 20 to be executed.

Images