RU2822824C1 - Method and apparatus for reconfiguring multichannel connections - Google Patents

Abstract

FIELD: communication technology.

SUBSTANCE: first multicast listener device (MLD) generates a transition control request frame to another basic service set (BSS), where the BSS request frame comprises a first field, which occupies one bit. First field either indicates a second MLD for disconnecting the communication channel over which the BSS request frame is transmitted from the first MLD, or indicates a second MLD for canceling the association with the first MLD, so that the second MLD disconnects all communication channels from the first MLD. First MLD transmits this BSS request frame to the second MLD.

EFFECT: high throughput of a multicast listener device.

19 cl, 26 dwg, 7 tbl

Description

Field of technology to which the invention relates

This application relates to the field of communications technology and, in particular, to a method and apparatus for reconfiguring multi-channel connections.

State of the art

To achieve the technical goals of exceptionally high throughput, the Institute of Electrical and Electronics Engineers (IEEE) IEEE 802.11be standard contains multi-link (ML) communications as one of its key technologies. A multi-link device (MLD) supporting ML communications is capable of transmitting and receiving over multiple communication channels. With this approach, the MLD device can use a wider bandwidth to transmit data to significantly improve throughput. A communication channel can be called a path in space along which an MLD device transmits data in a certain frequency range.

Today, one or more communication channels can be established between two MLD devices through an association procedure to enable communication between these devices. However, in some scenarios, the communication links established between two MLD devices may not meet the requirements for transferring data between the two MLD devices. There are no technical solutions in industry today that would solve this problem.

The essence of the invention

Embodiments of the present application provide a method and apparatus for multi-link reconfiguration that allows the communication channel between two MLD devices to be reconfigured.

According to a first aspect, there is provided a method for reconfiguring a multi-link connection, comprising: a first MLD device generating a first frame, where the first frame is used to reconfigure a communication channel between the first MLD device and the second MLD device; and the first MLD device transmits this first frame to the second MLD device. Based on the above technical solution, by transmitting the first frame to the second MLD device, the first MLD device can initiate a procedure for reconfiguring the communication channel between the first MLD device and the second MLD device to meet the data transmission requirements between the first MLD device and the second MLD device.

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

Optionally, the first frame may reuse an existing frame, for example, a reassociation request frame or a deassociation frame. It should be understood that the first frame reuses the reassociation request frame or deassociation frame so that major changes to the existing protocol are avoided, there is no need to redefine the information element to be included in the first frame, and the reserved value of the category field in the first frame is preserved. action frame.

