Multi-link reconfiguration method and device

Abstract

The invention discloses a multi-link reconfiguration method and device, relates to the technical field of communication, and is used for realizing reconfiguration of a link between two MLDs. The method comprises the following steps: a first MLD generates a first frame, wherein the first frame is used for reconfiguring a link between the first MLD and a second MLD; the first MLD transmits the first frame to the second MLD.

Description

[0001] This application is a divisional application. The application number of the original application is 202110778961.5, the original application date is July 9, 2021, and the entire content of the original application is incorporated herein by reference.

[0002] This application claims the priority of a Chinese patent application with the application number 202110058021.9 and the application title "Multi-link Reconfiguration Method and Apparatus" filed with the National Intellectual Property Administration on January 15, 2021, and also claims the priority of a Chinese patent application with the application number 202110713587.0 and the application title "Multi-link Reconfiguration Method and Apparatus" filed with the National Intellectual Property Administration on June 25, 2021. The entire content of both applications is incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technologies, and in particular to a multi-link reconfiguration method and apparatus. Background Art

[0004] To achieve the technical goal of extremely high throughput, the Institute of Electrical and Electronics Engineers (IEEE) 802.11be standard takes multi-link (ML) communication as one of the key technologies. A multi-link device (MLD) that supports ML communication has the ability to transmit and receive on multiple links. Thus, the MLD can utilize a larger bandwidth for data transmission, which is conducive to significantly improving the throughput. Herein, a link can refer to the spatial path for the MLD to perform data transmission on a frequency band.

[0005] Currently, two MLDs can establish one or more links for communication through an association process. However, in some scenarios, the links already established between two MLDs may not meet the data transmission requirements between the two MLDs. In response to this situation, the industry has not provided a corresponding solution. Summary of the Invention

[0006] Embodiments of this application provide a multi-link reconfiguration method and apparatus for implementing the reconfiguration of the links between two MLDs.

[0007] In a first aspect, a multi-link reconfiguration method is provided, including: a first MLD generates a first frame, where the first frame is used to reconfigure the link between the first MLD and the second MLD; the first MLD sends the first frame to the second MLD. Based on the above technical solution, by sending the first frame to the second MLD, the first MLD can trigger the reconfiguration of the link between the first MLD and the second MLD, so as to meet the data transmission requirements between the first MLD and the second MLD.

[0008] Optionally, the first frame may be a new type of action frame.

[0009] Optionally, the first frame may reuse an existing frame, such as a reassociation request frame or a disassociation frame. It should be understood that reusing the reassociation request frame or the disassociation frame for the first frame can avoid making excessive changes to the existing protocol, without redefining the information elements that the first frame should include, and save the reserved values of the category field in the action frame.

[0010] Optionally, in the case where the first frame reuses the reassociation request frame, after the first MLD sends the first frame to the second MLD, the first MLD and the second MLD may continue to cache the following information: enhanced distributed channel access (EDCA) function status, block acknowledgment protocol, sequence number (SN), packet number (PN), duplicate detection cache, data to be transmitted in the queue, fragmentation and reassembly buffer, power management mode, wireless network management sleep mode. It should be understood that different from the prior art where devices need to delete the above information during the reassociation process, in the embodiment of the present application, although the first frame reuses the reassociation request frame, it does not trigger the first MLD and the second MLD to delete the above information. Therefore, after changing the link configuration, the first MLD and the second MLD do not need to renegotiate to obtain the above information, which is beneficial to saving the overhead caused by the process of negotiating the above information.

[0011] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: the first frame is used to indicate establishing a target link between the first MLD and the second MLD. It should be understood that by adding one or more links between the first MLD and the second MLD, the data throughput between the first MLD and the second MLD can be increased.

[0012] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: the first frame is used to indicate deleting a target link from the links already established between the first MLD and the second MLD. It should be understood that by deleting one or more links between the first MLD and the second MLD, the corresponding energy consumption can be saved.

[0013] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: the first frame is used to indicate the target link, and the target link is used to transmit data between the first MLD and the second MLD.

[0014] In a possible design, the first frame includes a first field, and the first field is used to indicate the type of reconfiguration. The types of reconfiguration include: deleting a link, adding a link, or transferring a link. Based on this design, one type of first frame can implement multiple types of link reconfigurations.

[0015] In a possible design, the first frame may include a Multi-link element, and the Multi-link element includes a Per-link Profile, and the Per-link Profile includes a first field.

[0016] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: when the first field is used to indicate deleting a link, the first frame is used to indicate deleting the target link from the links already established between the first MLD and the second MLD; or, when the first field is used to indicate adding a link, the first frame is used to indicate establishing the target link between the first MLD and the second MLD; or, when the first field is used to indicate transferring a link, the first frame is used to indicate switching the link established between the first MLD and the second MLD to the target link.

[0017] It should be understood that transferring a link can enable two MLDs to transfer from a link with poor quality to a link with better quality for data transmission, which is beneficial to improving the quality of service of data transmission between the two MLDs.

[0018] In a possible design, the first frame further includes a second field, and the second field is used to indicate the target link.

[0019] In a possible design, the first frame may include a Multi-link element, the Multi-link element includes a Per-link Profile, and the Per-link Profile includes a second field.

[0020] In a possible design, the second field includes a bitmap, the bitmap includes at least one bit, and the bits in the bitmap are used to indicate whether the link corresponding to the bit is the target link.

[0021] In a possible design, the second field includes the identifier of the target link.

[0022] In a possible design, the first frame further includes a third field, and the third field is used to indicate whether the first link is a target link, where the first link is the link used to transmit the first frame.

[0023] In a possible design, the first frame may include a Multi-link element, and the Multi-link element includes a third field.

[0024] In a possible design, the first frame is a reassociation request frame or a disassociation frame; the first frame includes a multi-link element (Multi-link element), the Multi-link element includes a multi-link control (Multi-link control) field, the Multi-link control field includes a type field, and the type field with a value of a first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

[0025] In a possible design, the method further includes: the first MLD receives a request frame from the second MLD, and the request frame is used to request a link transfer between the first MLD and the second MLD; the first MLD sends a response frame to the second MLD, and the response frame is used to indicate whether to agree to the link transfer between the first MLD and the second MLD. Based on this design, before the link transfer, the negotiation of the link transfer between the two MLDs can enable the two MLDs to determine a better link for the transfer and ensure the quality of data transmission between the two MLDs after the link transfer.

[0026] In a possible design, the request frame is further used to indicate a recommended link.

[0027] In a possible design, before the first MLD receives the request frame from the second MLD, the method further includes: the first MLD sends an inquiry frame to the second MLD, and the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD. Based on this design, the first MLD can trigger the process of link transfer negotiation between the two MLDs by sending an inquiry frame.

[0028] In a second aspect, a method for reconfiguring a multi-link is provided, including: the second MLD receives a first frame from the first MLD, and the first frame is used to reconfigure the link between the first MLD and the second MLD; the second MLD parses the first frame.

[0029] In a possible design, that the first frame is used to reconfigure the link between the first MLD and the second MLD includes: the first frame is used to indicate to establish a target link between the first MLD and the second MLD.

[0030] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: the first frame is used to indicate deleting the target link from the links already established between the first MLD and the second MLD.

[0031] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: the first frame is used to indicate the target link, and the target link is used to transmit data between the first MLD and the second MLD.

[0032] In a possible design, the first frame includes a first field, and the first field is used to indicate the type of reconfiguration. The types of reconfiguration include: deleting a link, adding a link, or transferring a link.

[0033] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: when the first field is used to indicate deleting a link, the first frame is used to indicate deleting the target link from the links already established between the first MLD and the second MLD; or, when the first field is used to indicate adding a link, the first frame is used to indicate establishing the target link between the first MLD and the second MLD; or, when the first field is used to indicate transferring a link, the first frame is used to indicate switching the link established between the first MLD and the second MLD to the target link.

[0034] In a possible design, the first frame further includes a second field, and the second field is used to indicate the target link.

[0035] In a possible design, the second field includes a bitmap, the bitmap includes at least one bit, and the bits in the bitmap are used to indicate whether the link corresponding to the bit is the target link.

[0036] In a possible design, the second field includes the identifier of the target link.

[0037] In a possible design, the first frame further includes a third field, and the third field is used to indicate whether the first link is the target link, where the first link is the link used to transmit the first frame.

[0038] In a possible design, the first frame is a re-association request frame or a de-association frame; the first frame includes a Multi-link element, the Multi-link element includes a Multi-link control field, the Multi-link control field includes a type field, and the type field with a value of the first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

[0039] In a possible design, the method further includes: the second MLD sends a request frame to the first MLD, where the request frame is used to request a link transfer between the first MLD and the second MLD; the second MLD receives a response frame from the first MLD, where the response frame is used to indicate whether to agree to the link transfer between the first MLD and the second MLD.

[0040] In a possible design, the request frame is further used to indicate a recommended link.

[0041] In a possible design, before the second MLD sends a request frame to the first MLD, the method further includes: the second MLD receives an inquiry frame from the first MLD, where the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD.

[0042] In a third aspect, an MLD is provided, including a processing module and a communication module. The processing module is configured to generate a first frame, where the first frame is used to reconfigure a link between the first MLD and the second MLD. The communication module is configured to send the first frame to the second MLD.

[0043] In a possible design, the first frame is used to reconfigure a link between the first MLD and the second MLD, including: the first frame is used to indicate establishing a target link between the first MLD and the second MLD.

[0044] In a possible design, the first frame is used to reconfigure a link between the first MLD and the second MLD, including: the first frame is used to indicate deleting a target link from the links already established between the first MLD and the second MLD.

