Multilink communication setup method and related devices

Abstract

To provide a multi-link communication setting method for improving the efficiency of multi-link setting.SOLUTION: In a multi-link communication setting method, a non-access point multi-link device (non-AP MLD) transmits an association request frame on a first link to request multi-link setting. An AP MLD replies with an association response frame on the first link to notify whether the multi-link setting is successful, and sets a second status code field of a multi-link element of the association response frame to a newly defined value to indicate that the cause of the link being not acceptable is the first link being not acceptable.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] [Cross - reference to Related Applications] This application claims the priority of Chinese Patent Application No. 202210435613.2, entitled "MULTI - LINK COMMUNICATION SETUP METHOD AND RELATED APPARATUS", filed with the China National Intellectual Property Administration on April 24, 2022, and incorporates its entire content by reference.

[0002] [Technical Field] This application relates to the field of wireless communication technology, and particularly to a multi - link communication setup method and related apparatus.

Background Art

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

[0004] During multilink configuration (or multilink association), a non-AP MLD may send an association request frame to an AP MLD on the link (for ease of explanation, the link is shown as the first link). The association request frame carries a multi-link element (MLE) used to carry information about the non-AP MLD and information about other links in the non-AP MLD. The association request frame is used to request the establishment of multilink 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 multilink communication has been successfully established. The association response frame may also carry an MLE used to carry information about the AP MLD and information about other links in the AP MLD.

[0005] According to the multilink configuration rules, if the first link is unacceptable (or fails to configure), the other links cannot be accepted (or cannot be configured successfully). When the first link is unacceptable, the non-AP MLD does not know whether it will succeed in sending an association request frame on the other links to request the establishment of multilink communication with the AP MLD. As a result, the non-AP MLD can only send an association request frame on each link in an attempt to establish multilink communication with the AP MLD, which leads to low efficiency in multilink configuration. [Overview of the project]

[0006] Embodiments of this application provide a multilink communication configuration method and related apparatus for improving the efficiency of multilink configuration (or multilink association).

[0007] The present invention will be described below in terms of different embodiments. It should be understood that cross-referencing may be made to the following implementations and beneficial effects of the different embodiments.

[0008] According to a first aspect, the application provides a method for setting up multilink communication, the method comprising: a first station of a non-AP MLD transmits a first association request frame over a first link and receives a first association response frame over the first link. The first association request frame includes a multilink element, the multilink element includes instruction information, the instruction information indicates a second link. 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 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 reason the second link is unacceptable is that the first link is unacceptable.

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

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

[0011] Normally, if a link for transmitting an association request frame is not accepted by a non-AP MLD, other links cannot be accepted either. However, the reasons why a link may or may not be accepted can be different. Therefore, when a link for transmitting an association request frame is not accepted by a non-AP MLD, the non-AP MLD does not know whether multilink communication with the AP MLD can be successfully established if the association request frame is transmitted over other links. As a result, the non-AP MLD can only send association request frames on each link in an attempt to establish multilink communication, which leads to low efficiency in multilink setup.

[0012] However, in this application, the first status code field of the association response frame is set to a non-zero value to indicate that the reason the link corresponding to the second status code field is not accepted is that the transmission link is not accepted, or to inform the non-AP MLD that the link may be accepted if the association request frame is sent on the 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 a non-zero first value. Thus, the non-AP MLD may send an association request frame on the link for multilink setup to improve the probability of successful multilink setup. Furthermore, the non-AP MLD does not need to attempt to set up multilink communication on each link to reduce the number of attempts and improve the efficiency of multilink setup.

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

[0014] In this application, when an association request frame is sent on a link corresponding to a 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 multilink element of the first association response frame is set to a non-zero first value, in order to inform a non-AP MLD that the link may be accepted (or successfully configured). Thus, a non-AP MLD can know which link the association request frame is sent on, with a high probability of successfully configuring multilink communication. This can improve the probability of successful multilink configuration, reduce the number of attempts, and improve the efficiency of multilink configuration.

[0015] According to a second aspect, the application provides a method for setting up multilink communication, the method comprising: a first access point of AP MLD receiving a first association request frame on a first link and transmitting a first association response frame on the first link; the first association request frame includes a multilink element, the multilink element includes instruction information, the instruction information indicates a second link; 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 value of the first status code field is non-zero to indicate that the first link is not accepted, and the second status code field is set to a first non-zero value to indicate that the reason the second link is not accepted is that the first link is not accepted.

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

[0017] Referring to the second aspect, in a possible implementation, after the first access point of the AP MLD transmits 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 transmits a second association response frame on the second link.

[0018] In any one of the possible implementations described above, the first value may be a value that is not used or is not defined in the existing Status Code field, or the first value may be a value other than the existing values, such as 0 to (2 n It is one of the values ​​of -1). n indicates the length of the status code field. Existing values ​​include, but are not limited to, values ​​from 0 to 135, or values ​​from 0 to 135 other than the reserved values ​​(4, 8, 9, 20, 21, 26, 29, 36, 48, 66, 69-71, 90, 91, 114, 115, 127).

[0019] In any one of the possible implementations described above, the first status code field is located in the 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 either 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 any one of the possible implementations described above, the second status code field is located in the 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 application provides a communication device, specifically a non-AP MLD or a chip within a non-AP MLD, wherein the communication device is configured to perform a method in either the first aspect or a possible implementation of the first aspect. The communication device includes a unit configured to perform a method in either the first aspect or a possible implementation of the first aspect.

[0022] According to a fourth aspect, the application provides a communication device, specifically an AP MLD or a chip within an AP MLD, the communication device being configured to perform a method in either the second aspect or a possible implementation of the second aspect. The communication device includes a unit configured to perform a method in either the second aspect or a possible implementation of the second aspect.

[0023] In the third or fourth embodiment, the communication device may include a transceiver unit and a processing unit. For a specific description of the transceiver unit and the processing unit, refer to the embodiments of the device shown below. For the beneficial effects of the third and fourth embodiments, refer to the relevant descriptions of the first and second embodiments. Further details will not be explained again here.

