Method and apparatus for reconfiguring multiple links

Abstract

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

Description

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

[0002] This application claims priority to Chinese Patent Application No. 202110058021.9, filed on January 15, 2021, entitled "Multi-link Reconfiguration Method and Apparatus", and to Chinese Patent Application No. 202110713587.0, filed on June 25, 2021, entitled "Multi-link Reconfiguration Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a method and apparatus for reconfiguring multiple links. Background Technology

[0004] To achieve the technical goal of extremely high throughput, the Institute of Electrical and Electronics Engineers (IEEE) 802.11be standard includes multi-link (ML) communication as one of its key technologies. Multi-link devices (MLDs) supporting ML communication have the ability to transmit and receive across multiple links, allowing them to utilize greater bandwidth for data transmission and significantly improving throughput. A link refers to the spatial path along which an MLD transmits data within a single frequency band.

[0005] Currently, two MLDs can establish one or more links for communication through an association process. However, in some scenarios, the established links between two MLDs may not be sufficient to meet their data transmission needs. The industry has not yet provided a solution to this problem. Summary of the Invention

[0006] This application provides a method and apparatus for reconfiguring multiple links, used to reconfigure the links between two MLDs.

[0007] Firstly, a multi-link reconfiguration method is provided, comprising: a first MLD generating a first frame, the first frame being used to reconfigure the link between the first MLD and the second MLD; and the first MLD sending 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, thereby satisfying the data transmission requirements between the first MLD and the second MLD.

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

[0009] Optionally, the first frame can reuse an existing frame, such as a reassociation request frame or a deassociation frame. It should be understood that reusing a reassociation request frame or a deassociation frame as the first frame can make significant changes to the existing protocol without redefining the information elements that the first frame should include, and saves the reserved value of the category field in the action frame.

[0010] Optionally, if the first frame reuses the reassociation request frame, after the first MLD sends the first frame to the second MLD, the first and second MLDs can continue to cache the following information: enhanced distributed channel access (EDCA) function status, block acknowledgment protocol, sequence number (SN), packet number (PN), deduplication detection buffer, data to be transmitted in the queue, fragmentation and reassembly buffer, power management mode, and radio network management sleep mode. It should be understood that, unlike existing technologies where the device needs to delete the above information during the reassociation process, in this embodiment, although the first frame reuses the reassociation request frame, it does not trigger the first and second MLDs to delete the above information. Therefore, the first and second MLDs do not need to renegotiate and obtain the above information after changing the link configuration, which helps to save the overhead of negotiating the above information.

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

[0012] In one possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: the first frame instructing the removal of a target link from the existing link between the first MLD and the second MLD. It should be understood that the first MLD and the second MLD can save corresponding energy consumption by removing one or more links.

[0013] In one 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, which is used to transmit data between the first MLD and the second MLD.

[0014] In one possible design, the first frame includes a first field indicating the type of reconfiguration, which may include: deleting a link, adding a link, or transferring a link. Based on this design, a single type of first frame can implement multiple types of link reconfiguration.

[0015] In one possible design, the first frame may include a multi-link element, which includes per-link profile configuration information, and the per-link profile includes a first field.

[0016] In one possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: if the first field is used to indicate link deletion, the first frame is used to indicate the deletion of the target link from the link already established between the first MLD and the second MLD; or, if the first field is used to indicate link addition, the first frame is used to indicate the establishment of a target link between the first MLD and the second MLD; or, if the first field is used to indicate link transfer, 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 link transfer allows two MLDs to switch from a poor-quality link to a better-quality link for data transmission, which helps improve the service quality of data transmission between the two MLDs.

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

[0019] In one possible design, the first frame may include a multi-link element, which includes a per-link profile, and the per-link profile includes a second field.

[0020] In one possible design, the second field includes a bitmap, which 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 one possible design, the second field includes an identifier for the target link.

[0022] In one possible design, the first frame also includes a third field, which indicates whether the first link is the target link, and the first link is the link used to transmit the first frame.

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

[0024] In one possible design, the first frame is either a reassociation request frame or a deassociation 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 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, the first preset value is not 0 or 1.

[0025] In one possible design, the method further includes: a first MLD receiving a request frame from a second MLD, the request frame requesting a link transfer between the first MLD and the second MLD; and the first MLD sending a response frame to the second MLD, the response frame indicating whether it agrees to the link transfer between the first MLD and the second MLD. Based on this design, the negotiation between the two MLDs before the link transfer allows them to determine a better link for the transfer, ensuring the quality of data transmission between the two MLDs after the link transfer.

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

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

[0028] Secondly, a multi-link reconfiguration method is provided, comprising: a second MLD receiving a first frame from a first MLD, the first frame being used to reconfigure the link between the first MLD and the second MLD; and the second MLD parsing the first frame.

[0029] In one 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 instruct the establishment of a target link between the first MLD and the second MLD.

[0030] In one 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 instruct the removal of the target link from the link already established between the first MLD and the second MLD.

[0031] In one 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, which is used to transmit data between the first MLD and the second MLD.

[0032] In one possible design, the first frame includes a first field, which indicates the type of reconfiguration, including: deleting a link, adding a link, or transferring a link.

[0033] In one possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: if the first field is used to indicate link deletion, the first frame is used to indicate the deletion of the target link from the link already established between the first MLD and the second MLD; or, if the first field is used to indicate link addition, the first frame is used to indicate the establishment of a target link between the first MLD and the second MLD; or, if the first field is used to indicate link transfer, 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 one possible design, the first frame also includes a second field, which is used to indicate the target link.

[0035] In one possible design, the second field includes a bitmap, which 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 one possible design, the second field includes an identifier for the target link.

[0037] In one possible design, the first frame also includes a third field, which indicates whether the first link is the target link, and the first link is the link used to transmit the first frame.

[0038] In one possible design, the first frame is either a reassociation request frame or a deassociation 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 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. The first preset value is not 0 or 1.

[0039] In one possible design, the method further includes: the second MLD sending a request frame to the first MLD, the request frame being used to request a link transfer between the first MLD and the second MLD; and the second MLD receiving a response frame from the first MLD, the response frame being used to indicate whether it agrees to the link transfer between the first MLD and the second MLD.

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

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

[0042] Thirdly, an MLD is provided, including a processing module and a communication module. The processing module generates a first frame, which is used to reconfigure the link between the first MLD and the second MLD. The communication module sends the first frame to the second MLD.

[0043] In one 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 instruct the establishment of a target link between the first MLD and the second MLD.

[0044] In one 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 instruct the removal of the target link from the link already established between the first MLD and the second MLD.

[0045] In one 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, which is used to transmit data between the first MLD and the second MLD.

[0046] In one possible design, the first frame includes a first field, which indicates the type of reconfiguration, including: deleting a link, adding a link, or transferring a link.

