METHODS FOR RECONFIGURING MULTIPATHS, COMMUNICATION EQUIPMENT, MULTIPATH DEVICES, COMPUTER-READABLE RECORDING MATERIALS, AND CHIPS

Abstract

The invention relates to a method for reconfiguring a multi-link device and equipment in the field of communications technology for reconfiguring the link between two multi-link devices (MLDs). The method consists of: the first MLD creating the first frame, which is used to reconfigure the link between the first MLD and the second MLD. The first MLD sends the first frame to the second MLD.

Description

Multi-link reconfiguration method and device

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on January 15, 2021, with application number 202110058021.9 and application name “Multi-link reconfiguration method and device”, and claims priority to the Chinese patent application filed with the State Intellectual Property Office on June 25, 2021, with application number 202110713587.0 and application name “Multi-link reconfiguration method and device”, and claims priority to the Chinese patent application filed with the State Intellectual Property Office on July 9, 2021, with application number 202110778961.5 and application name “Multi-link reconfiguration method and device”, all of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a multi-link reconfiguration method and apparatus. Background Art

[0003] 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 a key technology. A multi-link device (MLD) that supports ML communication has the ability to transmit and receive on multiple links. This allows the MLD to utilize a larger bandwidth for data transmission, significantly improving throughput. A link refers to the spatial path used by the MLD to transmit data on a single frequency band.

[0004] Currently, two MLDs can establish one or more links for communication through the association process. However, in some scenarios, the established links between the two MLDs may not meet the data transmission requirements between the two MLDs. The industry has not yet provided a solution to this problem.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a multi-link reconfiguration method and apparatus for implementing the reconfiguration of a link between two MLDs.

[0007] In a first aspect, a multi-link reconfiguration method is provided, comprising: a first MLD generating a first frame, the first frame being used to reconfigure a link between the first MLD and a second MLD; and the first MLD sending the first frame to the second MLD. Based on the above technical solution, the first MLD can trigger the link reconfiguration between the first MLD and the second MLD by sending the first frame to the second MLD, thereby meeting data transmission requirements between the first MLD and the second MLD.

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

[0009] Alternatively, the first frame may be an existing frame, such as a reassociation request frame or a disassociation frame. It should be understood that by multiplexing the reassociation request frame or the disassociation frame as the first frame, significant changes to the existing protocol are avoided without redefining the information elements that the first frame should include, and the reserved value of the category field in the action frame is conserved.

[0010] Optionally, in the case where the first frame multiplexes the reassociation request frame, after the first MLD sends the first frame to the second MLD, the first MLD and the second MLD may continue to cache the following information: enhanced distributed channel access (EDCA) functional status, block confirmation protocol, sequence number (SN), packet number (PN), duplicate detection cache, data in the queue for transmission, fragmentation and reassembly buffer, power management mode, and wireless network management sleep mode. It should be understood that, unlike the prior art in which the device needs to delete the above information during the reassociation process, in the embodiment of the present application, although the first frame multiplexes the reassociation request frame, it will not trigger the first MLD and the second MLD to delete the above information, so that the first MLD and the second MLD do not need to renegotiate to obtain the above information after changing the link configuration, which is beneficial to saving the overhead caused by the process 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 is used to instruct the first MLD and the second MLD to establish a target link. It should be understood that the first MLD and the second MLD can increase the data throughput between the first MLD and the second MLD by adding one or more links.