[0024] According to a fifth aspect, this application provides a multi-link communication setting method. The method includes the following. 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. In order to jointly indicate that the reason why the second link cannot be accepted is that the first link cannot be accepted, the first status code field is set to a value indicating that the first link cannot be accepted or a value indicating the reason why the first link cannot be accepted (for example, 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 can be accepted (for example, the value of the second status code field is 0).

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

[0026] It can be understood that the value of the first status code field is not 0 in order to indicate that the first status code field does not indicate success, that is, the first link cannot be accepted. When the value of the second status code field is 0, this indicates that the second status code field indicates success, that is, the second link may be accepted.

[0027] In this application, the setting rules and corresponding interpretation rules for 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 reason why the link corresponding to the second status code field cannot be accepted is that the first link cannot be accepted. Therefore, the non-AP MLD knows that there is a high probability that the multi-link setting will succeed when the association request frame is transmitted on the link for multi-link setting. This can improve the probability of successful multi-link setting, reduce the number of attempts, and improve the efficiency of multi-link setting. Furthermore, in order to reduce overhead, there is no need to define new status code values 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 the following. The second station of the non-AP MLD transmits 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 method for setting up multilink communication, the method comprising: a first access point of AP MLD receiving a first association request frame on a first link and transmitting a first association response frame on the first link; the first association request frame includes a multilink element, the multilink element includes instruction information, the instruction information indicates a second link; 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; to jointly indicate that the reason the second link is unacceptable is that the first link is unacceptable, the first status code field is set to a value indicating that the first link is unacceptable or a value indicating the reason why the first link is unacceptable (for example, 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 (for example, the value of the second status code field is 0).

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

[0031] Referring to the sixth aspect, in a possible implementation, after the first access point of the AP MLD transmits 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 transmits a second association response frame on the second link.

[0032] Referring to the fifth or sixth aspect, in possible implementations, the first state code field is located in the frame body of the association response frame. For example, the first state code field is located outside the multilink elements of the association response frame. In other words, the first state code field is either not located in the multilink elements of the association response frame, or it is located in the core frame of the association response frame.

[0033] Referring to the fifth or sixth aspect, in possible implementations, the second status code field is 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 a per-STA profile subelement.

[0034] According to a seventh aspect, the application provides a communication device, specifically a non-AP MLD or a chip within a non-AP MLD, the communication device being configured to perform a method in either the fifth aspect or a possible implementation of the fifth aspect. The communication device includes a unit configured to perform a method in either the fifth aspect or a possible implementation of the fifth aspect.

[0035] According to the eighth aspect, the application provides a communication device, specifically an AP MLD or a chip within an AP MLD, the communication device being configured to perform a method in either the sixth aspect or a possible implementation of the sixth aspect. The communication device includes a unit configured to perform a method in either the sixth aspect or a possible implementation of the sixth aspect.

[0036] In the seventh or eighth embodiment, the communication device may include a transceiver unit and a processing unit. For a specific description of the transceiver unit and the processing unit, refer to the embodiments of the device shown below. For the beneficial effects of the seventh to eighth embodiments, refer to the relevant descriptions of the fifth and sixth embodiments. Further details will not be explained again here.

[0037] According to a ninth aspect, the application provides a method for setting up multilink communication, the method comprising: a first station of a non-AP MLD transmits a first association request frame over a first link and receives a first association response frame over the first link. The first association request frame includes a multilink element, the multilink element includes instruction information, the instruction information indicates a second link. The first association response frame includes a first status code field and a multilink element, the first status code field being set to a second non-zero value to indicate that multilink setting between the non-AP MLD and the AP MLD has failed and that multilink setting may succeed if the association request frame is transmitted over another requested link. The multilink element of the first association response frame includes a second status code field to indicate the reason why the second link is accepted or not accepted.

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

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

[0040] In this embodiment of the application, when a multilink configuration fails but one link exists and an association request frame is transmitted over that link, the first state code field of the association response frame is set to a newly defined value (i.e., a second value) to indicate that a multilink configuration may be successful. Thus, to avoid the high power consumption of the non-AP MLD caused by repeated attempts to configure multilink communication by the non-AP MLD when the probability of successful multilink configuration is low, the non-AP MLD knows whether or not there is a probability of successful multilink configuration with the AP MLD.

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

[0042] According to a tenth aspect, the application provides a method for setting up multilink communication, the method comprising: a first access point of an AP MLD receiving a first association request frame on a first link and transmitting a first association response frame on the first link. The first association request frame includes a multilink element, the multilink element includes instruction information, the instruction information indicates a second link. The first association response frame includes a first status code field and a multilink element, the first status code field being set to a second non-zero value to indicate that multilink setting between a non-AP MLD and an AP MLD has failed and that multilink setting may succeed if the association request frame is transmitted on another requested link. The multilink element of the first association response frame includes a second status code field to indicate the reason why the second link is accepted or not accepted.

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

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

[0045] Referring to the tenth aspect, in a possible implementation, after the first access point of the AP MLD transmits 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 transmits a second association response frame on the second link.

[0046] Referencing the ninth or tenth aspect, in possible implementations, 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 multilink configuration has failed and that the multilink configuration may succeed if the association request frame is transmitted over the link corresponding to the second status code field, or to indicate that the reason the link corresponding to the second status code field is unacceptable is that the first link is unacceptable (or the multilink configuration has failed).

[0047] In this application, to jointly demonstrate that multilink configuration may fail and that it may succeed 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 newly defined value (i.e., a second 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). Thus, a non-AP MLD can know which link the association request frame is transmitted on in order to successfully configure multilink communication. This can improve the probability of successful multilink configuration, reduce the number of attempts, and improve the efficiency of multilink configuration.

[0048] Referring to the ninth or tenth aspect, in possible implementations, the first state code field is located in the frame body of the association response frame. For example, the first state code field is located outside the multilink elements of the association response frame. In other words, the first state code field is either not located in the multilink elements of the association response frame, or it is located in the core frame of the association response frame.

[0049] Referring to the ninth or tenth aspect, in possible implementations, the second status code field is 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 a per-STA profile subelement.

[0050] According to the eleventh aspect, the application provides a communication device, specifically a non-AP MLD or a chip within a non-AP MLD, the communication device being configured to perform a method in either the ninth aspect or a possible implementation of the ninth aspect. The communication device includes a unit configured to perform a method in either the ninth aspect or a possible implementation of the ninth aspect.

[0051] According to a twelfth aspect, the application provides a communication device, specifically an AP MLD or a chip within an AP MLD, the communication device being configured to perform a method in either a tenth aspect or a possible implementation of the tenth aspect. The communication device includes a unit configured to perform a method in either a tenth aspect or a possible implementation of the tenth aspect.

[0052] In the eleventh or twelfth embodiment, the communication device may include a transceiver unit and a processing unit. For a specific description of the transceiver unit and the processing unit, refer to the embodiments of the device shown below. For the beneficial effects of the eleventh and twelfth embodiments, refer to the relevant descriptions of the ninth and tenth embodiments. Further details will not be explained again here.

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

[0054] Referring to the 13th aspect, in possible implementations, the memory is located outside the communication device.

[0055] Referring to the 13th aspect, in possible implementations, the memory is located in the communication device.

[0056] In this application, the processor and memory may be integrated into a single component as an alternative. In other words, the processor and memory may be integrated together as an alternative.

[0057] Referring to the 13th aspect, in possible implementations, the communication device further includes a transceiver configured to receive or transmit frames.

[0058] According to the 14th aspect, the application provides a communication device. The communication device is an AP MLD, which includes a processor configured to perform a method in the second, sixth, and tenth aspects, or any one of the possible implementations of any one of those aspects. Alternatively, the processor is configured to execute a program stored in memory. When the program is executed, a method in the second, sixth, and tenth aspects, or any one of the possible implementations of any one of those aspects is performed.

[0059] Referring to the 14th aspect, in possible implementations, the memory is located outside the second communication device.

[0060] Referring to the 14th aspect, in possible implementations, the memory is located in the second communication device.

[0061] In this application, the processor and memory may be integrated into a single component as an alternative. In other words, the processor and memory may be integrated together as an alternative.

[0062] Referring to the 14th aspect, in possible implementations, the communication device further includes a transceiver configured to receive or transmit frames.

[0063] According to the 15th aspect, the application provides a communication device, the communication device comprising a logic circuit and an interface, the logic circuit being coupled to the interface.

[0064] In a certain design, a logic circuit is configured to generate an association request frame. An interface is configured to output a first association request frame. The first association request frame includes a multilink element, the multilink element includes instruction information, the instruction information indicates 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 value of which is non-zero to indicate that the first link is not accepted, and the value of which is non-zero to indicate that the reason the second link is not accepted is that the first link is not accepted.

[0065] In a certain design, a logic circuit is configured to generate an association request frame. An interface is configured to output a first association request frame. The first association request frame includes a multilink element, the multilink element includes instruction information, and the instruction information indicates 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, and the value of the first status code field is not 0 and the value of the second status code field is 0 to jointly indicate that the reason the second link is not accepted is that the first link is not accepted.

[0066] In a certain design, a 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, which includes instruction information, which indicates 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, and the first status code field is set to a second non-zero value to indicate that the multilink setup between the non-AP MLD and the AP MLD has failed, and that the multilink setup may succeed if the association request frame is transmitted over another requested link. The multilink element of the first association response frame includes a second status code field to indicate the reason why the second link is accepted or not accepted.

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

[0068] 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 instruction information, and the instruction information indicates a second link. The logic circuit is configured to generate a first association response frame. The interface is configured to output 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 value of which is non-zero to indicate that the first link is not accepted, and the value of which is non-zero to indicate that the reason the second link is not accepted is that the first link is not accepted.

[0069] 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 instruction information, and the instruction information indicates a second link. The logic circuit is configured to generate a first association response frame. The interface is configured to output 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, and the value of the first status code field is not 0 and the value of the second status code field is 0 to jointly indicate that the reason the second link is not accepted is that the first link is not accepted.

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

[0071] According to the 17th aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium is configured to store a computer program, and when the computer program is executed on a computer, a method in the first aspect, the fifth aspect, and the ninth aspect, or any one possible implementation of any one of those aspects is performed.

[0072] According to the 18th aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium is configured to store a computer program, and when the computer program is executed on a computer, a method in the second aspect, the sixth aspect, and the tenth aspect, or any one possible implementation of any one of those aspects, is performed.

[0073] According to the 19th aspect, an embodiment of the present application provides a computer program product, the computer program product comprising a computer program or computer code, wherein when the computer program product is executed on a computer, a method in the first aspect, the fifth aspect and the 9th aspect, or any one of the possible implementations of any one of those aspects is performed.

[0074] According to the 20th aspect, an embodiment of the present application provides a computer program product, the computer program product comprising a computer program or computer code, wherein when the computer program product is executed on a computer, a method in the second aspect, the sixth aspect, and the tenth aspect, or any one possible implementation of any one of those aspects, is performed.

[0075] According to the 21st aspect, an embodiment of the present application provides a computer program. When the computer program is executed on a computer, a method in the first aspect, the fifth aspect, and the 9th aspect, or any one of the possible implementations of any one of those aspects is performed.

[0076] According to the 22nd aspect, an embodiment of the present application provides a computer program. When the computer program is executed on a computer, a method in the second aspect, the sixth aspect, and the tenth aspect, or any one of the possible implementations of any one of those aspects is performed.

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

[0078] In this embodiment of the application, when one or more other links in a 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 fails to be configured), the status code field of the association response frame is used to inform the non-AP MLD that the reason one or more other links cannot be 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 if the association request frame is transmitted on one or more other links, one or more other links may be accepted (or successfully configured). Therefore, the non-AP MLD may transmit the association request frame on one or more other links for multilink configuration to improve the probability of successful multilink configuration. Furthermore, the non-AP MLD does not need to attempt to configure multilink communication on each link in order to reduce the number of attempts and improve the efficiency of multilink configuration. [Brief explanation of the drawing]

[0079] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used to illustrate the embodiments are briefly described below. [Figure 1] This is a schematic diagram of the architecture of a wireless communication system according to an embodiment of this application. [Figure 2] This is a schematic diagram of multilink communication according to an embodiment of this application. [Figure 3a] This is a schematic diagram of the structure of a multilink device according to an embodiment of this application. [Figure 3b] This is a schematic diagram of another structure of the multilink device according to the embodiment of this application. [Figure 4]This is a schematic flowchart of the multilink communication setup method according to the embodiment of this application. [Figure 5] This is a schematic diagram of the frame format of a multilink element according to an embodiment of this application. [Figure 6] This is a schematic diagram of the frame format of the association response frame according to the embodiment of this application. [Figure 7] This is another schematic flowchart of the multilink communication setup method according to the embodiment of this application. [Figure 8] This is yet another schematic flowchart of the multilink communication setup method according to an embodiment of this application. [Figure 9] This is a schematic diagram of the structure of a communication device according to an embodiment of the present invention. [Figure 10] This is a schematic diagram of the structure of the communication device 1000 according to the embodiment of this application. [Figure 11] This is a schematic diagram of another structure of the communication device according to the embodiment of this application. [Modes for carrying out the invention]

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

[0081] In this description of the application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. In this specification, the term "and / or" describes only the relationship between related objects and indicates that three relationships may exist. For example, A and / or B may represent the following three cases: that only A exists, that both A and B exist, and that only B exists. Furthermore, "at least one" means one or more, and "plural" means two or more. At least one of the following items(parts) or similar expressions thereof indicates any combination of these items, including either a single item(part) or a combination of 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 this description of the application, terms such as "first" and "second" do not limit the number or order of execution, nor do terms such as "first" and "second" indicate a clear distinction.

[0083] In this application, terms such as “example” or “for example” are used to indicate that an example, illustration, or explanation is being given. No embodiment or design described by the use of “example” or “for example” in this application should be construed as being preferable to or having more advantages than other embodiments or design methods. More precisely, the use of terms such as “example,” “for example,” and “for example” is intended to present the relevant concepts in a particular manner.

[0084] In this application, elements expressed in the singular form are intended to represent "one or more," but not "unique" unless otherwise specified.

[0085] A multilink device may include multiple logical stations, each operating on a link, but multiple logical stations are permitted to operate on the same link. During data transmission between an AP MLD and a non-AP MLD, a link identifier may be used to identify the link or the stations on the link. Prior to 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 stations 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 stations on the link. This reduces signaling overhead and improves transmission efficiency.

[0086] Optionally, a multilink device may implement wireless communication compliant with the 802.11 series protocols. For example, an extremely high throughput (EHT) compliant station, an 802.11be compliant station, or an 802.11be compatible station may communicate with other devices. It is clear that these other devices may or may not be multilink devices.

[0087] The methods provided in this application may be applied to wireless local area network (WLAN) systems, such as Wi-Fi. The methods provided in this application are applicable to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series protocols, such as 802.11ax, the next-generation Wi-Fi protocol, such as 802.11be, Wi-Fi 7, or extremely high throughput (EHT), and the next-generation 802.11be, i.e., Wi-Fi 8. Other cases are not listed. The methods provided in this application may be further applied to ultra-wideband (UWB) based wireless personal area network systems or sensing systems.

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

[0089] Figure 1 is a schematic diagram of the architecture of a wireless communication system according to an embodiment of this application. As shown in Figure 1, the wireless communication system includes at least one AP MLD (e.g., AP MLD100 and AP MLD200 in Figure 1) and at least one non-AP MLD (e.g., non-AP MLD300 in Figure 1). Optionally, in Figure 1, the wireless communication system may further include a conventional station (e.g., also called STA400, single-link non-AP STA400 in Figure 1) that supports transmission over a single link only. 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 over multiple links to improve throughput. The STA in the non-AP MLD may also communicate with the AP in the AP MLD over a link. In Figure 1, it is used as an example that the non-AP MLD is a mobile phone and the AP MLD is a router, and it can be understood that this application does not limit the types of AP MLDs and non-AP MLDs. The number of AP MLDs and non-AP MLDs in Figure 1 are merely examples, and it can be further understood that there may be more or fewer AP MLDs or non-AP MLDs in a wireless communication system. This is not limited to this application.

[0090] In 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, Figure 2 is a schematic diagram of multilink communication according to an embodiment of this application. As shown in Figure 2, the AP MLD includes n stations, i.e., AP1, AP2, ..., and APn. The non-AP MLD also includes n stations, i.e., STA1, STA2, ..., and STAn. Communication between MLDs is multilink communication. Links 1 to n in Figure 2 form a multilink. In other words, the AP MLD and the non-AP MLD may perform parallel communication on links 1, 2, ..., and n. The APs in the AP MLD may establish association relationships with the STAs in the non-AP MLD. For example, STA1 in the non-AP MLD establishes an association relationship with AP1 in the AP MLD. STA2 in the non-AP MLD establishes an association relationship with AP2 in the AP MLD. STAn in the non-AP MLD establishes an association relationship with APn in the AP MLD.

[0092] Optionally, Figure 3a is a schematic diagram of the structure of a multilink 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) layers within a multilink device. As shown in Figure 3a, the multiple STAs included in the multilink device are independent of each other in the low MAC and PHY layers, and also independent of each other in the high MAC layer. Figure 3b is a schematic diagram of another structure of a multilink device according to an embodiment of this application. As shown in Figure 3b, the multiple STAs included in the multilink device are independent of each other in the low MAC and PHY layers, and share a high MAC layer. Clearly, in a multilink communication process, a non-AP MLD may use a structure in which the high MAC layers are independent of each other, while an AP MLD may use a structure in which the high MAC layers are shared. Alternatively, a non-AP MLD may use a structure in which the high MAC layers are shared, while an AP MLD may use a structure in which the high MAC layers are independent of each other. Alternatively, both the non-AP MLD and the AP MLD may use a structure in which the high MAC layer is shared. Alternatively, both the non-AP MLD and the AP MLD may use a structure in which the high MAC layers are independent of each other. Schematic diagrams of the internal structure of the multilink device are not limited to this embodiment of this application. Figures 3a and 3b are merely illustrative examples. For example, the high MAC layer or the low MAC layer may be implemented by one processor in the chip system of the multilink device, or by different processing modules in the chip system.

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

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