[0047] In one possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: if the first field is used to indicate link deletion, the first frame is used to indicate the deletion of the target link from the link already established between the first MLD and the second MLD; or, if the first field is used to indicate link addition, the first frame is used to indicate the establishment of a target link between the first MLD and the second MLD; or, if the first field is used to indicate link transfer, 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 one possible design, the first frame also includes a second field, which is used to indicate the target link.

[0049] In one possible design, the second field includes a bitmap, which 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 one possible design, the second field includes an identifier for the target link.

[0051] In one possible design, the first frame also includes a third field, which indicates whether the first link is the target link, and the first link is the link used to transmit the first frame.

[0052] In one possible design, the first frame is either a reassociation request frame or a deassociation 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 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. The first preset value is not 0 or 1.

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

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

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

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

[0057] In one 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 instruct the establishment of a target link between the first MLD and the second MLD.

[0058] In one 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 instruct the removal of the target link from the link already established between the first MLD and the second MLD.

[0059] In one 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, which is used to transmit data between the first MLD and the second MLD.

[0060] In one possible design, the first frame includes a first field, which indicates the type of reconfiguration, including: deleting a link, adding a link, or transferring a link.

[0061] In one possible design, the first frame is used to reconfigure the link between the first MLD and the second MLD, including: if the first field is used to indicate link deletion, the first frame is used to indicate the deletion of the target link from the link already established between the first MLD and the second MLD; or, if the first field is used to indicate link addition, the first frame is used to indicate the establishment of a target link between the first MLD and the second MLD; or, if the first field is used to indicate link transfer, 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 one possible design, the first frame also includes a second field, which is used to indicate the target link.

[0063] In one possible design, the second field includes a bitmap, which 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 one possible design, the second field includes an identifier for the target link.

[0065] In one possible design, the first frame also includes a third field, which indicates whether the first link is the target link, and the first link is the link used to transmit the first frame.

[0066] In one possible design, the first frame is either a reassociation request frame or a deassociation 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 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. The first preset value is not 0 or 1.

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

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

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

[0070] Fifthly, an MLD is provided, including a processor and a transceiver. The processor is used to perform processing actions in the corresponding methods of the first or second aspect described above, and the transceiver pins are used to perform communication actions in the corresponding methods of the first or second aspect described above.

[0071] In a sixth aspect, a computer-readable storage medium is provided, wherein instructions are stored therein, which, when executed on a computer, cause the computer to perform the method involved in any of the designs of the first or second aspect described above.

[0072] In a seventh aspect, a computer program product comprising instructions is provided, which, when run on a computer, causes the computer to perform the method involved in any of the designs in the first or second aspect described above.

[0073] Eighthly, a chip is provided, comprising: a processing circuit and transceiver pins, the processing circuit being configured to perform processing actions in the corresponding methods of the first or second aspect described above, and the transceiver pins being configured to perform communication actions in the corresponding methods of the first or second aspect described above.

[0074] Understandably, any of the MLDs, chips, computer storage media, or computer program products provided above are used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here. Attached Figure Description

[0075] Figure 1 This application provides a schematic diagram of a communication scenario between an AP multi-link device and a STA multi-link device.

[0076] Figure 2(a) and Figure 2(b) are schematic diagrams of the structure of AP multi-link devices and STA multi-link devices participating in communication;

[0077] Figure 3A schematic diagram of a frame structure of a multi-link element provided in an embodiment of this application;

[0078] Figure 4 A flowchart illustrating a multi-link reconfiguration method provided in an embodiment of this application;

[0079] Figure 5 A schematic diagram of another frame structure of a multi-link element provided in an embodiment of this application;

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

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

[0082] Figure 7 A schematic diagram of another frame structure of a multi-link element provided in an embodiment of this application;

[0083] Figure 8 A flowchart illustrating another multi-link reconfiguration method provided in an embodiment of this application;

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

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

[0086] Figure 10 This is a schematic diagram of the BTM process in related technologies;

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

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

[0089] Figure 12 This is a schematic diagram of the frame structure of a BTM request frame in related technologies;

[0090] Figure 13 This is a schematic diagram of the frame structure of a BTM response frame in related technologies;

[0091] Figure 14 A flowchart illustrating another multi-link reconfiguration method provided in an embodiment of this application;

[0092] Figure 15A schematic diagram of the frame structure of a neighbor report element provided in an embodiment of this application;

[0093] Figure 16 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0094] Figure 17 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0095] Figure 18 A flowchart illustrating a multi-link reconfiguration method provided in an embodiment of this application;

[0096] Figure 19 A flowchart illustrating another multi-link reconfiguration method provided in an embodiment of this application;

[0097] Figure 20 A flowchart illustrating another multi-link reconfiguration method provided in an embodiment of this application;

[0098] Figure 21 A flowchart illustrating another multi-link reconfiguration method provided in an embodiment of this application;

[0099] Figure 22 This is a schematic diagram of the frame structure of a request pattern field provided in an embodiment of this application. Detailed Implementation

[0100] In the description of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. The "and / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "multiple" means two or more. The terms "first," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., do not necessarily imply differences.

[0101] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0102] The technical solutions provided in this application can be applied to various communication systems, such as systems using the IEEE 802.11 standard. For example, the IEEE 802.11 standard includes, but is not limited to, the 802.11be standard, or next-generation 802.11 standards. The applicable scenarios for the technical solutions in this application include: communication between AP and STA, communication between APs, and communication between STAs.

[0103] The STA mentioned in this application can be any user terminal, user equipment, access device, subscriber station, subscriber unit, mobile station, user agent, user equipment, or other name with wireless communication capabilities. 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 capabilities, as well as various forms of user equipment (UE), mobile station (MS), terminal, terminal equipment, portable communication devices, handheld devices, portable computing devices, entertainment devices, gaming devices or systems, global positioning system devices, or any other suitable device configured for network communication via wireless media. For ease of description, the devices mentioned above are collectively referred to as a site or STA.