Optionally, if the first frame reuses the reassociation request frame, after the first MLD device transmits the first frame to the second MLD device, the first MLD device and the second MLD device may continue to buffer the following information: enhanced distributed channel access function status ( enhanced distributed channel access (EDCA), block acknowledgment agreement, Sequence Number (SN), packet number (PN), duplicate detection cache, data queued for transmission, fragmentation and reassembly buffer, mode power management and sleep mode control of the wireless (radio) communication network. It should be understood that, unlike conventional technology whereby the device needs to erase the above information during the reassociation procedure, in the present embodiment, although the first frame reuses the reassociation request frame, the first MLD device and the second MLD device do not receive commands launch to erase the above information. Therefore, the first MLD device and the second MLD device do not need to renegotiate with each other to obtain the above information after changing the communication channel configuration, which reduces the overhead of negotiations regarding the above information.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame indicates that a target communication channel should be established between the first MLD device and a second MLD device. It should be understood that the data transmission capacity between the first MLD device and the second MLD device can be increased by adding one or more communication channels between these devices.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame indicates that the target communication channel should be excluded from the communication channel established between the first MLD device and the second MLD device. It should be understood that the corresponding power consumption can be reduced in the first MLD device and in the second MLD device by eliminating one or more communication channels between these devices.

In one exemplary embodiment, a procedure for using a first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame specifies a target communication channel, and the target communication channel is used to transmit data between the first MLD device and the second MLD device.

In one embodiment, the first frame contains a first field, the first field indicating a type of reconfiguration, such that the type of reconfiguration may be a link drop, a link add, or a link switch. Based on this embodiment, one type of first frame can implement several types of communication channel reconfiguration.

In one embodiment, the first frame may contain a multi-link element, the multi-link element contains a per-link profile, and the per-link profile contains a first field.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: when the first field indicates exclusion of the communication channel, the first frame indicates that the target communication channel should be excluded from the communication channel established between the first device MLD and a second MLD device; when the first field indicates adding a communication channel, the first frame indicates that a target communication channel should be established between the first MLD device and the second MLD device; or when the first field indicates a link switch, the first frame indicates that the link established between the first MLD device and the second MLD device should be switched to the target link.

It should be understood that a link switching operation may allow two MLD devices to switch from a poor quality link to a higher quality link for data transmission, thereby improving the quality of service when transmitting data between the two MLD devices.

In one embodiment, the first frame further includes a second field, and the second field indicates the target communication channel.

In one embodiment, the first frame may include a multi-channel element, the multi-channel element contains a profile for a communication channel, and the profile for a communication channel contains a second field.

In one embodiment, the second field contains a bitmap, the bitmap contains at least one bit, and each bit in the bitmap indicates whether the communication channel corresponding to that bit is a target communication channel.

In one embodiment, the second field contains the identifier of the target communication channel.

In one embodiment, the first frame further includes a third field, the third field indicating whether the first communication channel is a target communication channel, and the first communication channel is a communication channel used to transmit the first frame.

In one embodiment, the first frame may contain a multi-channel element, and this multi-channel element contains a third field.

In one embodiment, the first frame is a reassociation request frame or a deassociation 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 type field. This type field, the value of which is equal to the first preset value, indicates that the first frame is used to reconfigure the communication channel between the first MLD device and the second MLD device, and this first preset value is not equal to 0 or 1.

In one exemplary embodiment, the method further comprises: the first MLD device receives a request frame from the second MLD device, where the request frame is used to request switching of a communication channel between the first MLD device and the second MLD device; and the first MLD device transmits a response frame to the second MLD device, where the response frame indicates whether the handover between the first MLD device and the second MLD device is accepted for execution. Based on this configuration, before handoff, the two MLD devices negotiate this handoff so that the two MLD devices can determine a higher quality channel to handover. This ensures the quality of data transfer between the two MLD devices in question after the communication channel is switched.

In one embodiment, the request frame further specifies a recommended communication channel.

In one embodiment, before the first MLD device receives a request frame from the second MLD device, the method further comprises: the first MLD device transmits a question frame to the second MLD device, where the question frame is used to reach an agreement regarding switching the communication channel between the first an MLD device and a second MLD device. Based on such a configuration, the first MLD device may transmit a question frame to initiate negotiations regarding handover between the two MLD devices.

According to a second aspect, there is provided a method for reconfiguring a multi-link connection, comprising: A second MLD device receives a first frame from a first MLD device, where the first frame is used to reconfigure a communication channel between the first MLD device and a second MLD device; and the second MLD device parses this first frame.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame indicates that a target communication channel should be established between the first MLD device and a second MLD device.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame indicates that the target communication channel should be excluded from the communication channel established between the first MLD device and the second MLD device.

In one exemplary embodiment, a procedure for using a first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame designates a target communication channel, and the target communication channel is used to transmit data between the first MLD device and the second MLD device.

In one embodiment, the first frame contains a first field, the first field indicates a type of reconfiguration, and this type of reconfiguration may be a link drop, a link add, or a link switch.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: when the first field indicates exclusion of the communication channel, the first frame indicates that the target communication channel should be excluded from the communication channel established between the first device MLD and a second MLD device; when the first field indicates adding a communication channel, the first frame indicates that a target communication channel should be established between the first MLD device and the second MLD device; or when the first field indicates a link switch, the first frame indicates that the link established between the first MLD device and the second MLD device should be switched to the target link.

In one embodiment, the first frame further includes a second field, and this second field indicates the target communication channel.

In one embodiment, the second field contains a bitmap, the bitmap contains at least one bit, and each bit in the bitmap indicates whether the communication channel corresponding to that bit is a target communication channel.

In one embodiment, the second field contains the identifier of the target communication channel.

In one embodiment, the first frame further includes a third field, the third field indicating whether the first communication channel is a target communication channel, and the first communication channel is a communication channel used to transmit the first frame.

In one embodiment, the first frame is a reassociation request frame or a deassociation frame; this first frame contains a multi-channel element, this multi-channel element contains a multi-channel control field, and this multi-channel control field contains a type field. A type field whose value is equal to the first preset value indicates that the first frame is used to reconfigure the communication channel between the first MLD device and the second MLD device, and this first preset value is not 0 or 1.

In one exemplary embodiment, the method further comprises: the second MLD device transmits a request frame to the first MLD device, where the request frame is used to request switching of a communication channel between the first MLD device and the second MLD device; and the second MLD device receives a response frame from the first MLD device, where the response frame indicates whether the handover between the first MLD device and the second MLD device is accepted for execution.

In one embodiment, the request frame further specifies a recommended communication channel.

In one embodiment, before the second MLD device transmits a request frame to the first MLD device, the method further comprises: the second MLD device receives a question frame from the first MLD device, where the question frame is used to negotiate a handover between the first device MLD and a second MLD device.

According to a third aspect, an MLD device is provided including a processor module and a communication module. The processor module is configured to generate a first frame, where the first frame is used to reconfigure a communication channel between the first MLD device and the second MLD device. The communication module is configured to transmit the first frame to the second MLD device.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame indicates that a target communication channel should be established between the first MLD device and a second MLD device.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame indicates that the target communication channel should be excluded from the communication channel established between the first MLD device and the second MLD device.

In one exemplary embodiment, a procedure for using a first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame specifies a target communication channel, and the target communication channel is used to transmit data between the first MLD device and the second MLD device.

In one embodiment, the first frame contains a first field, the first field indicates a type of reconfiguration, and this type of reconfiguration may be a link drop, a link add, or a link switch.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: when the first field indicates exclusion of the communication channel, the first frame indicates that the target communication channel should be excluded from the communication channel established between the first device MLD and a second MLD device; when the first field indicates adding a communication channel, the first frame indicates that a target communication channel should be established between the first MLD device and the second MLD device; or when the first field indicates a link switch, the first frame indicates that the link established between the first MLD device and the second MLD device should be switched to the target link.

In one embodiment, the first frame further includes a second field, and this second field indicates the target communication channel.

In one embodiment, the second field contains a bitmap, the bitmap contains at least one bit, and each bit in the bitmap indicates whether the communication channel corresponding to that bit is a target communication channel.

In one embodiment, the second field contains the identifier of the target communication channel.

In one embodiment, the first frame further includes a third field, the third field indicates whether the first communication channel is a target communication channel, and the first communication channel is a communication channel used to communicate with the first frame.

In one embodiment, the first frame is a reassociation request frame or a deassociation frame; this first frame contains a multi-channel element, this multi-channel element contains a multi-channel control field, and this multi-channel control field contains a type field. A type field whose value is equal to the first preset value indicates that the first frame is used to reconfigure the communication channel between the first MLD device and the second MLD device, and this first preset value is not 0 or 1.

In one embodiment, the communication module is further configured to: receive a request frame from a second MLD device, where the request frame is used to request switching of a communication channel between the first MLD device and the second MLD device; and transmitting a response frame to the second MLD device, where the response frame indicates whether the handover between the first MLD device and the second MLD device has been accepted for execution.

In one embodiment, the request frame further specifies a recommended communication channel.

In one embodiment, the communication module is further configured to transmit a question frame to a second MLD device, where the question frame is used to negotiate a communication channel switch between the first MLD device and the second MLD device.

According to a fourth aspect, there is provided an MLD device comprising a processor module and a communication module. The communication module is configured to receive a first frame from a first MLD device, where the first frame is used to reconfigure a communication channel between the first MLD device and the second MLD device. The processor module is configured to parse the first frame.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame indicates that a target communication channel should be established between the first MLD device and a second MLD device.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame indicates that the target communication channel should be excluded from the communication channel established between the first MLD device and the second MLD device.

In one exemplary embodiment, a procedure for using a first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: the first frame specifies a target communication channel, and the target communication channel is used to transmit data between the first MLD device and the second MLD device.

In one embodiment, the first frame comprises a first field, the first field indicates a type of reconfiguration, and the type of reconfiguration comprises a link drop, a link add, or a link switch.

In one exemplary embodiment, a procedure for using the first frame to reconfigure a communication channel between a first MLD device and a second MLD device comprises: when the first field indicates exclusion of the communication channel, the first frame indicates that the target communication channel should be excluded from the communication channel established between the first device MLD and a second MLD device; when the first field indicates adding a communication channel, the first frame indicates that a target communication channel should be established between the first MLD device and the second MLD device; or when the first field indicates a link switch, the first frame indicates that the link established between the first MLD device and the second MLD device should be switched to the target link.

In one embodiment, the first frame further includes a second field, and this second field indicates the target communication channel.

In one embodiment, the second field contains a bitmap, the bitmap contains at least one bit, and each bit in the bitmap indicates whether the communication channel corresponding to that bit is a target communication channel.

In one embodiment, the second field contains the identifier of the target communication channel.

In one embodiment, the first frame further includes a third field, the third field indicating whether the first communication channel is a target communication channel, and the first communication channel is a communication channel used to transmit the first frame.

In one embodiment, the first frame is a reassociation request frame or a deassociation frame; this first frame contains a multi-channel element, this multi-channel element contains a multi-channel control field, and this multi-channel control field contains a type field. A type field whose value is equal to the first preset value indicates that the first frame is used to reconfigure the communication channel between the first MLD device and the second MLD device, and this first preset value is not 0 or 1.

In one embodiment, the communication module is further configured to: transmit a request frame to the first MLD device, where the request frame is used to request switching of a communication channel between the first MLD device and the second MLD device; and receiving a response frame from the first MLD device, where the response frame indicates whether the handover between the first MLD device and the second MLD device has been accepted for execution.

In one embodiment, the request frame further denotes a recommended communication channel.

In one embodiment, the communication module is further configured to receive a question frame from the first MLD device, where the question frame is used to negotiate a communication channel switch between the first MLD device and the second MLD device.

According to a fifth aspect, an MLD device comprising a processor and a transceiver is provided. The processor is configured to perform data processing operations for the corresponding method according to the first aspect or the second aspect, and the transceiver is configured to perform communication operations for the corresponding method according to the first aspect or the second aspect.

According to a sixth aspect, a computer-readable medium for storing information is provided. This computer-readable information storage medium stores instructions such that when a computer executes the instructions, the computer can implement the method according to any one of the embodiments of the first aspect or the second aspect.

According to a seventh aspect, a computer program product containing instructions is provided. When a computer executes the computer program product, such computer may implement the method according to any one of the embodiments of the first aspect or the second aspect.

According to an eighth aspect, an integrated circuit (chip) comprising a processor circuit and a transceiver pin is provided. The processor circuit is configured to perform data processing operations for the corresponding method according to the first aspect or the second aspect, and the transceiver contact is configured to perform communication operations for the corresponding method according to the first aspect or the second aspect.

It should be understood that any of the objects - an MLD device, an integrated circuit, a computer storage medium, or a computer program product - provided above is configured to implement the corresponding method provided above. Therefore, for information about the beneficial effects achievable by the MLD device, integrated circuit, computer storage medium or computer program product, refer to the beneficial effects of the corresponding method listed above. The details will again not be described here.

Brief description of drawings

Fig. 1 is a simplified diagram of a communication scenario between a multi-channel AP device and a multi-channel STA device according to an embodiment of the present application;

fig. 2(a) and FIG. 2(b) are simplified diagrams of the structures of a multi-channel device of APs and a multi-channel device of an STA communicating with each other;

fig. 3 is a simplified diagram of the frame structure of a multi-channel element according to one embodiment of the present application;

fig. 4 is a flow diagram of a method for reconfiguring a multi-channel connection according to an embodiment of the present application;

fig. 5 is a simplified diagram of another multi-channel element frame structure according to an embodiment of the present application;

fig. 6(a) is a simplified diagram of another multi-channel element frame structure according to an embodiment of the present application;

fig. 6(b) is a simplified diagram of another multi-channel element frame structure according to an embodiment of the present application;

fig. 7 is a simplified diagram of another multi-channel element frame structure according to an embodiment of the present application;

fig. 8 is a logic diagram of another method for reconfiguring a multi-link connection according to an embodiment of the present application;

fig. 9(a) is a simplified diagram of another multi-channel element frame structure according to an embodiment of the present application;

fig. 9(b) is a simplified diagram of another multi-channel element frame structure according to an embodiment of the present application;

fig. 10 is a simplified diagram of a BTM control procedure in related technology;

fig. 11(a) is a simplified frame structure diagram for a BTM control interrogative frame in a related technology;

fig. 11(b) is a simplified frame structure diagram for a neighbor reporting element in a related technology;

fig. 12 is a simplified diagram of the structure of a BTM control request frame in related technology;

fig. 13 is a simplified diagram of a BTM response frame structure in related technology;

fig. 14 is a logic diagram of another method for reconfiguring a multi-link connection according to an embodiment of the present application;

fig. 15 is a simplified frame structure diagram for a neighbor report element according to an embodiment of the present application;

fig. 16 is a simplified diagram of the structure of communication equipment according to one embodiment of the present application;

fig. 17 is a simplified diagram of the structure of communication equipment according to one embodiment of the present application;

fig. 18 is a flow diagram of a method for reconfiguring a multi-link connection according to an embodiment of the present application;

fig. 19 is a logic diagram of another method for reconfiguring a multi-link connection according to an embodiment of the present application;

fig. 20 is a logic diagram of another method for reconfiguring a multi-link connection according to an embodiment of the present application;

fig. 21 is a logic diagram of another method for reconfiguring a multi-link connection according to an embodiment of the present application; And

fig. 22 is a simplified frame structure diagram for a request mode field according to an embodiment of the present application.

Description of options

In the specification of this application, unless otherwise specified, the symbol "/" means "or". For example, A/B may represent A or B. The term “and/or” as used herein represents only an association relationship between associated objects and indicates that three relationships are possible. 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, the term “at least one” means one or more, and “several” means two or more. Terms such as “first” and “second” do not limit the number and sequence of execution, nor do the terms “first” and “second” indicate any specific distinction.

In this application, a word such as “example” or “for example” is used to provide an example, illustration or description. No alternative or design scheme described in this application as “example” or “for example” should be construed as being preferable to or having greater benefits than other alternatives or design scheme. More precisely, the use of the word "for example" or "example" or other similar word is intended to represent a related concept in a specific way.

The technical solutions proposed in this application can be applied to various communication systems, for example, to a system that uses the IEEE 802.11 standard. For example, the IEEE 802.11 family of standards includes, without limitation, 802.11be or any next-generation 802.11 standard. The technical solutions of the present application are applicable to the following scenarios: communication between an AP and an STA, communication between APs, communication between STAs and other similar scenarios.

STAs in this application may be various user terminals, user equipment, access equipment, subscriber stations, subscriber units, mobile stations, user agents, user devices or other devices having a radio communication function. User terminals may be a variety of hand-held devices, vehicle-mounted devices, wearable devices, computer devices having a radio capability, or other processing devices connected to a wireless (radio) modem, and may be a variety of user equipment. user equipment (UE), mobile station (MS), terminals, terminal devices, portable communications devices, hand-held devices, portable computing devices, entertainment devices, gaming devices or systems, and global system devices location devices, or any other suitable devices configured to communicate with the network via wireless (radio) links. Here, for ease of description, the devices listed above will be collectively referred to as stations or STAs.

An access point, AP, in this application is a hardware deployed in a radio network and providing a radio function to an STA associated with that access point AP. An AP may be used as a hub in a communications system and may be a communications device such as a base station, router, gateway, repeater, communications server, switch, or bridge. The base station may represent a macro base station, a micro base station, a relay station, or other similar entities in a variety of forms. Here, for ease of description, the devices listed above will be collectively referred to as access points, APs.

An extremely high throughput (EHT) device according to the IEEE 802.11 standard, in other words a “wireless fidelity” (Wi-Fi) device that supports multiple streams, multiple frequency bands (for example, 2.4 GHz, 5 GHz and 6 GHz), joint transmission of several channels in the same frequency range and other similar modes to increase peak throughput and reduce delay in service transmission. Multiple frequency bands or multiple channels may be collectively referred to as multiple communication channels.

A multi-channel device contains one or more affiliate stations. An affiliate station may be a logical station or a physical station. In embodiments of the present application, the statement "multi-channel device contains an affiliated station" may be briefly written as "multi-channel device contains a station."

An affiliate station can be an access point (AP) or a non-AP STA. For ease of description, in embodiments of the present application, a multi-channel device whose affiliate station is an AP may be referred to as a multi-channel AP, an MLD AP device, or a multi-channel AP device, and a multi-channel device whose affiliate station is an STA may be referred to as a multi-channel device. an STA, a multi-channel STA device, an STA MLD device, or a non-AP MLD device.

The multi-channel device can communicate in accordance with the 802.11 standard protocol. For example, the 802.11 protocol may be an 802.11ax protocol, an 802.11be protocol, or a next-generation protocol from the 802.11 family of standards. The embodiments of this application are not limited to this.

A multi-channel device can communicate with another device. In embodiments of the present application, this other device may or may not be a multi-channel device.

For example, FIG. 1 shows a simplified diagram of a communication scenario between a multi-channel AP device and multi-channel STAs. As shown in FIG. 1, one multi-channel AP device may be associated with multiple multi-channel STAs and single-channel STAs. For example, a multi-channel AP device 100 is associated with a multi-channel STA device 200, a multi-channel STA device 300, and an STA 400. It should be understood that multiple APs in a multi-channel AP device individually operate on multiple communication channels, multiple STAs in In a multi-channel device, STAs individually operate on multiple communication channels, and one STA in a multi-channel STA device is associated with one AP in a multi-channel device of APs on the operating communication channel of that STA. A single-channel STA is associated with an AP in a multi-channel AP device via the single-channel STA's operational communication channel.

The set of frequency bands in which a multi-channel device operates may include, but is not limited to, the sub-1 GHz band, the 2.4 GHz band, the 5 GHz band, the 6 GHz band, and the 60 GHz high-frequency band. In fig. 2(a) and FIG. 2(b) shows two simplified diagrams in which a multi-channel device communicates with another device over multiple communication channels in a local radio network.

In fig. 2(a) illustrates a scenario in which a multi-channel AP device 101 communicates with a multi-channel STA device 102. The multi-channel AP device 101 includes an affiliated AP 101-1 and an AP 101-2, the multi-channel STA device 102 contains an affiliated STA 102-1 and an affiliated STA 102-2, and the multi-channel AP device 101 and the multi-channel STA device 102 communicate with each other via both channels – communication channel 1 and communication channel 2.

In fig. 2(b) depicts a scenario in which the multi-channel AP device 101 communicates with the multi-channel STA device 102, the multi-channel STA device 102, and the STA 104. The multi-channel AP device 101 contains affiliated access points from AP 101-1 to AP 101-3, Multi-channel STA device 102 includes affiliated STA 102-1 and STA 102-2, and multi-channel STA device 103 includes affiliated STA 103-1, STA 103-2. The STA 104 station is a single-link device (SLD). The multi-channel AP device can communicate with the multi-channel STA device 102 on communication channel 1 and communication channel 3, communicate with the multi-channel STA device 103 on communication channel 2 and communication channel 3, and communicate with the STA 104 on communication channel 1 . In one example, STA 104 operates in the 2.4 GHz frequency range; the multi-channel STA station device 103 includes a station STA 103-1 and a station STA 103-2, where the station STA 103-1 operates in the 5 GHz frequency range and the STA 103-2 station operates in the 6 GHz frequency range; The multi-channel STA station device 102 includes a station STA 102-1 and a station STA 102-2, where STA 102-1 operates in the 2.4 GHz frequency range and STA 102-2 operates in the 6 GHz frequency range. The AP 101-1 operating in the 2.4 GHz frequency range in the multi-channel AP device can exchange uplink or downlink data with STA 104 and STA 102-2 in the multi-channel STA device 102 on communication channel 1. A 5 GHz AP 101-2 in a multi-channel AP device can communicate uplink or downlink data with a 5 GHz STA 103-1 in a multi-channel STA device 103 on link 2. . The 6 GHz AP 101-3 in the multi-channel AP 101 can exchange uplink or downlink data with the 6 GHz STA 102-2 in the multi-STA 102 on channel 3 communication, and can also exchange uplink or downlink data with the STA 103-2 in the multi-channel STA device on communication channel 3.

It should be noted that in FIG. 2(a) shows a multi-channel AP device supporting only two frequency bands, and FIG. 2(b) uses an example where the multi-channel AP device supports only three frequency bands (2.4 GHz, 5 GHz and 6 GHz), each frequency band corresponds to one communication channel, and the multi-channel AP device 101 can operate in one or more channels. communication – communication channel 1, communication channel 2 and communication channel 3. On the AP side or the STA side, reference to a communication channel here can also be understood as indicating a station operating on that communication channel. In an actual application, the multi-channel AP device and the multi-channel STA device may each support more or fewer frequency bands. In other words, the multichannel AP device and the multichannel STA device may each operate on more communication channels or on fewer communication channels. This is not limited in the embodiments of this application.

For example, a multi-channel device is equipment that has a radio communication function. This hardware may be a complete device or may be an integrated circuit (chip), processor system, or other similar object installed in the complete device. A device in which an integrated circuit (chip) or processor system is installed may be controlled by the integrated circuit (chip) or processor system to perform the methods and functions of embodiments of the present application.

A multi-channel device may support simultaneous transmit and receive (STR) data, or the multi-channel device may not support simultaneous transmit and receive (STR) data. Support for simultaneous transmission and reception of data means that while a multi-channel device is transmitting data on one communication channel, that multi-channel device can receive data on another communication channel. Lack of support for simultaneous transmission and reception of data means that while a multi-channel device is transmitting data on one communication channel, that multi-channel device cannot receive data on another communication channel.

For example, a non-AP MLD device may perform a multi-link establishment operation on one of the communication channels to simultaneously establish multiple communication channels and establish association with the AP MLD device. During the association process, the non-AP MLD device and the AP MLD device may exchange Multi-link Association Request/Response frames over a single communication channel. The communication link over which multi-link association request/response frames are exchanged may be called a transmitted link, and the other communication links may be called non-transmitted Links. It should be understood that the multi-channel association request/response may carry information about multiple communication channels that need to be established in order to simultaneously establish multiple communication channels between the non-AP MLD device and the AP MLD device.

For example, a non-AP MLD device transmits a multi-link association request frame on link 1, and this multi-link association request frame contains STA side information regarding link 1 and STA side information regarding link 2. It should be understood that communication channel 1 may be referred to as a transmitted communication channel, and communication channel 2 may be referred to as a non-transmitting communication channel. The MLD AP transmits a multi-link association response frame to the non-AP MLD device on link 1, and this multi-link association response frame contains AP-side information regarding link 1 and AP-side information regarding link 2. Thus, communication channel 1 and communication channel 2 are established between the non-AP MLD device and the AP MLD device. Thereafter, the non-AP MLD device and the AP MLD device can transmit data on communication channel 1 and communication channel 2.

In a communication protocol, a multi-channel element is defined to convey information regarding a non-AP MLD device in an existing association request frame. For example, as shown in FIG. 3, the information transmitted in a multi-link element is divided into two parts: MLD device level information and a Per-link profile. A link profile may also be called a per-STA profile. It should be understood that the profile for the communication channel is an option. In other words, a multi-channel element may contain no profile for a communication channel at all, or may contain one or more profiles for communication channels. For example, in FIG. 3 shows a multi-channel element having a profile for communication channel x and a profile for communication channel y.

The MLD device level information contains the following fields: a Multi-link control field and one or more other fields. For example, the one or more fields may be the following fields: element ID, length, element ID, and other similar fields.

The multi-channel control field contains the following fields: the type field, the MLD MAC address present field, and the reserved field.

The profile for a communication channel contains the following fields: subelement ID, length, and data.

The profile data field for a link contains one or more of the following fields: a Per-STA control field, one or more elements, and a non-inheritance element. The non-inherited element field is an option.

The control field for a station contains at least a communication channel identifier (ID). It should be understood that a non-AP MLD device can obtain link information (eg, link ID) corresponding to each link by receiving a probe response frame or a beacon frame.

In some scenarios, after two MLD devices become associated with one another, the established communication channels may not meet the requirements for transmitting data between the two MLD devices.

For example, when two MLD devices are initially associated, only one communication channel is established. However, there is a large amount of data that needs to be transferred between these two MLD devices, so that a single communication channel cannot satisfy the data transmission bandwidth requirements. Therefore, it is necessary to add a communication channel between these two MLD devices.

As another example, when two MLD devices are initially associated, multiple communication channels are established between them. However, there is relatively little data to transmit between these two MLD devices, so a single communication channel can satisfy the bandwidth requirements for transmitting this data. Therefore, the redundant communication path between these two MLD devices must be eliminated to reduce power consumption.

As another example, when two MLD devices are initially associated, a link 1 is established between them, but the communication quality on that link 1 is poor. Therefore, the two MLDs need to move from link 1 to link 2 to transmit data.

Currently, the industry has not developed a technical solution that allows changing the configuration of communication channels after establishing the association of MLD devices.

One embodiment of the present application provides a method for reconfiguring a multi-link connection to support reconfiguration of communication channels after an association has been established between two MLD devices. As shown in FIG. 4, the method contains the following steps.

S101. The first MLD device generates the first frame.

This first frame is used to reconfigure multiple communication channels between the first MLD device and the second MLD device.

It should be understood that before performing step S101, one or more communication channels have already been established between the first MLD device and the second MLD device through association.

In embodiments of the present application, the first frame may be a newly defined frame or a reused existing frame (eg, a reassociation request frame or a deassociation frame). It's not limited.

Optionally, the first frame can use any one of the following configurations.

Configuration 1-1: The first frame indicates that the target communication channel should be established.

In particular, the first frame indicates that a target communication channel should be established between the first MLD device and the second MLD device. In other words, the target communication channel is a communication channel that has not yet been established at this time between the first MLD device and the second MLD device.

For example, a communication channel 1 and a communication channel 2 were established between a first MLD device and a second MLD device during an association process. The first frame indicates that a communication channel 3 should be established, so that this communication channel 3 can be further established between the first MLD device and the second MLD device. Then, communication channel 1, communication channel 2 and communication channel 3 can be used to transmit data between the first MLD device and the second MLD device.

In this embodiment of the present application, the subject two MLDs can transmit data on an established communication channel, but cannot transmit data on an unestablished communication channel. The two MLD devices may exchange some control frames (such as association request/response frames) over an unestablished communication channel to establish a communication channel.

Configuration 1-2: The first frame indicates that the target communication channel should be excluded.

In particular, the first frame indicates that the target communication channel should be excluded from the communication channel established between the first MLD device and the second MLD device. This target communication channel is a communication channel currently established between the first MLD device and the second MLD device.

For example, a communication channel 1 and a communication channel 2 were established between a first MLD device and a second MLD device during an association process. The first frame indicates that link 2 should be eliminated. After the first MLD device and the second MLD device exclude communication channel 2, this communication channel 2 becomes an unestablished communication channel between the first MLD device and the second MLD device. The first MLD device and the second MLD device can only use communication channel 1 to transmit data, but cannot use communication channel 2 to transmit data.

It should be understood that, based on the 1-1 configuration and the 1-2 configuration, the function of the first frame may be associated with the type of the first frame. Therefore, the second MLD device can determine the function of the first frame based on the type of the first frame. For example, the first frame in configuration 1-1 is a reassociation request frame. Upon receiving the reassociation request frame used to reconfigure the multi-link connection, the second MLD device may determine that the reassociation request frame is used to establish the target communication channel. Alternatively, the first frame in configuration 1-2 is a deassociation frame. Upon receiving the deassociation frame used to reconfigure the multi-link connection, the second MLD device may determine that the deassociation frame is used to disable the target communication channel.

Configuration 1-3: The first frame indicates the target communication channel.

In other words, the first frame indicates a target communication channel for data transmission between the first MLD device and the second MLD device.

The target communication channel may be used to transmit data between the first MLD device and the second MLD device. This target communication channel is a communication channel maintained between the first MLD device and the second MLD device. For example, the target communication channel may be an unestablished communication channel between a first MLD device and a second MLD device. Alternatively, the target communication channel may also be a communication channel that is currently already established between the first MLD device and the second MLD device.

For example, communication channel 1 and communication channel 2 have already been established between the first MLD device and the second MLD device during the association process. The first frame indicates communication channel 2, communication channel 3 and communication channel 4, so that communication channel 1 is excluded, and communication channel 3 and communication channel 4 are established between the first MLD device and the second MLD device. With this approach, the first MLD device and the second MLD device can use communication channel 2, communication channel 3 and communication channel 4 to transmit data, and cannot use communication channel 1 to transmit data.

It should be understood that the idea of configuration 1-3 is as follows: The first frame indicates a communication channel (in other words, a target communication channel) that is ultimately to be established between the first MLD device and the second MLD device, such that the first MLD device and the second The MLDs may determine a reconfiguration operation (eg, dropping a link and/or adding a link) to actually perform based on the currently established link and the link that is ultimately to be established.

Configuration 1-4: The first frame contains a first field, this first field indicates a type of reconfiguration, and this type of reconfiguration may be a link drop, a link add, or a link switch.

In embodiments of the present application, link deletion may also be referred to as link release, and is used to configure a link that has been established between two devices as an unestablished link. Adding a communication channel can also be called creating a communication channel, and it is used to configure an unestablished communication channel between two devices as an established communication channel. Communication channel switching can also be called channel hopping and is used to eliminate one communication channel established between two devices and establish another communication channel to switch to that other communication channel.

Optionally, based on the configuration 1-4, the procedure for using the first frame to reconfigure multiple communication channels between the first MLD device and the second MLD device contains the following cases.

Case 1: When the first field indicates a link exclusion, the first frame indicates that the target link should be excluded.

Case 2: When the first field indicates adding a link, the first frame indicates that the target link should be established.

Case 3: When the first field indicates a link switch, the first frame indicates that the link established between the first MLD device and the second MLD device should be switched to the target link.

For example, communication channel 1 and communication channel 2 have already been established between the first MLD device and the second MLD device during the association process. A first field included in the first frame indicates a communication channel switch, and this first field indicates that a communication channel 2 established between the first MLD device and the second MLD device should be switched to a communication channel 3. In this approach, communication channel 2 is eliminated, and communication channel 3 is established between the first MLD device and the second MLD device. The first MLD device and the second MLD device can communicate on communication channel 1 and communication channel 3, but not on communication channel 2.

For example, as shown in FIG. 5, the first frame may comprise a multi-channel element, the multi-channel element contains a profile for a communication channel, and the profile for a communication channel contains a first field.

For example, the first field could have a different name, such as an action field. It doesn't stop here.

It should be understood that, unlike the configurations from configuration 1-1 to configuration 1-3, the first frame in configuration 1-4 can be used to flexibly reconfigure the communication channel between the first MLD device and the second MLD device.

The above configurations from configuration 1-1 to configuration 1-4 are merely examples, and specific embodiments of the first frame are not limited. It should be understood that the configuration actually used for the first frame may be specified in the 802.11 protocol.

Optionally, the first frame may further include a second field, and this second field indicates the target communication channel.

Optionally, the second field can be used in any one of the following configurations.

Configuration 2-1: The second field contains the target communication channel ID.

Configuration 2-2: The second field contains a bitmap, this bitmap contains at least one bit, and each bit in the bitmap indicates whether the communication channel corresponding to this bit is the target communication channel.

For example, if the value of any bit in the bitmap is 1, it means that the communication channel corresponding to that bit is the target communication channel; or if the value of any bit in the bitmap is not 1, it means that the link corresponding to that bit is not the target link.

As another example, if the value of any bit in the bitmap is 0, it means that the communication channel corresponding to that bit is the target communication channel; or if the value of any bit in the bitmap is 1, it means that the communication channel corresponding to that bit is not the target communication channel.

For example, as shown in FIG. 6(a), the first frame may contain a multi-channel element, this multi-channel element contains a profile for a communication channel, and this profile for a communication channel contains a second field.

For example, as shown in FIG. 6(b), the first frame may contain a multi-channel element, and this multi-channel element contains a second field.

For example, the second field may have a different name, such as the target link set field. It doesn't stop here.

The following describes specific embodiments of the second field with reference to various embodiments of the application.

Option 1: The second field specifically indicates the target communication channel from the set of all communication channels supported by the first MLD device or from the set of all communication channels supported by the second MLD device.

Optionally, based on Option 1, if the second field contains a bitmap, the number of bits in that bitmap can be the same as the number of communication channels supported by the first MLD device, such that the bits in the bitmap are in a one-to-one correspondence with the channels communications supported by the first MLD device. Alternatively, the number of bits in the bitmap may be the same as the number of communication channels supported by the second MLD device, such that the bits in the bitmap are in a one-to-one correspondence with the communication channels supported by the second MLD device.

Option 2: The second field specifically indicates the target communication channel from a plurality of one or more second communication channels. These second communication channels are communication channels other than the first communication channel from among all communication channels supported by the first MLD device. The first communication channel is the communication channel used to transmit the first frame.

Optionally, based on Option 2, if the second field contains a bitmap, the number of bits in that bitmap can be the same as the number of second communication channels. Therefore, the bits in this bitmap are in a one-to-one correspondence with the second communication channels.

It should be understood that based on Option 2, the second field does not indicate whether the first communication channel is the target communication channel.

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

For example, as shown in FIG. 7, the first frame may contain a multi-channel element, and the MLD device level information in this multi-channel element contains a third field.

Optionally, when the second field uses Option 2, the first frame may implicitly indicate whether the link is the target link.

For example, if the first frame is used to add a target link, and the first link is an unestablished link between a first MLD device and a second MLD device, that first link may be considered the default target link.

As another example, if the first frame is used to exclude a target link, and the first link is a link established between a first MLD device and a second MLD device, the first link may be considered the default target link.

As another example, the first frame denotes a target communication channel, and the first communication channel may be considered the default target communication channel.

As an option, when the first frame reuses the reassociation request frame, the structure of the first frame should be referred to in Table 1.

Table 1

No. Information 1 Capability information 2 Listening interval 3 Current AP address (current AP address) 4 Service Set Identifier (SSID) 5 Support rates and BSS membership selectors 6 Extended supported rates and BSS membership selectors 7 Power capability 8 Supported channels ... ...

It should be understood that Table 1 shows only some information elements, and that the first frame may additionally contain other information elements. It doesn't stop here.

As an option, when the first frame reuses the deassociation frame, the structure of the first frame should be referred to in Table 2.

table 2

No. Information 1 Reason code ... ... Penultimate Vendor-specific information elements Last Control message integrity code element

It should be understood that Table 2 shows only some information elements, and that the first frame may additionally contain other information elements.

Optionally, when the first frame reuses a reassociation request frame or a deassociation frame, the first frame may contain a multi-channel element. In addition, the first frame may be different from an existing reassociation request frame or deassociation frame using a type field in the multi-channel control field in the multi-channel element.

For example, a type field whose value is equal to the first predefined value indicates that the first frame is used to reconfigure the communication channel between the first MLD device and the second MLD device. This first preset value is not 0 or 1. For example, the first preset value may be 2.

For example, information about the type field in embodiments of this application is shown in Table 3.

Table 3

Type field size Multichannel element variant name (variant name) 0 Basic 1 Probe request 2 Multi-link reconfiguration (ML reconfiguration) To be determined, TBD Reserved

It may be understood that in embodiments of the present application, a new multi-channel element variant name is defined using a reserved value (eg, 2) of an existing type field. Therefore, the device can determine that a frame using the multi-channel element variant name is used to reconfigure the multi-channel connection.

It should be understood that, rather than the first frame being a new type of action frame, this first frame reuses a reassociation request frame or a deassociation frame, which helps avoid unnecessary changes to the existing protocol. In addition, the information to be conveyed in the first frame does not need to be redefined, further saving the reserved value of the category field in the action frame.

S102: The first MLD device transmits the first frame to the second MLD device. Accordingly, the second MLD device receives the first frame from the first MLD device.

S103: The second MLD parses the first frame.

Based on the embodiment shown in FIG. 4, the first MLD device transmits the first frame to the second MLD device to trigger reconfiguration of the communication channel between the first MLD device and the second MLD device to meet the communication requirements between the two MLD devices and ensure normal communication between the two MLD devices.

Currently, the peer device participating in the reassociation of the device in question and the peer device participating in the initial association of the device in question may not be the same device. For example, device 1 is associated with device 2 when initially associated and associated with device 3 when reassociated. Therefore, some information stored in the device in question is not applicable for communication with the peer device participating in the reassociation. Therefore, according to the 802.11 protocol, during the reassociation process, the device in question erases some information, such as enhanced distributed channel access (EDCA) status, block handshaking protocol, Sequence Number (SN), packet number (PN), cache for duplicate detection, data queued for transmission, buffer for fragmentation and reassembly, power management mode and sleep mode for wireless (radio) network management. The device in question then renegotiates with the peer device participating in the reassociation to obtain this information.

Unlike the existing reassociation procedure, where the first frame reuses the reassociation request frame, the first MLD device and the second MLD device may not erase the above information to avoid transaction costs incurred by subsequent negotiations to obtain this information. In other words, after the first MLD device transmits the first frame to the second MLD device, the first MLD device and the second MLD device may continue to buffer the following enhanced distributed channel access function status information, block handshaking protocol, sequence number, packet number, cache for detection of duplicates, data queued for transmission, buffer for fragmentation and reassembly, power management mode, sleep mode of wireless (radio) communication network management and other similar information.

Optionally, based on the embodiment shown in FIG. 4, the multi-link connection reconfiguration method may further comprise step S104 after step S103 in the embodiment shown in FIG. 8.

S104: The second MLD device transmits the second frame to the first MLD device. Accordingly, the first MLD device receives a second frame from the second MLD device.

The second frame is used to respond to the first frame.

Optionally, when the first frame reuses the deassociation frame, the second frame may be an acknowledgment (ACK) frame.

Optionally, when the first frame is a newly defined frame, the second frame can also be a newly defined frame. The second frame may indicate whether reconfiguration of the communication channel between the first MLD device and the second MLD device should be initiated.

Optionally, when the first frame reuses the reassociation request frame, the second frame may reuse the reassociation response frame. The second frame may indicate whether reconfiguration of the communication channel between the first MLD device and the second MLD device should be initiated.

For example, when the second frame reuses the reassociation response frame, refer to Table 4 for information about the structure of the second frame.

Table 4

No. Information 1 Capability information 2 Status code 3 Association Identifier (AID) 4 Support rates and BSS membership selectors 5 Extended supported rates and BSS membership selectors 6 EDCA Parameter Set ... ...

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

For example, for a specific configuration, the status code is shown in Table 5.

Table 5

Status code meaning Name Meaning 0 Success Success 1 Rejected, reason for rejection not specified Unspecified failure 2 Cancellation of the establishment of a tunnel direct communication channel, an alternative is proposed. Establishment of a tunnel forward link has been cancelled, but an alternative schedule has been proposed. ... ... ...

It should be understood that the words "rejection reason not specified" means that the peer device refused to perform the reconfiguration operation requested by the first frame, but did not provide a reason for such refusal.

In one embodiment, the second frame may contain only one status code, and this status code is for all target communication channels.

For example, the first frame may indicate that link 1 and link 2 should be added, and the status code in the second frame indicates success. In such a case, a communication channel 1 and a communication channel 2 are established between the first MLD device and the second MLD device.

As another example, the first frame may indicate that link 1 and link 2 should be added, and the status code in the second frame indicates a rejection. In such a case, a communication channel 1 and a communication channel 2 are not established between the first MLD device and the second MLD device.

In another possible configuration, the second frame may contain one or more status codes. One status code corresponds to one target link, and this status code indicates the reconfiguration status of the corresponding target link.

For example, the first frame may indicate that link 1 and link 2 should be added, the status code corresponding to link 1 in the second frame indicates success, and the status code corresponding to link 2 in the second frame indicates failure. In such a case, communication channel 1 is established between the first MLD device and the second MLD device, but communication channel 2 is not established.

As another example, the first frame may indicate that communication channel 1 and communication channel 2 should be eliminated, the status code corresponding to communication channel 1 in the second frame indicates success, and the status code corresponding to communication channel 2 in the second frame indicates failure ( deviation). In such a case, communication channel 1 is eliminated between the first MLD device and the second MLD device, but communication channel 2 is not eliminated.

Optionally, for a target communication channel other than the first communication channel, a status code corresponding to that target communication channel may be located in a profile for the communication channel corresponding to that target communication channel. For example, as shown in FIG. 9(a), the second frame may contain a multi-channel element that includes a profile for a communication channel, this profile for a communication channel contains a control field for the STA, and this control field for the STA contains a status code.

Optionally, when the first communication channel is a target communication channel, the status code corresponding to that target communication channel may be a fixed field included in the frame body, or may be located in MLD device level information in a multi-channel element. For example, as shown in FIG. 9(b), the second frame may include a multi-channel element, and the multi-channel element may include a status code corresponding to the first communication channel.

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

Optionally, when the second frame reuses the reassociation response frame, the second frame may be different from the existing reassociation response frame by using a type field in the multilink connection control field in the multilink element. For example, a type field whose value is equal to the first predefined value indicates that the first frame is used to reconfigure the communication channel between the first MLD device and the second MLD device. This first preset value is not 0 or 1. For example, the first preset value may be 2.

According to the embodiment shown in FIG. 8, the second MLD device transmits a second frame to the first MLD device to allow the first MLD device to understand how to reconfigure the communication channel between the first MLD device and the second MLD device.

Currently, the STA and its affiliated AP can negotiate before moving to another BSS based on the BTM control procedure, so that the STA can move to a better BSS. For example, as shown in FIG. 10, the BTM control procedure may comprise the following steps.

When an STA detects that the link quality is poor, or for some other reason, the STA may transmit a BSS transition management (BTM) query frame to the STA's affiliated AP. . It should be understood that the step of transmitting the interrogative BTM management frame is optional. Upon receipt of a BTM control question sent by an STA, the designated AP may respond with an acknowledgment (ACK) frame.

When an AP wants an STA to transition to another BSS, the AP may send a BTM Control Request frame to the STA. After receiving this BTM control request frame, the STA may respond with an acknowledgment (ACK) frame.

The STA may transmit a BTM control response frame to the AP to indicate that it accepts or rejects the changeover request to another BSS. After receiving a BTM control response frame, the AP may respond with an acknowledgment (ACK) frame.

For example, as shown in FIG. 11(a), the BTM management question frame may contain the following fields: category, WNM action, dialogue token, BSS transition query reason, list of candidates for transition to another BSS set (BSS transition candidate list). A candidate list for moving to another BSS set is an option.

The BSS changeover question reason field indicates the reason for transmitting the BTM management question frame. For example, the structure of the reason field for a question about moving to another BSS set in the corresponding technology is shown in Table 6.

Table 6

The value of the reason field for a question about moving to another BSS set Description 0 Unspecified 1 Excessive packet loss rate or poor link quality 2 Too much delay ... ...

The candidate list field for moving to another BSS contains one or more neighbor report elements.

For example, as shown in FIG. 11(b), the neighbor report element contains the following elements: element ID, length, BSS set identifier (BSSID), BSSID information (info), operating class (operating class), channel number (channel number), physical layer type (PHY type), and optional subelement.

The BSSID field indicates the BSSID reported to the neighboring AP. The BSSID information field indicates corresponding information about the reported BSSID. The operation class field and the channel number field indicate the channel to which the reported BSSID belongs. The PHY Type field indicates the physical layer type of the AP corresponding to the reported BSSID.

Optionally, the BSSID information field may contain 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) located at the same location AP (co-located AP), and unsolicited probe response active, member of extended service set with 2.4 /5 GHz co-located AP), on-channel tunneling (OCT), supported with reporting AP, co-located with 6 GHz AP), and a reserved field.