[0095] For example, a multilink device (which may be a non-AP MLD or an AP MLD) is a device having wireless communication capabilities. This device may be an entire system device, or a chip, processing system, etc., installed within an entire system device. A device with a chip or processing system installed may implement the methods and functions of the embodiments of this application under the control of the chip or processing system. For example, in the embodiments of this application, a non-AP MLD may have wireless transceiver capabilities, support 802.11 series protocols, and communicate with an AP MLD, a single-link device, or another non-AP MLD. For example, a non-AP MLD is a user communication device that enables a user to communicate with an AP and / or a WLAN. For example, a non-AP MLD may be a user device that can connect to a network, such as a tablet computer, desktop computer, laptop computer, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), mobile phone, Internet of Things node in the Internet of Things, or in-vehicle communication device in the Internet of Vehicles. The non-AP MLD may, as an alternative, be a chip and processing system in the above-mentioned terminal. The AP MLD may be a device that provides services for the non-AP MLD and may support the 802.11 series protocol. For example, the AP MLD may be a communication entity such as a communication server, router, switch, or bridge, or the AP MLD may include various forms of macro base stations, micro base stations, relay stations, etc. Obviously, the AP MLD may, as an alternative, be a chip and processing system in various forms of devices. Thus, the methods and functions of the embodiments of this application are realized. The 802.11 protocol may support 802.11be or may be a protocol compatible with 802.11be.

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

