Multi-link communication setting method and related device

Abstract

This application relates to a multi-link communication setting method and related devices. The method includes: A non-AP MLD sends an association request frame on a first link to request a multi-link setting; The AP MLD replies with an association response frame on the first link to inform whether the multi-link setting is successful; The AP MLD sets a second status code field of the multi-link element of the association response frame to a newly defined value to indicate that the link is not accepted because the first link is not accepted. According to an embodiment of this application, the efficiency of the multi-link setting can be improved. This application applies to a WLAN system supporting a next-generation Wi-Fi protocol of 802.11ax, such as 802.11be, Wi-Fi7 or EHT, and other 802.11 series protocols, and in another example, applies to the next-generation protocol of 802.11, i.e., Wi-Fi8. This application may further apply to an ultra-wideband-based wireless personal area network system or a sensing system.

Description

[Technical field]

[0001] [CROSS-REFERENCE TO RELATED APPLICATIONS] This application claims priority to Chinese Patent Application No. 202210435613.2, entitled "MULTI-LINK COMMUNICATION SETUP METHOD AND RELATED APPARATUS," filed with the State Intellectual Property Office of the People's Republic of China on April 24, 2022, the entire contents of which are incorporated by reference.

[0002] [Technical field] The present application relates to the field of wireless communication technologies, and in particular to a multi-link communication setup method and related apparatus. [Background technology]

[0003] With the development of wireless communication technology, more and more wireless communication devices support multi-link (ML) communication. For example, the devices support simultaneous communication on 2.4 GHz, 5 GHz and 6 GHz frequency bands, or support communication on different channels of the same frequency band. This improves the communication rate between the devices. The devices are generally called multi-link devices (MLD). A multi-link device usually includes multiple stations, each of which operates on a frequency band, channel or link. If all stations in the MLD are access points (APs), the MLD may also be called AP MLD. If all stations in the MLD are non-access point stations (non-AP STAs), the MLD may also be called non-AP MLD. After a multi-link (also called a multi-link association) is established, the non-AP MLD may communicate with the AP MLD.

[0004] During multi-link setup (or multi-link association), the non-AP MLD may send an association request frame to the AP MLD on a link (for ease of explanation, the link is shown as the first link). The association request frame carries a multi-link element (MLE) that is used to carry information about the non-AP MLD and other links in the non-AP MLD. The association request frame is used to request to set up multi-link communication with the AP MLD. After receiving the association request frame on the first link, the AP MLD may send an association response frame back to the non-AP MLD on the first link. The association response frame is used to inform the non-AP MLD whether the multi-link communication has been set up successfully or not. The association response frame may also carry an MLE that is used to carry information about the AP MLD and other links in the AP MLD.

[0005] According to the multi-link configuration rule, if the first link is not accepted (or the first link fails to be configured), the other links cannot be accepted (or the other links cannot be successfully configured). When the first link is not accepted, the non-AP MLD does not know whether it is successful to send an association request frame on the other links to request to set up multi-link communication with the AP MLD. As a result, the non-AP MLD can only send an association request frame on each link to try to set up multi-link communication with the AP MLD, which causes low efficiency of multi-link configuration. Summary of the Invention

[0006] SUMMARY OF THE PRESENT APPLICATION An embodiment of the present application provides a multi-link communication setup method and related apparatus for improving the efficiency of multi-link setup (or multi-link association).

[0007] In the following, this application will be described from different aspects. It should be understood that cross-reference may be made to the following implementation manners and beneficial effects of the different aspects.

[0008] According to a first aspect, the application provides a multi-link communication setting method. The method includes: a first station of a non-AP MLD transmits a first association request frame on a first link, and receives a first association response frame on the first link. The first association request frame includes a multi-link element, the multi-link element includes indication information, and the indication information indicates a second link. The first association response frame includes a first status code field and a multi-link element, and the multi-link element of the first association response frame includes a second status code field. To indicate that the first link is not acceptable, the value of the first status code field is not 0, and to indicate that the reason why the second link is not acceptable is that the first link is not acceptable, the second status code field is set to a first value not 0.

[0009] In this application, a non-AP MLD has at least two links, and an AP MLD also has at least two links.

[0010] Optionally, the first station is any station in a non-AP MLD, and the first link is a link on which the first station operates.

[0011] Usually, if a link for transmitting an association request frame in a non-AP MLD is not accepted, other links cannot be accepted. However, the reasons why a link is accepted or not accepted may be different. Therefore, when a link for transmitting an association request frame in a non-AP MLD is not accepted, the non-AP MLD does not know whether multi-link communication with the AP MLD can be successfully established when the association request frame is transmitted on other links. As a result, the non-AP MLD can only send an association request frame on each link to try to establish multi-link communication, which causes low efficiency of multi-link establishment.

[0012] However, in this application, in order to indicate that the link corresponding to the second status code field is not acceptable because the transmission link is not acceptable, or to inform the non-AP MLD that the link may be acceptable if the association request frame is transmitted on the link corresponding to the second status code field, the first status code field of the association response frame is set to a non-zero value, and the second status code field of the multi-link element of the association response frame is set to a non-zero first value. Thus, the non-AP MLD may transmit an association request frame on the link for multi-link setup to improve the probability that the multi-link setup is successful. Furthermore, the non-AP MLD does not need to attempt to set up multi-link communication on each link to reduce the number of attempts and improve the efficiency of the multi-link setup.

[0013] Referring to the first aspect, in a possible implementation manner, after the first station of the non-AP MLD receives the first association response frame on the first link, the method further includes: a second station of the non-AP MLD sends a second association request frame on the second link, and receives a second association response frame on the second link.

[0014] In this application, when an association request frame is transmitted on a link corresponding to the second status code field, the first status code field of the first association response frame is set to a non-zero value, and the second status code field of the multi-link element of the first association response frame is set to a first non-zero value, to inform the non-AP MLD that the link may be accepted (or successfully configured). Thus, the non-AP MLD can know the link on which the association request frame is transmitted, for successfully configuring multi-link communication with a high probability. This can improve the probability of multi-link configuration success, reduce the number of attempts, and improve the efficiency of multi-link configuration.

[0015] According to a second aspect, the application provides a multi-link communication setting method, the method includes: a first access point of an AP MLD receives a first association request frame on a first link, and transmits a first association response frame on the first link. The first association request frame includes a multi-link element, the multi-link element includes indication information, and the indication information indicates a second link. The first association response frame includes a first status code field and a multi-link element, and the multi-link element of the first association response frame includes a second status code field. To indicate that the first link is not acceptable, the value of the first status code field is not 0, and to indicate that the reason why the second link is not acceptable is that the first link is not acceptable, the second status code field is set to a first value not 0.

[0016] Optionally, the first access point is an access point in AP MLD operating on a first link.

[0017] Referring to the second aspect, in a possible implementation manner, after the first access point of the AP MLD sends a first association response frame on the first link, the method further includes: the second access point of the AP MLD receives a second association request frame on the second link and sends a second association response frame on the second link.

[0018] In one possible implementation of the above aspects, the first value may be a value that is not used or is not defined in an existing status code field, or the first value may be a value between 0 and (2) other than an existing value. n -1), where n indicates the length of the status code field. Existing values ​​include, but are not limited to, values ​​0 through 135, excluding the following reserved values: 4, 8, 9, 20, 21, 26, 29, 36, 48, 66, 69 through 71, 90, 91, 114, 115, and 127.

[0019] In one possible implementation of the above aspects, the first status code field is located in a frame body of the association response frame. For example, the first status code field is located outside the multi-link element of the association response frame. In other words, the first status code field is not in the multi-link element of the association response frame, or the first status code field is located in the core frame of the association response frame.

[0020] In one possible implementation of the above aspects, the second status code field is located in a multilink element of the association response frame, for example, the second status code field is the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement.

[0021] According to a third aspect, the present application provides a communication device. The communication device is specifically a non-AP MLD or a chip in a non-AP MLD, and the communication device is configured to execute the method in the first aspect or any one of the possible implementations of the first aspect. The communication device includes a unit configured to execute the method in the first aspect or any one of the possible implementations of the first aspect.

[0022] According to a fourth aspect, the application provides a communication device. The communication device is specifically an AP MLD or a chip in the AP MLD, and the communication device is configured to execute the method in the second aspect or any one of the possible implementation manners of the second aspect. The communication device includes a unit configured to execute the method in the second aspect or any one of the possible implementation manners of the second aspect.

[0023] In the third or fourth aspect, the communication device may include a transceiver unit and a processing unit. For a specific description of the transceiver unit and the processing unit, please refer to the device embodiment shown below. For the beneficial effects of the third and fourth aspects, please refer to the relevant description of the first and second aspects. Details will not be described again here.

[0024] According to a fifth aspect, the application provides a multi-link communication setting method. The method includes: a first station of a non-AP MLD transmits a first association request frame on a first link, and receives a first association response frame on the first link. The first association request frame includes a multi-link element, the multi-link element includes indication information, and the indication information indicates a second link. The first association response frame includes a first status code field and a multi-link element, and the multi-link element of the first association response frame includes a second status code field. To jointly indicate that the reason why the second link is not acceptable is that the first link is not acceptable, the first status code field is set to a value indicating that the first link is not acceptable or a value indicating the reason why the first link is not acceptable (e.g., the value of the first status code field is not 0), and the second status code field is set to a value indicating that the second link is acceptable (e.g., the value of the second status code field is 0).

[0025] Optionally, the first station is any station in a non-AP MLD, and the first link is a link on which the first station operates.

[0026] It can be understood that the value of the first status code field is not 0 to indicate that the first status code field does not indicate SUCCESS, in other words, that the first link is not acceptable. If the value of the second status code field is 0, this indicates that the second status code field indicates SUCCESS, in other words, that the second link may be acceptable.

[0027] In this application, the setting rules and corresponding interpretation rules of the first status code field and the second status code field are designed. If the first status code field does not indicate success but the second status code field indicates success, this indicates that the link corresponding to the second status code field is not accepted because the first link is not accepted. Therefore, the non-AP MLD knows that when an association request frame is sent on the link for multi-link setup, there is a high probability that the multi-link setup is successful. This can improve the probability that the multi-link setup is successful, reduce the number of attempts, and improve the efficiency of the multi-link setup. Furthermore, in order to reduce overhead, no new status code value needs to be defined in this application.

[0028] Referring to the fifth aspect, in a possible implementation manner, after the first station of the non-AP MLD receives the first association response frame on the first link, the method further includes: a second station of the non-AP MLD sends a second association request frame on the second link, and receives a second association response frame on the second link.

[0029] According to a sixth aspect, the application provides a multi-link communication setting method. The method includes: a first access point of an AP MLD receives a first association request frame on a first link, and transmits a first association response frame on the first link. The first association request frame includes a multi-link element, the multi-link element includes indication information, and the indication information indicates a second link. The first association response frame includes a first status code field and a multi-link element, and the multi-link element of the first association response frame includes a second status code field. To jointly indicate that the reason why the second link is not acceptable is that the first link is not acceptable, the first status code field is set to a value indicating that the first link is not acceptable or a value indicating the reason why the first link is not acceptable (e.g., the value of the first status code field is not 0), and the second status code field is set to a value indicating that the second link is acceptable (e.g., the value of the second status code field is 0).

[0030] Optionally, the first access point is an access point in AP MLD operating on a first link.

[0031] Referring to the sixth aspect, in a possible implementation manner, after the first access point of the AP MLD sends a first association response frame on the first link, the method further includes: a second access point of the AP MLD receives a second association request frame on the second link and sends a second association response frame on the second link.

[0032] With reference to the fifth or sixth aspect, in a possible implementation manner, the first status code field is located in a frame body of the association response frame. For example, the first status code field is located outside the multilink element of the association response frame. In other words, the first status code field is not located in the multilink element of the association response frame, or the first status code field is located in the core frame of the association response frame.

[0033] Referring to the fifth or sixth aspect, in a possible implementation manner, the second status code field is located in a multilink element of the association response frame, for example, the second status code field is a status code field included in a STA profile field of a per-STA profile subelement.

