Multi-link reconfiguration method and apparatus

Abstract

To provide multi-link reconfiguration method and apparatus for reconfiguring a link between two multi-link devices (MLDs).SOLUTION: In a method, a first MLD generates a first frame S101. The first frame is used to reconfigure a link between the first MLD and a second MLD. The first MLD transmits the first frame to the second MLD S102. The second MLD analyzes the first frame S103.SELECTED DRAWING: Figure 4

Description

[Technical field]

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

[0002] To achieve the technical goal of extremely high throughput, the Institute of Electrical and Electronics Engineers (IEEE) 802.11be standard includes multi-link (ML) communication as one of the key technologies. A multi-link device (MLD) that supports ML communication is capable of transmitting and receiving on multiple links. In this way, the MLD can use a larger bandwidth for data transmission to significantly improve the throughput rate. A link may refer to a spatial path along which the MLD performs data transmission in a frequency band.

[0003] Currently, one or more links can be established between two MLDs for communication through an association procedure. However, in some scenarios, the links established between the two MLDs may not meet the requirements for data transmission between the two MLDs. There is no solution in the industry to solve this problem. Summary of the Invention [Means for solving the problem]

[0004] The embodiments of this application provide a multi-link reconfiguration method and apparatus for reconfiguring a link between two MLDs.

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

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

[0007] Optionally, the first frame may reuse an existing frame, for example, a reassociation request frame or a disassociation frame. It should be understood that the first frame reuses the reassociation request frame or the disassociation frame, thereby avoiding major changes to existing protocols, the information elements to be included in the first frame do not need to be redefined, and the reserved value of the category field in the action frame is saved.

[0008] Optionally, when the first frame reuses the reassociation request frame, after the first MLD sends the first frame to the second MLD, the first MLD and the second MLD may continue to buffer the following information: enhanced distributed channel access (EDCA) capability state, block acknowledgement agreement, sequence number (SN), packet number (PN), duplicate detection cache, data queued for transmission, fragment and reassembly buffer, power management mode, and wireless network management sleep mode. It should be understood that in this embodiment of the application, unlike the prior art in which the device needs to delete the aforementioned information in the reassociation procedure, although the first frame reuses the reassociation request frame, the first MLD and the second MLD are not triggered to delete the aforementioned information. Therefore, the first MLD and the second MLD do not need to re-negotiate to obtain the above-mentioned information after changing the link configuration, thereby reducing the overhead caused by the negotiation of the above-mentioned information.

[0009] In one possible design, the first frame used to reconfigure a link between the first MLD and the second MLD includes indicating that the first frame establishes a target link between the first MLD and the second MLD. It should be understood that data throughput between the first MLD and the second MLD may be increased by adding one or more links therebetween.

[0010] In one possible design, the first frame used to reconfigure the link between the first MLD and the second MLD includes indicating that the first frame is to remove the target link from the link established between the first MLD and the second MLD. It should be appreciated that corresponding energy consumption may be reduced in the first MLD and the second MLD by removing one or more links therebetween.

[0011] In one possible design, the first frame being used to reconfigure a link between the first MLD and the second MLD includes the first frame indicating a target link, the target link being used for data transmission between the first MLD and the second MLD.

[0012] In one possible design, the first frame includes a first field, the first field indicating a reconfiguration type, the reconfiguration type including a link removal, a link addition, or a link transition. Based on this design, one type of first frame can realize multiple types of link reconfigurations.

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

[0014] In one possible design, the first frame being used to reconfigure the link between the first MLD and the second MLD includes: when the first field indicates link removal, the first frame indicating removing a target link from the link established between the first MLD and the second MLD; when the first field indicates link addition, the first frame indicating establishing a target link between the first MLD and the second MLD; or when the first field indicates link transition, the first frame indicating switching the link established between the first MLD and the second MLD to the target link.

[0015] It should be appreciated that link transition can enable two MLDs to switch from a link having poor quality for data transmission to a link having better quality, which helps to improve the service quality of data transmission between the two MLDs.

[0016] In one possible design, the first frame further includes a second field, where the second field indicates a target link.

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

[0018] In one possible design, the second field includes a bitmap, the bitmap including at least one bit, where the bit in the bitmap indicates whether the link corresponding to the bit is a target link.

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

[0020] In one possible design, the first frame further includes a third field, where the third field indicates whether the first link is a target link, and the first link is a link used to convey the first frame.

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

[0022] 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, and the multi-link control field includes a type field, where the type field has a first preset value indicating that the first frame is used to reconfigure a link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

[0023] 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 transition between the first MLD and the second MLD, and the first MLD sending a response frame to the second MLD, the response frame indicating whether the link transition between the first MLD and the second MLD is accepted. Based on this design, before the link transition, the two MLDs negotiate the link transition, so that the two MLDs can determine a better link for the transition. This ensures the quality of data transmission between the two MLDs after the link transition.

[0024] In one possible design, the request frame further indicates a preferred link.

[0025] 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, the query frame being used to negotiate a link transition between the first MLD and the second MLD. Based on this design, the first MLD may send the query frame to trigger negotiation of a link transition between the two MLDs.

[0026] According to a second aspect, there is provided a multi-link reconfiguration method, including: a second MLD receiving a first frame from a first MLD, the first frame being used to reconfigure a link between the first MLD and the second MLD, and the second MLD analysing the first frame.

[0027] In one possible design, the first frame being used to reconfigure a link between the first MLD and the second MLD includes indicating that the first frame establishes a target link between the first MLD and the second MLD.

[0028] In one possible design, the first frame used to reconfigure a link between the first MLD and the second MLD includes indicating that the first frame is to remove a target link from a link established between the first MLD and the second MLD.

[0029] In one possible design, the first frame being used to reconfigure a link between the first MLD and the second MLD includes the first frame indicating a target link, the target link being used for data transmission between the first MLD and the second MLD.

[0030] In one possible design, the first frame includes a first field, where the first field indicates a reconfiguration type, where the reconfiguration type includes a link removal, a link addition, or a link transition.

[0031] In one possible design, the first frame being used to reconfigure the link between the first MLD and the second MLD includes: when the first field indicates link removal, the first frame indicating removing a target link from the link established between the first MLD and the second MLD; when the first field indicates link addition, the first frame indicating establishing a target link between the first MLD and the second MLD; or when the first field indicates link transition, the first frame indicating switching the link established between the first MLD and the second MLD to the target link.

[0032] In one possible design, the first frame further includes a second field, where the second field indicates a target link.

[0033] In one possible design, the second field includes a bitmap, the bitmap including at least one bit, where the bit in the bitmap indicates whether the link corresponding to the bit is a target link.

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

[0035] In one possible design, the first frame further includes a third field, where the third field indicates whether the first link is a target link, and the first link is a link used to convey the first frame.

[0036] 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, and the multi-link control field includes a type field, where the type field has a value of a first preset value indicating that the first frame is used to reconfigure a link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

[0037] In one possible design, the method further includes the second MLD sending a request frame to the first MLD, the request frame being used to request a link transition between the first MLD and the second MLD, and the second MLD receiving a response frame from the first MLD, the response frame indicating whether the link transition between the first MLD and the second MLD is accepted.

[0038] In one possible design, the request frame further indicates a preferred link.

[0039] In one possible design, before the second MLD sends the request frame to the first MLD, the method further includes the second MLD receiving a query frame from the first MLD, the query frame being used to negotiate a link transition between the first MLD and the second MLD.

[0040] According to a third aspect, there is provided an MLD including 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 the first MLD and a second MLD. The communication module is configured to transmit the first frame to the second MLD.

[0041] In one possible design, the first frame being used to reconfigure a link between the first MLD and the second MLD includes indicating that the first frame establishes a target link between the first MLD and the second MLD.

[0042] In one possible design, the first frame used to reconfigure a link between the first MLD and the second MLD includes indicating that the first frame is to remove a target link from a link established between the first MLD and the second MLD.

[0043] In one possible design, the first frame being used to reconfigure a link between the first MLD and the second MLD includes the first frame indicating a target link, the target link being used for data transmission between the first MLD and the second MLD.

[0044] In one possible design, the first frame includes a first field, where the first field indicates a reconfiguration type, where the reconfiguration type includes a link removal, a link addition, or a link transition.

[0045] In one possible design, the first frame being used to reconfigure the link between the first MLD and the second MLD includes: when the first field indicates link removal, the first frame indicating removing a target link from the link established between the first MLD and the second MLD; when the first field indicates link addition, the first frame indicating establishing a target link between the first MLD and the second MLD; or when the first field indicates link transition, the first frame indicating switching the link established between the first MLD and the second MLD to the target link.

[0046] In one possible design, the first frame further includes a second field, where the second field indicates a target link.

[0047] In one possible design, the second field includes a bitmap, the bitmap including at least one bit, where the bit in the bitmap indicates whether the link corresponding to the bit is a target link.

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

[0049] In one possible design, the first frame further includes a third field, where the third field indicates whether the first link is a target link, and the first link is a link used to convey the first frame.

[0050] 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, and the multi-link control field includes a type field, where the type field has a value of a first preset value indicating that the first frame is used to reconfigure a link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

[0051] In one possible design, the communications module is further configured to receive a request frame from the second MLD, the request frame being used to request a link transition between the first MLD and the second MLD, and further configured to send a response frame to the second MLD, the response frame indicating whether the link transition between the first MLD and the second MLD is accepted.