For example, as shown in FIG. 12, a BTM management request frame may contain the following fields: category, radio network management action, dialog token, request mode, disassociation timer, validity interval, BSS termination duration duration), session information (session info URL) and a list of candidates to move to another BSS. A candidate list for moving to another BSS set is an option.

The validity interval field indicates the number of beacon intervals in which the list of candidates for transition to another BSS is valid.

The deassociation timer field indicates the point in time after which the AP transmits a deassociation frame.

The request mode field indicates the specific request mode. This request mode field may contain the following fields: preferred candidate list included, abridged, disassociation imminent, BSS termination included, extended service set unassociation imminent (extended service set, ESS) (ESS disassociation imminent) and reserved bits. Three bits are reserved.

The "preferred candidate list included" field indicates whether the preferred candidate list is transmitted.

The abbreviation field is used as follows: The abbreviation field is set to 0 if the affiliate AP does not recommend or prohibit the STA from switching to a BSS that is not in the preferred candidate list. The abbreviation field is set to 1 if the associated AP sets a preference value to 0 for a BSS that is not in the candidate preference list.

The deassociation imminent field is used as follows: When this deassociation imminent field is set to 1, it indicates that the AP in question transmits a deassociation frame to deassociate with the STA; when this deassociation imminent field is set to 0, it indicates that the AP in question does not transmit a deassociation frame to deassociate with the STA.

