Multilink Reconfiguration Method and Apparatus

Abstract

The present invention provides a multilink reconfiguration method and apparatus for reconfiguring the link between two MLDs. [Solution] A multilink reconfiguration method and apparatus relating to the field of communication technology is provided for reconfiguring a link between two MLDs. The method includes: A first MLD generates a first frame, which is used to reconfigure the link between the first MLD and the second MLD. The first MLD transmits the first frame to the second MLD.

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 Art

[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 important technologies. A multi-link device (MLD) that supports ML communication can transmit and receive on multiple links. In this way, the MLD can use a larger bandwidth for data transmission in order to significantly improve the throughput rate. A link can refer to the spatial path through which the MLD performs data transmission in the 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 two MLDs may not meet the requirements for data transmission between the two MLDs. There is no solution in this industry to solve this problem.

Summary of the Invention

Means for Solving the Problems

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

[0005] According to a first embodiment, a multilink reconfiguration method is provided, which includes: a first MLD generates a first frame, the first frame is used to reconfigure the link between the first MLD and the second MLD, and the first MLD transmits the first frame to the second MLD. Based on the aforementioned technical solution, by transmitting the first frame to the second MLD, the first MLD can trigger a link reconfiguration between the first MLD and the second MLD to satisfy the requirements 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, such as a reassociation request frame or a disassociation frame. It should be understood that reusing a reassociation request frame or a disassociation frame in the first frame avoids significant changes to the existing protocol, eliminates the need to redefine information elements that should be included in the first frame, and saves reserved values ​​for the category field in the action frame.

[0008] If the first frame optionally reuses the reassociation request frame, after the first MLD transmits the first frame to the second MLD, the first and second MLDs may continue to buffer the following information: enhanced distributed channel access (EDCA) function state, block acknowledgment agreement, sequence number (SN), packet number (PN), duplicate detection cache, data queued for transmission, fragment and reassembly buffers, power management mode, and wireless network management sleep mode. In this embodiment of the application, it should be understood that, unlike prior art in which the device is required to delete the aforementioned information in the reassociation procedure, the first frame reuses the reassociation request frame, but the first and second MLDs are not triggered to delete the aforementioned information. Therefore, the first and second MLDs do not need to renegotiate to obtain the aforementioned information after changing the link configuration, thereby reducing the overhead caused by negotiating the aforementioned information.

[0009] In one possible design, the use of a first frame to reconfigure the link between a first MLD and a 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 the data throughput between the first MLD and the second MLD can be increased by adding one or more links between them.

[0010] In one possible design, the use of a first frame to reconfigure the link between a first MLD and a second MLD includes indicating that the first frame removes a target link from the established link between the first MLD and the second MLD. It should be understood that the corresponding energy consumption can be reduced in the first MLD and the second MLD by removing one or more links between them.

[0011] In one possible design, the first frame being used to reconfigure the link between the first MLD and the second MLD includes the first frame indicating the target link, and 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 the reconfiguration type, which includes link removal, link addition, or link transition. Based on this design, one type of first frame can implement multiple types of link reconfiguration.

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

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

[0015] Link transitions can allow two MLDs to switch from a link with poor quality to a link with better quality for data transmission, which should be understood as helping to improve the quality of service of data transmission between the two MLDs.

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

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

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

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

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

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

[0022] In one possible design, the first frame is a reassociation request frame or a disassociation frame, the first frame contains a multi-link element, the multi-link element contains a multi-link control field, and the multi-link control field contains a type field. The type field, whose value is a first preset value, 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.

[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 and second MLDs, the first MLD sending a response frame to the second MLD, the response frame indicating whether the link transition between the first and second MLDs has been accepted. Based on this design, prior to 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 recommended links.

[0025] In one possible design, before the first MLD receives a request frame from the second MLD, the method further includes the first MLD transmitting 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. Based on this design, the first MLD may transmit a query frame to trigger negotiation of a link transition between the two MLDs.

[0026] According to a second aspect, a multi-link reconfiguration method is provided that includes the second MLD receiving a first frame from the first MLD, the first frame being used to reconfigure a link between the first MLD and the second MLD, and the second MLD analyzing 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 the first frame establishing a target link between the first MLD and the second MLD.

[0028] 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 removing a target link from an established link 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, where the target link is 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, and the reconfiguration type includes link removal, link addition, or link transition.

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

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

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

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

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

[0036] In one possible design, the first frame is a reassociation request frame or a disassociation frame, the first frame contains a multi-link element, the multi-link element contains a multi-link control field, and the multi-link control field contains a type field. The type field, whose value is a first preset value, 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.

[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 and second MLDs, the second MLD receiving a response frame from the first MLD, the response frame indicating whether the link transition between the first and second MLDs has been accepted.

[0038] In one possible design, the request frame further indicates recommended links.

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

[0040] According to a third aspect, an MLD is provided which includes a processing module and a communication module. The processing module is configured to generate a first frame, which is used to reconfigure the link between a 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 use of a first frame to reconfigure the link between a first MLD and a 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 use of a first frame to reconfigure the link between a first MLD and a second MLD includes indicating that the first frame removes the target link from the link established between the first MLD and the second MLD.

[0043] In one possible design, the first frame being used to reconfigure the link between the first MLD and the second MLD includes the first frame indicating the target link, and 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, the first field indicating a reconfiguration type, and the reconfiguration type includes link removal, link addition, or link transition.

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

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

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

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

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

[0050] In one possible design, the first frame is a reassociation request frame or a disassociation frame, the first frame contains a multi-link element, the multi-link element contains a multi-link control field, and the multi-link control field contains a type field. The type field, whose value is a first preset value, 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.

[0051] In one possible design, the communication module is further configured to receive a request frame from the second MLD, which is used to request a link transition between the first and second MLDs, and to send a response frame to the second MLD, which indicates whether the link transition between the first and second MLDs has been accepted.

[0052] In one possible design, the request frame further indicates recommended links.

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

[0054] According to a fourth aspect, an MLD is provided which includes 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 reconstruct the 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 use of a first frame to reconfigure the link between a first MLD and a 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 use of a first frame to reconfigure the link between a first MLD and a second MLD includes indicating that the first frame removes the target link from the link established between the first MLD and the second MLD.

[0057] In one possible design, the first frame being used to reconfigure the link between the first MLD and the second MLD includes the first frame indicating the target link, and 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, the first field indicating a reconfiguration type, and the reconfiguration type includes link removal, link addition, or link transition.

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

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

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

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

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

[0064] In one possible design, the first frame is a reassociation request frame or a disassociation frame, the first frame contains a multi-link element, the multi-link element contains a multi-link control field, and the multi-link control field contains a type field. The type field, whose value is a first preset value, 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.

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

[0066] In one possible design, the request frame further indicates recommended links.

[0067] In one possible design, the communication module is further configured to receive query frames from the first MLD, which are used to negotiate link transitions between the first and second MLDs.

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

[0069] According to the sixth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores instructions, and when the instructions are executed in a computer, the computer is enabled to perform a method in either the design of the first or second aspect.

[0070] According to the seventh aspect, a computer program product including instructions is provided. When the computer program product is executed on a computer, the computer is enabled to perform a method in any design of the first or second aspect.

[0071] According to the eighth aspect, a chip is provided that includes a processing circuit and transceiver pins. The processing circuit is configured to perform a processing action in the corresponding manner of the first or second aspect, and the transceiver pins are configured to perform a communication action in the corresponding manner of 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 perform the corresponding method provided above. Therefore, for the beneficial effects that may 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. Further details are not provided here. [Brief explanation of the drawing]

[0073] [Figure 1] This is a schematic diagram illustrating a scenario for communication between an AP multilink device and an STA multilink device according to one embodiment of this application. [Figure 2(a)] This is a schematic diagram of the structure of the communicating AP multilink device and STA multilink device. [Figure 2(b)] This is a schematic diagram of the structure of the communicating AP multilink device and STA multilink device. [Figure 3] This is a schematic diagram of the frame structure of a multi-link element according to one embodiment of this application. [Figure 4] This is a flowchart of a multilink reconstruction method according to one embodiment of this application. [Figure 5] This is a schematic diagram of another frame structure of a multi-link element according to one embodiment of this application. [Figure 6(a)] This is a schematic diagram of another frame structure of a multi-link element according to one embodiment of this application. [Figure 6(b)] This is a schematic diagram of another frame structure of a multi-link element according to one embodiment of this application. [Figure 7] This is a schematic diagram of another frame structure of a multi-link element according to one embodiment of this application. [Figure 8] This is a flowchart of another multilink reconstruction method according to one embodiment of this application. [Figure 9(a)] This is a schematic diagram of another frame structure of a multi-link element according to one embodiment of this application. [Figure 9(b)] This is a schematic diagram of another frame structure of a multi-link element according to one embodiment of this application. [Figure 10] This is a schematic diagram of the BTM procedure in the relevant technologies. [Figure 11(a)] This is a schematic diagram of the frame structure of the BTM query frame in the related technologies. [Figure 11(b)] This is a schematic diagram of the frame structure of neighbor reporting elements in the related technologies. [Figure 12] This is a schematic diagram of the frame structure of the BTM request frame in the related technologies. [Figure 13] This is a schematic diagram of the frame structure of the BTM response frame in the related technologies. [Figure 14] This is a flowchart of another multilink reconstruction method according to one embodiment of this application. [Figure 15] This is a schematic diagram of the frame structure of a neighboring reporting element according to one embodiment of this application. [Figure 16] This is a schematic diagram of the structure of a communication device according to one embodiment of this application. [Figure 17] This is a schematic diagram of the structure of a communication device according to one embodiment of this application. [Figure 18] This is a flowchart of a multilink reconstruction method according to one embodiment of this application. [Figure 19] This is a flowchart of another multilink reconstruction method according to one embodiment of this application. [Figure 20] This is a flowchart of another multilink reconstruction method according to one embodiment of this application. [Figure 21] This is a flowchart of another multilink reconstruction method according to one embodiment of this application. [Figure 22] This is a schematic diagram of the frame structure of a requested mode field according to one embodiment of this application. [Modes for carrying out the invention]

[0074] In this description of the application, unless otherwise specified, " / " means "or". For example, A / B may represent A or B. In this specification, the term "and / or" describes only the relationship between related subjects and indicates that there may be three relationships. For example, A and / or B may 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 order of execution, and terms such as "first" and "second" do not indicate a limiting difference.

[0075] In this application, phrases such as “example” or “for example” are used to express that an example, illustration, or explanation is being given. Any embodiment or design described as “example” or “for example” in this application should not be described as being preferred over or having more advantages than another embodiment or design. More precisely, the use of phrases such as “for example” or “example” or similar is intended to present relative concepts in a specific manner.

[0076] The technical solutions provided in this application may be applied to various communication systems, for example, systems to which the IEEE 802.11 standard applies. 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 in this application are applicable to the following scenarios: communication between APs and STAs, communication between APs, communication between STAs, and similar scenarios.

[0077] In this application, STA 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 wireless modems, and may include various forms of user equipment (UE), mobile stations (MS), terminals, terminal equipment, mobile communication devices, handheld devices, mobile computing devices, entertainment devices, game 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 explanation, the above-mentioned devices are collectively referred to here as stations or STA.

[0078] In this application, an access point AP is a device deployed within a wireless communication network that provides wireless communication capabilities for a STA associated with the access point AP. The access point AP may be used as a hub in a communication system and may also be a communication device such as a base station, router, gateway, repeater, communication server, switch, or bridge. Base stations may include macro base stations, micro base stations, relay stations, and similar in various forms. For ease of explanation, these devices are collectively referred to here as access point APs.

[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.4GHz, 5GHz, 6GHz frequency bands), collaboration of multiple channels in the same frequency band, and similar features to improve peak throughput and reduce service transmission latency. Multiple frequency bands or multiple channels may collectively be referred to as multiple links.

[0080] A multilink device includes one or more affiliated stations. An affiliated station may be a logical station or a physical station. In embodiments of this application, “a multilink device includes affiliated stations” may be more concisely described as “a multilink device includes stations.”

[0081] The partner station may be an access point (AP) or a non-access point station (non-AP STA). For ease of explanation, in embodiments of this application, a multilink device in which the partner station is an AP may be referred to as a multilink AP, AP MLD, or multilink AP device, and a multilink device in which the partner station is an STA may be referred to as a multilink STA, multilink STA device, STA MLD, or non-AP MLD.

[0082] A multilink device may enable wireless communication in accordance with the 802.11 protocol. For example, the 802.11 protocol may be the 802.11ax protocol, the 802.11be protocol, or the next-generation 802.11 protocol. This is not limited to the embodiments of this application.

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

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

[0085] The frequency bands in which multilink devices operate are not limited, but may include Sub 1GHz, 2.4GHz, 5GHz, 6GHz, and high-frequency 60GHz. Figures 2(a) and 2(b) show two schematic diagrams of multilink devices communicating with other devices over multiple links in a wireless local area network.

[0086] Figure 2(a) illustrates a scenario in which the AP multilink device 101 communicates with the STA multilink device 102. The AP multilink device 101 includes partner AP101-1 and AP101-2, and ST A Luchilink device 102 includes the affiliated STA102-1 and STA102-2, and the AP multilink device 101 and STA multilink device 102 communicate with each other on both Link 1 and Link 2.

[0087] Figure 2(b) illustrates a scenario in which AP multilink device 101 communicates with STA multilink devices 102, STA multilink devices 103, and STA104. AP multilink device 101 includes partner AP101-1 to AP101-3, STA multilink device 102 includes partner STA102-1 and STA102-2, and STA multilink device 103 includes partner STA103-1 and STA103- 2 Includes. STA104 is a single-link device (SLD). An AP multilink device may communicate with STA multilink device 102 on links 1 and 3, with STA multilink device 103 on links 2 and 3, and with STA104 on link 1. In one example, STA104 operates in the 2.4GHz frequency band, STA multilink device 103 includes STA103-1 and STA103-2, with STA103-1 operating in the 5GHz frequency band and STA103-2 operating in the 6GHz frequency band, and STA multilink device 102 includes STA102-1 and STA102-2, with STA102-1 operating in the 2.4GHz frequency band and STA102-2 operating in the 6GHz frequency band. AP101-1, operating in the 2.4GHz frequency band within the AP multilink device, connects to STA104 and STA102- within the STA multilink device 102. 1 Uplink or downlink data can be exchanged over Link 1. AP101-2, operating in the 5GHz frequency band within the AP multilink device, can exchange uplink or downlink data over Link 2 with STA103-1, operating in the 5GHz frequency band within the STA multilink device 103. AP101-3, operating in the 6GHz frequency band within the AP multilink device 101, may exchange uplink or downlink data over Link 3 with STA102-2, operating in the 6GHz frequency band within the STA multilink device 102, and may also exchange uplink or downlink data over Link 3 with STA103-2 within the STA multilink device.

[0088] Figure 2(a) illustrates that the AP multilink device supports only two frequency bands, and Figure 2(b) uses an example where the AP multilink device supports only three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), with each frequency band corresponding to one link. It should be noted that the AP multilink device 101 may operate on one or more of links 1, 2, and 3. On the AP side or STA side, a link here may also be understood as a station operating on a link. In practical applications, AP multilink devices and STA multilink devices may further support more or fewer frequency bands. In other words, AP multilink devices and STA multilink devices may operate on more or fewer links. This is not limited to the embodiments of this application.

[0089] For example, a multilink device is a device having wireless communication capabilities. The device may be an entire device, or a chip, processing system, or similar 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 of the embodiments of this application.

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

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

[0092] For example, a 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 the transmission link, and link 2 may be referred to as the non-transmission link. An 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, links 1 and 2 are established between the non-AP MLD and the AP MLD. Furthermore, the non-AP MLD and AP MLD can perform data transmission on links 1 and 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 Figure 3, the information carried in a multi-link element is divided into two parts: MLD-level info and a per-link profile. The per-link profile is sometimes also called a per-STA profile. It should be understood that the per-link profile is optional. In other words, a multi-link element may or may not contain a per-link profile, or it may contain one or more per-link profiles. For example, Figure 3 shows a multi-link element with per-link profile x and per-link profile y.

[0094] MLD-level info includes the following fields, namely the Multi-link control field and one or more fields. For example, one or more fields may include the following fields, namely the element ID, length, extended element ID, and similar fields.

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

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

[0097] The data fields within a per-link profile include one or more of the following fields: a per-STA control field, one or more elements, and one or more non-inheritance elements. Non-inheritance elements are optional fields.

[0098] Each station's control field includes at least one link ID. It should be understood that non-AP MLDs can obtain link information (e.g., link ID) corresponding to each link by receiving probe response frames or beacon frames.

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

[0100] For example, when two MLDs are initially 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 for data transmission. Therefore, an additional link needs to be added between the two MLDs.

[0101] In another example, when two MLDs are initially 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 data transmission throughput requirements. Therefore, to reduce energy consumption, redundant links between the two MLDs need to be eliminated.

[0102] In another example, when two MLDs are initially associated, Link 1 is established, but the communication quality of Link 1 is poor. Therefore, 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 the link configuration after an MLD association.

[0104] One embodiment of this application provides a multilink reconfiguration method to support link configuration changes after two MLDs have been associated. As shown in Figure 4, the method includes the following steps:

[0105] S101. The first MLD generates the first frame.

[0106] The first frame is used to reconstruct multiple links between the first MLD and the second MLD.

[0107] Prior to step S101, it should be understood that one or more links have been established between the first MLD and the second MLD through an association.

[0108] In embodiments of this application, the first frame may be a newly defined frame, or an existing frame (for example, a reassociation request frame or an unassociation frame) may be reused. This is not limited to these embodiments.

[0109] Optionally, the first frame may use 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 the establishment of a target link between the first MLD and the second MLD. That is, 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 the first MLD and the second MLD through an association. The first frame indicates the establishment of Link 3, thereby Link 3 can be further established between the first MLD and the second MLD. Links 1, 2, and 3 can then be used for data transmission between the first MLD and the second MLD.

[0113] In this embodiment of the application, two MLDs can perform data transmission over an established link but cannot perform data transmission over an unestablished link. The two MLDs can exchange some management frames (such as association request / response frames) over an unestablished link for link establishment.

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

[0115] Specifically, this indicates that the first frame removes the target link from the link established between the first MLD and the second MLD. The target link is the link currently established 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 the removal of Link 2. After the first and second MLDs remove Link 2, Link 2 becomes an unestablished link between the first and second MLDs. The first and second MLDs can use only Link 1 for data transmission, but cannot use Link 2 for data transmission.

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

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

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

[0120] A target link can be used for data transmission between a first MLD and a 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, links 1 and 2 are established between the first MLD and the second MLD through an association. The first frame shows links 2, 3, and 4, thereby eliminating link 1 and establishing links 3 and 4 between the first MLD and the second MLD. In this way, the first and second MLDs may use links 2, 3, and 4 for data transmission, but cannot use link 1 for data transmission.

[0122] The idea behind Design 1-3 should be understood as follows: The first frame indicates the link to be ultimately established between the first MLD and the second MLD (i.e., the target link), thereby allowing the first and second MLDs to determine the reconfiguration actions to be actually performed (e.g., removing links and / or adding links) based on the currently established links and the link to be ultimately established.

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

[0124] In embodiments of this application, link removal, also sometimes referred to as link severance, is used to configure an established link between two devices as an unestablished link. Link addition, also sometimes referred to as link creation, is used to configure an unestablished link between two devices as an established link. Link transition, also sometimes referred to as link switching, is used to remove an established link between two devices and establish a link for transition.

[0125] Optionally, based on Design 1-4, the first frame may be used to reconfigure multiple links between the first MLD and the second MLD, including the following cases:

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

[0127] Case 2: When the first field indicates link addition, the first frame indicates establishing 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 the first MLD and the second MLD through an association. A first field included in the first frame indicates a link transition, and the first field indicates a switch from Link 2 to Link 3, which is established between the first MLD and the second MLD. In this way, Link 2 is removed and Link 3 is established between the first MLD and the second MLD. The first MLD and the second MLD can exchange data over Link 1 and Link 3, rather than over Link 2.

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

[0131] For example, the first field may have a different name, such as the action field. This is not limited to the case here.

[0132] Unlike designs 1-1 through 1-3, it should be understood that the first frame in design 1-4 can be used to flexibly reconfigure the link between the first MLD and the second MLD.

[0133] Designs 1-1 through 1-4 described above are merely examples, and do not limit the specific implementation of the first frame. 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, the second field indicating the target link.

[0135] Optionally, the second field may use 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 contains a bitmap, which contains at least one bit, and one bit in the bitmap indicates whether the link corresponding to the bit is the target link.

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

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

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

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

[0142] For example, the second field may have a different name, such as the target link set field. This is not limited to the case here.

[0143] The following describes a specific implementation of the second field by referring to different implementations.

[0144] Implementation 1: The second field specifically indicates the 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 contains a bitmap, the number of bits in the bitmap may be the same as the number of links supported by the first MLD, thereby establishing a one-to-one correspondence between the bits in the bitmap and 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, thereby establishing a one-to-one correspondence between the bits in the bitmap and the links supported by the second MLD.

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

[0147] Optionally, based on implementation 2, if the second field contains a bitmap, the number of bits in the bitmap may be the same as the number of links in the second link. Therefore, there is a one-to-one correspondence between the bits in the bitmap and the second link.

[0148] Based on Implementation 2, it should be understood that 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, the third field indicating whether the first link is a target link. For example, the third field may occupy one bit.

[0150] For example, as shown in Figure 7, the first frame may include a multi-link element, and the MLD-level info within 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 the first frame is used to add a target link, and the first link is an unestablished link between the first MLD and the second MLD, then the first link may be considered as the target link by default.

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

[0154] In another example, the first frame might represent the target link, and the first link might be considered the target link by default.

[0155] If the first frame optionally reuses a reassociation request frame, please refer to Table 1 for the frame structure of the first frame.

[0156] [Table 1]

[0157] Table 1 represents only a few information elements, and it should be understood that the first frame may contain other information elements as well. This is not limited to these elements.

[0158] If the first frame optionally reuses the disassociated frame, please refer to Table 2 for the frame structure of the first frame.

[0159] [Table 2]

[0160] Table 2 represents only a few information elements, and it should be understood that the first frame may contain other information elements as well. This is not limited to these elements.

[0161] Optionally, when the first frame reuses a reassociation request frame or a disassociation frame, the first frame may contain a multi-link element. In addition, the first frame can be distinguished from existing reassociation request frames or disassociation frames by using the type field within the multi-link control field of 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 reconstruct the 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.

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

[0164] [Table 3]

[0165] In embodiments 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) in an existing type field. Thus, a device may determine that a frame using the multi-link element variant name is to be used for multi-link reconstruction.

[0166] Compared to the first frame being a new type of action frame, it should be understood that the first frame reuses a reassociation request frame or a disassociation frame, which helps avoid excessive changes to the existing protocol. 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 transmits the first frame to the second MLD. 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 Figure 4, the first MLD transmits a first frame to the second MLD to trigger a link reconfiguration between the first MLD and the second MLD in order to satisfy the requirements for communication between the two MLDs and to ensure normal communication between the two MLDs.

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

[0171] Unlike existing reassociation procedures, when the first frame reuses the reassociation request frame, the first and second MLDs do not have to delete the aforementioned information to avoid the operational overhead caused by subsequent negotiation in order to retrieve the information. In other words, after the first MLD sends the first frame to the second MLD, the first and second MLDs may continue to buffer the following information, namely the Extended Distributed Channel Access Function status, block acknowledgment protocol, sequence number, packet number, duplicate detection cache, data queued for transmission, fragment and reassembly buffers, power management mode, wireless network management sleep mode, and similar.

[0172] Optionally, based on the embodiment shown in Figure 4, the multilink reconstruction method may further include step S104 after step S103 in the embodiment shown in Figure 8.

[0173] S104: The second MLD transmits the 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, if the first frame reuses a disassociation frame, the second frame may be an acknowledgment (ACK) frame.

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

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

[0178] For example, when the second frame reuses a reassociation response frame, please refer to 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, please refer to Table 5 for the specific structure of the status codes.

[0182] [Table 5]

[0183] It should be understood that "No reason for rejection 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 contain only one status code, and this status code is for all target links.

[0185] For example, the first frame might indicate the addition of links 1 and 2, and the status code in the second frame might indicate success. In this case, links 1 and 2 are established between the first MLD and the second MLD.

[0186] In another example, the first frame might indicate adding links 1 and 2, while the status code in the second frame indicates rejection. In this case, links 1 and 2 are not established between the first and second MLDs.

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

[0188] For example, the first frame may indicate the addition of links 1 and 2, with the status code corresponding to link 1 in the second frame indicating success and the status code corresponding to link 2 in the second frame indicating failure. In this case, link 1 is established between the first and second MLDs, but link 2 is not.

[0189] In another example, the first frame may indicate the removal of links 1 and 2, with the status code corresponding to link 1 in the second frame indicating success and the status code corresponding to link 2 in the second frame indicating failure. In this case, between the first and second MLDs, link 1 is removed, but link 2 is not.

[0190] Optionally, for target links other than the first link, the status code corresponding to the target link may be placed in the per-link profile corresponding to the target link. For example, as shown in Figure 9(a), the second frame may include a multi-link element containing a per-link profile, the per-link profile containing a per-STA control field, and the per-STA control field containing a status code.

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

[0192] Optionally, if 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 may be ignored (disregarded) in the second frame.

[0193] Optionally, when a second frame reuses a reassociation response frame, the second frame can be distinguished from the existing reassociation response frame by using the type field in the multi-link control field within 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 the 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 shown in Figure 8, the second MLD transmits a second frame to the first MLD so that the first MLD can know how to reconfigure the link between the first MLD and the second MLD.

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

[0196] When an STA discovers poor link quality or for other reasons, it may send a Basic Service Set Transition Management (BSS transition management, BTM) query frame to its affiliated AP. It should be understood that sending a BTM query frame is optional. After receiving a BTM query sent by an STA, the AP may respond with an ACK frame.

[0197] When the AP wants the 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 it accepts or rejects 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), a BTM query frame may include the following fields: category, wireless network management action (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 relevant technologies.

[0201] [Table 6]

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

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

[0204] The BSSID field indicates the reported BSSID corresponding to the neighboring AP. The BSSID information field shows 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, 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 shown in Figure 12, a BTM request frame may include the following fields: category, wireless network management action, dialog token, request mode, disassociation timer, validity interval, BSS termination duration, session info URL, and BSS transition candidate list. The BSS transition candidate list is optional.

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

[0208] The disassociation timer field indicates the time elapsed since the AP sent the disassociation frame.

[0209] The request mode field indicates the specific request mode. The request 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 the preferred candidate list is included.

[0211] The abridged field is used as follows: The abridged field is set to 0 if the affiliated AP does not recommend or prohibits the STA from switching to a BSS that does not appear in the preferred candidate list. The abridged field is set to 1 if the associated AP sets the preference value of a BSS that does not appear in the 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 will 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, a BTM response frame may include the following fields: Category, Wireless 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 relevant technology, when the BTM Status Code value 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 termination delay indicates the duration of the time period from the current time to the BSS termination 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 the two MLDs, the two MLDs may also perform link transition negotiation, thereby allowing the two MLDs to transition from the currently established link to a better link for communication. In view of this, one embodiment of this application provides a multilink reconfiguration method. As shown in Figure 14, the method includes the following steps:

[0220] S201 (Optional): The first MLD sends a query frame to the second MLD. 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. That is, the first MLD does not decide whether to perform link transition negotiation or BSS transition negotiation. Instead, the second MLD decides whether to perform link transition negotiation or BSS transition negotiation according to the actual situation.

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

[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, a query frame may include one or more neighbor reporting elements. It should be understood that each neighbor reporting element corresponds to one AP located near the first MLD.

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

[0226] Optionally, basic multi-link elements within neighbor reporting elements may omit a per-link profile to reduce signaling overhead.

[0227] Optionally, when a 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 the type field in the multi-link control field within 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 a link transition between a first MLD and a second MLD. The second preset value is neither 0 nor 1. Optionally, the second preset value may be the same as the first preset value mentioned above. This is not limited to this.

[0228] Optionally, when a query frame reuses an existing BTM query frame, one or more new values ​​may be defined for the `transition query reason` field within the query frame to indicate a reason for the link transition, such as a high link frame loss rate, poor link quality, or the discovery of a better link.

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

[0230] Optionally, after receiving a 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 recommended links. Recommended links may also be referred to as suggested links, candidate links, or by other names, but are not limited to these.

[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 a request frame reuses an existing BTM request frame, the request mode field in the request frame may include a fourth field, which may indicate a new request mode. The new request mode may be called a link transition request mode, a link removal mode, or a link-level association disassociation mode. For example, the fourth field may use reserved bits from the request mode field in the existing BTM frame. For example, the fourth field may occupy 1 bit. For example, Figure 22 shows the frame structure of the request mode field in a request frame. The fourth field may be the link removal field in Figure 22.

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

[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, which may include one or more neighbor reporting elements. Each neighbor reporting element corresponds to one AP located near the second MLD.

[0239] As shown in Figure 15, a fifth field may be added to the BSSID information field of the neighbor reporting element. The fifth field indicates the ID of the MLD to which the BSS corresponding to the link for 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 a 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 the AP MLD ID field.

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

[0243] Optionally, basic multi-link elements within neighbor reporting elements may omit 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 a response frame from the first MLD.

[0246] The response frame indicates whether it accepts a 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 a response frame reuses an existing BTM response frame, the BTM status code within the response frame may have one or more newly defined values ​​to indicate the link transition result, for example, whether the link transition was accepted or rejected.

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

[0250] In some embodiments, if the first MLD chooses to establish a connection to an AP that supports only a single link, the target BSSID field may include the BSSID corresponding to the AP. Alternatively, if the first MLD chooses 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 reporting elements. It should be understood that each neighbor reporting element corresponds to one AP located near the first MLD.

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

[0253] Optionally, basic multi-link elements within neighbor reporting elements may omit a per-link profile to reduce signaling overhead.

[0254] Optionally, after receiving the response frame, the second MLD receives the ACK frame. 1It can be sent to MLD.

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

[0256] Currently, multiple stations can be configured to support data transmission over multiple links in an MLD. However, in some cases, there are station removal requirements for MLDs. For example, when the traffic volume of an MLD is relatively low, the MLD may remove one or more stations, which helps reduce the MLD's power consumption. However, conventional technology does not provide a corresponding solution.

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

[0258] As shown in Figure 18, one embodiment of this application provides a multilink reconstruction method. The method includes the following steps:

[0259] S301: The first MLD transmits the third frame on the target link using broadcast mode.

[0260] Regarding the first MLD, the third frame indicates that the first MLD should remove the target station, which is a station that operates in conjunction with the first MLD and on 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 broadcast mode. When the first MLD should remove AP2, the first MLD transmits a third frame on link 2 in broadcast mode. When the first MLD should remove AP3, the first MLD transmits a third frame on link 3 in broadcast mode.

[0262] In one possible design, the third frame may reuse existing frames 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 contains a sixth field whose value is a third pre-set value.

[0264] A sixth field whose value is a third pre-set value may indicate that the MLD receiving the BTM request frame disconnects the target link from the first MLD. A sixth field whose value is a fourth pre-set value may indicate that the MLD receiving the BTM request frame disconnects all links from the first MLD in order to disassociate it 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 the 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 device receives the third frame on the target link.

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

[0269] For example, the receiving 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 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, when 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 the conventional stations and the MLDs that do not receive the third frame to perform a BSS transition.

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

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

[0274] Optionally, if the fourth frame reuses the beacon frame, a seventh field may be added to the beacon frame, which indicates the time after which 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 within 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 a different name, for example, a delete timer field. This is not limited to this.

[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 within the per-STA profile subelement of the target station corresponding to the 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 to this.

[0276] According to the embodiment shown in Figure 18, the first MLD transmits a third frame on the target link to allow another device to know that the first MLD should remove the target station.

[0277] As shown in Figure 19, one embodiment of this application provides a multilink reconstruction method. The method includes the following steps:

[0278] S401: The first MLD transmits the fifth frame on the target link in broadcast mode.

[0279] The fifth frame indicates that the first MLD should remove the target station, which is a station that operates in conjunction with the first MLD and on 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 existing frames 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 deassociation frame.

[0282] If the fifth frame reuses the disassociation frame, it should be understood that the disassociation frame needs to be improved so that the receiving end device of the disassociation frame can know that the function of the disassociation frame is to remove the current link but not to indicate disassociation. Optionally, if the fifth frame is a disassociation frame, the indication that the first MLD should remove the current link can be specifically achieved as follows: The disassociation frame includes fields used for multilink reconfiguration. Optionally, the fields used for multilink reconfiguration do not include information about the target link. The fields used for multilink reconfiguration may have a different name, e.g., ML reconfiguration variant ML element. This is not limited to this. Optionally, for broadcast disassociation frames, only the current link may be removed. In one implementation, the ML reconfiguration variant ML element does not have to include a per-link profile. For a unicast deassociation frame, one or more links may be removed. In one implementation, a multilink reconfiguration variant multilink element carries a per-link profile, link ID, or the link bitmap of the corresponding link to indicate the target link.

[0283] Alternatively, the indication that the first MLD should remove the current link can be specifically achieved as follows: The fifth frame includes a reason code field, the reason code field indicating that the current link should be removed. Compared to the reason code field included in the disassociation frame in the related technology, it should be understood that in this embodiment of the 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] If the fifth frame optionally reuses a disassociation frame, the disassociation frame has different functions in different cases. For example, when the disassociation frame includes fields used for multilink reconstruction, 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 fields used for multilink reconstruction, the disassociation frame is a disassociation frame as defined in existing standards, and the MLD receiving the disassociation frame should disassociate from the first MLD.

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

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

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

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

[0289] For example, the receiving 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, when the fifth frame is a newly defined management frame, the first MLD may further transmit a disassociation frame defined in the existing standard on the target link to disassociate from the conventional station and the MLD that has not previously received the fifth frame.

[0291] Based on the embodiment shown in FIG. 19, the first MLD transmits the fifth frame on the target link to enable another device to know that the first MLD should remove the target station.

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

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

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

[0295] S503: The first MLD transmits the fifth frame on the target link using broadcast mode.

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

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

[0298] Currently, multiple stations can be configured to support data transmission over multiple links in an MLD. 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 need one or more stations partnered with it to distribute the data transmission load. However, prior art does not provide a corresponding solution.

[0299] In view of this, one embodiment of this application provides a multilink reconstruction method. As shown in Figure 21, the method includes the following steps.

[0300] S601: The first MLD transmits the sixth frame in broadcast mode.

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

[0302] Optionally, the sixth frame may contain information about the target station. For example, information about the target station may include BSS operating parameters, BSS capability information, and similar information.

[0303] Optionally, the sixth frame may reuse an existing frame. For example, the sixth frame may reuse a beacon frame. The inclusion of information about the target station in the sixth frame can be specifically achieved as follows: an ML element or reduced neighbor report within the beacon frame contains information about the target station.

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

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

[0306] According to the embodiment shown in Figure 21, the first MLD transmits a sixth frame in a broadcast manner to enable another device to know that the first MLD should add a target station. Thus, the other device can establish a link with the target station of the first MLD for data transmission.

[0307] In this embodiment of the application, the removal of 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 responsible for. This is not limited to the above.

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

[0309] The solutions provided in embodiments of this application are described above in terms of method. It can be understood that, in order to implement the functions described above, the communication device includes corresponding hardware structures and / or software modules for performing each function. Combined with the example units and algorithmic steps described in the embodiments disclosed in this specification, it should be readily apparent to those skilled in the art that this application can be implemented in hardware or in 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 the design constraints of the technical solution. Those skilled in the art may use different methods to implement the functions described for each specific application, but the implementation should not be considered to be beyond the scope of this application.

[0310] In embodiments of this application, the device may be divided into functional modules based on the examples of the methods described above. For example, each functional module may be obtained through a division based on its respective corresponding function, or two or more functions may be integrated into a single functional module. The integrated module may be implemented in hardware form or in the form of a software functional module. In this embodiment of this application, the modularization is illustrative and merely a logical functional division. In actual implementations, other division methods may be used. An example in which each functional module is obtained through a division based on its respective corresponding function is used below for illustrative purposes.

[0311] Figure 16 shows a communication device according to one 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 the first MLD, or when the communication device is applied to the first MLD, the processing module 101 is configured to support the first MLD when performing step S101 in Figure 4. The communication module 102 is configured to support the first MLD when performing step S102 in Figure 4, step S104 in Figure 8, steps S201 to S203 in Figure 14, step S301 in Figure 18, step S401 in Figure 19, steps S501 and S503 in Figure 20, and step S601 in Figure 21.

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

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

[0315] Figure 17 is a schematic diagram of the structure of a possible product form 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 multilink device, which includes a processor 201 and a transceiver 202. Optionally, the multilink device further includes a memory 203.

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

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

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

[0320] In other possible product forms, the communication device described in this embodiment of this application may be implemented by using, alternatively, one or more field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, individual hardware components, any other suitable circuitry, or any combination of circuits capable of performing the various functions described in this application.

[0321] Optionally, one embodiment of this application further provides a computer-readable storage medium that stores computer instructions. When the computer instructions are executed in a computer, the computer is enabled to perform the method in the embodiment of the method described above.

[0322] Optionally, one embodiment of this application further provides a computer program product including computer instructions. When the computer instructions are executed in a computer, the computer is enabled to perform the method in the embodiment of the method described above.

[0323] It should be understood that computer instructions may be stored in computer-readable storage media or transmitted from one computer-readable storage medium to another. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wired means (e.g., coaxial cable, optical fiber, or digital subscriber line) or wireless means (e.g., infrared, radio, or microwave). Computer-readable storage media may be any available medium accessible by a data storage device, such as a computer or a server or data center that integrates one or more available media. Available media may be magnetic media (e.g., floppy disks, hard disks, or magnetic tapes), optical media, semiconductor media (e.g., solid-state drives), or similar.

[0324] Based on the above-described implementation, those skilled in the art will clearly understand that, for the purpose of convenient and simple explanation, the division into functional modules described above is used merely as an example for illustrative purposes. During actual application, the functions described above may be assigned to different functional modules for implementation based on requirements; in other words, the internal structure of the device may be divided into different functional modules to realize all or some of the functions described above.

[0325] It should be understood that the apparatus and methods disclosed in some embodiments provided in this application may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into modules or units is merely a logical functional division 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 performed. In addition, the mutual coupling, direct coupling or communication connection shown or discussed may be implemented through some interfaces. Indirect coupling or communication connection between apparatus or units may be implemented electrically, mechanically or in other forms.

[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, may be located in one place, or may be distributed in different places. Some or all of the units may be selected based on the actual requirements to achieve the objectives of the solution of the embodiment.

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

[0328] When an integrated unit is implemented 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 solutions of this application, or parts that contribute to the prior art, or all or some of the technical solutions, may be implemented in the form of a software product. The software product is stored in a storage medium and includes several instructions for instructing a device (which may be a single-chip microcomputer, chip, or similar) or processor to perform all or some of the steps of the method described in embodiments of this application.

[0329] The foregoing description is merely a specific implementation of this application and is not intended to limit the scope of protection of this application. Any modifications or substitutions within the scope of the art disclosed in this application are within the scope of protection of this application. Therefore, the scope of protection of this application is 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. A multilink reconfiguration method, A step of generating a first frame using a first multilink device (MLD), wherein the first frame is used to reconfigure the link between the first MLD and a second MLD. The first MLD transmits the first frame to the second MLD, A method that includes this.

2. The first frame is used to reconfigure the link between the first MLD and the second MLD. The method according to claim 1, comprising indicating that the first frame establishes a target link between the first MLD and the second MLD.

3. The first frame is used to reconfigure the link between the first MLD and the second MLD. The method according to claim 1, comprising indicating that the first frame removes the target link from the link established between the first MLD and the second MLD.

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

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

6. The first frame is used to reconfigure the link between the first MLD and the second MLD. When the first field indicates link removal, the first frame indicates removing the target link from the link established between the first MLD and the second MLD. When the first field indicates the addition of a link, the first frame indicates the establishment of 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 the link established between the first MLD and the second MLD to the target link. The method according to claim 5, including the method described in claim 5.

7. The method according to any one of claims 2 to 6, wherein the first frame further includes a second field, the second field indicating the target link.

8. The method according to claim 7, wherein the second field includes a bitmap, the bitmap includes at least one bit, and the bit in the bitmap indicates whether the link corresponding to the bit is the target link.

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

10. The method according to any one of claims 2 to 9, wherein the first frame further includes a third field, the third field indicating whether the first link is the target link, and the first link is a link used to transmit the first frame.

11. The method according to any one of claims 1 to 10, wherein the first frame is a reassociation request frame or an unassociation 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, the type field indicating that the first frame is used to reconfigure the link between the first MLD and the second MLD when the value of the type field is a first preset value, and the first preset value is neither 0 nor 1.

12. The aforementioned method, The steps include: receiving a request frame from the second MLD via the first MLD, wherein the request frame is used to request a link transition between the first MLD and the second MLD; A step of transmitting a response frame from the first MLD to the second MLD, wherein the response frame indicates whether the link transition between the first MLD and the second MLD has been accepted. The method according to any one of claims 1 to 11, further comprising:

13. The method according to 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 The method according to claim 12 or 13, further comprising the step of sending a query frame to the second MLD via the first MLD, wherein the query frame is used to negotiate a link transition between the first MLD and the second MLD.

15. A multilink reconfiguration method, A step of receiving a first frame from a first MLD by a second MLD, wherein the first frame is used to reconfigure the link between the first MLD and the second MLD. The second MLD is used to analyze the first frame, A method that includes this.

16. The first frame is used to reconfigure the link between the first MLD and the second MLD. The method according to claim 15, comprising indicating that the first frame establishes a target link between the first MLD and the second MLD.

17. The first frame is used to reconstruct the link between the first MLD and the second MLD. The method according to claim 15, comprising indicating that the first frame removes the target link from the link established between the first MLD and the second MLD.

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

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

20. The first frame is used to reconstruct the link between the first MLD and the second MLD. When the first field indicates link removal, the first frame indicates removing the target link from the link established between the first MLD and the second MLD. When the first field indicates the addition of a link, the first frame indicates the establishment of 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 the link established between the first MLD and the second MLD to the target link. The method according to claim 19, including the method described in claim 19.

21. The method according to any one of claims 16 to 20, wherein the first frame further includes a second field, the second field indicating the target link.

22. The method according to claim 21, wherein the second field includes a bitmap, the bitmap includes at least one bit, and the bit in the bitmap indicates whether the link corresponding to the bit is the target link.

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

24. The method according to any one of claims 16 to 23, wherein the first frame further includes a third field, the third field indicating whether the first link is the target link, and the first link is a link used to transmit the first frame.

25. The method according to any one of claims 15 to 24, wherein the first frame is a reassociation request frame or an unassociation 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, the type field indicating that the first frame is used to reconfigure the link between the first MLD and the second MLD when the value of the type field is a first preset value, and the first preset value is neither 0 nor 1.

26. The aforementioned method, The steps include: sending a request frame from the second MLD to the first MLD, wherein the request frame is used to request a link transition between the first MLD and the second MLD; A step of receiving a response frame from the first MLD by the second MLD, wherein the response frame indicates whether the link transition between the first MLD and the second MLD has been accepted. The method according to any one of claims 15 to 25, further comprising:

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

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

29. A Multi-Labeled Device (MLD) comprising a processing module and a communication module, The processing module is configured to generate a first frame, which is used to reconfigure the link between the first MLD and the second MLD. The communication module is configured to transmit the first frame to the second MLD, which is an MLD.

30. The first frame is used to reconfigure the link between the first MLD and the second MLD. The MLD according to claim 29, comprising indicating that the first frame establishes a target link between the first MLD and the second MLD.

31. The first frame is used to reconfigure the link between the first MLD and the second MLD. The MLD according to claim 29, comprising indicating that the first frame removes the target link from the link established between the first MLD and the second MLD.

32. The first frame is used to reconfigure the link between the first MLD and the second MLD. The MLD according to claim 29, wherein the first frame indicates a target link, and the target link is used for data transmission between the first MLD and the second MLD.

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

34. The first frame is used to reconfigure the link between the first MLD and the second MLD. When the first field indicates link removal, the first frame indicates removing the target link from the link established between the first MLD and the second MLD. When the first field indicates the addition of a link, the first frame indicates the establishment of 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 the link established between the first MLD and the second MLD to the target link. The MLD according to claim 33, including the following:

35. The MLD according to any one of claims 30 to 34, wherein the first frame further includes a second field, the second field indicating the target link.

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

37. The MLD according to claim 35, wherein the second field includes an identifier for the target link.

38. The MLD according to any one of claims 30 to 37, wherein the first frame further includes a third field, the third field indicating whether the first link is the target link, and the first link is a link used to transmit the first frame.

39. The MLD according to any one of claims 29 to 38, wherein the first frame is a reassociation request frame or an unassociation 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, the type field indicating that the first frame is used to reconfigure the link between the first MLD and the second MLD when the value of the type field is a first preset value, 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. 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, according to any one of claims 29 to 39.

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

42. 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, the query frame being used to negotiate a link transition between the first MLD and the second MLD, according to claim 40 or 41.

43. A multi-level disk (MLD) comprising a communication module and a processing module, The communication module is configured to receive a first frame from a first MLD, and the first frame is used to reconfigure the link between the first MLD and the second MLD. The processing module is configured to analyze the first frame, and is an MLD.

44. The first frame is used to reconfigure the link between the first MLD and the second MLD. The MLD according to claim 43, comprising indicating that the first frame establishes a target link between the first MLD and the second MLD.

45. The first frame is used to reconfigure the link between the first MLD and the second MLD. The MLD according to claim 43, comprising indicating that the first frame removes the target link from the link established between the first MLD and the second MLD.

46. The first frame is used to reconfigure the link between the first MLD and the second MLD. The MLD according to claim 43, wherein the first frame indicates a target link, and the target link is used for data transmission between the first MLD and the second MLD.

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

48. The first frame is used to reconfigure the link between the first MLD and the second MLD. When the first field indicates link removal, the first frame indicates removing the target link from the link established between the first MLD and the second MLD. When the first field indicates the addition of a link, the first frame indicates the establishment of 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 the link established between the first MLD and the second MLD to the target link. The MLD according to claim 47, including the following:

49. The MLD according to any one of claims 34 to 48, wherein the first frame further includes a second field, the second field indicating the target link.

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

51. The MLD according to claim 49, wherein the second field includes an identifier for the target link.

52. The MLD according to any one of claims 44 to 51, wherein the first frame further comprises a third field, the third field indicating whether the first link is the target link, and the first link is a link used to transmit the first frame.

53. The MLD according to any one of claims 43 to 52, wherein the first frame is a reassociation request frame or an unassociation 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, the type field indicating that the first frame is used to reconfigure the link between the first MLD and the second MLD when the value of the type field is a first preset value, and the first preset value is neither 0 nor 1.

54. The communication module is further configured to transmit 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. 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, according to any one of claims 43 to 53.

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

56. The MLD according to 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. MLD comprising a processor and a transceiver, wherein the processor is configured to perform processing operations according to any one of claims 1 to 28, and the transceiver is configured to perform communication operations according to any one of claims 1 to 28.

58. A computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and when the computer instructions are executed in the computer, the computer is enabled to perform the method according to any one of claims 1 to 28.

59. A computer program product wherein, when the computer program product is executed on a computer, the computer is enabled to perform the method described in any one of claims 1 to 28.

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

Images