[0052] In one possible design, the request frame further indicates a preferred link.

[0053] In one possible design, the communication module is further configured to send a query frame to the second MLD, where the query frame is used to negotiate a link transition between the first MLD and the second MLD.

[0054] According to a fourth aspect, there is provided an MLD including a processing module and a communication module. 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. The processing module is configured to analyze the first frame.

[0055] In one possible design, the first frame being used to reconfigure a link between the first MLD and the second MLD includes indicating that the first frame establishes a target link between the first MLD and the second MLD.

[0056] In one possible design, the first frame used to reconfigure a link between the first MLD and the second MLD includes indicating that the first frame is to remove a target link from a link established between the first MLD and the second MLD.

[0057] In one possible design, the first frame being used to reconfigure a link between the first MLD and the second MLD includes the first frame indicating a target link, the target link being used for data transmission between the first MLD and the second MLD.

[0058] In one possible design, the first frame includes a first field, where the first field indicates a reconfiguration type, where the reconfiguration type includes a link removal, a link addition, or a link transition.

[0059] In one possible design, the first frame being used to reconfigure the link between the first MLD and the second MLD includes: when the first field indicates link removal, the first frame indicating removing a target link from the link established between the first MLD and the second MLD; when the first field indicates link addition, the first frame indicating establishing a target link between the first MLD and the second MLD; or when the first field indicates link transition, the first frame indicating switching the link established between the first MLD and the second MLD to the target link.

[0060] In one possible design, the first frame further includes a second field, where the second field indicates a target link.

[0061] In one possible design, the second field includes a bitmap, the bitmap including at least one bit, where the bit in the bitmap indicates whether the link corresponding to the bit is a target link.

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

[0063] In one possible design, the first frame further includes a third field, where the third field indicates whether the first link is a target link, and the first link is a link used to convey the first frame.

[0064] 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, and the multi-link control field includes a type field, where the type field has a value of a first preset value indicating that the first frame is used to reconfigure a link between the first MLD and the second MLD, and the first preset value is not 0 or 1.

[0065] In one possible design, the communications module is further configured to send a request frame to the first MLD, where the request frame is used to request a link transition between the first MLD and the second MLD, and is further configured to receive a response frame from the first MLD, where the response frame indicates whether the link transition between the first MLD and the second MLD is accepted.

[0066] In one possible design, the request frame further indicates a preferred link.

[0067] In one possible design, the communication module is further configured to receive a query frame from the first MLD, where the query frame is used to negotiate a link transition between the first MLD and the second MLD.

[0068] According to a fifth aspect, there is provided an MLD including a processor and a transceiver, the processor being configured to perform processing actions in a corresponding manner in the first or second aspect, and the transceiver being configured to perform communication actions in a corresponding manner in the first or second aspect.

[0069] According to a sixth aspect, a computer-readable storage medium is provided, the computer-readable storage medium storing instructions that, when executed in a computer, enable the computer to perform the method in the design of either the first or second aspect.

[0070] According to a seventh aspect, there is provided a computer program product comprising instructions, which when executed on a computer, enables the computer to perform a method in any design of the first or second aspect.

[0071] According to an eighth aspect, there is provided a chip including a processing circuit and a transceiver pin, the processing circuit configured to perform a processing action in a corresponding manner in the first or second aspect, and the transceiver pin configured to perform a communication action in a corresponding manner in the first or second aspect.

[0072] It can be understood that any MLD, chip, computer storage medium, or computer program product provided above is configured to execute the corresponding method provided above. Therefore, for the beneficial effects that can be achieved by the MLD, chip, computer storage medium, or computer program product, please refer to the beneficial effects in the corresponding method provided above. Details will not be described again here. [Brief description of the drawings]

[0073] [Figure 1] 1 is a schematic diagram of a scenario for communication between an AP multi-link device and a STA multi-link device according to one embodiment of this application; [Figure 2(a)] 1 is a schematic diagram of the structure of a communicating AP multi-link device and a STA multi-link device; [Figure 2(b)] 1 is a schematic diagram of the structure of a communicating AP multi-link device and a STA multi-link device; [Diagram 3] FIG. 2 is a schematic diagram of a frame structure of a multi-link element according to an embodiment of this application. [Figure 4] 2 is a flowchart of a multi-link reconfiguration method according to an embodiment of the present application. [Diagram 5] FIG. 2 is a schematic diagram of another frame structure of a multi-link element according to an embodiment of this application; [Figure 6(a)] FIG. 2 is a schematic diagram of another frame structure of a multi-link element according to an embodiment of this application; [Figure 6(b)] FIG. 2 is a schematic diagram of another frame structure of a multi-link element according to an embodiment of this application; [Figure 7] FIG. 2 is a schematic diagram of another frame structure of a multi-link element according to an embodiment of this application; [Figure 8] 4 is a flowchart of another multi-link reconfiguration method according to an embodiment of the present application. [Figure 9(a)] FIG. 2 is a schematic diagram of another frame structure of a multi-link element according to an embodiment of this application; [Figure 9(b)] FIG. 2 is a schematic diagram of another frame structure of a multi-link element according to an embodiment of this application; [Figure 10] FIG. 1 is a schematic diagram of a BTM procedure in the related art. [Figure 11(a)] 1 is a schematic diagram of a frame structure of a BTM query frame in the related art; [Figure 11(b)] FIG. 2 is a schematic diagram of a frame structure of a neighbor reporting element in the related art; [Figure 12] 1 is a schematic diagram of a frame structure of a BTM request frame in the related art. [Figure 13] 1 is a schematic diagram of a frame structure of a BTM response frame in the related art; [Figure 14] 4 is a flowchart of another multi-link reconfiguration method according to an embodiment of the present application. [Figure 15] FIG. 2 is a schematic diagram of a frame structure of a neighbor reporting element according to an embodiment of the present application. [Figure 16] 1 is a schematic diagram of the structure of a communication device according to an embodiment of this application; [Figure 17] 1 is a schematic diagram of the structure of a communication device according to an embodiment of this application; [Figure 18] 2 is a flowchart of a multi-link reconfiguration method according to an embodiment of the present application. [Figure 19] 4 is a flowchart of another multi-link reconfiguration method according to an embodiment of the present application. [Figure 20] 4 is a flowchart of another multi-link reconfiguration method according to an embodiment of the present application. [Figure 21] 4 is a flowchart of another multi-link reconfiguration method according to an embodiment of the present application. [Figure 22] FIG. 2 is a schematic diagram of a frame structure of a requested mode field according to an embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0074] In the description of this application, unless otherwise specified, " / " means "or". For example, A / B can represent A or B. The term "and / or" in this specification describes only the association relationship between associated objects and indicates that there are three possible relationships. For example, A and / or B can represent the following three cases: only A exists, both A and B exist, and only B exists. In addition, "at least one" means one or more, and "multiple" means two or more. Terms such as "first" and "second" do not limit the quantity and execution order, and terms such as "first" and "second" do not indicate a limiting difference.

[0075] In this application, words such as "an example" or "for example" are used to express giving an example, illustration, or explanation. Any embodiment or design manner described in this application as an "example" or "for example" should not be described as preferred or having more advantages over another embodiment or design manner. Rather, use of the words "for example" or "example" or the like is intended to present relative concepts in a concrete manner.

[0076] The technical solutions provided in this application can be applied to various communication systems, such as systems to which the IEEE 802.11 standard is applied. For example, the IEEE 802.11 standard includes, but is not limited to, the 802.11be standard or the next generation 802.11 standard. The technical solutions of this application are applicable to the following scenarios: communication between an AP and a STA, communication between APs, communication between STAs, and the like.

[0077] The STA in this application may be various user terminals, user equipment, access devices, subscriber stations, subscriber units, mobile stations, user agents, user devices, or other devices having wireless communication capabilities. User terminals include various handheld devices, in-vehicle devices, wearable devices, computing devices having wireless communication capabilities, or other processing devices connected to a wireless modem, and may include various types of user equipment (UE), mobile stations (MS), terminals, terminal devices, portable communication devices, handheld devices, portable computing devices, entertainment devices, gaming devices or systems, and global positioning system devices, or any other suitable devices configured to perform network communications over a wireless medium. For ease of description herein, the above-mentioned devices are collectively referred to as stations or STAs.

[0078] An access point AP in this application is a device that is deployed in a wireless communication network and provides wireless communication functions for STAs associated with the access point AP. The access point AP may be used as a hub of a communication system and may be a communication device such as a base station, a router, a gateway, a repeater, a communication server, a switch, or a bridge. The base station may include macro base stations, micro base stations, relay stations, and the like in various forms. Herein, for ease of description, the above-mentioned devices are collectively referred to as an access point AP.

[0079] IEEE 802.11 extremely high throughput (EHT) devices, i.e., next generation wireless fidelity (Wi-Fi) devices, support multiple streams, multiple frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz frequency bands), multiple channel cooperation in the same frequency band, and the like, to improve peak throughput and reduce service transmission delay. Multiple frequency bands or multiple channels may be collectively referred to as multiple links.

[0080] The multilink device includes one or more affiliated stations. The affiliated stations may be logical stations or physical stations. In the embodiment of this application, "the multilink device includes an affiliated station" can be simply explained as "the multilink device includes a station."

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