The BSS Set Completion Enabled field indicates whether the BSS Set will be completed.

The ESS Set Deassociation Imminent field indicates whether the STA will be deassociated from the entire ESS Set.

For example, as shown in FIG. 13, the BTM control response frame may contain the following fields: category, radio network control action, dialog token, BTM control status code, BSS termination delay, target BSSID, and candidate list. to move to another BSS set. The target BSSID and candidate list for transition to another BSS are options. Currently, in the corresponding technology, when the value of the BTM control status code is 0, the BTM control response frame contains a target BSSID field.

The BTM management status code indicates whether a request to move to another BSS has been accepted for execution. The BSS Set Completion Delay indicates the length of time from the current time until the BSS Set is completed.

For example, the details of the BTM management status code are given in Table 7.

Table 7

BTM Management Status Code Meaning Description 0 Accepted for execution 1 Rejected for unspecified reason 2 Rejected due to insufficient beacon frame or probe response frame received from neighboring candidates 3 Rejected due to lack of available opportunities from adjacent candidates ... ...

According to the current BTM control procedure, before switching the communication channel between two MLD devices, the two MLD devices may also negotiate a communication channel switch, so that the two MLD devices can switch from the currently established communication channel to the channel higher quality communications for communication. In light of this, one embodiment of the present application proposes a method for reconfiguring a multi-channel connection. As shown in FIG. 14, the method contains the following steps.