[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 is used to instruct to delete the target link from the links already established 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 deleting one or more links.

[0013] In one possible design, the first frame is used to reconfigure a link between a first MLD and a second MLD, including: the first frame is used to indicate a target link, and the target link 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, and the first field is used to indicate a type of reconfiguration, where the reconfiguration type includes: deleting a link, adding a link, or transferring a link. Based on this design, one type of first frame can implement multiple types of link reconfigurations.

[0015] In one possible design, the first frame may include a multi-link element (Multi-link element), the Multi-link element includes each link configuration information (Per-link Profile), 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: when the first field is used to indicate deletion of a link, the first frame is used to indicate deletion of a target link from the link already established between the first MLD and the second MLD; or, when the first field is used to indicate addition of a link, the first frame is used to indicate establishment of a target link between the first MLD and the second MLD; or, when the first field is used to indicate transfer of a link, the first frame is used to indicate switching of 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 transfer data from a link with poor quality to a link with better quality, which is beneficial to improving the service quality of data transmission between the two MLDs.

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

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

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

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

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

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

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

[0025] In one possible design, the method further includes: the first MLD receiving 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 the first MLD sending a response frame to the second MLD, the response frame being used to indicate whether the link transfer between the first MLD and the second MLD is approved. Based on this design, before the link transfer, the two MLDs negotiate the link transfer, allowing the two MLDs to determine the preferred link for transfer, thereby 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 the request frame from the second MLD, the method further includes: the first MLD sending a query frame to the second MLD, where the query frame is used to negotiate a link transfer between the first MLD and the second MLD. Based on this design, the first MLD can trigger the link transfer negotiation process between the two MLDs by sending the query frame.

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

[0029] In one possible design, the first frame is used to reconfigure a link between a first MLD and a second MLD, including: the first frame is used to instruct the first MLD to establish a target link between 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 to delete 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 a link between a first MLD and a second MLD, including: the first frame is used to indicate a target link, and the target link 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, and the first field is used to indicate the type of reconfiguration, where the type of reconfiguration includes: 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: when the first field is used to indicate deletion of a link, the first frame is used to indicate deletion of a target link from the link already established between the first MLD and the second MLD; or, when the first field is used to indicate addition of a link, the first frame is used to indicate establishment of a target link between the first MLD and the second MLD; or, when the first field is used to indicate transfer of a link, the first frame is used to indicate switching of 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, and the second field is used to indicate the target link.

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

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

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

[0038] In one possible design, the first frame is a reassociation request frame or a disassociation 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 whose value is a first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

[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 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 the link transfer between the first MLD and the second MLD is agreed.

[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 the request frame to the first MLD, the method further includes: the second MLD receiving an inquiry frame from the first MLD, where the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD.

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

[0043] In one possible design, the first frame is used to reconfigure a link between a first MLD and a second MLD, including: the first frame is used to instruct the first MLD to establish a target link between 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 to delete 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 a link between a first MLD and a second MLD, including: the first frame is used to indicate a target link, and the target link 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, and the first field is used to indicate the type of reconfiguration, where the type of reconfiguration includes: 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: when the first field is used to indicate deletion of a link, the first frame is used to indicate deletion of a target link from the link already established between the first MLD and the second MLD; or, when the first field is used to indicate addition of a link, the first frame is used to indicate establishment of a target link between the first MLD and the second MLD; or, when the first field is used to indicate transfer of a link, the first frame is used to indicate switching of 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, and the second field is used to indicate the target link.

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

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

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

[0052] In one possible design, the first frame is a reassociation request frame or a disassociation 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 whose value is a first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

[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 link transfer between the first MLD and the second MLD; and send a response frame to the second MLD, the response frame being used to indicate whether the link transfer between the first MLD and the second MLD is approved.

[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 further configured to send an inquiry frame to the second MLD, where the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD.

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

[0057] In one possible design, the first frame is used to reconfigure a link between a first MLD and a second MLD, including: the first frame is used to instruct the first MLD to establish a target link between 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 to delete 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 a link between a first MLD and a second MLD, including: the first frame is used to indicate a target link, and the target link 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, and the first field is used to indicate the type of reconfiguration, where the type of reconfiguration includes: 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: when the first field is used to indicate deletion of a link, the first frame is used to indicate deletion of a target link from the link already established between the first MLD and the second MLD; or, when the first field is used to indicate addition of a link, the first frame is used to indicate establishment of a target link between the first MLD and the second MLD; or, when the first field is used to indicate transfer of a link, the first frame is used to indicate switching of 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, and the second field is used to indicate the target link.

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

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

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

[0066] In one possible design, the first frame is a reassociation request frame or a disassociation 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 whose value is a first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

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

[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 further configured to receive an inquiry frame from the first MLD, where the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD.

[0070] In a fifth aspect, an MLD is provided, comprising a processor and a transceiver. The processor is configured to execute the processing actions in the corresponding method in the first or second aspect, and the transceiver pins are configured to execute the communication actions in the corresponding method in the first or second aspect.

[0071] In a sixth aspect, a computer-readable storage medium is provided, in which instructions are stored. When the instructions are executed on a computer, the computer executes the method involved in any one of the designs in the first or second aspect above.

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

[0073] In the eighth aspect, a chip is provided, comprising: a processing circuit and a transceiver pin, wherein the processing circuit is used to execute the processing actions in the corresponding method in the above-mentioned first aspect or second aspect, and the transceiver pin is used to execute the communication actions in the corresponding method in the above-mentioned first aspect or second aspect.

[0074] It can be understood that 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 that can be achieved can refer to the beneficial effects of the corresponding methods provided above and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] FIG1 is a schematic diagram of a communication scenario between an AP multi-link device and a STA multi-link device according to an embodiment of the present application;

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

[0077] FIG3 is a schematic diagram of a frame structure of a Multi-link element provided in an embodiment of the present application;

[0078] FIG4 is a flowchart of a multi-link reconfiguration method provided in an embodiment of the present application;

[0079] FIG5 is a schematic diagram of a frame structure of another Multi-link element provided in an embodiment of the present application;

[0080] FIG6( a ) is a schematic diagram of a frame structure of another Multi-link element provided in an embodiment of the present application;

[0081] FIG6( b ) is a schematic diagram of a frame structure of another Multi-link element provided in an embodiment of the present application;

[0082] FIG7 is a schematic diagram of a frame structure of another Multi-link element provided in an embodiment of the present application;

[0083] FIG8 is a flowchart of another multi-link reconfiguration method provided in an embodiment of the present application;

[0084] FIG9( a ) is a schematic diagram of a frame structure of another Multi-link element provided in an embodiment of the present application;

[0085] FIG9( b ) is a schematic diagram of a frame structure of another Multi-link element provided in an embodiment of the present application;

[0086] FIG10 is a schematic diagram of a BTM process in related art;

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

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

[0089] FIG12 is a schematic diagram of a frame structure of a BTM request frame in the related art;

[0090] FIG13 is a schematic diagram of a frame structure of a BTM response frame in the related art;

[0091] FIG14 is a flowchart of another multi-link reconfiguration method provided in an embodiment of the present application;

[0092] FIG15 is a schematic diagram of a frame structure of a neighbor report element provided in an embodiment of the present application;

[0093] FIG16 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0094] FIG17 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0095] FIG18 is a flowchart of a multi-link reconfiguration method provided in an embodiment of the present application;

[0096] FIG19 is a flowchart of another multi-link reconfiguration method provided in an embodiment of the present application;

[0097] FIG20 is a flowchart of another multi-link reconfiguration method provided in an embodiment of the present application;

[0098] FIG21 is a flowchart of another multi-link reconfiguration method provided in an embodiment of the present application;

[0099] Figure 22 is a schematic diagram of a frame structure of a request mode field provided in an embodiment of the present application. DETAILED DESCRIPTION

[0100] In the description of this application, unless otherwise specified, " / " means "or", for example, A / B can mean A or B. "And / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, "at least one" means one or more, and "a plurality" means two or more. Words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not limit them to be necessarily different.

[0101] In this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described in this application as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0102] The technical solutions provided in this application can be applied to various communication systems, such as those using the IEEE 802.11 standard. Exemplary IEEE 802.11 standards include, but are not limited to, 802.11be or later 802.11 standards. Scenarios in which the technical solutions provided in this application are applicable include AP-STA communication, AP-AP communication, and STA-STA communication.

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

[0104] The access point (AP) referred to in this application is a device deployed in a wireless communication network to provide wireless communication functions for its associated STAs. The access point (AP) can serve as the hub of the communication system and can be a communication device such as a base station, router, gateway, repeater, communication server, switch, or bridge. The base station can include various forms of macro base stations, micro base stations, and relay stations. For the sake of convenience, the above-mentioned devices are collectively referred to as access points (APs).

[0105] IEEE 802.11, the next generation of wireless fidelity (WiFi), supports extremely high throughput (EHT) devices by increasing peak throughput and reducing service transmission latency through multiple streams, multiple frequency bands (for example, 2.4 GHz, 5 GHz, and 6 GHz), and collaborating multiple channels within the same frequency band. These multiple frequency bands or channels are collectively referred to as multilinks.

[0106] The multi-link device includes one or more subordinate sites, which may be logical sites or physical sites. In the embodiment of the present application, "the multi-link device includes subordinate sites" can be briefly described as "the multi-link device includes sites".

[0107] The subordinate station may be an access point (AP) or a non-access point station (non-AP STA). For ease of description, in the embodiments of the present application, a multi-link device whose subordinate station is an AP may be referred to as a multi-link AP, or an AP MLD, or a multi-link AP device; and a multi-link device whose subordinate station is a STA may be referred to as a multi-link STA, or a multi-link STA device, or a STA MLD, or a non-AP MLD.

[0108] The multi-link device can implement wireless communication according to 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, but the embodiments of the present application are not limited thereto.

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

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

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

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

[0114] It should be noted that Figure 2(a) only shows that the AP multi-link device supports two frequency bands, and Figure 2(b) only uses the example of the AP multi-link device supporting three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), each frequency band corresponding to a link, and the AP multi-link device 101 being able to operate on one or more links among link 1, link 2, or link 3. On the AP side or the STA side, the link here can also be understood as a station operating on the link. In actual 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, which is not limited in this embodiment of the present application.

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

[0116] A multi-link device may support simultaneous transmission and reception (STR) of data, or it may not support it. Supporting STR means that while a multi-link device is transmitting data on one link, it can also receive data on another link. Not supporting STR 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 perform a multi-link establishment operation on one of the links to establish associations with multiple links of an AP MLD simultaneously. During the association process, the non-AP MLD and the AP MLD can exchange multi-link association request / response frames on a single link. The link used to exchange the Multi-link Association Request / Response frames is referred to as a 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 multiple links to be associated, enabling the non-AP MLD and the AP MLD to associate multiple links simultaneously.

[0118] For example, the non-AP MLD sends a Multi-link Association Request frame on link 1. This frame carries STA-side information for link 1 and STA-side information for link 2. It should be understood that link 1 can be called a transmission link, and link 2 can be called a non-transmission link. The AP MLD sends a Multi-link Association Response frame on link 1 to the non-AP MLD. This frame carries AP-side information for link 1 and AP-side information for link 2. Thus, the non-AP MLD and the AP MLD establish an association on links 1 and 2. Furthermore, the non-AP MLD and the AP MLD can transmit data on links 1 and 2.

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

[0120] The MLD-level info includes the following fields: multi-link control and one or more fields. For example, the 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 (type), current MLD MAC address (MLD MAC address present), and reserved field (reserved).

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

[0123] The data fields in a per-link profile include one or more of the following fields: a per-STA control field, one or more elements, and a non-inheritance element. The non-inheritance element is optional.

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

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

[0126] For example, when two MLDs are initially associated, only one link is established. However, there is a lot of data to be transmitted between the two MLDs, and one link cannot meet the data transmission throughput requirement. Therefore, an additional link is needed between the two MLDs.

[0127] For another example, two MLDs establish multiple links during initial association. However, the amount of data to be transmitted between the two MLDs is small, and one link can meet the data transmission throughput requirement. Therefore, redundant links between the two MLDs need to be deleted to save energy consumption.

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

[0129] Currently, the industry has not yet provided a solution for how to change the link configuration after MLD association.

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

[0131] S101: A first MLD generates a first frame.

[0132] The first frame is used to reconfigure the multilink 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 embodiment of the present application, the first frame may be a newly defined frame, or a reused existing frame (eg, a reassociation request frame or a disassociation frame), which is not limited.

[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 instruct the first MLD to establish a target link between the first MLD and the second MLD. That is, the target link belongs to a link that has not yet been established between the first MLD and the second MLD.

[0138] For example, the first MLD and the second MLD have already established Link 1 and Link 2 based on the association process. The first frame is used to instruct the establishment of Link 3, so that the first MLD and the second MLD can establish Link 3. Afterwards, the first MLD and the second MLD can use Link 1, Link 2, and Link 3 for data transmission.

[0139] In the embodiment of the present application, two MLDs can transmit data on an established link, but cannot transmit data on an unestablished link. The two MLDs can exchange some management frames (such as association request / response frames) on the unestablished link to establish the 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 to delete a target link from the link established between the first MLD and the second MLD, wherein the target link belongs to the link currently established between the first MLD and the second MLD.

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

[0143] It should be understood that, based on Designs 1-1 and 1-2, the function of the first frame can be associated with the type of the first frame. Thus, the second MLD can determine the function of the first frame based on the type of the first frame. For example, if the first frame of Design 1-1 is a reassociation request frame, the second MLD, after receiving the reassociation request frame for multilink reconfiguration, can determine that the reassociation request frame is used to establish the target link. Alternatively, if the first frame of Design 1-2 is a disassociation frame, the second MLD, after receiving the disassociation frame for multilink reconfiguration, can determine that the disassociation 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 can be transmitted 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 is a link supported between the first MLD and the second MLD. For example, the target link can be a link that has not yet been established between the first MLD and the second MLD. Alternatively, the target link can be a link that has already been established between the first MLD and the second MLD.

[0147] For example, the first MLD and the second MLD have established Link 1 and Link 2 based on the association process. The first frame is used to indicate Link 2, Link 3, and Link 4. Therefore, Link 1 is deleted and Link 3 and Link 4 are created between the first and second MLDs. In this way, Link 2, Link 3, and Link 4 can be used for data transmission between the first and second MLDs, but Link 1 cannot be used for data transmission.

[0148] It should be understood that the idea of ​​designs 1-3 is that the first frame indicates the link (i.e., the target link) that should ultimately be established between the first MLD and the second MLD, so that the first MLD and the second MLD can determine the actual reconfiguration operation to be performed (such as deleting links and / or adding links) based on the currently established links and the links that should ultimately be established.

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

[0150] In the embodiments of the present application, deleting a link, also known as disconnecting a link, is used to configure an established 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 established link between two devices and establish a link to be transferred.

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

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

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

[0154] Scenario 3: When 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.

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

[0156] Exemplarily, as shown in FIG5 , 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] Exemplarily, the first field may have other names, such as an action field, which is not limited.

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

[0159] The above designs 1-1 to 1-4 are 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 may be specified by the 802.11 protocol.

[0160] Optionally, the first frame may further include a second field, where the second field is used to indicate a 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, the bitmap includes at least one bit, and one bit in the bitmap is used to indicate whether the link corresponding to the bit is a target link.

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

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

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

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

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

[0169] The specific implementation of the second field is introduced below in combination with different implementation methods.

[0170] Implementation 1: The second field is specifically used to indicate a 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 that 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 to 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 to the links supported by the second MLD.

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

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

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

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

[0176] Exemplarily, as shown in FIG7 , 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, when the second field adopts implementation mode 2, the first frame may 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 is a link that has not been established between the first MLD and the second MLD, the first link may be set as the target link by default.

[0179] For another example, if the first frame is used to delete a target link, and the first link is a link established between the first MLD and the second MLD, the first link may be set as the target link by default.

[0180] For another example, the first frame is used to indicate the target link, and the first link may be assumed to be the target link.

[0181] Optionally, in the case where the first frame multiplexes a reassociation request frame, the frame structure of the first frame may refer to that shown in the following Table 1.

[0182] Table 1

[0183]

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

[0185] Optionally, in the case where the first frame multiplexes a de-associated frame, the frame structure of the first frame may refer to that shown in the following Table 2.

[0186] Table 2

[0187] Sequence number information 1 Reason code (reason code) ... ... ... the second to last manufacturer-defined information element The first to last management message integrity code information element

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

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

[0190] For example, the type field having 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 may be 2.

[0191] For example, the type field provided in the embodiment of the present application can be referred to as shown in Table 3.

[0192] Table 3

[0193]

[0194] As can be seen, the embodiment of the present application utilizes the reserved value of the original type field (e.g., 2) to define a new Multi-link element variant name. Thus, the device can determine that the frame using the Multi-link element variant name is used for multi-link reconfiguration.

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

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

[0197] S103: The second MLD parses the first frame.

[0198] Based on the embodiment shown in FIG4 , the first MLD triggers link reconfiguration between the first MLD and the second MLD by sending the first frame to the second MLD, thereby meeting the communication requirements between the two MLDs and ensuring normal communication between the two MLDs.

[0199] Currently, the peer device involved in a device's reassociation process isn't 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 associates with device 3 in the reassociation process. Therefore, some information stored by the device is no longer suitable for communicating with the peer device involved in the reassociation process. Therefore, the 802.11 protocol specifies that when a device performs a reassociation process, it deletes some information, such as the enhanced distributed channel access (EDCA) function status, block acknowledgement protocol, sequence number (SN), packet number (PN), duplicate detection buffer, queued data for transmission, fragmentation and reassembly buffer, power management mode, and wireless network management sleep mode. The device then renegotiates with the peer device involved in the reassociation process to obtain this information.

[0200] Unlike existing reassociation processes, when the first frame multiplexes the reassociation request frame, the first and second MLDs do not need to delete the above information, thereby 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, the first and second MLDs can continue to cache the following information: enhanced distributed channel access function status, block acknowledgement protocol, sequence number, packet sequence number, duplicate detection buffer, data in queue for transmission, fragmentation and reassembly buffer, power management mode, radio network management sleep mode, etc.

[0201] Optionally, based on the embodiment shown in FIG4 , in the embodiment shown in FIG8 , the multi-link reconfiguration method may further include step S104 after step S103 .

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

[0203] The second frame is used to respond to the first frame.

[0204] Optionally, in the case where the first frame is multiplexed with a de-association frame, the second frame may be an acknowledgment (ACK) frame.

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

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

[0207] For example, in the case where the second frame multiplexes the reassociation response frame, the frame structure of the second frame may refer to that shown in Table 4.

[0208] Table 4

[0209]

[0210] The status code may be used to indicate a response to the reconfiguration operation requested by the first frame.

[0211] For example, the specific configuration of the status code can be referred to as shown in Table 5.

[0212] Table 5

[0213]

[0214] It should be understood that “rejection without specifying a reason” means that the peer device rejects the reconfiguration operation requested by the first frame, but does not provide a reason for the rejection.

[0215] In one possible design, the second frame may include only one status code, which is for all target links.

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

[0217] For another example, the first frame may be used to indicate adding link 1 and link 2, while the status code in the second frame is used to indicate rejection. Therefore, link 1 and link 2 are not established between the first MLD and the second MLD.

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

[0219] 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 indicates success, and the status code corresponding to link 2 indicates failure. Thus, link 1 is established between the first MLD and the second MLD, but link 2 is not established.

[0220] For another 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 indicates success, and the status code corresponding to link 2 indicates failure. Therefore, link 1 is deleted between the first MLD and the second MLD, but link 2 is not deleted.

[0221] Optionally, for a target link that is not the first link, the status code corresponding to the target link may be located in the Per-link Profile corresponding to the target link. For example, as shown in FIG9(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.

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

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

[0224] Optionally, when the second frame multiplexes a 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 having a value of a first preset value indicates 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. Exemplarily, the first preset value can be 2.

[0225] Based on the embodiment shown in FIG8 , the second MLD sends a second frame to the first MLD, so that the first MLD learns how to reconfigure the link between the first MLD and the second MLD.

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

[0227] When a STA detects poor link quality or other reasons, 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 optional. After receiving a BTM query from a STA, the AP can respond with an ACK frame.

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

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

[0230] For example, as shown in FIG11( a ), the 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.

[0231] The BSS transition query reason field is used to indicate the reason for sending the BTM query frame. For example, the structure of the BSS transition query reason field in the related art can be referred to Table 6.

[0232] Table 6

[0233] BSS transition query reason field value description 0 Unspecified 1 Too high packet loss rate or poor link quality 2 Too high delay...

[0234] The BSS transfer candidate list field carries one or more neighbor report elements.

[0235] Exemplarily, as shown in FIG11( 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.

[0236] The BSSID field indicates the BSSID of the reported neighboring AP. The BSSID Information field indicates information related to the reported BSSID. The Operating Class field and Channel Number field 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.

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

[0238] For example, as shown in FIG12 , the 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 information URL, and BSS transfer candidate list. The BSS transfer candidate list is optional.

[0239] The Validity Interval field is used to indicate how many beacon periods the BSS transfer candidate list is valid for.

[0240] The Disassociation Timer field is used to indicate the time after which the AP sends a disassociation frame.

[0241] The Request Mode field indicates the specific request mode. It may include the following fields: whether the preferred candidate list is included, abridge, imminent disassociation, BSS termination included, ESS disassociation imminent, and reserved bits. The reserved bits are three bits.

[0242] The Preferred Candidate List Included field is used to indicate whether to carry a preferred candidate list.

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

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

[0245] The BSS Termination Included field is used to indicate whether the BSS will be shut down.

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

[0247] For example, as shown in Figure 13, the 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 Alternative List. The Target BSSID and BSS Transfer Alternative List are optional. Currently, in related art, when the BTM Status Code value is 0, the BTM response frame includes the Target BSSID field.

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

[0249] For example, the BTM status code may refer to Table 7.

[0250] Table 7

[0251]

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

[0253] S201 (optional): A first MLD sends a query frame to a second MLD. Correspondingly, the second MLD receives the query frame from the first MLD.

[0254] In one possible design, the inquiry frame can be an existing BTM inquiry 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 actual conditions.

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

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

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

[0258] In some embodiments, the AP adjacent to the first MLD belongs to a certain AP MLD, and 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 links supported, and capability information of the AP MLD to which the AP adjacent to the first MLD belongs.

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

[0260] Optionally, when the inquiry frame reuses an existing BTM inquiry frame, the inquiry frame can include a Multi-link element, and the inquiry frame can use the Type field in the Multi-link Control field of the Multi-link element to determine whether the inquiry frame is used for link transfer negotiation. For example, the Type field with a second preset value indicates that the inquiry 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 described above, and this is not limited to this.

[0261] Optionally, when the query frame reuses the existing BTM query frame, the Transition Query Reason 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, discovery of a better link, etc.

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

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

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

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

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

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

[0268] Optionally, when the request frame reuses an existing BTM request frame, the request mode field in the request frame may include a fourth field, which may be used to indicate a new request mode. This new request mode may be called a link transfer request mode, a link removal mode, or a link-level disassociation mode. Exemplarily, the fourth field may utilize a reserved bit of the request mode field in the existing BTM frame. Exemplarily, the fourth field may occupy one bit. For example, FIG22 illustrates the frame structure of the request mode field of the request frame. The fourth field may be the link removal field in FIG22 .

[0269] Optionally, the request frame may include a Multi-link element, and the request frame may use the Type field in the Multi-link Control field of the Multi-link element to determine that the request frame is used for link transfer negotiation. For example, the Type field having a value of the second preset value indicates 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 may be the same as the first preset value described above, and this is not limited to this.

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

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

[0272] As shown in Figure 15, 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. In other words, 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.

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

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

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

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

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

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

[0279] The response frame is used to indicate whether the link transfer between the first MLD and the second MLD is approved.

[0280] Optionally, the response frame may be a newly defined frame, or the response frame may reuse an existing BTM response frame.

[0281] Optionally, when the response frame reuses an existing BTM response frame, the BTM status code in the response frame may have 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.

[0282] Optionally, if the response frame indicates acceptance of a link transfer or link removal, for example, if the BTM status code in the response frame is non-zero, the response frame does not carry the target BSSID field or the neighbor report element. If the response frame indicates acceptance of a BSS switch, for example, if the BTM status code in the response frame is zero, the response frame may also include the target BSSID field.

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

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

[0285] In some embodiments, the AP adjacent to the first MLD belongs to a certain AP MLD, and 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 links supported, and capability information of the AP MLD to which the AP adjacent to the first MLD belongs.

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

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

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

[0289] Currently, MLD can configure multiple sites to support data transmission on multiple links. However, in some cases, MLD may need to delete sites. For example, when the MLD traffic volume is low, deleting one or more sites can help reduce MLD power consumption. However, existing technologies do not provide a corresponding solution.

[0290] In view of this, the embodiments of the present application provide technical solutions as shown in FIG. 18 , FIG. 19 and FIG. 20 to achieve the purpose of MLD site deletion.

[0291] As shown in FIG18 , an embodiment of the present application provides a multi-link reconfiguration method, which includes the following steps:

[0292] S301: A first MLD sends a third frame on a target link in a broadcast manner.

[0293] For the first MLD, the third frame is used to indicate that the first MLD is ready to delete a target site, where the target site is a site belonging to the first MLD and working on a target link.

[0294] For example, take a case where the first MLD includes AP1, AP2, and AP3. AP1 operates on link 1, AP2 operates on link 2, and AP3 operates on link 3. When the first MLD is about to delete AP1, it broadcasts a third frame on link 1. When the first MLD is about to delete AP2, it broadcasts a third frame on link 2. When the first MLD is about to delete AP3, it broadcasts a third frame on link 3.

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

[0296] Optionally, when 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, which can be specifically implemented as follows: the BTM request frame includes a sixth field whose value is a third preset value.

[0297] The sixth field, whose value is the third preset value, may be used to instruct the MLD that receives the BTM request frame to disconnect the target link with the first MLD. The sixth field, whose value is the fourth preset value, may be used to instruct the MLD that receives the BTM request frame to disassociate with the first MLD (i.e., the MLD that receives the BTM request frame disconnects all links with the first MLD).

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

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

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

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

[0302] Taking the receiving end device as the second MLD as an example, after receiving the third frame, the second MLD prepares to delete the target link between itself and the first MLD.

[0303] Taking the receiving end device as a traditional site (ie, a single-link device) as an example, when the third frame can reuse the existing frame, the single-link device prepares to perform BSS switching after receiving the third frame.

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

[0305] Optionally, the first MLD may further send a fourth frame, where the fourth frame is used to indicate the time when the target site is deleted.

[0306] Exemplarily, the fourth frame may reuse an existing frame, such as a beacon frame.

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

[0308] Optionally, the beacon frame may further include an eighth field, which is used to indicate whether the beacon frame has the seventh field. Optionally, the eighth field may be located in the Per-STA Profile subelement of the target site corresponding to the Basic Multi-link element carried by the Beacon frame. The eighth field may also have other names, such as the delete timer present field, which is not limited to this.

[0309] Based on the embodiment shown in FIG. 18 , the first MLD sends a third frame on the target link, so that other devices know that the first MLD is going to delete the target site.

[0310] As shown in FIG19 , an embodiment of the present application provides a multi-link reconfiguration method, which includes the following steps:

[0311] S401: The first MLD sends a fifth frame on a target link in a broadcast manner.

[0312] The fifth frame is used to indicate that the first MLD deletes the target site, where the target site is a site belonging to the first MLD and working on the target link.

[0313] For example, a first MLD includes AP1, AP2, and AP3. AP1 operates on link 1, AP2 operates on link 2, and AP3 operates on link 3. When the first MLD is about to delete AP1, it broadcasts a fifth frame on link 1. Alternatively, when the first MLD is about to delete AP2, it broadcasts a fifth frame on link 2. Alternatively, when the first MLD is about to delete AP3, it broadcasts a fifth frame on link 3.

[0314] In one possible design, the fifth frame can reuse existing frames to ensure backward compatibility, that is, to ensure that legacy stations supporting previous protocols can parse the fifth frame. For example, the fifth frame can be a disassociation frame.

[0315] It should be understood that, in the case where the fifth frame multiplexes the disassociation frame, in order to make the receiving device of the disassociation frame aware that the function of the disassociation frame is to indicate the deletion of the current link rather than to indicate disassociation, it is necessary to improve the disassociation frame. Optionally, in the case where the fifth frame is a disassociation frame, the fifth frame is used to 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, the field for multi-link reconfiguration does not include information about the target link. The field for multi-link reconfiguration may have other names, such as multi-link reconfiguration variable multi-link information element (ML Reconfiguration Variant ML element), which is not limited to this. Optionally, for a broadcast Disassociation frame, only the current link can be deleted. One implementation method is that the multi-link reconfiguration variable multi-link information element may not include the Per-link Profile. For a unicast Disassociation frame, one or more links may be deleted. One implementation method is to use a multi-link reconfiguration variable multi-link information element to carry the Per-link Profile or Link ID or Link Bitmap of the corresponding link to indicate the target link.

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

[0317] Optionally, when the fifth frame multiplexes a disassociation frame, the disassociation frame has different functions in different situations. For example, when the disassociation frame includes a field for multilink reconfiguration, the disassociation frame is the fifth frame provided in the embodiment of the present application, and the MLD that receives the disassociation frame will disconnect the current link with the first MLD. When the disassociation frame does not include a field for multilink reconfiguration, the disassociation frame is the disassociation frame defined by existing standards, and the MLD that receives the disassociation frame will disassociate with the first MLD.

[0318] In another possible design, the fifth frame can be a newly defined management frame, such as a link removal notify frame, instead of reusing an existing frame, so as not to change the function of the existing frame.

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

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

[0321] For example, if the receiving device is the second MLD, after receiving the fifth frame, the second MLD deletes the target link with the first MLD. Consequently, the second MLD and the first MLD do not transmit data on the target link.

[0322] Taking the receiving end device as a traditional site (ie, a single-link device) as an example, when the fifth frame multiplexes the existing frame, the single-link device may disassociate from the first MLD after receiving the fifth frame.

[0323] Optionally, in the case that the fifth frame is a newly defined management frame, the first MLD may also send a Disassociation frame defined in an existing standard on the target link to disassociate the legacy station and the MLD that has not received the fifth frame before.

[0324] Based on the embodiment shown in FIG19 , the first MLD sends a fifth frame on the target link to inform other devices that the first MLD has deleted the target site.

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

[0326] S501: A first MLD sends a third frame on a target link in a broadcast manner.

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

[0328] S503: The first MLD sends a fifth frame on the target link in a broadcast manner.

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

[0330] Based on the embodiment shown in Figure 20, the first MLD may first send the third frame to enable other devices to prepare for the first MLD to delete the target site. Thereafter, the first MLD may send the fifth frame to delete the target site.

[0331] Currently, an MLD can configure multiple sites to support data transmission on multiple links. However, in some cases, an MLD may need to add more sites. For example, when the MLD's traffic volume is high, the MLD can add one or more sites to share the data transmission burden. However, existing technologies do not provide a corresponding solution.

[0332] In view of this, an embodiment of the present application provides a multi-link reconfiguration method, as shown in FIG21 , the method includes the following steps:

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

[0334] The sixth frame is used to instruct the first MLD to add a target station affiliated with the first MLD. The target station works on the target link.

[0335] Optionally, the sixth frame may include information of the target station. Exemplarily, the information of the target station includes BSS operating parameters, BSS capability information, and the like.

[0336] 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 follows: the ML element or Reduced Neighbor Report in the beacon frame includes information about the target station.

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

[0338] S602: The receiving device receives the sixth frame.

[0339] Based on the embodiment shown in Figure 21, the first MLD sends the sixth frame in a broadcast manner to inform other devices that the first MLD has added a target site. Thus, other devices can establish a link with the target site of the first MLD for data transmission.

[0340] In the embodiment of the present application, the MLD deletes the site subordinate to the MLD, which can also be described as: the MLD shuts down / deactivates the site subordinate to the MLD, or shuts down the BSS responsible for the site, which is not limited to this.

[0341] The MLD adds a site affiliated with the MLD, which can also be described as: the MLD starts / activates the site affiliated with the MLD, or starts the BSS responsible for the site, which is not limited to this.

[0342] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. It is understandable that, in order to realize the above functions, the communication device includes a hardware structure and / or software module corresponding to each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in a hardware or computer software driven hardware manner depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0343] The embodiment of the present application can divide the functional modules of the device according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one functional module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. The division of modules in the embodiment of the present application is schematic and is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function:

[0344] As shown in FIG16 , a communication device is provided in an embodiment of the present application, and the communication device includes: a processing module 101 and a communication module 102 .

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

[0346] Exemplarily, when the communication device is a second MLD, or the communication device is applied to a second MLD, the processing module 101 is configured to support the second MLD in executing step S103 in Figure 4. The communication module 102 is configured to support the second MLD in executing step S102 in Figure 4, step S104 in Figure 8, steps S201-S203 in Figure 14, step S302 in Figure 18, step S402 in Figure 19, steps S502 and S504 in Figure 20, and step S602 in Figure 21.

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

[0348] FIG17 is a structural diagram of a possible product form of the communication device described in an embodiment of the present application.

[0349] As a possible product form, the communication apparatus described in the embodiment of the present application may be a multi-link device, which includes a processor 201 and a transceiver 202. Optionally, the multi-link device further includes a memory 203.

[0350] Exemplarily, when the multi-link device is a first MLD, the processor 201 is configured to support the first MLD in executing step S101 in Figure 4. The transceiver 202 is configured to support the first MLD in executing step S102 in Figure 4, step S104 in Figure 8, steps S201-S203 in Figure 14, step S301 in Figure 18, step S401 in Figure 19, steps S501 and S503 in Figure 20, and step S601 in Figure 21.

[0351] Exemplarily, when the multi-link device is a second MLD, the processor 201 is configured to support the second MLD in executing step S103 in Figure 4. The transceiver 202 is configured to support the second MLD in executing step S102 in Figure 4, step S104 in Figure 8, steps S201-S203 in Figure 14, step S302 in Figure 18, step S402 in Figure 19, steps S502 and S504 in Figure 20, and step S602 in Figure 21.

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

[0353] As another possible product form, the communication device described in the embodiments of the present 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 that can perform the various functions described throughout this application.

[0354] Optionally, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer executes the method in the aforementioned method embodiment.

[0355] Optionally, an embodiment of the present application further provides a computer program product comprising computer instructions, which, when executed on a computer, enables the computer to execute the method in the aforementioned method embodiment.

[0356] 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 computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium, or a semiconductor medium (e.g., a solid-state drive).

[0357] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned 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.

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

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

[0360] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0361] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application, 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, which is stored in a storage medium and includes several instructions for causing a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application.

[0362] The above is only a specific embodiment of the present application, but the scope of protection of this application is not limited to this. Any changes or substitutions within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A multi-link reconfiguration method, It is characterized in that The method comprises: A first multi-link device MLD generates a first frame, where the first frame is used to reconfigure a link between the first MLD and a second MLD; The first MLD sends the first frame to the second MLD.

2. The method according to claim 1, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to instruct the first MLD to establish a target link with the second MLD.

3. The method according to claim 1, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to instruct to delete a target link from links that have been established between the first MLD and the second MLD.

4. The method according to claim 1, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to indicate a target link, and the target link is used to transmit data between the first MLD and the second MLD.

5. The method according to claim 1, It is characterized in that The first frame includes a first field, where the first field is used to indicate a type of reconfiguration, where the type of reconfiguration includes: deleting a link, adding a link, or transferring a link.

6. The method according to claim 5, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: In the case where the first field is used to indicate link deletion, the first frame is used to indicate deletion of a target link from links already established between the first MLD and the second MLD; or, In the case where the first field is used to indicate adding a link, the first frame is used to indicate establishing the target link between the first MLD and the second MLD; or, In a case where the first field is used to indicate a link transfer, the first frame is used to indicate that a link established between the first MLD and the second MLD is switched to the target link.

7. The method according to any one of claims 2 to 6, It is characterized in that The first frame further includes a second field, and the second field is used to indicate a target link.

8. The method according to claim 7, It is characterized in that The second field includes a bitmap, the bitmap includes at least one bit, and the bit in the bitmap is used to indicate whether the link corresponding to the bit is the target link.

9. The method according to claim 7, It is characterized in that The second field includes an identification of the target link.

10. The method according to any one of claims 2 to 9, It is characterized in that The first frame further includes a third field, where the third field is used to indicate whether the first link is a target link, where the first link is a link used to transmit the first frame.

11. The method according to any one of claims 1 to 10, It is characterized in that The first frame is a reassociation request frame or a disassociation frame; the first frame includes a multi-link element Multi-link element, the Multi-link element includes a multi-link control Multi-link control field, the Multi-link control field includes a type type field, the type field having a first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

12. The method according to any one of claims 1 to 11, It is characterized in that The method further comprises: The first MLD receives a request frame from the second MLD, where the request frame is used to request link transfer between the first MLD and the second MLD; The first MLD sends a response frame to the second MLD, where the response frame is used to indicate whether to approve the link transfer between the first MLD and the second MLD.

13. The method according to claim 12, It is characterized in that The request frame is also used to indicate a recommended link.

14. The method according to claim 12 or 13, It is characterized in that Before the first MLD receives the request frame from the second MLD, the method further includes: The first MLD sends an inquiry frame to the second MLD, where the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD.

15. A multi-link reconfiguration method, It is characterized in that The method comprises: The second MLD receives a first frame from the first MLD, where the first frame is used to reconfigure a link between the first MLD and the second MLD; The second MLD parses the first frame.

16. The method according to claim 15, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to instruct the first MLD to establish a target link with the second MLD.

17. The method according to claim 15, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to instruct to delete a target link from links that have been established between the first MLD and the second MLD.

18. The method according to claim 15, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to indicate a target link, and the target link is used to transmit data between the first MLD and the second MLD.

19. The method according to claim 15, It is characterized in that The first frame includes a first field, where the first field is used to indicate a type of reconfiguration, where the type of reconfiguration includes: deleting a link, adding a link, or transferring a link.

20. The method according to claim 19, Its special feature is that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: In the case where the first field is used to indicate link deletion, the first frame is used to indicate deletion of a target link from links already established between the first MLD and the second MLD; or, In the case where the first field is used to indicate adding a link, the first frame is used to indicate establishing the target link between the first MLD and the second MLD; or, In a case where the first field is used to indicate a link transfer, the first frame is used to indicate that a link established between the first MLD and the second MLD is switched to the target link.

21. The method according to any one of claims 16 to 20, It is characterized in that The first frame further includes a second field, and the second field is used to indicate a target link.

22. The method according to claim 21, It is characterized in that The second field includes a bitmap, the bitmap includes at least one bit, and the bit in the bitmap is used to indicate whether the link corresponding to the bit is the target link.

23. The method according to claim 21, It is characterized in that The second field includes an identification of the target link.

24. The method according to any one of claims 16 to 23, It is characterized in that The first frame further includes a third field, where the third field is used to indicate whether the first link is a target link, where the first link is a link used to transmit the first frame.

25. The method according to any one of claims 15 to 24, It is characterized in that The first frame is a reassociation request frame or a disassociation frame; the first frame includes a multi-link element Multi-link element, the Multi-link element includes a multi-link control Multi-link control field, the Multi-link control field includes a type type field, the type field having a first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

26. The method according to any one of claims 15 to 25, It is characterized in that The method further comprises: The second MLD sends a request frame to the first MLD, where the request frame is used to request link transfer between the first MLD and the second MLD; The second MLD receives a response frame from the first MLD, where the response frame is used to indicate whether link transfer between the first MLD and the second MLD is approved.

27. The method according to claim 26, It is characterized in that The request frame is also used to indicate a recommended link.

28. The method according to claim 26 or 27, It is characterized in that Before the second MLD sends the request frame to the first MLD, the method further includes: The second MLD receives an inquiry frame from the first MLD, where the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD.

29. A MLD, It is characterized in that including a processing module and a communication module; The processing module is used to generate a first frame, where the first frame is used to reconfigure a link between the first MLD and the second MLD; The communication module is configured to send the first frame to the second MLD.

30. The MLD according to claim 29, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to instruct the first MLD to establish a target link with the second MLD.

31. The MLD according to claim 29, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to instruct to delete a target link from links that have been established between the first MLD and the second MLD.

32. The MLD according to claim 29, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to indicate a target link, and the target link is used to transmit data between the first MLD and the second MLD.

33. The MLD according to claim 29, It is characterized in that The first frame includes a first field, where the first field is used to indicate a type of reconfiguration, where the type of reconfiguration includes: deleting a link, adding a link, or transferring a link.

34. The MLD according to claim 33, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: In the case where the first field is used to indicate link deletion, the first frame is used to indicate deletion of a target link from links already established between the first MLD and the second MLD; or, In the case where the first field is used to indicate adding a link, the first frame is used to indicate establishing the target link between the first MLD and the second MLD; or, In a case where the first field is used to indicate a link transfer, the first frame is used to indicate that a link established between the first MLD and the second MLD is switched to the target link.

35. The MLD according to any one of claims 30 to 34, It is characterized in that The first frame further includes a second field, and the second field is used to indicate a target link.

36. The MLD according to claim 35, It is characterized in that The second field includes a bitmap, the bitmap includes at least one bit, and the bit in the bitmap is used to indicate whether the link corresponding to the bit is the target link.

37. The MLD according to claim 35, It is characterized in that The second field includes an identification of the target link.

38. The MLD according to any one of claims 30 to 37, It is characterized in that The first frame further includes a third field, where the third field is used to indicate whether the first link is a target link, where the first link is a link used to transmit the first frame.

39. The MLD according to any one of claims 29 to 38, It is characterized in that The first frame is a reassociation request frame or a disassociation frame; the first frame includes a multi-link element Multi-link element, the Multi-link element includes a multi-link control Multi-link control field, the Multi-link control field includes a type type field, the type field having a first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

40. The MLD according to any one of claims 29 to 39, It is characterized in that The communication module is further configured to receive a request frame from the second MLD, wherein the request frame is used to request link transfer between the first MLD and the second MLD; The communication module is further configured to send a response frame to the second MLD, where the response frame is used to indicate whether link transfer between the first MLD and the second MLD is approved.

41. The MLD according to claim 40, It is characterized in that The request frame is also used to indicate a recommended link.

42. The MLD according to claim 40 or 41, It is characterized in that The communication module is further configured to send an inquiry frame to the second MLD before the first MLD receives a request frame from the second MLD, wherein the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD.

43. A MLD, It is characterized in that including a communication module and a processing module; The communication module is configured to receive a first frame from the first MLD, where the first frame is used to reconfigure a link between the first MLD and a second MLD; The processing module is used to parse the first frame.

44. The MLD according to claim 43, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to instruct the first MLD to establish a target link with the second MLD.

45. The MLD according to claim 43, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to instruct to delete a target link from links that have been established between the first MLD and the second MLD.

46. ​​The MLD according to claim 43, It is characterized in that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: The first frame is used to indicate a target link, and the target link is used to transmit data between the first MLD and the second MLD.

47. The MLD according to claim 43, It is characterized in that The first frame includes a first field, where the first field is used to indicate a type of reconfiguration, where the type of reconfiguration includes: deleting a link, adding a link, or transferring a link.

48. The MLD according to claim 47, Its special feature is that The first frame is used to reconfigure a link between the first MLD and the second MLD, including: In the case where the first field is used to indicate link deletion, the first frame is used to indicate deletion of a target link from links already established between the first MLD and the second MLD; or, In the case where the first field is used to indicate adding a link, the first frame is used to indicate establishing the target link between the first MLD and the second MLD; or, In a case where the first field is used to indicate a link transfer, the first frame is used to indicate that a link established between the first MLD and the second MLD is switched to the target link.

49. The MLD according to any one of claims 34 to 48, It is characterized in that The first frame further includes a second field, and the second field is used to indicate a target link.

50. The MLD according to claim 49, It is characterized in that The second field includes a bitmap, the bitmap includes at least one bit, and the bit in the bitmap is used to indicate whether the link corresponding to the bit is the target link.

51. The MLD according to claim 49, It is characterized in that The second field includes an identification of the target link.

52. The MLD according to any one of claims 44 to 51, It is characterized in that The first frame further includes a third field, where the third field is used to indicate whether the first link is a target link, where the first link is a link used to transmit the first frame.

53. The MLD according to any one of claims 43 to 52, It is characterized in that The first frame is a reassociation request frame or a disassociation frame; the first frame includes a multi-link element Multi-link element, the Multi-link element includes a multi-link control Multi-link control field, the Multi-link control field includes a type type field, the type field having a first preset value is used to indicate that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

54. The MLD according to any one of claims 43 to 53, It is characterized in that The communication module is further used to send a request frame to the first MLD, where the request frame is used to request a link transfer between the first MLD and the second MLD; The communication module is further configured to receive a response frame from the first MLD, where the response frame is used to indicate whether link transfer between the first MLD and the second MLD is approved.

55. The MLD according to claim 54, It is characterized in that The request frame is also used to indicate a recommended link.

56. The MLD according to claim 54 or 55, It is characterized in that The communication module is further configured to receive an inquiry frame from the first MLD before sending a request frame to the first MLD, wherein the inquiry frame is used to negotiate a link transfer between the first MLD and the second MLD.

57. A MLD, It is characterized in that The method comprises a processor and a transceiver, wherein the processor is used to perform the processing operation in the method of any one of claims 1 to 28, and the transceiver is used to perform the communication operation in the method of any one of claims 1 to 28.

58. A computer readable storage medium, It is characterized in that The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 28.

59. A computer program product, It is characterized in that When the computer program product is run on a computer, the computer is caused to execute the method according to any one of claims 1 to 28.

60. A chip, It is characterized in that The chip includes a processing circuit and a transceiver pin; the processing circuit is used to perform the processing operation in any one of the methods of claims 1 to 28, and the transceiver pin is used to perform the communication operation in any one of the methods of claims 1 to 28.

Images