[0045] In a possible design, the first frame is used to reconfigure a link between the first MLD and the second MLD, including: the first frame is used to indicate a target link, where the target link is used to transmit data between the first MLD and the second MLD.

[0046] In a possible design, the first frame includes a first field, where the first field is used to indicate the type of reconfiguration, and the type of reconfiguration includes: deleting a link, adding a link, or transferring a link.

[0047] In a possible design, the first frame is used to reconfigure a link between the first MLD and the second MLD, including: when the first field is used to indicate deleting a link, the first frame is used to indicate deleting a target link from the links already established between the first MLD and the second MLD; or, when the first field is used to indicate adding a link, the first frame is used to indicate establishing a target link between the first MLD and the second MLD; or, when the first field is used to indicate transferring a link, the first frame is used to indicate switching the link established between the first MLD and the second MLD to the target link.

[0048] In a possible design, the first frame further includes a second field, and the second field is used to indicate the target link.

[0049] In a possible design, the second field includes a bitmap, the bitmap includes at least one bit, and the bits in the bitmap are used to indicate whether the link corresponding to the bit is the target link.

[0050] In a possible design, the second field includes the identifier of the target link.

[0051] In a possible design, the first frame further includes a third field, and the third field is used to indicate whether the first link is the target link, where the first link is the link used to transmit the first frame.

[0052] In a possible design, the first frame is a re-association request frame or a de-association frame; the first frame includes a Multi-link element, the Multi-link element includes a Multi-link control field, and the Multi-link control field includes a type field. The type field with a value of the first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

[0053] In a possible design, the communication module is further configured to receive a request frame from the second MLD, where the request frame is used to request a link transfer between the first MLD and the second MLD; and send a response frame to the second MLD, where the response frame is used to indicate whether to agree to the link transfer between the first MLD and the second MLD.

[0054] In a possible design, the request frame is further used to indicate the recommended link.

[0055] In a possible design, the communication module is further configured to send an inquiry frame to the second MLD, where the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD.

[0056] In a fourth aspect, an MLD is provided, including a processing module and a communication module. The communication module is configured to receive a first frame from the first MLD, where the first frame is used to reconfigure the link between the first MLD and the second MLD. The processing module is configured to parse the first frame.

[0057] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: the first frame is used to indicate to establish a target link between the first MLD and the second MLD.

[0058] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: the first frame is used to indicate deleting the target link from the link already established between the first MLD and the second MLD.

[0059] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: the first frame is used to indicate the target link, and the target link is used to transmit data between the first MLD and the second MLD.

[0060] In a possible design, the first frame includes a first field, and the first field is used to indicate the type of reconfiguration. The type of reconfiguration includes: deleting a link, adding a link, or transferring a link.

[0061] In a possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: when the first field is used to indicate deleting a link, the first frame is used to indicate deleting the target link from the link already established between the first MLD and the second MLD; or, when the first field is used to indicate adding a link, the first frame is used to indicate establishing the target link between the first MLD and the second MLD; or, when the first field is used to indicate transferring a link, the first frame is used to indicate switching the link established between the first MLD and the second MLD to the target link.

[0062] In a possible design, the first frame further includes a second field, and the second field is used to indicate the target link.

[0063] In a possible design, the second field includes a bitmap, the bitmap includes at least one bit, and the bits in the bitmap are used to indicate whether the link corresponding to the bit is the target link.

[0064] In a possible design, the second field includes the identifier of the target link.

[0065] In a possible design, the first frame further includes a third field, and the third field is used to indicate whether the first link is the target link, where the first link is the link used to transmit the first frame.

[0066] In a possible design, the first frame is a re-association request frame or a de-association frame; the first frame includes a Multi-link element, the Multi-link element includes a Multi-link control field, the Multi-link control field includes a type field, and the type field with a value of the first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

[0067] In a possible design, the communication module is further configured to send a request frame to the first MLD, where the request frame is used to request a link transfer between the first MLD and the second MLD; and receive a response frame from the first MLD, where the response frame is used to indicate whether to agree to the link transfer between the first MLD and the second MLD.

[0068] In a possible design, the request frame is further used to indicate a recommended link.

[0069] In a possible design, the communication module is further configured to receive an inquiry frame from the first MLD, where the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD.

[0070] In a fifth aspect, an MLD is provided, including a processor and a transceiver. The processor is configured to perform the processing actions in the corresponding methods in the first aspect or the second aspect above, and the transceiver pin is configured to perform the communication actions in the corresponding methods in the first aspect or the second aspect above.

[0071] In a sixth aspect, a computer-readable storage medium is provided, where instructions are stored in the computer-readable storage medium. When the instructions run on a computer, the computer is caused to execute the methods involved in any one of the designs in the first aspect or the second aspect above.

[0072] In a seventh aspect, a computer program product including instructions is provided. When the computer program product runs on a computer, the computer is caused to execute the methods involved in any one of the designs in the first aspect or the second aspect above.

[0073] In an eighth aspect, a chip is provided, including: a processing circuit and a transceiver pin. The processing circuit is configured to perform the processing actions in the corresponding methods in the first aspect or the second aspect above, and the transceiver pin is configured to perform the communication actions in the corresponding methods in the first aspect or the second aspect above.

[0074] It can be understood that any of the above-provided MLDs, chips, computer storage media, or computer program products is used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] Figure 1 FIG. 1 is a schematic diagram of a communication scenario between an AP multi-link device and an STA multi-link device provided in an embodiment of the present application;

[0076] FIGS. 2(a) and 2(b) are schematic diagrams of the structures of the AP multi-link device and the STA multi-link device participating in communication;

[0077] Figure 3Schematic diagram of a frame structure of a Multi-link element provided by an embodiment of this application;

[0078] Figure 4 Flowchart of a multi-link reconfiguration method provided by an embodiment of this application;

[0079] Figure 5 Schematic diagram of another frame structure of a Multi-link element provided by an embodiment of this application;

[0080] Figure 6(a) is a schematic diagram of another frame structure of a Multi-link element provided by an embodiment of this application;

[0081] Figure 6(b) is a schematic diagram of another frame structure of a Multi-link element provided by an embodiment of this application;

[0082] Figure 7 Schematic diagram of another frame structure of a Multi-link element provided by an embodiment of this application;

[0083] Figure 8 Flowchart of another multi-link reconfiguration method provided by an embodiment of this application;

[0084] Figure 9(a) is a schematic diagram of another frame structure of a Multi-link element provided by an embodiment of this application;

[0085] Figure 9(b) is a schematic diagram of another frame structure of a Multi-link element provided by an embodiment of this application;

[0086] Figure 10 Schematic diagram of the BTM process in the related art;

[0087] Figure 11(a) is a schematic diagram of the frame structure of a BTM inquiry frame in the related art;

[0088] Figure 11(b) is a schematic diagram of the frame structure of a neighbor report element in the related art;

[0089] Figure 12 Schematic diagram of the frame structure of a BTM request frame in the related art;

[0090] Figure 13 Schematic diagram of the frame structure of a BTM response frame in the related art;

[0091] Figure 14 Flowchart of another multi-link reconfiguration method provided by an embodiment of this application;

[0092] Figure 15Schematic diagram of a frame structure of a neighbor report element provided by an embodiment of the present application;

[0093] Figure 16 Schematic diagram of the structure of a communication device provided by an embodiment of the present application;

[0094] Figure 17 Schematic diagram of the structure of a communication device provided by an embodiment of the present application;

[0095] Figure 18 Flowchart of a multi-link reconfiguration method provided by an embodiment of the present application;

[0096] Figure 19 Flowchart of another multi-link reconfiguration method provided by an embodiment of the present application;

[0097] Figure 20 Flowchart of another multi-link reconfiguration method provided by an embodiment of the present application;

[0098] Figure 21 Flowchart of another multi-link reconfiguration method provided by an embodiment of the present application;

[0099] Figure 22 Schematic diagram of a frame structure of a request mode field provided by an embodiment of the present application. Detailed implementation manners

[0100] In the description of the present application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. The "and / or" herein is merely a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, "at least one" means one or more, and "a plurality" means two or more. The terms such as "first" and "second" do not limit the quantity and execution order, and the terms such as "first" and "second" do not necessarily mean different.

[0101] In the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Exactly speaking, using words such as "exemplary" or "for example" aims to present relevant concepts in a specific manner.

[0102] The technical solutions provided by this application can be applied to various communication systems, such as systems adopting the IEEE 802.11 standard. Exemplarily, the IEEE 802.11 standard includes but is not limited to: the 802.11be standard, or the next-generation 802.11 standard. The scenarios applicable to the technical solutions of this application include: communication between an AP and an STA, communication between APs, and communication between STAs, etc.

[0103] The STA involved in this application can be various user terminals, user devices, access devices, subscriber stations, subscriber units, mobile stations, user agents, user equipment or other names with wireless communication functions. Among them, the user terminal can include various handheld devices, vehicle-mounted devices, wearable devices, computing devices or other processing devices connected to a wireless modem with wireless communication functions, as well as various forms of user equipment (UE), mobile station (MS), terminal, terminal equipment, portable communication device, handheld device, portable computing device, entertainment device, game device or system, global positioning system device or any other suitable device configured to communicate over a wireless medium, etc. Here, for the sake of description, the above-mentioned devices are collectively referred to as stations or STAs.