[0034] According to a seventh aspect, the present application provides a communication device. The communication device is specifically a non-AP MLD or a chip in a non-AP MLD, and the communication device is configured to execute the method of the fifth aspect or any one of the possible implementations of the fifth aspect. The communication device includes a unit configured to execute the method of the fifth aspect or any one of the possible implementations of the fifth aspect.

[0035] According to an eighth aspect, the present application provides a communication device. The communication device is specifically an AP MLD or a chip in the AP MLD, and the communication device is configured to execute the method in the sixth aspect or any one of the possible implementation manners of the sixth aspect. The communication device includes a unit configured to execute the method in the sixth aspect or any one of the possible implementation manners of the sixth aspect.

[0036] In the seventh or eighth aspect, the communication device may include a transceiver unit and a processing unit. For specific descriptions of the transceiver unit and the processing unit, please refer to the device embodiments shown below. For beneficial effects of the seventh to eighth aspects, please refer to the relevant descriptions of the fifth and sixth aspects. Details will not be described again here.

[0037] According to a ninth aspect, the application provides a multi-link communication setup method. The method includes: a first station of a non-AP MLD transmits a first association request frame on a first link, and receives a first association response frame on the first link. The first association request frame includes a multi-link element, the multi-link element includes indication information, and the indication information indicates a second link. The first association response frame includes a first status code field and a multi-link element, and the first status code field is set to a second value other than 0 to indicate that the multi-link setup between the non-AP MLD and the AP MLD has failed, and that the multi-link setup may be successful if the association request frame is transmitted on another requested link. The multi-link element of the first association response frame includes a second status code field to indicate a reason why the second link is accepted or not accepted.

[0038] Optionally, the first station is any station in a non-AP MLD, and the first link is a link on which the first station operates.

[0039] Optionally, the second value is a value that is not used or is not defined in an existing Status Code field, or the second value is a value between 0 and (2) other than an existing value. n-1), where n indicates the length of the status code field. Existing values ​​include, but are not limited to, values ​​0 through 135, excluding the following reserved values: 4, 8, 9, 20, 21, 26, 29, 36, 48, 66, 69 through 71, 90, 91, 114, 115, and 127.

[0040] In this embodiment of the application, when the multi-link setup fails but one link exists and an association request frame is transmitted on the link, the first status code field of the association response frame is set to a newly defined value (i.e., the second value) to indicate that the multi-link setup may succeed. Thus, to avoid the high power consumption of the non-AP MLD caused by continuous attempts to set up multi-link communication by the non-AP MLD when the probability of the multi-link setup succeeding is small, the non-AP MLD knows whether the probability of the multi-link setup with the AP MLD succeeding exists.

[0041] Referring to the ninth aspect, in a possible implementation manner, after the first station of the non-AP MLD receives the first association response frame on the first link, the method further includes: a second station of the non-AP MLD sends a second association request frame on the second link, and receives a second association response frame on the second link.

[0042] According to a tenth aspect, the application provides a multi-link communication setup method. The method includes: a first access point of an AP MLD receives a first association request frame on a first link, and transmits a first association response frame on the first link. The first association request frame includes a multi-link element, the multi-link element includes indication information, and the indication information indicates a second link. The first association response frame includes a first status code field and a multi-link element, and the first status code field is set to a second value other than 0 to indicate that the multi-link setup between the non-AP MLD and the AP MLD has failed, and that the multi-link setup may be successful if the association request frame is transmitted on another requested link. The multi-link element of the first association response frame includes a second status code field to indicate a reason why the second link is accepted or not accepted.

[0043] Optionally, the first access point is an access point in AP MLD operating on a first link.

[0044] Optionally, the second value is a value that is not used or is not defined in an existing Status Code field, or the second value is a value between 0 and (2) other than an existing value. n -1), where n indicates the length of the status code field. Existing values ​​include, but are not limited to, values ​​0 through 135, excluding the following reserved values: 4, 8, 9, 20, 21, 26, 29, 36, 48, 66, 69 through 71, 90, 91, 114, 115, and 127.

[0045] Referring to the tenth aspect, in a possible implementation manner, after the first access point of the AP MLD sends a first association response frame on the first link, the method further includes: a second access point of the AP MLD receives a second association request frame on the second link and sends a second association response frame on the second link.

[0046] With reference to the ninth or tenth aspect, in a possible implementation, the value of the second status code field is set to 0. The first status code field is set to the second value and the second status code field is set to 0 to jointly indicate that the multi-link setup has failed and that the multi-link setup may be successful if the association request frame is transmitted on the link corresponding to the second status code field, or to indicate that the link corresponding to the second status code field is not acceptable because the first link is not acceptable (or the multi-link setup has failed).

[0047] In this application, the first status code field of the association response frame is set to a newly defined value (i.e., a second value) to jointly indicate that the multilink setup has failed and that the multilink setup may be successful if the association request frame is transmitted on a link corresponding to the second status code field, and the second status code field of the multilink element of the association response frame is set to 0 (or set to indicate success). Thus, the non-AP MLD can know the link on which the association request frame is transmitted to successfully set up multilink communication. This can improve the probability of the multilink setup being successful, reduce the number of attempts, and improve the efficiency of the multilink setup.

[0048] With reference to the ninth or tenth aspect, in a possible implementation manner, the first status code field is located in a frame body of the association response frame. For example, the first status code field is located outside the multilink element of the association response frame. In other words, the first status code field is not located in the multilink element of the association response frame, or the first status code field is located in the core frame of the association response frame.

[0049] Referring to the ninth or tenth aspect, in a possible implementation manner, the second status code field is located in a multilink element of the association response frame, for example, the second status code field is a status code field included in a STA profile field of a per-STA profile subelement.

[0050] According to an eleventh aspect, the present application provides a communication device. The communication device is specifically a non-AP MLD or a chip in a non-AP MLD, and the communication device is configured to execute the method in the ninth aspect or any one of the possible implementations of the ninth aspect. The communication device includes a unit configured to execute the method in the ninth aspect or any one of the possible implementations of the ninth aspect.

[0051] According to a twelfth aspect, the present application provides a communication device. The communication device is specifically an AP MLD or a chip in the AP MLD, and the communication device is configured to execute the method in the tenth aspect or any one of the possible implementations of the tenth aspect. The communication device includes a unit configured to execute the method in the tenth aspect or any one of the possible implementations of the tenth aspect.

[0052] In the eleventh or twelfth aspect, the communication device may include a transceiver unit and a processing unit. For a specific description of the transceiver unit and the processing unit, please refer to the device embodiment shown below. For the beneficial effects of the eleventh and twelfth aspects, please refer to the relevant description of the ninth and tenth aspects. Details will not be described again here.

[0053] According to a thirteenth aspect, the present application provides a communication device. The communication device is a non-AP MLD, and the communication device includes a processor configured to execute the method in any one of the first, fifth and ninth aspects, or any one of the possible implementations of the aspects. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method in any one of the first, fifth and ninth aspects, or any one of the possible implementations of the aspects is executed.

[0054] Referring to the thirteenth aspect, in a possible implementation the memory is located outside the communication device.

[0055] Referring to the thirteenth aspect, in a possible implementation, the memory is located in the communication device.

[0056] In this application, the processor and memory may alternatively be integrated into one component. In other words, the processor and memory may alternatively be integrated together.

[0057] Referring to the thirteenth aspect, in a possible implementation, the communication device further includes a transceiver, the transceiver configured to receive the frame or to transmit the frame.

[0058] According to a fourteenth aspect, the present application provides a communication device. The communication device is an AP MLD, and the communication device includes a processor configured to execute the method in any one of the second aspect, the sixth aspect, and the tenth aspect, or any one of the possible implementation manners of any one of the aspects. Alternatively, the processor is configured to execute a program stored in a memory. When the program is executed, the method in any one of the second aspect, the sixth aspect, and the tenth aspect, or any one of the possible implementation manners of any one of the aspects is executed.

[0059] With reference to the fourteenth aspect, in a possible implementation the memory is located outside the second communication device.

[0060] Referring to the fourteenth aspect, in a possible implementation, the memory is located in the second communication device.

[0061] In this application, the processor and memory may alternatively be integrated into one component. In other words, the processor and memory may alternatively be integrated together.

[0062] Referring to the fourteenth aspect, in a possible implementation, the communication device further includes a transceiver, the transceiver configured to receive the frame or transmit the frame.

[0063] According to a fifteenth aspect, the present application provides a communication device, the communication device including a logic circuit and an interface, the logic circuit coupled to the interface.

[0064] In one design, the logic circuit is configured to generate an association request frame. The interface is configured to output a first association request frame. The first association request frame includes a multilink element, the multilink element includes the indication information, the indication information indicating a second link. The interface is further configured to input a first association response frame. The first association response frame includes a first status code field and a multilink element, the multilink element of the first association response frame includes a second status code field, the first status code field has a value non-zero to indicate that the first link is not acceptable, and the second status code field is set to a first value non-zero to indicate that the second link is not acceptable due to the first link being unacceptable.

[0065] In one design, the logic circuit is configured to generate an association request frame. The interface is configured to output a first association request frame. The first association request frame includes a multilink element, the multilink element includes the indication information, the indication information indicating the second link. The interface is further configured to input a first association response frame. The first association response frame includes a first status code field and a multilink element, the multilink element of the first association response frame includes a second status code field, the first status code field having a value non-zero and the second status code field having a value of 0 to jointly indicate that the second link is not acceptable due to the first link being unacceptable.

[0066] In one design, the logic circuit is configured to generate an association request frame. The interface is configured to output a first association request frame. The first association request frame includes a multilink element, the multilink element includes the indication information, the indication information indicating a second link. The interface is further configured to input a first association response frame. The first association response frame includes a first status code field and a multilink element, where the first status code field is set to a second non-zero value to indicate that multilink setup between the non-AP MLD and the AP MLD has failed and that multilink setup may be successful if the association request frame is transmitted on the other requested link. The multilink element of the first association response frame includes a second status code field to indicate a reason why the second link is accepted or not accepted.

[0067] According to a sixteenth aspect, the present application provides another communication device, the communication device including a logic circuit and an interface, the logic circuit coupled to the interface.

[0068] In one design, the interface is configured to input a first association request frame, the first association request frame including a multilink element, the multilink element including indication information, the indication information indicating a second link. The logic circuit is configured to generate a first association response frame. The interface is configured to output the first association response frame, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field, the first status code field having a value non-zero to indicate that the first link is not acceptable, and the second status code field being set to a first value non-zero to indicate that the second link is not acceptable due to the first link being unacceptable.

[0069] In one design, the interface is configured to input a first association request frame, the first association request frame including a multilink element, the multilink element including indication information, the indication information indicating a second link. The logic circuit is configured to generate a first association response frame. The interface is configured to output the first association response frame, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field, the first status code field having a value non-zero and the second status code field having a value of zero to jointly indicate that the second link is not acceptable due to the first link being unacceptable.

[0070] In one design, the interface is configured to input a first association request frame. The first association request frame includes a multilink element, the multilink element includes indication information, the indication information indicating a second link. The logic circuit is configured to generate a first association response frame. The interface is configured to output the first association response frame. The first association response frame includes a first status code field and a multilink element, where the first status code field is set to a second non-zero value to indicate that multilink setup between the non-AP MLD and the AP MLD has failed and that multilink setup may be successful if the association request frame is transmitted on the other requested link. The multilink element of the first association response frame includes a second status code field to indicate a reason why the second link is accepted or not accepted.

[0071] According to a seventeenth aspect, an embodiment of the present application provides a computer readable storage medium configured to store a computer program, which, when executed on a computer, performs the method of the first, fifth and ninth aspects or any one of the possible implementations of any one of said aspects.

[0072] According to an eighteenth aspect, an embodiment of the present application provides a computer readable storage medium configured to store a computer program, which, when executed on a computer, performs the method of the second aspect, the sixth aspect and the tenth aspect, or any one of the possible implementations of any one of said aspects.