[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 Stations (STAs). The AP can serve as the central hub of the communication system and can be a base station, router, gateway, repeater, communication server, switch, or bridge, among other communication devices. The base station can include various forms of macro base stations, micro base stations, repeater stations, etc. For ease of description, the devices mentioned above are collectively referred to as Access Points (APs).

[0105] The IEEE 802.11 next-generation Wireless Fidelity (WiFi) protocol's Extremely High Throughput (EHT) devices support increased peak throughput and reduced service transmission latency through multiple streams, multiple frequency bands (e.g., 2.4 GHz, 5 GHz, and 6 GHz bands), and cooperation of multiple channels on the same frequency band. This multi-band or multi-channel approach can be collectively referred to as multi-link.

[0106] A multi-link device includes one or more affiliated sites, which can be logical sites or physical sites. In the embodiments of this application, "a multi-link device includes affiliated sites" can be briefly described as "a multi-link device includes sites".

[0107] The affiliated site can be an access point (AP) or a non-access point station (non-AP STA). For ease of description, in this application embodiment, a multi-link device whose affiliated site is an AP can be referred to as a multi-link AP, or AP MLD, or multi-link AP device; a multi-link device whose affiliated site is a STA can be referred to as a multi-link STA, or multi-link STA device, or STA MLD, or non-AP MLD.

[0108] Multi-link devices can implement wireless communication by following the 802.11 protocol. For example, the 802.11 protocol can be the 802.11ax protocol, the 802.11be protocol, and the next-generation 802.11 protocol, and the embodiments of this application are not limited thereto.

[0109] A multi-link device can communicate with other devices. In this embodiment, the other devices may or may not be multi-link devices.

[0110] For example, Figure 1 This is a schematic diagram illustrating a communication scenario between an AP multi-link device and a STA multi-link device. (Example:) Figure 1 As shown, an AP multi-link device can be associated with multiple STA multi-link devices and a single-link STA. For example, AP multi-link device 100 is associated with STA multi-link devices 200, STA multi-link devices 300, and STA 400. It should be understood that multiple APs in an AP multi-link device operate on multiple links, and multiple STAs in a STA multi-link device operate on multiple links. One STA in a STA multi-link device is associated with one AP in the AP multi-link device on its operating link. A single-link STA is associated with one AP in the AP multi-link device on its operating link.

[0111] Multi-link devices can operate in frequency bands including, but not limited to, sub-1GHz, 2.4GHz, 5GHz, 6GHz, and high-frequency 60GHz. Figures 2(a) and 2(b) illustrate two schematic diagrams of multi-link devices communicating with other devices through multiple links in a wireless local area network.

[0112] Figure 2(a) illustrates a scenario of communication between an AP multi-link device 101 and a STA multi-link device 102. The AP multi-link device 101 includes AP101-1 and AP101-2, and the STA multi-link device 102 includes STA102-1 and STA102-2. 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) illustrates a scenario where AP multi-link device 101 communicates with STA multi-link devices 102, STA multi-link devices 103, and STA 104. AP multi-link device 101 includes subordinate AP101-1 to AP101-3. STA multi-link device 102 includes two subordinate STAs, STA102-1 and STA102-2. STA multi-link device 103 includes two subordinate STAs, STA103-1, STA103-2, and STA103-3. STA 104 is a single-link device (SLD). The AP multi-link device can communicate with STA multi-link device 102 using links 1 and 3, communicate with STA 103 using links 2 and 3, and communicate with STA 104 using link 1. In one example, STA104 operates in the 2.4 GHz band; STA multi-link device 103 includes STA103-1 and STA103-2, with STA103-1 operating in the 5 GHz band and STA103-2 operating in the 6 GHz band; STA multi-link device 102 includes STA102-1 and STA102-2, with STA102-1 operating in the 2.4 GHz band and STA102-2 operating in the 6 GHz band. AP101-1, operating in the 2.4 GHz band, can transmit uplink or downlink data with STA104 and STA102-2 in STA multi-link device 102 via link 1. AP101-2, operating in the 5 GHz band, can transmit uplink or downlink data with STA103-1, operating in the 5 GHz band, in STA multi-link device 103 via link 2. AP101-3, operating in the 6GHz band in AP multi-link device 101, can transmit uplink or downlink data with STA102-2, operating in the 6GHz band in STA multi-link device 102, via link 3. It can also transmit uplink or downlink data with STA103-2 in STA multi-link device 102 via link 3.

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

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

[0116] Multi-link devices can support simultaneous transmit and receive (STR) data, or they may not support simultaneous transmit and receive data. Supporting simultaneous transmit and receive data means that while a multi-link device is transmitting data on one link, it can receive data on another link. Not supporting simultaneous transmit and receive data means that while a multi-link device is transmitting data on one link, it cannot receive data on another link.

[0117] For example, a non-AP MLD can establish associations with multiple links simultaneously with an AP MLD through a multi-link establishment operation on one of the links. During the association process, the non-AP MLD and AP MLD can exchange Multi-link Association Request / Response frames on one link. The link used to exchange Multi-link Association Request / Response frames can be called the transmission link (transmission link), and the other links are non-transmitted links. It should be understood that the Multi-link Association Request / Response can carry information about the multiple links to be associated, enabling simultaneous association of multiple links between the non-AP MLD and AP MLD.

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

[0119] To carry information about non-AP MLDs within existing association request frames, the protocol defines a multi-link element. For example, such as... Figure 3 As shown, the information carried by a multi-link element is divided into two parts: MLD-level info and per-link profile configuration information. The per-link profile can also be called a per-STA profile. It should be understood that the per-link profile is optional. That is, a multi-link element may not include a per-link profile, or it may include one or more per-link profiles. For example, Figure 3 The diagram shows that a multi-link element has a per-link profile x and a per-link profile y.

[0120] The MLD-level info includes the following fields: Multi-link control, and one or more fields. For example, one or more fields may include the following fields: element ID, length, extended element ID, and other fields.

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

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

[0123] The data fields in the Per-link Profile include one or more of the following fields: Per-STA control field, one or more elements, and non-inheritance elements. The non-inheritance elements are optional.

[0124] Each site control domain includes at least a link ID. It should be understood that a non-AP MLD can obtain link information (e.g., link identifier) ​​for each link by receiving probe response frames or beacon frames.

[0125] In some scenarios, after two MLDs establish a connection, the established link may not be able to meet the data transmission requirements between the two MLDs.

[0126] For example, two MLDs may establish only one link during initial association, but if there is a large amount of data to be transmitted between the two MLDs, one link cannot meet the throughput requirements of data transmission, so an additional link needs to be added between the two MLDs.

[0127] For example, two MLDs may establish multiple links during initial association, 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 between the two MLDs need to be removed to save energy consumption.

[0128] For example, two MLDs establish link 1 during initial association, but the communication quality of link 1 is poor. Therefore, the two MLDs want to switch from link 1 to link 2 for data transmission.

[0129] Currently, the industry has not provided a solution on how to change the link configuration after MLD is associated.

[0130] To support changes in link configurations after two MLDs are associated, embodiments of this application provide a method for reconfiguring multiple links. For example... Figure 4 As shown, the method includes the following steps:

[0131] S101, The first MLD generates the first frame.

[0132] 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 this application, the first frame can be a newly defined frame or a reused existing frame (e.g., a reassociation request frame or a deassociation frame), and there is no limitation thereto.

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

[0136] Design 1-1: The first frame is used to indicate the establishment of the 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 a link between the first MLD and the second MLD that has not yet been established.

[0138] For example, links 1 and 2 have already been established between the first MLD and the second MLD based on an association process. The first frame is used to indicate the establishment of link 3, so that the first MLD and the second MLD can then establish link 3. Afterwards, the first MLD and the second MLD can use links 1, 2, and 3 to transmit data.

[0139] In this embodiment, two MLDs can transmit data on an established link, but cannot transmit data on an unestablished link. The two MLDs can exchange a subset of management frames (e.g., association request / response frames) on an unestablished link to establish a link.

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

[0141] Specifically, the first frame is used to instruct the removal of the target link from the existing link between the first MLD and the second MLD. The target link is a link that is currently established between the first MLD and the second MLD.

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