[0104] The access point AP involved in this application is a device deployed in a wireless communication network to provide wireless communication functions for its associated STAs. The access point AP can be used as the center of this communication system and can be communication devices such as a base station, router, gateway, repeater, communication server, switch or bridge, etc. Among them, the base station can include various forms of macro base stations, micro base stations, relay stations, etc. Here, for the sake of description, the above-mentioned devices are collectively referred to as access point APs.

[0105] The IEEE 802.11 next-generation wireless fidelity (WiFi) protocol extremely high throughput (EHT) devices support improving the peak throughput and reducing the latency of service transmission by means of multiple stream numbers, multiple frequency bands (for example, 2.4 GHz, 5 GHz, and 6 GHz frequency bands), and cooperation through multiple channels on the same frequency band. The multiple frequency bands or multiple channels can be collectively referred to as multi-links.

[0106] The multi-link device includes one or more subordinate stations, and the subordinate stations can be logical stations or physical stations. In the embodiments of this application, "the multi-link device includes subordinate stations" can be briefly described as "the multi-link device includes stations".

[0107] Among them, the affiliated station can be an access point (AP) or a non-access point station (non-AP STA). For convenience of description, in the embodiments of the present application, a multi-link device with an affiliated station being an AP can be referred to as a multi-link AP, or an AP MLD, or a multi-link AP device; a multi-link device with an affiliated station being an STA can be referred to as a multi-link STA, or a multi-link STA device, or an STA MLD, or a non-AP MLD.

[0108] The multi-link device can implement wireless communication by following the 802.11 protocol. Exemplarily, the 802.11 protocol can be the 802.11ax protocol, the 802.11be protocol, and the next-generation 802.11 protocol. The embodiments of the present application are not limited thereto.

[0109] The multi-link device can communicate with other devices. In the embodiments of the present application, other devices can be multi-link devices or not.

[0110] Exemplarily, Figure 1 FIG. 1 is a schematic diagram of a communication scenario between an AP multi-link device and an STA multi-link device. As Figure 1 shown, an AP multi-link device can be associated with multiple STA multi-link devices and a single-link STA. For example, the AP multi-link device 100 is associated with the STA multi-link device 200, the STA multi-link device 300, and the STA 400. It should be understood that multiple APs in the AP multi-link device work on multiple links respectively, multiple STAs in the STA multi-link device work on multiple links respectively, and one STA in the STA multi-link device is associated with one AP in the AP multi-link device on its working link. The single-link STA is associated with one AP in the AP multi-link device on its working link.

[0111] The frequency bands on which the multi-link device operates can include but are not limited to: sub 1GHz, 2.4GHz, 5GHz, 6GHz, and high-frequency 60GHz. FIGS. 2(a) and 2(b) show two schematic diagrams of a multi-link device and other devices communicating through multiple links in a wireless local area network.

[0112] FIG. 2(a) shows a scenario where an AP multi-link device 101 and an STA multi-link device 102 communicate. The AP multi-link device 101 includes affiliated APs 101-1 and 101-2, the STA multi-link device 102 includes affiliated STAs 102-1 and 102-2, and the AP multi-link device 101 and the STA multi-link device 102 communicate in parallel using Link 1 and Link 2.

[0113] Figure 2(b) shows a scenario where the AP multi-link device 101 communicates with the STA multi-link device 102, the STA multi-link device 103, and the STA 104. The AP multi-link device 101 includes subordinate APs 101-1 to 101-3. The STA multi-link device 102 includes two subordinate STAs 102-1 and 102-2. The STA multi-link device 103 includes 2 subordinate STAs 103-1, 103-2, and 103-3. The STA 104 is a single-link device (SLD). The AP multi-link device can communicate with the STA multi-link device 102 using Link 1 and Link 3 respectively, communicate with the multi-link 103 using Link 2 and Link 3, and communicate with the STA 104 using Link 1. In one example, the STA 104 operates in the 2.4 GHz band; the STA multi-link device 103 includes the STA 103-1 and the STA 103-2. The STA 103-1 operates in the 5 GHz band, and the STA 103-2 operates in the 6 GHz band; the STA multi-link device 102 includes the STA 102-1 and the STA 102-2. The STA 102-1 operates in the 2.4 GHz band, and the STA 102-2 operates in the 6 GHz band. The AP 101-1 operating in the 2.4 GHz band in the AP multi-link device can transmit uplink or downlink data between the STA 104 and the STA 102-2 in the STA multi-link device 102 through Link 1. The AP 101-2 operating in the 5 GHz band in the AP multi-link device can transmit uplink or downlink data between the AP 101-2 and the STA 103-1 operating in the 5 GHz band in the STA multi-link device 103 through Link 2. The AP 101-3 operating in the 6 GHz band in the AP multi-link device 101 can transmit uplink or downlink data between the AP 101-3 and the STA 102-2 operating in the 6 GHz band in the STA multi-link device 102 through Link 3, and can also transmit uplink or downlink data between the AP 101-3 and the STA 103-2 in the STA multi-link device through Link 3.

[0114] It should be noted that Figure 2(a) only shows that the AP multi-link device supports 2 bands. Figure 2(b) only takes the AP multi-link device supporting three bands (2.4 GHz, 5 GHz, 6 GHz), with each band corresponding to one link, and the AP multi-link device 101 can operate on one or more of Link 1, Link 2, or Link 3 as an example for illustration. On the AP side or the STA side, the link here can also be understood as the station operating on this link. In practical applications, the AP multi-link device and the STA multi-link device can also support more or fewer bands, that is, the AP multi-link device and the STA multi-link device can operate on more or fewer links. The embodiments of the present application do not limit this.

[0115] Exemplarily, the multi-link device is a device with wireless communication capabilities. This device can be a complete device, or it can be a chip or a processing system installed in the complete device. The device installed with these chips or processing systems can, under the control of these chips or processing systems, implement the methods and functions of the embodiments of the present application.

[0116] The multi-link device can support simultaneously transmit and receive (STR) data, or the multi-link device may not support simultaneously transmit and receive data. Among them, supporting simultaneously transmit and receive data means that: during the process of the multi-link device transmitting data on one link, it can receive data on another link. Not supporting simultaneously transmit and receive data means that: during the process of the multi-link device transmitting data on one link, it cannot receive data on another link.

[0117] Exemplarily, the non-AP MLD can perform multi-link establishment operations through one of its links to simultaneously establish associations with multiple links of the AP MLD. During the association process, the non-AP MLD and the AP MLD can exchange multi-link association request / response (Multi-link Association Request / Response) frames on one link. Among them, the link used to exchange the Multi-link Association Request / Response frames can be referred to as the transmission link (transmission link), and the other links are non-transmitted links (Non-transmitted Link). It should be understood that the Multi-link Association Request / Response can carry information about the multiple links to be associated to achieve simultaneous association of multiple links between the non-AP MLD and the AP MLD.

[0118] For example, the non-AP MLD sends a Multi-link Association Request frame on Link 1, and the Multi-link Association Request frame carries the STA-side information of Link 1 and the STA-side information of Link 2. It should be understood that Link 1 can be referred to as the transmission link, and Link 2 can be referred to as the non-transmission link. The AP MLD sends a Multi-link Association Response frame to the non-AP MLD on Link 1, and the Multi-link Association Response frame can carry the AP-side information of Link 1 and the AP-side information of Link 2. Thus, the non-AP MLD and the AP MLD establish an association on Link 1 and Link 2. Furthermore, the non-AP MLD and the AP MLD can perform data transmission on Link 1 and Link 2.

[0119] To carry the relevant information of the non-AP MLD in the existing association request frame, the protocol defines a Multi-link element. Exemplarily, as Figure 3 shown, the information carried by the Multi-link element is divided into two parts, one part is the MLD-level info, and the other part is the per-link configuration information (Per-link Profile). Among them, the Per-link Profile can also be referred to as the Per-STA Profile. It should be understood that the Per-link Profile is optional. That is, the Multi-link element may not include the Per-link Profile, or may include one or more Per-link Profiles. For example, Figure 3 shows that there are Per-link Profile x and Per-link Profile y in the Multi-link element.

[0120] Among them, the MLD-level info includes the following fields: Multi-link control, and one or more fields. Exemplarily, one or more of the fields may include the following fields: element ID, length, extended element ID, and other fields, etc.

[0121] The Multi-link control field includes the following fields: type, current MLD MAC address present, and reserved field.

[0122] The Per-link Profile includes the following fields: subelement ID, length, and data.

[0123] The data field in the Per-link Profile includes one or more of the following fields: Per-STA control field, one or more elements, and non-inheritance element. Among them, the non-inheritance element is an optional field.

[0124] Each Per-STA control field includes at least a link ID. It should be understood that a non-AP MLD can obtain the link information (such as link identifier) corresponding to each link by receiving a probe response frame or a beacon frame.

[0125] In some scenarios, after two MLDs establish an association, the established link may not meet the data transmission requirements between the two MLDs.

[0126] For example, when two MLDs initially establish an association, only one link is established, but there is a large amount of data to be transmitted between the two MLDs, and one link cannot meet the throughput requirements of data transmission. Therefore, additional links are needed between the two MLDs.

[0127] For another example, when two MLDs initially establish an association, multiple links are established, but the amount of data to be transmitted between the two MLDs is small, and one link can meet the throughput requirements of data transmission. Therefore, redundant links need to be deleted between the two MLDs to save energy consumption.

[0128] For another example, when two MLDs initially establish an association, link 1 is established, but the communication quality of link 1 is poor. Therefore, the two MLDs want to transfer from link 1 to link 2 for data transmission.

[0129] Currently, the industry has not given a solution on how MLD changes the link configuration after association.

[0130] To support two MLDs in changing the link configuration after association, the embodiments of the present application provide a multi-link reconfiguration method. As Figure 4 shown, the method includes the following steps:

[0131] S101. The first MLD generates a first frame.

[0132] Among them, the first frame is used to reconfigure the multi-link between the first MLD and the second MLD.

[0133] It should be understood that before step S101, one or more links have been established between the first MLD and the second MLD through an association process.

[0134] In the embodiments of the present application, the first frame can be a newly defined frame or an existing frame can be reused (such as a re-association request frame or a disassociation frame), and this is not limited.

[0135] Optionally, the first frame can adopt any one of the following designs:

[0136] Design 1-1: The first frame is used to indicate the establishment of a target link.

[0137] Specifically, the first frame is used to indicate the establishment of a target link between the first MLD and the second MLD. That is, the target link belongs to the link that has not been established between the first MLD and the second MLD currently.

[0138] For example, link 1 and link 2 have been established between the first MLD and the second MLD based on the association process. The first frame is used to indicate the establishment of link 3, so that the first MLD and the second MLD can establish link 3 again. After that, the first MLD and the second MLD can use link 1, link 2, and link 3 for data transmission.

[0139] In the embodiments of the present application, two MLDs can perform data transmission on the established links, but cannot perform data transmission on the unestablished links. Two MLDs can exchange a part of management frames (such as association request / response frames) on the unestablished links to establish a link.

[0140] Design 1-2: The first frame is used to indicate the deletion of a target link.

[0141] Specifically, the first frame is used to indicate the deletion of a target link from the links that have been established between the first MLD and the second MLD. Among them, the target link belongs to the link that has been established between the first MLD and the second MLD currently.

[0142] For example, link 1 and link 2 have been established between the first MLD and the second MLD based on the association process. The first frame is used to indicate the deletion of link 2, so that the first MLD and the second MLD delete link 2, making link 2 an unestablished link between the first MLD and the second MLD. The first MLD and the second MLD can only use link 1 to transmit data and cannot use link 2 to transmit data.

[0143] It should be understood that based on Design 1-1 and Design 1-2, the function of the first frame can be associated with the type of the first frame. Thus, the second MLD can determine the function of the first frame according to the type of the first frame. For example, the first frame adopting Design 1-1 is a re-association request frame. After receiving the re-association request frame for multi-link reconfiguration, the second MLD can determine that the re-association request frame is used to establish the target link. Or, the first frame adopting Design 1-2 is a de-association frame. After receiving the de-association frame for multi-link reconfiguration, the second MLD can determine that the de-association frame is used to delete the target link.

[0144] Design 1-3, the first frame is used to indicate the target link.

[0145] Or rather, the first frame is used to indicate that data transmission can be performed between the first MLD and the second MLD on the target link.

[0146] Among them, the target link can be used for data transmission between the first MLD and the second MLD. The target link belongs to the links supported between the first MLD and the second MLD. Exemplarily, the target link can belong to the link that has not been established yet between the first MLD and the second MLD. Or, the target link can also belong to the link that has been established between the first MLD and the second MLD.

[0147] For example, links 1 and 2 have been established between the first MLD and the second MLD based on the association process. The first frame is used to indicate links 2, 3, and 4. Thus, link 1 is deleted between the first MLD and the second MLD, and links 3 and 4 are newly established. In this way, data transmission can be performed between the first MLD and the second MLD using links 2, 3, and 4, and data transmission cannot be performed using link 1.

[0148] It should be understood that the idea of Design 1-3 is that the first frame indicates the link that should be finally established between the first MLD and the second MLD (i.e., the target link). Thus, the first MLD and the second MLD can determine the actual reconfiguration operations (such as deleting links and / or adding links) according to the currently established links and the link that should be finally established.

[0149] Design 1-4, the first frame includes a first field, and the first field is used to indicate the type of reconfiguration. The type of reconfiguration includes deleting a link, adding a link, or transferring a link.

[0150] In the embodiments of the present application, a deletion link, which can also be referred to as a disconnection link, is used to configure an established link between two devices as an unestablished link. An addition link, which can also be referred to as a new link, is used to configure an unestablished link between two devices as an established link. A transfer link, which can also be referred to as a switch link, is used to delete an established link between two devices and establish a link to be transferred.

[0151] Optionally, based on Design 1-4, the first frame is used to reconfigure the multi-link between the first MLD and the second MLD, including the following situations:

[0152] Situation 1: When the first field is used to indicate a deletion link, the first frame is used to indicate the deletion of the target link.

[0153] Situation 2: When the first field is used to indicate an addition link, the first frame is used to indicate the establishment of the target link.

[0154] Situation 3: When the first field is used to indicate a transfer link, the first frame is used to indicate switching the link established between the first MLD and the second MLD to the target link.

[0155] For example, link 1 and link 2 have been established between the first MLD and the second MLD based on the association process. The first field included in the first frame is used to indicate a transfer link, and the first field is used to indicate switching link 2 established between the first MLD and the second MLD to link 3. Thus, link 2 between the first MLD and the second MLD is deleted and link 3 is established. Data can be transmitted between the first MLD and the second MLD on link 1 and link 3, but not on link 2.

[0156] Exemplarily, as Figure 5 shown, the first frame may include a Multi-link element, and the Multi-link element includes a Per-link Profile, and the Per-link Profile includes a first field.

[0157] Exemplarily, the first field may have other names, such as an action field, and there is no limitation in this regard.

[0158] It should be understood that different from Design 1-1 to Design 1-3, the first frame adopting Design 1-4 can flexibly reconfigure the link between the first MLD and the second MLD.

[0159] The above Designs 1-1 to 1-4 are only examples and do not limit the specific implementation of the first frame. It should be understood that in actual use, which design the first frame adopts can be specified by the 802.11 protocol.

[0160] Optionally, the first frame may further include a second field for indicating the target link.

[0161] Optionally, the second field may adopt any one of the following designs:

[0162] Design 2-1: The second field includes the link identifier of the target link.

[0163] Design 2-2: The second field includes a bitmap, the bitmap includes at least one bit, and one bit in the bitmap is used to indicate whether the link corresponding to the bit is the target link.

[0164] For example, if the value of the bit in the bitmap is 1, it indicates that the link corresponding to the bit is the target link; or, if the value of the bit in the bitmap is 0, it indicates that the link corresponding to the bit is not the target link.

[0165] Again, for example, if the value of the bit in the bitmap is 0, it indicates that the link corresponding to the bit is the target link; or, if the value of the bit in the bitmap is 1, it indicates that the link corresponding to the bit is not the target link.

[0166] Exemplarily, as shown in FIG. 6(a), the first frame may include a Multi-link element, the Multi-link element includes a Per-link Profile, and the Per-link Profile includes a second field.

[0167] Exemplarily, as shown in FIG. 6(b), the first frame may include a Multi-link element, and the Multi-link element includes a second field.

[0168] Exemplarily, the second field may have other names, such as the target link set field, which is not limited herein.

[0169] The following introduces the specific implementation of the second field in combination with different implementation manners.

[0170] Implementation manner 1: The second field is specifically used to indicate the target link from all the links supported by the first MLD or all the links supported by the second MLD.

[0171] Optionally, based on Implementation manner 1, assuming that the second field includes a bitmap, the number of bits of the bitmap may be the same as the number of links supported by the first MLD, so that the bits in the bitmap correspond to the links supported by the first MLD one by one; or, the number of bits in the bitmap may be the same as the number of links supported by the second MLD, so that the bits in the bitmap correspond to the links supported by the second MLD one by one.

[0172] Implementation method 2: The second field is specifically used to indicate the target link from among the second links. The second links are the links other than the first link among the links supported by the first MLD. The first link is the link used to transmit the first frame.

[0173] Optionally, based on implementation method 2, assuming that the second field includes a bitmap, the number of bits in the bitmap can be the same as the number of second links. Thus, the bits in the bitmap correspond one-to-one with the second links.

[0174] It should be understood that, based on implementation method 2, the second field is not used to indicate whether the first link is the target link.

[0175] Optionally, when the second field adopts implementation method 2, the first frame can explicitly indicate whether the first link is the target link. For example, the first frame can further include a third field, and the third field is used to indicate whether the first link is the target link. Exemplarily, the third field can occupy 1 bit.

[0176] Exemplarily, as Figure 7 shown, the first frame can include a Multi-link element, and the MLD-level info in the Multi-link element includes the third field.

[0177] Optionally, when the second field adopts implementation method 2, the first frame can implicitly indicate whether the first link is the target link.

[0178] For example, if the first frame is used to add a target link, and the first link belongs to the link that has not been established between the first MLD and the second MLD, then it can be defaulted that the first link is the target link.

[0179] For another example, if the first frame is used to delete a target link, and the first link belongs to the link that has been established between the first MLD and the second MLD, then it can be defaulted that the first link is the target link.

[0180] For another example, if the first frame is used to indicate a target link, it can be defaulted that the first link is the target link.

[0181] Optionally, when the first frame multiplexes a re-association request frame, the frame structure of the first frame can refer to Table 1 shown below.

[0182] Table 1

[0183]

[0184] It should be understood that Table 1 only shows a part of the cells, and the first frame can further include other cells, which are not limited herein.

[0185] Optionally, when the first frame multiplexes a disassociation frame, the frame structure of the first frame may refer to Table 2 below.

[0186] Table 2

[0187] Serial number Information 1 Reason code …… …… Penultimate Manufacturer-defined information element Last but one Management message integrity code information element

[0188] It should be understood that Table 2 only shows a part of the cells, and the first frame may also include other cells, which are not limited herein.