[0082] The multi-link device may implement wireless communication according to an 802.11 protocol. For example, the 802.11 protocol may be an 802.11ax protocol, an 802.11be protocol, or a next-generation 802.11 protocol. This is not limited in the embodiments of this application.

[0083] A multilink device may communicate with another device. In the embodiment of this application, the other device may or may not be a multilink device.

[0084] For example, Fig. 1 is a schematic diagram of a scenario of communication between an AP multilink device and a STA multilink device. As shown in Fig. 1, one AP multilink device can be associated with multiple STA multilink devices and single-link STAs. For example, an AP multilink device 100 is associated with a STA multilink device 200, a STA multilink device 300, and a STA 400. It should be understood that multiple APs in an AP multilink device operate separately on multiple links, multiple STAs in a STA multilink device operate separately on multiple links, and a STA in a STA multilink device is associated with an AP in an AP multilink device on the working link of the STA. A single-link STA is associated with an AP in an AP multilink device on the working link of the single-link STA.

[0085] 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 another device over multiple links in a wireless local area network.

[0086] 2(a) illustrates a scenario in which an AP multilink device 101 communicates with a STA multilink device 102. The AP multilink device 101 includes an associated AP 101-1 and an AP 101-2, and A Rutilink device 102 includes associated STAs 102-1 and 102-2, and AP multilink device 101 and STA multilink device 102 communicate with each other over both link 1 and link 2.

[0087] 2(b) illustrates a scenario in which the AP multilink device 101 communicates with the STA multilink device 102, the STA multilink device 103, and the STA 104. The AP multilink device 101 includes associated APs 101-1 to 101-3, the STA multilink device 102 includes associated STAs 102-1 and 102-2, and the STA multilink device 103 includes associated STAs 103-1, 103- 2 The AP multi-link device may communicate with the STA multi-link device 102 on link 1 and link 3, with the STA multi-link device 103 on link 2 and link 3, and with the STA 104 on link 1. In one example, the STA 104 operates in a 2.4 GHz frequency band, the STA multi-link device 103 includes STA 103-1 and STA 103-2, with the STA 103-1 operating in a 5 GHz frequency band and the STA 103-2 operating in a 6 GHz frequency band, and the STA multi-link device 102 includes STA 102-1 and STA 102-2, with the STA 102-1 operating in a 2.4 GHz frequency band and the STA 102-2 operating in a 6 GHz frequency band. The AP 101-1 operating in the 2.4 GHz frequency band in the AP multilink device is connected to the STA 104 and the STA 102- 1 and may exchange uplink or downlink data on link 1. AP 101-2 operating in the 5 GHz frequency band in the AP multilink device may exchange uplink or downlink data on link 2 with STA 103-1 operating in the 5 GHz frequency band in the STA multilink device 103. AP 101-3 operating in the 6 GHz frequency band in the AP multilink device 101 may exchange uplink or downlink data on link 3 with STA 102-2 operating in the 6 GHz frequency band in the STA multilink device 102, and may also exchange uplink or downlink data on link 3 with STA 103-2 in the STA multilink device.

[0088] It should be noted that FIG. 2(a) represents that the AP multilink device only supports two frequency bands, and FIG. 2(b) uses an example in which the AP multilink device only supports three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), each frequency band corresponds to one link, and the AP multilink device 101 can operate in one or more of link 1, link 2, and link 3. On the AP side or STA side, the link here can also be understood as the station operating in the link. In practical application, the AP multilink device and the STA multilink device can further support more or less frequency bands. In other words, the AP multilink device and the STA multilink device can operate in more or less links. This is not limited in the embodiment of this application.

[0089] For example, a multi-link device is a device having wireless communication capabilities. The device may be an entire device, or a chip, processing system, or the like, mounted within the entire device. The device to which the chip or processing system is mounted may be controlled by the chip or processing system to implement the methods and functions in the embodiments of this application.

[0090] A multilink device may support simultaneous transmission and reception (STR) of data, or may not support simultaneous transmission and reception of data. Supporting simultaneous transmission and reception of data means that in the process of transmitting data on one link, the multilink device can receive data on another link. Not supporting simultaneous transmission and reception of data means that in the process of transmitting data on one link, the multilink device cannot receive data on another link.

[0091] For example, the non-AP MLD may perform a multi-link establishment operation on one of the links to simultaneously establish multiple links and establish an association with the AP MLD. In the association process, the non-AP MLD and the AP MLD may exchange Multi-link Association Request / Response frames on one link. The link on which the multi-link association request / response frames are exchanged may be referred to as a transmitted link, and the other link is referred to as a non-transmitted link. It should be understood that the multi-link association request / response may carry information about multiple links to be established in order to simultaneously establish multiple links between the non-AP MLD and the AP MLD.

[0092] For example, the non-AP MLD sends a multi-link association request frame on link 1, and the multi-link association request frame carries STA-side information for link 1 and STA-side information for link 2. It should be understood that link 1 may be referred to as a transmission link, and link 2 may be referred to as a non-transmission link. The AP MLD sends a multi-link association response frame to the non-AP MLD on link 1, and the multi-link association response frame may carry AP-side information for link 1 and AP-side information for link 2. Thus, link 1 and link 2 are established between the non-AP MLD and the AP MLD. Furthermore, the non-AP MLD and the AP MLD may perform data transmission on link 1 and link 2.

[0093] A multi-link element is defined in the protocol to carry information related to non-AP MLD in an existing association request frame. For example, as shown in FIG. 3, the information carried in the multi-link element is divided into two parts, namely MLD-level info and a per-link profile. The per-link profile may also be referred to as a per-STA profile. It should be understood that the per-link profile is optional. In other words, a multi-link element may not include a per-link profile, or may include one or more per-link profiles. For example, FIG. 3 shows a multi-link element with per-link profile x and per-link profile y.

[0094] The MLD-level info includes the following fields: a Multi-link control field and one or more fields, for example, the one or more fields may include the following fields: element ID, length, extended element ID, and the like.

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

[0096] The per-link profile contains the following fields: subelement ID, length, and data.

[0097] The data fields in the 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. A non-inheritance element is an optional field.

[0098] The control field for each station includes at least one link ID. It should be understood that the non-AP MLD may obtain link information (e.g., link ID) corresponding to each link by receiving a probe response frame or a beacon frame.

[0099] In some scenarios, after two MLDs are associated, the established link may not meet the requirements for data transmission between the two MLDs.

[0100] For example, when two MLDs are first associated, only one link is established. However, there is a large amount of data to be transmitted between the two MLDs, and one link cannot meet the throughput requirements of data transmission. Therefore, a link needs to be added between the two MLDs.

[0101] In another example, when two MLDs are first associated, multiple links are established. However, the amount of data to be transmitted between the two MLDs is relatively small, and one link can meet the throughput requirements of data transmission. Therefore, in order to reduce energy consumption, the redundant links between the two MLDs need to be removed.

[0102] In another example, when two MLDs are first associated, link 1 is established, but the communication quality of link 1 is poor, so the two MLDs intend to transition from link 1 to link 2 for data transmission.

[0103] Currently, there is no industry provided solution for changing link configuration after MLD association.

[0104] An embodiment of this application provides a multi-link reconfiguration method to support link configuration change after two MLDs are associated. As shown in Figure 4, the method includes the following steps:

[0105] S101. A first MLD generates a first frame.

[0106] The first frame is used to reconfigure a number of links between the first MLD and the second MLD.

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

[0108] In the embodiment of this application, the first frame may be a newly defined frame or may reuse an existing frame (e.g., a reassociation request frame or a disassociation frame), which is not limited.

[0109] Optionally, the first frame may use any one of the following designs.

[0110] Design 1-1: The first frame indicates the establishment of a target link.

[0111] Specifically, the first frame indicates establishing a target link between the first MLD and the second MLD, i.e., the target link is a link that is not currently established between the first MLD and the second MLD.

[0112] For example, link 1 and link 2 are established between a first MLD and a second MLD through an association. A first frame indicates establishing link 3, so that link 3 may be further established between the first MLD and the second MLD. Link 1, link 2, and link 3 may then be used for data transmission between the first MLD and the second MLD.

[0113] In this embodiment of the present application, the two MLDs can perform data transmission on the established link, but cannot perform data transmission on the non-established link, and the two MLDs can exchange some management frames (such as association request / response frames) on the non-established link for link establishment.

[0114] Design 1-2: The first frame shows removing the target link.

[0115] Specifically, the first frame indicates that a target link is to be removed from an established link between the first MLD and the second MLD. The target link is a currently established link between the first MLD and the second MLD.

[0116] For example, link 1 and link 2 are established between the first MLD and the second MLD through an association. The first frame indicates to remove link 2. After the first MLD and the second MLD remove link 2, link 2 becomes an unestablished link between the first MLD and the second MLD. The first MLD and the second MLD can only use link 1 for data transmission, but cannot use link 2 for data transmission.