[0143] It should be understood that, based on Design 1-1 and Design 1-2, the function and type of the first frame can be associated. Therefore, the second MLD can determine the function of the first frame based on its type. For example, if the first frame of Design 1-1 is a reassociation request frame, the second MLD, upon receiving a reassociation request frame for multi-link reconfiguration, can determine that this reassociation request frame is used to establish the target link. Alternatively, if the first frame of Design 1-2 is a deassociation frame, the second MLD, upon receiving a deassociation frame for multi-link reconfiguration, can determine that this deassociation frame is used to delete the target link.

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

[0145] In other words, the first frame is used to indicate that data transmission can occur between the first MLD and the second MLD on the target link.

[0146] The target link can be used for data transmission between the first MLD and the second MLD. The target link belongs to a supported link between the first MLD and the second MLD. For example, the target link can belong to a link between the first MLD and the second MLD that has not yet been established. Alternatively, the target link can also belong to a link between the first MLD and the second MLD that has already been established.

[0147] For example, links 1 and 2 have been established between the first MLD and the second MLD based on an association process. The first frame is used to indicate links 2, 3, and 4, thereby deleting link 1 and creating links 3 and 4 between the first MLD and the second MLD. In this way, data can be transmitted between the first MLD and the second MLD using links 2, 3, and 4, but not using link 1.

[0148] It should be understood that the idea behind Design 1-3 is that the first frame indicates the final link (i.e., the target link) that should be established between the first MLD and the second MLD, so that the actual reconfiguration operation (e.g., deleting a link and / or adding a link) can be determined between the first MLD and the second MLD based on the currently established link and the final link that should be established.

[0149] Design 1-4: The first frame includes a first field, which indicates the type of reconfiguration. The type of reconfiguration includes deleting a link, adding a link, or transferring a link.

[0150] In this embodiment, deleting a link, also known as disconnecting a link, is used to configure an existing link between two devices as an unestablished link. Adding a link, also known as creating a new link, is used to configure an unestablished link between two devices as an established link. Transferring a link, also known as switching a link, is used to delete an existing link between two devices and to establish a link to be transferred.

[0151] Optionally, based on designs 1-4, the first frame is used to reconfigure the multilink between the first MLD and the second MLD, including the following scenarios:

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

[0153] Scenario 2: When the first field is used to indicate adding a link, the first frame is used to indicate establishing the target link.

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

[0155] For example, links 1 and 2 have been established between the first MLD and the second MLD based on an association process. The first field included in the first frame indicates a link transfer, specifically switching link 2 between the first MLD and the second MLD to link 3. Therefore, link 2 is deleted between the first MLD and the second MLD, and link 3 is established. Data transmission can occur between the first MLD and the second MLD on links 1 and 3, but not on link 2.

[0156] For example, such as Figure 5 As shown, 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 first field.

[0157] For example, the first field may have other names, such as the action field, without limitation.

[0158] It should be understood that, unlike Designs 1-1 to 1-3, the first frame of Design 1-4 allows for flexible reconfiguration of the link between the first MLD and the second MLD.

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

[0160] Optionally, the first frame may also include a second field, which is used to indicate the target link.

[0161] Optionally, the second field can adopt any 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, which includes at least one bit. One bit in the bitmap is used to indicate whether the link corresponding to the bit is the target link.

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

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

[0166] For example, as shown in Figure 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] For example, as shown in Figure 6(b), the first frame may include a multi-link element, which includes a second field.

[0168] For example, the second field may have other names, such as the target link set field, without limitation.

[0169] The following section introduces the specific implementation of the second field using different implementation methods.

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

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

[0172] Implementation Method 2: The second field is specifically used to indicate the target link from the second link. The second link refers to any link supported by the first MLD other than the first link. The first link is the link used to transmit the first frame.

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

[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, if 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 may also include a third field, which is used to indicate whether the first link is the target link. For example, the third field can occupy 1 bit.

[0176] For example, such as Figure 7 As shown, the first frame may include a multi-link element, and the MLD-level info in the multi-link element includes a third field.

[0177] Optionally, if 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 an unestablished link between the first MLD and the second MLD, then the first link can be defaulted as the target link.

[0179] For example, if the first frame is used to delete the target link, and the first link belongs to the link already established between the first MLD and the second MLD, then the first link can be defaulted as the target link.

[0180] For example, the first frame is used to indicate the target link, and the first link can be defaulted to the target link.

[0181] Optionally, if the first frame reuses the reassociation request frame, the frame structure of the first frame can be referred to Table 1 below.

[0182] Table 1

[0183]

[0184]

[0185] It should be understood that Table 1 only shows a portion of the information cells, and the first frame may also include other information cells, which is not limited.

[0186] Optionally, if the first frame is multiplexed from the deassociative frame, the frame structure of the first frame can be referenced as shown in Table 2 below.

[0187] Table 2

[0188] Serial Number information 1 Reason code …… …… The second to last Manufacturer-defined information elements Last one Management message complete code information element

[0189] It should be understood that Table 2 only shows a portion of the information cells, and the first frame may also include other information cells, which is not limited.

[0190] Optionally, if the first frame reuses a reassociation request frame or a deassociation frame, the first frame may include a multi-link element. Furthermore, the first frame may be distinguished from existing reassociation request frames or deassociation frames by utilizing the Type field in the Multi-link Control field of the multi-link element.

[0191] For example, the type field, with 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. The first preset value is not 0 or 1. For instance, the first preset value can be 2.

[0192] For example, the type field provided in the embodiments of this application can be referred to Table 3.

[0193] Table 3

[0194]

[0195] As can be seen, this embodiment utilizes a reserved value (e.g., 2) of the original type field to define a new Multi-link element variant name. Therefore, the device can determine that frames using this Multi-link element variant name are used for multi-link reconfiguration.

[0196] It should be understood that, compared to a new type of action frame, reusing the reassociation request frame or deassociation frame in the first frame helps avoid making excessive changes to the existing protocol. At the same time, it does not require redefining 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, Second MLD analyzes the first frame.

[0199] based on Figure 4 In the illustrated embodiment, the first MLD triggers a link reconfiguration between the first MLD and the second MLD by sending a first frame to the second MLD, thereby satisfying the communication needs between the two MLDs and ensuring normal communication between them.

[0200] Currently, the peer device involved in a reassociation process is not necessarily the same device as the peer device involved in the initial association process. For example, device 1 associates with device 2 in the initial association process and with device 3 in the reassociation process. Therefore, some information stored by the device is not applicable to communication with the peer device involved in the reassociation process. Therefore, the 802.11 protocol stipulates that the device deletes some information during the reassociation process, such as the enhanced distributed channel access (EDCA) function status, block acknowledgment protocol, sequence number (SN), packet number (PN), duplicate detection buffer, data to be transmitted in the queue, fragmentation and reassembly buffers, power management mode, and radio network management sleep mode. Afterwards, the device renegotiates with the peer device involved in the reassociation process to obtain this information.

[0201] Unlike existing reassociation procedures, when the first frame reuses the reassociation request frame, neither the first MLD nor the second MLD needs to delete the aforementioned information, thus avoiding the operational overhead of subsequently negotiating to obtain this information. That is, after the first MLD sends the first frame to the second MLD, both the first and second MLDs can continue to cache the following information: enhanced distributed channel access function status, block acknowledgment protocol, sequence number, packet sequence number, duplicate detection buffer, data to be transmitted in the queue, fragmentation and reassembly buffers, power management mode, radio network management sleep mode, etc.

[0202] Optional, based on Figure 4 The illustrated embodiments, such as Figure 8 In the embodiment shown, the multi-link reconfiguration method may further include step S104 after step S103.

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

[0204] The second frame is used in response to the first frame.

[0205] Optionally, if the first frame is multiplexed with a deassociation frame, the second frame can be an acknowledgment (ACK) frame.

[0206] Optionally, if 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 it is agreed to reconfigure the link between the first MLD and the second MLD.

[0207] Optionally, if the first frame reuses the reassociation request frame, the second frame may reuse the reassociation response frame. The second frame may be used to indicate whether agreement is reached to reconfigure the link between the first MLD and the second MLD.

[0208] For example, in the case where the second frame reuses the reassociated response frame, the frame structure of the second frame can be referred to Table 4.

[0209] Table 4

[0210]

[0211] The status code can be used to indicate the response to the reconfiguration operation requested in the first frame.

[0212] For example, the specific configuration of the status coding can be found in Table 5.

[0213] Table 5

[0214]

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

[0216] In one possible design, the second frame could include only a status code that applies to all target links.

[0217] For example, the first frame can be used to indicate the addition of link 1 and link 2, while the status code in the second frame indicates success. Thus, link 1 and link 2 are established between the first MLD and the second MLD.

[0218] For example, the first frame can be used to indicate the addition of Link 1 and Link 2, while 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] Another possible design is that each second frame can include one or more status codes. Each status code corresponds to a target link and is used to indicate the reconfiguration status of the corresponding target link.