S201 (optional): The first MLD device transmits a question frame to the second MLD device. Accordingly, the second MLD device receives this question frame from the first MLD device.

In one embodiment, the question frame may be an existing BTM management question frame. In other words, the first MLD device does not determine whether to negotiate a handoff or negotiate a transition to another BSS. Instead, the second MLD determines, according to the actual situation, whether to negotiate a handover or negotiate a transition to another BSS.

In another possible configuration, the first MLD device may determine that a handover should be negotiated. Therefore, a question frame is used to negotiate a handover between the first MLD device and the second MLD device.

Based on this configuration, the question frame can be a newly defined frame. Alternatively, the question frame may reuse an existing BTM control question frame.

Optionally, the question frame may contain one or more neighbor report elements. It should be understood that each neighbor report element corresponds to one AP adjacent to the first MLD device.

In some embodiments, when an AP adjacent to the first MLD device is affiliated with the MLD AP device, the neighbor report element may comprise a basic multi-channel element, and the basic multi-channel element may include a MAC address, the number of supported communication channels, capability information, and other similar information regarding the MLD AP with which the AP adjacent to the first MLD is affiliated.

As an option, the basic multi-channel element in the neighbor reporting element may not contain a profile for the communication channel to reduce signaling overhead.

Optionally, when an interrogative frame reuses an existing BTM control interrogative frame, the interrogative frame may contain a multi-channel element, and for this interrogative frame it can be determined, based on the type field in the multi-channel control field in the multi-channel element, that this interrogative frame is used for negotiations (agreement) on switching the communication channel. For example, a type field whose value is equal to the second predetermined value indicates that the interrogative frame is used to negotiate a handover between the first MLD device and the second MLD device. The second preset value is not 0 or 1. Optionally, the second preset value can be the same as the first one above. It doesn't stop here.