[0117] It should be understood that based on Design 1-1 and Design 1-2, the function of the first frame may be associated with the type of the first frame. Thus, the second MLD may determine the function of the first frame based on the type of the first frame. For example, the first frame in Design 1-1 is a reassociation request frame. After receiving the reassociation request frame used for multilink reconfiguration, the second MLD may determine that the reassociation request frame is used to establish the target link. Alternatively, the first frame in Design 1-2 is a disassociation frame. After receiving the disassociation frame used for multilink reconfiguration, the second MLD may determine that the disassociation frame is used to remove the target link.

[0118] Design 1-3: The first frame shows the target link.

[0119] In other words, the first frame indicates a target link for data transmission between the first MLD and the second MLD.

[0120] The target link may be used for data transmission between the first MLD and the second MLD. The target link is a supported link between the first MLD and the second MLD. For example, the target link may be an unestablished link between the first MLD and the second MLD. Alternatively, the target link may also be a currently established link between the first MLD and the second MLD.

[0121] For example, link 1 and link 2 are established between the first MLD and the second MLD through association. The first frame indicates link 2, link 3, and link 4, whereby link 1 is removed and link 3 and link 4 are established between the first MLD and the second MLD. In this way, the first MLD and the second MLD may use link 2, link 3, and link 4 for data transmission and cannot use link 1 for data transmission.

[0122] It should be understood that the idea of ​​Designs 1-3 is as follows: the first frame indicates a link (i.e., a target link) to be finally established between the first MLD and the second MLD, so that the first MLD and the second MLD can determine the reconfiguration operation (e.g., removing a link and / or adding a link) to be actually performed based on the currently established link and the link to be finally established.

[0123] Design 1-4: The first frame includes a first field, and the first field indicates a reconfiguration type, where the reconfiguration type includes a link removal, a link addition, or a link transition.

[0124] In the embodiment of this application, link removal may also be referred to as link disconnection and is used to configure an established link between two devices as a non-established link. Link addition may also be referred to as link creation and is used to configure an non-established link between two devices as an established link. Link transition may also be referred to as link switching and is used to remove an established link between two devices and establish a link for transition.

[0125] Optionally, based on designs 1-4, the first frame being used to reconfigure multiple links between the first MLD and the second MLD includes the following cases.

[0126] Case 1: When the first field indicates link removal, the first frame indicates to remove the target link.

[0127] Case 2: When the first field indicates link addition, the first frame indicates to establish a target link.

[0128] Case 3: When the first field indicates a link transition, the first frame indicates switching the link established between the first MLD and the second MLD to the target link.

[0129] For example, link 1 and link 2 are established between a first MLD and a second MLD through an association. A first field included in a first frame indicates a link transition, and the first field indicates switching from link 2 established between the first MLD and the second MLD to link 3. In this manner, link 2 is removed and link 3 is established between the first MLD and the second MLD. The first MLD and the second MLD may exchange data over link 1 and link 3, but not over link 2.

[0130] For example, as shown in FIG. 5, the first frame may include a multi-link element, which includes a per-link profile, and the per-link profile includes a first field.

[0131] For example, the first field may have another name, such as an action field, which is not limited here.

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

[0133] The above-mentioned designs 1-1 to 1-4 are merely examples, and the specific implementation of the first frame is not limited. It should be understood that the design actually used for the first frame may be specified in the 802.11 protocol.

[0134] Optionally, the first frame may further include a second field, where the second field indicates a target link.

[0135] Optionally, the second field may use any one of the following designs.

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

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

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

[0139] In another example, if the value of a bit in the bitmap is 0, it indicates that the link corresponding to that bit is a target link, or if the value of a bit in the bitmap is 1, it indicates that the link corresponding to that bit is not a target link.

[0140] For example, as shown in FIG. 6(a), the first frame may include a multi-link element, which includes a per-link profile, and the per-link profile includes a second field.

[0141] For example, as shown in FIG. 6(b), the first frame may include a multi-link element, which includes a second field.

[0142] For example, the second field may have another name, such as a target link set field, which is not limited here.

[0143] The following describes the specific implementation of the second field with reference to different implementations.

[0144] Implementation 1: The second field specifically indicates a target link among all links supported by the first MLD or all links supported by the second MLD.

[0145] Optionally, based on implementation 1, if the second field includes a bitmap, the number of bits in the bitmap may be the same as the number of links supported by the first MLD, such that the bits in the bitmap are in one-to-one correspondence with the links supported by the first MLD. Alternatively, the number of bits in the bitmap may be the same as the number of links supported by the second MLD, such that the bits in the bitmap are in one-to-one correspondence with the links supported by the second MLD.

[0146] Implementation 2: The second field specifically indicates a target link among one or more second links. The second links are other links among the links supported by the first MLD, except for the first link. The first link is a link used to transmit the first frame.

[0147] Optionally, based on implementation 2, if 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 have a one-to-one correspondence with the second links.

[0148] It should be understood that based on Implementation 2, the second field does not indicate whether the first link is a target link.

[0149] Optionally, when the second field uses implementation 2, the first frame may explicitly indicate whether the first link is a target link. For example, the first frame may further include a third field, and the third field indicates whether the first link is a target link. For example, the third field may occupy one bit.

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

[0151] Optionally, when the second field uses implementation 2, the first frame may implicitly indicate whether the first link is a target link.

[0152] For example, if a first frame is used to add a target link and the first link is an unestablished link between a first MLD and a second MLD, the first link may be considered as the target link by default.

[0153] As another example, if a first frame is used to remove a target link and the first link is an established link between a first MLD and a second MLD, the first link may be considered as the target link by default.

[0154] In another example, the first frame may indicate a target link, and the first link may be considered as the target link by default.

[0155] Optionally, when the first frame reuses a reassociation request frame, see Table 1 for the frame structure of the first frame.

[0156] [Table 1]

[0157] It should be understood that Table 1 only shows some information elements, and the first frame may further include other information elements, which is not limited.

[0158] Optionally, when the first frame reuses a disassociation frame, see Table 2 for the frame structure of the first frame.

[0159] [Table 2]

[0160] It should be understood that Table 2 only shows some information elements, and the first frame may further include other information elements, which is not limited.

[0161] Optionally, when the first frame reuses a reassociation request frame or a disassociation frame, the first frame may include a multi-link element. In addition, the first frame may be distinguished from an existing reassociation request frame or a disassociation frame by using a type field in a multi-link control field in the multi-link element.

[0162] For example, a type field whose value is a first preset value indicates that the first frame is used to reconfigure a link between a first MLD and a second MLD. The first preset value is neither 0 nor 1. For example, the first preset value may be 2.

[0163] For example, see Table 3 for the type field provided in an embodiment of this application.

[0164] [Table 3]

[0165] In an embodiment of this application, it may be known that a new multi-link element variant name is defined by using a reserved value (e.g., 2) of an existing type field. Thus, a device may determine that a frame using the multi-link element variant name is used for multi-link reconfiguration.

[0166] It should be understood that compared to the first frame being a new type of action frame, the first frame reuses a reassociation request frame or a disassociation frame, which helps to avoid excessive changes to existing protocols. In addition, the information to be carried in the first frame does not need to be redefined, which further saves the reserved value of the category field in the action frame.

[0167] S102: The first MLD sends a first frame to the second MLD, and in response, the second MLD receives the first frame from the first MLD.

[0168] S103: The second MLD analyzes the first frame.

[0169] Based on the embodiment shown in FIG. 4 , the first MLD sends a first frame to the second MLD to trigger a link reconfiguration between the first MLD and the second MLD, so as to meet the requirements for communication between the two MLDs and ensure normal communication between the two MLDs.

[0170] Currently, the peer device involved in the reassociation of a device and the peer device involved in the initial association of a device may not be the same device. For example, device 1 is associated with device 2 in the initial association and associated with device 3 in the reassociation. Therefore, some information stored in the device is not applicable to communication with the peer device involved in the reassociation. Therefore, according to the 802.11 protocol, during the reassociation, the device deletes some information, such as enhanced distributed channel access (EDCA) function status, block acknowledgement protocol, sequence number (SN), packet number (PN), duplicate detection cache, data queued for transmission, fragment and reassembly buffer, power management mode, and wireless network management sleep mode. Then, the device renegotiates with the peer device involved in the reassociation to obtain the information.

[0171] Unlike the existing reassociation procedure, when the first frame reuses the reassociation request frame, the first MLD and the second MLD may not delete the aforementioned information, so as to avoid the operation overhead caused by subsequent negotiation to obtain the information. In other words, after the first MLD transmits the first frame to the second MLD, the first MLD and the second MLD may continue to buffer the following information: enhanced distributed channel access function status, block acknowledgement protocol, sequence number, packet number, duplicate detection cache, data queued for transmission, fragment and reassembly buffer, power management mode, wireless network management sleep mode, and the like.

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

[0173] S104: The second MLD transmits a second frame to the first MLD. In response, the first MLD receives the second frame from the second MLD.

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

[0175] Optionally, when the first frame reuses a disassociation frame, the second frame may be an acknowledgement (ACK) frame.

[0176] Optionally, when the first frame is a newly defined frame, the second frame may also be a newly defined frame. The second frame may indicate whether to accept a reconfiguration of a link between the first MLD and the second MLD.

[0177] Optionally, when the first frame reuses the reassociation request frame, the second frame may reuse the reassociation response frame. The second frame may indicate whether to accept a reconfiguration of the link between the first MLD and the second MLD.

[0178] For example, when the second frame reuses the reassociation response frame, see Table 4 for the frame structure of the second frame.