[0073] According to a nineteenth aspect, an embodiment of the present application provides a computer program product comprising a computer program or computer code, which, when the computer program product runs on a computer, performs the method of the first, fifth and ninth aspects or any one of the possible implementations of any one of said aspects.

[0074] According to a twentieth aspect, an embodiment of the present application provides a computer program product comprising a computer program or computer code, which, when the computer program product runs on a computer, performs the method of the second aspect, the sixth aspect and the tenth aspect, or any one of the possible implementations of any one of said aspects.

[0075] According to a twenty-first aspect, an embodiment of the present application provides a computer program, which, when run on a computer, performs the method of the first, fifth and ninth aspects or any one of the possible implementations of any one of said aspects.

[0076] According to a twenty-second aspect, an embodiment of the present application provides a computer program, which, when run on a computer, performs the method of the second, sixth and tenth aspects or any one of the possible implementations of any one of said aspects.

[0077] According to a twenty-third aspect, an embodiment of the present application provides a wireless communication system, the wireless communication system including a non-AP MLD and an AP MLD. The non-AP MLD is configured to perform the method in any one of the first aspect, the fifth aspect, and the ninth aspect, or a possible implementation manner of any one of the aspects is performed. The AP MLD is configured to perform the method in any one of the second aspect, the sixth aspect, and the tenth aspect, or a possible implementation manner of any one of the aspects is performed.

[0078] In this embodiment of the application, when one or more other links in the non-AP MLD can be accepted (or successfully configured), but one or more other links cannot be accepted because the link for transmitting the association request frame is not accepted (or failed to be configured) in the non-AP MLD, the status code field of the association response frame is used to inform the non-AP MLD that the reason for the one or more other links not being accepted is that the link for transmitting the association request frame is not accepted. In other words, in this embodiment of the application, the status code field of the association response frame is used to inform the non-AP MLD that one or more other links can be accepted (or successfully configured) when the association request frame is transmitted on one or more other links. Therefore, the non-AP MLD may transmit an association request frame on one or more other links for multi-link configuration to improve the probability that the multi-link configuration is successful. Furthermore, the non-AP MLD does not need to attempt to set up multi-link communication on each link to reduce the number of attempts and improve the efficiency of the multi-link configuration. [Brief description of the drawings]

[0079] In order to describe the technical solutions in the embodiments of this application more clearly, the following briefly describes the accompanying drawings used to describe the embodiments. [Figure 1] 1 is a schematic diagram of the architecture of a wireless communication system according to an embodiment of the present application; [Diagram 2] FIG. 1 is a schematic diagram of multi-link communication according to an embodiment of the present application. [Figure 3a] FIG. 2 is a schematic diagram of a structure of a multi-link device according to an embodiment of the present application. [Figure 3b] FIG. 2 is a schematic diagram of another structure of a multi-link device according to an embodiment of the present application. [Figure 4]1 is a schematic flowchart of a multi-link communication setting method according to an embodiment of the present application; [Diagram 5] FIG. 2 is a schematic diagram of a frame format of a multilink element according to an embodiment of the present application; [Figure 6] FIG. 2 is a schematic diagram of a frame format of an association response frame according to an embodiment of the present application; [Figure 7] 4 is another schematic flowchart of a multi-link communication setting method according to an embodiment of the present application; [Figure 8] 4 is yet another schematic flowchart of a multi-link communication setting method according to an embodiment of the present application. [Figure 9] 1 is a schematic diagram of the structure of a communication device according to an embodiment of the present invention; [Figure 10] 1 is a schematic diagram of the structure of a communication device 1000 according to an embodiment of the present application. [Figure 11] FIG. 2 is a schematic diagram of another structure of a communication device according to an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0080] Hereinafter, the technical solutions in the embodiments of this application will be clearly and completely described with reference to the accompanying drawings in the embodiments of this application.

[0081] In the description of this application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. The term "and / or" in this specification describes only the association relationship between related objects and indicates that three relationships may exist. For example, A and / or B may represent the following three cases: only A exists, both A and B exist, and only B exists. Furthermore, "at least one" means one or more, and "multiple" means two or more. At least one of the following items (parts) or similar expressions refers to any combination of these items, including any combination of a single item (part) or multiple items (parts). For example, at least one of a, b, or c may represent a, b, c, a and b, a and c, b and c, or a, b, and c. a, b, and c may each be singular or plural.

[0082] In the description of this application, terms such as "first" and "second" are not intended to limit the number and order of execution, and terms such as "first" and "second" do not indicate clear distinctions.

[0083] In this application, terms such as "example" or "for example" are used to denote providing an example, illustration, or explanation. The use of "example" or "for example" in this application should not be construed as indicating that any embodiment or design manner described is preferred or has more advantages over other embodiments or design manners. Rather, use of terms such as "example", "in an example", "for example", etc. is intended to present related concepts in a particular manner.

[0084] In this application, the terms "a," "an," and "the" are intended to mean "one or more" and not "one and only one," unless specifically stated otherwise.

[0085] A multi-link device may include multiple logical stations, each of which operates on a link, but multiple logical stations are permitted to operate on the same link. During data transmission between the AP MLD and the non-AP MLD, the link identifier may be used to identify the link or the station on the link. Before communication, the AP MLD and the non-AP MLD may first negotiate or communicate the correspondence between the link identifier and the link or the station on the link. Thus, during data transmission, the link identifier is carried without transmitting a large amount of signaling information to indicate the link or the station on the link. This reduces the signaling overhead and improves transmission efficiency.

[0086] Optionally, the multi-link device may realize wireless communication according to the 802.11 series of protocols. For example, an extremely high throughput (EHT) compliant station, an 802.11be compliant station, or an 802.11be compatible station realizes communication with other devices. It is clear that the other devices may or may not be multi-link devices.

[0087] The method provided in this application may be applied to a wireless local area network (WLAN) system, such as Wi-Fi. The method provided in this application is applicable to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series of protocols, such as 802.11ax next generation Wi-Fi protocols, such as 802.11be, Wi-Fi7 or extremely high throughput (EHT), and next generation 802.11be, i.e., Wi-Fi8. Otherwise not enumerated. The method provided in this application may further be applied to an ultra wide band (UWB) based wireless personal area network system or sensing system.

[0088] Although this application is primarily described using a network in which IEEE 802.11 is deployed as an example, those skilled in the art will readily appreciate that various aspects of this application can be extended to other networks using a variety of standards or protocols, such as high performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard and used primarily in Europe), wide area networks (WANs), wireless local area networks (WLANs), personal area networks (PANs), or other known or later developed networks.

[0089] FIG. 1 is a schematic diagram of the architecture of a wireless communication system according to an embodiment of this application. As shown in FIG. 1, the wireless communication system includes at least one AP MLD (for example, AP MLD 100 and AP MLD 200 in FIG. 1) and at least one non-AP MLD (for example, non-AP MLD 300 in FIG. 1). Optionally, in FIG. 1, the wireless communication system may further include a conventional station (for example, single-link non-AP STA 400 in FIG. 1, also called STA 400) that supports transmission only on a single link. The AP MLD is a device that provides services for the non-AP MLD, and the non-AP MLD may communicate with the AP MLD on multiple links to improve throughput. The STA in the non-AP MLD may also communicate with the AP in the AP MLD on a link. It can be understood that in FIG. 1, the non-AP MLD is a mobile phone and the AP MLD is a router are used as an example, and do not limit the types of the AP MLD and the non-AP MLD in this application. It can be further understood that the number of AP MLDs and the number of non-AP MLDs in Figure 1 are merely examples, and there may be more or fewer AP MLDs or non-AP MLDs in the wireless communication system, which is not limited in this application.

[0090] In the embodiments of this application, the term "communication" may also be described as "data transmission," "information transmission," or "transmission." The term "transmission" may generally mean sending and receiving.

[0091] Optionally, FIG. 2 is a schematic diagram of multi-link communication according to an embodiment of this application. As shown in FIG. 2, AP MLD includes n stations, namely AP1, AP2, ... and APn. Non-AP MLD also includes n stations, namely STA1, STA2, ... and STAn. The communication between MLDs is multi-link communication. Link 1 to link n in FIG. 2 form a multi-link. In other words, AP MLD and non-AP MLD may perform parallel communication on link 1, link 2, ... and link n. AP in AP MLD may set up an association relationship with STA in non-AP MLD. For example, STA1 in non-AP MLD sets up an association relationship with AP1 in AP MLD. STA2 in non-AP MLD sets up an association relationship with AP2 in AP MLD. STAn in non-AP MLD sets up an association relationship with APn in AP MLD.

[0092] Optionally, FIG. 3a is a schematic diagram of a structure of a multi-link device according to an embodiment of this application. The 802.11 standard focuses on the 802.11 physical layer (PHY) and medium access control (MAC) layer in a multi-link device. As shown in FIG. 3a, multiple STAs included in the multi-link device are independent of each other in the low MAC layer and the PHY layer, and are also independent of each other in the high MAC layer. FIG. 3b is a schematic diagram of another structure of a multi-link device according to an embodiment of this application. As shown in FIG. 3b, multiple STAs included in the multi-link device are independent of each other in the low MAC layer and the PHY layer, and share a high MAC layer. Obviously, in the multi-link communication process, non-AP MLD may use a structure in which the high MAC layers are independent of each other, and AP MLD uses a structure in which the high MAC layers are shared. Alternatively, non-AP MLD may use a structure in which the high MAC layers are shared, and AP MLD uses a structure in which the high MAC layers are independent of each other. Alternatively, both non-AP MLD and AP MLD may use a structure in which the high MAC layer is shared. Alternatively, both non-AP MLD and AP MLD may use a structure in which the high MAC layer is independent of each other. The schematic diagram of the internal structure of the multi-link device is not limited in this embodiment of the application. Figures 3a and 3b are merely examples for explanation. For example, the high MAC layer or the low MAC layer may be realized by one processor in the chip system of the multi-link device, or may be realized by different processing modules in the chip system.

[0093] The frequency bands in which a multi-link device operates may include one or more of the following frequency bands: sub-1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and higher frequency 60 GHz.

[0094] For example, the multi-link device in this embodiment of the present application may be a single antenna device or a multi-antenna device. For example, the multi-link device may be a device having more than two antennas. The number of antennas included in the multi-link device is not limited in the embodiment of the present application.

[0095] For example, a multi-link device (here, it may be a non-AP MLD or an AP MLD) is a device having a wireless communication function. The device may be an entire system device, or a chip, a processing system, etc. installed in the entire system device. The device in which the chip or processing system is installed may realize the method and functions in the embodiments of this application under the control of the chip or processing system. For example, in the embodiments of this application, the non-AP MLD may have a wireless transceiver function, support the 802.11 series of protocols, and communicate with an AP MLD, a single-link device, or other non-AP MLD. For example, the non-AP MLD is any user communication device that allows a user to communicate with an AP and communicate with a WLAN. For example, the non-AP MLD may be a user equipment that can connect to a network, such as a tablet computer, a desktop computer, a laptop computer, a notebook computer, an ultra-mobile personal computer (UMPC), a handheld computer, a netbook, a personal digital assistant (PDA), a mobile phone, an Internet of Things node in the Internet of Things, or an in-vehicle communication device in the Internet of Vehicles. The non-AP MLD may alternatively be a chip and a processing system in the above terminal. The AP MLD may be a device that provides services for the non-AP MLD and may support the 802.11 series of protocols. For example, the AP MLD may be a communication entity such as a communication server, a router, a switch or a bridge, or the AP MLD may include various types of macro base stations, micro base stations, relay stations, etc. Obviously, the AP MLD may alternatively be a chip and a processing system in various types of devices. In this way, the method and functions in the embodiments of this application are realized. The 802.11 protocol may support 802.11be or be a protocol compatible with 802.11be.