[0189] Optionally, when the first frame multiplexes a re-association request frame or a disassociation frame, the first frame may include a Multi-link element. Moreover, the first frame may utilize the Type field in the Multi-link Control field of the Multi-link element to distinguish it from the existing re-association request frame or disassociation frame.

[0190] For example, the type field with a value of a first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD. Herein, the first preset value is not 0 or 1. Exemplarily, the first preset value may be 2.

[0191] Exemplarily, the type field provided by the embodiments of the present application may refer to Table 3 below.

[0192] Table 3

[0193]

[0194]

[0195] It can be seen that the embodiments of the present application utilize the reserved value (such as 2) of the original type field to define a new Multi-link element variant name. Thus, the device can determine that the frame using this Multi-link element variant name is for multi-link reconfiguration.

[0196] It should be understood that compared with the first frame being a new type of action frame, multiplexing the first frame with a re-association request frame or a disassociation frame is beneficial to avoiding excessive changes to the existing protocol, and at the same time, there is no need to re-define what information the first frame should carry, and it can also save the reserved value of the category field in the action frame.

[0197] S102. The first MLD sends the first frame to the second MLD. Correspondingly, the second MLD receives the first frame from the first MLD.

[0198] S103. The second MLD parses the first frame.

[0199] Based on Figure 4 In the embodiment shown, the first MLD triggers reconfiguration of the link between the first MLD and the second MLD by sending a first frame to the second MLD, so as to meet the communication requirements between the two MLDs and ensure normal communication between the two MLDs.

[0200] Currently, the peer device involved in the re-association process of a device is not necessarily the same device as the peer device involved in the initial association process of the device. For example, Device 1 associates with Device 2 in the initial association process and associates with Device 3 in the re-association process. Therefore, some information stored by the device is not applicable for communicating with the peer device involved in the re-association process. Therefore, the 802.11 protocol stipulates that the device will delete some information when performing the re-association process, such as the enhanced distributed channel access (EDCA) function status, block acknowledgment protocol, sequence number (SN), packet number (PN), duplicate detection cache, data to be transmitted in the queue, fragmentation and reassembly buffer, power management mode, wireless network management sleep mode. After that, the device renegotiates with the peer device involved in the re-association process to obtain this information.

[0201] Different from the existing re-association process, in the case where the first frame multiplexes the re-association request frame, the first MLD and the second MLD do not need to delete the above information to avoid the operation overhead caused by subsequent negotiation to obtain this information. That is, after the first MLD sends the first frame to the second MLD, the first MLD and the second MLD can continue to cache the following information: enhanced distributed channel access function status, block acknowledgment protocol, sequence number, packet number, duplicate detection cache, data to be transmitted in the queue, fragmentation and reassembly buffer, power management mode, wireless network management sleep mode, etc.

[0202] Optionally, based on Figure 4 the embodiment shown, as Figure 8 shown in the embodiment, the multi-link reconfiguration method may further include step S104 after step S103.

[0203] S104. The second MLD sends a second frame to the first MLD. Correspondingly, the first MLD receives the second frame from the second MLD.

[0204] Wherein, the second frame is used to respond to the first frame.

[0205] Optionally, in the case where the first frame multiplexes the disassociation frame, the second frame may be an acknowledgment (ACK) frame.

[0206] Optionally, when the first frame is a newly defined frame, the second frame can also be a newly defined frame. The second frame can be used to indicate whether to agree to reconfigure the link between the first MLD and the second MLD.

[0207] Optionally, when the first frame multiplexes a reassociation request frame, the second frame can multiplex a reassociation response frame. The second frame can be used to indicate whether to agree to reconfigure the link between the first MLD and the second MLD.

[0208] Exemplarily, when the second frame multiplexes a reassociation response frame, the frame structure of the second frame can refer to that shown in Table 4.

[0209] Table 4

[0210]

[0211] Among them, the status code can be used to indicate the response to the reconfiguration operation requested by the first frame.

[0212] Exemplarily, the specific configuration of the status code can refer to that shown in Table 5.

[0213] Table 5

[0214]

[0215] It should be understood that "rejection for unspecified reason" means that the peer device rejects the reconfiguration operation requested by the first frame, but does not give the reason for rejection.

[0216] In a possible design, the second frame can include only one status code, and this status code is for all target links.

[0217] For example, the first frame can be used to indicate adding Link 1 and Link 2, and the status code in the second frame is used to indicate success. Thus, Link 1 and Link 2 are established between the first MLD and the second MLD.

[0218] For another example, the first frame can be used to indicate adding Link 1 and Link 2, and the status code in the second frame is used to indicate rejection. Thus, Link 1 and Link 2 are not established between the first MLD and the second MLD.

[0219] In another possible design, the second frame can include one or more status codes. One status code corresponds to one target link, and this status code is used to indicate the reconfiguration status of the corresponding target link.

[0220] For example, the first frame can be used to indicate adding Link 1 and Link 2. The status code corresponding to Link 1 in the second frame is used to indicate success, and the status code corresponding to Link 2 is used to indicate failure. Thus, a link is established between the first MLD and the second MLD for Link 1, and no link is established for Link 2.

[0221] For another example, the first frame can be used to indicate deleting Link 1 and Link 2. The status code corresponding to Link 1 in the second frame is used to indicate success, and the status code corresponding to Link 2 is used to indicate failure. Thus, Link 1 is deleted between the first MLD and the second MLD, and Link 2 is not deleted.

[0222] Optionally, for a target link that is not the first link, the status code corresponding to the target link can be located in the Per-link Profile corresponding to the target link. Exemplarily, as shown in FIG. 9(a), the second frame can include a Multi-link element including a Per-link Profile, the Per-link Profile includes a Per STA control field, and the Per STA control field includes a status code.

[0223] Optionally, when the first link is the target link, the status code corresponding to the target link can be a fixed field carried in the frame body or located in the MLD-level info in the Multi-link element. Exemplarily, as shown in FIG. 9(b), the second frame can include a Multi-link element, and the Multi-link element can include the status code corresponding to the first link.

[0224] Optionally, when the first link is not the target link, the second frame can set the status code to a reserved value or disregard the status code corresponding to the first link.

[0225] Optionally, when the second frame multiplexes a reassociation response frame, the second frame can use the Type field in the Multi-link Control field in the Multi-link element to distinguish it from the existing reassociation response frame. For example, the type field with a value of a first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD. Among them, the first preset value is not 0 or 1. Exemplarily, the first preset value can be 2.

[0226] Based on Figure 8In the illustrated embodiment, the second MLD sends a second frame to the first MLD so that the first MLD learns how to reconfigure the link between the first MLD and the second MLD.

[0227] Currently, the STA and its associated AP can negotiate based on the BTM process before transferring the BSS so that the STA can transfer to a better BSS. Exemplarily, as Figure 10 shown, the BTM process may include the following steps:

[0228] When the STA discovers poor link quality or other reasons, the STA can send a Basic Service Set Transition Management (BTM) query frame to its associated AP. It should be understood that sending the BTM query frame is an optional step. After receiving the BTM query sent by the STA, the AP can reply with an ACK frame.

[0229] When the AP wants the STA to perform a BSS transfer, the AP can send a BTM request frame to the STA. After receiving the BTM request frame, the STA can reply with an ACK frame.

[0230] The STA can send a BTM response frame to the AP to indicate acceptance or rejection of the BSS transfer request. After receiving the BTM response frame, the AP can reply with an ACK frame.

[0231] Exemplarily, as shown in FIG. 11(a), the BTM query frame may include the following fields: category, Wireless Network Management (WNM) action, dialog token, BSS transition query reason, and BSS transition candidate list. Among them, the BSS transition candidate list is optional.

[0232] Among them, the BSS transition query reason field is used to indicate the reason for sending the BTM query frame. Exemplarily, the structure of the BSS transition query reason field in the related art can refer to Table 6.

[0233] Table 6

[0234]

[0235]

[0236] The BSS transition alternative list field carries one or more neighbor report elements.

[0237] Exemplarily, as shown in Fig. 11(b), the neighbor report element includes the following elements: element ID, length, BSSID, BSSID information, operating class, channel number, PHY type, optional sub-elements.

[0238] Among them, the BSSID field is used to indicate the BSSID corresponding to the reported neighbor AP. The BSSID information field is used to indicate the relevant information of the reported BSSID. The operating class field and the channel number field are used to indicate the channel to which the reported BSSID belongs. The PHY Type field indicates the physical layer type of the AP corresponding to the reported BSSID.

[0239] Optionally, the BSSID information field may include the following fields: AP reachability, security, key scope, capabilities, mobility domain, high throughput, very high throughput, fine timing measurement (FTM), high efficiency, extended range BSS (ER BSS), co-located AP, unsolicited probe response active, member of extended service set with 2.4 / 5GHz co-located AP, on-channel tunneling (OCT) supported with reporting AP, co-located with 6GHz AP, reserved field.

[0240] Exemplarily, such as Figure 12As shown, the BTM request frame may include the following fields: category, wireless network management operation, conversation token, request mode, disassociation timer, validity interval, BSS termination duration, session info URL, and BSS transition alternative list. Among them, the BSS transition alternative list is optional.

[0241] Among them, the Validity Interval field is used to indicate how many beacon cycles the BSS transition alternative list is valid for.

[0242] The Disassociation Timer field is used to indicate how long it will be before the AP sends a disassociation frame.

[0243] The request mode field is used to indicate the specific request mode. The request mode field may include the following fields: whether to carry a preferred candidate list, abridge, disassociation imminent, whether BSS termination is included, extended service set (ESS) disassociation imminent, reserved bits. Among them, the reserved bits are 3 bits.