[0220] For example, the first frame can be used to indicate the addition of link 1 and link 2. In the second frame, the status code corresponding to link 1 is used to indicate success, and the status code corresponding to link 2 is used to indicate failure. Thus, link 1 is established between the first MLD and the second MLD, but link 2 is not established.

[0221] For example, the first frame can be used to indicate the deletion of link 1 and link 2. In the second frame, the status code corresponding to link 1 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, but link 2 is not deleted.

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

[0223] Optionally, if 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 it can be MLD-level info located in the multi-link element. For example, as shown in Figure 9(b), the second frame may include a multi-link element, and the multi-link element may include the status code corresponding to the first link.

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

[0225] Optionally, when the second frame reuses the reassociation response frame, the second frame can utilize the Type field in the Multi-link Control field of the Multi-link element to distinguish it from the existing reassociation response frame. For example, the type field with 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. The first preset value is not 0 or 1. For example, 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 knows how to reconfigure the link between the first MLD and the second MLD.

[0227] Currently, STAs and their associated APs can negotiate before transferring to a BSS based on the BTM process, enabling the STA to be transferred to a better BSS. For example, such as... Figure 10 As shown, the BTM process may include the following steps:

[0228] When a STA detects poor link quality or other issues, it can send a Basic Service Set Transition Management (BSS Transition Management, BTM) query frame to its associated AP. It should be understood that sending a BTM query frame is an optional step. Upon receiving the BTM query from 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 whether it accepts or rejects the BSS transfer request. After receiving the BTM response frame, the AP can reply with an ACK frame.

[0231] For example, as shown in Figure 11(a), a BTM query frame may include the following fields: category, WNM action, dialog token, BSS transition query reason, and BSS transition candidate list. The BSS transition candidate list is optional.

[0232] The BSS transition query reason field indicates the reason for sending the BTM query frame. For example, the structure of the BSS transition query reason field in related technologies can be found in Table 6.

[0233] Table 6

[0234] Values ​​of the BSS transition query reason field describe 0 not specified 1 Excessive packet loss rate or poor link quality 2 High latency … …

[0235] The BSS transfer alternative list field carries one or more neighbor report elements.

[0236] For example, as shown in Figure 11(b), the neighbor report element includes the following elements: element ID, length, BSSID, BSSID information (info), operating class, channel number, physical layer type (PHY type), and optional subelements.

[0237] The BSSID field indicates the BSSID of the neighboring AP being reported. The BSSID information field indicates relevant information about the reported BSSID. The Operating class and channel number fields 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.

[0238] Optionally, the BSSID information fields 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, co-located with 2.4 / 5 GHz AP and a member of an extended service set, reporting AP supported with on-channel tunneling (OCT), co-located with 6 GHz AP, and reserved fields.

[0239] For example, such as Figure 12As shown, a BTM request frame may include the following fields: category, radio network management operation, session token, request mode, disassociation timer, validity interval, BSS termination duration, session info URL, and BSS transfer candidate list. The BSS transfer candidate list is optional.

[0240] The Validity Interval field indicates how many beacon periods the BSS transfer candidate list is valid for.

[0241] The Disassociation Timer field indicates how long after the AP will send the associated frame.

[0242] The Request Mode field indicates the specific request mode. The Request Mode field may include the following fields: whether a preferred candidate list is included, abridge, disassociation imminent, BSS termination included, extended service set (ESS), ESS disassociation imminent, and reserved bits. The reserved bits are 3 bits.

[0243] The Preferred Candidate List Included field indicates whether a preferred list of candidates is included.

[0244] The purpose of the Abridged 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, the Abridged field is set to 1.

[0245] The purpose of the Disassociation Imminent field: When the Disassociation Imminent field is set to 1, it means that the AP will send a Disassociation frame to associate with the STA; when the Disassociation Imminent field is set to 0, it means that the AP will not send a Disassociation frame to associate with the STA.

[0246] The BSS Termination Included field indicates whether the BSS will be turned off.

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

[0248] For example, such as Figure 13 As shown, a BTM response frame may include the following fields: category, radio network management operation, session token, BTM status code, BSS termination delay, target BSSID, and BSS transfer candidate list. The target BSSID and BSS transfer candidate list are optional. Currently, in related technologies, when the BTM status code is 0, the BTM response frame includes the target BSSID field.

[0249] The BTM status code indicates whether the BSS transfer request has been accepted. The BSS termination delay indicates the duration of the time period from the current time to the termination of the BSS.

[0250] For example, BTM status codes can be found in Table 7.

[0251] Table 7

[0252]

[0253] Referring to existing BTM procedures, before two MLDs perform link transfer, they can negotiate the link transfer to allow them to switch from the currently established link to a better link for communication. Based on this, this application provides a multi-link reconfiguration method. Figure 14 As shown, the method includes the following steps:

[0254] 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.