[0097] This application provides a multilink communication configuration method and related apparatus for improving the efficiency of multilink configuration (or multilink association).

[0098] Typically, a non-AP MLD may simultaneously establish associations with multiple links in an AP MLD by performing a multi-link setup on a single 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 explanation, the link is shown as the first link). The multi-link element carries information about the other links in order to request the establishment of multi-link communication with the AP MLD. After receiving the association request frame, the AP MLD sends back an association response frame carrying the multi-link element on the first link to the non-AP MLD to inform it whether the multi-link communication setup was successful.

[0099] Normally, in a non-AP MLD, if the link for transmitting association request frames (i.e., the first link) is not accepted (or the first link fails to configure), then other links in the non-AP MLD cannot be accepted (or the other links fail to configure). However, the reasons why a link is accepted or not accepted (or whether a link is configured successfully or fails to configure) can differ. For example, the load on different links can differ. If a link is heavily loaded, it may not be accepted (or the link may fail to configure). For example, the capabilities of non-AP MLDs on different links can differ. If the capabilities of non-AP MLDs on a link are weak, the link may not be accepted (or the link may fail to configure). As a result, the following may occur: In a non-AP MLD, when the link for transmitting association request frames (i.e., the first link) is not accepted (or fails to configure), one or more other links may be accepted (or successfully configured). However, since the first link is unacceptable (or fails to configure), one or more other links cannot be accepted (or fail to configure). Therefore, when a non-AP MLD cannot accept (or fails to configure) a link for transmitting an association request frame, the non-AP MLD does not know whether multilink communication with the AP MLD can be successfully configured if the association request frame is sent over another link. As a result, the non-AP MLD can only send an association request frame on each link in an attempt to configure multilink communication, which leads to low efficiency in multilink configuration.

[0100] However, in this embodiment of the application, when one or more other links in a 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 fails to be configured), the status code field of the association response frame is used to inform the non-AP MLD that the reason one or more other links cannot be 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 if the association request frame is transmitted on one or more other links, one or more of the other links may be accepted (or successfully configured). Thus, the non-AP MLD may transmit the association request frame on one or more other links for multilink configuration to improve the probability of successful multilink configuration. Furthermore, the non-AP MLD does not need to attempt to configure multilink communication on each link in order to reduce the number of attempts and improve the efficiency of multilink configuration.

[0101] Since association request frames and association response frames are transmitted over the same link, it can be understood that the “link for transmitting association request frames” as referred to in this application is also the “link for transmitting association response frames.” The “other links” as referred to in this application are links other than the “link for transmitting association request frames” in non-AP MLDs.

[0102] The technical solutions provided in this application will be described in detail below with reference to more attached drawings.

[0103] To clearly illustrate the technical solutions in this application, this application is described by using multiple embodiments. See below for details. In this application, unless otherwise specified, the same or similar parts of embodiments or implementations refer to one another. In the embodiments and implementations / methods in embodiments of this application, unless otherwise specified or unless a logical inconsistency arises, the terminology and / or descriptions are consistent and may refer to one another between different embodiments and between implementations / methods in embodiments. The technical features and implementations / methods in different embodiments may be combined to form new embodiments, implementations or methods based on their internal logical relationships. The following implementations in this application are not intended to limit the scope of protection of this application.

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

[0105] Figure 4 is a schematic flowchart of a multilink communication setup method according to an embodiment of this application. As shown in Figure 4, the multilink communication setup method includes, but is not limited to, the following steps.

[0106] S101: The first station of the non-AP MLD transmits a first association request frame on the first link, the first association request frame includes a multilink element, the multilink element includes instruction information, and the instruction information indicates the second link.

[0107] Accordingly, the first access point of the AP MLD receives the 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 to this embodiment of the application.

[0109] Optionally, the first station is any station in a non-AP MLD, and the first link is the link on which the first station operates. Specifically, a station in a non-AP MLD (i.e., the first station in this embodiment of this application) may transmit an association request frame (i.e., the first link in this embodiment of this application) over a link (i.e., the first link in this embodiment of this application). To request the establishment of multilink communication with the AP MLD, the association request frame carries a multi-link element (MLE), and the multi-link element carries information about another link (hereinafter referred to as the second link). For the specific frame format and function of the first association request frame, refer to the description in existing standards. Further details are not described in this embodiment of this application.

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

[0111] Optionally, instruction information is carried in the STA control field of the per-STA profile subelement of the multilink element. For example, instruction information may also be in the 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 values ​​and meanings of the link ID subfields should be referred to in existing standards. Further details are not provided here.

[0112] Figure 5 is a schematic diagram of the frame format of a multilink element according to an embodiment of this application. As shown in Figure 5, the multilink element includes, but is not limited to, a Multi-Link Control field, a Common Info field, and a Link Info field. The Multi-Link Control field carries the type of the multilink element and indicator information showing which fields are present and absent in the Common Info field. The Common Info field carries information about the multilink device (MLD-level information, i.e., MLD-level info) and common information for multiple stations of the multilink device. The Link Info field carries information about stations on each link within the multilink device. For the specific meaning of each field of the multilink element, it is understandable to refer to the descriptions in existing standards. Details are not described here. It is further understandable that Figure 5 shows only some of the fields of the multilink element. For the specific frame format of the multilink element, it is understandable to refer to the descriptions in existing standards. Details are not described here.

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

[0114] If a multilink element carried in an association request frame contains multiple STA per profile sub-elements, it can be understood that there are multiple link identifier sub-fields, or in other words, multiple second links.

[0115] S102: The first access point of the AP MLD sends a first association response frame on the first link, 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 value of the first status code field is non-zero to indicate that the first link is not accepted, and the second status code field is set to a first non-zero value to indicate that the reason the second link is not accepted is that the first link is not accepted.

[0116] Correspondingly, the first non-AP MLD station receives a first association response frame on the first link. The first non-AP MLD station may obtain information from the first and second status code fields of the first association response frame regarding whether the first link is acceptable (or whether the multilink communication setup is successful or not) and whether the second link is acceptable (including the reasons why the second link is not acceptable).

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