Optionally, when a question frame reuses an existing BTM control question frame, one or more values may be newly defined for the switch question reason field in the question frame to indicate the reason for switching the communication channel, for example, a high frame loss rate on the communication channel , poor quality of the communication channel or detection of a higher quality channel.

Optionally, the question frame may further contain a communication channel identifier or a communication channel bitmap that indicates a communication channel with a high frame loss rate.

Optionally, after receiving the question frame, the second MLD device may transmit an acknowledgment (ACK) frame to the first MLD device.

S202: The second MLD device transmits a request frame to the first MLD device. Accordingly, the first MLD device receives a request frame from the second MLD device.

The request frame is used to request a handoff between the first MLD device and the second MLD device.

Optionally, a request frame can be used to indicate the recommended communication channel. This recommended communication channel may also be called a proposed communication channel, a candidate communication channel, or some other name. It doesn't stop here.

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

Optionally, when a request frame reuses an existing BTM management request frame, a request mode field in that request frame may include a fourth field, and this fourth field may indicate a new request mode. This new request mode may be referred to as a link switch request mode, a link deletion mode, or a link layer deassociation mode. For example, the fourth field may use a reserved bit in the request mode field in an existing BTM management frame. For example, the fourth field may occupy one bit. For example, FIG. 22 shows a frame structure for a request mode field in a request frame. The fourth field may be a link exclusion field in FIG. 22.

Optionally, the request frame may include a multi-channel element, and the request frame may determine, based on a type field in the multi-channel control field in the multi-channel element, that the request frame is used for negotiating a handoff. For example, a type field whose value is equal to the second predetermined value indicates that the request frame is used to negotiate a handover between the first MLD device and the second MLD device. The second preset value is not 0 or 1. Optionally, the second preset value may be the same as the above first preset value. It doesn't stop here.

As an option, if the request frame is used for link deletion negotiations, the value of the Preferred Candidate List Included field in the request frame shall be set to 0 to indicate that the request frame does not contain a list of preferred BSS set switch candidates. .

Optionally, the request frame may contain a switch candidate list field, and the switch candidate list field may contain one or more neighbor report elements. Each neighbor report element corresponds to one AP adjacent to the second MLD.

As shown in FIG. 15, a fifth field may be added to the BSSID information field in the neighbor report element. This fifth field indicates the ID of the MLD to which the BSS corresponding to the communication channel for transmitting the request frame belongs. In other words, the fifth field indicates that the device transmitting the request frame is an MLD device. Therefore, upon receiving the request frame, the first MLD device may preferably consider performing a handoff with the second MLD device.

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

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

In some embodiments, when an AP adjacent to a second MLD device is affiliated with the MLD AP device, the neighbor report element may comprise a basic multi-channel element, and the basic multi-channel element may include the MAC address of the MLD device, the number of supported communication channels, information about capabilities and other similar characteristics of the AP MLD device with which the AP adjacent to the second MLD device is affiliated.

As an option, the basic multi-channel element in the neighbor reporting element may not contain a profile for the communication channel to reduce signaling overhead.

Optionally, after receiving the request frame, the first MLD device may transmit an acknowledgment (ACK) frame to the second MLD device.

S203: The first MLD device transmits a response frame to the second MLD device. Accordingly, the second MLD device receives a response frame from the first MLD device.

The response frame indicates whether a handover between the first MLD device and the second MLD device should be executed.

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

Optionally, when a response frame reuses an existing BTM control response frame, the BTM control status code in that response frame may have one or more newly defined values to indicate the result of the link switch, e.g., link switch accepted or channel switch connection rejected.

Optionally, if the response frame indicates an accepted handoff or link exception, for example, the value of the status code for BTM management in the response frame is not 0, the response frame does not contain a target BSSID field or a neighbor report element. If the response frame indicates that a transition to another BSS has been received, eg, the status code value for BTM management in that response frame is 0, the response frame may further include a target BSSID field.

In some embodiments, if the first MLD device chooses to establish a connection with an AP that supports only one communication channel, the target BSSID field may contain a BSSID corresponding to that AP. Alternatively, if the first MLD device chooses to establish a connection with the MLD AP, the target BSSID field may contain the media access control (MAC) address of the MLD device associated with the MLD AP.

Optionally, the response frame may contain one or more neighbor report elements. It should be understood that each neighbor report element corresponds to one AP adjacent to the first MLD device.

In some embodiments, when an AP adjacent to the first MLD device is affiliated with the MLD AP device, the neighbor report element may comprise a basic multi-channel element, and the basic multi-channel element may include the MAC address of the MLD device, the number of supported communication channels, information about capabilities and other similar information regarding the AP MLD device with which the AP adjacent to the first MLD device is affiliated.

As an option, the basic multi-channel element in the neighbor reporting element may not contain a profile for the communication channel to reduce signaling overhead.

Optionally, after receiving the response frame, the second MLD device may transmit an acknowledgment (ACK) frame to the first MLD device.

As shown in FIG. 14, before performing a handoff, the first MLD device and the second MLD device may agree to determine a communication channel with a higher communication quality. Therefore, after switching the communication channel between the first MLD device and the second MLD device, communication can be carried out on a higher quality communication channel, thereby ensuring proper communication between the first MLD device and the second MLD device.

Currently, multiple stations can be configured for an MLD device to support data transmission over multiple communication channels. However, in some cases the MLD device may be required to exclude a station. For example, when the volume of traffic through an MLD device is relatively small, that MLD device eliminates one or more stations, which helps reduce the power consumed by that MLD device. However, in conventional technology there are no corresponding technical solutions.

In light of this, embodiments of the present application provide the technical solutions shown in FIG. 18, fig. 19 and fig. 20, to exclude stations in the MLD device.

As shown in FIG. 18, one embodiment of the present application proposes a method for reconfiguring a multi-link connection. The method contains the following steps.

S301: The first MLD device transmits the third frame on the target communication channel in broadcast mode.

For the first MLD device, the third frame indicates that the first MLD device should exclude a target station, where the target station is a station affiliated with the first MLD device and operating on the target communication channel.

For example, the first MLD device contains AP 1, AP 2, and AP 3. AP 1 operates on link 1, AP 2 operates on link 2, and AP 3 operates on link 3. When the first MLD device needs to exclude AP 1, the first MLD device transmits a third frame on communication channel 1 in broadcast mode. When the first MLD device needs to exclude AP 2, the first MLD device transmits a third frame on communication channel 2 in broadcast mode. When the first MLD device needs to exclude AP 3, the first MLD device transmits a third frame on communication channel 3 in broadcast mode.

In one embodiment, the third frame may reuse an existing frame to provide backward compatibility, in other words, to ensure that a conventional station supporting an earlier version of the protocol can parse the third frame. For example, the third frame may reuse the BTM control request frame.

Optionally, if the third frame is a BTM control request frame, and the third frame indicates that the first MLD device should exclude the target station, a specific implementation may be as follows: The BTM control request frame contains a sixth field having a third preset value.

A sixth field having a third predetermined value may indicate to an MLD device that has received a BTM control request frame that it should disconnect the target communication link from the first MLD device. The sixth field, having a fourth preset value, may indicate to an MLD device that has received a BTM control request frame that it should disassociate from the first MLD device (in other words, the MLD device that has received a BTM control request frame disassociates all communication channels from the first device MLD).