[0244] Among them, the Preferred Candidate List Included field is used to indicate whether to carry a preferred candidate list.

[0245] The purpose of the Abridge field: If the associated AP does not recommend or prohibits the STA from switching to a BSS that does not appear in the Preferred Candidate List, the Abridged field is set to 0; if the associated AP sets the preference value of a BSS that does not appear in the Preferred Candidate List to 0, then the Abridged field is set to 1.

[0246] Use of the Disassociation Imminent field: When the Disassociation Imminent field is set to 1, it indicates that the AP will send a Disassociation frame to disassociate with the STA; when the Disassociation Imminent field is set to 0, it indicates that the AP will not send a Disassociation frame to disassociate with the STA.

[0247] The BSS Termination Included field is used to indicate whether the BSS will be closed.

[0248] The ESSDisassociation Imminent field is used to indicate whether the STA will be disassociated by the entire ESS.

[0249] Exemplarily, as Figure 13 shown, the BTM response frame may include the following fields: category, wireless network management operation, conversation token, BTM status code, BSS termination delay, Target BSSID, and BSS transition alternative list. Among them, the Target BSSID and the BSS transition alternative list are optional. Currently, in the related art, when the value of the BTM status code is 0, the BTM response frame will include the Target BSSID field.

[0250] Among them, the BTM status code is used to indicate whether the BSS transition request is accepted. The BSS termination delay is used to indicate the duration of the time period from the current time to the termination of the BSS.

[0251] Exemplarily, the BTM status code can be referred to as shown in Table 7.

[0252] Table 7

[0253] Values of BTM status code Description 0 Accepted 1 Rejected for unknown reason 2 Rejected due to insufficient beacon frames or probe responses received from alternative neighbors 3 Rejected due to insufficient available capacity of alternative neighbors

[0254] Referring to the existing BTM process, before two MLDs perform a link transfer, the two MLDs can also negotiate the link transfer so that the two MLDs can transfer from the currently established link to a better link for communication. Based on this, an embodiment of the present application provides a multi-link reconfiguration method. As Figure 14 shown, the method includes the following steps:

[0255] S201 (optional), the first MLD sends an inquiry frame to the second MLD. Correspondingly, the second MLD receives the inquiry frame from the first MLD.

[0256] In a possible design, the inquiry frame can be an existing BTM inquiry frame. That is, the first MLD does not decide whether to perform link transfer negotiation or BSS transfer negotiation. Instead, the second MLD determines whether to perform link transfer negotiation or BSS transfer negotiation according to the actual situation.

[0257] In another possible design, the first MLD can determine to perform link transfer negotiation. Thus, the inquiry frame is used to negotiate link transfer between the first MLD and the second MLD.

[0258] Based on this design, the inquiry frame can be a newly defined frame. Or, the inquiry frame can reuse the existing BTM inquiry frame.

[0259] Optionally, the inquiry frame can include one or more neighbor report elements. It should be understood that each neighbor report element corresponds to an AP adjacent to the first MLD.

[0260] In some embodiments, when the AP adjacent to the first MLD belongs to a certain AP MLD, the neighbor report element can include a Basic Multi-link element, and the Basic Multi-link element can include the MLD MAC address, the number of supported links, and capability information, etc. of the AP MLD to which the AP adjacent to the first MLD belongs.

[0261] Optionally, the Basic Multi-link element in the neighbor report element can not include Per-linkProfile to save signaling overhead.

[0262] Optionally, when the inquiry frame reuses the existing BTM inquiry frame, the inquiry frame can include a Multi-link element, and the inquiry frame can use the Type field in the Multi-link Control field of the Multi-link element to determine that the inquiry frame is used for link transfer negotiation. For example, the type field with a value of the second preset value is used to indicate that the inquiry frame is used to negotiate link transfer between the first MLD and the second MLD. Among them, the second preset value is not 0 or 1. Optionally, the second preset value can be the same as the first preset value in the above text, and no limitation is made in this regard.

[0263] Optionally, when the inquiry frame reuses the existing BTM inquiry frame, one or more values can be newly defined in the Transition QueryReason field in the inquiry frame to indicate the reasons for link transfer, such as a high link frame loss rate, poor link quality, and discovery of a better link, etc.

[0264] Optionally, the inquiry frame may further include: a link identifier or a link bit map for indicating a link with a high link frame loss rate.

[0265] Optionally, after receiving the inquiry frame, the second MLD may send an ACK frame to the first MLD.

[0266] S202. The second MLD sends a request frame to the first MLD. Correspondingly, the first MLD receives the request frame from the second MLD.

[0267] Wherein, the request frame is used to request a link transfer between the first MLD and the second MLD.

[0268] Optionally, the request frame may be used to indicate a recommended link. The recommended link may also be referred to as a suggested link, an alternative link, or other names, which is not limited herein.

[0269] Optionally, the request frame may be a newly defined frame. Alternatively, the request frame may reuse an existing BTM request frame.

[0270] Optionally, in the case where the request frame reuses an existing BTM request frame, the request mode field in the request frame may include a fourth field, and the fourth field may be used to indicate a new request mode. The new request mode may be referred to as a link transfer request mode, or a link removal mode, or a link-level disassociation mode. Exemplarily, the fourth field may use the reserved bits of the request mode field in the existing BTM frame. Exemplarily, the fourth field may occupy 1 bit. For example, Figure 22 The frame structure of the request mode field of the request frame is shown. The fourth field may be Figure 22 the link removal field in

[0271] Optionally, the request frame may include a Multi-link element, and the request frame may use the Type field in the Multi-link Control field in the Multi-link element to determine that the request frame is used for link transfer negotiation. For example, the type field with a value of a second preset value is used to indicate that the request frame is used to negotiate a link transfer between the first MLD and the second MLD. Wherein, the second preset value is not 0 or 1. Optionally, the second preset value may be the same as the first preset value in the foregoing, which is not limited herein.

[0272] Optionally, if the request frame is used to negotiate link removal, the value of the Preferred Candidate ListIncluded field included in the request frame should be set to 0 to indicate that the request frame does not carry a preferred BSS transfer alternative list.

[0273] Optionally, the request frame may include a handover alternative list field, and the handover alternative list field may include one or more neighbor report elements. Each neighbor report element corresponds to an AP adjacent to the second MLD.

[0274] As Figure 15 shown, a fifth field may be added to the BSSID information field of the neighbor report element, and this fifth field is used to indicate the ID of the MLD to which the BSS to which the link for transmitting the request frame belongs. That is, this fifth field is used to indicate that the device sending the request frame is an MLD. Thus, after receiving the request frame, the first MLD may give priority to considering a link handover with the second MLD.

[0275] Optionally, the fifth field may occupy all or part of the reserved bits in the current BSSID information field.

[0276] Exemplarily, the fifth field may have other names, such as the AP MLD ID field.

[0277] In some embodiments, when the AP adjacent to the second MLD belongs to a certain AP MLD, the neighbor report element may include a Basic Multi-link element, and the Basic Multi-link element may include the MLD MAC address of the AP MLD to which the AP adjacent to the second MLD belongs, the number of supported links, and capability information, etc.

[0278] Optionally, the Basic Multi-link element in the neighbor report element may not include Per-linkProfile to save signaling overhead.

[0279] Optionally, after receiving the request frame, the first MLD may send an ACK frame to the second MLD.

[0280] S203. The first MLD sends a response frame to the second MLD. Correspondingly, the second MLD receives the response frame from the first MLD.

[0281] Among them, the response frame is used to indicate whether to agree to a link handover between the first MLD and the second MLD.

[0282] Optionally, the response frame may be a newly defined frame. Or, the response frame may reuse the existing BTM response frame.

[0283] Optionally, in the case where the response frame reuses the existing BTM response frame, one or more newly defined values may exist in the BTM status code in the response frame, which are used to indicate the result of the link handover, such as accepting the link handover or rejecting the link handover.

[0284] Optionally, if the response frame is used to indicate acceptance of link transfer or link removal, for example, when the value of the BTM status code in the response frame is 0, the response frame does not carry the target BSSID field and the neighbor report element. If the response frame is used to indicate acceptance of BSS handover, for example, when the value of the BTM status code in the response frame is 0, the response frame may further include the target BSSID field.

[0285] In some embodiments, assuming that the first MLD selects to establish a connection with an AP that only supports a single link, the above-mentioned target BSSID field may include the BSSID corresponding to the AP. Alternatively, assuming that the first MLD selects to establish a connection with an AP MLD, the above-mentioned target BSSID field may include the MLD media access control (MAC) address of the AP MLD.

[0286] Optionally, the response frame may include one or more neighbor report elements. It should be understood that each neighbor report element corresponds to an AP adjacent to the first MLD.

[0287] In some embodiments, if the AP adjacent to the first MLD belongs to a certain AP MLD, the neighbor report element may include a Basic Multi-link element, and the Basic Multi-link element may include the MLD MAC address, the number of supported links, and capability information, etc., of the AP MLD to which the AP adjacent to the first MLD belongs.

[0288] Optionally, the Basic Multi-link element in the neighbor report element may not include the Per-linkProfile to save signaling overhead.

[0289] Optionally, after receiving the response frame, the second MLD may send an ACK frame to the second MLD.

[0290] Based on Figure 14 As shown, before performing link transfer, the first MLD and the second MLD may negotiate with each other to determine a link with better communication quality. Thus, after the first MLD and the second MLD perform link transfer, they can communicate on the link with better communication quality to ensure normal communication between the first MLD and the second MLD.