[0179] [Table 4]

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

[0181] For example, see Table 5 for specific configurations of status codes.

[0182] [Table 5]

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

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

[0185] For example, a first frame may indicate adding link 1 and link 2, and the status code in the second frame indicates success, in which case link 1 and link 2 are established between the first MLD and the second MLD.

[0186] In another example, a first frame may indicate adding link 1 and link 2, and the status code in the second frame indicates rejection, in which case link 1 and link 2 are not established between the first MLD and the second MLD.

[0187] In another possible design, the second frame may include one or more status codes, one corresponding to one target link, and the status code indicating a reconfiguration status of the corresponding target link.

[0188] For example, a first frame may indicate adding link 1 and link 2, and a status code corresponding to link 1 in a second frame indicates success and a status code corresponding to link 2 in the second frame indicates failure, in which case link 1 is established but link 2 is not established between the first MLD and the second MLD.

[0189] In another example, a first frame may indicate removing link 1 and link 2, with a status code corresponding to link 1 in a second frame indicating success and a status code corresponding to link 2 in the second frame indicating failure, in which case link 1 is removed but link 2 is not removed between the first MLD and the second MLD.

[0190] Optionally, for a target link that is not the first link, the status code corresponding to the target link may be placed in a per-link profile corresponding to the target link. For example, as shown in FIG. 9(a), the second frame may include a multi-link element including a per-link profile, where the per-link profile may include a per STA control field, and the per STA control field may include a status code.

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

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

[0193] Optionally, when the second frame reuses a reassociation response frame, the second frame may be distinguished from an existing reassociation response frame by using a type field in a multi-link control field in the multi-link element. For example, a type field whose value is a first preset value indicates that the first frame is used to reconfigure a link between the first MLD and the second MLD. The first preset value is neither 0 nor 1. For example, the first preset value may be 2.

[0194] According to the embodiment depicted in FIG. 8, the second MLD transmits a second frame to the first MLD to enable the first MLD to know how to reconfigure the link between the first MLD and the second MLD.

[0195] Currently, a STA and its affiliated AP may perform negotiation before a BSS transition based on the BTM procedure, so that the STA may transition to a better BSS. For example, as shown in FIG. 10, the BTM procedure may include the following steps:

[0196] When a STA finds that the link quality is poor, or for other reasons, the STA may send a basic service set transition management (BSS transition management, BTM) query frame to its affiliated AP. It should be understood that the step of sending a BTM query frame is optional. After receiving the BTM query sent by the STA, the AP may respond with an ACK frame.

[0197] When an AP wants a STA to perform a BSS transition, the AP may send a BTM request frame to the STA. After receiving the BTM request frame, the STA may respond with an ACK frame.

[0198] The STA may send a BTM response frame to the AP to indicate whether to accept or reject the BSS transition request. After receiving the BTM response frame, the AP may respond with an ACK frame.