[0096] It can be understood that the multi-link device may support high-rate and low-latency transmission. With the continuous evolution of application scenarios of wireless local area networks, the multi-link device may further be used in more scenarios, such as sensor nodes (e.g., smart meters, smart electric meters, and smart air detection nodes) in smart cities, smart devices (e.g., smart cameras, projectors, displays, televisions, stereos, refrigerators, and washing machines) in smart homes, nodes in the Internet of Things, entertainment terminals (e.g., AR, VR, or other wearable devices), smart devices (e.g., printers and projectors) in smart offices, Internet of Vehicles devices in the Internet of Vehicles, and some infrastructures (vending machines, self-service navigation stations in supermarkets, self-service cash register devices, and self-service ordering machines) in daily life scenarios. The specific forms of non-AP MLD and AP MLD are not limited in the embodiments of this application, and are merely examples for the description herein.

[0097] This application provides a multi-link communication setup method and related apparatus for improving the efficiency of multi-link setup (or multi-link association).

[0098] Normally, a non-AP MLD may simultaneously set up associations with multiple links in an AP MLD by performing multi-link setup on one link. The multi-link setup process is as follows: The non-AP MLD sends an association request frame carrying a multi-link element (MLE) on a link (for ease of description, the link is shown as the first link). The multi-link element carries information about other links to request to set up multi-link communication with the AP MLD. After receiving the association request frame, the AP MLD replies to the non-AP MLD with an association response frame carrying a multi-link element on the first link to inform the non-AP MLD whether the multi-link communication setup is successful or not.

[0099] Usually, in non-AP MLD, when a link for transmitting an association request frame (i.e., the first link) is not accepted (or the first link fails to be set up), other links in non-AP MLD cannot be accepted (or other links fail to be set up). However, the reasons why a link is accepted or not accepted (or the link is successfully set up or fails to be set up) may be different. For example, the loads of different links may be different. When the load of a link is heavy, the link may not be accepted (or the link fails to be set up). For example, the capabilities of non-AP MLD on different links may be different. When the capabilities of non-AP MLD on a link are weak, the link may not be accepted (or the link fails to be set up). As a result, the following cases may occur: In non-AP MLD, when a link for transmitting an association request frame (i.e., the first link) is not accepted (or fails to be set up), one or more other links may be accepted (or successfully set up). However, since the first link is not accepted (or fails to be set up), one or more other links cannot be accepted (or fails to be set up). Therefore, in non-AP MLD, when a link for transmitting an association request frame is not accepted (or fails to be set up), the non-AP MLD does not know whether multi-link communication with the AP MLD can be successfully set up if the association request frame is sent on another link. As a result, the non-AP MLD can only send an association request frame on each link to try to set up multi-link communication, which causes low efficiency of multi-link setting.

[0100] However, in this embodiment of the application, when one or more other links in the non-AP MLD can be accepted (or successfully configured), but one or more other links cannot be accepted because the link for transmitting the association request frame is not accepted (or failed to be configured), the status code field of the association response frame is used to inform the non-AP MLD that the reason for the one or more other links not being accepted is that the link for transmitting the association request frame is not accepted. In other words, in this embodiment of the application, the status code field of the association response frame is used to inform the non-AP MLD that one or more other links can be accepted (or successfully configured) when the association request frame is transmitted on one or more other links. Therefore, the non-AP MLD may transmit an association request frame on one or more other links for multi-link configuration to improve the probability that the multi-link configuration is successful. Furthermore, the non-AP MLD does not need to attempt to set up multi-link communication on each link to reduce the number of attempts and improve the efficiency of the multi-link configuration.

[0101] Since the association request frame and the association response frame are transmitted on the same link, it can be understood that the "link for transmitting the association request frame" referred to in this application is also the "link for transmitting the association response frame." The "other link" referred to in this application is a link other than the "link for transmitting the association request frame" in non-AP MLD.

[0102] Below, the technical solutions provided in this application will be described in detail with reference to more accompanying drawings.

[0103] In order to clearly describe the technical solutions in this application, this application is described by using multiple embodiments. For details, please refer to the following. In this application, unless otherwise specified, the same or similar parts of the embodiments or realization methods will refer to each other. In the embodiments and the realization methods / methods in the embodiments of this application, the terms and / or descriptions are consistent and may be mutually referenced between different embodiments and between the realization methods / methods in the embodiments, unless otherwise specified or unless logical contradiction occurs. The technical features in different embodiments and the realization methods / methods in the embodiments may be combined to form new embodiments, realization methods or realization methods based on their internal logical relationships. The following realization methods of this application are not intended to limit the protection scope of this application.

[0104] [Embodiment 1] Embodiment 1 of this application mainly describes a case where the value of a Status Code field of a multi-link element (MLE) is extended to indicate that the reason why a link in a non-AP MLD (where the link is not a link for transmitting an association request frame) is not accepted is that the link in a non-AP MLD is not accepted for transmitting an association request frame.

[0105] 4 is a schematic flowchart of a multi-link communication setting method according to an embodiment of this application. As shown in FIG. 4, the multi-link communication setting method includes, but is not limited to, the following steps:

[0106] S101: A first station in a non-AP MLD sends a first association request frame on a first link, where the first association request frame includes a multilink element, where the multilink element includes indication information, and where the indication information indicates a second link.

[0107] In response, the first access point in the AP MLD receives a first association request frame on the first link.

[0108] In this embodiment of the application, the non-AP MLD has at least two links, and the AP MLD also has at least two links. It can be understood that the number of links in the non-AP MLD may or may not be equal to the number of links in the AP MLD. This is not limited in this embodiment of the application.

[0109] Optionally, the first station is any station in non-AP MLD, and the first link is the link on which the first station operates. Specifically, the station in non-AP MLD (i.e., the first station in this embodiment of this application) may send an association request frame (i.e., the first association request frame in this embodiment of this application) on a link (i.e., the first link in this embodiment of this application). To request to set up multi-link communication with AP MLD, the association request frame carries a multi-link element (MLE), and the multi-link element carries information about another link (hereinafter, the second link). For the specific frame format and function of the first association request frame, please refer to the description in the existing standard. Details will not be described in this embodiment of this application.

[0110] Optionally, the multilink element included in the first association request frame carries indication information, and the indication information indicates a second link. The second link is a link other than the first link in the non-AP MLD, i.e., another link. It can be understood that the second link is a link within a link where the non-AP MLD performs multilink configuration with the AP MLD other than the first link. For example, the non-AP MLD has three links, i.e., link 1, link 2, and link 3. When the non-AP MLD performs multilink configuration (or multilink communication configuration) with the AP MLD on link 1 and link 3, and the non-AP MLD sends an association request frame on link 1, link 1 is the first link and link 3 is the second link. In another example, the non-AP MLD has three links, i.e., link 1, link 2, and link 3. When a non-AP MLD performs multi-link configuration (or multi-link communication configuration) with an AP MLD on link 1, link 2, and link 3, and the non-AP MLD sends an association request frame on link 1, link 1 is the first link, and both link 2 and link 3 are second links.

[0111] Optionally, the indication information is carried in a STA control field of a per-STA profile subelement of the multi-link element. For example, the indication information may be a link ID subfield of the STA control field. It can be understood that one link ID subfield is used to identify one second link. It can be further understood that the value and meaning of the link ID subfield refer to the meaning in the existing standard. Details are not described here.

[0112] FIG. 5 is a schematic diagram of a frame format of a multi-link element according to an embodiment of this application. As shown in FIG. 5, the multi-link element includes, but is not limited to, a multi-link control field, a common information field, and a link information field. The multi-link control field carries indication information indicating the type of the multi-link element and the fields present and absent in the common information field. The common information field carries information about the multi-link device (MLD level information, i.e., MLD-level info) and the common information of multiple stations of the multi-link device. The link information field carries information about the stations on each link in the multi-link device. It can be understood that the specific meaning of each field of the multi-link element can be referred to the description in the existing standard. Details are not described here. It can be further understood that FIG. 5 only shows some fields of the multi-link element. For the specific frame format of the multi-link element, refer to the description in the existing standard. Details are not described here.

[0113] As shown in FIG. 5, the Link Information field includes one or more per-STA profile subelements. One per-STA profile subelement carries information about a station on a link. The per-STA profile subelement includes a STA Control field, which includes a link ID subfield. The Link ID subfield specifies a value that uniquely identifies the link where the reported STA is operating on. In other words, the link ID subfield indicates a link. It can be understood that the reported STA in this application is the STA operating on the second link.

[0114] It may be understood that if the multilink element carried in the association request frame includes multiple per-STA profile sub-elements, then there are multiple link identifier sub-fields, in other words, there are multiple second links.

[0115] S102: A first access point in the AP MLD sends a first association response frame on a first link, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field, the value of the first status code field is not 0 to indicate that the first link is not acceptable, and the second status code field is set to a first value not 0 to indicate that the cause of the second link being not acceptable is that the first link is not acceptable.

[0116] In response, the first station of the non-AP MLD receives a first association response frame on the first link. The first station of the non-AP MLD may know information about whether the first link is acceptable (or whether the multi-link communication setup is successful or not, or whether the multi-link setup is successful or not) and whether the second link is acceptable (including the reason why the second link is not acceptable) from the first status code field and the second status code field of the first association response frame.

[0117] Optionally, the first access point is an access point in AP MLD operating on a first link.

[0118] Optionally, the first status code field may indicate whether the first link (or the link for transmitting the first association request frame) is accepted, whether the first link is successfully set, or whether the first link becomes a link in the multi-link communication. If the first link is accepted, the first status code field may indicate success. If the first link is not accepted, the first status code field may indicate a failure cause (the Status Code field in the core frame or frame body or not in the multi-link element of the Association Response frame shall indicate SUCCESS if the link is accepted or the failure cause if the link is not accepted). When the first status code field is set to 0, it indicates success, i.e., the first link is accepted. In other words, when the value of the first status code field is not 0, it indicates that the first link is not accepted, or indicates a cause that the first link is not accepted. Specifically, the value and meaning of the first status code refer to existing standards. The details will not be explained here.

[0119] It may be understood that "unacceptable" and "cannot be accepted" in this application have the same meaning, such as not being accepted, not being successfully set up, not becoming a link in a multi-link communication, or other same or similar meanings.

[0120] Optionally, if the first link is accepted (if the link is accepted), the multi-link setup between the non-AP MLD and the AP MLD may be successful, or the multi-link communication between the non-AP MLD and the AP MLD may be successfully set up. However, if the first link is not accepted (if the link is not accepted), the multi-link setup between the non-AP MLD and the AP MLD may fail, or the multi-link communication between the non-AP MLD and the AP MLD may fail to be set up. When the first status code field indicates that the first link is not accepted, or when the first status code field indicates the cause of the first link being not accepted, the first status code field also indicates that the multi-link setup between the non-AP MLD and the AP MLD has failed, or the multi-link communication between the non-AP MLD and the AP MLD has failed to be set up. In other words, when the value of the first status code field is not 0, it may indicate that the first link is not acceptable or the reason why the first link is not acceptable, and may further indicate that multi-link setup between the non-AP MLD and the AP MLD has failed, or that multi-link communication between the non-AP MLD and the AP MLD has failed to be setup.

[0121] Optionally, the second status code field may indicate whether the second link is accepted, whether the second link is successfully set up, or whether the second link will be a link in the multi-link communication. If the second link is accepted, the second status code field may indicate success. If the second link is not accepted, the second status code field may indicate a failure cause (the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement shall indicate SUCCESS if the link is accepted or the failure cause if the link is not accepted). When the second status code field is set to 0, it indicates SUCCESS, i.e., the second link is accepted. In other words, when the value of the second status code field is not 0, it indicates that the second link is not accepted or indicates the cause of the second link not being accepted.

[0122] Optionally, a first value other than 0 is newly defined in this embodiment of the application, as shown in Table 1. When the second status code field is set to the first value, the second status code field indicates that the second link is not acceptable because the first link is not acceptable, or indicates that the second link is not acceptable only because the first link is not acceptable. In other words, when the second status code field is set to the first value, it indicates that the second link may be successfully established when the non-AP MLD sends an association request frame on the second link. The value of the first status code field cannot be the first value in this embodiment of the application. In other words, only the second status code field can be the first value.