[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 configured, or whether the first link is a link in multilink communication. If the first link is accepted (the 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 the cause of failure (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, 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 cause of the first link not being accepted. Specifically, refer to existing standards for the values ​​and meanings of the first status code. I won't go into details here.

[0119] In this application, “unacceptable” and “cannot be accepted” may be understood to have the same meaning, for example, unacceptable, not properly configured, not forming a link in multilink communication, or any other same or similar meaning.

[0120] Optionally, if the first link is accepted (the link is accepted), the multi-link setup between the non-AP MLD and the AP MLD may be successful, or multi-link communication between the non-AP MLD and the AP MLD may be successfully configured. However, if the first link is not accepted (the link is not accepted), the multi-link setup between the non-AP MLD and the AP MLD will fail, or multi-link communication between the non-AP MLD and the AP MLD will fail to be configured. When the first status code field indicates that the first link is not accepted, or when the first status code field indicates the reason why the first link is 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 that multi-link communication between the non-AP MLD and the AP MLD has failed to be configured. In other words, when the value of the first status code field is not 0, this may indicate that the first link is unacceptable or the reason why the first link is unacceptable, and may further indicate that the multilink configuration between the non-AP MLD and the AP MLD has failed, or that the multilink communication between the non-AP MLD and the AP MLD has failed to be configured.

[0121] Optionally, the second status code field may indicate whether the second link is accepted, whether the second link is successfully configured, or whether the second link is a link in multilink 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 the cause of failure (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, 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 cause of the second link not being accepted.

[0122] Optionally, a non-zero first value is newly defined in this embodiment of this 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 reason the second link is not accepted is that the first link is not accepted, or that the reason the second link is not accepted is solely that the first link is not accepted. In other words, when the second status code field is set to the first value, this indicates that the second link may be successfully established if a non-AP MLD sends an association request frame over the second link. The value of the first status code field cannot be the first value in this embodiment of this 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 is not defined in the existing Status Code field. For example, assuming the length of the Status Code field is n bits, the first value may be any value other than the existing values, from 0 to (2 n It can be any of the values ​​of -1). For example, n is equal to 16. Existing values ​​include values ​​from 0 to 135, or values ​​from 0 to 135 other than the reserved values ​​(4, 8, 9, 20, 21, 26, 29, 36, 48, 66, 69 to 71, 90, 91, 114, 115, 127). For example, the first value is a value other than 0 to 135, from 0 to (2 16 -1) is one of the values, for example, 136, 137, 138, or 139. In other examples, the first value is one of the reserved values ​​from 0 to 135, for example, 4, 8, 9, 20, 21, 26, 29, 36, 48, 66, 69-71, 90, 91, 114, 115, or 127. [Table 1]

[0124] In this application, it should be understood that the link on which association request / response frames are exchanged may be called a transmitted link, and correspondingly, other links may be called non-transmitted links. Therefore, 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 the first value may also be described as follows: The reason why a non-transmitted link is not accepted is that a transmitted link is not accepted.

[0125] Optionally, the first status code field may be located in the 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 may not be in the multi-link element of the association response frame, or the first status code field may be located in the core frame of the association response frame. The core frame may be content other than the multi-link element (MLE) within 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 may be the status code field included in the STA Profile subfield of the Per-STA Profile subelement.

[0126] Figure 6 is a schematic diagram of the frame format of an association response frame according to an embodiment of this application. As shown in Figure 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, an STA Control field and an STA Profile field. The STA Control field includes a link ID subfield, which indicates a second link (or non-transmission link). The STA Profile field includes a Status Code field (i.e., a second status code field) indicating whether the link indicated by the link ID subfield is accepted. It should be understood that Figure 6 shows only some of the 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. Details are not provided here. For the specific meaning of each field of the association response frame, it should be further understood by referring to the description in the existing standard. Details are not provided 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, one of which indicates whether a non-transmission link is acceptable or not. When a non-transmission link in a non-AP MLD can be accepted (or successfully configured), but the non-transmission link cannot be accepted because the transmission link is not accepted (or fails to be configured), the AP MLD may set the second status code field corresponding to the non-transmission link to a first value to indicate that the non-transmission link is not accepted because the transmission link is not accepted, or to notify the non-AP MLD that the non-transmission link may be accepted (or successfully configured) if the non-AP MLD sends an association request frame over the non-transmission link. When the second status code field is set to a first value to indicate that the reason the second link is not accepted is because the first link is not accepted, it can be understood that the value of the first status code field should be set to a non-zero value.

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

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

[0130] Optionally, after step S102, the multilink communication setup method may further include one or more of the following steps.

[0131] S103: The second station of the non-AP MLD sends a second association request frame over the second link.

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

[0133] According to the definition of a transmitted link (a link on which 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 a non-transmitted link. Here, the second link is a transmitted link.

[0134] S104: The AP MLD's second access point sends a second association response frame over the second link.

[0135] In response, the second station, which is not an AP MLD, receives the second association response frame on the second link.

[0136] Optionally, the value of the second status code field in the first association response frame is the first value. Thus, the non-AP MLD may determine that the reason the second link corresponding to the second status code field is unacceptable is that the first link is unacceptable, or that the reason the second link failed to be set up is solely because the first link failed to be set up, or that the second link may be successfully set up if the non-AP MLD sends an association request frame on the second link. Thus, when the first link is unacceptable (in other words, the value of the first status code field in the first association response frame is not 0) and the value of the second status code field in the first association response frame is the 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 that an association with the AP MLD be set up on at least the second link. In response, after receiving the second association request frame on the second link, the AP MLD's second access point sends back a second association response frame on the second link to indicate whether the association was successfully established.

[0137] It can be understood that the exchange of a second association request frame and a second association response frame between a non-AP MLD and an AP MLD may be for multilink configuration or for association configuration on the second link only. This is not limited to this embodiment of the application. In other words, whether or not the second association request frame and the second association response frame carry a multilink element is not limited to this embodiment of the application. If the exchange of a second association request frame and the second association response frame between a non-AP MLD and an AP MLD is for multilink configuration, it can be further understood that the multilink communication may not have to be configured on the first link. In other words, if the second association request frame carries a multilink element, the multilink element may not have to carry information about the first link. In the preceding process of multilink configuration (e.g., steps S201 and S202), the first link is not accepted (i.e., configuration fails). In this case, the second association request frame is sent over the second link for multilink configuration, and it is highly likely that the first link is still not accepted (i.e., configuration fails). Therefore, to improve the probability of successful multilink configuration, the multilink 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 information about the first link may, as an alternative, be carried in the multilink element of the second association request frame. The case of the first link may change compared to the case of the first link in the preceding process of multilink configuration (e.g., steps S201 and S202), and the first link may be accepted (i.e., successfully configured).

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

[0139] [Embodiment 2] Embodiment 2 of this application primarily describes a case in which the status code field outside the multilink element of the association response frame (i.e., the first status code field) and the status code field of the multilink element (i.e., the second status code field) jointly indicate that the reason 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] Figure 7 is another schematic flowchart of a multilink communication setup method according to an embodiment of this application. As shown in Figure 7, the multilink communication setup method includes, but is not limited to, the following steps.

[0141] S201: The first station of the non-AP MLD transmits a first association request frame on the first link, the first association request frame includes a multilink element, the multilink element includes instruction information, and the instruction information indicates the second link.

[0142] Accordingly, the first access point of the AP MLD receives the first association request frame on the first link.

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

[0144] S202: The first access point of AP MLD transmits a first association response frame on the first link, 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 is set to a value indicating that the first link is not accepted or a value indicating the reason why the first link is not accepted, in order to jointly indicate that the reason the second link is not accepted is that the first link is not accepted, and the second status code field is set to a value indicating that the second link is accepted.

[0145] Correspondingly, the first non-AP MLD station receives a first association response frame on the first link. Based on the values ​​of the first and second status code fields of the first association response frame, the first non-AP MLD station may determine that the reason the second link is unacceptable is that the first link is unacceptable.

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

[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 configured, or whether the first link is a link in multilink 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 configured, or whether the second link is a link in multilink 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. To jointly indicate that the reason the second link is not accepted is that the first link is not accepted, the first status code field may be set to a value indicating that the first link is not accepted or a value indicating the reason the first link is not accepted, and the second status code field may be set to a value indicating that the second link is accepted. Alternatively, to jointly indicate that the reason the second link is not accepted is that the first link is not accepted, the value of the first status code field is not 0, and the value of the second status code field is 0.

[0148] For the relationship between whether the first link is accepted and whether the multilink setup is successful (optional), please refer to the relevant explanation in Embodiment 1. Further details will not be provided here.

[0149] Optionally, the first status code field may be located in the 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 may not be located within the multilink element of the association response frame, or it may be located in the core frame of the association response frame, and the core frame may contain content other than the multilink element (MLE) within the association response frame. The second status code field may be located within the multilink element of the association response frame. For example, the second status code field may be a status code field included in the STA profile field of a per-STA profile subelement. See Figure 6 for the frame format of the association response frame. Details will not be explained again here.

[0150] Optionally, in this embodiment of the application, the multilink element of the first association response frame includes one or more second status code fields, one of which indicates whether a non-transmission link is acceptable or not. When a non-transmission link can be accepted (or successfully configured), but cannot be accepted because a transmission link is not accepted (or has failed to be configured), the AP MLD may jointly indicate that the reason the non-transmission link is not accepted (or has failed to be configured) is that the transmission link is not accepted (or has failed to be configured), or jointly indicate that the reason the non-transmission link is not accepted is solely that the transmission link is not accepted, or, if a non-AP MLD sends an association request frame over the non-transmission link, the AP MLD may set the first status code field to a non-zero value and the second status code field corresponding to the non-transmission link to the first value to notify the non-AP MLD that the non-transmission link may 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 accepted, or indicates a reason why the first link is not accepted, 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 accepted, or the value of the second status code field is 0), this indicates that the reason why the second link is not accepted is that the first link is not accepted.

[0152] In other words, if a non-transmission link is accepted, the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement (i.e., the second Status Code field) may indicate success. If a non-transmission link is not accepted, the Status Code field indicates the cause of failure. However, the following exceptions apply: 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, the second link is not accepted when the Status Code field outside the multi-link element of the Association Response frame (i.e., the first Status Code field) does not indicate success, and the Status Code field in the STA Profile subfield of the Per-STA Profile subelement corresponding to the second link (i.e., the second Status Code field) indicates success. However, the second link may be accepted if the Association Request frame is transmitted on that link.

[0154] In this embodiment of the application, setting rules and corresponding interpretation rules for a first and 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 reason the link corresponding to the second status code field is not accepted is that the first link is not accepted. Thus, a non-AP MLD knows that when an association request frame is sent on a link for multilink setup, there is a high probability that the multilink setup will succeed. This can improve the probability of successful multilink setup, reduce the number of attempts, and improve the efficiency of multilink setup.

[0155] Optionally, in this embodiment of the application, to jointly indicate that the reason for the rejection of at least one second link is the rejection of the first link, the value of the first state code field in the first association response frame is not 0 and the value of at least one second state 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 state field in the first association response frame is 0.

[0156] Optionally, after step S202, the multilink communication setup method may further include the following steps.

[0157] S203: The second station of the non-AP MLD sends a second association request frame over the second link.

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

[0159] According to the definition of a transmitted link (a link on which 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 a non-transmitted link. Here, the second link is a transmitted link.

[0160] S204: The AP MLD's second access point sends a second association response frame over the second link.

[0161] In response, the second station, which is not an AP MLD, receives the second association response frame on the second link.

[0162] For the implementation of steps S203 and S204 in this embodiment of this application, refer to the implementation of steps S103 and S104 in Embodiment 1. Details will not be explained again here.

[0163] In this embodiment of the application, when one or more non-transmission links in a non-AP MLD can be accepted (or successfully configured), but one or more non-transmission links cannot be accepted because a transmission link is not accepted (or fails to configure), the value of the first status code field in the association response frame is set to a non-zero value and the second status code field of the multilink element in the association response frame is set to 0 (or set to indicate success) to jointly indicate that the reason the non-transmission links cannot be accepted is that the transmission link is not accepted, or to inform the non-AP MLD that the non-transmission links may be accepted (or successfully configured) when an association request frame is sent over a non-transmission link. This can increase the probability of successful multilink configuration. Furthermore, the non-AP MLD does not need to attempt to configure multilink communication on each link in order to reduce the number of attempts and improve the efficiency of multilink configuration. To save overhead, it is not necessary to define new status code values.

[0164] [Embodiment 3] Embodiment 3 of this application primarily describes extending the value of the status code field outside the multilink element of the association response frame (i.e., the first status code field) to indicate that the multilink configuration has failed. Furthermore, the value of the status code field of the multilink element (i.e., the second status code field) may be set to jointly indicate that the reason the link corresponding to the second status code field is unacceptable is that the transmission link is unacceptable.

[0165] Figure 8 is another schematic flowchart of a multilink communication setup method according to an embodiment of this application. As shown in Figure 8, the multilink communication setup method includes, but is not limited to, the following steps.

[0166] S301: The first station of the non-AP MLD transmits a first association request frame on the first link, the first association request frame includes a multilink element, the multilink element includes instruction information, and the instruction information indicates the second link.

[0167] Accordingly, the first access point of the AP MLD receives the first association request frame on the first link.

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

[0169] S302: The first access point of the AP MLD sends a first association response frame on the first link, the first association response frame includes a first status code field, which is set to a second non-zero value to indicate that the multilink configuration between the non-AP MLD and the AP MLD has failed, and that the multilink configuration may succeed if the association request frame is transmitted on another requested link.

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

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

[0172] Optionally, 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 one or more second status code fields, one of which indicates the reason why a link is accepted or rejected. For the specific meaning of the second status code fields, refer to the relevant description in Embodiment 1. Further details will not be explained again here.

[0173] Optionally, a second value is newly defined in this embodiment of the application, and the second value is a value that is not used or defined in the existing Status Code field. For example, assuming the length of the Status Code field is n bits, the second value is 0 to (2) other than the existing values. n It can be any of the values ​​of -1). For example, n is equal to 16. Existing values ​​include, but are not limited to, values ​​from 0 to 135, or values ​​from 0 to 135 other than 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 is any value from 0 to (2) other than 0 to 135. 16 -1) is one of the values, for example, 136, 137, 138, or 139. In other examples, the second value is one of the reserved values ​​from 0 to 135, for example, 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 Embodiment 1.

[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 multilink setup between the non-AP MLD and the AP MLD has failed, or that the multilink setup between the non-AP MLD and the AP MLD has failed, and that the multilink setup may succeed if the association request frame is transmitted over another requested link (a link other than the first link). In this embodiment of the 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] When the value of the first status code field is an existing value (e.g., 0 to 135), it should be understood that this indicates whether the first link (or the link for transmitting the first association request frame) is accepted, whether the configuration is successful, or whether the first link becomes a link in multilink communication. For details, see the relevant 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 multilink configuration has failed, or that the multilink configuration has failed, but the multilink configuration may succeed if the association request frame is transmitted over another requested link.

[0176] In this embodiment of the application, when a multilink configuration fails but one link exists and an association request frame is transmitted over that link, the first state code field of the association response frame is set to a newly defined value (i.e., a second value) to indicate that a multilink configuration may be successful. Thus, to avoid the high power consumption of the non-AP MLD caused by repeated attempts to configure multilink communication by the non-AP MLD when the probability of successful multilink configuration is low, the non-AP MLD knows whether or not there is a probability of successful multilink configuration with the AP MLD.

[0177] Optionally, the first status code field may be located in the 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 may not be located in the multilink element of the association response frame, or it may be located in the core frame of the association response frame, and the core frame may be content other than the multilink element (MLE) within 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 a per-STA profile subelement. See Figure 6 for the frame format of the association response frame. Details will not be explained again here.

[0178] Optionally, if a non-transmission link can be accepted (or successfully configured), but the non-transmission link cannot be accepted because multilink configuration has failed (e.g., the transmission link is not accepted), AP MLD may set the first status code field to the second value and set the second status code field corresponding to the non-transmission link to 0 to jointly indicate that multilink configuration has failed and that multilink configuration may succeed if the association request frame is transmitted over the non-transmission link, or to jointly indicate that the reason the non-transmission link cannot be accepted is that the transmission link is not accepted (or multilink configuration 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 accepted, or the value of the second status code field is 0), this indicates that the multilink setup has failed and that the multilink setup may succeed if the association request frame is transmitted over the second link, or that the reason the second link is not accepted is that the first link is not accepted (or the multilink setup has failed).

[0180] Optionally, in this embodiment of the application, to jointly indicate that multilink setup may succeed in the first association response frame if multilink setup fails and the association request frame is transmitted over at least one second link corresponding to at least one second status code field, the first status code field is set to a second value, and the value of 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 in the first association response frame is 0.

[0181] Optionally, after step S302, the multilink communication setup method may further include the following steps.

[0182] S303: The second station of the non-AP MLD sends a second association request frame over the second link.

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

[0184] According to the definition of a transmitted link (a link on which 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 a non-transmitted link. Here, the second link is a transmitted link.

[0185] S304: The AP MLD's second access point sends a second association response frame over the second link.

[0186] In response, the second station, which is not an AP MLD, receives the second association response frame on the second link.

[0187] For the implementation of steps S303 and S304 in this embodiment of this application, refer to the implementation of steps S303 and S304 in Embodiment 1. Details will not be explained again here.

[0188] In this embodiment of the application, to jointly indicate that multilink configuration has failed and that multilink configuration may succeed 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 newly defined value (i.e., the second 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). Thus, a non-AP MLD can know which link the association request frame is transmitted on in order to successfully configure multilink communication. This can improve the probability of successful multilink configuration, reduce the number of attempts, and improve the efficiency of multilink configuration.

[0189] The above description details the method provided in this application. To facilitate the implementation of the above solution in the embodiments of this application, embodiments of this application further provide corresponding apparatus or devices.

[0190] In this application, AP MLDs and non-AP MLDs are divided into functional modules based on embodiments of the method. For example, each functional module may be obtained through division based on a corresponding function, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in hardware form 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 functional division. Other division methods may be used in actual implementations. AP MLDs and non-AP MLDs in embodiments of this application will be described in detail below with reference to Figures 9 to 11.

[0191] Figure 9 is a schematic diagram of the structure of a communication device according to an embodiment of this application. As shown in Figure 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 a non-AP MLD as described above. In other words, the communication device shown in Figure 9 may be configured to perform steps, functions, etc., that are performed by a non-AP MLD in embodiments of the method. For example, the communication device may be a non-AP MLD, a 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 over a first link and to receive a first association response frame over the first link. The first association request frame includes a multilink element, the multilink element includes instruction information, and the instruction information indicates a second link. 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 value of which is non-zero to indicate that the first link is not accepted, and the value of which is non-zero to indicate that the reason the second link is not accepted is that the first link is not accepted.

[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 over a second link and to receive a second association response frame over a 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] For a detailed explanation of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., it may be helpful to refer to the embodiments of the method. Further details will not be explained here.

[0198] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to embodiments of the method (as shown in Figure 4). Further details are not described here.

[0199] In other designs, the transceiver unit 10 is configured to transmit a first association request frame over a first link and to receive a first association response frame over the first link. The first association request frame includes a multilink element, which includes instruction information, which indicates a second link. 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, and the value of the first status code field is not 0 and the value of the second status code field is 0 to jointly indicate that the reason the second link is not accepted is that the first link is not accepted.

[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 over a second link and to receive a second association response frame over a 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] For a detailed explanation of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., it may be helpful to refer to the embodiments of the method. Further details will not be explained here.

[0204] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to embodiments of the method (as shown in Figure 7). Further details are not described here.

[0205] In yet another design, the transceiver unit 10 is configured to transmit a first association request frame over a first link and to receive a first association response frame over the first link. The first association request frame includes a multilink element, which includes instruction information, which indicates a second link. The first association response frame includes a first status code field, which is set to a second non-zero value to indicate that the multilink setup between the non-AP MLD and the AP MLD has failed, and that the multilink setup may succeed if the association request frame is transmitted over another 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 over a second link and to receive a second association response frame over a 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] For a detailed explanation of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., it may be helpful to refer to the embodiments of the method. Further details will not be explained here.

[0210] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to embodiments of the method (as shown in Figure 8). Further details are not described here.

[0211] Refer to Figure 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 Figure 9 may be configured to perform steps, functions, etc., that are performed by the AP MLD in the embodiment of the method. 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, the transceiver unit 10 is configured to receive a first association request frame on a first link and to transmit a first association response frame on the first link. The first association request frame includes a multilink element, the multilink element includes instruction information, and the instruction information indicates a second link. 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 value of which is non-zero to indicate that the first link is not accepted, and the value of which is non-zero to indicate that the reason the second link is not accepted is that the first link is not accepted.

[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] For a detailed explanation of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., it may be helpful to refer to the embodiments of the method. Further details will not be explained here.

[0217] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to embodiments of the method (as shown in Figure 4). Further details are not described here.

[0218] In other designs, the transceiver unit 10 is configured to receive a first association request frame on a first link and to transmit a first association response frame on the first link. The first association request frame includes a multilink element, which includes instruction information, which indicates a second link. 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, and the value of the first status code field is not 0 and the second status code field is 0 to jointly indicate that the reason the second link is not accepted is that the first link is not accepted.

[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] For a detailed explanation of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., it may be helpful to refer to the embodiments of the method. Further details will not be explained here.

[0223] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to embodiments of the method (as shown in Figure 7). Further details are not described here.

[0224] In yet another design, the transceiver unit 10 is configured to receive a first association request frame on a first link and to transmit a first association response frame on the first link. The first association request frame includes a multilink element, which includes instruction information, which indicates a second link. The first association response frame includes a first status code field, which is set to a second non-zero value to indicate that the multilink setup between the non-AP MLD and the AP MLD has failed, and that the multilink setup may succeed if the association request frame is transmitted on another 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] For a detailed explanation of the first association request frame, the first association response frame, the second association request frame, the second association response frame, etc., it may be helpful to refer to the embodiments of the method. Further details will not be explained here.

[0229] It should be understood that the specific description of the transceiver unit and processing unit in this embodiment of this application is merely illustrative. For specific functions or steps performed by the transceiver unit and processing unit, refer to embodiments of the method (as shown in Figure 8). Further details are not described here.

[0230] The above describes the non-AP MLD and AP MLD in embodiments of this application, and the possible product forms of the non-AP MLD and AP MLD are described below. It should be understood that any product of any form having the functionality of the non-AP MLD shown in Figure 9, and any product of any form having the functionality of the AP MLD shown in Figure 9, fall within the scope of protection of embodiments 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 embodiments of this application.

[0231] In possible implementations, in the communication device shown in Figure 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 a single component, for example, a transceiver. In this embodiment of the application, the processor and the transceiver may be coupled, etc. The connection method between the processor and the transceiver is not limited to this embodiment of the application. In the process of performing 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 the process of the processor outputting information. When outputting information, the processor outputs the information to the transceiver so that the transceiver can transmit the information. After the information is output by the processor, other processing may need to be performed on the information before the information arrives at the transceiver. Similarly, the process of receiving information in a method (for example, 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 the process by which the processor receives the input information. When the processor receives the input information, the transceiver receives the information and inputs it 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] Figure 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. Figure 10 shows only the main components of the communication device 1000. In addition to the processor 1001 and 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 equipment, execute software programs, and process data from 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 conversions between baseband signals and radio frequency signals and to process radio frequency signals. The antenna is primarily configured to receive and transmit radio frequency signals in the form of electromagnetic waves. An input / output device, such as a touchscreen, display, or keyboard, is primarily configured to receive data entered by the user and output data to the 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 the 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 electromagnetic wave form through the 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 circuit and antenna may be located independently of the processor that performs baseband processing. For example, in a distributed scenario, the radio frequency circuit and antenna may be located independently of the communication equipment.

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

[0237] In a certain design, the communication device 1000 may be configured to perform the functions of a 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 Figure 4, and / or to perform other processes for performing the techniques described in this specification. The transceiver 1002 may be configured to perform steps S101, S103, etc. in Figure 4, and / or to perform other processes for performing the techniques described in this specification.

[0238] In other designs, the communication device 1000 may be configured to perform the functions of the AP MLD in Embodiment 1. The processor 1001 may be configured to generate a first association response frame transmitted in step S102 and a second association response frame transmitted in step S104 in Figure 4, and / or to perform other processes for performing the technology described in this specification. The transceiver 1002 may be configured to perform steps S102 and S104 in Figure 4, and / or to perform other processes for performing the technology described in this specification.

[0239] In a certain design, the communication device 1000 may be configured to perform the functions of a 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 Figure 7, and / or to perform other processes for performing the techniques described in this specification. The transceiver 1002 may be configured to perform steps S201, S203, etc. in Figure 7, and / or to perform other processes for performing the techniques described in this specification.

[0240] In other designs, the communication device 1000 may be configured to perform the functions 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 Figure 7, and / or to perform other processes for performing the technology described in this specification. The transceiver 1002 may be configured to perform steps S202 and S204 in Figure 7, and / or to perform other processes for performing the technology described in this specification.

[0241] In a certain design, the communication device 1000 may be configured to perform the functions of a 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 Figure 8, and / or to perform other processes for performing the techniques described in this specification. The transceiver 1002 may be configured to perform steps S301, S303, etc. in Figure 8, and / or to perform other processes for performing the techniques described in this specification.

[0242] In other designs, the communication device 1000 may be configured to perform the functions 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 Figure 8, and / or to perform other processes for performing the technology described in this specification. The transceiver 1002 may be configured to perform steps S302 and S304 in Figure 8, and / or to perform other processes for performing the technology described in this specification.

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

[0244] In any one of the above designs, the processor 1001 may store instructions. The instructions may be a computer program. The computer program is executed on the processor 1001, thereby enabling the communication device 1000 to perform the method described in the embodiment of the above method. The computer program may be fixed to the processor 1001, in which case the processor 1001 may be implemented by hardware.

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

[0246] The scope of communication devices described in this application is not limited to that, and the structure of the communication device is not limited to that shown in Figure 10. The communication device may be an independent device or part of a larger device. For example, the communication device may be the following: (1) An independent integrated circuit (IC), chip, or chip system or subsystem. (2) A set comprising one or more ICs, the set of ICs may optionally further include a storage component configured to store data and computer programs. (3) ASIC such as a modem (4) Modules 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) Others

[0247] In other possible implementations, in the communication device shown in Figure 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, interface circuit, interface, etc. Alternatively, the transceiver unit 10 may be a transmit unit and a receive unit. The transmit unit may be an output interface, and the receive unit may be an input interface. The transmit unit and the receive unit are integrated into a single unit, for example, an input / output interface. Figure 11 is a schematic diagram of another structure of the communication device according to an embodiment of this application. As shown in Figure 11, the communication device shown in Figure 11 includes a logic circuit 901 and an interface 902. In other words, the processing unit 20 may be implemented using the logic circuit 901, and the transceiver unit 10 may be implemented using the interface 902. The logic circuit 901 may be a chip, a processing circuit, an integrated circuit, a system on a chip (SoC), etc. The interface 902 may be a communication interface, an input / output interface, a pin, etc. For example, Figure 11 shows an example where a communication device is used as a chip. The chip includes a logic circuit 901 and an interface 902.

[0248] In this embodiment of the application, the logic circuits may be further coupled to an interface. The specific connection methods of the logic circuits and the interface are not limited to this embodiment of the application.

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

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

[0251] For a detailed explanation of the first association request frame, the first association response frame, etc., it may be helpful to refer to the embodiments of the method. Further details will not be provided here.

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

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

[0254] Embodiments of this application further provide a wireless communication system, comprising a non-AP MLD and an AP MLD, the non-AP MLD and the AP MLD being configured to perform the method in any one of the embodiments described above.

[0255] Furthermore, this application further provides a computer program. The computer program is configured to perform operations and / or processes that are performed by a non-AP MLD in the manner provided in this application.

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

[0257] This application further provides a computer-readable storage medium for storing computer code. When the computer code is executed on a computer, the computer becomes capable of performing operations and / or processes performed by a non-AP MLD in the manner provided in this application.

[0258] This application further provides a computer-readable storage medium for storing computer code. When the computer code is executed on a computer, the computer is able to perform operations and / or processes performed by AP MLD in the manner provided in this application.

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

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

[0261] In some embodiments provided in this application, it should be understood that the disclosed systems, apparatuses and methods may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used in actual implementations. For example, multiple units or components may be coupled or integrated into other systems, or some features may be ignored or not performed. Furthermore, the mutual coupling, direct coupling or communication connection shown or discussed may be implemented through some interfaces, indirect coupling or communication connection between apparatuses or units, or through electrical, mechanical, or other forms of connection.

[0262] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, may be located in one place, or may be distributed across multiple network units. Some or all of the units may be selected on a practical basis to achieve the technical effects of the solution provided in the embodiments of this application.

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

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

[0265] The above description merely outlines a specific implementation of this application and is not intended to limit the scope of protection. Any modification or substitution that is readily conceived by a person skilled in the art within the scope of the technical scope disclosed in this application shall fall within the scope of protection. Accordingly, the scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. A method for configuring multilink communication, The steps include: transmitting a first association request frame on a first link, wherein the first association request frame includes a multilink element, the multilink element includes instruction information, and the instruction information indicates a second link different from the first link; The steps include receiving a first association response frame on the first link, wherein 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 a second status code field, and Includes, A method in which the value of the first status code field is not 0 to indicate that the first link is unacceptable, and the value of the second status code field is set to 139 to indicate that the reason the second link is unacceptable is solely because the first link is unacceptable.

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

3. The method according to claim 1, wherein the second status code field is a status code field included in the STA profile subfield of the STA profile sub-element.

4. After receiving a first association response frame on the first link, the method: The steps include sending a second association request frame over the second link, The steps include receiving a second association response frame on the second link described above, and The method according to claim 1, further comprising:

5. A method for configuring multilink communication, The steps include receiving a first association request frame on a first link, wherein the first association request frame includes a multilink element, the multilink element includes instruction information, and the instruction information indicates a second link different from the first link. The steps include: transmitting a first association response frame over the first link, wherein 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 a second status code field; Includes, A method in which the value of the first status code field is not 0 to indicate that the first link is unacceptable, and the value of the second status code field is set to 139 to indicate that the reason the second link is unacceptable is solely because the first link is unacceptable.

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

7. The method according to claim 5, wherein the second status code field is a status code field included in the STA profile subfield of the STA profile sub-element.

8. After sending the first association response frame over the first link described above, the method, The steps include receiving a second association request frame on the second link, The steps include: sending a second association response frame over the second link; The method according to claim 5, further comprising:

9. A communication device, The communication device includes a processing unit and a transceiver unit. The processing unit controls the transceiver unit, A first association request frame is transmitted over a first link, the first association request frame includes a multilink element, the multilink element includes instruction information, the instruction information indicates a second link different from the first link, A first association response frame is received on the first link, 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 a second status code field. It is configured in such a way, A communication device wherein the value of the first status code field is not 0 to indicate that the first link is unacceptable, and the value of the second status code field is set to 139 to indicate that the reason the second link is unacceptable is solely because the first link is unacceptable.

10. The aforementioned transceiver unit is Send a second association request frame over the second link, The second association response frame is received on the second link described above. The communication device according to claim 9, further configured as follows.

11. The communication device according to 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 communication device according to claim 9, wherein the second status code field is a status code field included in the STA profile subfield of the STA profile sub-element.

13. A communication device, The communication device includes a processing unit and a transceiver unit. The processing unit controls the transceiver unit, A first association request frame is received on a first link, the first association request frame includes a multilink element, the multilink element includes instruction information, the instruction information indicates a second link different from the first link, A first association response frame is transmitted over the first link, 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 a second status code field. It is configured in such a way, A communication device wherein the value of the first status code field is not 0 to indicate that the first link is unacceptable, and the value of the second status code field is set to 139 to indicate that the reason the second link is unacceptable is solely because the first link is unacceptable.

14. The transceiver unit is Upon receiving the second association request frame on the second link, Send a second association response frame over the second link described above. The communication device according to claim 13, further configured as follows.

15. The communication device according to 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 communication device according to claim 13, wherein the second status code field is a status code field included in the STA profile subfield of the STA profile sub-element.

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

18. A communication device including a processor and memory, The memory is configured to store instructions, A communication device wherein the processor is configured to execute the instructions and perform the 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 communication 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 the 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 communication 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 the method according to any one of claims 5 to 8.

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

22. A computer-readable storage medium, The computer-readable storage medium is configured to store a computer program, and when the computer program is executed, an access point multilink device (AP MLD) performs the method according to any one of claims 5 to 8.

Images