[0255] In one possible design, the query frame can be an existing BTM query frame. That is, the first MLD does not decide whether to conduct link transfer negotiation or BSS transfer negotiation, but the second MLD determines whether to conduct link transfer negotiation or BSS transfer negotiation based on the actual situation.

[0256] In another possible design, the first MLD can determine to initiate link transfer negotiation. Therefore, the query frame is used to negotiate the link transfer between the first MLD and the second MLD.

[0257] Based on this design, the interrogation frame can be a newly defined frame. Alternatively, the interrogation frame can reuse an existing BTM interrogation frame.

[0258] Optionally, the query 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.

[0259] 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. The Basic Multi-link element may include the MLD MAC address, the number of supported links, and capability information of the AP MLD to which the AP adjacent to the first MLD belongs.

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

[0261] Optionally, when the interrogation frame reuses an existing BTM interrogation frame, the interrogation frame may include a Multi-link element, and the interrogation frame may utilize the Type field in the Multi-link Control field of the Multi-link element to determine whether the interrogation frame is used for link transfer negotiation. For example, a type field with a second preset value is used to indicate that the interrogation frame is used to negotiate a link transfer between the first MLD and the second MLD. The second preset value is not 0 or 1. Optionally, the second preset value can be the same as the first preset value mentioned above, and this is not limited.

[0262] Optionally, when the query frame reuses an existing BTM query frame, the Transition QueryReason field in the query frame can be newly defined with one or more values ​​to indicate the reason for link transfer, such as high link frame loss rate, poor link quality, or discovery of a better link.

[0263] Optionally, the query frame may further include: a link identifier or a link bitmap for indicating links with high link frame loss rates.

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

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

[0266] The request frame is used to request a link transfer between the first MLD and the second MLD.

[0267] Optionally, the request frame can 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, without limitation.

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

[0269] Optionally, when a request frame reuses an existing BTM request frame, the request mode field in the request frame may include a fourth field, which can be used to indicate a new request mode. This new request mode may be referred to as a link transfer request mode, a link removal mode, or a link-level deassociation mode. For example, this fourth field may use reserved bits from the request mode field in the existing BTM frame. For example, this fourth field may occupy 1 bit. Figure 22 This shows the frame structure of the request mode field of the request frame. The fourth field can be... Figure 22 The link removal field in the document.

[0270] Optionally, the request frame may include a Multi-link element, and the request frame may utilize the Type field in the Multi-link Control field of the Multi-link element to determine whether the request frame is used for link transfer negotiation. For example, a type field with 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. The second preset value is not 0 or 1. Optionally, the second preset value can be the same as the first preset value mentioned above, and this is not limited.

[0271] 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 candidate list.

[0272] Optionally, the request frame may include a transfer candidate list field, which may include one or more neighbor report elements. Each neighbor report element corresponds to an AP adjacent to the second MLD.

[0273] like Figure 15 As shown, a fifth field can be added to the BSSID information field of the neighbor report element. This fifth field indicates the ID of the MLD to which the BSS corresponding to the link transmitting the request frame belongs. That is, this fifth field indicates that the device sending the request frame is an MLD. Therefore, after receiving the request frame, the first MLD can prioritize link transfer with the second MLD.

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

[0275] For example, the fifth field can have other names, such as the AP MLD ID field.

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

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

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

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

[0280] The response frame is used to indicate whether a link transfer between the first MLD and the second MLD is agreed upon.

[0281] Optionally, the response frame can be a newly defined frame. Alternatively, the response frame can reuse an existing BTM response frame.

[0282] Optionally, when the response frame reuses an existing BTM response frame, the BTM status code in the response frame may contain one or more newly defined values ​​to indicate the result of the link transfer, such as accepting the link transfer or rejecting the link transfer.

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

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

[0285] 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.

[0286] 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. The Basic Multi-link element may include the MLD MAC address, the number of supported links, and capability information of the AP MLD to which the AP adjacent to the first MLD belongs.

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

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

[0289] based on Figure 14 As shown, before link transfer, the first MLD and the second MLD can negotiate with each other to determine the link with better communication quality. Therefore, after link transfer, the first MLD and the second MLD can communicate on the link with better communication quality, ensuring normal communication between them.

[0290] Currently, MLDs can be configured with multiple sites to support data transmission over multiple links. However, in some cases, there is a need to delete sites, such as when the MLD's traffic is low. Deleting one or more sites can help reduce the MLD's power consumption. However, no corresponding solution is provided in the existing technology.

[0291] In view of this, embodiments of this application provide as follows: Figure 18 , Figure 19 as well as Figure 20 The technical solution shown is intended to achieve the goal of deleting sites in MLD.

[0292] like Figure 18 As shown in the figure, this application embodiment provides a multi-link reconfiguration method, which includes the following steps:

[0293] S301, The first MLD broadcasts the third frame on the target link.

[0294] Specifically, for the first MLD, the third frame indicates that the first MLD is ready to delete the target site, which is a site belonging to the first MLD and operating on the target link.

[0295] For example, taking a first MLD comprising AP1, AP2, and AP3, where AP1 operates on link 1, AP2 operates on link 2, and AP3 operates on link 3, when the first MLD prepares to delete AP1, it broadcasts a third frame on link 1. When the first MLD prepares to delete AP2, it broadcasts a third frame on link 2. When the first MLD prepares to delete AP3, it broadcasts a third frame on link 3.

[0296] In one possible design, the third frame can reuse an existing frame to ensure backward compatibility, meaning that legacy sites supporting previous protocols can parse the third frame. For example, the third frame can reuse a BTM request frame.

[0297] Optionally, if the third frame is a BTM request frame, the third frame is used to instruct the first MLD to prepare to delete the target site. Specifically, the BTM request frame includes a sixth field with a value of a third preset value.

[0298] The sixth field, which takes a 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, which takes a fourth preset value, can be used to indicate that the MLD receiving the BTM request frame associates with the first MLD (that is, the MLD receiving the BTM request frame disconnects all links with the first MLD).

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

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

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

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

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

[0304] Taking a traditional site (i.e., a single-link device) as an example, if the third frame can reuse the existing frame, the single-link device will prepare to perform BSS handover after receiving the third frame.

[0305] Optionally, if the third frame is a newly defined management frame, the first MLD can also send a BTM request frame on the target link to trigger BSS handover for traditional sites and MLDs that have not received the third frame.

[0306] Optionally, the first MLD may also send a fourth frame, which indicates the time when the target site was deleted.

[0307] For example, the fourth frame can reuse an existing frame. For instance, the fourth frame can reuse a beacon frame.

[0308] Optionally, when the fourth frame reuses a beacon frame, a seventh field can be added to the beacon frame. This seventh field indicates the time after which the target site will be deleted. Specifically, this seventh field indicates how many target beacon transmission times (TBTTs) the target site will be deleted after. Optionally, this seventh field can be located in the per-STA profile subelement of the corresponding target site within the basic multi-link element carried by the beacon frame. This seventh field can have other names, such as a delete timer field, and there is no limitation on this.