[0123] The first value may be a value that is not used or defined in an existing Status Code field. For example, assuming that the length of the Status Code field is n bits, the first value may be any value from 0 to (2 n For example, n is equal to 16. Existing values ​​include values ​​from 0 to 135, excluding the reserved values ​​(4, 8, 9, 20, 21, 26, 29, 36, 48, 66, 69-71, 90, 91, 114, 115, 127). For example, the first value may be any value from 0 to (2 16 -1), for example, 136, 137, 138, or 139. In other examples, the first value is any reserved value between 0 and 135, for example, any value between 4, 8, 9, 20, 21, 26, 29, 36, 48, 66, 69-71, 90, 91, 114, 115, or 127. [Table 1]

[0124] It should be understood that in this application, the link through which the association request / response frames are exchanged may be called a transmitted link, and the other link is called a non-transmitted link correspondingly. Thus, in steps S101 and S102, the first link is a transmitted link, and the second link is a non-transmitted link. The meaning indicated when the second status code field is set to a first value may also be described as follows: The cause of the non-transmitted link not being accepted is that the transmitted link is not accepted.

[0125] Optionally, the first status code field may be located in a frame body of the association response frame. For example, the first status code field may be located outside the multi-link element of the association response frame. In other words, the first status code field is not in the multi-link element of the association response frame, or the first status code field is located in the core frame of the association response frame. The core frame may be a content other than the multi-link element (MLE) in the association response frame. The second status code field may be located in the multi-link element of the association response frame. For example, the second status code field is a status code field included in the STA Profile subfield of the Per-STA Profile subelement.

[0126] FIG. 6 is a schematic diagram of a frame format of an association response frame according to an embodiment of this application. As shown in FIG. 6, the association response frame includes, but is not limited to, a Status Code field (i.e., a first status code field) and a multi-link element (MLE). The multi-link element includes, but is not limited to, a Multi-Link Control field, a Common Info field, and a Link Info field. The Link Info field includes one or more per-STA profile subelements. The per-STA profile subelements include, but are not limited to, a STA Control field and a STA Profile field. The STA Control field includes a link ID subfield, which indicates a second link (or a non-transmission link). The STA Profile field includes a Status Code field (i.e., a second status code field) which indicates whether the link indicated by the link ID subfield is accepted. It can be understood that FIG. 6 only shows some fields of the association response frame. For the specific frame format of the association response frame, please refer to the description in the existing standard. The details will not be described here. It can be further understood that for the specific meaning of each field of the association response frame, please refer to the description in the existing standard. The details will not be described here.

[0127] Optionally, in this embodiment of the application, the multilink element of the first association response frame includes one or more second status code fields, and one second status code field indicates whether one non-transmitting link is accepted. When the non-transmitting link in the non-AP MLD can be accepted (or successfully configured) but the non-transmitting link cannot be accepted because the transmitting link is not accepted (or failed to be configured), the AP MLD may set the second status code field corresponding to the non-transmitting link to a first value to indicate that the non-transmitting link is not accepted because the transmitting link is not accepted, or to inform the non-AP MLD that the non-transmitting link may be accepted (or successfully configured) when the non-AP MLD sends an association request frame on the non-transmitting link. It can be understood that when the second status code field is set to a first value, the value of the first status code field needs to be set to a non-zero value to indicate that the reason why the second link is not accepted is that the first link is not accepted.

[0128] In this embodiment of the application, when one or more non-transmitting links in the non-AP MLD can be accepted (or successfully configured), but one or more non-transmitting links cannot be accepted because a transmitting link is not accepted (or failed to be configured), the value of the first status code field of the association response frame is not 0, and the second status code field of the multi-link element of the association response frame (the status code field included in the STA profile subfield of the per-STA profile subelement) is set to a newly defined value (i.e., the first value) to indicate that the reason why one or more non-transmitting links are not accepted is that the transmitting link is not accepted. In other words, when the association request frame is transmitted on one or more non-transmitting links, the second status code field is set to the first value to inform the non-AP MLD that one or more non-transmitting links may be accepted (or successfully configured). Therefore, according to this embodiment of the application, the probability of the multi-link configuration being successful can be improved. Furthermore, the non-AP MLD does not need to attempt to set up multi-link communication on each link, so as to reduce the number of attempts and improve the efficiency of the multi-link configuration.

[0129] Optionally, in the first association response frame in this embodiment of the application, the value of at least one second status code field is a first value, to indicate that the reason why the at least one second link is not accepted is that the first link is not accepted. For ease of explanation, this embodiment of the application is described by using an example in which the value of one second status field of the first association response frame is a first value.

[0130] Optionally, after step S102, the multi-link communication setting method may further include one or more of the following steps:

[0131] S103: A second station in the non-AP MLD sends a second association request frame on the second link.

[0132] In response, a second access point in the AP MLD receives a second association request frame on the second link.

[0133] According to the definition of a transmitted link (the link through which the association request / response frames are exchanged is called a transmitted link), it can be understood that in the process of steps S103 to S104, the first link is no longer a transmitted link but becomes a non-transmitted link, and the second link is now a transmitted link.

[0134] S104: A second access point in the AP MLD sends a second association response frame on the second link.

[0135] In response, the second station in the non-AP MLD receives a second association response frame on the second link.

[0136] Optionally, the value of the second status code field of the first association response frame is a first value. Thus, the non-AP MLD may determine that the reason why the second link corresponding to the second status code field is not accepted is that the first link is not accepted, or may determine that the reason why the second link fails to be set is only because the first link fails to be set, or may determine that the second link may be successfully set if the non-AP MLD sends an association request frame on the second link. Thus, when the first link is not accepted (in other words, the value of the first status code field of the first association response frame is not 0) and the value of the second status code field of the first association response frame is a first value, the second station of the non-AP MLD may send a second association request frame on the second link corresponding to the second status code field to request to set up an association with the AP MLD on at least the second link. Correspondingly, after receiving the second association request frame on the second link, the second access point of the AP MLD replies with a second association response frame on the second link to notify whether the association is successfully established or not.

[0137] It may be understood that the exchange of the second association request frame and the second association response frame between the non-AP MLD and the AP MLD may be for multi-link setup or for association setup only on the second link. This is not limited in this embodiment of the application. In other words, whether the second association request frame and the second association response frame carry a multi-link element is not limited in this embodiment of the application. It may be further understood that if the exchange of the second association request frame and the second association response frame between the non-AP MLD and the AP MLD is for multi-link setup, the multi-link communication may not be set up on the first link. In other words, if the second association request frame carries a multi-link element, the multi-link element may not carry information about the first link. In the previous process of multi-link setup (for example, step S201 and step S202), the first link is not accepted (i.e., the setup fails). In this case, the second association request frame is sent on the second link for multi-link setup, and it is highly likely that the first link is still not accepted (i.e., the setup fails). Therefore, in order to improve the probability that the multi-link setup is successful, the multi-link element of the second association request frame does not carry information about the first link (in this case, the first link is a non-transmission link). It is clear that the information about the first link may be carried in the multi-link element of the second association request frame instead. Compared with the case of the first link in the previous process of multi-link setup (for example, step S201 and step S202), the case of the first link may change, and the first link may be accepted (i.e., successfully set up).

[0138] In this embodiment of the application, when an association request frame is transmitted on a link corresponding to the second status code field, the second status code field of the multi-link element of the association response frame is set to a newly defined value (i.e., the first value) to inform the non-AP MLD that the link may be accepted (or successfully configured). Thus, the non-AP MLD can know the link on which the association request frame is transmitted to successfully configure multi-link communication with a high probability. This can improve the probability of multi-link configuration success, reduce the number of attempts, and improve the efficiency of multi-link configuration.

[0139] [Embodiment 2] Embodiment 2 of this application mainly describes the case where the outer status code field (i.e., the first status code field) of the multilink element of the association response frame and the status code field (i.e., the second status code field) of the multilink element jointly indicate that the reason why the link is not accepted in the non-AP MLD is that the link for transmitting the association request frame is not accepted in the non-AP MLD.

[0140] 7 is another schematic flowchart of a multi-link communication setting method according to an embodiment of this application. As shown in FIG. 7, the multi-link communication setting method includes, but is not limited to, the following steps:

[0141] S201: A first station in a non-AP MLD sends a first association request frame on a first link, where the first association request frame includes a multilink element, where the multilink element includes indication information, and where the indication information indicates a second link.

[0142] In response, the first access point in the AP MLD receives a first association request frame on the first link.

[0143] For the implementation manner of step S201 in this embodiment of this application, please refer to the implementation manner of step S101 in embodiment 1. The details will not be described again here.

[0144] S202: A first access point in the AP MLD sends a first association response frame on a first link, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field, and the first status code field is set to a value indicating that the first link is not acceptable or a value indicating the cause of the first link being not acceptable, and the second status code field is set to a value indicating that the second link is acceptable, to jointly indicate that the cause of the second link being not acceptable is that the first link is not acceptable.

[0145] In response, the non-AP MLD first station receives a first association response frame on the first link, and may determine that the second link is not acceptable because the first link is not acceptable based on the value of the first status code field and the value of the second status code field of the first association response frame.

[0146] Optionally, the first access point is an access point in AP MLD operating on a first link.

[0147] Optionally, the first status code field may indicate whether the first link (or the link for transmitting the first association request frame) is accepted, whether the first link is successfully set up, or whether the first link will be a link in a multi-link communication. For example, when the first status code field is set to 0, this indicates SUCCESS, i.e., the first link is accepted. In other words, when the value of the first status code field is not 0, this indicates that the first link is not accepted, or indicates the reason why the first link is not accepted. The second status code field may indicate whether the second link is accepted, whether the second link is successfully set up, or whether the second link will be a link in a multi-link communication. For example, when the second status code field is set to 0, this indicates SUCCESS, i.e., the second link is accepted. In other words, when the value of the second status code field is not 0, this indicates that the second link is not accepted, or indicates the reason why the second link is not accepted. The first status code field being set to a value indicating that the first link is not acceptable or a value indicating the reason why the first link is not acceptable, and the second status code field being set to a value indicating that the second link is acceptable, to jointly indicate that the reason why the second link is not acceptable is that the first link is not acceptable, may alternatively be written as follows: The first status code field has a value other than 0, and the second status code field has a value of 0, to jointly indicate that the reason why the second link is not acceptable is that the first link is not acceptable.

[0148] Optionally, for the relationship between whether the first link is accepted and whether the multi-link setup is successful, refer to the relevant description in embodiment 1. The details are not described again here.

[0149] Optionally, the first status code field may be located in a frame body of the association response frame. For example, the first status code field may be located outside the multilink element of the association response frame. In other words, the first status code field is not located in the multilink element of the association response frame, or the first status code field is located in the core frame of the association response frame, and the core frame may be a content other than the multilink element (MLE) in the association response frame. The second status code field may be located in the multilink element of the association response frame. For example, the second status code field is a status code field included in the STA profile field of the per-STA profile subelement. For the frame format of the association response frame, please refer to FIG. 6. Details will not be described again here.

[0150] Optionally, in this embodiment of this application, the multilink element of the first association response frame includes one or more second status code fields, and one second status code field indicates whether one non-transmitting link is accepted. When the non-transmitting link can be accepted (or successfully configured) but the non-transmitting link cannot be accepted because the transmitting link is not accepted (or failed to be configured), the AP MLDs may jointly indicate that the reason the non-transmitting link is not accepted (or failed to be configured) is that the transmitting link is not accepted (or failed to be configured), or jointly indicate that the reason the non-transmitting link is not accepted is only that the transmitting link is not accepted, or when the non-AP MLD sends an association request frame on the non-transmitting link, the first status code field may be set to a non-zero value and the second status code field corresponding to the non-transmitting link may be set to a first value to inform the non-AP MLD that the non-transmitting link can be accepted (or successfully configured).

[0151] In other words, if the first status code field does not indicate success (i.e., the first status code field indicates that the first link is not acceptable, or indicates a reason why the first link is not acceptable, or the value of the first status code field is not 0) and the second status code field indicates success (i.e., the second status code field indicates that the second link is acceptable, or the value of the second status code field is 0), this indicates that the reason why the second link is not acceptable is that the first link is not acceptable.

[0152] In other words, if the non-transmitting link is accepted, the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement shall indicate SUCCESS if the link is accepted or the failure cause if the link is not accepted with the exception below. If the only reason the link is not accepted is because the transmitting link is not accepted, the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement shall indicate SUCCESS if the link is not accepted only because the transmitting link is not accepted.

[0153] Alternatively, when the Status Code field not in the multi-link element of the Association Response frame does not indicate SUCCESS, and the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement indicates SUCCESS, the corresponding link is not accepted, but can be accepted if the Association Request frame is transmitted on that link.

[0154] In this embodiment of the application, the setting rule and corresponding interpretation rule of the first status code field and the second status code field are designed. When the first status code field does not indicate success, but the second status code field indicates success, this indicates that the link corresponding to the second status code field is not accepted because the first link is not accepted. Therefore, the non-AP MLD knows that when an association request frame is sent on the link for multi-link setup, there is a high probability that the multi-link setup is successful. This can improve the probability that the multi-link setup is successful, reduce the number of attempts, and improve the efficiency of the multi-link setup.

[0155] Optionally, in this embodiment of the application, to jointly indicate that the reason why at least one second link is not acceptable is that the first link is not acceptable, the value of the first status code field of the first association response frame is not 0, and the value of the at least one second status code field is 0. For ease of explanation, this embodiment of the application is described by using an example in which the value of one second status field of the first association response frame is 0.

[0156] Optionally, after step S202, the multi-link communication setting method may further include the following steps:

[0157] S203: A second station in the non-AP MLD sends a second association request frame on the second link.

[0158] In response, a second access point in the AP MLD receives a second association request frame on the second link.

[0159] According to the definition of a transmitted link (the link through which the association request / response frames are exchanged is called a transmitted link), it can be understood that in the process of steps S103 to S104, the first link is no longer a transmitted link but becomes a non-transmitted link, and the second link is now a transmitted link.

[0160] S204: A second access point in the AP MLD sends a second association response frame on the second link.

[0161] In response, the second station in the non-AP MLD receives a second association response frame on the second link.

[0162] For the implementation manner of step S203 and step S204 in this embodiment of the present application, please refer to the implementation manner of step S103 and step S104 in embodiment 1. The details will not be described again here.

[0163] In this embodiment of the application, when one or more non-transmitting links in a non-AP MLD can be accepted (or successfully configured), but one or more non-transmitting links cannot be accepted because a transmitting link is not accepted (or failed to be configured), the value of the first status code field of the association response frame is set to a non-zero value, and the second status code field of the multilink element of the association response frame is set to 0 (or set to indicate success) to jointly indicate that the reason why the non-transmitting links are not accepted is that the transmitting link is not accepted, or to inform the non-AP MLD that the non-transmitting links may be accepted (or successfully configured) when an association request frame is sent on a non-transmitting link. This can increase the probability that the multilink configuration is successful. Furthermore, the non-AP MLD does not need to try to set up multilink communication on each link, so as to reduce the number of attempts and improve the efficiency of the multilink configuration. In order to save overhead, no new status code value needs to be defined.

[0164] [Embodiment 3] The third embodiment of this application mainly describes extending the value of the outer status code field (i.e., the first status code field) of the multi-link element of the association response frame to indicate that the multi-link setup has failed. In addition, the value of the status code field (i.e., the second status code field) of the multi-link element may be set to jointly indicate that the link corresponding to the second status code field is not acceptable because the transmission link is not acceptable.

[0165] 8 is yet another schematic flowchart of a multi-link communication setting method according to an embodiment of this application. As shown in FIG. 8, the multi-link communication setting method includes, but is not limited to, the following steps:

[0166] S301: A first station in a non-AP MLD sends a first association request frame on a first link, where the first association request frame includes a multilink element, where the multilink element includes indication information, and where the indication information indicates a second link.

[0167] In response, the first access point in the AP MLD receives a first association request frame on the first link.

[0168] For the implementation manner of step S301 in this embodiment of this application, please refer to the implementation manner of step S101 in embodiment 1. The details will not be described again here.

[0169] S302: A first access point of the AP MLD sends a first association response frame on the first link, where the first association response frame includes a first status code field, and the first status code field is set to a second value other than 0 to indicate that multi-link setup between the non-AP MLD and the AP MLD has failed and that the multi-link setup may be successful if the association request frame is transmitted on the other requested link.

[0170] In response, the first station in the non-AP MLD receives a first association response frame on the first link.

[0171] Optionally, the first access point is an access point in AP MLD operating on a first link.

[0172] Optionally, the first association response frame includes a first status code field and a multilink element, and the multilink element of the first association response frame includes one or more second status code fields, and a second status code field indicates the reason why a link is accepted or not accepted. For the specific meaning of the second status code field, please refer to the relevant description in embodiment 1. Details will not be described again here.

[0173] Optionally, a second value is newly defined in this embodiment of the present application, and the second value is a value that is not used or defined in the existing Status Code field. For example, assuming that the length of the Status Code field is n bits, the second value can be any value between 0 and (2 n For example, n is equal to 16. The existing values ​​include, but are not limited to, values ​​from 0 to 135 other than 0 to 135 or the reserved values ​​(4, 8, 9, 20, 21, 26, 29, 36, 48, 66, 69 to 71, 90, 91, 114, 115, 127). For example, the second value may be any value from 0 to (2 16 −1), for example, 136, 137, 138 or 139. Second The value of is any reserved value between 0 and 135, such as any value between 4, 8, 9, 20, 21, 26, 29, 36, 48, 66, 69-71, 90, 91, 114, 115, or 127. It can be understood that the second value in this embodiment of the application is different from the first value in the first embodiment.

[0174] As shown in Table 2, when the first status code field is set to the second value, the first status code field indicates that the multi-link setup between the non-AP MLD and the AP MLD has failed, or indicates that the multi-link setup between the non-AP MLD and the AP MLD has failed and that the multi-link setup may be successful if the association request frame is transmitted on another requested link (a link other than the first link). In this embodiment of this application, the value of the second status code field cannot be the second value. In other words, only the first status code field can be the second value. [Table 2]

[0175] It should be understood that when the value of the first status code field is an existing value (e.g., 0 to 135), this indicates whether the first link (or the link for transmitting the first association request frame) is accepted, whether the setting is successful, or whether the first link becomes a link in multi-link communication. For details, refer to the related description in embodiment 1. Details will not be described again here. When the value of the first status code field is a second value, this indicates that the multi-link setting has failed, or indicates that the multi-link setting has failed but may be successful if the association request frame is transmitted on another requested link.

[0176] In this embodiment of the application, when the multi-link setup fails but one link exists and an association request frame is transmitted on the link, the first status code field of the association response frame is set to a newly defined value (i.e., the second value) to indicate that the multi-link setup may succeed. Thus, to avoid the high power consumption of the non-AP MLD caused by continuous attempts to set up multi-link communication by the non-AP MLD when the probability of the multi-link setup succeeding is small, the non-AP MLD knows whether the probability of the multi-link setup with the AP MLD succeeding exists.

[0177] Optionally, the first status code field may be located in a frame body of the association response frame. For example, the first status code field may be located outside the multilink element of the association response frame. In other words, the first status code field is not located in the multilink element of the association response frame, or the first status code field is located in the core frame of the association response frame, and the core frame may be a content other than the multilink element (MLE) in the association response frame. The second status code field may be located in the multilink element of the association response frame. For example, the second status code field is a status code field included in the STA profile field of the per-STA profile subelement. For the frame format of the association response frame, please refer to FIG. 6. Details will not be described again here.

[0178] Optionally, when a non-transmitting link can be accepted (or successfully configured) but cannot be accepted because multi-link setup has failed (e.g., the transmitting link is not accepted), the AP MLD may set the first status code field to a second value and set the second status code field corresponding to the non-transmitting link to 0 to jointly indicate that multi-link setup has failed and that multi-link setup may be successful if the association request frame is transmitted on the non-transmitting link, or to jointly indicate that the reason the non-transmitting link is not accepted is that the transmitting link is not accepted (or the multi-link setup has failed).

[0179] In other words, if the first status code field is set to the second value and the second status code field indicates success (in other words, the second status code field indicates that the second link is acceptable or the value of the second status code field is 0), this indicates that the multi-link setup has failed and that the multi-link setup may be successful if the association request frame is transmitted on the second link, or indicates that the second link is not acceptable because the first link is not acceptable (or the multi-link setup has failed).

[0180] Optionally, in the first association response frame in this embodiment of this application, the first status code field is set to a second value, and the value of the at least one second status code field is 0, to jointly indicate that the multi-link setup may be successful if the multi-link setup fails and the association request frame is transmitted on at least one second link corresponding to the at least one second status code field. For ease of explanation, this embodiment of this application is described by using an example in which the value of one second status field of the first association response frame is 0.

[0181] Optionally, after step S302, the multi-link communication setting method may further include the following steps:

[0182] S303: A second station in the non-AP MLD sends a second association request frame on the second link.

[0183] In response, a second access point in the AP MLD receives a second association request frame on the second link.

[0184] According to the definition of a transmitted link (the link through which the association request / response frames are exchanged is called a transmitted link), it can be understood that in the process of steps S103 to S104, the first link is no longer a transmitted link but becomes a non-transmitted link, and the second link is now a transmitted link.

[0185] S304: A second access point in the AP MLD sends a second association response frame on the second link.

[0186] In response, the second station in the non-AP MLD receives a second association response frame on the second link.

[0187] For the implementation manner of step S303 and step S304 in this embodiment of the present application, please refer to the implementation manner of step S303 and step S304 in embodiment 1. The details will not be described again here.

[0188] In this embodiment of the application, the first status code field of the association response frame is set to a newly defined value (i.e., the second value) to jointly indicate that the multilink setup has failed and that the multilink setup may be successful if the association request frame is transmitted on a link corresponding to the second status code field, and the second status code field of the multilink element of the association response frame is set to 0 (or set to indicate success). Thus, the non-AP MLD can know the link on which the association request frame is transmitted to successfully set up multilink communication. This can improve the probability of the multilink setup being successful, reduce the number of attempts, and improve the efficiency of the multilink setup.

[0189] The above describes in detail the method provided in this application. In order to facilitate the implementation of the above solutions in the embodiments of this application, the embodiments of this application further provide a corresponding apparatus or device.

[0190] In this application, the AP MLD and the non-AP MLD are divided into functional modules based on the embodiment of the method. For example, each functional module may be obtained through division based on the corresponding function, or two or more functions may be integrated into one processing module. The integrated module may be realized in the form of hardware, or in the form of a software functional module. It should be noted that in this application, the division into modules is an example, and is merely a logical division of functions. In the actual implementation, other division methods may be used. Hereinafter, the AP MLD and the non-AP MLD in the embodiment of this application will be described in detail with reference to FIG. 9 to FIG. 11.

[0191] 9 is a schematic diagram of a structure of a communication device according to an embodiment of this application. As shown in FIG. 9, the communication device includes: a transceiver unit 10 and a processing unit 20.

[0192] In some embodiments of this application, the communication device may be the non-AP MLD described above. In other words, the communication device shown in FIG. 9 may be configured to perform the steps, functions, etc. performed by the non-AP MLD in the method embodiments. For example, the communication device may be a non-AP MLD, chip, etc. This is not limited to this embodiment of this application.

[0193] In one design, the transceiver unit 10 is configured to transmit a first association request frame on a first link and receive a first association response frame on the first link, the first association request frame including a multilink element, the multilink element including indication information, the indication information indicating a second link, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field, the first status code field having a value non-zero to indicate that the first link is not acceptable, and the second status code field being set to a first value non-zero to indicate that the second link is not acceptable due to the first link being unacceptable.

[0194] For example, the processing unit 20 is configured to generate a first association request frame and to use or control the transceiver unit 10 to transmit the first association request frame.

[0195] In a possible implementation, the transceiver unit 10 is further configured to transmit a second association request frame on the second link and to receive a second association response frame on the second link.

[0196] For example, the processing unit 20 is configured to generate a second association request frame and to use or control the transceiver unit 10 to transmit the second association request frame.

[0197] It can be understood that for specific descriptions of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., please refer to the embodiments of the method. Details will not be described again here.

[0198] It can be understood that the specific description of the transceiver unit and the processing unit in this embodiment of this application is merely an example. For the specific functions or steps performed by the transceiver unit and the processing unit, please refer to the embodiment of the method (as shown in FIG. 4). The details will not be described again here.

[0199] In another design, transceiver unit 10 is configured to transmit a first association request frame on the first link and receive a first association response frame on the first link, where the first association request frame includes a multilink element, where the multilink element includes indication information, where the indication information indicates a second link, where the first association response frame includes a first status code field and a multilink element, where the multilink element of the first association response frame includes a second status code field, where the first status code field has a value non-zero and the second status code field has a value 0 to jointly indicate that the second link is not acceptable due to the first link being unacceptable.

[0200] For example, the processing unit 20 is configured to generate a first association request frame and to use or control the transceiver unit 10 to transmit the first association request frame.

[0201] In a possible implementation, the transceiver unit 10 is further configured to transmit a second association request frame on the second link and to receive a second association response frame on the second link.

[0202] For example, the processing unit 20 is configured to generate a second association request frame and to use or control the transceiver unit 10 to transmit the second association request frame.

[0203] It can be understood that for specific descriptions of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., please refer to the embodiments of the method. Details will not be described again here.

[0204] It can be understood that the specific description of the transceiver unit and the processing unit in this embodiment of this application is merely an example. For the specific functions or steps performed by the transceiver unit and the processing unit, please refer to the embodiment of the method (as shown in FIG. 7). The details will not be described again here.

[0205] In yet another design, the transceiver unit 10 is configured to transmit a first association request frame on the first link and receive a first association response frame on the first link, the first association request frame including a multilink element, the multilink element including indication information, the indication information indicating a second link, the first association response frame including a first status code field, the first status code field set to a second non-zero value to indicate that multilink setup between the non-AP MLD and the AP MLD has failed and that multilink setup may be successful if the association request frame is transmitted on the other requested link.

[0206] For example, the processing unit 20 is configured to generate a first association request frame and to use or control the transceiver unit 10 to transmit the first association request frame.

[0207] In a possible implementation, the transceiver unit 10 is further configured to transmit a second association request frame on the second link and to receive a second association response frame on the second link.

[0208] For example, the processing unit 20 is configured to generate a second association request frame and to use or control the transceiver unit 10 to transmit the second association request frame.

[0209] It can be understood that for specific descriptions of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., please refer to the embodiments of the method. Details will not be described again here.

[0210] It can be understood that the specific description of the transceiver unit and the processing unit in this embodiment of this application is merely an example. For the specific functions or steps performed by the transceiver unit and the processing unit, please refer to the embodiment of the method (as shown in FIG. 8). The details will not be described again here.

[0211] Continue to refer to FIG. 9. In some other embodiments of this application, the communication device may be the AP MLD described above. In other words, the communication device shown in FIG. 9 may be configured to perform the steps, functions, etc. performed by the AP MLD in the method embodiments. For example, the communication device may be an AP MLD, a chip, etc. This is not limited to this embodiment of this application.

[0212] In one design, transceiver unit 10 is configured to receive a first association request frame on a first link and transmit a first association response frame on the first link, where the first association request frame includes a multilink element, where the multilink element includes indication information, where the indication information indicates a second link, where the first association response frame includes a first status code field and a multilink element, where the multilink element of the first association response frame includes a second status code field, where the value of the first status code field is non-zero to indicate that the first link is not acceptable, and where the second status code field is set to a first non-zero value to indicate that the second link is not acceptable due to the first link being unacceptable.

[0213] For example, the processing unit 20 is configured to generate a first association response frame and to use or control the transceiver unit 10 to transmit the first association response frame.

[0214] In a possible implementation, the transceiver unit 10 is further configured to receive a second association request frame on the second link and to transmit a second association response frame on the second link.

[0215] For example, the processing unit 20 is configured to generate a second association response frame and to use or control the transceiver unit 10 to transmit the second association response frame.

[0216] It can be understood that for specific descriptions of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., please refer to the embodiments of the method. Details will not be described again here.

[0217] It can be understood that the specific description of the transceiver unit and the processing unit in this embodiment of this application is merely an example. For the specific functions or steps performed by the transceiver unit and the processing unit, please refer to the embodiment of the method (as shown in FIG. 4). The details will not be described again here.

[0218] In another design, transceiver unit 10 is configured to receive a first association request frame on the first link and transmit a first association response frame on the first link, where the first association request frame includes a multilink element, where the multilink element includes indication information, where the indication information indicates a second link, where the first association response frame includes a first status code field and a multilink element, where the multilink element of the first association response frame includes a second status code field, where the first status code field has a value non-zero and the second status code field is zero to jointly indicate that the second link is not acceptable due to the first link being unacceptable.

[0219] For example, the processing unit 20 is configured to generate a first association response frame and to use or control the transceiver unit 10 to transmit the first association response frame.

[0220] In a possible implementation, the transceiver unit 10 is further configured to receive a second association request frame on the second link and to transmit a second association response frame on the second link.

[0221] For example, the processing unit 20 is configured to generate a second association response frame and to use or control the transceiver unit 10 to transmit the second association response frame.

[0222] It can be understood that for specific descriptions of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., please refer to the embodiments of the method. Details will not be described again here.

[0223] It can be understood that the specific description of the transceiver unit and the processing unit in this embodiment of this application is merely an example. For the specific functions or steps performed by the transceiver unit and the processing unit, please refer to the embodiment of the method (as shown in FIG. 7). The details will not be described again here.

[0224] In yet another design, the transceiver unit 10 is configured to receive a first association request frame on the first link and transmit a first association response frame on the first link, where the first association request frame includes a multilink element, where the multilink element includes indication information, where the indication information indicates a second link, and where the first association response frame includes a first status code field, where the first status code field is set to a second non-zero value to indicate that multilink setup between the non-AP MLD and the AP MLD has failed and that multilink setup may be successful if the association request frame is transmitted on the other requested link.

[0225] For example, the processing unit 20 is configured to generate a first association response frame and to use or control the transceiver unit 10 to transmit the first association response frame.

[0226] In a possible implementation, the transceiver unit 10 is further configured to receive a second association request frame on the second link and to transmit a second association response frame on the second link.

[0227] For example, the processing unit 20 is configured to generate a second association response frame and to use or control the transceiver unit 10 to transmit the second association response frame.

[0228] It can be understood that for specific descriptions of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., please refer to the embodiments of the method. Details will not be described again here.

[0229] It can be understood that the specific description of the transceiver unit and the processing unit in this embodiment of this application is merely an example. For the specific functions or steps performed by the transceiver unit and the processing unit, please refer to the embodiment of the method (as shown in FIG. 8). The details will not be described again here.

[0230] The above describes the non-AP MLD and AP MLD in the embodiment of this application, and the following describes the possible product forms of the non-AP MLD and AP MLD. It should be understood that any product of any type having the function of the non-AP MLD described in Figure 9 and any product of any type having the function of the AP MLD described in Figure 9 fall within the protection scope of the embodiment of this application. It should be further understood that the following description is merely an example and does not limit the product forms of the non-AP MLD and AP MLD in this embodiment of this application.

[0231] In a possible implementation manner, in the communication device shown in FIG. 9, the processing unit 20 may be one or more processors, and the transceiver unit 10 may be a transceiver. Alternatively, the transceiver unit 10 may be a transmitting unit and a receiving unit, the transmitting unit may be a transmitter, and the receiving unit may be a receiver. The transmitting unit and the receiving unit are integrated into one component, for example, a transceiver. In this embodiment of the application, the processor and the transceiver may be combined, etc. The connection manner between the processor and the transceiver is not limited in this embodiment of the application. In the process of executing the method, the process of transmitting information in the method (for example, transmitting a first association request frame, a first association response frame, a second association request frame, or a second association response frame) may be understood as a process of the processor outputting information. When outputting information, the processor outputs the information to the transceiver, so that the transceiver transmits the information. After the information is output by the processor, other processing may need to be further performed on the information before the information arrives at the transceiver. Similarly, the process of receiving information in the method (e.g., receiving a first association request frame, a first association response frame, a second association request frame, or a second association response frame) may be understood as a process of the processor receiving input information. When the processor receives the input information, the transceiver receives the information and inputs the information to the processor. Furthermore, after the transceiver receives the information, other processing may need to be performed on the information before the information is input to the processor.

[0232] Fig. 10 is a schematic diagram of the structure of a communication device 1000 according to an embodiment of this application. The communication device 1000 may be a first communication device, a second communication device or a chip thereof. Fig. 10 shows only the main components of the communication device 1000. In addition to the processor 1001 and the transceiver 1002, the communication device may further include a memory 1003 and an input / output device (not shown in the drawing).

[0233] The processor 1001 is primarily configured to process communication protocols and communication data, control communication devices, execute software programs, and process data of the software programs. The memory 1003 is primarily configured to store software programs and data. The transceiver 1002 may include a control circuit and an antenna. The control circuit is primarily configured to perform conversion between baseband signals and radio frequency signals, and process the radio frequency signals. The antenna is primarily configured to receive and transmit the radio frequency signals in the form of electromagnetic waves. The input / output device, such as a touch screen, a display, or a keyboard, is primarily configured to receive data entered by a user and output data to a user.

[0234] After the communication device is powered on, the processor 1001 may read the software program in the memory 1003, interpret and execute the instructions of the software program, and process data of the software program. When data needs to be transmitted wirelessly, the processor 1001 performs baseband processing on the data to be transmitted, and then outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal, and then transmits the radio frequency signal in the form of an electromagnetic wave through an antenna. When data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1001. The processor 1001 converts the baseband signal into data and processes the data.

[0235] In other implementations, the radio frequency circuitry and antenna may be located separately from the processor performing the baseband processing, for example in a distributed scenario, the radio frequency circuitry and antenna may be located separately from the communication device.

[0236] The processor 1001, the transceiver 1002 and the memory 1003 may be connected via a communication bus.

[0237] In one design, the communication device 1000 may be configured to perform the functionality of the non-AP MLD in embodiment 1. The processor 1001 may be configured to generate a first association request frame transmitted in step S101 and a second association request frame transmitted in step S103 in FIG. 4, and / or perform other processes for performing the techniques described herein. The transceiver 1002 may be configured to perform steps S101, S103, etc. in FIG. 4, and / or perform other processes for the techniques described herein.

[0238] In another design, the communication device 1000 may be configured to perform the function of the AP MLD in the first embodiment. The processor 1001 may be configured to generate the first association response frame transmitted in step S102 and the second association response frame transmitted in step S104 in FIG. 4, and / or perform other processes for performing the techniques described in this specification. The transceiver 1002 may be configured to generate the first association response frame transmitted in step S102 and the second association response frame transmitted in step S104 in FIG. 4, and / or perform other processes for performing the techniques described in this specification. 4 10 and / or other processes of the techniques described herein.

[0239] In one design, the communications device 1000 may be configured to perform the functionality of non-AP MLD in embodiment 2. The processor 1001 may be configured to generate a first association request frame transmitted in step S201 and a second association request frame transmitted in step S203 in FIG. 7, and / or perform other processes for performing the techniques described herein. The transceiver 1002 may be configured to perform steps S201, S203, etc. in FIG. 7, and / or perform other processes for the techniques described herein.

[0240] In another design, the communication device 1000 may be configured to perform the function of the AP MLD in embodiment 2. The processor 1001 may be configured to generate a first association response frame transmitted in step S202 and a second association response frame transmitted in step S204 in FIG. 7, and / or perform other processes for performing the techniques described in this specification. The transceiver 1002 may be configured to perform steps S202 and S204 in FIG. 7, and / or perform other processes for the techniques described in this specification.

[0241] In one design, the communications device 1000 may be configured to perform the functionality of the non-AP MLD in embodiment 3. The processor 1001 may be configured to generate a first association request frame transmitted in step S301 and a second association request frame transmitted in step S303 in FIG. 8, and / or perform other processes for performing the techniques described herein. The transceiver 1002 may be configured to perform steps S301, S303, etc. in FIG. 8, and / or perform other processes for the techniques described herein.

[0242] In another design, the communication device 1000 may be configured to perform the function of the AP MLD in embodiment 3. The processor 1001 may be configured to generate a first association response frame transmitted in step S302 and a second association response frame transmitted in step S304 in FIG. 8, and / or perform other processes for performing the techniques described in this specification. The transceiver 1002 may be configured to perform steps S302 and S304 in FIG. 8, and / or perform other processes for the techniques described in this specification.

[0243] In any one of the above designs, the processor 1001 may include a transceiver configured to realize the transmitting and receiving functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, the interface, or the interface circuit configured to realize the receiving and transmitting functions may be separate or integrated together. The transceiver circuit, the interface, or the interface circuit may be configured to read and write code / data. Alternatively, the transceiver circuit, the interface, or the interface circuit may be configured to transmit or forward a signal.

[0244] In any one of the above designs, the processor 1001 may store instructions. The instructions may be computer programs. The computer programs execute on the processor 1001, thereby enabling the communication device 1000 to perform the methods described in the above method embodiments. The computer programs may be fixed to the processor 1001, in which case the processor 1001 may be implemented in hardware.

[0245] In an implementation, the communication device 1000 may include circuits, which may implement the transmitting, receiving or communication functions in the above method embodiments. The processors and transceivers described in this application may be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFIC), a mixed signal IC, an application-specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processors and transceivers may alternatively be fabricated using various IC technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe) and gallium arsenide (GaAs).

