Multi-link reconfiguration method and device
Patent Information
- Application Number
- CN202380036272.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-24
- Filing Date
- 2023-01-09
- Publication Date
- 2024-12-06
AI Technical Summary
During the multi-link communication establishment process, if the first link is not accepted, the non-AP MLD cannot determine whether other links can successfully establish multi-link communication, resulting in low multi-link establishment efficiency.
By setting the first status code field and the second status code field in the association response frame, non-AP MLD can learn which links can successfully establish multi-link communication by sending association request frames, improving the possibility of successful multi-link establishment. and reduce the number of attempts.
It improves the efficiency of multi-link establishment, avoids the necessity for non-AP MLD to try on each link, and saves the number of attempts and power consumption.
Smart Images

Figure CN119096687A_ABST
Abstract
Description
Multi-link reconfiguration method and device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on April 24, 2022, with application number 202210435613.2 and application name “Method for establishing multi-link communication and related devices”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of wireless communication technology, and in particular to a method for establishing multi-link communication and related devices. Background Art
[0003] With the development of wireless communication technology, more and more wireless communication devices support multi-link (ML) communication. For example, they can communicate simultaneously on the 2.4 GHz, 5 GHz, and 6 GHz frequency bands, or on different channels within the same frequency band, thereby increasing the communication rate between devices. Such devices are generally called multi-link devices (MLDs). Multi-link devices typically contain multiple stations, each operating on a frequency band, a channel, or a link. If all stations within an MLD are access points (APs), it can be further referred to as an AP MLD; if all stations within an MLD are non-access point stations (non-AP STAs), it can be further referred to as a non-AP MLD. Non-AP MLDs can communicate with AP MLDs after establishing multiple links (also called multi-link association).
[0004] During the multi-link establishment (or multi-link association) process, the non-AP MLD can send an association request frame to the AP MLD on a link (for ease of description, this link is referred to as the first link). The association request frame carries a multi-link element (MLE) that carries information about the non-AP MLD and other links in the non-AP MLD. The association request frame is used to request the establishment of multi-link communication with the AP MLD. After receiving the association request frame on the first link, the AP MLD can reply with an association response frame on the first link to the non-AP MLD. The association response frame informs the non-AP MLD whether multi-link communication is successfully established. The association response frame can also carry an MLE that carries information about the AP MLD and other links in the AP MLD.
[0005] According to the multi-link establishment rules, if the first link is not accepted (or the first link establishment fails), then other links cannot be accepted (or other links cannot be successfully established). Therefore, if the first link is not accepted, the non-AP MLD does not know whether it can successfully send association request frames on other links to request multi-link communication with the AP MLD. Therefore, the non-AP MLD can only send association request frames on each link to attempt to establish multi-link communication with the AP MLD, but this results in low multi-link establishment efficiency.
[0006] Summary of the Invention
[0007] The embodiments of the present application provide a method for establishing multi-link communication and related devices, which can improve the efficiency of multi-link establishment (or multi-link association).
[0008] The present application is introduced below from different aspects. It should be understood that the implementation methods and beneficial effects of the following different aspects can be referenced to each other.
[0009] In a first aspect, the present application provides a method for establishing multi-link communication, the method comprising: a first station of a non-AP MLD sends 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 is used to indicate 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. The value of the first status code field is not 0, indicating that the first link is not accepted; the second status code field is set to a first value that is not 0, indicating that the reason why the second link is not accepted is that the first link is not accepted.
[0010] In this application, non-AP MLD has at least two links, and AP MLD also has at least two links.
[0011] Optionally, the first site is any site in the non-AP MLD, and the first link is a link on which the first site works.
[0012] Generally, if the link on which the association request frame is transmitted in non-AP MLD is rejected, the other links cannot be accepted either. However, the reasons for acceptance on each link may vary. Therefore, if the link on which the association request frame is transmitted in non-AP MLD is rejected, non-AP MLD does not know whether sending association request frames on other links will successfully establish multilink communication with AP MLD. Therefore, non-AP MLD can only send association request frames on each link to attempt to establish multilink communication, which results in low multilink establishment efficiency.
[0013] In this case, the present application sets the first status code field in the association response frame to a non-zero value and sets the second status code field in the multilink element of the association response frame to a non-zero first value. This indicates that the reason why the link corresponding to the second status code field is not accepted is that the transmission link is not accepted. In other words, this notifies the non-AP MLD that if an association request frame is sent on the link corresponding to the second status code field, the link can be accepted. This allows the non-AP MLD to send an association request frame on this link to establish multiple links, thereby increasing the probability of successful multilink establishment. Furthermore, the non-AP MLD does not need to attempt to establish multiple links on each link, thereby reducing the number of attempts and improving the efficiency of multilink establishment.
[0014] In combination with the first aspect, in one possible implementation, after the first station of the non-AP MLD receives the first association response frame on the first link, the method further includes: the second station of the non-AP MLD sends a second association request frame on the second link and receives a second association response frame on the second link.
[0015] The present application sets the first status code field in the first association response frame to non-zero, and sets the second status code field in the multilink element of the first association response frame to a non-zero first value, thereby notifying the non-AP MLD that if an association request frame is sent on the link corresponding to the second status code field, the link will be accepted (or successfully established). This allows the non-AP MLD to know which links are most likely to successfully establish multilink communication by sending the association request frame, thereby increasing the probability of successful multilink establishment, reducing the number of attempts, and improving the efficiency of multilink establishment.
[0016] In a second aspect, the present application provides a method for establishing multi-link communication, the method comprising: the first access point of AP MLD receives a first association request frame on the first link, and sends a first association response frame on the first link. The first association request frame includes a multi-link element, and the multi-link element includes indication information, and the indication information is used to indicate the 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. The value of the first status code field is not 0, which is used to indicate that the first link is not accepted; the second status code field is set to a first value that is not 0, which is used to indicate that the reason why the second link is not accepted is that the first link is not accepted.
[0017] Optionally, the first access point is an access point working on the first link in the AP MLD.
[0018] In combination with the second aspect, in a possible implementation, after the first access point of AP MLD sends a first association response frame on the first link, the method also includes: the second access point of AP MLD receives a second association request frame on the second link and sends a second association response frame on the second link.
[0019] In a possible implementation of any of the above aspects, the first value may be a value that is not used or defined in the existing status code (Status Code) field, or the first value is 0 to (2 n -1). n represents the length of the status code field. Existing values include, but are not limited to, 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, and 127).
[0020] In one possible implementation of any of the above aspects, the first status code field is located in a frame body of an association response frame. Exemplarily, the first status code field is located outside a multilink element of the association response frame. Alternatively, the first status code field is not in the multi-link element of the Association Response frame. Alternatively, the first status code field is in the core frame of the Association Response frame.
[0021] In a possible implementation of any of the above aspects, the second status code field is located in the multilink element of the association response frame. Exemplarily, the second status code field is the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement.
[0022] In a third aspect, the present application provides a communication device, specifically a non-AP MLD or a chip therein, configured to perform the method of the first aspect or any possible implementation of the first aspect. The communication device includes a unit configured to perform the method of the first aspect or any possible implementation of the first aspect.
[0023] In a fourth aspect, the present application provides a communication device, specifically an AP MLD or a chip therein, configured to execute the method of the second aspect or any possible implementation of the second aspect. The communication device includes a unit configured to execute the method of the second aspect or any possible implementation of the second aspect.
[0024] In the third or fourth aspect, the communication device may include a transceiver unit and a processing unit. For a detailed description of the transceiver unit and the processing unit, reference may be made to the device embodiments shown below. The beneficial effects of the third to fourth aspects may be referenced to the relevant descriptions of the first and second aspects, and are not further elaborated here.
[0025] In a fifth aspect, the present application provides a method for establishing multi-link communication, the method comprising: a first station of a non-AP MLD sends 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 multilink element, the multilink element includes indication information, and the indication information is used to indicate a second 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. The first status code field is set to a value indicating that the first link is not accepted or to a value indicating the reason why the first link is not 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 is accepted (for example, the value of the second status code field is 0), for jointly indicating that the reason why the second link is not accepted is that the first link is not accepted.
[0026] Optionally, the first site is any site in the non-AP MLD, and the first link is a link on which the first site works.
[0027] It is understood that if the value of the first status code field is not 0, it means that the first status code field does not indicate success (SUCCESS), that is, the first link is not accepted. If the value of the second status code field is 0, it means that the second status code field indicates SUCCESS, that is, the second link is accepted.
[0028] This application designs the setting rules and corresponding interpretation rules for the first status code field and the second status code field. When the first status code field does not indicate SUCCESS but the second status code field indicates SUCCESS, it indicates that the reason why the link corresponding to the second status code field was not accepted is that the first link was not accepted. This allows the non-AP MLD to know that if an association request frame is sent on this link to establish multiple links, the probability of success is high, thereby increasing the probability of successful multi-link establishment, reducing the number of attempts, and improving the efficiency of multi-link establishment. In addition, this application does not need to define new status code values, saving overhead.
[0029] In combination with the fifth aspect, in one possible implementation, after the first station of the non-AP MLD receives the first association response frame on the first link, the method further includes: the second station of the non-AP MLD sends a second association request frame on the second link and receives a second association response frame on the second link.
[0030] In a sixth aspect, the present application provides a method for establishing multi-link communication, the method comprising: the first access point of AP MLD receives a first association request frame on the first link, and sends a first association response frame on the first link. The first association request frame includes a multi-link element, and the multi-link element includes indication information, and the indication information is used to indicate the 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. The first status code field is set to a value indicating that the first link is not accepted or to a value indicating the reason why the first link is not 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 is accepted (for example, the value of the second status code field is 0), which is used to jointly indicate that the reason why the second link is not accepted is that the first link is not accepted.
[0031] Optionally, the first access point is an access point working on the first link in the AP MLD.
[0032] In combination with the sixth aspect, in a possible implementation, after the first access point of AP MLD sends a first association response frame on the first link, the method also includes: the second access point of AP MLD receives a second association request frame on the second link and sends a second association response frame on the second link.
[0033] In conjunction with the fifth or sixth aspect, in one possible implementation, the first status code field is located in the frame body of the association response frame. Exemplarily, the first status code field is located outside the multilink element of the association response frame. Alternatively, the first status code field is not located in the multilink element of the association response frame. Alternatively, the first status code field is located in the core frame of the association response frame.
[0034] In combination with the fifth aspect or the sixth aspect, in one possible implementation, the second status code field is located in the multi-link element of the association response frame. Exemplarily, the second status code field is the status code field included in the STA Profile field of the Per-STA Profile subelement.
[0035] In a seventh aspect, the present application provides a communication device, specifically a non-AP MLD or a chip therein, configured to perform the method of the fifth aspect or any possible implementation of the fifth aspect. The communication device includes a unit having a function of performing the method of the fifth aspect or any possible implementation of the fifth aspect.
[0036] In an eighth aspect, the present application provides a communication device, specifically an AP MLD or a chip therein, configured to execute the method of the sixth aspect or any possible implementation of the sixth aspect. The communication device includes a unit configured to execute the method of the sixth aspect or any possible implementation of the sixth aspect.
[0037] In the seventh or eighth aspects, the communication device may include a transceiver unit and a processing unit. For a detailed description of the transceiver unit and the processing unit, reference may be made to the device embodiments shown below. The beneficial effects of the seventh to eighth aspects may be referenced to the relevant descriptions of the fifth and sixth aspects, and are not further elaborated here.
[0038] In a ninth aspect, the present application provides a method for establishing multi-link communication, the method comprising: a first station of a non-AP MLD sends 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 multilink element, and the multilink element includes indication information, and the indication information is used to indicate a second link. 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 value other than 0, which is used to indicate that the multi-link establishment between the non-AP MLD and the AP MLD has failed and that the multi-link establishment may succeed if the association request frame is transmitted on other requested links. The multilink element of the first association response frame includes a second status code field, which is used to indicate the reason why the second link is received or not accepted.
[0039] Optionally, the first site is any site in the non-AP MLD, and the first link is a link on which the first site works.
[0040] Optionally, the second value is an unused or undefined value in the existing Status Code field, or the second value is 0 to (2 n -1). n represents the length of the status code field. Existing values include, but are not limited to, 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, and 127).
[0041] In this embodiment of the present application, the first status code field in the association response frame is set to a newly defined value (i.e., the second value) to indicate that multilink establishment has failed but one link exists. When an association request frame is transmitted on this link, multilink establishment can succeed. This allows the non-AP MLD to know whether multilink establishment with the AP MLD is likely to succeed, thereby avoiding the problem of the non-AP MLD repeatedly attempting to establish multilink communication when the probability of successful establishment is low, which would result in high power consumption for the non-AP MLD.
[0042] In combination with the ninth aspect, in one possible implementation, after the first station of the non-AP MLD receives the first association response frame on the first link, the method further includes: the second station of the non-AP MLD sends a second association request frame on the second link and receives a second association response frame on the second link.
[0043] In a tenth aspect, the present application provides a method for establishing multi-link communication, the method comprising: a first access point of an AP MLD receives a first association request frame on a first link, and sends a first association response frame on the first link. The first association request frame includes a multi-link element, and the multi-link element includes indication information, and the indication information is used to indicate a second link. The first association response frame includes a first status code field and a multi-link element, and the first status code field is set to a second value other than 0, which is used to indicate that the multi-link establishment between the non-AP MLD and the AP MLD has failed and that the multi-link establishment may succeed if the association request frame is transmitted on other requested links. The multi-link element of the first association response frame includes a second status code field, which is used to indicate the reason why the second link is received or not accepted.
[0044] Optionally, the first access point is an access point working on the first link in the AP MLD.
[0045] Optionally, the second value is an unused or undefined value in the existing Status Code field, or the second value is 0 to (2 n -1). n represents the length of the status code field. Existing values include, but are not limited to, 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, and 127).
[0046] In combination with the tenth aspect, in a possible implementation, after the first access point of AP MLD sends a first association response frame on the first link, the method also includes: the second access point of AP MLD receives a second association request frame on the second link and sends a second association response frame on the second link.
[0047] In combination with the ninth aspect or the tenth aspect, in a possible implementation method, the value of the above-mentioned second status code field is set to 0; when the first status code field is set to the second value and the second status code field is set to 0, it is used to jointly indicate that the multi-link establishment failed and if the association request frame is transmitted on the link corresponding to the second status code field, the multi-link establishment may be successful, or it indicates that the reason why the link corresponding to the second status code field is not accepted is that the first link is not accepted (or the multi-link establishment fails).
[0048] The present application sets the first status code field in the association response frame to a newly defined value (i.e., the second value) and sets the second status code field in the multilink element of the association response frame to 0 (or to indicate SUCCESS), thereby jointly indicating that multilink establishment has failed and that multilink establishment may succeed if an association request frame is transmitted on the link corresponding to the second status code field. This allows the non-AP MLD to know on which links sending the association request frame can successfully establish multilink communication, thereby increasing the possibility of successful multilink establishment, reducing the number of attempts, and improving the efficiency of multilink establishment.
[0049] In conjunction with the ninth aspect or the tenth aspect, in one possible implementation, the first status code field is located in the frame body of the association response frame. Exemplarily, the first status code field is located outside the multilink element of the association response frame. Alternatively, the first status code field is not located in the multilink element of the association response frame. Alternatively, the first status code field is located in the core frame of the association response frame.
[0050] In combination with the ninth aspect or the tenth aspect, in one possible implementation, the second status code field is located in the multi-link element of the association response frame. Exemplarily, the second status code field is the status code field contained in the STA Profile field of the Per-STA Profile subelement.
[0051] In an eleventh aspect, the present application provides a communication device, specifically a non-AP MLD or a chip therein, configured to perform the method of the ninth aspect or any possible implementation of the ninth aspect. The communication device includes a unit configured to perform the method of the ninth aspect or any possible implementation of the ninth aspect.
[0052] In a twelfth aspect, the present application provides a communication device, specifically an AP MLD or a chip therein, configured to execute the method of the tenth aspect or any possible implementation of the tenth aspect. The communication device includes a unit configured to execute the method of the tenth aspect or any possible implementation of the tenth aspect.
[0053] In the eleventh or twelfth aspect, the communication device may include a transceiver unit and a processing unit. For a detailed description of the transceiver unit and the processing unit, reference may be made to the device embodiments described below. The beneficial effects of the eleventh to twelfth aspects may be described with reference to the relevant descriptions of the ninth and tenth aspects, and are not further elaborated here.
[0054] In a thirteenth aspect, the present application provides a communication device, which is a non-AP MLD, and includes a processor configured to execute the method described in the first aspect, the fifth aspect, the ninth aspect, or any possible implementation of any one of these aspects. Alternatively, the processor is configured to execute a program stored in a memory, and when the program is executed, the method described in the first aspect, the fifth aspect, the ninth aspect, or any possible implementation of any one of these aspects is executed.
[0055] In combination with the thirteenth aspect, in a possible implementation, the memory is located outside the above-mentioned communication device.
[0056] In combination with the thirteenth aspect, in a possible implementation, the memory is located within the above-mentioned communication device.
[0057] In the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.
[0058] In combination with the thirteenth aspect, in a possible implementation, the communication device further includes a transceiver, and the transceiver is used to receive a frame or send a frame.
[0059] In a fourteenth aspect, the present application provides a communication device, which is an AP MLD, and includes a processor configured to execute the method described in the second aspect, the sixth aspect, the tenth aspect, or any possible implementation of any one of the aspects. Alternatively, the processor is configured to execute a program stored in a memory, and when the program is executed, the method described in the second aspect, the sixth aspect, the tenth aspect, or any possible implementation of any one of the aspects is executed.
[0060] In combination with the fourteenth aspect, in a possible implementation, the memory is located outside the above-mentioned second communication device.
[0061] In combination with the fourteenth aspect, in a possible implementation, the memory is located within the above-mentioned second communication device.
[0062] In the present application, the processor and the memory may also be integrated into one device, that is, the processor and the memory may also be integrated together.
[0063] In combination with the fourteenth aspect, in a possible implementation, the communication device also includes a transceiver, and the transceiver is used to receive frames or send frames.
[0064] In a fifteenth aspect, the present application provides a communication device, which includes a logic circuit and an interface, and the logic circuit and the interface are coupled.
[0065] In one design, a logic circuit is used to generate a first association request frame; an interface is used to output the first association request frame, the first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate a second link; the interface is also used 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 the first status code field is not 0, and is used to indicate that the first link is not accepted; the second status code field is set to a first value that is not 0, and is used to indicate that the reason why the second link is not accepted is that the first link is not accepted.
[0066] In one design, a logic circuit is used to generate a first association request frame; an interface is used to output the first association request frame, the first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate a second link; the interface is also used 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 the first status code field is not 0 and the value of the second status code field is 0, which are used to jointly indicate that the reason why the second link is not accepted is that the first link is not accepted.
[0067] In one design, a logic circuit is configured to generate a first association request frame; an interface is configured to output the first association request frame, the first association request frame including a multilink element, the multilink element including indication information, the indication information indicating a second link; and the interface is further configured to input a first association response frame, the first association response frame including a first status code field and a multilink element, the first status code field being set to a second value other than 0 to indicate that multilink establishment between a non-AP MLD and an AP MLD has failed and that multilink establishment 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 a reason why the second link was accepted or not accepted.
[0068] In a sixteenth aspect, the present application provides another communication device, which includes a logic circuit and an interface, and the logic circuit and the interface are coupled.
[0069] In one design, an interface is used to input a first association request frame, wherein the first association request frame includes a multilink element, and the multilink element includes indication information, wherein the indication information is used to indicate a second link; a logic circuit is used to generate a first association response frame; an interface is used to output the first association response frame, wherein the first association response frame includes a first status code field and a multilink element, wherein the multilink element of the first association response frame includes a second status code field, wherein the value of the first status code field is not 0, and is used to indicate that the first link is not accepted; and the second status code field is set to a first value that is not 0, and is used to indicate that the reason why the second link is not accepted is that the first link is not accepted.
[0070] In one design, an interface is used to input a first association request frame, the first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate a second link; a logic circuit is used to generate a first association response frame; and an interface is used to output the 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 the first status code field is not 0 and the value of the second status code field is 0, which are used to jointly indicate that the reason why the second link is not accepted is that the first link is not accepted.
[0071] In one design, an interface is configured to input a first association request frame, the first association request frame including a multilink element, the multilink element including indication information, the indication information indicating a second link; a logic circuit is configured to generate a first association response frame; and an interface is configured to output the first association response frame, the first association response frame including a first status code field and a multilink element, the first status code field being set to a second value other than 0, indicating that multilink establishment between a non-AP MLD and an AP MLD has failed and that multilink establishment 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 indicating the reason why the second link was accepted or not accepted.
[0072] In the seventeenth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program. When the computer program is run on a computer, the method shown in any possible implementation of the first aspect, the fifth aspect, the ninth aspect or any of them is executed.
[0073] In the eighteenth aspect, an embodiment of the present application provides a computer-readable storage medium, which is used to store a computer program. When the computer program is run on a computer, the method shown in the second aspect, the sixth aspect, the tenth aspect or any possible implementation of any aspect thereof is executed.
[0074] In the nineteenth aspect, an embodiment of the present application provides a computer program product, which includes a computer program or computer code, and when it runs on a computer, it enables the method shown in any possible implementation of the first aspect, the fifth aspect, the ninth aspect or any of the aspects above to be executed.
[0075] In the twentieth aspect, an embodiment of the present application provides a computer program product, which includes a computer program or computer code, and when it runs on a computer, it enables the method shown in any possible implementation of the second aspect, the sixth aspect, the tenth aspect or any of the aspects above to be executed.
[0076] In aspect 21, an embodiment of the present application provides a computer program. When the computer program is run on a computer, the method shown in any possible implementation of the first aspect, the fifth aspect, the ninth aspect or any one of them is executed.
[0077] In aspect 22, an embodiment of the present application provides a computer program. When the computer program runs on a computer, the method shown in the second aspect, the sixth aspect, the tenth aspect, or any possible implementation of any one of the aspects is executed.
[0078] In aspect 23, an embodiment of the present application provides a wireless communication system, which includes a non-AP MLD and an AP MLD, wherein the non-AP MLD is used to execute the method shown in the above-mentioned first aspect, the above-mentioned fifth aspect, the above-mentioned ninth aspect, or any possible implementation of any aspect therein, and the AP MLD is used to execute the method shown in the above-mentioned second aspect, the above-mentioned sixth aspect, the above-mentioned tenth aspect, or any possible implementation of any aspect therein.
[0079] In an embodiment of the present application, if one or more other links in a non-AP MLD could have been accepted (or successfully established) but could not be accepted because the link on which the non-AP MLD transmitted an association request frame was not accepted (or failed to establish), the non-AP MLD is notified of the non-AP MLD's failure to accept the one or more other links by using the status code field in the association response frame. In other words, the embodiment of the present application notifies the non-AP MLD, using the status code field in the association response frame, that the one or more other links could have been accepted (or successfully established) if an association request frame had been sent on the one or more other links. This allows the non-AP MLD to send association request frames on the one or more other links to establish multiple links, thereby increasing the likelihood of successful multi-link establishment. Furthermore, the non-AP MLD does not need to attempt to establish multiple links on each link, thereby reducing the number of attempts and improving the efficiency of multi-link establishment. BRIEF DESCRIPTION OF THE DRAWINGS
[0080] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for describing the embodiments.
[0081] FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;
[0082] FIG2 is a schematic diagram of multi-link communication provided by an embodiment of the present application;
[0083] FIG3a is a schematic structural diagram of a multi-link device provided in an embodiment of the present application;
[0084] FIG3 b is another schematic structural diagram of a multi-link device provided in an embodiment of the present application;
[0085] FIG4 is a flow chart of a method for establishing multi-link communication according to an embodiment of the present application;
[0086] FIG5 is a schematic diagram of a frame format of a multi-link element provided in an embodiment of the present application;
[0087] FIG6 is a schematic diagram of the frame format of an association response frame provided in an embodiment of the present application;
[0088] FIG7 is another schematic flow chart of a method for establishing multi-link communication according to an embodiment of the present application;
[0089] FIG8 is another schematic flow chart of a method for establishing multi-link communication according to an embodiment of the present application;
[0090] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application;
[0091] FIG10 is a schematic structural diagram of a communication device 1000 provided in an embodiment of the present application;
[0092] FIG11 is another schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0093] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application.
[0094] In the description of this application, unless otherwise specified, " / " means "or", for example, A / B can mean A or B. "And / or" in this article is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, "at least one" means one or more, and "plurality" means two or more. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c; a and b; a and c; b and c; or a, b, and c. Among them, a, b, and c can be single or multiple.
[0095] In the description of this application, words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit differences.
[0096] In this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary," "for example," or "for example" should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete way.
[0097] Elements used in the singular herein are intended to mean "one or more" rather than "one and only one" unless specifically stated otherwise.
[0098] A multi-link device can include multiple logical sites, each operating on a link. However, multiple logical sites can operate on the same link. During data transmission, AP MLD and non-AP MLD can use link identifiers to identify a link or a site on a link. Before communication, the AP MLD and non-AP MLD can negotiate or communicate the correspondence between the link identifier and a link or a site on a link. Therefore, during data transmission, there is no need to transmit a large amount of signaling information to indicate the link or the site on the link. The link identifier is sufficient, reducing signaling overhead and improving transmission efficiency.
[0099] Optionally, a multi-link device can implement wireless communications using the 802.11 family of protocols, such as an extremely high throughput (EHT) station or an 802.11be-based or 802.11be-compatible station, to communicate with other devices. Of course, other devices may or may not be multi-link devices.
[0100] The method provided in this application can be applied to wireless local area network (WLAN) systems, such as Wi-Fi, etc. For example, the method provided in this application can be applied to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series protocols, such as the 802.11ax next-generation Wi-Fi protocol, such as 802.11be, Wi-Fi 7 or extremely high throughput (EHT), and the next generation of 802.11be, Wi-Fi 8, etc., which are not listed here one by one. The method provided in this application can also be applied to wireless personal area network systems based on ultra wide band (UWB), sensing systems.
[0101] Although this application is mainly described using a network deploying IEEE 802.11 as an example, those skilled in the art will readily appreciate that the various aspects of this application can be extended to other networks that adopt various standards or protocols, such as high-performance wireless LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, primarily used in Europe), wide area networks (WANs), wireless local area networks (WLANs), personal area networks (PANs), or other networks now known or developed in the future.
[0102] Referring to FIG. 1 , FIG. 1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application. As shown in FIG. 1 , the wireless communication system includes at least one AP MLD (such as AP MLD 100 and AP MLD 200 in FIG. 1 ) and at least one non-AP MLD (such as non-AP MLD 300 in FIG. 1 ). Optionally, FIG. 1 may also include a traditional station that only supports transmission over a single link (such as single-link non-AP STA 400 in FIG. 1 , also referred to as STA 400). The AP MLD is a device that provides services to the non-AP MLD. The non-AP MLD can communicate with the AP MLD using multiple links, thereby improving throughput. A STA in the non-AP MLD can also communicate with an AP in the AP MLD via a single link. It is understood that FIG. 1 uses a mobile phone as an example of a non-AP MLD and a router as an example, and does not limit the types of AP MLDs and non-AP MLDs in this application. It is also understandable that the number of AP MLDs and non-AP MLDs in FIG1 is merely exemplary, and the number of AP MLDs or non-AP MLDs in the wireless communication system may be greater or lesser, which is not limited in this application.
[0103] In the embodiments of the present application, the term "communication" may also be described as "data transmission," "information transmission," or "transmission." The term "transmission" may generally refer to sending and receiving.
[0104] Optionally, refer to Figure 2, which is a schematic diagram of multi-link communication provided by an embodiment of the present application. As shown in Figure 2, AP MLD includes n sites, namely AP1, AP2, ..., APn; non-AP MLD also includes n sites, namely STA1, STA2, ..., STAn. The communication between MLDs is multi-link communication, and link 1 to link n in Figure 2 constitute a multi-link. In other words, AP MLD and non-AP MLD can communicate in parallel using link 1, link 2, ..., link n. Among them, an AP in AP MLD can establish an association relationship with a STA in non-AP MLD. For example, STA1 in non-AP MLD establishes an association relationship with AP1 in AP MLD, STA2 in non-AP MLD establishes an association relationship with AP2 in AP MLD, STAn in non-AP MLD establishes an association relationship with APn in AP MLD, and so on.
[0105] Optionally, refer to Figure 3a, which is a structural diagram of a multi-link device provided in an embodiment of the present application. The 802.11 standard focuses on the 802.11 physical layer (PHY) and medium access control (MAC) layer parts in the multi-link device. As shown in Figure 3a, the multiple STAs included in the multi-link device are independent of each other in the low MAC layer and the PHY layer, and are also independent of each other in the high MAC layer. Refer to Figure 3b, which is another structural diagram of the multi-link device provided in an embodiment of the present application. As shown in Figure 3b, the multiple STAs included in the multi-link device are independent of each other in the low MAC layer and the PHY layer, and share the high MAC layer. Of course, during multi-link communication, the non-AP MLD can adopt an independent high MAC layer structure, while the AP MLD adopts a shared high MAC layer structure; the non-AP MLD can also adopt a shared high MAC layer structure, while the AP MLD adopts an independent high MAC layer structure; the non-AP MLD and AP MLD can both adopt a shared high MAC layer structure; or the non-AP MLD and AP MLD can both adopt an independent high MAC layer structure. The embodiments of the present application do not limit the internal structure diagram of the multi-link device; Figures 3a and 3b are merely exemplary. For example, the high MAC layer and the low MAC layer can both be implemented by a processor in a chip system of the multi-link device, or can be implemented by different processing modules in a chip system.
[0106] The frequency bands in which the multi-link device operates may include one or more frequency bands of sub 1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high frequency 60 GHz.
[0107] For example, the multi-link device in the embodiments of the present application can be a single-antenna device or a multi-antenna device. For example, it can be a device with two or more antennas. The embodiments of the present application do not limit the number of antennas included in the multi-link device.
[0108] Exemplarily, a multi-link device (here, either a non-AP MLD or an AP MLD) is a device with wireless communication capabilities. This device can be a complete device or a chip or processing system installed in the complete device. Devices equipped with these chips or processing systems can implement the methods and functions of the embodiments of the present application under the control of these chips or processing systems. For example, the non-AP MLD in the embodiments of the present application has wireless transceiver capabilities, supports the 802.11 series of protocols, and can communicate with AP MLDs, single-link devices, or other non-AP MLDs. For example, a non-AP MLD is any user communication device that allows a user to communicate with an AP and, in turn, with a WLAN. For example, a non-AP MLD can be a tablet computer, desktop, laptop, notebook computer, ultra-mobile personal computer (UMPC), handheld computer, netbook, personal digital assistant (PDA), mobile phone, or other network-capable user device, or an IoT node in the Internet of Things (IoT), or an in-vehicle communication device in the Internet of Vehicles (IoV). A non-AP MLD can also be a chip or processing system in these terminals. The AP MLD can be a device that provides services to non-AP MLDs and can support the 802.11 series of protocols. For example, the AP MLD can be a communication entity such as a communication server, router, switch, or bridge. Alternatively, the AP MLD can include various forms of macro base stations, micro base stations, and relay stations. Of course, the AP MLD can also be a chip or processing system within these various devices, thereby implementing the methods and functions of the embodiments of the present application. The 802.11 protocol can be a protocol that supports or is compatible with 802.11be.
[0109] It is understandable that multi-link devices can support high-speed and low-latency transmission. With the continuous evolution of wireless LAN application scenarios, multi-link devices can also be applied to more scenarios, such as sensor nodes in smart cities (for example, smart water meters, smart electricity meters, smart air detection nodes), smart devices in smart homes (for example, smart cameras, projectors, displays, TVs, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (for example, wearable devices such as AR and VR), smart devices in smart offices (for example, printers, projectors, etc.), Internet of Vehicles devices in the Internet of Vehicles, and some infrastructure in daily life scenarios (for example, vending machines, self-service navigation counters in supermarkets, self-service cash registers, self-service ordering machines, etc.). The specific forms of non-AP MLD and AP MLD are not limited in the embodiments of this application and are only illustrative.
[0110] The present application provides a method and related apparatus for establishing multi-link communication, which can improve the efficiency of multi-link establishment (or multi-link association).
[0111] Typically, a non-AP MLD can establish associations with multiple links of an AP MLD simultaneously by performing a multi-link setup operation 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 single link (referred to as the first link for ease of description). This multi-link element carries information about other links, requesting multi-link communication with the AP MLD. After receiving the association request frame, the AP MLD sends an association response frame carrying a multi-link element on the first link to the non-AP MLD, informing it whether multi-link communication has been successfully established.
[0112] Generally speaking, if the link transmitting the association request frame in non-AP MLD (i.e., the first link) is not accepted (or the first link fails to be established), then all other links in non-AP MLD are also not accepted (or all other links fail to be established). However, the reasons for whether each link is accepted (or whether it is successfully established) may vary. For example, different links may have different loads; excessive load may be the reason for a link's non-AP MLD capabilities. Alternatively, the non-AP MLD capabilities on different links may vary; insufficient capabilities may also be the reason for a link's non-AP MLD capabilities. Therefore, the following situation may occur: when the link transmitting the association request frame in non-AP MLD (i.e., the first link) is not accepted (or the first link fails to be established), one or more other links may have been accepted (or successfully established), but due to the non-AP MLD's non-AP MLD capabilities, these links cannot be accepted (or fail to be established). Therefore, if the link on which the association request frame is transmitted in the non-AP MLD is not accepted (or the establishment fails), the non-AP MLD does not know whether it can successfully establish multilink communication with the AP MLD by sending an association request frame on other links. Therefore, the non-AP MLD can only send an association request frame on each link to try, which leads to low multilink establishment efficiency.
[0113] In an embodiment of the present application, if one or more other links in the non-AP MLD could have been accepted (or successfully established) but could not be accepted because the link that transmitted the association request frame was not accepted (or failed to be established), the non-AP MLD is notified of the non-AP MLD's non-acceptance of the one or more other links by using the status code field in the association response frame. In other words, the embodiment of the present application notifies the non-AP MLD, using the status code field in the association response frame, that the one or more other links could have been accepted (or successfully established) if the association request frame had been sent on the one or more other links. This allows the non-AP MLD to send association request frames on the one or more other links to establish multiple links, thereby increasing the likelihood of successful multi-link establishment. Furthermore, the non-AP MLD does not need to attempt to establish multiple links on each link, thereby reducing the number of attempts and improving the efficiency of multi-link establishment.
[0114] It is understandable that because the association request frame and the association response frame are transmitted on the same link, the "link for transmitting the association request frame" mentioned in this application is also the "link for transmitting the association response frame." The "other links" mentioned in this application refer to links in the non-AP MLD except the "link for transmitting the association request frame."
[0115] The technical solution provided in this application will be described in detail below with reference to more drawings.
[0116] In order to facilitate the clear description of the technical solution of the present application, the present application is described through a plurality of embodiments, and the specific embodiments are as follows. In the present application, unless otherwise specified, the same or similar parts between the various embodiments or implementation methods can refer to each other. In the various embodiments of the present application, and the various implementation methods / implementation methods / implementation methods in each embodiment, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The implementation methods of the present application described below do not constitute a limitation on the scope of protection of the present application.
[0117] Example 1
[0118] Embodiment 1 of the present application mainly introduces the method of extending the value of the Status Code field in the multi-link element (MLE) to indicate that the reason why a certain link of the non-AP MLD (this link is not the link that transmits the association request frame) is not accepted is that the link that transmits the association request frame in the non-AP MLD is not accepted.
[0119] Referring to Figure 4, Figure 4 is a flow chart of a method for establishing multi-link communication provided by an embodiment of the present application. As shown in Figure 4, the method for establishing multi-link communication includes but is not limited to the following steps:
[0120] S101: A first station of a non-AP MLD sends a first association request frame on a first link. The first association request frame includes a multilink element. The multilink element includes indication information. The indication information is used to indicate a second link.
[0121] Correspondingly, the first access point of AP MLD receives the first association request frame on the first link.
[0122] In the embodiment of the present application, non-AP MLD has at least two links, and AP MLD also has at least two links. It is understandable that the number of links in non-AP MLD and AP MLD can be equal or unequal, and this embodiment of the present application does not limit this.
[0123] Optionally, the first station is any station in a non-AP MLD, and the first link is a link on which the first station operates. That is, a station in a non-AP MLD (i.e., the first station in the embodiment of the present application) can send an association request frame (i.e., the first association request frame in the embodiment of the present application) on a link (i.e., the first link in the embodiment of the present application). The association request frame carries a multi-link element (MLE), and the multi-link element carries information about other links (such as the second link described below), thereby requesting to establish multi-link communication with the AP MLD. The specific frame format and function of the first association request frame can be found in the description of existing standards and will not be elaborated in detail in the embodiment of the present application.
[0124] Optionally, the multi-link element included in the above-mentioned first association request frame carries indication information, and the indication information is used to indicate a second link. The second link is a link in the non-AP MLD other than the first link, that is, the other link mentioned above. It can be understood that the second link is a link other than the first link among the links that the non-AP MLD wants to establish multi-links with the AP MLD. For example, there are three links in the non-AP MLD, namely link 1, link 2, and link 3; if the non-AP MLD wants to establish multi-links (or establish multi-link communication) with the AP MLD on link 1 and link 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. For example, a non-AP MLD has three links: link 1, link 2, and link 3. If the non-AP MLD wants to establish multi-link communication with the AP MLD on links 1, 2, and 3, and sends an association request frame on link 1, link 1 is the primary link, and link 2 and link 3 are both secondary links.
[0125] Optionally, the above-mentioned indication information is carried in the STA control field of the Per-STA Profile subelement of the multi-link element. For example, the indication information may be the link ID subfield in the STA Control field. It is understandable that a link ID subfield is used to identify a second link. It is also understandable that the value and meaning of the link ID subfield can be referred to the meaning of the existing standard and will not be described in detail here.
[0126] Refer to Figure 5, which is a schematic diagram of the frame format of the multi-link element provided in an embodiment of the present application. As shown in Figure 5, the multi-link element includes but is not limited to: a multi-link control (Multi-Link Control) field, a common information (Common Info) field, and a link information (Link Info) field. Among them, the multi-link control field carries the type of this multi-link element and an indication of which fields in the common information field exist and which fields do not exist. The common information field carries information about the multi-link device itself (this is MLD-level information, i.e., MLD-level info) and common information about multiple sites in this multi-link device. The link information field carries information about the sites on each link in the multi-link device. It is understandable that the specific meaning of each field in the multi-link element can be referred to the description of the existing standard, and will not be described in detail here. It is also understandable that Figure 5 only shows some of the fields in the multi-link element. The specific frame format of the multi-link element can be referred to the description of the existing standard, and will not be repeated here.
[0127] As shown in Figure 5, the link information field includes one or more Per-STA Profile subelement (each STA profile subelement). A Per-STA Profile subelement carries information about a station on a link. The Per-STA Profile subelement includes a STA Control field, which includes a link ID subfield. The Link ID subfield specifies a value that uniquely identifies the link where the reported STA is operating on. That is, the link identification subfield is used to indicate a link. It is understandable that the reported STA here in this application refers to the STA operating on the second link.
[0128] It is understandable that if the multi-link element carried in the association request frame includes multiple Per-STA Profile subelements, then there are multiple link identification subfields, that is, there are multiple second links.
[0129] 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 not 0, indicating that the first link is not accepted; the second status code field is set to a first value that is not 0, indicating that the reason why the second link is not accepted is that the first link is not accepted.
[0130] Accordingly, the non-AP MLD first station receives the first association response frame on the first link. The non-AP MLD first station can learn from the first status code field and the second status code field of the first association response frame whether the first link is accepted (or whether multi-link communication is successfully established, or whether multi-link establishment is successful) and whether the second link is accepted (including the reason why the second link is not accepted).
[0131] Optionally, the first access point is an access point working on the first link in the AP MLD.
[0132] Optionally, the first status code field can be used to indicate whether the first link (or the link that transmits the first association request frame) is accepted, or whether it is successfully established, or whether it becomes a link in multi-link communication. If the first link is accepted (if the link is accepted), the first status code field should indicate success; if the first link is not accepted, the first status code field indicates 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, it indicates success (SUCCESS), that is, the first link is received; in other words, when the value of the first status code field is not 0, it indicates that the first link is not accepted or the reason for not accepting it. Specifically, the value and meaning of the first status code can refer to the existing standards and will not be explained in detail here.
[0133] It is understandable that "not accepted" and "not accepted" in this application have the same meaning, for example, both refer to not being accepted, not being established successfully, or not becoming a link in multi-link communication, etc., which are the same or similar meanings.
[0134] Optionally, if the first link is accepted, multi-link setup between the non-AP MLD and the AP MLD may succeed, or multi-link communication between the non-AP MLD and the AP MLD may be successfully established. However, if the first link is not accepted, multi-link setup between the non-AP MLD and the AP MLD fails, or multi-link communication between the non-AP MLD and the AP MLD fails. Therefore, 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 multi-link setup between the non-AP MLD and the AP MLD fails, or multi-link communication between the non-AP MLD and the AP MLD fails. In other words, when the value of the first status code field is not 0, it can not only indicate that the first link is not accepted or the reason for the non-acceptance; it can also indicate that the multi-link establishment between the non-AP MLD and the AP MLD has failed, or that the multi-link communication establishment between the non-AP MLD and the AP MLD has failed.
[0135] Optionally, the second status code field can be used to indicate whether the second link is accepted, or whether it is successfully established, or whether it becomes a link in multi-link communication. If the second link is accepted, the second status code field should indicate success; if the second link is not accepted, the second status code field indicates the failure cause (the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement shall indicate SUCCESS if the link is accepted or the failure cause if the link is not accepted). When the second status code field is set to 0, it indicates success (SUCCESS), that is, the second link is received; in other words, when the value of the second status code field is not 0, it indicates that the second link is not accepted or the reason for not accepting it.
[0136] Optionally, the embodiment of the present application newly defines a first value that is not 0, as shown in Table 1 below; when the second status code field is set to the first value, it is used to indicate that the reason why the second link is not accepted is that the first link is not accepted; or it is used to indicate that the reason why the second link is not accepted is simply that the first link is not accepted. In other words, when the second status code field is set to the first value, it means that if the non-AP MLD sends an association request frame on this second link, the second link can be successfully established. Among them, the value of the first status code field cannot be the first value of the embodiment of the present application. In other words, only the second status code field can take this first value.
[0137] The first value may be a value that is not used or defined in the existing status code field. For example, assuming that the length of the status code field is n bits, the first value may be 0 to (2 n -1) except the existing value. For example, n is equal to 16. The existing values here include: 0 to 135, or values between 0 and 135 except the reserved values (4, 8-9, 20-21, 26, 29, 36, 48, 66, 69-71, 90-91, 114-115, 127). For example, the first value is 0 to (2 16 -1) except 0 to 135, such as 136, or 137, or 138, or 139. For another example, the first value is any reserved value from 0 to 135, such as any value from 4, 8-9, 20-21, 26, 29, 36, 48, 66, 69-71, 90-91, 114-115, and 127.
[0138] Table 1
[0139]
[0140] It should be understood that in this application, the link for exchanging association request / response frames can be referred to as a transmitted link, and correspondingly, other links are referred to as non-transmitted links. Therefore, in the aforementioned steps S101 and S102, the first link is a transmitted link, and the second link is a non-transmitted link. Therefore, when the second status code field is set to the first value, the meaning can also be described as: the reason why the non-transmitted link is not accepted is that the transmitted link is not accepted.
[0141] Optionally, the first status code field may be located in the frame body of the association response frame. Exemplarily, the first status code field may be located outside the multi-link element of the association response frame. In other words, the first status code field is not in the multi-link element of the association response frame (the Status Code field not in the multi-link element of the Association Response frame). Alternatively, the first status code field is in the core frame of the association response frame (the Status Code field in the core frame of the Association Response frame), where the core frame may be the content of the association response frame other than the multi-link element (MLE). The second status code field may be located in the multi-link element of the association response frame. Exemplarily, the second status code field is the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement.
[0142] Referring to Figure 6, Figure 6 is a schematic diagram of the frame format of the association response frame provided in an embodiment of the present application. As shown in Figure 6, the association response frame includes but is not limited to: a status code (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 (Multi-Link Control) field, a common information (Common Info) field, and a link information (Link Info) field. The link information (Link Info) field includes one or more Per-STA Profile subelement (each STA profile subelement). The Per-STA Profile subelement includes but is not limited to: a STA Control (STA Control) field and a STA Profile (STA Profile) field. The STA Control field includes a link identification (link ID) subfield, which is used to indicate a second link (or non-transmission link). The STA Profile field includes a status code (Status Code) field (i.e., a second status code field) for indicating whether the link indicated by the link ID subfield is accepted. It is understandable that Figure 6 only shows some fields in the association response frame. The specific frame format of the association response frame can be found in the description of the existing standard and is not repeated here. It is also understandable that the specific meaning of each field in the association response frame can also refer to the description of the existing standard, and will not be described in detail here.
[0143] Optionally, in an embodiment of the present application, the multilink element of the first association response frame includes one or more second status code fields, where a second status code field is used to indicate whether a non-transmission link is accepted. When a non-transmission link in the non-AP MLD could have been accepted (or successfully established) but cannot be accepted because the transmission link is not accepted (or fails to be established), the AP MLD may set the second status code field corresponding to the non-transmission link to a first value to indicate that the reason the non-transmission link is not accepted is that the transmission link is not received, or to inform the non-AP MLD that if it sends an association request frame on the non-transmission link, the non-transmission link can be accepted (or successfully established). It is understandable that when the second status code field is set to the first value to 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 should be set to a value other than 0.
[0144] In an embodiment of the present application, if one or more non-transmission links in a non-AP MLD could have been accepted (or successfully established) but could not be accepted because a transmission link was not accepted (or failed to be established), the value of the first status code field in the association response frame is not 0. The second status code field (the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement) in the multilink element of the association response frame is set to a newly defined value (i.e., a first value) to indicate that the reason why the one or more non-transmission links were not accepted was that the transmission link was not accepted. In other words, setting the second status code field to the first value notifies the non-AP MLD that if an association request frame is sent on the one or more non-transmission links, the one or more non-transmission links can be accepted (or successfully established). Therefore, using this embodiment of the present application, the possibility of successful multi-link establishment can be increased. The non-AP MLD does not need to attempt to establish a connection on each link, thereby reducing the number of attempts and improving the efficiency of multi-link establishment.
[0145] Optionally, in the first association response frame of the embodiment of the present application, at least one second status code field having a value of the first value is used to indicate that the reason why at least one second link was not received was that the first link was not accepted. For ease of description, the embodiment of the present application is described using the example of a case where the value of the second status field in the first association response frame having the first value is present.
[0146] Optionally, after step S102, the method for establishing multi-link communication may further include one or more of the following steps:
[0147] S103: The second station of the non-AP MLD sends a second association request frame on the second link.
[0148] Correspondingly, the second access point of AP MLD receives the second association request frame on the second link.
[0149] It can be understood that according to the definition of a transmitted link (the link for exchanging association request / response frames is called a transmitted link), in the process from step S103 to step S104, the aforementioned first link is no longer a transmitted link and becomes a non-transmitted link, while the second link here is a transmitted link.
[0150] S104: The second access point of the AP MLD sends a second association response frame on the second link.
[0151] Correspondingly, the second station of the non-AP MLD receives the second association response frame on the second link.
[0152] Optionally, because the value of a second status code field in the first association response frame is the first value, the non-AP MLD can determine that the reason the second link corresponding to the second status code field was not accepted is because the first link was not accepted, or can determine that the reason the second link was not successfully established is simply because the first link was not successfully established, or can further determine that if the non-AP MLD sends an association request frame on the second link, the second link can be successfully established. Therefore, if the first link is not accepted (i.e., the value of the first status code field in the first association response frame is not 0) and the value of a second status code field in the first association response frame is the first value, the second station of the non-AP MLD can send a second association request frame on the second link corresponding to the second status code field, requesting to establish an association with the AP MLD on at least the second link. Accordingly, after receiving the second association request frame on the second link, the second access point of the AP MLD responds with a second association response frame on the second link to indicate whether the association was successfully established.
[0153] It is understood that the exchange of the second association request frame and the second association response frame between the non-AP MLD and the AP MLD can be for multilink establishment or for establishing an association only for the second link; this is not limited in this embodiment of the present application. In other words, whether the second association request frame and the second association response frame carry the multilink element is not limited in this embodiment of the present application. It is also understood that if the exchange of the second association request frame and the second association response frame between the non-AP MLD and the AP MLD is for multilink establishment, multilink communication may not be established on the first link at this time. In other words, if the second association request frame carries the multilink element, the multilink element may not carry information about the first link. This is because during the previous multilink establishment process (such as steps S201 and S202 described above), the first link was not accepted (i.e., the establishment was not successful). At this time, sending the second association request frame on the second link to establish the multilink will likely result in the first link still not being accepted (i.e., the establishment will not be successful). Therefore, not carrying information about the first link (in this case, the first link is a non-transmission link) in the multilink element of the second association request frame can increase the likelihood of successful multilink establishment this time. Of course, the information of the first link may also be carried in the multilink element of the second association request frame, because compared with the situation on the first link during the last multilink establishment (such as the aforementioned steps S201 and S202), the situation of the first link may have changed at this time, so it may be accepted (i.e., it may be established successfully).
[0154] In this embodiment of the present application, by setting the second status code field in the multilink element of the association response frame to a newly defined value (i.e., the first value), the non-AP MLD is informed that if an association request frame is sent on the link corresponding to the second status code field, the link will be accepted (or successfully established). This allows the non-AP MLD to know which links are most likely to successfully establish multilink communication by sending the association request frame, thereby increasing the probability of successful multilink establishment, reducing the number of attempts, and improving the efficiency of multilink establishment.
[0155] Example 2
[0156] The second embodiment of the present application mainly introduces the use of a status code field (i.e., a first status code field) outside the multilink element of the association response frame and a status code field (i.e., a second status code field) within the multilink element to jointly indicate that the reason why a link of the non-AP MLD is not accepted is that the link transmitting the association request frame in the non-AP MLD is not accepted.
[0157] Referring to Figure 7, Figure 7 is another flow chart of a method for establishing multi-link communication provided by an embodiment of the present application. As shown in Figure 7, the method for establishing multi-link communication includes but is not limited to the following steps:
[0158] S201: A first station of a non-AP MLD sends a first association request frame on a first link. The first association request frame includes a multilink element. The multilink element includes indication information. The indication information is used to indicate a second link.
[0159] Correspondingly, the first access point of AP MLD receives the first association request frame on the first link.
[0160] The implementation of step S201 in the embodiment of the present application refers to the implementation of step S101 in the aforementioned embodiment 1, and will not be repeated here.
[0161] S202, the first access point of 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 first status code field is set to a value indicating that the first link is not accepted or to a value indicating the reason why the first link is not accepted, and the second status code field is set to a value indicating that the second link is accepted, which is used to jointly indicate that the reason why the second link is not accepted is that the first link is not accepted.
[0162] Accordingly, the first station of the non-AP MLD receives the first association response frame on the first link. The first station of the non-AP MLD can determine, based on the values of the first status code field and the second status code field in the first association response frame, that the reason why the second link was not accepted is that the first link was not accepted.
[0163] Optionally, the first access point is an access point working on the first link in the AP MLD.
[0164] Optionally, the first status code field can be used to indicate whether the first link (or the link that transmits the first association request frame) is accepted, or whether it is successfully established, or whether it becomes a link in multi-link communication. Exemplarily, when the first status code field is set to 0, it indicates success (SUCCESS), that is, the first link is received; in other words, when the value of the first status code field is not 0, it indicates that the first link is not accepted or the reason for not accepting it. The second status code field can be used to indicate whether the second link is accepted, or whether it is successfully established, or whether it becomes a link in multi-link communication. Exemplarily, when the second status code field is set to 0, it indicates success (SUCCESS), that is, the second link is received; in other words, when the value of the second status code field is not 0, it indicates that the second link is not accepted or the reason for not accepting it. Then, the above-mentioned first status code field is set to a value indicating that the first link is not accepted or to a value indicating the reason why the first link is not accepted, and the above-mentioned second status code field is set to a value indicating that the second link is accepted, which is used to jointly indicate that the reason why the second link is not accepted is that the first link is not accepted. It can also be described as: the value of the first status code field is not 0 and the value of the second status code field is 0, which is used to jointly indicate that the reason why the second link is not accepted is that the first link is not accepted.
[0165] Optionally, the relationship between whether the first link is accepted and whether the multi-link is successfully established can be found in the related description of the first embodiment above, which will not be repeated here.
[0166] Optionally, the first status code field may be located in the frame body of the association response frame. Exemplarily, the first status code field may be located outside the multilink element of the association response frame. In other words, the first status code field is not in the multilink element of the association response frame. In other words, the first status code field is in the core frame of the association response frame, where the core frame may be the content of the association response frame other than the multilink element (MLE). The second status code field may be located in the multilink element of the association response frame. Exemplarily, the second status code field is the status code field contained in the STA Profile field of the Per-STA Profile subelement. The frame format of the association response frame is shown in FIG6 above and will not be described here.
[0167] Optionally, in an embodiment of the present application, the multilink element of the first association response frame includes one or more second status code fields, where a second status code field is used to indicate whether a non-transmission link is accepted. When a non-transmission link could have been accepted (or successfully established) but cannot be accepted because the transmission link is not accepted (or fails to be established), the AP MLD may set the first status code field to a non-zero value and set the second status code field corresponding to the non-transmission link to 0, thereby jointly indicating that the reason why the non-transmission link was not accepted (or not successfully established) was that the transmission link was not accepted (or not successfully established), or jointly indicating that the reason why the non-transmission link was not accepted was simply that the transmission link was not accepted, or informing the non-AP MLD that if it sends an association request frame on the non-transmission link, the non-transmission link can be accepted (or successfully established).
[0168] In other words, if the first status code field does not indicate SUCCESS (that is, the first status code field indicates that the first link is not accepted or the reason for not accepting it, or the value of the first status code field is not 0), and the second status code field indicates SUCCESS (that is, the second status code field indicates that the second link is accepted, or the value of the second status code field is 0); then it means that the reason why the second link is not accepted is that the first link is not accepted.
[0169] In other words, the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement shall indicate SUCCESS if the link is accepted or the failure cause if the link is not accepted with the exception below: 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.
[0170] Alternatively, when the status code field (i.e., the first status code field) outside the multi-link element in the association response frame does not indicate success, and the status code field (i.e., the second status code field) of the STA Profile subfield in the Per-STA Profile subelement corresponding to the second link indicates success, the second link is not accepted, but if the association request frame is sent on the second link, the second link can be accepted (When the Status Code field not in the multi-link element of the Association Response frame does not indicate SUCCESS, and the Status Code field included in the STA Profile subfield of the Per-STA Profile subelement indicates SUCCESS, the corresponding link is not accepted, but can be accepted if the Association Request frame is transmitted on that link).
[0171] In the embodiment of the present application, by designing setting rules and corresponding interpretation rules for the first status code field and the second status code field, when the first status code field does not indicate SUCCESS but the second status code field indicates SUCCESS, it indicates that the reason why the link corresponding to the second status code field is not accepted is that the first link is not accepted; so that the non-AP MLD knows that if an association request frame is sent on this link to establish multiple links, the possibility of success is high, thereby increasing the possibility of successful multi-link establishment, reducing the number of attempts, and improving the efficiency of multi-link establishment.
[0172] Optionally, in the first association response frame of the embodiment of the present application, the value of the first status code field is not 0, and at least one second status code field has a value of 0, which is used to jointly indicate that the reason why at least one second link was not received is that the first link was not accepted. For ease of description, the embodiment of the present application is described using the example of a case where the value of the second status field in the first association response frame is 0.
[0173] Optionally, after step S202, the method for establishing multi-link communication may further include:
[0174] S203: The second station of the non-AP MLD sends a second association request frame on the second link.
[0175] Correspondingly, the second access point of AP MLD receives the second association request frame on the second link.
[0176] It can be understood that according to the definition of a transmitted link (the link for exchanging association request / response frames is called a transmitted link), in the process from step S103 to step S104, the aforementioned first link is no longer a transmitted link and becomes a non-transmitted link, while the second link here is a transmitted link.
[0177] S204: The second access point of AP MLD sends a second association response frame on the second link.
[0178] Correspondingly, the second station of the non-AP MLD receives the second association response frame on the second link.
[0179] The implementation of step S203-step S204 in the embodiment of the present application refers to the implementation of step S103-step S104 in the aforementioned embodiment 1, and will not be repeated here.
[0180] In an embodiment of the present application, if one or more non-transmission links in a non-AP MLD could have been accepted (or successfully established) but could not be accepted because a transmission link was not accepted (or failed to be established), the first status code field in an association response frame is set to a value other than 0, and the second status code field in a multilink element of the association response frame is set to 0 (or set to indicate SUCCESS), thereby jointly indicating that the reason a non-transmission link was not accepted was that the transmission link was not accepted, or notifying the non-AP MLD that if an association request frame is sent on this non-transmission link, this non-transmission link can be accepted (or successfully established). This not only increases the probability of successful multi-link establishment, but also eliminates the need for the non-AP MLD to attempt to establish a connection on each link, thereby reducing the number of attempts and improving the efficiency of multi-link establishment. It also eliminates the need to define new status code values, saving overhead.
[0181] Example 3
[0182] Example 3 of the present application mainly introduces indicating the failure of multi-link establishment by extending the value of the status code field (i.e., the first status code field) outside the multi-link element located in the association response frame; further, it is also possible to set the value of the status code field (i.e., the second status code field) in the multi-link element to jointly indicate that the reason why the link corresponding to the second status code field is not accepted is that the transmission link is not accepted.
[0183] Referring to Figure 8, Figure 8 is another flow chart of a method for establishing multi-link communication provided in an embodiment of the present application. As shown in Figure 8, the method for establishing multi-link communication includes but is not limited to the following steps:
[0184] S301: A first station of a non-AP MLD sends a first association request frame on a first link. The first association request frame includes a multilink element. The multilink element includes indication information. The indication information is used to indicate a second link.
[0185] Correspondingly, the first access point of AP MLD receives the first association request frame on the first link.
[0186] The implementation method of step S301 in the embodiment of the present application refers to the implementation method of step S101 in the aforementioned embodiment 1, and will not be repeated here.
[0187] 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, where the first status code field is set to a second value other than 0, indicating that multi-link establishment with the non-AP MLD and the AP MLD has failed and that multi-link establishment may succeed if an association request frame is transmitted on another requested link.
[0188] Correspondingly, the first station of the non-AP MLD receives the first association response frame on the first link.
[0189] Optionally, the first access point is an access point working on the first link in the AP MLD.
[0190] 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, where a second status code field is used to indicate whether a link is accepted or not accepted, or the reason for not accepting the link. The specific meaning of the second status code field is described in the previous embodiment 1 and is not repeated here.
[0191] Optionally, the embodiment of the present application defines a new second value, which is a value that has not been used or defined in the existing status code field. For example, assuming that the length of the status code field is n bits, the second value can be 0 to (2 n -1) except the existing value. For example, n is equal to 16. The existing values here include but are not limited to: 0 to 135, or values from 0 to 135 except the reserved values (4, 8-9, 20-21, 26, 29, 36, 48, 66, 69-71, 90-91, 114-115, 127). For example, the second value is 0 to (2 16-1) except any value from 0 to 135, such as 136, or 137, or 138, or 139. For another example, the first value is any reserved value from 0 to 135, such as any value from 4, 8-9, 20-21, 26, 29, 36, 48, 66, 69-71, 90-91, 114-115, or 127. It is understandable that the second value in the embodiment of the present application is different from the first value in the aforementioned embodiment 1.
[0192] As shown in Table 2 below, when the first status code field is set to the second value, it indicates that multilink establishment between the non-AP MLD and AP MLD has failed; or, it indicates that multilink establishment between the non-AP MLD and AP MLD has failed and that multilink establishment may succeed if an association request frame is transmitted on another requested link (referring to a link other than the first link). The value of the second status code field cannot be the second value of the embodiment of the present application. In other words, the second value can only be the first status code field.
[0193] Table 2
[0194]
[0195]
[0196] It should be understood that when the value of the first status code field is an existing value (e.g., 0 to 135), it is used to indicate whether the first link (or the link that transmitted the first association request frame) was accepted, or whether it was successfully established, or whether it became a link in multi-link communication; for details, please refer to the relevant description in the above embodiment 1, which is not repeated here. When the value of the first status code field is the second value, it is used to indicate that the multi-link establishment failed, or that the multi-link establishment failed, but that the association request could succeed if transmitted on other requested links.
[0197] In this embodiment of the present application, the first status code field in the association response frame is set to a newly defined value (i.e., the second value) to indicate that multilink establishment has failed but one link exists. When an association request frame is transmitted on this link, multilink establishment can succeed. This allows the non-AP MLD to know whether multilink establishment with the AP MLD is likely to succeed, thereby avoiding the problem of the non-AP MLD repeatedly attempting to establish multilink communication when the probability of successful establishment is low, which would result in high power consumption for the non-AP MLD.
[0198] Optionally, the first status code field may be located in the frame body of the association response frame. Exemplarily, the first status code field may be located outside the multilink element of the association response frame. In other words, the first status code field is not in the multilink element of the association response frame. In other words, the first status code field is in the core frame of the association response frame, where the core frame may be the content of the association response frame other than the multilink element (MLE). The second status code field may be located in the multilink element of the association response frame. Exemplarily, the second status code field is the status code field contained in the STA Profile field of the Per-STA Profile subelement. The frame format of the association response frame is shown in FIG6 above and will not be described here.
[0199] Optionally, when a non-transmission link could have been accepted (or established successfully) but cannot be accepted due to a failure in multi-link establishment (for example, the transmission link is not accepted), the AP MLD can set the first status code field to the second value and the second status code field corresponding to the non-transmission link to 0, which is used to jointly indicate that the multi-link establishment failed and that the multi-link establishment may succeed if an association request frame is transmitted on the non-transmission link; or to jointly indicate that the reason why the non-transmission link is not accepted is that the transmission link is not accepted (or the multi-link establishment fails).
[0200] In other words, if the first status code field is set to the second value and the second status code field indicates SUCCESS (that is, the second status code field indicates that the second link is accepted, or the value of the second status code field is 0), it indicates that the multi-link establishment has failed and the multi-link establishment may succeed if the association request frame is transmitted on the second link, or it indicates that the reason why the second link is not accepted is that the first link is not accepted (or the multi-link establishment fails).
[0201] Optionally, in the first association response frame of an embodiment of the present application, the first status code field is set to a second value, and at least one second status code field has a value of 0, which is used to jointly indicate that multi-link establishment has failed and that multi-link establishment may succeed if an association request frame is transmitted on at least one second link corresponding to the at least one second status code field. For ease of description, the embodiment of the present application is described using the example of a case where the value of the second status field in the first association response frame is 0.
[0202] Optionally, after step S302, the method for establishing multi-link communication may further include:
[0203] S303: The second station of the non-AP MLD sends a second association request frame on the second link.
[0204] Correspondingly, the second access point of AP MLD receives the second association request frame on the second link.
[0205] It can be understood that according to the definition of a transmitted link (the link for exchanging association request / response frames is called a transmitted link), in the process from step S103 to step S104, the aforementioned first link is no longer a transmitted link and becomes a non-transmitted link, while the second link here is a transmitted link.
[0206] S304: The second access point of the AP MLD sends a second association response frame on the second link.
[0207] Correspondingly, the second station of the non-AP MLD receives the second association response frame on the second link.
[0208] The implementation of step S303-step S304 in the embodiment of the present application refers to the implementation of step S303-step S304 in the aforementioned embodiment 1, and will not be repeated here.
[0209] In the embodiment of the present application, the first status code field in the association response frame is set to a newly defined value (i.e., the second value), and the second status code field in the multilink element of the association response frame is set to 0 (or set to indicate SUCCESS), thereby jointly indicating that the multilink establishment has failed and that the multilink establishment may succeed if the association request frame is transmitted on the link corresponding to the second status code field. This allows the non-AP MLD to know on which links sending the association request frame can successfully establish multilink communication, thereby increasing the possibility of successful multilink establishment, reducing the number of attempts, and improving the efficiency of multilink establishment.
[0210] The above content elaborates on the method provided by the present application. In order to facilitate the implementation of the above scheme of the embodiment of the present application, the embodiment of the present application also provides corresponding devices or equipment.
[0211] Based on the above-mentioned method embodiment, this application divides the AP MLD and non-AP MLD into functional modules. For example, each functional module can be divided into corresponding functional modules, or two or more functions can be integrated into a single processing module. The integrated modules can be implemented as either hardware or software functional modules. It should be noted that the module division in this application is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used. The AP MLD and non-AP MLD of the present embodiment are described in detail below with reference to Figures 9 to 11.
[0212] Refer to Figure 9, which is a structural diagram of a communication device provided in an embodiment of the present application. As shown in Figure 9, the communication device includes a transceiver unit 10 and a processing unit 20.
[0213] In some embodiments of the present application, the communication device may be the non-AP MLD described above. Specifically, the communication device shown in Figure 9 may be used to execute the steps or functions performed by the non-AP MLD in the method embodiments described above. For example, the communication device may be a non-AP MLD or a chip, etc., which is not limited in the present embodiments.
[0214] In one design, the transceiver unit 10 is configured to send a first association request frame on a first link and receive a first association response frame on the first link. The first association request frame includes a multilink element, and the multilink element includes indication information, where the indication information is used to indicate a second 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, wherein the value of the first status code field is not 0, indicating that the first link is not accepted; and the second status code field is set to a first value that is not 0, indicating that the reason why the second link is not accepted is that the first link is not accepted.
[0215] Exemplarily, the processing unit 20 is configured to generate a first association request frame, and transmit the first association request frame through or by controlling the transceiver unit 10 .
[0216] In a possible implementation, the transceiver unit 10 is further configured to send a second association request frame on the second link, and receive a second association response frame on the second link.
[0217] Exemplarily, the processing unit 20 is configured to generate a second association request frame, and transmit the second association request frame through or by controlling the transceiver unit 10 .
[0218] It is understandable that for detailed descriptions of the first association request frame, the first association response frame, the second association request frame, and the second association response frame, reference may be made to the method embodiments shown above, and they will not be described in detail here.
[0219] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above method embodiment (such as Figure 4), which will not be described in detail here.
[0220] In another design, the transceiver unit 10 is configured to send a first association request frame on a first link and receive a first association response frame on the first link. The first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate the 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 not 0 and the value of the second status code field is 0, which are used to jointly indicate that the reason why the second link was not accepted is that the first link was not accepted.
[0221] Exemplarily, the processing unit 20 is configured to generate a first association request frame, and transmit the first association request frame through or by controlling the transceiver unit 10 .
[0222] In a possible implementation, the transceiver unit 10 is further configured to send a second association request frame on the second link, and receive a second association response frame on the second link.
[0223] Exemplarily, the processing unit 20 is configured to generate a second association request frame, and transmit the second association request frame through or by controlling the transceiver unit 10 .
[0224] It is understandable that for detailed descriptions of the first association request frame, the first association response frame, the second association request frame, and the second association response frame, reference may be made to the method embodiments shown above, and they will not be described in detail here.
[0225] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above method embodiment (such as Figure 7), which will not be described in detail here.
[0226] In another design, transceiver unit 10 is configured to send a first association request frame on a first link and receive a first association response frame on the first link. The first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate the second link. The first association response frame includes a first status code field, the first status code field is set to a second value other than 0, and is used to indicate that multilink establishment between the non-AP MLD and the AP MLD failed and that multilink establishment may succeed if the association request frame is transmitted on another requested link.
[0227] Exemplarily, the processing unit 20 is configured to generate a first association request frame, and transmit the first association request frame through or by controlling the transceiver unit 10 .
[0228] In a possible implementation, the transceiver unit 10 is further configured to send a second association request frame on the second link, and receive a second association response frame on the second link.
[0229] Exemplarily, the processing unit 20 is configured to generate a second association request frame, and transmit the second association request frame through or by controlling the transceiver unit 10 .
[0230] It is understandable that for detailed descriptions of the first association request frame, the first association response frame, the second association request frame, and the second association response frame, reference may be made to the method embodiments shown above, and they will not be described in detail here.
[0231] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above method embodiment (such as Figure 8), which will not be described in detail here.
[0232] Referring to Figure 9 , in other embodiments of the present application, the communication device may be the AP MLD shown above. Specifically, the communication device shown in Figure 9 may be used to execute the steps or functions performed by the AP MLD in the method embodiments described above. For example, the communication device may be an AP MLD or a chip, etc., but this embodiment of the present application is not limited thereto.
[0233] In one design, the transceiver unit 10 is configured to receive a first association request frame on a first link and send a first association response frame on the first link. The first association request frame includes a multilink element, and the multilink element includes indication information, where the indication information is used to indicate a second 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, wherein the value of the first status code field is not 0, indicating that the first link is not accepted; and the second status code field is set to a first value that is not 0, indicating that the reason why the second link is not accepted is that the first link is not accepted.
[0234] Exemplarily, the processing unit 20 is configured to generate a first association response frame, and transmit the first association response frame through or by controlling the transceiver unit 10 .
[0235] In a possible implementation, the transceiver unit 10 is further configured to receive a second association request frame on the second link, and send a second association response frame on the second link.
[0236] Exemplarily, the processing unit 20 is configured to generate a second association response frame, and transmit the second association response frame through or by controlling the transceiver unit 10 .
[0237] It is understandable that for detailed descriptions of the first association request frame, the first association response frame, the second association request frame, and the second association response frame, reference may be made to the method embodiments shown above, and they will not be described in detail here.
[0238] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above method embodiment (such as Figure 4), which will not be described in detail here.
[0239] In another design, the transceiver unit 10 is configured to receive a first association request frame on a first link and send a first association response frame on the first link. The first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate the 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 not 0 and the value of the second status code field is 0, which are used to jointly indicate that the reason why the second link was not accepted is that the first link was not accepted.
[0240] Exemplarily, the processing unit 20 is configured to generate a first association response frame, and transmit the first association response frame through or by controlling the transceiver unit 10 .
[0241] In a possible implementation, the transceiver unit 10 is further configured to receive a second association request frame on the second link, and send a second association response frame on the second link.
[0242] Exemplarily, the processing unit 20 is configured to generate a second association response frame, and transmit the second association response frame through or by controlling the transceiver unit 10 .
[0243] It is understandable that for detailed descriptions of the first association request frame, the first association response frame, the second association request frame, and the second association response frame, reference may be made to the method embodiments shown above, and they will not be described in detail here.
[0244] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above method embodiment (such as Figure 7), which will not be described in detail here.
[0245] In another design, the transceiver unit 10 is configured to receive a first association request frame on a first link and send a first association response frame on the first link. The first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate the second link. The first association response frame includes a first status code field, the first status code field is set to a second value other than 0, indicating that multilink establishment between the non-AP MLD and the AP MLD failed and that multilink establishment may succeed if the association request frame is transmitted on another requested link.
[0246] Exemplarily, the processing unit 20 is configured to generate a first association response frame, and transmit the first association response frame through or by controlling the transceiver unit 10 .
[0247] In a possible implementation, the transceiver unit 10 is further configured to receive a second association request frame on the second link, and send a second association response frame on the second link.
[0248] Exemplarily, the processing unit 20 is configured to generate a second association response frame, and transmit the second association response frame through or by controlling the transceiver unit 10 .
[0249] It is understandable that for detailed descriptions of the first association request frame, the first association response frame, the second association request frame, and the second association response frame, reference may be made to the method embodiments shown above, and they will not be described in detail here.
[0250] It can be understood that the specific description of the transceiver unit and the processing unit shown in the embodiment of the present application is only an example. For the specific functions or execution steps of the transceiver unit and the processing unit, please refer to the above method embodiment (such as Figure 8), which will not be described in detail here.
[0251] The above describes the non-AP MLD and AP MLD embodiments of the present application. The following describes possible product forms for the non-AP MLD and AP MLD. It should be understood that any product that possesses the functions of the non-AP MLD described in Figure 9 above, or any product that possesses the functions of the AP MLD described in Figure 9 above, falls within the scope of protection of the embodiments of the present application. It should also be understood that the following description is merely illustrative and does not limit the product forms of the non-AP MLD and AP MLD embodiments of the present application to these examples.
[0252] In one possible implementation, in the communication device shown in FIG9 , the processing unit 20 may be one or more processors, the transceiver unit 10 may be a transceiver, or the transceiver unit 10 may be a sending unit and a receiving unit, the sending unit may be a transmitter, the receiving unit may be a receiver, and the sending unit and the receiving unit are integrated into one device, such as a transceiver. In the embodiment of the present application, the processor and the transceiver may be coupled, etc., and the embodiment of the present application does not limit the connection method between the processor and the transceiver. In the process of executing the above method, the process of sending information (such as sending a first association request frame, a first association response frame, a second association request frame, a second association response frame, etc.) in the above method can be understood as the process of the processor outputting the above information. When outputting the above information, the processor outputs the above information to the transceiver so that it is transmitted by the transceiver. After being output by the processor, the above information may also need to undergo other processing before reaching the transceiver. Similarly, the process of receiving information (such as receiving a first association request frame, a first association response frame, a second association request frame, a second association response frame, etc.) in the above method can be understood as the process of the processor receiving the input information. When the processor receives the input information, the transceiver receives the information and inputs it into the processor. Furthermore, after the transceiver receives the information, the information may need to be processed further before being input into the processor.
[0253] Referring to Figure 10, Figure 10 is a schematic diagram of the structure of a communication device 1000 provided in an embodiment of the present application. The communication device 1000 can be a first communication device or a second communication device, or a chip therein. Figure 10 only shows the main components of the communication device 1000. In addition to the processor 1001 and the transceiver 1002, the communication device may further include a memory 1003 and an input / output device (not shown).
[0254] Processor 1001 is primarily used to process communication protocols and communication data, control the entire communication device, execute software programs, and process software program data. Memory 1003 is primarily used to store software programs and data. Transceiver 1002 may include control circuitry and an antenna. The control circuitry is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input / output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.
[0255] When the communication device is powered on, the processor 1001 can 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 sent wirelessly, the processor 1001 performs baseband processing on the data to be sent and 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 to the outside in the form of electromagnetic waves through the antenna. When data is sent 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.
[0256] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely arranged independent of the communication device.
[0257] The processor 1001 , the transceiver 1002 , and the memory 1003 may be connected via a communication bus.
[0258] In one design, the communication device 1000 can be used to perform the functions of the non-AP MLD in the aforementioned embodiment 1: the processor 1001 can be used to generate the first association request frame sent in step S101 and the second association request frame sent in step S103 in Figure 4, and / or be used to perform other processes of the technology described in this document; the transceiver 1002 can be used to perform steps S101 and S103 in Figure 4, etc., and / or be used for other processes of the technology described in this document.
[0259] In another design, the communication device 1000 can be used to perform the functions of the AP MLD in the aforementioned embodiment one: the processor 1001 can be used to generate the first association response frame sent in step S102 of Figure 4 and the second association response frame sent in step S104, and / or for performing other processes of the technology described in this document; the transceiver 1002 can be used to perform steps S102 and S104 in Figure 7, and / or for other processes of the technology described in this document.
[0260] In one design, the communication device 1000 can be used to perform the functions of the non-AP MLD in the aforementioned embodiment 2: the processor 1001 can be used to generate the first association request frame sent in step S201 and the second association request frame sent in step S203 in Figure 7, and / or be used to perform other processes of the technology described in this document; the transceiver 1002 can be used to perform steps S201 and S203 in Figure 7, etc., and / or be used for other processes of the technology described in this document.
[0261] In another design, the communication device 1000 can be used to perform the functions of the AP MLD in the aforementioned embodiment 2: the processor 1001 can be used to generate the first association response frame sent in step S202 of Figure 7 and the second association response frame sent in step S204, and / or for performing other processes of the technology described in this document; the transceiver 1002 can be used to perform steps S202 and S204 in Figure 7, and / or for other processes of the technology described in this document.
[0262] In one design, the communication device 1000 can be used to perform the functions of the non-AP MLD in the aforementioned embodiment three: the processor 1001 can be used to generate the first association request frame sent in step S301 of Figure 8 and the second association request frame sent in step S303, and / or be used to perform other processes of the technology described in this document; the transceiver 1002 can be used to perform steps S301 and S303 in Figure 8, etc., and / or be used for other processes of the technology described in this document.
[0263] In another design, the communication device 1000 can be used to perform the functions of the AP MLD in the aforementioned embodiment three: the processor 1001 can be used to generate the first association response frame sent in step S302 of Figure 8 and the second association response frame sent in step S304, and / or for performing other processes of the technology described in this document; the transceiver 1002 can be used to perform steps S302 and S304 in Figure 8, and / or for other processes of the technology described in this document.
[0264] In any of the above designs, processor 1001 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.
[0265] In any of the above designs, processor 1001 may store instructions, which may be computer programs. The computer programs, when executed on processor 1001, may cause communication device 1000 to perform the methods described in the above method embodiments. The computer programs may be embedded in processor 1001, in which case processor 1001 may be implemented by hardware.
[0266] In one implementation, the communication device 1000 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit (RFIC), a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.
[0267] The scope of the communication device described in this application is not limited thereto, and the structure of the communication device may not be limited to FIG10. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:
[0268] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;
[0269] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;
[0270] (3) ASIC, such as modem;
[0271] (4) Modules that can be embedded in other devices;
[0272] (5) Receivers, terminals, smart terminals, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;
[0273] (6)Others, etc.
[0274] In another possible implementation, in the communication device shown in Figure 9, the processing unit 20 can be one or more logic circuits, and the transceiver unit 10 can be an input / output interface, or a communication interface, or an interface circuit, or an interface, etc. Or the transceiver unit 10 can also be a sending unit and a receiving unit, the sending unit can be an output interface, and the receiving unit can be an input interface, and the sending unit and the receiving unit are integrated into one unit, such as an input / output interface. See Figure 11, which is another structural diagram of the communication device provided in an embodiment of the present application. As shown in Figure 11, the communication device shown in Figure 11 includes a logic circuit 901 and an interface 902. That is, the above-mentioned processing unit 20 can be implemented with a logic circuit 901, and the transceiver unit 10 can be implemented with an interface 902. Among them, the logic circuit 901 can be a chip, a processing circuit, an integrated circuit or a system on chip (SoC) chip, etc., and the interface 902 can be a communication interface, an input / output interface, a pin, etc. Exemplarily, Figure 11 is shown as an example of the above-mentioned communication device being a chip, and the chip includes a logic circuit 901 and an interface 902.
[0275] In the embodiment of the present application, the logic circuit and the interface may also be coupled to each other. The embodiment of the present application does not limit the specific connection method between the logic circuit and the interface.
[0276] Exemplarily, when the communication device is used to execute the method, function or step performed by the non-AP MLD in the aforementioned embodiment one, embodiment two or embodiment three, the logic circuit 901 is used to generate a first association request frame; the interface 902 is used to output the first association request frame; and the interface 902 is also used to input a first association response frame.
[0277] Exemplarily, when the communication device is used to execute the method, function or steps performed by AP MLD in the aforementioned embodiment one, embodiment two or embodiment three, interface 902 is used to input a first association request frame; logic circuit 901 is used to generate a first association response frame; interface 902 is also used to output a first association response frame.
[0278] It is understandable that for the specific description of the first association request frame, the first association response frame, etc., reference can be made to the method embodiments shown above, and they will not be described in detail here.
[0279] It can be understood that the communication device shown in the embodiment of the present application can implement the method provided in the embodiment of the present application in the form of hardware, or can implement the method provided in the embodiment of the present application in the form of software, etc., and the embodiment of the present application is not limited to this.
[0280] For the specific implementation of each embodiment shown in FIG11 , reference may also be made to the above embodiments, which will not be described in detail here.
[0281] An embodiment of the present application further provides a wireless communication system, which includes a non-AP MLD and an AP MLD. The non-AP MLD and the AP MLD can be used to execute the method in any of the aforementioned embodiments.
[0282] In addition, the present application also provides a computer program, which is used to implement the operations and / or processing performed by the non-AP MLD in the method provided in the present application.
[0283] The present application also provides a computer program, which is used to implement the operations and / or processing performed by the AP MLD in the method provided in the present application.
[0284] The present application also provides a computer-readable storage medium having computer code stored therein. When the computer code is executed on a computer, the computer executes the operations and / or processing performed by the non-AP MLD in the method provided in the present application.
[0285] The present application also provides a computer-readable storage medium having computer code stored therein. When the computer code is executed on a computer, the computer is enabled to execute the operations and / or processes performed by the AP MLD in the method provided in the present application.
[0286] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program runs on a computer, the operations and / or processing performed by the non-AP MLD device in the method provided in the present application are executed.
[0287] The present application also provides a computer program product, which includes computer code or computer program. When the computer code or computer program runs on a computer, the operations and / or processes performed by the AP MLD in the method provided by the present application are executed.
[0288] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, or can be electrical, mechanical or other forms of connection.
[0289] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the technical effects of the solutions provided in the embodiments of the present application.
[0290] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0291] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a readable storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned readable storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other media that can store program code.
[0292] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A method for establishing multi-link communication, characterized in that: include: A first station of a non-access point multi-link device (non-AP MLD) sends a first association request frame on a first link, where the first association request frame includes a multi-link element, the multi-link element includes indication information, and the indication information is used to indicate a second link; The first station of the non-AP MLD receives a first association response frame on the first link, where the first association response frame includes a first status code field and a multilink element, where the multilink element of the first association response frame includes a second status code field, where the value of the first status code field is not 0, indicating that the first link is not accepted; and where the second status code field is set to a first value not 0, indicating that a reason why the second link is not accepted is that the first link is not accepted.
2. A method for establishing multi-link communication, characterized in that: include: A first access point of an access point multi-link device AP MLD receives a first association request frame on a first link, where the first association request frame includes a multi-link element, the multi-link element includes indication information, and the indication information is used to indicate a second link; The first access point of the AP MLD sends a first association response frame on the first link, where the first association response frame includes a first status code field and 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 not 0, indicating that the first link is not accepted; the second status code field is set to a first value that is not 0, indicating that the reason why the second link is not accepted is that the first link is not accepted.
3. The method according to claim 1 or 2, characterized in that The first status code field is a status code field outside the multilink element of the first association response frame.
4. The method according to any one of claims 1 to 3, characterized in that The second status code field is a status code field included in the STA profile subfield of each STA profile sub-element.
5. The method according to claim 1, wherein After the first station of the non-AP MLD receives a first association response frame on the first link, the method further includes: The second station of the non-AP MLD sends a second association request frame on the second link; The second station of the non-AP MLD receives a second association response frame on the second link.
6. The method according to claim 2, characterized in that After the first access point of the AP MLD sends a first association response frame on the first link, the method further includes: The second access point of the AP MLD receives a second association request frame on the second link; The second access point of the AP MLD sends a second association response frame on the second link.
7. A method for establishing multi-link communication, characterized in that: include: A first station of a non-access point multi-link device (non-AP MLD) sends a first association request frame on a first link, where the first association request frame includes a multi-link element, the multi-link element includes indication information, and the indication information is used to indicate a second link; The first station of the non-AP MLD receives a first association response frame on the first link, where the first association response frame includes a first status code field and a multilink element, where the multilink element of the first association response frame includes a second status code field, where a value of the first status code field is not 0 and a value of the second status code field is 0, jointly indicating that a reason why the second link is not accepted is that the first link is not accepted.
8. A method for establishing multi-link communication, characterized in that: include: A first access point of an access point multi-link device AP MLD receives a first association request frame on a first link, where the first association request frame includes a multi-link element, the multi-link element includes indication information, and the indication information is used to indicate a second link; The first access point of the AP MLD sends a first association response frame on the first link, where the first association response frame includes a first status code field and 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 not 0 and the value of the second status code field is 0, which are used to jointly indicate that the reason why the second link is not accepted is that the first link is not accepted.
9. The method according to claim 7 or 8, characterized in that The first status code field is a status code field outside the multilink element of the first association response frame.
10. The method according to any one of claims 7 to 9, characterized in that The second status code field is a status code field included in the STA profile subfield of each STA profile sub-element.
11. The method according to claim 7, characterized in that After the first station of the non-AP MLD receives a first association response frame on the first link, the method further includes: The second station of the non-AP MLD sends a second association request frame on the second link; The second station of the non-AP MLD receives a second association response frame on the second link.
12. The method according to claim 8, characterized in that After the first access point of the AP MLD sends a first association response frame on the first link, the method further includes: The second access point of the AP MLD receives a second association request frame on the second link; The second access point of the AP MLD sends a second association response frame on the second link.
13. A communication device, characterized in that: The communication device includes a processing unit and a transceiver unit, wherein the processing unit is configured to control the transceiver unit to perform the following steps: Sending a first association request frame on the first link, where the first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate the second link; A first association response frame is received on the first link, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field, the value of the first status code field is not 0, used to indicate that the first link is not accepted; the second status code field is set to a first value not 0, used to indicate that the reason why the second link is not accepted is that the first link is not accepted.
14. The communication device according to claim 13, wherein: The transceiver unit is further configured to execute: sending a second association request frame on the second link; A second association response frame is received on the second link.
15. A communication device, characterized in that: The communication device includes a processing unit and a transceiver unit, wherein the processing unit is configured to control the transceiver unit to perform the following steps: Receiving a first association request frame on the first link, where the first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate the second link; A first association response frame is sent on the first link, where the first association response frame includes a first status code field and a multilink element, where the multilink element of the first association response frame includes a second status code field, where the value of the first status code field is not 0, indicating that the first link is not accepted; and the second status code field is set to a first value not 0, indicating that the reason why the second link is not accepted is that the first link is not accepted. The communication device according to claim 15 , wherein: The transceiver unit is further configured to execute: receiving a second association request frame on the second link; A second association response frame is sent on the second link.
17. A communication device, characterized in that: The communication device includes a processing unit and a transceiver unit, wherein the processing unit is configured to control the transceiver unit to perform the following steps: Sending a first association request frame on the first link, where the first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate the second link; A first association response frame is received on the first link, the first association response frame including a first status code field and a multilink element, the multilink element of the first association response frame including a second status code field, the value of the first status code field is not 0 and the value of the second status code field is 0, which are used to jointly indicate that the reason why the second link is not accepted is that the first link is not accepted.
18. The communication device according to claim 17, wherein: The transceiver unit is further configured to execute: sending a second association request frame on the second link; A second association response frame is received on the second link.
19. A communication device, characterized in that: The communication device includes a processing unit and a transceiver unit, wherein the processing unit is configured to control the transceiver unit to perform the following steps: Receiving a first association request frame on the first link, where the first association request frame includes a multilink element, the multilink element includes indication information, and the indication information is used to indicate the second link; A first association response frame is sent on the first link, where the first association response frame includes a first status code field and a multilink element, where the multilink element of the first association response frame includes a second status code field, where the value of the first status code field is not 0 and the value of the second status code field is 0, which are used to jointly indicate that the reason why the second link is not accepted is that the first link is not accepted.
20. The communication device according to claim 19, wherein The transceiver unit is further configured to execute: receiving a second association request frame on the second link; A second association response frame is sent on the second link.
21. A communication device, characterized in that: including processor and memory; The memory is used to store instructions; The processor is configured to execute the instructions so that the method according to any one of claims 1 to 12 is performed.
22. A communication device, characterized in that: comprising a logic circuit and an interface, wherein the logic circuit and the interface are coupled; The interface is used to input and / or output code instructions, and the logic circuit is used to execute the code instructions so that the method according to any one of claims 1 to 12 is executed.
23. A computer-readable storage medium, characterized in that The computer-readable storage medium is used to store a computer program. When the computer program is executed, the method according to any one of claims 1 to 12 is performed.