[0309] Optionally, the beacon frame may also include an eighth field, which indicates whether the seventh field exists. Optionally, this eighth field may be located in the Per-STAProfile subelement of the corresponding target station within the Basic Multi-link element carried by the beacon frame. This eighth field may also have other names, such as "delete timer present," and there is no limitation on this.

[0310] based on Figure 18 In the embodiment shown, the first MLD sends a third frame on the target link so that other devices know that the first MLD is preparing to delete the target site.

[0311] like Figure 19 As shown in the figure, this application embodiment provides a multi-link reconfiguration method, which includes the following steps:

[0312] S401, The first MLD broadcasts the fifth frame on the target link.

[0313] The fifth frame indicates that the first MLD deletes the target site, which is a site belonging to the first MLD and operating on the target link.

[0314] For example, taking a first MLD comprising AP1, AP2, and AP3, where AP1 operates on link 1, AP2 operates on link 2, and AP3 operates on link 3. When the first MLD is ready to delete AP1, it broadcasts a fifth frame on link 1. Alternatively, when the first MLD is ready to delete AP2, it broadcasts a fifth frame on link 2. Or, when the first MLD is ready to delete AP3, it broadcasts a fifth frame on link 3.

[0315] In one possible design, the fifth frame can reuse an existing frame to ensure backward compatibility, meaning that legacy sites supporting previous protocols can parse the fifth frame. For example, the fifth frame could be a disassociation frame.

[0316] It should be understood that, in the case where the fifth frame is a disassociation frame, in order for the receiving 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 to indicate deassociation, it is necessary to improve the disassociation frame. Optionally, when the fifth frame is a disassociation frame, the fifth frame is used to indicate that the first MLD deletes the current link, which can be specifically implemented as follows: the disassociation frame includes a field for multi-link reconfiguration. Optionally, this field for multi-link reconfiguration does not include information about the target link. This field for multi-link reconfiguration can have other names, such as Multi-link Reconfiguration Variant ML element, and is not limited thereto. Optionally, for broadcast disassociation frames, only the current link can be deleted. One implementation is that the Multi-link Reconfiguration Variant ML element may not include the Per-link Profile. For unicast disassociation frames, one or more links can be deleted. One implementation method is to use multi-link reconfiguration variables to carry the corresponding link's Per-link Profile, Link ID, or Link Bitmap in the multi-link information cell to indicate the target link.

[0317] Alternatively, the fifth frame can be used to indicate that the first MLD has deleted the current link. Specifically, the fifth frame includes a reason code field, which indicates the deletion of the current link. It should be understood that, compared to the reason code field included in the disassociation frame in related technologies, the reason code field included in the fifth frame in this embodiment has an additional value to indicate the deletion of the current link.

[0318] Optionally, when the fifth frame reuses the disassociation frame, the disassociation frame has different functions in different situations. For example, if the disassociation frame includes a field for multi-link reconfiguration, then this disassociation frame is the fifth frame provided in this embodiment, and the MLD receiving this disassociation frame will disconnect the current link with the first MLD. If the disassociation frame does not include a field for multi-link reconfiguration, then this disassociation frame is the disassociation frame defined by existing standards, and the MLD receiving this disassociation frame will associate with the first MLD.

[0319] In another possible design, the fifth frame could be a newly defined management frame, such as a link removal notify frame, instead of reusing an existing frame. This would avoid changing the functionality of the existing frame.

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

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

[0322] 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. Therefore, the second MLD and the first MLD no longer transmit data on the target link.

[0323] Taking the receiving device as a traditional site (i.e., a single-link device) as an example, when the fifth frame reuses the existing frame, the single-link device can associate with the first MLD after receiving the fifth frame.

[0324] Optionally, if the fifth frame is a newly defined management frame, the first MLD may also send an existing standard-defined Disassociation frame on the target link to deassociate legacy sites and MLDs that have not previously received the fifth frame.

[0325] based on Figure 19 In the illustrated embodiment, the first MLD sends a fifth frame on the target link to inform other devices that the first MLD has deleted the target site.

[0326] Optional, Figure 18 The illustrated embodiments can be combined with Figure 19 The illustrated embodiments are used in combination. For example... Figure 20 As shown in the figure, this application embodiment provides a multi-link reconfiguration method, which includes the following steps:

[0327] S501, the first MLD broadcasts the third frame on the target link.

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

[0329] S503, the first MLD broadcasts the fifth frame on the target link.

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

[0331] based on Figure 20In the illustrated embodiment, the first MLD can send a third frame to prepare other devices for the first MLD to delete the target site. Then, the first MLD can send a fifth frame to delete the target site.

[0332] Currently, MLDs can be configured with multiple sites to support data transmission over multiple links. However, in some cases, there is a need to add more sites, such as when the MLD's traffic is high. In such cases, one or more sites belonging to the MLD can be added to distribute the data transmission load. However, existing technologies do not provide a corresponding solution.

[0333] In view of this, embodiments of this application provide a method for reconfiguring multiple links, such as... Figure 21 As shown, the method includes the following steps:

[0334] S601, the first MLD broadcasts the sixth frame.

[0335] The sixth frame is used to instruct the first MLD to add a target site belonging to the first MLD. This target site operates on the target link.

[0336] Optionally, the sixth frame may include information about the target site. For example, the target site information may include BSS operation parameters, BSS capability information, etc.

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

[0338] As one possible implementation, the first MLD sends the sixth frame as a beacon frame on all the links it supports.

[0339] S602, The receiving device has received the sixth frame.

[0340] based on Figure 21 In the illustrated embodiment, the first MLD broadcasts the sixth frame to inform other devices that the first MLD has added a target site. This allows other devices to establish links with the first MLD's target site for data transmission.

[0341] In the embodiments of this application, the deletion of a site belonging to the MLD by the MLD can also be described as the MLD shutting down / deactivating a site belonging to the MLD, or shutting down the BSS that the site is responsible for, without limitation.

[0342] Adding a site belonging to an MLD can also be described as: an MLD enabling / activating a site belonging to an MLD, or enabling the BSS that the site is responsible for; there are no restrictions on this.

[0343] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the above functions, the communication device includes hardware structures and / or software modules corresponding to each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0344] This application embodiment can divide the device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one functional module. The integrated module can be implemented in hardware or as a software functional module. The module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. The following description uses the example of dividing each function into a separate functional module:

[0345] like Figure 16 As shown, a communication device provided in an embodiment of this application is provided. The communication device includes a processing module 101 and a communication module 102.

[0346] For example, 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 execution of the first MLD. Figure 4 Step S101. Communication module 102 is used to support the execution of the first MLD. Figure 4 Step S102 in the process, Figure 8 Step S104 in the process, Figure 14 Steps S201-S203 in the process, Figure 18 Step S301 in the process, Figure 19 Step S401 in the process, Figure 20 Steps S501 and S503 in the process, Figure 21 Step S601 in the process.