[0246] The scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited to that of FIG. 10. The communication device may be a separate device or may be part of a larger device. For example, the communication device may be: (1) An independent integrated circuit IC, chip, or chip system or subsystem (2) A set including one or more ICs, optionally the set of ICs may further include a storage component configured to store data and computer programs. (3) ASICs such as modems (4) A module that can be incorporated into other devices (5) Receivers, terminals, intelligent terminals, mobile phones, wireless devices, handheld devices, mobile units, in-vehicle devices, network devices, cloud devices, artificial intelligence devices, etc.; (6)Other

[0247] In another possible implementation manner, in the communication device shown in FIG. 9, the processing unit 20 may be one or more logic circuits, and the transceiver unit 10 may be an input / output interface, or may be called a communication interface, an interface circuit, an interface, etc. Alternatively, the transceiver unit 10 may be a transmitting unit and a receiving unit. The transmitting unit may be an output interface, and the receiving unit may be an input interface. The transmitting unit and the receiving unit are integrated into one unit, for example, an input / output interface. FIG. 11 is a schematic diagram of another structure of a communication device according to an embodiment of this application. As shown in FIG. 11, the communication device shown in FIG. 11 includes a logic circuit 901 and an interface 902. In other words, the processing unit 20 may be realized by using the logic circuit 901, and the transceiver unit 10 may be realized by using the interface 902. The logic circuit 901 may be a chip, a processing circuit, an integrated circuit, a system on chip (SoC) chip, etc. The interface 902 may be a communication interface, an input / output interface, a pin, etc. 11 shows an example in which the communication device is used as a chip. The chip includes a logic circuit 901 and an interface 902.