Optionally, the sixth field may occupy one or more reserved bits in the existing BTM control 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.

In another possible configuration, the third frame may be a newly defined control frame, such as a link removal request frame.

S302: The receiving end device receives the third frame on the target communication channel.

After receiving the third frame, the device at the receiving end may parse the third frame and further perform a corresponding operation according to the third frame.

For example, the receiving end device is a second MLD device. After receiving the third frame, the second MLD device must discard the target communication channel leading to the first MLD device.

For example, the device at the receiving end is a regular station (in other words, a single-channel device). When the third frame can reuse an existing frame, the single-channel device prepares to perform a transition to another BSS after receiving the third frame.

Optionally, if the third frame is a newly defined control frame, the first MLD may optionally transmit a BTM control request frame on the target link to instruct the conventional station and the MLD that did not receive the third frame to move to another set of BSSs. .

Optionally, the first MLD device may optionally transmit a fourth frame, where the fourth frame indicates a point in time at which the target station should be excluded.

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

Optionally, if the fourth frame reuses the beacon frame, a seventh field may be added to the beacon frame, and the seventh field indicates a point in time at which the target station should be excluded. Specifically, the seventh field specifies the number of target beacon transmission times (TBTT) after which the target station should be excluded. Optionally, the seventh field may be located in a profile sub-element (per-STA) for the target station corresponding to the basic multi-link element transmitted in the beacon frame. The seventh field may have a different name, for example, the delete timer field. It doesn't stop here.

Optionally, the beacon frame may further include an eighth field, and the eighth field indicates whether the beacon frame contains the seventh field. Optionally, the eighth field may be located in a profile sub-element (per-STA) for the target station corresponding to the basic multi-link element transmitted in the beacon frame. This eighth field may additionally have another name, the delete timer present field. It doesn't stop here.

According to the embodiment shown in FIG. 18, the first MLD device transmits a third frame on the target communication channel to allow the other device to determine that the first MLD device should exclude the target station.

As shown in FIG. 19, one embodiment of the present application proposes a method for reconfiguring a multi-channel connection. The method contains the following steps.

S401: The first MLD device transmits the fifth frame on the target communication channel in the broadcast mode.

The fifth frame indicates that the first MLD device should exclude a target station, where the target station is a station affiliated with the first MLD device and operating on the target communication channel.

For example, the first MLD device contains AP 1, AP 2, and AP 3. AP 1 operates on link 1, AP 2 operates on link 2, and AP 3 operates on link 3. When the first MLD device needs to exclude AP 1, the first MLD device transmits a fifth frame on communication channel 1 in broadcast mode. Alternatively, when the first MLD device needs to exclude AP 2, the first MLD device transmits a fifth frame on the broadcast link 2. Alternatively, when the first MLD device needs to exclude AP 3, the first MLD device transmits a fifth frame on the broadcast link 3.

In one embodiment, the fifth frame may reuse an existing frame to provide backward compatibility, in other words, ensuring that a conventional station supporting an earlier version of the protocol can parse the fifth frame. For example, the fifth frame may be a deassociation frame.

It should be understood that if the fifth frame reuses the deassociation frame to allow the device at the end receiving the deassociation frame to determine that the deassociation frame function indicates that the current communication channel should be discarded but does not indicate deassociation, it is necessary to enhance the deassociation frame association. Optionally, if the fifth frame is a deassociation frame, then the fifth frame indicating that the first MLD device should discard the current communication channel may be specifically implemented as follows: The deassociation frame contains a field used for reconfiguring the multi-link connection. Optionally, the field used to reconfigure the multilink connection does not contain information regarding the target link. The field used for multilink reconfiguration may have a different name, such as ML reconfiguration variant ML element. It doesn't stop here. Optionally, for a broadcast deassociation frame, only the current communication channel can be discarded. In one embodiment, the multi-channel element of the multi-channel connection reconfiguration option may not contain a profile for the communication channel. For a unicast deassociation frame, one or more communication channels may be eliminated. In one embodiment, the multi-channel element of the multi-channel connection reconfiguration embodiment comprises a profile for a communication channel, a communication channel identifier (ID), or a bitmap for a corresponding communication channel to indicate the target communication channel.

Alternatively, the fifth frame indicating that the first MLD device should bypass the current communication channel may be specifically implemented as follows: The fifth frame contains a reason code field, where this reason code field indicates that it should exclude the current communication channel. It should be understood that, compared to the reason code field included in the deassociation frame in a related technology, in the present embodiment, a new value is added to the reason code field included in the fifth frame to indicate deletion of the current communication channel.

Optionally, when the fifth frame reuses the deassociation frame, the deassociation frame has different functions in different cases. For example, when the deassociation frame contains a field used for reconfiguring a multi-link connection, this deassociation frame is the fifth frame provided in the present embodiment, the MLD device receiving the deassociation frame disconnects the current communication channel from the first MLD device. If the deassociation frame does not contain a field used to reconfigure the multilink connection, the deassociation frame is a deassociation frame defined in an existing standard, and the MLD device receiving the deassociation frame shall deassociate the first MLD device.

In another possible configuration, the fifth frame may be a newly defined control frame, such as a link removal notify frame, rather than reusing an existing frame. With this approach, the function of the existing frame can remain unchanged.

S402: The receiving end device receives the fifth frame on the target communication channel.

After receiving the fifth frame, the device at the receiving end may parse the fifth frame and further perform a corresponding operation in accordance with the fifth frame.

For example, the receiving end device is a second MLD device. After receiving the fifth frame, the second MLD device must drop the target communication channel to the first MLD device. Additionally, the second MLD device and the first MLD device do not transmit data on the target communication channel.

For example, the device at the receiving end is a regular station (in other words, a single-channel device). When the fifth frame reuses an existing frame, the single-channel device may de-associate with the first MLD device after receiving the fifth frame.

Optionally, if the fifth frame is a newly defined control frame, the first MLD device may optionally transmit a deassociation frame defined in an existing standard on the target communication channel to deassociate the conventional station and the MLD device that did not receive the fifth frame. earlier.

Based on the embodiment shown in FIG. 19, the first MLD device transmits a fifth frame on the target communication channel to allow the other device to determine that the first MLD device should exclude the target station.

As an option, the embodiment shown in FIG. 18 and the embodiment shown in FIG. 19, can be used in combination with one another. As shown in FIG. 20, one embodiment of the present application proposes a method for reconfiguring a multi-channel connection. The method contains the following steps.

S501: The first MLD device transmits the third frame on the target communication channel in broadcast mode.

S502: The receiving end device receives the third frame on the target communication channel.

S503: The first MLD device transmits the fifth frame on the target communication channel in the broadcast mode.

S504: The receiving end device receives the fifth frame on the target communication channel.

According to the embodiment shown in FIG. 20, the first MLD device may first transmit the third frame so that the other device is prepared for the first MLD device to exclude the target station. The first MLD device may then transmit a fifth frame to eliminate the target station.

Currently, multiple stations can be configured for an MLD device to support data transmission over multiple communication channels. However, in some cases the MLD device has a requirement to add a station. For example, when the volume of service provided by or to an MLD device is relatively large, the MLD device may add one or more stations affiliated with the MLD device to distribute the data transmission load. However, a corresponding technical solution has not been developed in conventional technology.

In light of this, one embodiment of the present application proposes a method for reconfiguring a multi-channel connection. As shown in FIG. 21, the method contains the following steps.

S601: The first MLD device transmits the sixth frame in the broadcast mode.

This sixth frame is used to indicate to the first MLD device that it should add a target station affiliated with this first MLD device. This target station operates on the target communication channel.

Optionally, the sixth frame may contain information about the target station. For example, this target station information includes a BSS set operating parameter, BSS set capability information, and other such information.

Optionally, the sixth frame can reuse an existing frame. For example, the sixth frame may reuse the beacon frame. That the sixth frame contains information regarding the target station can be particularly implemented as follows: The ML element or shortened neighbor report in the beacon frame contains information regarding the target station.

In one possible implementation, the first MLD device transmits the sixth frame in beacon frame mode over all communication channels supported by the first MLD device.

S602: The receiving end device receives the sixth frame.

According to the embodiment shown in FIG. 21, the first MLD device broadcasts a sixth frame to allow the other device to determine that the first MLD device should add a target station. Therefore, another device can establish a communication channel with the target station of the first MLD device to transmit data.

In the exemplary embodiment of the present application, the fact that an MLD device disables a station affiliated with that MLD device may also be described as follows: The MLD device disables/deactivates a station affiliated with that MLD device or terminates the BSS for which that station is responsible. . It doesn't stop here.

That an MLD device adds a station affiliated with the MLD device can also be described as follows: The MLD device enables/activates a station affiliated with the MLD device, or activates the BSS set for which this station is responsible. It doesn't stop here.

The technical solutions proposed in the embodiments of the present application are described above in terms of methods. It can be understood that in order to implement the above functions, the communication equipment includes a corresponding hardware configuration and/or software module to implement each function. One skilled in the art will readily appreciate that, in combination with the modules and algorithm steps described in the embodiments provided herein, this application may be implemented by hardware or a combination of hardware and computer software. Whether a function is performed by hardware alone or by hardware controlled by associated computer software depends on the specific application and design constraints of the technology. One skilled in the art may employ various techniques to implement the functions discussed herein in any given application, but such implementation should not be considered beyond the scope of this application.

In embodiments of the present application, the hardware may be divided into functional modules based on the above example methods. For example, each function module can be obtained by partitioning based on each corresponding function, or two or more functions can be integrated into one function module. The integrated module may be implemented in the form of hardware, or it may be implemented in the form of a software function module. In the present application, modularization is just one example and is simply a division of logical functions. In actual implementation, a different partitioning method may be used. Below, an example is used for description in which each function module is obtained by partitioning based on each corresponding function.

In fig. 16 shows communication equipment according to one embodiment of the present application. This communication equipment includes a processor module 101 and a communication module 102.