[0199] For example, as shown in Figure 11(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.

[0200] The BSS transition query reason field indicates the reason for sending the BTM query frame. For example, see Table 6 for the structure of the BSS transition query reason field in the related art.

[0201] [Table 6]

[0202] The BSS transition candidate list field carries one or more neighbor report elements.

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

[0204] The BSSID field indicates the reported BSSID corresponding to the neighboring AP. The BSSID information field indicates relevant information about the reported BSSID. The operating class and channel number fields indicate the channel to which the reported BSSID belongs. The PHY type field indicates the physical layer type of the AP corresponding to the reported BSSID.

[0205] 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, and unsolicited probe response active, member of extended service set with 2.4 / 5 GHz co-located AP, on-channel tunneling (OCT) supported with reporting AP, co-located with 6GHz AP, and reservation.

[0206] For example, as depicted in Figure 12, the BTM request frame may include the following fields: category, radio network management action, dialogue token, request mode, disassociation timer, validity interval, BSS termination duration, session info URL, BSS transition candidate list. The BSS transition candidate list is optional.

[0207] The validity interval field indicates the number of beacon intervals for which the BSS transition candidate list is valid.

[0208] The disassociation timer field indicates the time after which the AP sends a disassociation frame.

[0209] The requested mode field indicates a specific requested mode. The requested mode field may include the following fields: preferred candidate list included, abridged, disassociation imminent, BSS termination included, extended service set (ESS) disassociation imminent, and reserved bits. Three bits are reserved.

[0210] The preferred candidate list included field indicates whether a preferred candidate list is carried.

[0211] The abridged field is used as follows: The abridged field is set to 0 if the affiliated AP discourages or prohibits the STA from switching to a BSS that does not appear in its preferred candidate list. The abridged field is set to 1 if the associated AP sets the preference value of a BSS that does not appear in its preferred candidate list to 0.

[0212] The disassociation imminent field is used as follows: when the disassociation imminent field is set to 1, it indicates that the AP will send a disassociation frame to disassociate from the STA, and when the disassociation imminent field is set to 0, it indicates that the AP will not send a disassociation frame to disassociate from the STA.

[0213] The BSS termination included field indicates whether the BSS is to be terminated.

[0214] The ESS disassociation imminent field indicates whether the STA is disassociated from the entire ESS.

[0215] For example, as shown in Figure 13, the BTM response frame may include the following fields: category, radio network management action, dialog token, BTM status code, BSS termination delay, target BSSID, and BSS transition candidate list. The target BSSID and BSS transition candidate list are optional. Currently, in the related art, when the value of the BTM status code is 0, the BTM response frame includes the target BSSID field.

[0216] The BTM status code indicates whether the BSS transition request was accepted. The BSS Exit Delay indicates the duration of the time period from the current time to the BSS Exit Time.

[0217] For example, see Table 7 for details on BTM status codes.

[0218] [Table 7]

[0219] According to the current BTM procedure, before a link transition is performed between two MLDs, the two MLDs may also perform link transition negotiation, so that the two MLDs can transition from a currently established link to a better link for communication. In view of this, one embodiment of this application provides a multi-link reconfiguration method. As shown in Figure 14, the method includes the following steps:

[0220] S201 (optional): A first MLD transmits a query frame to a second MLD, and in response, the second MLD receives a query frame from the first MLD.

[0221] In one possible design, the query frame may be an existing BTM query frame, i.e., the first MLD does not determine whether to perform link transition negotiation or BSS transition negotiation, instead, the second MLD determines whether to perform link transition negotiation or BSS transition negotiation according to the actual situation.

[0222] In another possible design, the first MLD may decide to perform link transition negotiation, and thus the query frame is used to negotiate a link transition between the first MLD and the second MLD.

[0223] Based on this design, the query frame may be a newly defined frame. Alternatively, the query frame may reuse an existing BTM query frame.

[0224] Optionally, the query frame may include one or more neighbor report elements, where each neighbor report element corresponds to one AP in the vicinity of the first MLD.

[0225] In some embodiments, when an AP near the first MLD is affiliated with an AP MLD, the neighbor report element may include a basic multi-link element, which may include the MAC address, number of supported links, capability information, and the like, of the AP MLD with which the AP near the first MLD is affiliated.

[0226] Optionally, the basic multi-link element in the neighbor report element may not include a per-link profile to reduce signaling overhead.

[0227] Optionally, when the query frame reuses an existing BTM query frame, the query frame may include a multi-link element, and the query frame may determine that the query frame is used for link transition negotiation based on a type field in a multi-link control field in the multi-link element. For example, a type field whose value is a second preset value indicates that the query frame is used to negotiate link transition between the first MLD and the second MLD. The second preset value is neither 0 nor 1. Optionally, the second preset value may be the same as the aforementioned first preset value. This is not limited.

[0228] Optionally, when the query frame reuses an existing BTM query frame, one or more values ​​may be newly defined for the transition query reason field in the query frame to indicate the reason for the link transition, e.g., high link frame loss rate, poor link quality, or a better link has been discovered.

[0229] Optionally, the query frame may further include a link identifier or a link bitmap indicating links that have a high link frame loss rate.

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

[0231] S202: The second MLD sends a request frame to the first MLD. In response, the first MLD receives a request frame from the second MLD.

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

[0233] Optionally, the request frame may be used to indicate a recommended link, which may also be referred to as a proposed link, a candidate link, or another name, without being limited thereto.

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

[0235] Optionally, when the request frame reuses an existing BTM request frame, the request mode field in the request frame may include a fourth field, and the fourth field may indicate a new request mode. The new request mode may be referred to as a link transition request mode, a link removal mode, or a link-level disassociation mode. For example, the fourth field may use a reserved bit of the request mode field in the existing BTM frame. For example, the fourth field may occupy one bit. For example, FIG. 22 represents a frame structure of the request mode field of the request frame. The fourth field may be the link removal field in FIG. 22.

[0236] Optionally, the request frame may include a multi-link element, and the request frame may determine that the request frame is used for link transition negotiation based on a type field in a multi-link control field in the multi-link element. For example, a type field whose value is a second preset value indicates that the request frame is used to negotiate link transition between the first MLD and the second MLD. The second preset value is neither 0 nor 1. Optionally, the second preset value may be the same as the above-mentioned first preset value. This is not limited.

[0237] Optionally, if the request frame is used to negotiate link removal, the value of the preferred candidate list included field in the request frame should be set to 0 to indicate that the request frame does not carry a preferred BSS transition candidate list.

[0238] Optionally, the request frame may include a transition candidate list field, and the transition candidate list field may include one or more neighbor report elements, each of which corresponds to one AP in the vicinity of the second MLD.

[0239] As shown in Figure 15, a fifth field may be added to the BSSID information field of the neighbor report element. The fifth field indicates the ID of the MLD to which the BSS corresponding to the link for the request frame transmission belongs. In other words, the fifth field indicates that the device sending the request frame is an MLD. Therefore, after receiving the request frame, the first MLD may preferentially consider performing link transition with the second MLD.

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

[0241] For example, the fifth field may have a different name, such as an AP MLD ID field.

[0242] In some embodiments, when an AP in the vicinity of the second MLD is affiliated with an AP MLD, the neighbor report element may include a basic multi-link element, which may include the MLD MAC address, number of supported links, capability information, and the like, of the AP MLD with which the AP in the vicinity of the second MLD is affiliated.

[0243] Optionally, the basic multi-link element in the neighbor report element may not include a per-link profile to reduce signaling overhead.

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

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

[0246] The response frame indicates whether to accept the link transition between the first MLD and the second MLD.

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

[0248] 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 link transition result, e.g., the link transition was accepted or the link transition was rejected.

[0249] Optionally, if the response frame indicates link transition acceptance or link removal, e.g., the value of the BTM status code in the response frame is not 0, the response frame does not carry a target BSSID field or a neighbor report element. If the response frame indicates BSS transition acceptance, e.g., the value of the BTM status code in the response frame is 0, the response frame may further include a target BSSID field.

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

[0251] Optionally, the response frame may include one or more neighbor report elements, where each neighbor report element corresponds to one AP in the vicinity of the first MLD.

[0252] In some embodiments, when an AP near the first MLD is affiliated with an AP MLD, the neighbor report element may include a basic multi-link element, which may include the MLD MAC address, number of supported links, capability information, and the like, of the AP MLD with which the AP near the first MLD is affiliated.

[0253] Optionally, the basic multi-link element in the neighbor report element may not include a per-link profile to reduce signaling overhead.

[0254] Optionally, after receiving the response frame, the second MLD sends an ACK frame to the first MLD. 1The MLD may be transmitted to the

[0255] As shown in Figure 14, before a link transition is performed, the first MLD and the second MLD may negotiate to determine a link having better communication quality. Thus, after a link transition is performed between the first MLD and the second MLD, communication can be performed on a link having better communication quality, thereby ensuring proper communication between the first MLD and the second MLD.

[0256] Currently, multiple stations can be configured so that the MLD supports data transmission on multiple links. However, in some cases, there is a station removal requirement for the MLD. For example, when the traffic volume of the MLD is relatively low, the MLD removes one or more stations, which helps to reduce the power consumption of the MLD. However, the prior art does not provide a corresponding solution.

[0257] In view of this, the embodiments of this application provide technical solutions, shown in Figures 18, 19 and 20, for MLD to remove stations.

[0258] As shown in Figure 18, an embodiment of this application provides a multi-link reconfiguration method. The method includes the following steps:

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

[0260] For the first MLD, the third frame indicates that the first MLD should remove the target station, which is a station associated with the first MLD and operating in the target link.

[0261] For example, 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 should remove AP1, the first MLD transmits a third frame on link 1 in a broadcast manner. When the first MLD should remove AP2, the first MLD transmits a third frame on link 2 in a broadcast manner. When the first MLD should remove AP3, the first MLD transmits a third frame on link 3 in a broadcast manner.

[0262] In one possible design, the third frame may reuse an existing frame to ensure backward compatibility, i.e., to ensure that legacy stations supporting earlier versions of the protocol can parse the third frame. For example, the third frame may reuse a BTM request frame.

[0263] Optionally, if the third frame is a BTM request frame, the third frame indicates that the first MLD should remove the target station. A specific implementation may be as follows: The BTM request frame includes a sixth field, the value of which is a third preset value.

[0264] The sixth field, whose value is a third preset value, may indicate that the MLD receiving the BTM request frame disconnects the target link from the first MLD. The sixth field, whose value is a fourth preset value, may indicate that the MLD receiving the BTM request frame disassociates from the first MLD (i.e., the MLD receiving the BTM request frame disconnects all links from the first MLD).

[0265] Optionally, the sixth field may occupy one or more reserved bits in an existing BTM request frame format. For example, 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.

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

[0267] S302: The receiving end device receives a third frame on the target link.

[0268] After receiving the third frame, the receiving end device may analyze the third frame and further perform a corresponding operation according to the third frame.

[0269] For example, the receiving end device is the second MLD. After receiving the third frame, the second MLD should remove the target link to the first MLD.

[0270] For example, the receiving end device is a conventional station (i.e., a single-link device). When the third frame can reuse an existing frame, the single-link device prepares to perform a BSS transition after receiving the third frame.

[0271] Optionally, if the third frame is a newly defined management frame, the first MLD may further send a BTM request frame on the target link to trigger conventional stations and MLDs that do not receive the third frame to perform a BSS transition.

[0272] Optionally, the first MLD may further transmit a fourth frame, where the fourth frame indicates a time when the target station should be removed.

[0273] For example, the fourth frame may reuse an existing frame, e.g., the fourth frame may reuse a beacon frame.

[0274] Optionally, if the fourth frame reuses a beacon frame, a seventh field may be added to the beacon frame, and the seventh field indicates the time when the target station should be removed. Specifically, the seventh field indicates the amount of target beacon transmission times (TBTTs) after which the target station should be removed. Optionally, the seventh field may be placed in the per-STA profile subelement of the target station corresponding to the basic multi-link element carried in the beacon frame. The seventh field may have another name, for example, a delete timer field. This is not limited.

[0275] Optionally, the beacon frame may further include an eighth field, which indicates whether the beacon frame includes the seventh field. Optionally, the eighth field may be located in a per-STA profile subelement of the target station corresponding to a basic multi-link element carried in the beacon frame. The eighth field may further have another name, for example, a delete timer present field. This is not limited.

[0276] According to the embodiment depicted in FIG. 18, the first MLD transmits a third frame on the target link to allow other devices to know that the first MLD should remove the target station.

[0277] As shown in Figure 19, an embodiment of this application provides a multi-link reconfiguration method. The method includes the following steps:

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

[0279] The fifth frame indicates that the first MLD should remove the target station, which is a station associated with the first MLD and operating in the target link.

[0280] For example, 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 should remove AP1, the first MLD transmits a fifth frame on link 1 in a broadcast manner. Alternatively, when the first MLD should remove AP2, the first MLD transmits a fifth frame on link 2 in a broadcast manner. Alternatively, when the first MLD should remove AP3, the first MLD transmits a fifth frame on link 3 in a broadcast manner.

[0281] In one possible design, the fifth frame may reuse an existing frame to ensure backward compatibility, i.e., to ensure that legacy stations supporting earlier versions of the protocol can parse the fifth frame. For example, the fifth frame may be a disassociation frame.

[0282] It should be understood that if the fifth frame reuses the disassociation frame, the disassociation frame needs to be improved to allow the receiving end device of the disassociation frame to know that the function of the disassociation frame indicates to remove the current link but does not indicate disassociation. Optionally, if the fifth frame is a disassociation frame, the fifth frame indicating that the first MLD should remove the current link may be specifically realized as follows: The disassociation frame includes a field used for multilink reconfiguration. Optionally, the field used for multilink reconfiguration does not include information about the target link. The field used for multilink reconfiguration may have another name, for example, a multilink reconfiguration variant multilink element (ML reconfiguration variant ML element). This is not limited. Optionally, for a broadcast disassociation frame, only the current link may be removed. In one implementation, the multilink reconfiguration variant multilink element may not include a per-link profile. For a unicast disassociation frame, one or more links may be removed. In one implementation, the multilink reconfiguration variant multilink element carries a per-link profile, a link ID, or a link bitmap of the corresponding link to indicate the target link.

[0283] Alternatively, the fifth frame indicating that the first MLD should remove the current link can be specifically realized as follows: the fifth frame includes a reason code field, and the reason code field indicates to remove the current link. It should be understood that, compared with the reason code field included in the disassociation frame in the related technology, in this embodiment of this application, a new value is added for the reason code field included in the fifth frame to indicate the removal of the current link.

[0284] Optionally, when the fifth frame reuses the disassociation frame, the disassociation frame has different functions in different cases. For example, when the disassociation frame includes a field used for multi-link reconfiguration, the disassociation frame is the fifth frame provided in this embodiment of this application, and the MLD receiving the disassociation frame disconnects the current link from the first MLD. If the disassociation frame does not include a field used for multi-link reconfiguration, the disassociation frame is the disassociation frame defined in the existing standard, and the MLD receiving the disassociation frame should disassociate from the first MLD.

[0285] In another possible design, the fifth frame may be a newly defined management frame, such as a link removal notify frame, instead of reusing an existing frame. In this way, the functionality of the existing frame may remain unchanged.

[0286] S402: The receiving end device receives a fifth frame on the target link.

[0287] After receiving the fifth frame, the receiving end device may analyze the fifth frame and further perform a corresponding operation according to the fifth frame.

[0288] For example, the receiving end device is the second MLD. After receiving the fifth frame, the second MLD should remove the target link to the first MLD. Furthermore, the second MLD and the first MLD do not transmit data in the target link.

[0289] For example, the receiving end device is a conventional station (i.e., a single-link device). When the fifth frame reuses an existing frame, the single-link device may disassociate from the first MLD after receiving the fifth frame.

[0290] Optionally, if the fifth frame is a newly defined management frame, the first MLD may further transmit a disassociation frame defined in existing standards on the target link to disassociate from legacy stations and MLDs that have not previously received the fifth frame.

[0291] Based on the embodiment depicted in FIG. 19, the first MLD transmits a fifth frame on the target link to allow other devices to know that the first MLD should remove the target station.

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

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

[0294] S502: The receiving end device receives a third frame on the target link.

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

[0296] S504: The receiving end device receives a fifth frame on the target link.

[0297] According to the embodiment depicted in Figure 20, the first MLD may first transmit the third frame so that another device is ready for the first MLD to remove the target station, and then the first MLD may transmit the fifth frame to remove the target station.

[0298] Currently, multiple stations can be configured so that the MLD supports data transmission on multiple links. However, in some cases, the MLD has a requirement to add stations. For example, when the service volume of the MLD is relatively large, the MLD may add one or more stations associated with the MLD to distribute the data transmission load. However, the prior art does not provide a corresponding solution.

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

[0300] S601: The first MLD transmits a sixth frame in a broadcast manner.

[0301] The sixth frame is used by the first MLD to indicate that the first MLD is adding a target station associated with the first MLD, the target station operating in the target link.

[0302] Optionally, the sixth frame may include information about the target station, for example, the information about the target station includes BSS operating parameters, BSS capability information, and the like.

[0303] Optionally, the sixth frame may reuse an existing frame. For example, the sixth frame may reuse a beacon frame. The sixth frame including information about the target station may be specifically realized as follows: The ML element or reduced neighbor report in the beacon frame includes information about the target station.

[0304] In one possible implementation, the first MLD transmits the sixth frame in a beacon frame manner on all links supported by the first MLD.

[0305] S602: The receiving end device receives a sixth frame.

[0306] According to the embodiment depicted in Fig. 21, the first MLD transmits the sixth frame in a broadcast manner to allow other devices to know that the first MLD should add the target station, so that the other devices can establish a link with the target station of the first MLD for data transmission.

[0307] In this embodiment of the application, the MLD removing a station associated with the MLD can be described as follows: the MLD disables / deactivates the station associated with the MLD or terminates the BSS that the station is in charge of. This is not limited.

[0308] The MLD adding a station associated with the MLD can also be described as follows: the MLD enables / activates the station associated with the MLD or enables the BSS that the station is responsible for, but is not limited to this.

[0309] The solutions provided in the embodiments of this application have been described above in terms of methods. To realize the aforementioned functions, it can be understood that the communication device includes corresponding hardware structures and / or software modules for performing each function. In combination with the example units and algorithm steps described in the embodiments disclosed in this specification, those skilled in the art should easily recognize that this application can be realized by hardware or a combination of hardware and computer software. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to realize the described functions for each specific application, but the implementation should not be considered to go beyond the scope of this application.

[0310] In an embodiment of this application, the device may be divided into functional modules based on the above-mentioned method examples. For example, each functional module may be obtained through division based on each corresponding function, or two or more functions may be integrated into one functional module. The integrated module may be realized in the form of hardware, or in the form of a software functional module. In this embodiment of this application, the module division is an example, and is merely a logical function division. In actual implementation, other division methods may be used. An example in which each functional module is obtained through division based on each corresponding function is used below for explanation.

[0311] 16 illustrates a communication device according to an embodiment of this application. The communication device includes a processing module 101 and a communication module 102.

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

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

[0314] The following describes possible product forms of a communication device. It should be understood that any product of any form having the characteristics of a communication device is within the protection scope of this application. It should be further understood that the following description is merely an example, and does not limit the product form of the communication device in the embodiment of this application.

[0315] FIG. 17 is a schematic diagram of a possible product type structure of a communication device according to one embodiment of this application.

[0316] As one possible product form, the communication device in this embodiment of this 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.

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

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

[0319] As one possible product form, the communication device described in the embodiments of this application can be realized by using a chip. The chip includes a processing circuit 201 and a transceiver pin 202. Optionally, the chip can further include a storage medium 203.

[0320] In another possible product form, the communications apparatus described in this embodiment of this application may alternatively be realized by using any combination of the following circuits or components: one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, any other suitable circuitry, or circuitry capable of performing the various functions described in this application.

[0321] Optionally, an embodiment of this application further provides a computer-readable storage medium, which stores computer instructions, which, when running on a computer, enable the computer to perform the method in the aforementioned method embodiments.

[0322] Optionally, an embodiment of this application further provides a computer program product comprising computer instructions, which, when running on a computer, enable the computer to perform the method in the aforementioned method embodiments.

[0323] It should be understood that computer instructions may be stored in a computer-readable storage medium or transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center in a wired (e.g., coaxial cable, optical fiber, or digital subscriber line) or wireless (e.g., infrared, radio, or microwave) manner. A computer-readable storage medium may be any available medium accessible by a computer, or a data storage device, such as a server or data center, that incorporates one or more available media. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, or a magnetic tape), an optical medium, a semiconductor medium (e.g., a solid-state drive), or the like.