[0248] In this embodiment of the present application, the logic circuit may be further coupled to an interface. The specific connection manner of the logic circuit and the interface is not limited in this embodiment of the present application.

[0249] For example, when the communication device is configured to perform the method, function, or step performed by the non-AP MLD in embodiment 1, embodiment 2, or embodiment 3, the logic circuit 901 is configured to generate a first association request frame. The interface 902 is configured to output the first association request frame. The interface 902 is further configured to input a first association response frame.

[0250] For example, when the communication device is configured to perform the method, function, or step performed by the AP MLD in embodiment 1, embodiment 2, or embodiment 3, the interface 902 is configured to input a first association request frame. The logic circuit 901 is configured to generate a first association response frame. The interface 902 is further configured to output the first association response frame.

[0251] It can be understood that for specific descriptions of the first association request frame, the first association response frame, etc., please refer to the method embodiments, and the details will not be described again here.

[0252] It can be understood that the communication device shown in this embodiment of this application may implement the method provided in the embodiment of this application in the form of hardware or software, which is not limited to the embodiment of this application.

[0253] For the specific implementation of the embodiment shown in Figure 11, please refer to the above embodiment, and the details will not be described again here.

[0254] An embodiment of the present application further provides a wireless communication system. The wireless communication system includes a non-AP MLD and an AP MLD, and the non-AP MLD and the AP MLD may be configured to perform the method in any one of the above embodiments.