For example, when the communication equipment is a first MLD device, or the communication equipment is used in the first MLD device, the processor module 101 is configured to support the first MLD device in performing step S101 shown in FIG. 4. The communication module 102 is configured to support the first MLD device in carrying out step S101 shown in FIG. 4, step S104 shown in FIG. 8, steps S201 to S203 shown in FIG. 14, step S301 shown in FIG. 18, step S401 shown in FIG. 19, steps S501 and S503 shown in FIG. 20, and step S601 shown in FIG. 21.

For example, when the communication equipment is a second MLD device, or the communication equipment is used in the second MLD device, the processor module 101 is configured to support the second MLD device in step S103 shown in FIG. 4. The communication module 102 is configured to support the second MLD device in step S102 shown in FIG. 4, step S104 shown in FIG. 8, steps S201 to S203 shown in FIG. 14, step S302 shown in FIG. 18, step S402 shown in FIG. 19, steps S502 and S504 shown in FIG. 20, and step S602 shown in FIG. 21.

The following describes a possible product form for communication equipment. It should be understood that any product, of any form, having the functions of the specified communication equipment falls within the scope of protection of this application. It should be further understood that the following description is only an example and does not limit the form of the communication equipment in the embodiments of the present application.

In fig. 17 shows a diagram of the structure of a possible product form for communication equipment according to one of the variants of this application.

A possible form of product for the communication equipment in the present embodiment may be a multi-channel device, and the multi-channel device includes a processor 201 and a transceiver 202. Optionally, the multi-channel device further includes a storage device 203.

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

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

As a possible product form, the communication equipment contemplated in the embodiments of this application may be implemented using an integrated circuit (chip). This integrated circuit (chip) includes a processor circuit 201 and a transceiver pin 202. Optionally, the integrated circuit (chip) may further include an information storage medium 203.

In another possible product form, the communications equipment described in the subject embodiment of this application may alternatively be implemented using the following circuit or component: one or more field programmable gate arrays (FPGA), a programmable logic device ( logic device (PLD), controller, state machine, logic gate circuit, discrete hardware component, any other suitable circuitry, or any combination of circuitry that can perform the functions described in this application.

As an option, one embodiment of the present application further provides a computer-readable medium for storing information. This computer-readable storage medium stores computer instructions. When a computer executes these computer instructions, the computer may implement the methods of the above embodiments.

As an option, one embodiment of the present application further provides a computer program product containing computer instructions. When a computer executes these computer instructions, the computer may implement the methods of the above embodiments.

It should be understood that these computer instructions may be stored on a computer-readable storage medium, or may be transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer commands may be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, fiber optic cable, or digital subscriber line) or wireless (such as infrared beam, radio or microwave) method. A computer-readable storage medium may be any suitable medium accessible to a computer or data storage device, such as a server or data center, integrating one or more media suitable for use. Such a suitable medium may be a magnetic medium (eg, a floppy disk, hard disk, or magnetic tape), optical media, semiconductor media (eg, a solid state drive), or other similar media.

Based on the above descriptions of the embodiments, one skilled in the art can clearly understand that for convenience and brevity of the description, the breakdown into the above functional modules is merely used as an example for consideration. In actual implementation, the above functions may be assigned to different function modules for implementation based on specific requirements, in other words, the internal structure of the hardware is divided into different function modules to implement all or part of the functions described above.

It should be understood that the apparatus and method described in several embodiments proposed in this application may be implemented differently. For example, the described hardware options are presented simply as examples. For example, partitioning into modules or blocks is simply partitioning of logical functions, so the actual implementation may have a different partition. For example, several blocks or components may be combined or integrated in other hardware, or some features may be ignored or not implemented. In addition, the relationships shown or discussed, or direct communications or connections for information transfer, may be implemented through certain interfaces. Indirect communications or data connections may be implemented in mechanical, electrical, or other forms.

Units described as separate parts may or may not be physically separate, and parts described as single units may be one or more physical units, may be located in one location, or may be distributed over multiple locations. Some or all of the blocks may be selected based on actual requirements to achieve the technical solution objectives of the application options.

In addition, the functional modules in embodiments of the present application may be integrated within a single processor module, each of the modules or blocks may physically exist alone, or two or more blocks may be integrated within a single block. The integrated unit may be implemented in the form of hardware, or it may be implemented in the form of a software function module.

When an integrated module is implemented in the form of a software function module and is sold or used as an independent product, the integrated module may be stored on a readable storage medium. Based on such understanding, the technical solutions of the present application, substantially or in part known in the art, or all or some of the technical solutions may be implemented in the form of a software product. This software product is stored on a storage medium and contains a number of instructions for controlling a device (which may be a single-chip microprocessor, integrated circuit (chip), or other similar device) or processor (processor) to carry out all or some of the steps of the methods described in the embodiments of this application.

The above descriptions represent only specific embodiments of the present application and are not intended to limit the scope of the application. Any variations or substitutions within the technical scope described in this application will fall within the scope of protection of the application. Therefore, the scope of protection of the present application corresponds to the scope of protection of the Claims.

Claims (31)

1. A method for reconfiguring a multi-channel connection, wherein the method comprises: generating, by the first multi-link device (MLD), a basic transition management (BTM) request frame, wherein the BTM request frame contains a first field that occupies one bit; and the first field either indicates a second MLD to disable the communication channel over which the BTM request frame is transmitted from the first MLD, or indicates the second MLD to de-associate with the first MLD so that the second MLD disables all communication channels from the first MLD; And transmission by the first MLD device of this BTM request frame to the second MLD device. 2. A method for reconfiguring a multi-channel connection, wherein the method comprises: receiving, by the second multi-link device (MLD), a basic transition management (BTM) request frame from the first MLD device, wherein the BTM request frame contains a first field that occupies one bit; and the first field either indicates a second MLD to disable the communication channel carrying the BTM request frame from the first MLD, or indicates a second MLD to de-associate with the first MLD such that the second MLD disconnects all communication channels from the first MLD; And parsing by the second MLD device of the BTM request frame. 3. The method of claim 1 or 2, wherein the value of the first field is equal to the first predetermined value, and the first field indicates the second MLD to disable the communication channel over which the BTM request frame is transmitted from the first MLD. 4. The method of claim 3, wherein the value of the first field is equal to the second predetermined value, and the first field indicates a second MLD to unassociate with the first MLD. 5. The method of claim 4, wherein the first preset value is 1 and the second preset value is 0. 6. The method according to claim 1 or 2, in which the method additionally contains: receiving, by the first MLD device, a BTM control response frame indicating whether the handover between the first MLD device and the second MLD device has been accepted for execution; or transmitting, by the second MLD device, a BTM control response frame indicating whether the handover between the first MLD device and the second MLD device has been accepted for execution. 7. The method of claim 6, wherein the BTM control response frame contains a target Basic Service Set Identifier (BSSID) field, and the target BSSID field contains a media access control address (MAC address) of the MLD device associated with the access point of the device MLD (AP MLD) that the second MLD device has chosen to establish a connection. 8. The method of claim 6 or 7, wherein the BTM control response frame comprises a neighbor reporting element, and the neighbor reporting element comprises a basic multi-channel element, and the basic multi-channel element does not contain a profile for the communication channel. 9. Communication equipment containing a processor module and a communication module, in which the processor module is configured to generate a Basic Transition Management (BTM) request frame for transmission to a second MLD device, wherein the BTM request frame contains a first field that occupies one bit; and the first field either indicates a second MLD to disable the communication channel over which the BTM request frame is transmitted from the first MLD, or indicates the second MLD to de-associate with the first MLD so that the second MLD disables all communication channels from the first MLD; And the communication module is configured to transmit the BTM request frame to the second MLD device. 10. Communication equipment containing a processor module and a communication module, in which the communication module is configured to receive a basic transition control (BTM) request frame from the first MLD device, where the BTM request frame contains a first field that occupies one bit; and the first field either indicates a second MLD to disable the communication channel over which the BTM request frame is transmitted from the first MLD, or indicates the second MLD to de-associate with the first MLD so that the second MLD disables all communication channels from the first MLD; And the processor module is configured to parse the BTM request frame. 11. The apparatus of claim 9 or 10, wherein the value of the first field is equal to the first predetermined value, and the first field indicates the second MLD to disable the communication channel over which the BTM request frame from the first MLD is transmitted. 12. The apparatus of claim 11, wherein the value of the first field is equal to the second predetermined value, and the first field indicates a second MLD to de-associate with the first MLD. 13. The apparatus of claim 12, wherein the first preset value is 1 and the second preset value is 0. 14. The apparatus of claim 9 or 10, wherein the communication module is configured to: receiving a BTM control response frame indicating whether a handover between the first MLD device and the second MLD device has been accepted for execution; or transmitting a BTM control response frame indicating whether the handover between the first MLD device and the second MLD device has been accepted for execution. 15. The apparatus of claim 14, wherein the BTM control response frame contains a target Basic Service Set Identifier (BSSID) field, and the target BSSID field contains a media access control address (MAC address) of the MLD device associated with the access point of the device MLD (AP MLD) that the second MLD device has chosen to establish a connection. 16. The apparatus of claim 14 or 15, wherein the BTM control response frame comprises a neighbor reporting element, and the neighbor reporting element comprises a basic multi-channel element, and the basic multi-channel element does not comprise a profile for the communication channel. 17. A multi-link communication device (MLD) comprising a processor and a transceiver, where the processor is configured to perform data processing operations in accordance with the multi-link connection reconfiguration method of any one of claims. 1-8, and the transceiver is configured to perform communication operations according to the multi-link connection reconfiguration method of any one of claims. 1-8. 18. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, the computer program comprising program instructions; and when a computer executes these program instructions, such computer may implement the method of any one of claims. 1-8. 19. An integrated circuit for reconfiguring a multi-channel connection, wherein the integrated circuit comprises a processor circuit and a transceiver, the processor circuit being configured to perform processing operations according to the method of reconfiguring a multi-channel connection according to any one of claims. 1-8, and the transceiver is configured to perform communication operations according to the multi-link connection reconfiguration method of any one of claims. 1-8.