[0324] Based on the above description of the implementation, those skilled in the art can clearly understand that for the purpose of convenient and simple description, the above division into functional modules is used only as an example for description. During actual application, the above functions can be allocated to different functional modules for implementation based on requirements, in other words, the internal structure of the device is divided into different functional modules to realize all or part of the functions described above.

[0325] It should be understood that the apparatus and method disclosed in some embodiments provided in this application may be realized in other ways. For example, the described apparatus embodiments are merely examples. For example, the division into modules or units is merely a logical division of functions, and may be other divisions during actual implementation. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not implemented. In addition, the shown or discussed mutual couplings or direct couplings or communication connections may be realized through some interfaces. Indirect couplings or communication connections between apparatuses or units may be realized in an electrical, mechanical, or other form.

[0326] The units described as separate parts may or may not be physically separate, and the parts shown as units may be one or more physical units and may be located in one place or distributed in different places. Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the embodiments.

[0327] In addition, the functional units in the embodiments of this application may be integrated into one processing unit, each of the units may exist physically alone, or two or more units may be integrated into one unit. The integrated units may be realized in the form of hardware or in the form of software functional units.

[0328] When the integrated unit is realized in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored in a readable storage medium. Based on such understanding, the technical solution of this application in essence, or the part contributing to the prior art, or all or some of the technical solutions may be realized in the form of a software product. The software product is stored in a storage medium and includes some instructions for instructing a device (which may be a single-chip microcomputer, a chip, or the like) or a processor to execute all or some of the steps of the method described in the embodiments of this application.

[0329] The above description is merely a specific implementation of this application, but is not intended to limit the scope of protection of this application. Any variation or replacement within the technical scope disclosed in this application shall be within the scope of protection of this application. Therefore, the scope of protection of this application shall be subject to the scope of protection of the claims. [Explanation of symbols]

[0330] 1 Link 2 Links 3. Links 100 AP Multilink Device 101 AP Multilink Device 101 Processing Module 101-1 Affiliated AP 101-2 AP 101-3 AP 102 STA Multilink Device 102 Communication module 102-1 Affiliated STA 102-2 STA 103 STA Multilink Device 103-1 Affiliated STA 103-2 STA 103-3 STA 104 STA 200 STA Multilink Device 201 Processor 202 Transceiver 203 Memory 300 Multilink Devices 400 STA

Claims

1. 1. A multi-link reconfiguration method, comprising: generating a first frame by a first multi-link device MLD, the first frame being used to reconfigure a link between the first MLD and a second MLD; transmitting, by the first MLD, the first frame to the second MLD; The method includes:

2. The first frame is used to reconfigure a link between the first MLD and a second MLD.

2. The method of claim 1, wherein the first frame includes indicating establishment of a target link between the first MLD and the second MLD.

3. The first frame is used to reconfigure a link between the first MLD and a second MLD.

2. The method of claim 1, wherein the first frame includes indicating removal of a target link from a link established between the first MLD and the second MLD.

4. The first frame is used to reconfigure a link between the first MLD and a second MLD. The method of claim 1 , wherein the first frame indicates a target link, the target link being used for data transmission between the first MLD and the second MLD.

5. The method of claim 1 , wherein the first frame includes a first field, the first field indicating a reconfiguration type, the reconfiguration type including a link removal, a link addition, or a link transition.

6. The first frame is used to reconfigure a link between the first MLD and a second MLD. When the first field indicates link removal, the first frame indicates removal of a target link from a link established between the first MLD and the second MLD; When the first field indicates a link addition, the first frame indicates establishing a target link between the first MLD and the second MLD; or When the first field indicates a link transition, the first frame indicates switching of an established link between the first MLD and the second MLD to a target link; 6. The method of claim 5, comprising:

7. 7. The method of claim 2, wherein the first frame further comprises a second field, the second field indicating the target link.

8. 8. The method of claim 7, wherein the second field comprises a bitmap, the bitmap comprising at least one bit, a bit in the bitmap indicating whether a link corresponding to the bit is the target link.