[0347] For example, 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 execution of the second MLD. Figure 4Step S103. Communication module 102 is used to support the execution of the second MLD. Figure 4 Step S102 in the process, Figure 8 Step S104 in the process, Figure 14 Steps S201-S203 in the process, Figure 18 Step S302 in the process, Figure 19 Step S402 in the process, Figure 20 Steps S502 and S504 in the process, Figure 21 Step S602 in the process.

[0348] The following describes possible product forms of the communication device. It should be understood that any product possessing the characteristics of a communication device falls within the protection scope of this application. It should also be understood that the following description is merely illustrative and does not limit the product form of the communication device in the embodiments of this application to this extent.

[0349] Figure 17 This is a structural diagram of a possible product form of the communication device described in the embodiments of this application.

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

[0351] For example, in the case where the multi-link device is the first MLD, the processor 201 is used to support the execution of the first MLD. Figure 4 Step S101. Transceiver 202 is used to support the first MLD execution. Figure 4 Step S102 in the process, Figure 8 Step S104 in the process, Figure 14 Steps S201-S203 in the process, Figure 18 Step S301 in the process, Figure 19 Step S401 in the process, Figure 20 Steps S501 and S503 in the process, Figure 21 Step S601 in the process.

[0352] For example, in the case where the multi-link device is the second MLD, the processor 201 is used to support the execution of the second MLD. Figure 4 Step S103. Transceiver 202 is used to support the execution of the second MLD. Figure 4 Step S102 in the process, Figure 8 Step S104 in the process, Figure 14 Steps S201-S203 in the process, Figure 18 Step S302 in the process, Figure 19 Step S402 in the process, Figure 20 Steps S502 and S504 in the process, Figure 21Step S602 in the process.

[0353] As another possible product form, the communication device described in this application embodiment can also be implemented by a chip. The chip includes a processing circuit 201 and transceiver pins 202. Optionally, the chip may also include a storage medium 203.

[0354] As another possible product form, the communication device described in the embodiments of this application can 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 this application.

[0355] Optionally, embodiments of this application also provide a computer-readable storage medium that stores computer instructions that, when executed on a computer, cause the computer to perform the methods described in the foregoing method embodiments.

[0356] Optionally, embodiments of this application also provide a computer program product containing computer instructions, which, when executed on a computer, cause the computer to perform the methods described in the foregoing method embodiments.

[0357] It should be understood that the computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access, or it can include one or more data storage devices such as servers or data centers that can be integrated with media. The available medium can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media, or semiconductor media (e.g., solid-state drives), etc.

[0358] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0359] It should be understood that the apparatuses and methods disclosed in the several embodiments provided in this application can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0360] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0361] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0362] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this 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 the 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 cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application.

[0363] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for reconfiguring multiple links, characterized in that, The method includes: Receive a first frame, which is a Basic Service Set Transfer Management Request (BTM) frame; the first frame is used to reconfigure the link between the first MLD and the second MLD; the first frame includes a first field. The first field takes a first preset value, which is used to indicate the deletion of the target link from the established link between the first MLD and the second MLD, where the target link is the link through which the first frame was transmitted. The value of the first field is a second preset value, which is used to indicate that the second MLD disconnects all links with the first MLD; Analyze the first frame.

2. The method according to claim 1, characterized in that, The first preset value is 1, and the second preset value is 0.

3. The method according to claim 2, characterized in that, The method further includes: Send a Basic Service Set Transfer Management (BTM) response frame to indicate whether to agree to a BSS transfer between the first MLD and the second MLD.

4. The method according to claim 3, characterized in that, The BTM response frame includes a target BSSID field, which indicates the MLD Media Access Control MAC address of the access point AP MLD selected by the second MLD to establish a connection.

5. The method according to claim 3 or 4, characterized in that, The BTM response frame includes one or more neighbor report elements, each of which includes a Basic Multi-link element, which does not include a Per-link Profile.

6. The method according to claim 1, characterized in that, The first frame includes a multi-link element, which includes a multi-link control field. The multi-link control field includes a type field, wherein the type field has a value of 2, indicating that the first frame is used to reconfigure the target link between the first MLD and the second MLD.

7. The method according to claim 6, characterized in that, The first frame also includes a second field, which is used to indicate the target link.

8. The method according to claim 6, characterized in that, The method further includes: Send a second frame to indicate whether you agree to reconfigure the link between the first MLD and the second MLD.

9. The method according to any one of claims 6-8, characterized in that, The first frame also includes a third field and a fourth field; wherein the third field is used to indicate the time when the target site was deleted; and the fourth field is used to indicate whether the third field exists.

10. The method according to any one of claims 6-8, characterized in that, The first frame is a beacon frame.

11. A multi-link device (MLD), characterized in that, Includes a communication module and a processing module; The communication module is used to receive a first frame, which is a Basic Service Set Transfer Management Request (BTM) frame. The first frame is used to reconfigure the link between the first MLD and the second MLD; the first frame includes a first field; The first field takes a first preset value, which is used to indicate the deletion of the target link from the established link between the first MLD and the second MLD, where the target link is the link through which the first frame was transmitted. The value of the first field is a second preset value, which is used to indicate that the second MLD disconnects all links with the first MLD; The processing module is used to parse the first frame.

12. The MLD according to claim 11, characterized in that, The first preset value is 1, and the second preset value is 0.

13. The MLD according to claim 12, characterized in that, The communication module is also used for: Send a Basic Service Set Transfer Management (BTM) response frame to indicate whether to agree to a BSS transfer between the first MLD and the second MLD.

14. The MLD according to claim 13, characterized in that, The BTM response frame includes a target BSSID field, which indicates the MLD Media Access Control MAC address of the access point AP MLD selected by the second MLD to establish a connection.

15. The MLD according to claim 13 or 14, characterized in that, The BTM response frame includes one or more neighbor report elements, each of which includes a Basic Multi-link element, which does not include a Per-link Profile.

16. The MLD according to claim 11, characterized in that, The first frame includes a multi-link element, which includes a multi-link control field. The multi-link control field includes a type field, wherein the type field has a value of 2, indicating that the first frame is used to reconfigure the target link between the first MLD and the second MLD.

17. The MLD according to claim 16, characterized in that, The first frame also includes a second field, which is used to indicate the target link.

18. The MLD according to claim 16, characterized in that, The communication module is also used for: Send a second frame to indicate whether you agree to reconfigure the link between the first MLD and the second MLD.

19. The MLD according to any one of claims 16-18, characterized in that, The first frame also includes a third field and a fourth field; wherein the third field is used to indicate the time when the target site was deleted; and the fourth field is used to indicate whether the third field exists.

20. The MLD according to any one of claims 16-18, characterized in that, The first frame is a beacon frame.

21. An MLD, characterized in that, It includes a processor and a transceiver, the processor being configured to perform processing operations in any one of claims 1 to 10, and the transceiver being configured to perform communication operations in any one of claims 1 to 10.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed on a computer, cause the computer to perform the method according to any one of claims 1 to 10.

23. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method according to any one of claims 1 to 10.

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

Images