[0291] Currently, an MLD can configure multiple stations to support data transmission on multiple links. However, in some cases, the MLD has a need to delete stations. For example, when the traffic volume of the MLD is small, deleting one or more stations by the MLD is beneficial to reducing the power consumption of the MLD. However, the prior art does not provide a corresponding solution.

[0292] In view of this, embodiments of the present application provide technical solutions as shown in Figure 18 , Figure 19 and Figure 20 to achieve the purpose of deleting a site by MLD.

[0293] As shown in Figure 18 , embodiments of the present application provide a multi-link reconfiguration method, which includes the following steps:

[0294] S301. The first MLD sends a third frame in a broadcast manner on the target link.

[0295] Among them, for the first MLD, the third frame is used to indicate that the first MLD is ready to delete the target site, and the target site is a site that belongs to the first MLD and works on the target link.

[0296] Exemplarily, taking the first MLD including AP1, AP2, and AP3 as an example, AP1 works on link 1, AP2 works on link 2, and AP3 works on link 3. When the first MLD is ready to delete AP1, the first MLD sends a third frame in a broadcast manner on link 1. When the first MLD is ready to delete AP2, the first MLD sends a third frame in a broadcast manner on link 2. When the first MLD is ready to delete AP3, the first MLD sends a third frame in a broadcast manner on link 3.

[0297] In a possible design, the third frame can reuse the existing frame to ensure backward compatibility, that is, to ensure that traditional sites that support the previous protocol can parse the third frame. Exemplarily, the third frame can reuse the BTM request frame.

[0298] Optionally, when the third frame is a BTM request frame, the third frame is used to indicate that the first MLD is ready to delete the target site, and it can be specifically implemented as: the BTM request frame includes a sixth field with a value of a third preset value.

[0299] Among them, the sixth field with a value of the third preset value can be used to indicate that the MLD receiving the BTM request frame disconnects the target link with the first MLD. The sixth field with a value of the fourth preset value can be used to indicate that the MLD receiving the BTM request frame disassociates from the first MLD (that is, the MLD receiving the BTM request frame disconnects all links with the first MLD).

[0300] Optionally, the sixth field may occupy one or more reserved bits in the existing BTM request frame format. Exemplarily, when the sixth field occupies one bit, the third preset value may be 1 and the fourth preset value may be 0; or the third preset value may be 0 and the fourth preset value may be 1.

[0301] In another possible design, the third frame may be a newly defined management frame, such as a link removal request frame.

[0302] S302. The receiving device receives the third frame on the target link.

[0303] After receiving the third frame, the receiving device may parse the third frame and then perform corresponding operations according to the third frame.

[0304] Taking the receiving device as the second MLD as an example, after receiving the third frame, the second MLD is ready to delete the target link with the first MLD.

[0305] Taking the receiving device as a traditional station (i.e., a single-link device) as an example, when the third frame can reuse an existing frame, the single-link device is ready to perform a BSS handover after receiving the third frame.

[0306] Optionally, when the third frame is a newly defined management frame, the first MLD may also send a BTM request frame on the target link to trigger the traditional station and the MLD that has not received the third frame to perform a BSS handover.

[0307] Optionally, the first MLD may also send a fourth frame, which is used to indicate the time when the target station is deleted.

[0308] Exemplarily, the fourth frame may reuse an existing frame. For example, the fourth frame may reuse a beacon frame.

[0309] Optionally, when the fourth frame reuses the beacon frame, the beacon frame may add a seventh field, which is used to indicate the time when the target station is deleted. Specifically, this seventh field is used to indicate after how many target beacon transmission times (TBTTs) the target station will be deleted. Optionally, this seventh field may be located in the Per-STA Profile subelement of the target station corresponding to the Basic Multi-link element carried in the beacon frame. This seventh field may have other names, such as a delete timer field, and is not limited thereto.

[0310] Optionally, the beacon frame may further include an eighth field for indicating whether the seventh field exists in the beacon frame. Optionally, the eighth field may be located in the Per-STA Profile subelement of the corresponding target station in the Basic Multi-link element carried by the Beacon frame. The eighth field may also have other names, such as the delete timer present field, which is not limited herein.

[0311] Based on Figure 18 the illustrated embodiment, the first MLD sends a third frame on the target link so that other devices can learn that the first MLD is about to delete the target station.

[0312] As Figure 19 illustrated, an embodiment of the present application provides a multi-link reconfiguration method, which includes the following steps:

[0313] S401. The first MLD broadcasts a fifth frame on the target link.

[0314] Wherein, the fifth frame is used to indicate that the first MLD deletes the target station, and the target station is a station that belongs to the first MLD and operates on the target link.

[0315] Exemplarily, taking the first MLD including AP1, AP2, and AP3 as an example, AP1 operates on link 1, AP2 operates on link 2, and AP3 operates on link 3. When the first MLD is about to delete AP1, the first MLD broadcasts a fifth frame on link 1. Or, when the first MLD is about to delete AP2, the first MLD broadcasts a fifth frame on link 2. Or, when the first MLD is about to delete AP3, the first MLD broadcasts a fifth frame on link 3.

[0316] In a possible design, the fifth frame can reuse an existing frame to ensure backward compatibility, that is, to ensure that traditional stations supporting previous protocols can parse the fifth frame. Exemplarily, the fifth frame can be a disassociation frame.

[0317] It should be understood that in the case where the fifth frame multiplexes the disassociation frame, in order for the receiving-end device of the disassociation frame to know that the function of the disassociation frame is to indicate the deletion of the current link rather than indicating disassociation, it is necessary to improve the disassociation frame. Optionally, in the case where the fifth frame is a disassociation frame, the fifth frame is used to represent the first MLD deleting the current link, and it can be specifically implemented as: the disassociation frame includes a field for multi-link reconfiguration. Optionally, the field for multi-link reconfiguration does not include information about the target link. The field for multi-link reconfiguration may have other names, such as multi-link reconfiguration variant multi-link element (MLReconfiguration Variant ML element), and no limitation is imposed thereon. Optionally, for a broadcast Disassociation frame, only the current link can be deleted. One implementation is that the multi-link reconfiguration variant multi-link element may not include the Per-link Profile. For a unicast Disassociation frame, one or more links can be deleted. One implementation is to indicate the target link by carrying the Per-link Profile or Link ID or Link Bitmap of the corresponding link in the multi-link reconfiguration variant multi-link element.

[0318] Alternatively, the fifth frame is used to represent the first MLD deleting the current link, and it can be specifically implemented as: the fifth frame includes a reason code field, and the reason code field is used to indicate the deletion of the current link. It should be understood that compared with the reason code field included in the disassociation frame in the related art, the reason code field included in the fifth frame in the embodiment of the present application adds a value to represent the deletion of the current link.

[0319] Optionally, in the case where the fifth frame multiplexes the disassociation frame, the disassociation frame has different functions in different cases. For example, in the case where the disassociation frame includes a field for multi-link reconfiguration, the disassociation frame is the fifth frame provided in the embodiment of the present application, and the MLD that receives the disassociation frame will disconnect the current link with the first MLD. In the case where the disassociation frame does not include a field for multi-link reconfiguration, the disassociation frame is the disassociation frame defined by the existing standard, and the MLD that receives the disassociation frame will disassociate from the first MLD.

[0320] In another possible design, the fifth frame can be a newly defined management frame, such as a link removal notify frame, instead of reusing an existing frame. This way, the functions of the existing frames do not need to be changed.

[0321] S402. The receiving device receives the fifth frame on the target link.

[0322] After receiving the fifth frame, the receiving device can parse the fifth frame and then perform corresponding operations based on the fifth frame.

[0323] Taking the receiving device as the second MLD as an example, after receiving the fifth frame, the second MLD deletes the target link with the first MLD. Furthermore, the second MLD and the first MLD do not transmit data on the target link.

[0324] Taking the receiving device as a traditional station (i.e., a single-link device) as an example, in the case where the fifth frame reuses an existing frame, the single-link device can disassociate from the first MLD after receiving the fifth frame.

[0325] Optionally, in the case where the fifth frame is a newly defined management frame, the first MLD can also send a Disassociation frame defined by the existing standard on the target link to disassociate from the traditional station and the MLD that has not received the fifth frame before.

[0326] Based on Figure 19 the embodiments shown, the first MLD sends the fifth frame on the target link so that other devices can learn that the first MLD deletes the target station.

[0327] Optionally, Figure 18 the embodiments shown can be used in combination with Figure 19 the embodiments shown. As Figure 20 shown, an embodiment of the present application provides a multi-link reconfiguration method, and the method includes the following steps:

[0328] S501. The first MLD broadcasts the third frame on the target link.

[0329] S502. The receiving device receives the third frame on the target link.

[0330] S503. The first MLD broadcasts the fifth frame on the target link.

[0331] S504. The receiving device receives the fifth frame on the target link.

[0332] Based on Figure 20In the illustrated embodiment, the first MLD may first send a third frame to enable other devices to prepare for the first MLD to delete the target station. Subsequently, the first MLD may send a fifth frame to delete the target station.

[0333] Currently, the MLD may configure multiple stations to support data transmission on multiple links. However, in some cases, the MLD has a need to add stations. For example, when the traffic volume of the MLD is large, the MLD may add one or more stations affiliated with the MLD to share the data transmission pressure. However, the prior art does not provide a corresponding solution.

[0334] In view of this, an embodiment of the present application provides a multi-link reconfiguration method. As Figure 21 shown, the method includes the following steps:

[0335] S601. The first MLD sends a sixth frame in a broadcast manner.