9. The method of claim 7 , wherein the second field includes an identifier of the target link.

10. 10. The method of claim 2, wherein the first frame further includes a third field, the third field indicating whether a first link is the target link, the first link being a link used to convey the first frame.

11. 11. The method of claim 1, wherein 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 when a value of the type field is a first preset value, the type field indicates 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 comprises: receiving a request frame from the second MLD by the first MLD, the request frame being used to request a link transition between the first MLD and the second MLD; sending a response frame by the first MLD to the second MLD, the response frame indicating whether the link transition between the first MLD and the second MLD is accepted; 12. The method of claim 1, further comprising:

13. The method of claim 12 , wherein the request frame is further used to indicate a recommended link.

14. Prior to the step of receiving a request frame from the second MLD by the first MLD, the method further comprises:

14. The method of claim 12 or 13, further comprising the step of transmitting a query frame by the first MLD to the second MLD, the query frame being used to negotiate a link transition between the first MLD and the second MLD.

15. 1. A multi-link reconfiguration method, comprising: receiving, by a second MLD, a first frame from a first MLD, the first frame being used to reconfigure a link between the first MLD and the second MLD; analyzing the first frame by the second MLD; The method includes:

16. The first frame is used to reconfigure a link between the first MLD and a second MLD.

16. The method of claim 15, wherein the first frame includes indicating establishment of a target link between the first MLD and the second MLD.

17. The first frame is used to reconfigure a link between the first MLD and the second MLD, 16. The method of claim 15, wherein the first frame includes indicating removal of a target link from a link established between the first MLD and the second MLD.

18. The first frame is used to reconfigure a link between the first MLD and the second MLD, 16. The method of claim 15, wherein the first frame indicates a target link, the target link being used for data transmission between the first MLD and the second MLD.

19. 16. The method of claim 15, wherein the first frame includes a first field, the first field indicating a reconfiguration type, the reconfiguration type including a link removal, a link addition, or a link transition.

20. The first frame is used to reconfigure a link between the first MLD and the second MLD, When the first field indicates link removal, the first frame indicates removal of a target link from a link established between the first MLD and the second MLD; When the first field indicates a link addition, the first frame indicates establishing a target link between the first MLD and the second MLD; or When the first field indicates a link transition, the first frame indicates switching of an established link between the first MLD and the second MLD to a target link; 20. The method of claim 19, comprising:

21. 21. The method of claim 16, wherein the first frame further comprises a second field, the second field indicating the target link.

22. 22. The method of claim 21, wherein the second field comprises a bitmap, the bitmap comprising at least one bit, a bit in the bitmap indicating whether a link corresponding to the bit is the target link.

23. The method of claim 21 , wherein the second field includes an identifier of the target link.

24. 24. The method of claim 16, wherein the first frame further includes a third field, the third field indicating whether a first link is the target link, the first link being a link used to convey the first frame.

25. 25. The method of claim 15, wherein 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 when a value of the type field is a first preset value, the type field indicates 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 comprises: sending a request frame by the second MLD to the first MLD, the request frame being used to request a link transition between the first MLD and the second MLD; receiving, by the second MLD, a response frame from the first MLD, the response frame indicating whether the link transition between the first MLD and the second MLD was accepted; 26. The method of any one of claims 15 to 25, further comprising:

27. The method of claim 26 , wherein the request frame is further used to indicate a recommended link.

28. Prior to the step of transmitting a request frame to the first MLD by the second MLD, the method further comprises:

28. The method of claim 26 or 27, further comprising the step of receiving, by the second MLD, a query frame from the first MLD, the query frame being used to negotiate a link transition between the first MLD and the second MLD.

29. An MLD 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 transmit the first frame to the second MLD.

30. The first frame is used to reconfigure a link between a first MLD and a second MLD.

30. The MLD of claim 29, wherein the first frame includes indicating establishment of a target link between the first MLD and the second MLD.

31. The first frame is used to reconfigure a link between a first MLD and a second MLD.

30. The MLD of claim 29, wherein the first frame includes indicating removal of a target link from a link established between the first MLD and the second MLD.

32. The first frame is used to reconfigure a link between a first MLD and a second MLD.

30. The MLD of claim 29, wherein the first frame indicates a target link, the target link being used for data transmission between the first MLD and the second MLD.

33. 30. The MLD of claim 29, wherein the first frame includes a first field, the first field indicating a reconfiguration type, the reconfiguration type including a link removal, a link addition, or a link transition.

34. The first frame is used to reconfigure a link between a first MLD and a second MLD. When the first field indicates link removal, the first frame indicates removal of a target link from a link established between the first MLD and the second MLD; When the first field indicates a link addition, the first frame indicates establishing a target link between the first MLD and the second MLD; or When the first field indicates a link transition, the first frame indicates switching of an established link between the first MLD and the second MLD to a target link; 34. The MLD of claim 33, comprising:

35. 35. The MLD of claim 30, wherein the first frame further includes a second field, the second field indicating the target link.

36. 36. The MLD of claim 35, wherein the second field includes a bitmap, the bitmap including at least one bit, a bit in the bitmap indicating whether a link corresponding to the bit is the target link.

37. 36. The MLD of claim 35, wherein the second field includes an identifier of the target link.

38. 38. The MLD of claim 30, wherein the first frame further includes a third field, the third field indicating whether a first link is the target link, and the first link is a link used to convey the first frame.

39. 39. The MLD of claim 29, wherein 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 when a value of the type field is a first preset value, the type field indicates that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is neither 0 nor 1.

40. The communication module is further configured to receive a request frame from the second MLD, the request frame being used to request a link transition between the first MLD and the second MLD; 40. The MLD of claim 29, wherein the communication module is further configured to transmit a response frame to the second MLD, the response frame indicating whether the link transition between the first MLD and the second MLD has been accepted.

41. The MLD of claim 40, wherein the request frame is further used to indicate a recommended link.

42. The MLD of claim 40 or 41, wherein the communication module is further configured to send a query frame to the second MLD before the first MLD receives the request frame from the second MLD, and the query frame is used to negotiate a link transition between the first MLD and the second MLD.

43. An MLD comprising a communication module and a processing module, 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; The processing module is configured to analyze the first frame.

44. The first frame is used to reconfigure a link between the first MLD and a second MLD.

44. The MLD of claim 43, wherein the first frame includes indicating establishment of a target link between the first MLD and the second MLD.

45. The first frame is used to reconfigure a link between the first MLD and a second MLD.

44. The MLD of claim 43, wherein the first frame includes indicating removal of a target link from a link established between the first MLD and the second MLD.

46. The first frame is used to reconfigure a link between the first MLD and a second MLD.

44. The MLD of claim 43, wherein the first frame indicates a target link, the target link being used for data transmission between the first MLD and the second MLD.

47. 44. The MLD of claim 43, wherein the first frame includes a first field, the first field indicating a reconfiguration type, the reconfiguration type including a link removal, a link addition, or a link transition.

48. The first frame is used to reconfigure a link between the first MLD and a second MLD. When the first field indicates link removal, the first frame indicates removal of a target link from a link established between the first MLD and the second MLD; When the first field indicates a link addition, the first frame indicates establishing a target link between the first MLD and the second MLD; or When the first field indicates a link transition, the first frame indicates switching of an established link between the first MLD and the second MLD to a target link; 48. The MLD of claim 47, comprising:

49. 49. The MLD of claim 34, wherein the first frame further includes a second field, the second field indicating the target link.

50. 50. The MLD of claim 49, wherein the second field includes a bitmap, the bitmap including at least one bit, a bit in the bitmap indicating whether a link corresponding to the bit is the target link.

51. 50. The MLD of claim 49, wherein the second field includes an identifier of the target link.

52. 52. The MLD of claim 44, wherein the first frame further includes a third field, the third field indicating whether a first link is the target link, and the first link is a link used to convey the first frame.

53. 53. The MLD of claim 43, wherein 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 when a value of the type field is a first preset value, the type field indicates that the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first preset value is neither 0 nor 1.

54. The communication module is further configured to send a request frame to the first MLD, the request frame being used to request a link transition between the first MLD and the second MLD; 54. The MLD of any one of claims 43 to 53, wherein the communication module is further configured to receive a response frame from the first MLD, the response frame indicating whether the link transition between the first MLD and the second MLD has been accepted.

55. The MLD of claim 54, wherein the request frame is further used to indicate a recommended link.

56. 56. The MLD of claim 54 or 55, wherein the communication module is further configured to receive a query frame from the first MLD before sending the request frame to the first MLD, the query frame being used to negotiate a link transition between the first MLD and the second MLD.

57. 29. An MLD comprising a processor and a transceiver, the processor configured to perform processing operations in the method of any one of claims 1 to 28, and the transceiver configured to perform communication operations in the method of any one of claims 1 to 28.

58. 29. A computer-readable storage medium storing computer instructions that, when executed in a computer, enable the computer to perform the method of any one of claims 1 to 28.

59. A computer program product, which when executed on a computer enables the computer to carry out the method according to any one of claims 1 to 28.

60. A chip comprising a processing circuit and a transceiver pin, the processing circuit configured to perform the processing operations of the method according to any one of claims 1 to 28, and the transceiver pin configured to perform the communication operations of the method according to any one of claims 1 to 28.

Images