[0255] Additionally, this application further provides a computer program, the computer program being configured to implement the operations and / or processes performed by the non-AP MLD in the methods provided in this application.

[0256] This application further provides a computer program, configured to implement the operations and / or processes performed by the AP MLD in the methods provided in this application.

[0257] This application further provides a computer-readable storage medium, which stores computer code that, when executed on a computer, enables the computer to perform the actions and / or processes performed by a non-AP MLD in the methods provided in this application.

[0258] This application further provides a computer-readable storage medium, which stores computer code, which when executed on a computer, enables the computer to perform the actions and / or processes performed by the AP MLD in the methods provided in this application.

[0259] This application further provides a computer program product, which includes computer code or a computer program that, when executed on a computer, performs the operations and / or processes performed by a non-AP MLD device in the methods provided in this application.

[0260] This application further provides a computer program product, which includes computer code or a computer program, which, when executed on a computer, performs the operations and / or processes performed by the AP MLD in the methods provided in this application.

[0261] In some embodiments provided in this application, it should be understood that the disclosed system, device, and method may be realized in other ways. For example, the described device embodiment is merely an example. For example, the division into units is merely a logical division of functions, and may be divided in other ways in actual implementation. For example, multiple units or components may be combined or integrated into other systems, or some features may be ignored or not implemented. Furthermore, the shown or discussed mutual couplings or direct couplings or communication connections may be realized through some interfaces, indirect couplings or communication connections between devices or units, or electrical connections, mechanical connections, or other types of connections.

[0262] The units described as separate parts may or may not be physically separate, and the parts shown as units may or may not be physical units, and may be located in one place or distributed among multiple network units. Some or all of the units may be selected based on actual requirements to achieve the technical effects of the solutions provided in the embodiments of this application.

[0263] Furthermore, the functional units in the embodiments of this application may be integrated into one processing unit, each of the units may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be realized in the form of hardware or in the form of a software functional unit.

[0264] When the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of this application may be essentially realized, or the part contributing to the prior art or all or part of the technical solution may be realized in the form of a software product. The computer software product is stored in a readable storage medium and includes some instructions for instructing a computer device (which may be a personal computer, a server, a network device, etc.) to execute all or part of the steps of the method described in the embodiments of this application. The readable storage medium includes any medium that can store program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0265] The above description is merely a specific implementation of this application, and is not intended to limit the scope of protection of this application. Any variations or replacements that are easily conceived by those skilled in the art within the technical scope disclosed in this application shall fall within the scope of protection of this application. Therefore, the scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. A multi-link communication setting method, comprising: transmitting a first association request frame on a first link by a first station of a non-access point multilink device (non-AP MLD), the first association request frame including a multilink element, the multilink element including indication information, the indication information indicating a second link different from the first link; receiving a first association response frame on the first link by the first station in the non-AP MLD, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field; Including, the value of the first status code field is non-zero to indicate that the first link is unacceptable, and the second status code field is set to a first non-zero value to indicate that the second link is unacceptable solely because the first link is unacceptable.

2. 2. The method of claim 1, wherein the first status code field is a status code field located outside the multilink element of the first association response frame.

3. The method of claim 1 , wherein the second status code field is a status code field included in a STA profile subfield of a Per-STA profile subelement.

4. After receiving a first association response frame on the first link by the first station in the non-AP MLD, the method includes: transmitting a second association request frame on the second link by a second station in the non-AP MLD; receiving a second association response frame on the second link by the second station in the non-AP MLD; The method of claim 1 further comprising:

5. A multi-link communication setting method, comprising: receiving a first association request frame on a first link by a first access point of an access point multilink device (AP MLD), the first association request frame including a multilink element, the multilink element including indication information, the indication information indicating a second link different from the first link; transmitting a first association response frame on the first link by the first access point of the AP MLD, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field; Including, the value of the first status code field is non-zero to indicate that the first link is unacceptable, and the second status code field is set to a first non-zero value to indicate that the second link is unacceptable solely because the first link is unacceptable.

6. 6. The method of claim 5, wherein the first status code field is a status code field located outside the multilink element of the first association response frame.

7. The method of claim 5 , wherein the second status code field is a status code field included in a STA profile subfield of a Per-STA profile subelement.

8. After transmitting a first association response frame on the first link by the first access point of the AP MLD, the method includes: receiving a second association request frame on the second link by a second access point in the AP MLD; transmitting a second association response frame on the second link by the second access point in the AP MLD; The method of claim 5 further comprising:

9. 1. A communication device, comprising: The communication device includes a processing unit and a transceiver unit. The processing unit controls the transceiver unit to transmitting a first association request frame on a first link, the first association request frame including a multilink element, the multilink element including indication information, the indication information indicating a second link different from the first link; receiving a first association response frame on the first link, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field; It is configured as follows: A communications device, wherein the value of the first status code field is not 0 to indicate that the first link is not acceptable, and the second status code field is set to a first value other than 0 to indicate that the second link is not acceptable only because the first link is not acceptable.

10. The transceiver unit includes: transmitting a second association request frame on the second link; receiving a second association response frame on the second link The communication device of claim 9 , further configured to:

11. 10. The communication device of claim 9, wherein the first status code field is a status code field located outside the multilink element of the first association response frame.

12. The communications device of claim 9 , wherein the second status code field is a status code field included in a STA profile subfield of a per-STA profile subelement.

13. 1. A communication device, comprising: The communication device includes a processing unit and a transceiver unit. The processing unit controls the transceiver unit to receiving a first association request frame on a first link, the first association request frame including a multilink element, the multilink element including indication information, the indication information indicating a second link different from the first link; transmitting a first association response frame on the first link, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field; It is configured as follows: A communications device, wherein the value of the first status code field is not 0 to indicate that the first link is not acceptable, and the second status code field is set to a first value other than 0 to indicate that the second link is not acceptable only because the first link is not acceptable.

14. The transceiver unit includes: receiving a second association request frame on the second link; Transmitting a second association response frame on the second link. The communication device of claim 13 further configured to:

15. 14. The communication device of claim 13, wherein the first status code field is a status code field located outside the multilink element of the first association response frame.

16. The communications device of claim 13 , wherein the second status code field is a status code field included in a STA profile subfield of a per-STA profile subelement.

17. A communication device including a processor and a memory, The memory is configured to store instructions; A communications device, the processor being configured to execute the instructions to perform a method according to any one of claims 1 to 4.

18. A communication device including a processor and a memory, The memory is configured to store instructions; A communications device, wherein the processor is configured to execute the instructions to perform a method according to any one of claims 5 to 8.

19. A communication device including a logic circuit and an interface, the logic circuit is coupled to the interface; A communications device, wherein the interface is configured to input and / or output code instructions, and the logic circuit is configured to execute the code instructions to perform a method according to any one of claims 1 to 4.

20. A communication device including a logic circuit and an interface, the logic circuit is coupled to the interface; A communications device, wherein the interface is configured to input and / or output code instructions, and the logic circuit is configured to execute the code instructions to perform a method according to any one of claims 5 to 8.

21. 1. A computer-readable storage medium, comprising: The computer-readable storage medium is configured to store a computer program, the computer program being configured to, when executed, perform the method of any one of claims 1 to 4 by a non-access point multilink device (non-AP MLD).

22. 1. A computer-readable storage medium, comprising: The computer-readable storage medium is configured to store a computer program, the computer program being configured to, when executed, perform the method of any one of claims 5 to 8 by an Access Point Multilink Device (AP MLD).

Images