[0336] Among them, the sixth frame is used to indicate that the first MLD adds a target station affiliated with the first MLD. The target station operates on the target link.

[0337] Optionally, the sixth frame may include information about the target station. Exemplarily, the information about the target station includes BSS operation parameters, BSS capability information, etc.

[0338] Optionally, the sixth frame may reuse an existing frame. For example, the sixth frame may reuse a beacon frame. The sixth frame including the information about the target station may be specifically implemented as follows: the ML element or Reduced Neighbor Report in the beacon frame includes the information about the target station.

[0339] As a possible implementation manner, the first MLD sends the sixth frame in the form of a beacon frame on all links it supports.

[0340] S602. The receiving device receives the sixth frame.

[0341] Based on Figure 21 In the illustrated embodiment, the first MLD sends the sixth frame in a broadcast manner so that other devices can learn that the first MLD adds a target station. Thus, other devices can establish a link with the target station of the first MLD for data transmission.

[0342] In the embodiment of the present application, the MLD deleting a station affiliated with the MLD may also be described as: the MLD closing / deactivating a station affiliated with the MLD, or closing the BSS responsible for the station, which is not limited herein.

[0343] The MLD adds the stations affiliated with the MLD, which can also be described as: the MLD turns on / activates the stations affiliated with the MLD, or turns on the BSS responsible for the stations, and this is not limited.

[0344] The above mainly introduces the solution provided by the embodiments of the present application from the perspective of methods. It can be understood that in order for the communication device to implement the above functions, it includes the corresponding hardware structure and / or software module for executing each function. Those skilled in the art should easily realize that, combining the units and algorithm steps of each example described in the embodiments disclosed in this article, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0345] The embodiments of the present application can divide the device into functional modules according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one functional module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. The division of modules in the embodiments of the present application is illustrative, only a logical function division, and there can be other division methods in actual implementation. The following takes the example of dividing each functional module corresponding to each function for illustration:

[0346] As Figure 16 shown, a communication device provided by an embodiment of the present application includes: a processing module 101 and a communication module 102.

[0347] Exemplarily, when the communication device is the first MLD, or the communication device is applied to the first MLD, the processing module 101 is used to support the first MLD to execute Figure 4 the step S101 in Figure 4 The communication module 102 is used to support the first MLD to execute Figure 8 the step S104 in Figure 14 the steps S201 - S203 in Figure 18 the step S301 in Figure 19 the step S401 in Figure 20 the steps S501 and S503 in Figure 21 the step S601 in

[0348] Exemplarily, when the communication device is the second MLD, or the communication device is applied to the second MLD, the processing module 101 is used to support the second MLD to execute Figure 4Step S103 in it. The communication module 102 is used to support the execution of the second MLD Figure 4 Step S102 in it, Figure 8 Step S104 in it, Figure 14 Steps S201 - S203 in it, Figure 18 Step S302 in it, Figure 19 Step S402 in it, Figure 20 Steps S502 and S504 in it, Figure 21 Step S602 in it.

[0349] The possible product forms of the communication device are introduced below. It should be understood that any product form with the characteristics of the communication device falls within the protection scope of this application. It should also be understood that the following introduction is only for example, and does not limit the product forms of the communication device in the embodiments of this application to this.

[0350] Figure 17 is the structural diagram of the possible product forms of the communication device described in the embodiments of this application.

[0351] As a possible product form, the communication device described in the embodiments of this application can be a multi - link device, and the multi - link device includes a processor 201 and a transceiver 202. Optionally, the multi - link device further includes a memory 203.

[0352] Exemplarily, when the multi - link device is the first MLD, the processor 201 is used to support the first MLD to execute Figure 4 Step S101 in it. The transceiver 202 is used to support the first MLD to execute Figure 4 Step S102 in it, Figure 8 Step S104 in it, Figure 14 Steps S201 - S203 in it, Figure 18 Step S301 in it, Figure 19 Step S401 in it, Figure 20 Steps S501 and S503 in it, Figure 21 Step S601 in it.

[0353] Exemplarily, when the multi - link device is the second MLD, the processor 201 is used to support the second MLD to execute Figure 4 Step S103 in it. The transceiver 202 is used to support the second MLD to execute Figure 4 Step S102 in it, Figure 8 Step S104 in it, Figure 14 Steps S201 - S203 in it, Figure 18 Step S302 in it, Figure 19 Step S402 in it, Figure 20 Steps S502 and S504 in it, Figure 21Step S602 in

[0354] As another possible product form, the communication device described in the embodiments of the present application may also be implemented by a chip. The chip includes: a processing circuit 201 and a transceiver pin 202. Optionally, the chip may further include a storage medium 203.

[0355] As another possible product form, the communication device described in the embodiments of the present application may also be implemented using the following circuits or devices: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuits, or any combination of circuits capable of performing the various functions described throughout the present application.

[0356] Optionally, the embodiments of the present application further provide a computer-readable storage medium storing computer instructions, which, when run on a computer, cause the computer to execute the methods in the foregoing method embodiments.

[0357] Optionally, the embodiments of the present application further provide a computer program product containing computer instructions, which, when run on a computer, cause the computer to execute the methods in the foregoing method embodiments.

[0358] It should be understood that the computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or a data center that includes one or more integrated media. The available medium may be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium, or a semiconductor medium (such as a solid-state drive), etc.

[0359] Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the above division of each functional module is used as an example. In actual applications, the above functions may be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.

[0360] It should be understood that the devices and methods disclosed in several embodiments provided in this application can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in electrical, mechanical or other forms.

[0361] The units described as separate components may or may not be physically separated. The components displayed as units can be one physical unit or multiple physical units, that is, they can be located in one place, or they can be distributed to multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0362] In addition, the functional units in each embodiment of this application can be integrated in a processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0363] If the above 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 readable storage medium. Based on such an understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to enable a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods described in each embodiment of this application.

[0364] As described above, the above are only the specific implementation manners of this application, but the protection scope of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

1. A reconfiguration method for multiple links, applied to a second multi-link device (MLD), characterized in that, The method includes: The second MLD receives a Basic Service Set Transition Management (BTM) request frame from the first MLD. The BTM request frame includes a first field that occupies 1 bit and is used to indicate that the second MLD receiving the BTM request frame disconnects the link for transmitting the BTM request frame between the second MLD and the first MLD, or indicates that the second MLD de-associates from the first MLD. Parse the BTM request frame.

2. The method according to claim 1, characterized in that, The value of the first field is a first preset value, which is used to indicate that the second MLD disconnects the link for transmitting the BTM request frame between the second MLD and the first MLD.

3. The method according to claim 2, wherein The value of the first field is a second preset value, which is used to indicate that the second MLD disconnects all links between the second MLD and the first MLD.

4. The method according to claim 3, wherein The first preset value is 1, and the second preset value is 0.

5. The method according to claim 1, wherein The method further includes: Send a Basic Service Set Transition Management (BTM) response frame, which is used to indicate whether to agree to perform a Basic Service Set (BSS) transition between the first MLD and the second MLD.

6. The method according to claim 5, characterized in that The BTM response frame includes a Target BSSID field, which is used to indicate the MLD Media Access Control (MAC) address of the Access Point (AP) MLD that the second MLD selects to establish a connection with.

7. The method according to claim 5 or 6, characterized in that, The BTM response frame includes one or more neighbor report elements. The neighbor report element includes a Basic Multi-link element, and the Basic Multi-link element does not include per-link profile information.

8. A multi-link device MLD, applied to a second multi-link device MLD, characterized in that, Includes a processing module and a communication module; The communication module is configured to receive a Basic Service Set Transition Management (BTM) request frame from the first MLD. The BTM request frame includes a first field that occupies 1 bit and is used to indicate that the second MLD receiving the BTM request frame disconnects the link for transmitting the BTM request frame between the second MLD and the first MLD, or indicates that the second MLD de-associates from the first MLD. The processing module is configured to parse the BTM request frame.

9. The MLD according to claim 8, wherein, The value of the first field is a first preset value, which is used to indicate that the second MLD disconnects the link for transmitting the BTM request frame between the second MLD and the first MLD.

10. The MLD according to claim 9, wherein, The value of the first field is a second preset value, which is used to indicate that the second MLD disconnects all links between the second MLD and the first MLD.

11. The MLD according to claim 10, wherein The first preset value is 1, and the second preset value is 0.

12. The MLD according to claim 8, wherein, The communication module is further configured to: Send a Basic Service Set Transition Management (BTM) response frame, which is used to indicate whether to agree to perform a Basic Service Set (BSS) transition between the first MLD and the second MLD.

13. The MLD according to claim 12, characterized in that, The BTM response frame includes a Target BSSID field, which is used to indicate the MLD Media Access Control (MAC) address of the Access Point (AP) MLD that the second MLD selects to establish a connection with.

14. The MLD according to claim 12 or 13, characterized in that, The BTM response frame includes one or more neighbor report elements. The neighbor report element includes a Basic Multi-link element, and the Basic The multi-link element does not include the per-link profile for each link configuration information.

15. A multi-link device MLD, characterized in that, It includes a processor and a transceiver. The processor is used to perform the processing operations in any one of the methods of claims 1 to 7, and the transceiver is used to perform the communication operations in any one of the methods of claims 1 to 7.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions. When the computer instructions are run on a computer, the computer is caused to execute the method according to any one of claims 1 to 7.

17. A chip, characterized in that, The chip includes a processing circuit and transceiver pins; the processing circuit is used to perform the processing operations in any one of the methods of claims 1 to 7, and the transceiver pins are used to perform the communication operations in any one of the methods of claims 1 to 7.

Images