Communication method, apparatus, device and system in wireless local area network

Abstract

A communication method, apparatus, device and system in a wireless local area network. The method comprises: an ultra-high reliability (UHR) access point multi-link logical entity receives a second frame from a non-access point multi-link logical entity, wherein the second frame is used for indicating a roaming request; and the UHR access point multi-link logical entity sends a first frame to the non-access point multi-link logical entity, wherein the first frame is used for indicating a roaming reconfiguration, the UHR access point multi-link logical entity includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point multi-link logical entity.

Description

[Corrected 28.11.2024 in accordance with Rule 26] Communication method, device, equipment and system in wireless local area network

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on November 3, 2023, with application number 202311457656.1 and invention name “Communication method, device, equipment and system in wireless local area network”, the Chinese patent application filed with the China Patent Office on November 8, 2023, with application number 202311479127.1 and invention name “Communication method, device, equipment and system in wireless local area network”, and the Chinese patent application filed with the China Patent Office on November 22, 2023, with application number 202311572418.5 and invention name “Communication method, device, equipment and system in wireless local area network”, all of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to a communication method, apparatus, device, and system in a wireless local area network. Background Art

[0003] In related technologies, when a mobile device moves from the coverage of one access point (AP) to the coverage of another AP, it is necessary to switch the connection between the mobile device and different APs. However, the switching process involves a large amount of signaling interaction, resulting in a large switching delay and possible data transmission interruption. Therefore, how to achieve seamless roaming to ensure data transmission continuity is an urgent problem that needs to be solved.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a communication method, apparatus, device, system, and storage medium in a wireless local area network.

[0006] An embodiment of the present application provides a communication method in a wireless local area network, including:

[0007] An ultra-high reliability (UHR) access point multi-link logical entity receives a second frame from a non-access point multi-link logical entity, wherein the second frame is used to initiate a roaming request;

[0008] The UHR access point multi-link logical entity sends a first frame to the non-access point multi-link logical entity, wherein the first frame is used to indicate roaming reconfiguration;

[0009] The UHR access point multi-link logical entity includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point multi-link logical entity.

[0010] An embodiment of the present application provides a communication method in a wireless local area network, including:

[0011] The non-access point multi-link logical entity sends a second frame to the ultra-high reliability (UHR) access point multi-link logical entity, wherein the second frame is used to initiate a roaming request;

[0012] The non-access point multi-link logical entity receives a first frame from the UHR access point multi-link logical entity, wherein the first frame is used to indicate roaming reconfiguration;

[0013] The UHR access point multi-link logical entity includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point multi-link logical entity.

[0014] Each exemplary embodiment of the present application provides a method for constructing a communication frame, which is applied to wireless network communication of an ultra-high reliability (UHR) access point multi-link logical entity, including: generating a first indication field, wherein the first indication field indicates that a non-access point multi-link logical entity is to be switched to one or more links associated with a first access point multi-link logical entity, wherein the first access point multi-link logical entity is attached to the UHR access point multi-link logical entity.

[0015] In some embodiments, the first indication field is used to indicate logical entity identification information corresponding to the first access point multi-link logical entity and link information corresponding to the one or more links.

[0016] In some embodiments, the link information includes link quantity information and one or more link identification information.

[0017] In some embodiments, the first indication field also includes a STA control field.

[0018] In some embodiments, the STA control field includes a link deletion mode field and / or a link deletion count field.

[0019] In some embodiments, the method further includes: generating an action field, wherein the field content included in the first indication field depends on the value of the action field.

[0020] In some embodiments, the first indication further indicates a switching order of the one or more links.

[0021] Each exemplary embodiment of the present application provides a method for constructing a communication frame, which is applied to wireless network communication of an ultra-high reliability (UHR) access point multi-link logical entity, including: generating a UHR mobility domain element field, wherein the UHR mobility element field includes a seamless transition capability field.

[0022] In some embodiments, the byte length of the seamless transition capability is greater than 2 bits.

[0023] In some embodiments, the UHR mobility domain element field further includes a mobility domain identification field.

[0024] In some embodiments, the UHR mobility domain field is set in the sixth frame.

[0025] In some embodiments, the UHR mobility domain field reuses the FT Capability and Policy subfield in the Mobility Domain Information Element (MDIE) field.

[0026] Each embodiment of the present application provides an access point device, including: a sending module, configured to send a first frame to a non-access point multi-link logical entity (Non-AP Multi-link logical entity), wherein the first frame includes first link identification information, and the first link identification information indicates that the non-access point multi-link logical entity is to be switched to a target link associated with the first access point multi-link logical entity.

[0027] Each embodiment of the present application provides an access point device, including:

[0028] a receiving module, configured to receive a second frame from a non-access point multi-link logical entity, wherein the second frame is used to initiate a roaming request;

[0029] A sending module, configured to send a first frame to a non-access point multi-link logical entity, wherein the first frame is used to indicate roaming reconfiguration;

[0030] The access point device includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point multi-link logical entity.

[0031] Each embodiment of the present application provides a non-access point device, including:

[0032] A sending module, configured to send a second frame to an ultra-high reliability UHR access point multi-link logical entity, wherein the second frame is used to initiate a roaming request;

[0033] A receiving module, configured to receive a first frame from the UHR access point multi-link logical entity, wherein the first frame is used to indicate roaming reconfiguration;

[0034] The UHR access point multi-link logical entity includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point device.

[0035] Each exemplary embodiment of the present application provides an access point multi-link device, including: a processor and a transceiver; wherein the processor is configured to call a computer program and cooperate with the transceiver to implement the communication method described in each of the above embodiments.

[0036] Each embodiment of the present application provides a non-access point multi-link device, including: a processor and a transceiver; wherein the processor is configured to call a computer program and cooperate with the transceiver to implement the communication method described in the above embodiments.

[0037] Each embodiment of the present application provides a communication system in a wireless local area network, including: the access point device according to the above embodiments or the access point multi-link device according to the above embodiments, and the non-access point device according to the above embodiments or the non-access point multi-link device according to the above embodiments.

[0038] Each exemplary embodiment of the present application provides a computer-readable storage medium having instructions stored thereon. When the instructions are executed by a processor, the processor executes the communication method in a wireless local area network provided by each of the above embodiments.

[0039] Each exemplary embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute the communication method in a wireless local area network provided by each of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the technical solution of the present application, a brief introduction will be given below in combination with the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, without paying any creative work, drawings of other embodiments can be obtained based on these drawings.

[0041] FIG1 shows a network architecture diagram of an application environment of a communication method in a wireless local area network provided in an embodiment of the present application.

[0042] FIG2 shows a schematic diagram of an application scenario of a communication method in a wireless local area network provided in an embodiment of the present application.

[0043] FIG3 shows a schematic structural diagram of a mobility domain element field provided in an embodiment of the present application.

[0044] FIG4 shows a schematic structural diagram of a seamless transition capability field of a mobility domain element field provided in an embodiment of the present application.

[0045] FIG5 shows a schematic diagram of a frame structure extension of a mobility domain element field provided in an embodiment of the present application.

[0046] FIG6 shows a schematic structural diagram of a Basic Service Set (BSS) Transmit Management (BTM) Roaming frame provided in an embodiment of the present application.

[0047] FIG7 is a schematic diagram showing the values ​​of the Action subfield of the BTM roaming frame and their functional correspondence provided by an embodiment of the present application.

[0048] FIG8 shows a schematic structural diagram of the CommonInfo subfield of the BTM roaming frame provided in an embodiment of the present application.

[0049] FIG9 shows a flow chart of the access procedure of the communication method provided in an embodiment of the present application.

[0050] FIG10 shows a flow chart of the network access process of the communication method provided in an embodiment of the present application.

[0051] FIG11 shows a schematic structural diagram of the KDE field of the key information of the multicast key in the communication method provided in an embodiment of the present application.

[0052] FIG12 shows a schematic structural diagram of the FTE field of the Fast Transition protocol of the key information of the multicast key in the communication method provided in an embodiment of the present application.

[0053] FIG13 shows a schematic diagram of a communication method in a wireless local area network provided in an embodiment of the present application.

[0054] FIG14 shows a schematic diagram of another communication method in a wireless local area network provided in an embodiment of the present application.

[0055] FIG15 shows a schematic diagram of part of the seamless roaming process in the communication method provided in an embodiment of the present application.

[0056] FIG16 is a schematic diagram showing the remaining process of the seamless roaming process in the communication method shown in FIG15 .

[0057] FIG17 shows a flow chart of a seamless roaming process of a communication method provided in another embodiment of the present application.

[0058] FIG18 shows a flow chart of a seamless roaming process of a communication method according to another embodiment of the present application.

[0059] FIG19 shows the BTM request frame format of the seamless roaming process according to another embodiment of the present application and the structure of the neighbor report element (Neighbor Report element) in its BSS transition candidate table entry field.

[0060] FIG20 shows the format of the BSS transition candidate preference sub-element of the BSS transition candidate entry field according to another embodiment of the present application.

[0061] FIG21 shows a Basic Multi-Link Element structure of a BSS transition candidate entry field according to another embodiment of the present application.

[0062] FIG22 shows a flow chart of a seamless roaming process of a communication method according to another embodiment of the present application.

[0063] FIG23 shows the ST capability field format of the UHR mobility domain element of the network entry process according to another embodiment of the present application.

[0064] FIG24 shows the values ​​and corresponding meanings of the Seamless BSS Transition Mode (Seamless BSS TransitionMode) of the ST capability field in another embodiment of the present application.

[0065] FIG25 shows a schematic diagram of the internal structure of an access point device provided in an embodiment of the present application.

[0066] FIG26 shows a schematic diagram of the internal structure of a non-access point device provided in an embodiment of the present application.

[0067] FIG27 shows a block diagram of an access point multi-link device provided in an embodiment of the present application.

[0068] FIG28 shows a block diagram of a non-access point multi-link device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0069] Although the present application allows for embodiments in many forms, embodiments of the present application including preferred embodiments are shown in the accompanying drawings that will be described in detail herein. It should be understood that the content disclosed herein will be considered as an explanation of the principles of the present application and is not intended to limit the broad aspects of the present application to one or more embodiments shown or disclosed.

[0070] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application. In the absence of conflict, the embodiments in the present application and the features in the embodiments can be combined with each other in any way, and the technical solutions formed by any combination are still within the scope of protection sought in this application. In addition, although the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in an order different from that here.

[0071] The terms "first" and "second" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "including" and any variations thereof are intended to cover non-exclusive protection. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to the process, method, system, product, or device.

[0072] When “including,” “having,” and “comprising” are used in the present application, another component may be added unless a clear limiting term such as “only,” “consisting of,” etc. is used. Unless mentioned otherwise, a term in the singular form may include a plural form and should not be understood as having only one number.

[0073] Unless otherwise defined in the context, the term "logical entity" in this application may refer to a functional module implemented by software, a hardware unit with specific functions implemented by hardware, or a combination of software functional modules and hardware units.

[0074] Figure 1 is a schematic diagram of an application scenario applicable to an embodiment of the present application. As shown in Figure 1, the application scenario includes a station (STA) 201 and an access point (AP) 202; wherein, AP 202 includes 3 APs. It should be noted that there is no limit on the number of APs involved in AP 202, and Figure 1 only uses 3 APs as an example. The AP shown in Figure 1 can be a multi-link access logical entity, such as a non-co-located multi-link access logical entity, which is attached to an ultra-high reliability (UHR) multi-link logical entity.

[0075] AP 202 forms an AP wireless network environment 203 with three APs. When STA 201 enters the AP wireless network environment 203, it can perform seamless roaming.

[0076] Site 201 can be an electronic device such as a mobile phone, smart wearable device, tablet computer, notebook, etc.; in addition, a related client can also be installed on site 201, and the client can be software, such as an application (Application, APP), a browser, short video software, etc., or a web page, mini program, etc.

[0077] To facilitate understanding of the embodiments of the present application, the related technologies of the present application are explained.

[0078] 802.11be networks, also known as Extremely High Throughput (EHT) networks, achieve extremely high throughput through a series of system features and various mechanisms. In 802.11be networks, wireless devices can support multi-link communication. Multi-link communication support can mean that the wireless device supports simultaneous communication on multiple frequency bands or on different channels within the same frequency band. A wireless device that supports multi-link communication is often referred to as a multi-link device (MLD). An MLD has one or more STAs.

[0079] Multi-link devices in wireless local area networks (WLANs) are divided into two categories: AP multi-link devices and non-AP multi-link devices. STAs in AP MLDs are called AP STAs, while STAs in non-AP MLDs are called non-AP STAs. For simplicity, AP STAs are often referred to as APs, and non-AP STAs as STAs.

[0080] A non-AP multi-link device can establish one or more links with an AP multi-link device, forming associated links. Each associated link connects a non-AP STA in the non-AP multi-link device and an AP in the AP multi-link device.

[0081] In an exemplary embodiment, the AP MLD is an EHT AP MLD, and each of the EHT AP MLDs has a corresponding EHT Up Media Access Control (UMAC). When the APs attached to the AP MLD are co-located with each other, the AP MLD is a co-located AP MLD; otherwise, the AP MLD is a non-co-located AP MLD.

[0082] Figure 2 shows an exemplary architecture diagram of an Ultra High Reliability (UHR) AP MLD. In this example, the UHR AP MLD includes N EHT AP MLDs and a UHR AP MLD UMAC that independently communicates with the N EHT AP MLDs via a wired or wireless backhaul network. As shown in Figure 2, EHT AP MLD 1 includes N APs (AP 0 to AP N in Figure 2), each of which can be associated with multiple links (Link 0 to Link N, as shown in the figure). The N APs are each communicated with N LMACs, which converge on the TID (Traffic Identifier)-to-Link mapping / Link merging module. The TID-to-Link mapping / Link merging module communicates with the UHR AP MLD's UMAC backhaul. The UHR AP MLD UMAC controls and manages the link communications of EHT AP MLD 1 to EHT AP MLD N.

[0083] Traditional Wi-Fi technology uses standard roaming to switch between different APs when a mobile device (STA) moves from one AP to another, ensuring optimal Internet access. However, with standard roaming, when a mobile device moves from one AP to another, the user must manually disconnect from the current connection, search for available Wi-Fi networks again, and manually select a new AP to connect to. This roaming method can lead to connection interruptions, reduced data transmission reliability, and decreased user experience.

[0084] Therefore, Fast Transition (FT) roaming technology has been introduced to traditional Wi-Fi technologies. FT roaming, also known as 802.11r, is a fast Wi-Fi roaming technology. When a mobile device moves from one AP to another, it embeds the four-way key handshake with the target AP into the reassociation process, enabling fast AP switching.

[0085] However, whether it is standard roaming or FT roaming, the following problems may occur during AP switching:

[0086] 1. When a mobile device switches between APs, it incurs significant frame overhead and requires link authentication, including 802.1X Extensible Authentication Protocol (EAP) authentication and a four-way handshake for roaming, resulting in significant latency.

[0087] 2. During the roaming process of mobile devices, the transmission of user data will be interrupted, the continuity of data cannot be guaranteed, the reliability of data transmission will decrease, and the user experience will deteriorate.

[0088] A communication method provided in an embodiment of the present application can achieve seamless roaming of mobile devices through a UHR multi-link logical entity, reduce switching delays during roaming, and ensure the continuity of data transmission.

[0089] Each exemplary embodiment of the present application provides a communication method applied to a UHR multi-link logical entity, which realizes fast roaming while ensuring the continuity of data transmission.

[0090] To this end, the embodiment of the present application introduces seamless roaming frames and adds fields to the 802.11be frames. These introduced frames and fields are described below with reference to Figures 3 to 12.

[0091] It should be noted that the naming of frames, fields or elements provided in the embodiments of the present application is only an example and can be replaced with other names, which is not limited in the present application.

[0092] FIG3 shows a schematic structural diagram of a UHR mobility domain element field provided in an embodiment of the present application.

[0093] The UHR mobility domain element field is used to declare seamless transition capability (Seamless Transition Capability) or seamless roaming capability (Seamless Roaming Capability). For example, the UHR mobility domain element field includes a seamless transition capability (Seamless Transition Capability) field, which is used to declare wireless roaming capability or wireless transition capability.

[0094] Optionally, the length of the seamless transition capability field is 1 octet, or longer, such as 2 octets, 3 octets, etc.

[0095] Optionally, the UHR mobility domain element further includes at least one of an element identifier (Element ID), a length (Length), or a mobility domain identifier (Mobility Domain ID, MDID), wherein the MDID field is an identifier that names the UHR roaming mobility domain.

[0096] The UHR Mobility Domain Element field can be appended to Beacon Frames, Probe Response Frames, Association Request Frames, Association Response Frames, and Authentication Frames from a UHR AP MLD (or AP) to announce the seamless transition capabilities of the UHR AP MLD (e.g., to non-access point multilink devices). The extended structures of these frames are further described below.

[0097] It is understood that the UHR Mobility Domain Element field can also be attached to frames from non-AP STA MLD (or non-AP STA). When the UHR Mobility Domain Element field is attached to frames from non-AP STA MLD, the UHR Mobility Domain Element field is used to indicate the seamless transition capability of the non-AP STA MLD (or non-AP STA).

[0098] In some embodiments, the UHR Mobility Domain Element field may be appended as a new field in the above frames.

[0099] Alternatively, the UHR Mobility Domain Element field may reuse or extend existing fields in the aforementioned frames. For example, the UHR Mobility Domain Element field may extend and reuse the FT Capability and Policy subfield in the Mobility Domain Information Element (MDIE) field in the 802.11r protocol.

[0100] Figure 4 shows a schematic diagram of the structure of the seamless transition capability (ST Capability) field of a UHR mobility domain element field provided by an embodiment of the present application. The seamless transition capability field is used to declare the seamless transition capability of an AP or non-AP STA that can perform seamless basic service set (BSS) transition.

[0101] The seamless transition capability field may include a seamless basic service set transition status (Seamless BSS Transition Status) subfield. Optionally, 1 bit is used to indicate the seamless basic service set transition status.

[0102] In some embodiments, when the MLD has seamless transition capability, the seamless basic service set transition status subfield may be set to 1, otherwise it may be set to 0. Of course, more bits may be used to indicate the seamless basic service set transition status, which is not limited in this embodiment of the present application.

[0103] Optionally, the seamless transition capability field may further include a reserved field. The length of the reserved field may be 7 bits, or may be other number of bits, which is not particularly limited in the embodiment of the present application.

[0104] FIG5 shows a schematic structural diagram of a frame structure extension field of a UHR mobility domain element field provided in an embodiment of the present application.

[0105] As previously described, the UHR Mobility Domain Element field can be appended to Beacon frames, Probe Response frames, Association Request frames, Association Response frames, and Authentication frames from a UHR AP MLD (or AP) to declare the seamless transition capability of the UHR AP MLD (e.g., to non-access point multilink devices). In the embodiment shown in FIG5 , when the value of the "dot11SeamlessBSSTransition Activated" field is true, the UHR Mobility Domain Element field can be present at the end of the aforementioned frames, i.e., the UHR Mobility Domain Element field can be added to a reserved field of these frames or extended to the end of these frames.

[0106] Alternatively, the UHR mobility domain element field may also be added at other locations in the above frame, which is not particularly limited in the embodiment of the present application.

[0107] Alternatively, whether the UHR mobility domain element field exists may also be determined based on other fields except the "dot11SeamlessBSSTransition Activated" field, which is not particularly limited in this embodiment of the present application.

[0108] FIG6 shows a schematic structural diagram of a BSS Transmit Management (BTM) roaming frame provided in an embodiment of the present application.

[0109] To achieve seamless roaming in a UHR AP MLD environment, the BTM roaming frame is introduced for exchanging roaming messages between a non-AP multi-link logical entity (e.g., a non-AP STA MLD) and a UHR AP MLD. Roaming messages include a roaming request (e.g., sent from a non-AP STA MLD to a UHR AP MLD), a roaming link switching indication (e.g., sent from a UHR AP MLD to a non-AP STA MLD), and a roaming link switching confirmation (e.g., sent from a non-AP STA MLD to a UHR AP MLD).

[0110] As shown in Figure 6, the BTM roaming frame includes an Action field. Optionally, the byte length of the Action field is 1 octet, or more bytes, such as 2 octets, 5 octets, or 10 octets.

[0111] Optionally, as shown in FIG6 , the BTM roaming frame may further include a Category field.

[0112] The Category field is already defined in the existing 802.11 standard. For example, if it is set to 10, it will be affected by Wireless Network Management (WNM).

[0113] Optionally, as shown in FIG6 , the BTM roaming frame may further include a Dialog Token field. The Dialog Token field is a non-zero value taken by the STA sending the BTM roaming frame to identify whether the frame type is a request frame type or a response frame type.

[0114] Figure 7 shows a schematic diagram of the values ​​of the Action field of a BTM roaming frame and their corresponding functions according to an embodiment of the present application. Different values ​​of the Action field result in different types of BTM roaming frames.

[0115] For example, when the Action field value is 28, the BTM roaming frame is a Roaming Request frame. When the Action field value is 29, the BTM roaming frame is a Roaming Reconfigure frame. When the Action field value is 30, the BTM roaming frame is a Roaming Confirm frame.

[0116] As shown in FIG6 , the BTM roaming frame further includes a public information field.

[0117] Figure 8 shows a schematic diagram of the structure of the Common Info field of a BTM roaming frame provided by an embodiment of the present application. Different values ​​in the Action field, i.e., different BTM roaming frame types (which may also indicate different frame senders and receivers), will result in different roaming information carried in the corresponding Common Info field.

[0118] The common information field of the BTM roaming frame includes at least an MLD AP ID field and a Links Info field.

[0119] Optionally, the common information field may further include a length field, where the length field is used to indicate the length of fields other than the length field in the common information field.

[0120] When the BTM roaming frame is a BTM roaming reconfiguration frame, the common information field may further include a status code field. Optionally, the common information field may further include a STA control field.

[0121] When the BTM roaming frame is a BTM roaming confirmation frame, the common information field may further include a status code field.

[0122] Optionally, as shown in the embodiment of FIG8 , the common information field of the BTM roaming frame may include a length field, an MLD AP ID field, a link information field, a status code field, and a STA control field.

[0123] The length field indicates the length of the fields in the common information field excluding the length field. The length of the length field may be 1 octet. In other embodiments, the length of the length field may be longer, for example, 2 octets, 5 octets, or 10 octets, which is not particularly limited in this application.

[0124] The MLD AP ID field indicates the identifier of the requested AP MLD, that is, the identifier of the MLD AP to which handover is requested. The length of the MLD AP ID field is 1 octet. In other embodiments, the length of the MLD AP ID field may be longer, for example, 2 octets, 5 octets, or 10 octets, which is not particularly limited in this application.

[0125] The Link Information field indicates link information for the target link, that is, the link information for the target link that the non-AP MLD wants to disconnect from the original MLD AP and associate with the new MLD AP. The Link Information field has a variable length, depending on the number of target links in the Link Information field. Therefore, the length of the Common Information field is also variable.

[0126] Optionally, as shown in FIG8 , the link information field may include a link number (Link Num) field and one or more link identification information (Link ID Info) fields. The link number field indicates the number of links requested for switching (or disconnection request), or the number of target links. The link identification information field indicates the link identifier of the link requested for switching, or the link identifier of the target link.

[0127] The status code field is already defined in the existing 802.11 standard and will not be described in detail in this application. The length of the status code field can be 1 octet. In other embodiments, the length of the status code field can also be longer, for example, 2 octets, 5 octets, or 10 octets, which is not specifically limited in this application.

[0128] Optionally, as shown in Figure 8, the STA Control field may include a Link Del Mode field. The Link Del Mode field may be 8 bits long. In other embodiments, the Link Del Mode field may be of other lengths, such as 4 bits, 12 bits, or 16 bits.

[0129] The link deletion mode field can indicate the link deletion method, or the link disconnection method, link switching method, such as immediate disconnection (or immediate deletion, immediate switching) or delayed disconnection (or delayed deletion, delayed switching).

[0130] For example, if the Link Deletion Mode field is 1 bit, when the Link Deletion Mode field is set to 0, the requested link can be disconnected (or deleted, switched) immediately. When the Link Deletion Mode field is set to 1, the requested link can be disconnected (or deleted, switched) after waiting for a specified period of time.

[0131] Alternatively, in the case where the link deletion field is 2 bits, when the link deletion mode field is set to 0, the association with the link can be disconnected immediately; when the link deletion mode field is set to 1, 2 or 3, the association with the link is disconnected after waiting for the corresponding first preset time, second preset time or third preset time respectively.

[0132] Optionally, the STA control field may also include a Link Del Count field, which is used to indicate the delay duration of the delayed disconnection. The Link Del Count field may indicate that after receiving the corresponding frame, the link requested will be disconnected (or deleted, switched) after waiting for a specified number of time units (TU). The Link Del Count field may also indicate other physical quantities to control the waiting time for the link requested to be disconnected (or deleted, switched). The length of the Link Del Count field may be 8 bits. In other embodiments, the length of the Link Del Count field may also be other values, for example, 4 bits, 12 bits, or 16 bits.

[0133] FIG9 shows a schematic diagram of an access process (Access Process) of the communication method provided in an embodiment of the present application.

[0134] As shown in Figure 9, in the network access process, after completing detection, multi-link authentication, and association, the non-AP STA MLD and / or the ultra-high reliability access point multi-link device (UHR AP MLD) can calculate and generate a unicast key (e.g., a pairwise transition key (PTK)) through the EAPOL-Key frame. The PTK can be calculated based on the UMAC address of the UHR AP MLD and stored in the UMAC of the UHR AP MLD. Therefore, the PTK can be shared with all AP MLDs attached to the UHR AP MLD, and the PTK is the same for each AP MLD.

[0135] Specifically, the PTK can be shared with multiple AP MLDs of the UHR AP MLD after it is generated during the network access process. Alternatively, the PTK can be stored in the UHR AP MLD UMAC after it is generated during the network access process, and then shared with a specific AP MLD during the seamless roaming process under the control of the UHR AP MLD UMAC.

[0136] In addition, the multicast key (e.g., group transient key (GTK), integrated group transient key (IGTK), beacon integrated group transient key (BIGTK)) can be calculated based on the EHT AP MLD LMAC address corresponding to each link of the AP MLD attached to the UHR AP MLD (i.e., the LMAC address corresponding to the UHR AP MLD, or the LMAC address corresponding to the EHT AP MLD).

[0137] The UHR AP MLD calculates and sends these multicast keys, or instructs the UHR AP MLD to send them, to the corresponding non-AP STA MLD. The non-AP STA MLD then stores these multicast keys. These multicast keys can be calculated using the UHR AP MLD UMAC and sent by the UHR AP MLD UMAC. Alternatively, they can be calculated using the EHT AP MLD UMAC to which the EHT AP MLD belongs and sent directly by the EHT AP MLD to the corresponding non-AP STA MLD. Alternatively, they can be sent back to the UHR AP MLD UMAC and then sent to the corresponding non-AP STA MLD via the UHR AP MLD UMAC.

[0138] For example, during the network access phase of a non-AP STA MLD, the UHR AP MLD sends the calculated multicast key to the non-AP STA MLD during the network access process.

[0139] Additionally or alternatively, when a non-AP STA MLD is before or during seamless roaming, the UHR AP MLD sends a multicast key or an indication to the non-AP STA MLD.

[0140] Optionally, in some embodiments, identification information of the AP MLD corresponding to the corresponding link may be added to the multicast key information to avoid confusion of same-frequency links of different AP MLDs in a non-co-location environment. This will be described in detail in the following embodiments.

[0141] Based on the above unicast and multicast key designs, in the UHR AP MLD architecture, during seamless roaming when a non-AP STA switches from MLD1 to MLD2, there is no need for key re-authentication, re-association, or a 4-way handshake when the non-AP STA switches to the new AP MLD. This reduces the frame overhead of seamless roaming and the roaming authentication delay caused by the FT roaming mechanism.

[0142] The working manner of the unicast key and the multicast key in the seamless roaming process will be described in the following specific implementation manner.

[0143] FIG10 shows a flow chart of a network access process of a communication method provided in another embodiment of the present application.

[0144] In step S1500, after the Non-AP STA is powered on, it first enters passive scanning mode and listens for beacons on supported links. The Non-AP STA then enters active scanning mode and actively sends normal probe request frames on each link. The UHR AP MLD receives the normal probe request frame and controls the EHT AP MLD LMAC to return a normal probe response. The sending and receiving addresses of the normal probe frame are set to the link-bound address to avoid misunderstandings on other links on the same frequency. Therefore, the TA of the probe response frame is filled in with the Link Mac Address of the EHT AP MLD LMAC, and the RA is filled in with the Link Mac Address of the Non-AP STA.

[0145] In step S1510 , after completing the scan, the Non-AP STA integrates all the scan results and selects the best link to initiate Multi-Link access.

[0146] In step S1520, the Non-AP STA sends a Multi-Link Probe Request frame. Address 1 (Addr1) and Address 3 (Addr3) in the Probe Request frame are filled with the Link Mac Address of the optimal EHT AP MLD selected after the scan. At the same time, the STA Control in the Link Info carries information about other links.

[0147] In step S1530 , the UHR AP MLD generates a Multi-Link Probe Response based on the received Multi-Link Probe Request and through the received Link, and replies with relevant information on the corresponding Link.

[0148] In step S1540, the Non-AP STA MLD initiates a Multi-Link Authen Request, carrying information of other links associated with the request.

[0149] In step S1550 , the UHR AP MLD replies with a Multi-Link Authen Response on the received Link.

[0150] In step S1560, the Non-AP STA MLD initiates a Multi-Link Assoc Request and carries other link information.

[0151] In step S1570 , the UHR AP MLD responds with a Multi-Link Assoc Response on the received Link and responds with an association success or failure on the Link requested by the corresponding Non-AP STA.

[0152] In step S1580, the Non-AP STA MLD and the UHR AP MLD perform 802.1X authentication on the received Link.

[0153] In step S1590, the non-AP STA MLD and the UHR AP MLD perform a four-way handshake key negotiation on the current link. The PTK is calculated according to the UMAC address of the UHR AP MLD, and the GTK, IGTK, and BIGTK are calculated according to the EHT AP MLD Link Address. The GTK, IGTK, and BIGTK of the links under all EHT AP MLDs belonging to the same UHR AP MLD are sent to the non-AP STA MLD.

[0154] FIG11 shows a schematic structural diagram of a KDE field of key information of a multicast key in a communication method provided by an embodiment of the present application.

[0155] For each associated link, the broadcasts exchanged between the UHR AP MLD and the non-AP STA MLD use different multicast keys, such as GTK, IGTK, and BIGTK. That is, the multicast keys are calculated at the link level. For example, GTK, IGTK, and BIGTK are calculated using the LMAC address of each link on the AP side.

[0156] As shown in Figure 11, the multicast key is generated based on the LMAC address corresponding to each link on the AP side. In order to ensure the execution of the 4-step handshake in the network access process, the embodiment of the present application extends the EAPOK key KDE (for example, GTK KDE, IGTK KDE, and BIGTK KDE) with new fields, such as the APMLD identifier (AP MLD ID) field. The AP MLD identifier field is used to identify the AP MLD corresponding to the link identifier (Link ID). Therefore, under the co-located UHR AP MLD architecture, the AP MLD identifier field combined with the link identifier field can distinguish the same-frequency links of different AP MLDs.

[0157] FIG12 shows a schematic structural diagram of the FTE field of the FT protocol of the key information of the multicast key in the communication method provided in an embodiment of the present application.

[0158] Similarly, to ensure the execution of the four-step handshake during the network access process, the embodiments of the present application similarly extend the FTE field of the FT protocol, for example, by adding an AP MLD identification field to the MLOGTK sub-element, MLO IGTK sub-element, and MLO BIGTK sub-element. This AP MLD identification field, combined with the Link ID Info field, can distinguish intra-frequency links with different AP MLDs.

[0159] FIG13 shows a flow chart of a communication method in a wireless local area network provided in an embodiment of the present application.

[0160] As shown in FIG13 , the communication method in the wireless local area network may include the following steps:

[0161] S210, the UHR access point multi-link logical entity sends a first frame to the non-access point multi-link logical entity, wherein the first frame includes first link identification information, and the first link identification information is used to indicate the target link of the first access point multi-link logical entity (i.e., the target access point multi-link logical entity, such as the target AP MLD) to which the non-access point multi-link logical entity switches.

[0162] In some embodiments, the UHR access point multi-link logical entity may be a UHR non-co-located multi-access point multi-link logical entity.

[0163] In some embodiments, the UHR access point multi-link logical entity may be a UHR AP MLD. The UHR access point multi-link logical entity includes a first access point multi-link logical entity (e.g., EHT AP MLD2, hereinafter referred to as AP MLD2) and a second access point multi-link logical entity (e.g., EHT AP MLD1, hereinafter referred to as AP MLD1) attached to the UHR AP MLD. The second access point multi-link logical entity includes multiple links (e.g., Link0 and Link1) associated with a non-access point multi-link logical entity (e.g., non-AP STA MLD, hereinafter referred to as STA MLD).

[0164] It can be understood that the UHR access point multi-link logical entity sends frames to the non-access point multi-link logical entity through the access point multi-link entity associated with the non-access point multi-link logical entity in the UHR access point multi-link logical entity (i.e., the second access point multi-link logical entity, or the original AP MLD, the service AP MLD), or it can also be sent through the UHR control module (for example, the non-co-located control module) in the UHR access point multi-link logical entity, or the UHR control module instructs the second access point multi-link logical entity to send.

[0165] In some embodiments, the UHR control module may be a UHR AP MLD UMAC, or may be other hardware or software, basic or independent control devices.

[0166] In some embodiments, the first frame is used to indicate a roaming reconfiguration.

[0167] In some embodiments, the first frame may be a BTM roaming frame. For example, the first frame may be a BTM Roaming Reconfigure frame.

[0168] In some embodiments, the BTM roaming reconfiguration frame may include a UHR mobility field element, which is used to indicate whether the UHR multi-link logical entity has seamless transition capability.

[0169] Optionally, the target link includes one or more links associated with the non-access point multi-link logical entity and the second access point multi-link logical entity.

[0170] In some embodiments, the UHR access point multi-link logical entity sending the first frame to the non-access point multi-link logical entity may include:

[0171] The second access point multi-link logical entity sends a first frame to the non-access point multi-link logical entity;

[0172] The first access point multi-link logical entity sends a first frame to the non-access point multi-link logical entity; or

[0173] The UHR control module instructs the sending of the first frame to the non-access point multi-link logical entity.

[0174] In some embodiments, the target link of the non-access point multi-link logical entity switching to the first access point multi-link logical entity may mean that the non-access point multi-link logical entity expects to disconnect the target link (e.g., Link0) from the second access point multi-link logical entity (i.e., the original AP MLD, e.g., AP MLD1), and expects to associate the target link with the first access point multi-link entity (i.e., the target AP MLD, e.g., AP MLD2) attached to the same UHR AP LMD.

[0175] Optionally, the first link identification information includes logical entity identification information of the first access point multi-link logical entity and link information of the target link.

[0176] Optionally, the first link identification information may be carried in a common information field in a BTM roaming frame.

[0177] Optionally, the logical entity identification information of the first access point multi-link logical entity may be the MLD AP identifier of the first access point multi-link logical entity. Optionally, the link information of the target link may include at least one of the number of links, link identifiers, link switching order, and link priority.

[0178] Optionally, the common information field may include an MLD AP ID field and a link information field, wherein the MLD AP ID field is used to indicate the MLD AP ID of the first access point multi-link logical entity to be switched to, and the link information field is used to indicate link information of the target link.

[0179] Optionally, the link information field may include a link number (Link Num) field and one or more link identification (Link ID) fields.

[0180] In some embodiments, the first frame may include a first indication for indicating a switching mode (eg, a disconnection mode, a deletion mode) of the target link.

[0181] Optionally, the first indication may be carried in the STA control field in the BTM roaming frame.

[0182] Optionally, the switching mode may be immediate switching.

[0183] Optionally, the switching mode may be delayed switching. Optionally, in this case, the first indication may further indicate a delay duration of the delayed switching.

[0184] In a specific embodiment, the first indication is used to indicate a link deletion mode, or a link deletion mode and a link deletion count, so that delayed disconnection can be achieved.

[0185] In some embodiments of the present application, before the UHR access point multi-link logical entity sends the first frame to the non-access point multi-link logical entity, the method 200 further includes:

[0186] The non-access point multi-link logical entity sends a second frame to the UHR access point multi-link logical entity, wherein the second frame is used to initiate a roaming request.

[0187] In some embodiments, the non-access point multi-link logical entity sending the second frame to the UHR access point multi-link logical entity may include:

[0188] The non-access point multi-link logical entity sends a second frame to the second access point multi-link logical entity; or

[0189] The non-access point multi-link logical entity sends the second frame to the first access point multi-link logical entity.

[0190] In some embodiments, the second frame includes second link identification information, where the second link identification information is used to indicate the link of the access point multi-link logical entity to which the non-access point multi-link logical entity requests to be switched.

[0191] For example, after receiving the second frame, the UHR access point multi-link logical entity obtains the first access point multi-link logical entity to which the non-access point multi-link logical entity expects to switch the target link from the second access point multi-link logical entity. Therefore, the UHR AP MLD UMAC can instruct (including indirectly instructing or directly controlling) to disconnect the association between the second access point multi-link logical entity and the target link, and instruct (including indirectly instructing or directly controlling) the first access point multi-link logical entity to associate with the target link, that is, the first access point multi-link logical entity is associated with the non-access point multi-link logical entity through the target link.

[0192] Optionally, the second frame may be a BTM roaming request frame.

[0193] Optionally, the second link identification information may be carried in a common information field in a BTM roaming request frame.

[0194] Optionally, the common information field of the BTM roaming request frame may include an MLD AP ID field and a link information field, wherein the MLD AP ID field is used to indicate the MLD AP ID of the access point multi-link logical entity to which the non-access point multi-link logical entity requests handover, and the link information field is used to indicate link information of the link to which the non-access point multi-link logical entity requests handover. Optionally, the link information may include at least one of the number of links, link identifiers, link handover order, and link priority.

[0195] Optionally, the BTM roaming request frame may further include a UHR mobility field element, which is used to indicate whether the non-access point multi-link logical entity has UHR wireless transition capability.

[0196] Optionally, the first link identification information may be determined based on the second link identification information.

[0197] In some embodiments of the present application, after the UHR access point multi-link logical entity sends the first frame to the non-access point multi-link logical entity, the method 200 further includes:

[0198] The UHR control module instructs the second access point multi-link logical entity to disconnect from the target link, and the second access point multi-link logical entity to associate with the target link.

[0199] For example, during wireless roaming, the UHR AP MLD UMAC can indirectly instruct or directly control the second access point multi-link logical entity to disconnect from the target link (e.g., Link0), and indirectly instruct or directly control the first access point multi-link logical entity to establish an association with the target link, thereby completing the link switching on the AP side.

[0200] In some embodiments, the UHR AP MLD UMAC can also share or copy the unicast key stored in the UHR AP MLD UMAC obtained based on the UMAC address of the UHR AP MLD to the first access point multi-link logical entity, so that when the link is switched during wireless roaming, the non-access point multi-link logical entity and the first access point multi-link logical entity no longer need to handshake and negotiate the unicast key, thereby reducing the frame overhead during the roaming process and reducing the delay of the roaming process.

[0201] In some embodiments of the present application, the method 200 further includes:

[0202] When a preset condition is met, the UHR access point multi-link logical entity determines that the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity.

[0203] In some embodiments, the preset condition is used to indicate whether both the non-access point multi-link logical entity and the UHR access point multi-link logical entity have completed configuration preparation for link switching.

[0204] In some embodiments, the preset condition includes at least one of the following:

[0205] The UHR access point multi-link logical entity receives a fourth frame from the non-access point multi-link logical entity;

[0206] A preset time has passed since the UHR access point multi-link logic entity sent the first frame.

[0207] Optionally, the fourth frame includes fourth link identification information, and the fourth link identification information corresponds to the first link identification information.

[0208] Optionally, the fourth frame may be a BTM Roaming Confirm frame.

[0209] In some embodiments, after the UHR access point multi-link logical entity sends the first frame, if no notification of link reconfiguration failure is received from the non-access point multi-link logical entity within a preset time, the link reconfiguration of the non-access point multi-link logical entity is considered to be retransmitted.

[0210] In some embodiments, the fourth frame may include a fourth indication for indicating whether the non-access point multi-link logical entity has completed the operation requested in the first frame.

[0211] Optionally, the fourth indication may be carried in a status code field in a BTM roaming frame.

[0212] In some embodiments, after the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the method further includes:

[0213] The UHR access point multi-link logical entity sends the buffered downlink data to the non-access point multi-link logical entity, wherein the buffered downlink data is the downlink data buffered on the target link before the handover.

[0214] In some implementations, the UHR access point multi-link logical entity sending the buffered downlink data to the non-access point multi-link logical entity includes:

[0215] The UHR access point multi-link logical entity sends the buffered downlink data to the non-access point multi-link logical entity through the second access point multi-link logical entity; and / or

[0216] The second access point multi-link logical entity sends the buffered downlink data to the first access point multi-link logical entity, and the first access point multi-link logical entity sends the buffered downlink data to the non-access point multi-link logical entity.

[0217] For example, after the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the UHR access point multi-link logical entity can send the downlink data buffered on the target link before the switch to the non-access point multi-link logical entity through the original AP MLD. For example, after the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the UHR control module can send the downlink data buffered on the target link before the switch through at least one associated link other than the target link after the switch, wherein the at least one associated link is a link other than the target link associated between the non-access point multi-link logical entity and the second access point multi-link logical entity.

[0218] For example, after the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the UHR access point multi-link logical entity can send the downlink data cached on the target link before the switch to the target AP MLD through the original AP MLD, and then the target AP MLD sends the cached downlink data to the non-access point multi-link logical entity.

[0219] In some embodiments, the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, which may include: the target link to be switched, which is associated with the non-access point multi-link logical entity, has completed the disconnection from the second access point multi-link logical entity and the association with the first access point multi-link logical entity on the UHR access point multi-link logical entity side.

[0220] The UHR control module instructing that the cached downlink data for the target link before the switching be sent through at least one associated link other than the target link after the switching may mean that: due to the at least one or more links having completed the switching on the UHR AP MLD side, the cached downlink data before the switching needs to continue to be sent to the non-access point multi-link logical entity through other still associated links of the second access point multi-link logical entity. The new data obtained by the UHR AP MLD for sending to the non-access point multi-link logical entity may be sent by the UHR AP MLD UMAC to the newly associated first access point multi-link logical entity through the newly associated link.

[0221] In some embodiments, the UHR control module instructs the buffered downlink data for the target link before the switching to be sent through at least one associated link other than the target link after the switching, including:

[0222] The UHR control module enables the buffered downlink data to be accessible to the at least one associated link other than the switched target link; and the UHR control module instructs the buffered downlink data to be sent through the at least one associated link.

[0223] In some embodiments, the UHR control module enables the cached downlink data to be accessible to the at least one associated link other than the switched target link, including:

[0224] The UHR control module instructs the cached downlink data to be shared or copied to the at least one associated link other than the switched target link;

[0225] The UHR control module instructs the cached downlink data to be sent to an external storage device, wherein the at least one associated link is communicatively connected to the external storage device; and / or

[0226] The UHR control module instructs to send the buffered downlink data to the UHR control module.

[0227] For example, the UHR control module may instruct the access point multi-link logical entity that buffers the downlink data to transmit the corresponding downlink data back to the UHR control module, and the UHR control module instructs other access point multi-link logical entities associated with non-access point multi-link logical entities to continue forwarding the downlink data.

[0228] Additionally or alternatively, the UHR control module may instruct the access point multi-link logical entity that buffers the downlink data to allow other links associated with non-access point multi-link logical entities to continue sending the corresponding downlink data by directly sending, sharing, or copying.

[0229] Additionally or alternatively, the UHR control module may instruct the access point multi-link logical entity that caches the downlink data to send the cached downlink data to an external storage device (e.g., a cloud server or a local server), and the external storage device may continue to send the cached downlink data to the non-access point multi-link logical entity.

[0230] In some embodiments, after the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the method further includes:

[0231] The UHR control module instructs the second access point multi-link logical entity to preferentially receive uplink data from the non-access point multi-link logical entity through the switched target link.

[0232] In some embodiments, after the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the method further includes:

[0233] The UHR control module instructs to send data received after the target link is switched and whose target address is the non-access point multi-link logical entity to the non-access point multi-link logical entity through the switched target link.

[0234] In some embodiments, after the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the method 200 further includes:

[0235] The UHR access point multi-link logical entity sends a fifth frame to the non-access point multi-link logical entity, where the fifth frame includes fifth link identification information;

[0236] The fifth link identification information is used to indicate that one or more remaining links of the non-access point multi-link logical entity are switched to the associated first access point multi-link logical entity, and the one or more remaining links include one or more links other than the target link among the links associated with the non-access point multi-link logical entity and the second access point multi-link logical entity.

[0237] In some embodiments, the fifth frame may be a BTM roaming reconfiguration frame, which is used to complete roaming switching of all links of the non-access point multi-link logical entity.

[0238] In some embodiments, the fifth frame can be sent by the UHR access point multi-link logical entity through the access point multi-link logical entity of the remaining unswitched link (for example, the second access point multi-link logical entity), or it can be sent through the access point multi-link logical entity corresponding to the target link (that is, the first access point multi-link logical entity).

[0239] In some embodiments of the present application, the method 200 further includes:

[0240] The UHR access point multi-link logical entity determines first key information of the UHR access point multi-link logical entity according to an upper media access control (UMAC) address of the UHR access point multi-link logical entity. The first key information may include unicast key information, such as PTK.

[0241] In some embodiments, the first key information may be generated by the UHR control module.

[0242] In some embodiments, the first key information is stored in the UHR control module.

[0243] In some embodiments, the method further comprises:

[0244] The UHR control module shares, copies or sends the first key information to the first access point multi-link logical entity for use in associated links of the first access point multi-link logical entity.

[0245] In some embodiments, the first key information can be shared, copied or sent by the UHR control module to multiple access point multi-link logical entities during the network access stage, and can also be shared, copied or sent to the access point multi-link logical entity to be switched to, such as the first access point multi-link logical entity, during the link switching process of the AP MLD during wireless roaming.

[0246] In some embodiments, the first key information is calculated based on the UHR AP MLD UMAC address, for example, the PTK key information is calculated based on the UHR AP MLD UMAC address.

[0247] In some embodiments, the method further comprises:

[0248] The UHR access point multi-link logical entity sends the unicast key information of the UHR access point multi-link logical entity to the non-access point multi-link logical entity;

[0249] The UHR access point multi-link logical entity sends the multicast key information of one or more links of the first access point multi-link logical entity to the non-access point multi-link logical entity.

[0250] In some embodiments of the present application, the method further includes:

[0251] The UHR access point multi-link logical entity determines multicast key information of one or more links of the first access point multi-link logical entity according to one or more lower media access control LMAC addresses of the first access point multi-link logical entity.

[0252] In some embodiments, the multicast key information may include a fifth indication, where the fifth indication is used to indicate link information corresponding to the multicast key information.

[0253] In some embodiments, the fifth indication may be carried in the AP MLD ID field in the MLO GTK KDE, MLO IGTK KDE, and MLO BIGTK KDE fields.

[0254] In some embodiments, the type of the multicast key information may include at least one of a group temporary key (GTK), an integrated group temporary key (IGTK), and a beacon integrated group temporary key (BIGTK).

[0255] In some embodiments of the present application, before the non-access point multi-link logical entity sends the second frame to the UHR access point multi-link logical entity, the method 200 further includes:

[0256] The UHR access point multi-link logical entity sends a ninth frame to the non-access point multi-link logical entity, where the ninth frame is configured to request the non-access point multi-link logical entity to send the second frame.

[0257] Optionally, the ninth frame may be a BTM roaming inquiry frame. The BTM roaming inquiry frame is used to induce or request the non-access point multi-link logical entity to send a BTM roaming request frame.

[0258] In some embodiments of the present application, before the UHR access point multi-link logical entity sends the first frame to the non-access point multi-link logical entity, the method 200 further includes:

[0259] The UHR access point multi-link logical entity sends a sixth frame to the non-access point multi-link logical entity, where the sixth frame is used to indicate that the UHR access point multi-link logical entity has a seamless transition capability.

[0260] In some embodiments, the sixth frame includes a UHR mobility domain element, where the UHR mobility domain element is used to indicate that the UHR access point multi-link logical entity has seamless transition capability.

[0261] In some embodiments, the sixth frame may include at least one of the following:

[0262] Beacon Frame, Probe Response Frame, Association Request Frame, Association Response Frame, and Authentication Frame are used to announce the seamless transition capability of the UHR AP MLD (e.g., to a non-access point multi-link logical entity).

[0263] In some embodiments, the non-access point multi-link logical entity may decide to start roaming by the non-access point multi-link logical entity itself. For example, the non-access point multi-link logical entity decides to start roaming according to the current link status.

[0264] In other embodiments, the decision of the non-access point multi-link logical entity to start roaming may also be made by the UHR access point multi-link logical entity. For example, the second access point multi-link logical entity may trigger the non-access point multi-link logical entity to start roaming based on the uplink signal quality of the non-access point multi-link logical entity.

[0265] In some embodiments, the target link may be determined by a non-access point multi-link logical entity, for example, by a multi-access point multi-link logical entity according to uplink signal qualities sent by multiple access point multi-link logical entities of a UHR access point multi-link logical entity.

[0266] In some embodiments, the method further comprises:

[0267] The non-access point multi-link logical entity sends a seventh frame to a plurality of access point multi-link logical entities of the UHR access point multi-link logical entity; and

[0268] The non-access point multi-link logical entity receives an eighth frame sent by multiple access point multi-link logical entities of the UHR access point multi-link logical entity, where the eighth frame is used to determine the first access point multi-link logical entity.

[0269] In some embodiments, the non-access point multi-link logical entity sends a seventh frame on multiple links associated with the UHR access point multi-link logical entity respectively; the non-access point multi-link logical entity receives multiple eighth frames from the UHR access point multi-link logical entity in response to the seventh frame; and then the non-access point multi-link logical entity determines the target link of the first access point multi-link logical entity to switch to based on the multiple eighth frames.

[0270] Optionally, the seventh frame may be a probe request frame, and the eighth frame may be a probe response frame.

[0271] In some embodiments, the non-access point multi-link logical entity determines the target link of the first access point multi-link logical entity based on the multiple eighth frames, including: the non-access point multi-link logical entity determines multiple signal qualities of multiple links corresponding to the multiple eighth frames respectively based on the multiple eighth frames; and the non-access point multi-link logical entity determines the target link of the first access point multi-link logical entity based on the multiple signal qualities.

[0272] In some embodiments, the UHR access point multi-link logical entity (e.g., a UHR control module) may provide a recommended target link set and link priority for a non-access point multi-link logical entity, wherein the link priority may be determined based on the link load of an adjacent access point multi-link logical entity of the second access point multi-link logical entity. Furthermore, the UHR access point multi-link logical entity (e.g., a UHR control module) may inform the non-access point multi-link logical entity of the target link set and link priority, and the non-access point multi-link logical entity may determine the target link based on the target link set and link priority in combination with the signal quality of the link (e.g., obtained through a probe response frame).

[0273] In some embodiments, before the non-access point multi-link logical entity sends the second frame to the UHR access point multi-link logical entity, the method further includes:

[0274] The non-access point multi-link logical entity receives a third frame from the UHR access point multi-link logical entity, where the third frame includes third link identification information, and the third link identification information is used to indicate the candidate access point multi-link logical entity and / or candidate link to which the UHR access point multi-link logical entity recommends that the non-access point multi-link logical entity switch.

[0275] In some embodiments, the third frame includes a candidate list field, wherein the candidate list field includes at least one sub-element, each sub-element corresponds to a candidate access point multi-link logical entity, and each sub-element is used to indicate one or more candidate links of the corresponding candidate access point multi-link logical entity;

[0276] The sub-element includes at least one of the following fields:

[0277] The first field is used to indicate the address information of the candidate access point multi-link logical entity;

[0278] The second field is used to indicate whether to recommend the non-access point multi-link logical entity to switch to all candidate links of the candidate access point multi-link logical entity; or

[0279] The third field is used to indicate one or more candidate links of the candidate access point multi-link logical entity to which handover is recommended.

[0280] Optionally, the third field may indicate one or more recommended candidate links in a bitmap manner.

[0281] The structure of the third frame is further described below with reference to FIG. 19 to FIG. 21 .

[0282] In some embodiments, the neighboring access point multi-link logical entity of the second access point multi-link logical entity can evaluate the uplink signal quality, for example, obtain the signal quality of the corresponding link through a detection request frame, and further report the signal quality of the link to the UHR control module. The UHR control module can determine the target link based on the signal quality and link load of the link.

[0283] To facilitate understanding of the embodiments of the present application, the following description uses two AP MLDs and two associated links as an example. In other embodiments, there may be more than two AP MLDs and / or more than two associated links. Those skilled in the art will appreciate that in other embodiments of the present application, for situations with more than two AP MLDs and / or more than two associated links, there are further possible link switching methods.

[0284] FIG14 is a schematic flowchart of a communication method provided in an embodiment of the present application.

[0285] In this embodiment, the UHR AP MLD includes a first access point multi-link logical entity (e.g., EHT AP MLD2, hereinafter referred to as AP MLD2) and a second access point multi-link logical entity (e.g., EHT AP MLD1, hereinafter referred to as AP MLD1) attached to the UHR AP MLD. The second access point multi-link logical entity includes multiple links (e.g., Link0 and Link1) associated with a non-access point multi-link logical entity (e.g., non-AP STA MLD, hereinafter referred to as STA MLD).

[0286] It is understood that Link0 and Link1 have different frequency bands or different channels in the same frequency band. For example, the frequency band of Link0 can be 2.4 GHz and the frequency band of Link1 can be 5 GHz, or the frequency band of Link0 can be 5 GHz and the frequency band of Link1 can be 2.4 GHz. In some embodiments, Link2 can be associated with MLD1 and STA MLD, and its frequency band can be, for example, 6 GHz.

[0287] As shown in FIG14 , the wireless communication method may include the following steps:

[0288] Step S900: Receive a second frame from the STA MLD.

[0289] Specifically, the second frame may be a BTM Roaming Request frame, which includes indication information indicating the AP MLD to be switched to and the link to be switched.

[0290] The BTM roaming request may also include a mobility domain element to indicate whether the STA MLD has UHR seamless transition capability.

[0291] Step S910: Switch the link with the STA MLD from AP MLD1 to AP MLD2, and disconnect AP MLD1 from the link.

[0292] Specifically, after receiving the second frame, the UHR AP MLD obtains the new AP MLD (i.e., AP MLD2) to which the STA MLD expects Link0 to be switched from the original AP MLD (i.e., AP MLD1). Therefore, the UHR AP MLD disconnects AP MLD1 from Link0 and associates AP MLD2 with Link0. That is, AP MLD2 is associated with the STA MLD via Link0.

[0293] In this embodiment, the UHR AP MLD may obtain the second frame from the non-AP STA MLD through AP MLD1.

[0294] Step S940: Send the buffered downlink data for STA MLD before link switching through an associated link other than Link0; and send the new downlink data for STA MLD received after link switching through the switched link.

[0295] After the UHR AP MLD completes the switching of Link 0 in the above steps, the UHR AP MLD continues to send the downlink data buffered before the switching for the non-AP STA MLD to the non-AP STA MLD through an associated link other than Link 0 (for example, Link 1). Specifically, the UHR AP MLD sends the downlink data buffered before the switching and originally transmitted to the non-AP STA MLD through Link 0 before the switching through other links that are still associated with the non-AP STA MLD. These still associated links include the link that MLD1 and the non-AP STA MLD maintain an association with and the link that MLD2 and the non-AP STA MLD maintain an association with.

[0296] In addition, the UHR AP MLD sends the newly received downlink data for the non-AP STA MLD after the switch to the non-AP STA MLD through the switched Link0.

[0297] By continuing to send data to the non-AP STA MLD after the handover, data can be sent to the non-AP STA MLD uninterruptedly before and after the handover, ensuring the continuity of data transmission during seamless roaming and the transmission reliability of wireless communication.

[0298] Step S960: Send the first frame to the STA MLD.

[0299] After completing the link switch, the UHR AP MLD sends the first frame to the STA MLD to notify the STA MLD.

[0300] In some embodiments, the first frame may be a BTM Roaming Reconfigure frame.

[0301] In some embodiments, the BTM Roaming Reconfiguration frame includes a UHR Mobility Field element to indicate whether the UHR AP MLD has seamless transition capability.

[0302] In some embodiments, the UHR AP MLD may send the first frame to the non-AP STA MLD through the originally associated AP MLD1, or through other links associated with the non-AP STA MLD, or directly through the UHR AP MLD UMAC.

[0303] In this embodiment, during the network access phase, UHR AP MLD UMAC has shared or copied the unicast key for AP MLD2 generated during the network access process to AP MLD 1. Therefore, during seamless roaming, UHR AP MLD UMAC does not need to share the unicast key with AP MLD1.

[0304] Alternatively, in another embodiment, during the network access phase, the UHR AP MLD UMAC does not share or copy the unicast key for AP MLD2 generated during the network access process phase to AP MLD 1. Therefore, during seamless roaming, optionally, before step S960, the UHR AP MLD UMAC needs to share or copy the stored unicast key to the AP MLD after the switch (i.e., MLD 1) to complete the link switch on the UHR AP MLD side. This avoids the need to re-perform the four-way handshake for the key when the non-AP STA MLD switches to the new AP MLD during roaming, thereby reducing the frame overhead during roaming and shortening the roaming latency.

[0305] Step S980: Receive the fourth frame from the STA MLD.

[0306] After receiving the first frame, the STA MLD adjusts the link management for sending and receiving uplink data and downlink data from the UHR AP MLD accordingly (for example, the STA MLD disconnects from the AP MLD1 on Link0) to achieve seamless roaming.

[0307] The internal configuration adjustment step in the non-AP STA MLD includes adjusting the AP MLD identifier in the field corresponding to the multicast key so that the multicast key automatically corresponds to the corresponding link of the AP MLD after the switch. This prevents confusion between same-frequency links of different AP MLDs and saves the frame overhead of re-handshake.

[0308] After the non-AP STA MLD adjustment configuration is completed, the fourth frame is sent to the UHR AP MLD. The fourth frame can be a BTM Roaming Confirm frame.

[0309] In other embodiments, after the non-AP STA MLD completes configuration adjustment, the non-AP STA MLD may not send a fourth frame. Instead, the non-AP STA MLD and the UHR AP MLD determine whether the handover configuration has been completed based on a specified time period. That is, after a specified time period after the UHR AP MLD sends the first frame, the non-AP STA MLD is assumed to have completed the handover. If the configuration cannot be completed within the specified time period, a notification is sent to the other party to inform them of the handover failure.

[0310] In other embodiments, additionally, after the switching of one or a group of links between the non-AP STA MLD and the original AP MLD of the UHR AP MLD is completed, the switching of the remaining links between the non-AP STA MLD and the original AP MLD is completed according to similar method steps, which will not be repeated in this document.

[0311] In other embodiments, the EHT AP MLD attached to the UHR AP MLD may further include a corresponding EHT AP MLD UMAC, and the EHT AP MLD UMAC is configured to directly communicate with the DS to be compatible with other communication networks (eg, Wi-Fi 7).

[0312] FIG15 is a schematic diagram showing a portion of a wireless roaming process in a communication method provided in an embodiment of the present application. As shown in FIG15 , the process may include the following steps:

[0313] In step S1300 , the following associations are established in the network access process: Link0 of the non-AP STA MLD (hereinafter referred to as STA MLD) is associated with Link0 of the EHT AP MLD1 (hereinafter referred to as AP MLD1), and Link1 of the STA MLD is associated with Link1 of the EHT AP MLD1.

[0314] It can be understood that the association between Link0 of STA MLD and Link0 of MLD1 means that both ends of link Link0 are associated with STA MLD and AP MLD1 respectively.

[0315] Step S1310: The STA MLD decides whether to roam based on the current link status.

[0316] In some embodiments, the current link status may include at least one of the following:

[0317] Signal quality of the link associated with AP MLD1 and STA MLD;

[0318] The distance between the AP MLD and the STA MLD of the currently associated link.

[0319] AP MLD load status of the currently associated link;

[0320] Current link load.

[0321] Optionally, the link status may further include other parameters that affect the signal quality of the associated link between the AP MLD and the STA MLD, which is not limited in this application.

[0322] In other embodiments, the UHR AP MLD (e.g., the UHR AP UMAC, AP MLD1, or AP MLD2) may decide whether the STA MLD roams, or induce the STA MLD to initiate roaming. For example, the UHR AP UMAC may send a BTM roaming query frame to the STA MLD based on the link status of the STA MLD's associated link to induce the STA MLD to decide to roam.

[0323] In step S1320, in the overlapping signal coverage area, the STA MLD simultaneously or sequentially uses all of its links to send a probe request frame to a neighboring AP MLD (e.g., AP MLD2). Each neighboring AP MLD is connected to the same UHR AP MLD UMAC, or in other words, is affiliated with the same UHR AP MLD. Each AP MLD (e.g., AP MLD2) responds to the probe request frame from the STA MLD with a probe response frame.

[0324] In step S1330 , the STA MLD determines the link status of each link according to the probe response frame returned by each link, and determines the target AP MLD (eg, AP MLD2 ) to be switched to according to the link status of each link.

[0325] Optionally, the link status may include at least one of the signal quality of the link between the AP MLD and the STA MLD determined according to the probe response frame, the distance between the AP MLD and the STA MLD, the load condition of the AP MLD, and the load condition of the link.

[0326] Optionally, in S1330, STA MLD may also determine the link switching order during seamless roaming to AP MLD2. For example, Link0 is first switched from AP MLD1 to AP MLD2, that is, STA MLD disconnects from Link0 of AP MLD1 and disconnects from Link0 of AP MLD2.

[0327] Figure 16 shows the remaining flow diagram of the seamless roaming process shown in Figure 15. As shown in Figure 16, the wireless roaming process may further include the following steps:

[0328] In step S1340, the STA MLD selects a suitable link from the associated links as the target link to be switched. It then sends a BTM roaming request frame to the original AP MLD associated with the target link (i.e., AP MLD1). The BTM roaming request frame may carry the AP MLD information and link information corresponding to the target link. The BTM roaming request frame is used to request switching from the original link (e.g., AP MLD1 Link0) to the target link (e.g., AP MLD2 Link0).

[0329] Optionally, after determining the target link, the STA MLD may send identification information indicating the AP MLD to be switched to and link information of the target link to be switched to the UHR AP MLD. For example, it may be sent to any associated AP MLD attached to the UHR AP MLD (for example, the AP MLD originally associated with the target link), or it may be sent to the UHR AP MLD UMAC.

[0330] Step S1350: The UHR AP MLD instructs (indirectly instructs or directly controls) link switching on the AP MLD side, specifically including the following steps:

[0331] 1) The original AP MLD (i.e., AP MLD1) transmits the STA MLD's roaming request back to the UHR AP MLD UMAC (hereinafter referred to as UHR UMAC). The UHR UMAC approves or rejects the roaming request based on the link status (e.g., load status) of the target link (Link0) of the target AP MLD (MLD2) and notifies the original AP MLD of the approval or rejection result.

[0332] 2) When the UHR UMAC approves the roaming request, the original AP MLD sends a BTM roaming reconfiguration frame to the STA MLD via the corresponding receiving link.

[0333] 3) When STA MLD receives the BTM roaming reconfiguration frame, it triggers link reconfiguration of the corresponding link (Link0) of STA MLD (i.e., link switching on the non-AP side, for example, switching from associating STA MLD Link0 with AP MLD1 Link0 to associating STA MLD Link0 with AP MLD2 Link0).

[0334] 4) After STA MLD completes link reconfiguration, it sends a BTM roaming confirmation frame to AP MLD2 through the switched link (from Link0 of STA MLD to Link0 of AP MLD2) to notify the UHR AP MLD that STA MLD has successfully completed link reconfiguration.

[0335] Step S1360 : After receiving the BTM roaming confirmation frame from the STA MLD, the UHR AP MLD UMAC updates the configuration of the target link (Link 0 ).

[0336] Specifically, the UHR AP MLD may give priority to transmitting the newly received downlink data after the link switching through the newly associated Link0 between the STA MLD and the AP MLD2. Before the link is successfully switched, the cached downlink data cached by the UHR AP MLD and originally used to be sent to the STA MLD through the Link0 before the switching can continue to be sent through the remaining associated links between the UHR AP MLD and the STA MLD (i.e., the unswitched associated links). These cached downlink data can be set by the UHR UMAC to be accessible to the AP MLD corresponding to the remaining associated links. Through such a setting, in the STA MLD roaming process, the transmission of downlink data will not be interrupted due to roaming switching, thereby ensuring the continuity of data transmission during the roaming process and improving the data transmission reliability of wireless roaming.

[0337] In some other embodiments, relative to step S1350 and step S1360, alternatively, the communication method may include the following steps:

[0338] In step S1352, the UHR AP MLD controls link switching on the AP side, specifically including the following steps:

[0339] 1) The original AP MLD (i.e., AP MLD1) returns the STA MLD's roaming request to the UHR UMAC. The UHR UMAC approves or rejects the roaming request based on the link status (e.g., load status) of the target link (Link0) of the target AP MLD (i.e., AP MLD2) and notifies the original AP MLD of the approval or rejection result.

[0340] 2) When the UHR UMAC approves the roaming request, the original AP MLD sends a BTM roaming reconfiguration frame to the STA MLD via the corresponding receiving link. The UHR AP MLD UMAC updates the configuration of the target link (Link 0). The UHR AP MLD preferentially transmits data over the new link between Link 0 of the STA MLD and Link 0 of MLD2.

[0341] 3) When STA MLD receives the BTM roaming reconfiguration frame, it triggers link reconfiguration of the corresponding link (Link0) of STA MLD (i.e., link switching on the non-AP side, for example, switching from associating STA MLD Link0 with AP MLD1 Link0 to associating STA MLD Link0 with AP MLD2 Link0).

[0342] 4) After STA MLD completes link reconfiguration, it sends a BTM roaming confirmation frame to AP MLD2 through the switched link (from Link0 of STA MLD to Link0 of AP MLD2) to notify the UHR AP MLD that STA MLD has successfully completed link reconfiguration.

[0343] In some other embodiments, for the above step 4), alternatively:

[0344] 4a) STA MLD sends a BTM roaming confirmation frame to AP MLD2, indicating whether STA MLD's Link 0 is reconfigured successfully. If STA MLD's Link 0 is reconfigured successfully, STA MLD sends a BTM roaming confirmation frame to AP MLD2 over the switched link (from STA MLD's Link 0 to AP MLD2's Link 0) to notify the UHR AP MLD that STA MLD has successfully completed the reconfiguration.

[0345] In some other embodiments, after the above step 4), optionally, the communication method further includes:

[0346] 5a) When the UHR AP MLD does not receive the BTM roaming confirmation frame sent by the STA MLD after a preset time interval, it confirms that the STA MLD has successfully completed the reconfiguration.

[0347] During seamless roaming, links other than Link0 of the STA MLD (eg, Link1) maintain connection and communication with the AP MLD1.

[0348] Step S1370: Complete the handover of the remaining links between the STA MLD and the original AP MLD. For example, the following steps may be included:

[0349] 1) UHR AP MLD UMAC determines to switch the remaining links. Optionally, the reconfiguration of the remaining links of the STA MLD can be triggered by a BTM roaming reconfiguration frame received through an existing associated link (eg, Link1 of AP MLD1 or Link0 of AP MLD2).

[0350] 2) After receiving the BTM roaming reconfiguration frame, the STA MLD reconfigures the link and switches the associated link between STA MLD Link1 and AP MLD1 Link1 to the associated link between STA MLD Link1 and AP MLD2 Link1.

[0351] 3) After reconfiguration, the STA MLD sends a BTM roaming confirmation frame to the AP MLD2 via the remaining link after the switch (eg, Link1).

[0352] 4) Complete the roaming switching of all links of STA MLD, and STA MLD is associated with and communicates only with AP MLD2.

[0353] FIG17 shows a flow chart of a seamless roaming process of a communication method provided in another embodiment of the present application.

[0354] As shown in the figure, the seamless roaming process of the communication method may include the following steps.

[0355] In step S1600, the STA has completed the network connection with AP1, and all links have been associated.

[0356] Step S1610: The STA determines that roaming is required based on the current network status and decides to start roaming.

[0357] In step S1620, the STA sends a Probe Request (without a Multi-Link element) on each Link, and all the Non-collocated AP MLDs attached to the UHR reply with a Probe Response.

[0358] In step S1630, the STA measures the signal quality according to the Probe Response and determines the link switching order between the non-collocated AP MLD2 to which the UHR is attached and the currently associated link.

[0359] In step S1640, the STA selects a suitable link from the associated links and sends a BTM Roaming frame (e.g., a BTM roaming request) containing a Roaming Request to the EHT AP MLD1 (denoted as AP MLD1). The frame carries a Multi-Link reconfigure element, informing AP MLD1 of the information of the EHT AP MLD2 (denoted as AP MLD2) to which it wants to roam and the target handover link, that is, the link to be reconfigured, such as the Link ID.

[0360] In step S1650, AP MLD1 sends a BTM Roaming ReConfigure frame to the STA over the corresponding received Link, triggering the STA to reconfigure Link 1. The STA disconnects Link 1 from AP MLD1's Link 1 and reconfigures it to AP MLD2's Link 1. After successful reconfiguration, the STA sends a BTM Roaming Confirm frame to AP MLD2 over the newly connected Link 1 to confirm the successful reconfiguration of Link 1. During this process, STA Link 2 maintains a connection and communication with AP MLD1's Link 2.

[0361] Step S1660: Seamless data transmission is performed during the handover process. After completing the handover of Link 1, the UHR AP MLD UMAC forwards new service data destined for the STA to AP MLD2 Link 1 for transmission. Downlink service data buffered in AP MLD1 Link 2 can still be sent to the STA via MLD1 Link 2. After the STA successfully switches links, its uplink service data is preferentially transmitted via Link 1, which has already completed the handover. During this process, the STA maintains data communication with MLD1 via Link 2 and with MLD2 via Link 1.

[0362] In step S1670, the UHR MLD UMAC decides to switch the remaining link. It sends a BTM Roaming ReConfigure frame to the STA via either Link 2 of AP MLD1 or Link 1 of AP MLD2, triggering the reconfiguration of Link 2. After receiving this frame, the STA reconfigures Link 2 from AP MLD1 to AP MLD2. After the reconfiguration is successful, the STA sends a BTM Roaming Confirm frame to AP MLD2 on Link 2 to confirm the successful reconfiguration of Link 2. At this point, the STA completes roaming handover on all links, and the STA is connected and communicating only with AP MLD2.

[0363] The embodiment shown in FIG. 18 differs from the aforementioned embodiment in that, in this embodiment, the UHR AP MLD determines to initiate roaming based on uplink signal quality.

[0364] In some embodiments, the difference from the aforementioned exemplary embodiments is that, first, the UHR AP MLD UMAC determines the target link set (i.e., the link set to be switched) and sets the priority of the links in the target link set based on the link load of one or more neighboring APs of the original associated AP MLD. The UHR AP MLD UMAC then sends the target link set and link priority to the non-AP STAMLD via the association link between the original AP MLD and the non-AP STA MLD. The non-AP STA MLD determines the target link, i.e., the link to be switched, based on the link priority and the probe response signal quality of the link.

[0365] 18 , this embodiment can be applied to the logical entity architecture of a UHR AP that has completed step 1710 of the network access process. That is, the non-AP STA MLD and the UHRAP MLD's AP MLD1 are associated via link Link0, and the non-AP STA MLD and the UHR AP MLD's AP MLD1 are associated via link Link1. The roaming process of this embodiment includes the following steps.

[0366] In step S1720, AP MLD1 determines to have the non-AP STA MLD prepare for roaming based on the uplink signal quality. AP MLD1 notifies the UHR AP MLD UMAC of this information via the backhaul link. The UHR AP MLD UMAC then provides a target link set and prioritizes the links in the target link set based on the link loads of AP MLD1's neighbor APs. The UHR AP MLD UMAC notifies AP MLD1 of the target link set and the link priorities via the backhaul link.

[0367] Step S1730 : AP MLD1 notifies the non-AP STA MLD of the target link set and the priorities of the links in the target link set through a BTM request frame.

[0368] The BTM request frame and downlink quality can jointly trigger the non-AP STA MLD roaming process.

[0369] In step S1740, the non-AP STA MLD sends probe requests to one or more neighboring AP MLDs (e.g., AP MLD2) through all of its links one by one, and receives corresponding probe responses. The neighboring AP MLDs are all affiliated with the same UHR AP MLD UMAC. The neighboring AP MLD (e.g., AP MLD2) sends a probe response in response to the probe request from the non-AP STA MLD. The non-AP STA MLD evaluates the signal quality of the probe responses of the links in the target link set. The non-AP STA MLD determines the target link for roaming (e.g., Link 0 of AP MLD2) based on a combination of the link priority and the signal quality of the probe responses of the links. That is, in this step, the non-AP STA MLD determines the target link (e.g., Link 0 between the non-AP STA MLD and AP MLD2).

[0370] After the non-AP STA MLD determines the target link, the subsequent roaming steps refer to the description in any other embodiment and are not repeated here.

[0371] Figure 19 shows a BTM request frame format applicable to the embodiment shown in Figure 18. For example, the BTM request frame includes a BSS transition candidate table entry field, and the byte length of this field is variable.

[0372] The BSS Transition Candidate Entry field may include zero or more Neighbor Report Elements. The Neighbor Report Element includes a Subelement field. The Subelement field may have a variable length, for example, 3 octets, 5 octets, or other lengths.

[0373] The sub-element field may include a BSS transition candidate preference sub-element field and / or a basic multilink element.

[0374] As shown in FIG20 , the BSS transition candidate preference sub-element includes a preference field. The length of the preference field can be 1 octet, 2 octets, or other lengths.

[0375] In one embodiment, the value of the Preference field indicates the order of preference for BSSs. For example, a value of 255 indicates the most preferred candidate, i.e., the most preferred AP MLD. A value of 1 indicates the least preferred candidate, i.e., the least preferred AP MLD.

[0376] FIG21 shows a Basic Multi-Link Element structure of a BSS transition candidate entry field according to another embodiment of the present application.

[0377] When the AP MLD intends to give preference to the reported AP MLD when there is no specific subordinate AP recommendation, all subfields in the Presence bitmap field may be set to 0 and no Per-STA Profile subfield may be included in the basic multilink element.

[0378] When the AP MLD intends to give preference to the reported AP MLD when it has only a subset of recommended subordinate APs, the Link ID Info field is included in the common information of the basic multilink element, and the field value of the Link ID Info field is set to correspond to the corresponding field value of the AP reported in the neighbor report element.

[0379] The embodiment shown in FIG. 22 differs from the aforementioned exemplary embodiments in that the roaming triggering method is different, that is, the AP MLD initiates roaming based on an uplink signal.

[0380] The embodiment shown in Figure 22 also differs from the aforementioned exemplary embodiments in that the target link (i.e., the link to be switched) is determined differently. In this embodiment, the neighbor AP MLD first evaluates the signal quality of the probe request (uplink) and reports the uplink signal quality and link load to the UHR AP MLD UMAC. The UHR AP MLD determines the target link based on a combination of the link load status and the uplink signal quality.

[0381] In the embodiment shown in Figure 22, this embodiment is applied to the UHR AP logical entity architecture of step S2010 of the network access process. That is, the non-AP STA MLD and the UHR AP MLD's AP MLD1 are associated via link Link0, and the non-AP STA MLD and the UHR AP MLD's AP MLD1 are associated via link Link1. The roaming process of this embodiment includes the following steps.

[0382] In step S2020, the original AP MLD (e.g., AP MLD1) prepares the non-AP STA MLD for roaming based on the uplink signal quality. The original AP MLD sends a roaming preparation message to one or more neighboring AP MLDs (e.g., AP MLD2) via the UHR AP MLD UMAC. After receiving the message, the neighboring AP MLD reserves time to measure the probe request signal from the non-AP STA MLD. The original AP MLD notifies the non-AP STA MLD of the roaming preparation message via a BTM request frame.

[0383] In step S2030, the BTM request frame triggers the roaming process of the non-AP STA MLD. The non-AP STA MLD uses all its links to send probe request signals to one or more adjacent AP MLDs (e.g., AP MLD2, AP MLD3, etc.), where these adjacent AP MLDs are all affiliated with the same UHR AP MLD UMAC.

[0384] In step 2040, the neighboring AP MLD of the original AP MLD evaluates the signal quality of the probe request signal for each link. The neighboring AP MLD reports the signal quality and link load of each link to the UHR AP MLD UMAC. The UHR AP MLD UMAC determines the roaming target link based on a combination of the load status and signal quality of each link. The UHR AP MLD UMAC notifies the original AP MLD (e.g., AP MLD1) of the roaming target link (e.g., Link 0 between the non-AP STA MLD and AP MLD 2).

[0385] The embodiment shown in Figure 22 , on the one hand, evaluates the quality of the probe signal by the AP MLD rather than the non-AP STA AP, thereby reducing the burden on the non-AP STA MLD. On the other hand, this embodiment eliminates the need for the non-AP MLD to notify the original AP MLD of the target link, nor does it require the AP MLD to send a probe response to the non-AP STA MLD. This reduces frame overhead and improves seamless roaming efficiency.

[0386] FIG23 and FIG24 show another format example of a UHR mobility domain field provided in an embodiment of the present application.

[0387] As shown in the figure, the difference from the embodiment shown in Figures 3 and 4 is that in the ST Capability field of the UHR Mobility Domain, the length of the Seamless BSS Transition Mode field is 2 bits, and the reserved field is 6 bits. When the length of the Seamless BSS Transition Mode field is 2, the value of this field can have different meanings, as shown in Figure 24.

[0388] When the value of Seamless BSS Transition Mode is 0, it may indicate that the seamless roaming mode is that the MLD does not have the seamless transition capability. When the value of Seamless BSS Transition Mode is 1, it may indicate that the seamless roaming mode is that the non-AP STA MLD initiates seamless roaming. When the value of Seamless BSS Transition Mode is 2, it may indicate that the seamless roaming mode is that the APMLD initiates seamless roaming, and the non-AP STA MLD determines the roaming target link (for example, the roaming link to be switched). When the value of Seamless BSS Transition Mode is 3, it may indicate that the seamless roaming mode is that the APMLD initiates seamless roaming, and the UHR AP MLD UMAC determines the roaming target link.

[0389] The communication method provided in this application will be further described below.

[0390] Each embodiment of the present application provides a communication method in a wireless network, which is applied to a non-collocated control module of an ultra-high reliability (UHR) non-co-located access point multi-link logical entity, including: the UHR control module instructs the sending of a first frame to a non-access point multi-link logical entity (Non-AP Multi-link logical entity), wherein the first frame includes first link identification information, and the first link identification information indicates that the non-access point multi-link logical entity is to be switched to one or more links associated with the first access point multi-link logical entity.

[0391] In one embodiment, the first link identification information includes logical entity identification information corresponding to the first access point multi-link logical entity and link information corresponding to the one or more links.

[0392] In one embodiment, before the UHR control module instructs the sending of the first frame to the non-access point multi-link logical entity, the method further includes: the UHR control module instructs the second access point multi-link logical entity to disconnect the association with the one or more links, and the first access point multi-link logical entity to associate with the one or more links.

[0393] In one embodiment, before the UHR control module instructs to send the first frame to the non-access point multi-link logical entity, the method further includes: the UHR control module receives a second frame from the non-access point multi-link logical entity, the second frame including second link identification information, wherein the first link identification information corresponds to the second link identification information.

[0394] In one embodiment, the one or more links are associated with the non-access point multi-link logical entity and the second access point link logical entity respectively.

[0395] In one embodiment, the first frame further includes a first indication, wherein the first indication indicates a disconnection mode of the one or more links.

[0396] In one embodiment, the disconnection mode is delayed disconnection, and the first indication further indicates the delay duration of the delayed disconnection.

[0397] In one embodiment, the first frame further includes a second indication, where the second indication indicates whether the UHR control module has completed the operation requested by the second frame.

[0398] In one embodiment, after the UHR control module instructs to send the first frame to the non-access point multi-link logical entity, the method further includes:

[0399] In response to a preset condition being met, the UHR control module confirms that the one or more links of the non-access point multi-link logical entity have been switched to be associated with the first access point multi-link logical entity.

[0400] In one embodiment, the preset condition includes: the UHR control module receives a fourth frame from the non-access point multi-link logical entity, and the fourth frame includes fourth link identification information corresponding to the first link identification information.

[0401] In one embodiment, the fourth frame further includes a fourth indication, and the fourth indication indicates whether the non-access point multi-link logical entity has completed the operation requested in the first frame.

[0402] In one embodiment, the preset condition includes: a preset time has passed after the UHR control module indicates that the first frame has been sent.

[0403] In one embodiment, after the one or more links of the non-access point multi-link logical entity have been switched to be associated with the first access point multi-link logical entity, the method further includes: the UHR control module instructs that the cached downlink data used for the one or more links before the switching be sent through at least one associated link other than the one or more links after the switching, wherein the at least one associated link is associated with the non-access point multi-link logical entity and the second access point multi-link logical entity, respectively.

[0404] In one embodiment, the UHR control module instructs the cached downlink data used for the one or more links before the switching to be sent through at least one associated link other than the one or more links after the switching, including: the UHR control module makes the cached downlink data accessible to the at least one associated link other than the one or more links after the switching; and the UHR control module instructs the cached downlink data to be sent through the at least one associated link.

[0405] In one embodiment, making the cached downlink data accessible to the at least one associated link other than the one or more links after switching includes: the UHR control module instructing the cached downlink data to be shared or copied to the at least one associated link other than the one or more links after switching; the UHR address control module instructing the cached downlink data to be sent to an external storage device, wherein the at least one associated link can be communicatively connected to the external storage device; or the UHR control module instructing the cached downlink data to be sent to the UHR control module.

[0406] In one embodiment, after the one or more links of the non-access point multi-link logical entity have been switched to be associated with the first access point multi-link logical entity, the method further includes: the UHR control module instructing the second access point multi-link logical entity to preferentially receive uplink data from the non-access point multi-link logical entity through the one or more links after the switch.

[0407] In one embodiment, after the one or more links of the non-access point multi-link logical entity have been switched to be associated with the first access point multi-link logical entity, the method further includes: the UHR control module instructs that data received after the one or more links are switched and whose destination address is the non-access point multi-link logical entity be sent to the non-access point multi-link logical entity through the one or more links after the switch.

[0408] In one embodiment, after the one or more links of the non-access point multi-link logical entity have been switched to be associated with the first access point multi-link logical entity, the method further includes: the UHR control module instructing the sending of a fifth frame to the non-access point multi-link logical entity, wherein the fifth frame includes fifth link identification information, and the fifth link identification information indicates that the non-access point multi-link logical entity is to be switched to one or more remaining links associated with the first access point multi-link logical entity.

[0409] In one embodiment, after the UHR control module confirms that the one or more links of the non-access point multi-link logical entity have been switched to be associated with the first access point multi-link logical entity, the method further includes:

[0410] The UHR control module shares or copies the first key information used for the UHR access point multi-link logical entity to the first access point multi-link logical entity for use in associated links of the first access point multi-link logical entity.

[0411] In one embodiment, the first key information is based on an upper media access control (UMAC) address of the UHR control module.

[0412] In one embodiment, the multicast key information for the one or more links of the first access point multi-link logical entity is based on a corresponding lower medium access control (LMAC) address of the first access point multi-link logical entity.

[0413] In one embodiment, the multicast key information includes a fourth indication, and the fourth indication indicates link information corresponding to the multicast key information.

[0414] In one embodiment, the types of the multicast key information include a group transient key (GTK), an integrated group transient key (IGTK), and a beacon integrated group transient key (BIGTK).

[0415] In one embodiment, before the UHR control module receives the second frame from the non-access point multi-link logical entity, the method further includes: the UHR control template sending a ninth frame to the non-access point multi-link logical entity, wherein the ninth frame is configured to request the non-access point multi-link logical entity to send the second frame.

[0416] In one embodiment, the UHR control module is configured to store first key information for the UHR access point multi-link logical entity.

[0417] In one embodiment, before the UHR control module instructs the sending of the first frame to the non-access point multi-link logical entity, the method further includes: the UHR control module instructs the sending of a sixth frame to the non-access point multi-link logical entity, wherein the sixth frame includes a UHR mobility domain element, and the UHR mobility domain element indicates the seamless transition capability of the UHR access point multi-link logical entity.

[0418] In one embodiment, the method further comprises: determining first key information for the UHR access point multi-link logical entity based on a UMAC address of the UHR control module, wherein the first key information is stored in the UHR control module.

[0419] In one embodiment, the first key information includes unicast key information.

[0420] In one embodiment, the unicast key information includes pairwise transition key (PTK) key information.

[0421] In one embodiment, the method further includes: determining multicast key information for the one or more links of the first access point multi-link logical entity based on the corresponding lower media access control (LMAC) address of the first access point multi-link logical entity; and the UHR control module instructing the sending of the multicast key information to the non-access point multi-link logical entity.

[0422] Various embodiments of the present application provide a communication method in a wireless local area network, which is applied to a non-access point multi-link logical entity, where the non-access point multi-link logical entity is associated with a non-collocated control module of an ultra-high reliability (UHR) non-co-located access point multi-link logical entity. The method includes: the non-access point multi-link logical entity sending a second frame to the UHR access point multi-link logical entity, where the second frame includes second link identification information, wherein the second link identification information indicates that the non-access point multi-link logical entity is to be switched to one or more links associated with the first access point multi-link logical entity.

[0423] In one embodiment, the second link identification information includes logical entity identification information corresponding to the first access point multi-link logical entity and link information corresponding to the one or more links.

[0424] In one embodiment, the one or more links are associated with the non-access point multi-link logical entity and the second access point link logical entity respectively.

[0425] Specifically, the one or more links may be one or more links that the non-access point multi-link logical entity requests to be disconnected from the second access point link logical entity.

[0426] Alternatively, the one or more links may also be one or more links that the UHR control module requests to be disconnected from a non-access point multi-link logical entity.

[0427] In one embodiment, after the non-access point multi-link logical entity sends the second frame to the UHR access point multi-link logical entity, the method further includes: the non-access point multi-link logical entity receives a first frame from the UHR access point multi-link logical entity, the first frame including first link identification information, wherein the second link identification information corresponds to the first link identification information.

[0428] In one embodiment, after the non-access point multi-link logical entity receives the first frame from the UHR access point multi-link logical entity, the method further includes: the non-access point multi-link logical entity sends a fourth frame to the UHR access point multi-link logical entity, and the fourth frame includes fourth link identification information corresponding to the first link identification information.

[0429] In one embodiment, the fourth frame further includes a fourth indication, and the fourth indication indicates whether the non-access point multi-link logical entity has completed the operation requested in the first frame.

[0430] In one embodiment, after the non-access point multi-link logical entity receives the first frame from the UHR access point multi-link logical entity, the method further includes: the non-access point multi-link logical entity disconnecting from the second access point multi-link logical entity on the one or more links; and the non-access point multi-link logical entity associating with the first access point multi-link logical entity on the one or more links to complete the switching of the one or more links.

[0431] In one embodiment, after the non-access point multi-link logical entity is associated with the first access point multi-link logical entity on the one or more links, the method further includes: the non-access point multi-link logical entity preferentially sending uplink data to the first access point multi-link logical entity through the one or more links after the switch.

[0432] In one embodiment, after the non-access point multi-link logical entity is associated with the first access point multi-link logical entity on the one or more links, the method further includes: the non-access point multi-link logical entity receives cached downlink data from the UHR access point multi-link logical entity through at least one associated link other than the one or more links after the switch, wherein the cached downlink data is cached downlink data for the one or more links before the switch.

[0433] In one embodiment, the method further includes: the non-access point multi-link logical entity sending a seventh frame on multiple links associated with the UHR access point multi-link logical entity respectively; the non-access point multi-link logical entity receiving multiple eighth frames from the UHR access point multi-link logical entity in response to the seventh frame; and the non-access point multi-link logical entity determining the one or more links of the first access point multi-link logical entity based on the multiple eighth frames.

[0434] In one embodiment, the non-access point multi-link logical entity determines the one or more links of the first access point multi-link logical entity based on the multiple eighth frames, including: the non-access point multi-link logical entity determines multiple signal qualities of multiple links corresponding to the multiple eighth frames respectively based on the multiple eighth frames; and the non-access point multi-link logical entity determines the one or more links of the first access point multi-link logical entity based on the multiple signal qualities.

[0435] In one embodiment, the method further includes: the non-access point multi-link logical entity receiving a multicast key signal from the UHR access point multi-link logical entity, wherein the multicast key information is a corresponding lower media access control (LMAC) address based on the access point multi-link logical entity.

[0436] In one embodiment, the method further includes: the non-access point multi-link logical entity receiving a sixth frame from the UHR access point multi-link logical entity, wherein the sixth frame includes a UHR mobility domain element, and the UHR mobility domain element indicates a seamless transition capability of the UHR access point multi-link logical entity.

[0437] Each exemplary embodiment of the present application provides a method for constructing a communication frame, which is applied to wireless network communication of an ultra-high reliability (UHR) non-co-located access point multi-link logical entity, including: generating a first indication field, wherein the first indication field indicates that the non-access point multi-link logical entity is to be switched to one or more links associated with a first access point multi-link logical entity, wherein the first access point multi-link logical entity is attached to the UHR access point multi-link logical entity.

[0438] In one embodiment, the first indication field includes logical entity identification information corresponding to the first access point multi-link logical entity and link information corresponding to the one or more links.

[0439] In one embodiment, the link information includes link quantity information and one or more link identification information.

[0440] In one embodiment, the first indication field further includes a STA control field.

[0441] In one embodiment, the STA control field includes a link deletion mode field and / or a link deletion count field.

[0442] In one embodiment, the method further includes: generating an action field, wherein the field content included in the first indication field depends on the value of the action field.

[0443] In one embodiment, the first indication further indicates a switching order of the one or more links.

[0444] Each exemplary embodiment of the present application provides a method for constructing a communication frame, wherein the frame is applied to wireless network communication of an ultra-high reliability (UHR) non-co-located access point multi-link logical entity, comprising: generating a UHR

[0445] The UHR mobility element field includes a seamless transition capability field.

[0446] In one embodiment, the byte length of the seamless transition capability is greater than 2 bits.

[0447] In one embodiment, the UHR mobility domain element field further includes a mobility domain identification field.

[0448] In one embodiment, the UHR mobility domain field is set in the sixth frame.

[0449] In one embodiment, the UHR mobility domain field reuses the FT Capability and Policy subfield in the Mobility Domain Information Element (MDIE) field. Embodiments of the present application provide an access point device, including: a sending module configured to send a first frame to a non-access point multi-link logical entity (Non-AP Multi-link logical entity), wherein the first frame includes first link identification information, and the first link identification information indicates that the non-access point multi-link logical entity is to be switched to one or more links associated with the first access point multi-link logical entity.

[0450] FIG25 is a schematic diagram of the structure of an access point device 400 provided in an embodiment of the present application. The access point device 400 may be the access point multi-link device 202 in the WLAN as shown in FIG1 . As shown in FIG25 , the access point device 400 includes

[0451] The receiving module 410 is configured to receive a second frame from a non-access point multi-link logical entity, wherein the second frame is used to initiate a roaming request;

[0452] A sending module 420 is configured to send a first frame to a non-access point multi-link logical entity, wherein the first frame is used to indicate roaming reconfiguration;

[0453] The access point device 400 includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point multi-link logical entity.

[0454] In some embodiments, the first frame includes first link identification information, where the first link identification information is used to indicate a target link of the first access point multi-link logical entity to which the non-access point multi-link logical entity switches.

[0455] In some embodiments, the second frame includes second link identification information, where the second link identification information is used to indicate a link of an access point multi-link logical entity to which the non-access point multi-link logical entity requests to be switched.

[0456] Optionally, the access point device 400 may be an access point multi-link logical entity, such as a UHR access point multi-link logical entity.

[0457] In some embodiments, the sending module 420 is further configured to:

[0458] A first frame is sent to the non-access point multi-link logical entity through the first access point multi-link logical entity or the second access point multi-link logical entity.

[0459] In some embodiments, the receiving module 410 is further configured to:

[0460] A second frame from the non-access point multi-link logical entity is received through the first access point multi-link logical entity or the second access point multi-link logical entity.

[0461] In some embodiments, the first link identification information includes identification information of the first access point multi-link logical entity and link information of the target link.

[0462] In some embodiments, the first frame includes a common information field, and the first link identification information is carried in the common information field.

[0463] In some embodiments, the first frame further includes a first indication, where the first indication is used to indicate a switching mode of the target link.

[0464] In some embodiments, the first indication is used to indicate immediate switching, or the first indication is used to indicate delayed switching, and the first indication is also used to indicate a delay duration of the delayed switching.

[0465] In some embodiments, before receiving the second frame from the non-AP multi-link logical entity, the sending module 420 is further configured to:

[0466] A third frame is sent to the non-access point multi-link logical entity, where the third frame includes third link identification information, where the third link identification information is used to indicate a candidate access point multi-link logical entity and / or a candidate link to which the access point device 400 recommends the non-access point multi-link logical entity to switch.

[0467] In some embodiments, the third frame includes a candidate list field, wherein the candidate list field includes at least one sub-element, each sub-element corresponds to a candidate access point multi-link logical entity, and each sub-element is used to indicate one or more candidate links of the corresponding candidate access point multi-link logical entity.

[0468] In some embodiments, the sub-element includes at least one of the following fields:

[0469] The first field is used to indicate the address information of the candidate access point multi-link logical entity;

[0470] The second field is used to indicate whether to recommend the non-access point multi-link logical entity to switch to all candidate links of the candidate access point multi-link logical entity; or

[0471] The third field is used to indicate one or more candidate links of the candidate access point multi-link logical entity to which handover is recommended.

[0472] In some embodiments, the candidate access point multi-link logical entity and / or the candidate link are determined by the UHR access point multi-link logical entity based on the load condition and / or signal quality of the link of the neighbor access point multi-link logical entity of the second access point multi-link logical entity.

[0473] In some embodiments, the access point device 400 further includes:

[0474] a processing module, configured to determine, when a preset condition is met, that the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity;

[0475] The preset conditions include at least one of the following:

[0476] receiving a fourth frame from the non-access point multi-link logical entity, where the fourth frame includes fourth link identification information, and the fourth link identification information corresponds to the first link identification information; or

[0477] A preset time has passed since the first frame was sent.

[0478] In some embodiments, after the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the sending module 420 is further configured to:

[0479] Sending a fifth frame to the non-access point multi-link logical entity, where the fifth frame includes fifth link identification information;

[0480] The fifth link identification information is used to indicate that one or more remaining links of the non-access point multi-link logical entity are switched to the associated first access point multi-link logical entity, and the one or more remaining links include one or more links other than the target link among the links associated with the non-access point multi-link logical entity and the second access point multi-link logical entity.

[0481] In some embodiments, after the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the sending module 420 is further configured to:

[0482] Sending buffered downlink data to the non-access point multi-link logical entity, wherein the buffered downlink data is downlink data buffered on the target link before switching.

[0483] In some embodiments, the sending module 420 is further configured to:

[0484] The buffered downlink data is sent to the non-access point multi-link logical entity through the second access point multi-link logical entity.

[0485] In some embodiments, the sending module 420 is further configured to:

[0486] sending the buffered downlink data to the first access point multi-link logical entity through the second access point multi-link logical entity;

[0487] The buffered downlink data is sent to the non-access point multi-link logical entity through the first access point multi-link logical entity.

[0488] In some embodiments, the access point device 400 further includes:

[0489] The processing module is configured to determine the unicast key information of the access point device 400 according to the upper medium access control UMAC address of the access point device 400 .

[0490] The processing module is further configured to: share, copy or send the unicast key information of the access point device 400 to the first access point multi-link logical entity;

[0491] The sending module 420 is further configured to send the unicast key information of the access point device 400 to the non-access point multi-link logical entity.

[0492] In some embodiments, the access point device 400 further includes:

[0493] The processing module is configured to respectively determine multicast key information of one or more links of the first access point multi-link logical entity according to one or more downlink medium access control LMAC addresses of the first access point multi-link logical entity.

[0494] In some embodiments, the sending module 420 is further configured to: send multicast key information of one or more links of the first access point multi-link logical entity to the non-access point multi-link logical entity.

[0495] In some embodiments, before sending the first frame to the non-access point multi-link logical entity, the sending module 420 is further configured to:

[0496] A sixth frame is sent to the non-access point multi-link logical entity, where the sixth frame is used to indicate that the UHR access point multi-link logical entity has a seamless transition capability.

[0497] In some embodiments, the sixth frame includes an ultra-high reliability (UHR) mobility domain element, where the UHR mobility domain element is used to indicate that the UHR access point multi-link logical entity has seamless transition capability.

[0498] In some embodiments, the receiving module 410 is further configured to: receive the seventh frame sent by the non-access point multi-link logical entity through multiple access point multi-link logical entities; and

[0499] The sending module 420 is further configured to send an eighth frame in response to the seventh frame to the non-access point multi-link logical entity through the multiple access point multi-link logical entities, where the eighth frame is used to determine the first access point multi-link logical entity.

[0500] The access point device 400 may also include other modules to implement the communication methods of the above-mentioned embodiments. The above-mentioned exemplary embodiments of the communication methods, as well as improvements, modifications, and variations based on these embodiments obtained by those skilled in the art without inventive effort, may also be used to define the access point device 400, and will not be further described in this application.

[0501] FIG26 is a schematic diagram of the structure of a non-access point device 500 provided in an embodiment of the present application. The non-access point device 500 may be the terminal device 201 in the WLAN as shown in FIG1 . As shown in FIG26 , the non-access point device 500 includes:

[0502] A sending module 510 is configured to send a second frame to an ultra-high reliability (UHR) access point multi-link logical entity, wherein the second frame is used to initiate a roaming request;

[0503] The receiving module 520 is configured to receive a first frame from the UHR access point multi-link logical entity, wherein the first frame is used to indicate roaming reconfiguration;

[0504] The UHR access point multi-link logical entity includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point device 500 .

[0505] In some embodiments, the first frame includes first link identification information, where the first link identification information is used to indicate a target link of the first access point multi-link logical entity to which the non-access point device 500 switches.

[0506] In some embodiments, the second frame includes second link identification information, where the second link identification information is used to indicate the link of the access point multi-link logical entity to which the non-access point device 500 requests to switch.

[0507] Optionally, the non-access point device 500 may be a non-access point multi-link logical entity.

[0508] In some embodiments, the receiving module 520 is further configured to:

[0509] Receive a first frame sent by the first access point multi-link logical entity or the second access point multi-link logical entity from the UHR access point multi-link logical entity.

[0510] In some embodiments, the first link identification information includes identification information of the first access point multi-link logical entity and link information of the target link.

[0511] In some embodiments, the first frame includes a common information field, and the first link identification information is carried in the common information field.

[0512] In some embodiments, the first frame further includes a first indication, where the first indication is used to indicate a switching mode of the target link.

[0513] In some embodiments, the first indication is used to indicate immediate switching, or the first indication is used to indicate delayed switching, and the first indication is also used to indicate a delay duration of the delayed switching.

[0514] In some embodiments, the access point multi-link logical entity and link indicated by the second link identification information are determined by the non-access point device 500 according to signal quality of a downlink signal of at least one access point multi-link logical entity attached to the UHR access point multi-link logical entity.

[0515] In some embodiments, before sending the second frame to the UHR access point multi-link logical entity, the method further includes:

[0516] The receiving module 520 is further configured to receive a third frame from the UHR access point multi-link logical entity, where the third frame includes third link identification information, where the third link identification information is used to indicate a candidate access point multi-link logical entity and / or candidate link to which the UHR access point multi-link logical entity recommends that the non-access point device 500 switch.

[0517] In some embodiments, the third frame includes a candidate list field, wherein the candidate list field includes at least one sub-element, each sub-element corresponds to a candidate access point multi-link logical entity, and each sub-element is used to indicate one or more candidate links of the corresponding candidate access point multi-link logical entity.

[0518] In some embodiments, the sub-element includes at least one of the following fields:

[0519] The first field is used to indicate the address information of the candidate access point multi-link logical entity;

[0520] The second field is used to indicate whether to recommend the non-access point device 500 to switch to all candidate links of the candidate access point multi-link logical entity; or

[0521] The third field is used to indicate one or more candidate links of the candidate access point multi-link logical entity to which handover is recommended.

[0522] In some embodiments, the access point multi-link logical entity and link indicated by the second link identification information are determined by the non-access point device 500 according to link qualities of candidate links of the candidate access point multi-link logical entity indicated by the third link identification information.

[0523] In some embodiments, after the target link of the non-access point device 500 has been switched to be associated with the first access point multi-link logical entity, the receiving module 520 is further configured to:

[0524] receiving a fifth frame from the UHR access point multi-link logical entity, the fifth frame including fifth link identification information;

[0525] The fifth link identification information is used to indicate that one or more remaining links of the non-access point multi-link logic are switched to the associated first access point multi-link logical entity, where the one or more remaining links include one or more links other than the target link in the links associated between the non-access point device 500 and the second access point multi-link logical entity.

[0526] In some embodiments, after the target link of the non-access point device 500 has been switched to be associated with the first access point multi-link logical entity, the receiving module 520 is further configured to:

[0527] Receive buffered downlink data from the UHR access point multi-link logical entity, wherein the buffered downlink data is downlink data buffered on the target link before switching.

[0528] In some embodiments, the receiving module 520 is further configured to: receive the buffered downlink data sent by the UHR access point multi-link logical entity through the second access point multi-link logical entity.

[0529] In some embodiments, the receiving module 520 is further used to: receive the cached downlink data sent by the UHR access point multi-link logical entity through the first access point multi-link logical entity, wherein the cached downlink data is forwarded by the second access point multi-link logical entity to the first access point multi-link logical entity.

[0530] In some embodiments, the receiving module 520 is further used to: receive unicast key information of the UHR access point multi-link logical entity from the UHR access point multi-link logical entity, wherein the unicast key information is determined according to the upper medium access control UMAC address of the UHR access point multi-link logical entity.

[0531] In some embodiments, the receiving module 520 is further used to: receive multicast key information of one or more links of the first access point multi-link logical entity from the UHR access point multi-link logical entity, wherein the multicast key information of the one or more links is determined based on one or more lower media access control LMAC addresses of the first access point multi-link logical entity.

[0532] In some embodiments, the receiving module 520 is further configured to: receive a sixth frame from the UHR access point multi-link logical entity, where the sixth frame is used to indicate that the UHR access point multi-link logical entity has seamless transition capability.

[0533] In some embodiments, the sixth frame includes an ultra high reliability (UHR) mobility domain element, where the UHR mobility domain element is used to indicate that the UHR access point multi-link logical entity has seamless transition capability.

[0534] In some embodiments, the sending module 510 is further configured to: send a seventh frame to multiple access point multi-link logical entities of the UHR access point multi-link logical entity; and

[0535] The receiving module 520 is further configured to receive an eighth frame sent by multiple access point multi-link logical entities of the UHR access point multi-link logical entity, where the eighth frame is used to determine the first access point multi-link logical entity.

[0536] The non-access point device 500 may also include other modules to implement the communication methods of the above-mentioned embodiments. The above-mentioned exemplary embodiments of the communication methods, as well as improvements, modifications, and variations based on these embodiments obtained by those skilled in the art without inventive effort, may also be used to define the non-access point device 500, and will not be further described in this application.

[0537] An embodiment of the present application provides an access point multi-link device, including: a processor and a transceiver;

[0538] The processor is configured to call a computer program and cooperate with the transceiver to implement the actions performed by the access point multi-link device in the above method embodiment.

[0539] For example, Figure 27 is a block diagram of an access point multi-link device provided in an embodiment of the present application. As shown in Figure 27, the access point multi-link device 600 includes a processor 601 and a transceiver 602. The transceiver 602 is configured to perform the transceiver operations of the access point multi-link device in the above-described method embodiment under the control of the processor 601.

[0540] Optionally, the access point multi-link device 600 further includes a memory 603 , a communication bus 604 and a communication interface 605 .

[0541] The processor 601 may be a general-purpose central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0542] The communication bus 604 may include a pathway for transmitting information between the aforementioned components.

[0543] The memory 603 may be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 603 may exist independently and be connected to the processor 601 via a communication bus 604. The memory 603 may also be integrated with the processor 601.

[0544] Among them, the memory 603 is used to store the program code for executing the solution of the present application, and the execution is controlled by the processor 601. The processor 601 is used to execute the program code stored in the memory 603. The program code may include one or more software modules. These one or more software modules may be the software modules provided in the embodiment of Figure 17. The communication interface 605 uses the transceiver 602 to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), WLAN, etc.

[0545] In a specific implementation, as an example, an access point multi-link device may include multiple processors. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0546] In a specific implementation, the access point multi-link device may be a router or a switch.

[0547] Optionally, the access point multi-link device is an access point multi-link device. The multiple APs included in the access point multi-link device are independent of each other in the LMAC layer and the PHY layer, and are also independent of each other in the UMAC layer. Alternatively, the multiple STAs included in the access point multi-link device are independent of each other in the low MAC layer and the PHY layer, and share the UMAC layer. The embodiments of the present application do not limit the internal structure of the access point multi-link device. For example, the UMAC layer or the LMAC layer can be implemented by a processor in the chip system of the access point multi-link device, and can also be implemented by different processors in the chip system.

[0548] An embodiment of the present application provides a non-access point multi-link device, including: a processor and a transceiver;

[0549] The processor is configured to call a computer program and cooperate with the transceiver to implement the actions performed by the non-access point multi-link device in the above method embodiment.

[0550] For example, Figure 28 is a block diagram of a non-access point multi-link device provided in an embodiment of the present application. As shown in Figure 28, the non-access point multi-link device 700 includes a processor 701 and a transceiver 702. Transceiver 702 is configured to execute the transceiver operations performed by the non-access point multi-link device in the above-described method embodiment under the control of processor 701.

[0551] Optionally, the access point multi-link device 700 further includes a memory 703 , a communication bus 704 and a communication interface 705 .

[0552] The processor 701 may be a general-purpose CPU, an ASIC, or one or more integrated circuits for controlling the execution of the program of the present application.

[0553] The communication bus 704 may include a pathway for transmitting information between the aforementioned components.

[0554] The memory 703 may be a ROM or other type of static storage device capable of storing static information and instructions, a RAM or other type of dynamic storage device capable of storing information and instructions, an EEPROM, a CD-ROM or other optical disk storage, an optical disk storage (including a compact disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, etc.), a magnetic disk or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto. The memory 703 may be independently connected to the processor 701 via a communication bus 704. The memory 703 may also be integrated with the processor 701.

[0555] The memory 703 is used to store program code for executing the solution of the present application, and the execution is controlled by the processor 701. The processor 701 is used to execute the program code stored in the memory 2003. The program code may include one or more software modules. These one or more software modules may be the software modules provided in Figure 28.

[0556] The communication interface 705 uses the transceiver 702 to communicate with other devices or communication networks, such as Ethernet, RAN, WLAN, etc.

[0557] In a specific implementation, as an example, a non-access point multi-link device may include multiple processors. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0558] In a specific implementation, the non-access point multi-link device may be a wireless terminal such as a mobile phone, a computer, or a smart wearable device.

[0559] Optionally, the non-access point multi-link device is a non-access point multi-link device. The multiple non-AP STAs included in the non-access point multi-link device are independent of each other in the LMAC layer and the PHY layer, and are also independent of each other in the UMAC layer. Alternatively, the multiple non-AP STAs included in the non-access point multi-link device are independent of each other in the LMAC layer and the PHY layer, and share the UMAC layer. The embodiments of the present application do not limit the internal structure of the non-access point multi-link device. For example, the high MAC layer or the low MAC layer can be implemented by a processor in the chip system of the non-access point multi-link device, and can also be implemented by different processors in the chip system.

[0560] It should be noted here that the above-mentioned electronic device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0561] An embodiment of the present application further provides a computer-readable storage medium, which stores computer-executable instructions. The computer-executable instructions are used to enable a computer to execute a terminal roaming guidance method in the above embodiment.

[0562] An embodiment of the present application further provides a computer program product. When the computer program product is called by a computer, the computer is caused to execute a terminal roaming guidance method in the above embodiment.

[0563] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0564] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0565] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0566] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

Claims

1. A communication method in a wireless local area network, comprising: An ultra high reliability (UHR) access point multi-link logic entity receives a second frame from a non-access point multi-link logic entity, wherein the second frame is used to initiate a roaming request; and The UHR access point multi-link logical entity sends a first frame to the non-access point multi-link logical entity, wherein the first frame is used to indicate roaming reconfiguration; The UHR access point multi-link logical entity includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point multi-link logical entity.

2. The method according to claim 1, wherein: The UHR access point multi-link logical entity sends a first frame to the non-access point multi-link logical entity, comprising: the UHR access point multi-link logical entity sends the first frame to the non-access point multi-link logical entity through the first access point multi-link logical entity or the second access point multi-link logical entity.

3. The method according to claim 1 or 2, wherein: The first frame includes first link identification information, where the first link identification information is used to indicate a target link of the first access point multi-link logical entity to which the non-access point multi-link logical entity switches; and / or The second frame includes second link identification information, where the second link identification information is used to indicate a link of an access point multi-link logical entity to which the non-access point multi-link logical entity requests to switch.

4. The method according to claim 3, wherein: The first link identification information includes identification information of the first access point multi-link logical entity and link information of the target link.

5. The method according to claim 3 or 4, wherein: The first frame also includes a first indication, where the first indication is used to indicate a switching mode of the target link.

6. The method according to claim 5, wherein: The first indication is used to indicate an immediate switch, or the first indication is used to indicate a delayed switch, and the first indication is also used to indicate a delay duration of the delayed switch.

7. The method according to any one of claims 1 to 6, wherein: The ultra high reliability (UHR) access point multi-link logical entity receives a second frame from a non-access point multi-link logical entity, including: the UHR access point multi-link logical entity receives the second frame through the first access point multi-link logical entity or the second access point multi-link logical entity.

8. The method according to any one of claims 1 to 7, wherein: Before the ultra-high reliability (UHR) access point multi-link logical entity receives a second frame from a non-access point multi-link logical entity, the method further includes: The UHR access point multi-link logical entity sends a third frame to the non-access point multi-link logical entity, where the third frame includes third link identification information, and the third link identification information is used to indicate the candidate access point multi-link logical entity and / or candidate link to which the UHR access point multi-link logical entity recommends that the non-access point multi-link logical entity switch.

9. The method according to claim 8, wherein: The third frame includes a candidate list field, wherein the candidate list field includes at least one sub-element, the at least one sub-element corresponds to at least one candidate access point multi-link logical entity, and the at least one sub-element is used to indicate one or more candidate links of the at least one candidate access point multi-link logical entity.

10. The method according to claim 9, wherein the sub-element comprises at least one of the following fields: The first field is used to indicate the address information of the candidate access point multi-link logical entity; The second field is used to indicate whether to recommend the non-access point multi-link logical entity to switch to all candidate links of the candidate access point multi-link logical entity; or The third field is used to indicate one or more candidate links of the candidate access point multi-link logical entity to which switching is recommended.

11. The method according to any one of claims 8 to 10, wherein: The candidate access point multi-link logical entity and / or the candidate link are determined by the UHR access point multi-link logical entity according to the load status and / or signal quality of the link of the neighboring access point multi-link logical entity of the second access point multi-link logical entity.

12. The method according to any one of claims 1 to 11, wherein: The method further comprises: When a preset condition is met, the UHR access point multi-link logical entity determines that the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity; wherein the preset condition includes at least one of the following: The UHR access point multi-link logical entity receives a fourth frame from the non-access point multi-link logical entity, the fourth frame includes fourth link identification information, and the fourth link identification information corresponds to the first link identification information in the first frame; or A preset time has passed since the UHR access point multi-link logic entity sent the first frame.

13. The method according to any one of claims 1 to 12, wherein: After the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the method further includes: the UHR access point multi-link logical entity sending a fifth frame to the non-access point multi-link logical entity, the fifth frame including fifth link identification information; The fifth link identification information is used to indicate that one or more remaining links of the non-access point multi-link logical entity are switched to the associated first access point multi-link logical entity, and the one or more remaining links include one or more links other than the target link in the links associated with the non-access point multi-link logical entity and the second access point multi-link logical entity.

14. The method according to any one of claims 1 to 13, wherein: After the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the method further includes: The UHR access point multi-link logical entity sends the buffered downlink data to the non-access point multi-link logical entity, wherein the buffered downlink data is the downlink data buffered on the target link before switching.

15. The method according to claim 14, wherein: The UHR access point multi-link logical entity sends the buffered downlink data to the non-access point multi-link logical entity, including: The UHR access point multi-link logical entity sends the buffered downlink data to the non-access point multi-link logical entity through the second access point multi-link logical entity.

16. The method according to claim 14 or 15, wherein: The UHR access point multi-link logical entity sends the buffered downlink data to the non-access point multi-link logical entity, including: The second access point multi-link logical entity sends the buffered downlink data to the first access point multi-link logical entity; and The first access point multi-link logical entity sends the buffered downlink data to the non-access point multi-link logical entity.

17. The method according to any one of claims 1 to 16, wherein: The method further comprises: The UHR access point multi-link logical entity determines the unicast key information of the UHR access point multi-link logical entity according to the upper medium access control UMAC address of the UHR access point multi-link logical entity.

18. The method according to claim 17, wherein: The method further comprises at least one of the following: The UHR access point multi-link logical entity shares, copies or sends the unicast key information of the UHR access point multi-link logical entity to the first access point multi-link logical entity; or The UHR access point multi-link logical entity sends the unicast key information of the UHR access point multi-link logical entity to the non-access point multi-link logical entity.

19. The method according to any one of claims 1 to 18, wherein: The method further comprises: The UHR access point multi-link logical entity determines the multicast key information of one or more links of the first access point multi-link logical entity according to one or more lower medium access control LMAC addresses of the first access point multi-link logical entity.

20. The method according to claim 19, wherein: The method further comprises: The UHR access point multi-link logical entity sends the multicast key information of one or more links of the first access point multi-link logical entity to the non-access point multi-link logical entity.

21. The method according to any one of claims 1 to 20, wherein: Before the UHR access point multi-link logical entity sends the first frame to the non-access point multi-link logical entity, the method further includes: The UHR access point multi-link logical entity sends a sixth frame to the non-access point multi-link logical entity, where the sixth frame is used to indicate that the UHR access point multi-link logical entity has a seamless transition capability.

22. The method according to claim 21, wherein: The sixth frame includes an ultra high reliability (UHR) mobility domain element, and the UHR mobility domain element is used to indicate that the UHR access point multi-link logical entity has a seamless transition capability.

23. The method according to any one of claims 1 to 22, wherein: The method further comprises: The plurality of access point multi-link logical entities of the UHR access point multi-link logical entity receive the seventh frame sent by the non-access point multi-link logical entity; and The multiple access point multi-link logical entities of the UHR access point multi-link logical entity send an eighth frame in response to the seventh frame to the non-access point multi-link logical entity, and the eighth frame is used to determine the first access point multi-link logical entity.

24. A communication method in a wireless local area network, wherein: include: The non-access point multi-link logical entity sends a second frame to the ultra-high reliability UHR access point multi-link logical entity, wherein the second frame is used to initiate a roaming request; The non-access point multi-link logical entity receives a first frame from the UHR access point multi-link logical entity, wherein the first frame is used to indicate roaming reconfiguration; The UHR access point multi-link logical entity includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point multi-link logical entity.

25. The method according to claim 24, wherein the non-access point multi-link logical entity receives the first frame from the UHR access point multi-link logical entity, comprising: The non-access point multi-link logical entity receives a first frame sent by the first access point multi-link logical entity or the second access point multi-link logical entity from the UHR access point multi-link logical entity.

26. The method according to claim 24 or 25, wherein: The first frame includes first link identification information, where the first link identification information is used to indicate a target link of the first access point multi-link logical entity to which the non-access point multi-link logical entity switches; and / or; The second frame includes second link identification information, and the second link identification information is used to indicate the link of the access point multi-link logical entity to which the non-access point multi-link logical entity requests to switch.

27. The method according to claim 26, wherein: The first link identification information includes identification information of the first access point multi-link logical entity and link information of the target link.

28. The method according to claim 26 or 27, wherein: The first frame also includes a first indication, where the first indication is used to indicate a switching mode of the target link.

29. The method according to claim 28, wherein: The first indication is used to indicate an immediate switch, or the first indication is used to indicate a delayed switch, and the first indication is also used to indicate a delay duration of the delayed switch.

30. The method according to any one of claims 24 to 29, wherein: The non-access point multi-link logical entity sends a second frame to an ultra-high reliability UHR access point multi-link logical entity, including: The non-access point multi-link logical entity sends a second frame to the first access point multi-link logical entity or the second access point multi-link logical entity of the UHR access point multi-link logical entity.

31. The method of claim 26, wherein: The access point multi-link logical entity and the link indicated by the second link identification information are determined by the non-access point multi-link logical entity according to the signal quality of the downlink signal of at least one access point multi-link logical entity attached to the UHR access point multi-link logical entity.

32. The method according to any one of claims 24 to 31, wherein: Before the non-access point multi-link logical entity sends the second frame to the ultra-high reliability UHR access point multi-link logical entity, the method further includes: The non-access point multi-link logical entity receives a third frame from the UHR access point multi-link logical entity, the third frame including third link identification information, and the third link identification information is used to indicate the candidate access point multi-link logical entity and / or candidate link to which the UHR access point multi-link logical entity recommends that the non-access point multi-link logical entity switch.

33. The method of claim 32, wherein: The third frame includes a candidate list field, wherein the candidate list field includes at least one sub-element, the at least one sub-element corresponds to at least one candidate access point multi-link logical entity, and the at least one sub-element is used to indicate one or more candidate links of the at least one candidate access point multi-link logical entity.

34. The method according to claim 32 or 33, wherein: The access point multi-link logical entity and the link indicated by the second link identification information in the second frame are determined by the non-access point multi-link logical entity according to the link quality of the candidate link of the candidate access point multi-link logical entity indicated by the third link identification information.

35. The method according to any one of claims 24 to 34, wherein: After the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the method further includes: The non-access point multi-link logical entity receives a fifth frame from the UHR access point multi-link logical entity, wherein the fifth frame includes fifth link identification information; The fifth link identification information is used to indicate that one or more remaining links of the non-access point multi-link logical entity are switched to the associated first access point multi-link logical entity, and the one or more remaining links include one or more links other than the target link in the links associated with the non-access point multi-link logical entity and the second access point multi-link logical entity.

36. The method according to any one of claims 24 to 35, wherein: After the target link of the non-access point multi-link logical entity has been switched to be associated with the first access point multi-link logical entity, the method further includes: The non-access point multi-link logical entity receives the buffered downlink data from the UHR access point multi-link logical entity, wherein the buffered downlink data is the downlink data buffered on the target link before switching.

37. The method according to claim 36, wherein the non-access point multi-link logical entity receives the buffered downlink data from the UHR access point multi-link logical entity, comprising: The non-access point multi-link logical entity receives the buffered downlink data sent by the UHR access point multi-link logical entity through the second access point multi-link logical entity.

38. The method according to claim 36 or 37, wherein the non-access point multi-link logical entity receives the buffered downlink data from the UHR access point multi-link logical entity, comprising: The non-access point multi-link logical entity receives the buffered downlink data sent by the UHR access point multi-link logical entity through the first access point multi-link logical entity, wherein the buffered downlink data is forwarded by the second access point multi-link logical entity to the first access point multi-link logical entity.

39. The method according to any one of claims 24 to 38, wherein: The method further comprises: The non-access point multi-link logical entity receives unicast key information of the UHR access point multi-link logical entity from the UHR access point multi-link logical entity, wherein the unicast key information is determined according to an upper medium access control UMAC address of the UHR access point multi-link logical entity.

40. The method according to any one of claims 24 to 39, wherein: The method further comprises: The non-access point multi-link logical entity receives multicast key information of one or more links of the first access point multi-link logical entity from the UHR access point multi-link logical entity, wherein the multicast key information of the one or more links is determined respectively according to one or more lower medium access control LMAC addresses of the first access point multi-link logical entity.

41. The method according to any one of claims 24 to 40, wherein: Before the non-access point multi-link logical entity receives a first frame from the UHR access point multi-link logical entity, the method further includes: The non-access point multi-link logical entity receives a sixth frame from the UHR access point multi-link logical entity, where the sixth frame is used to indicate that the UHR access point multi-link logical entity has a seamless transition capability.

42. The method according to claim 41, wherein: The sixth frame includes an ultra high reliability (UHR) mobility domain element, and the UHR mobility domain element is used to indicate that the UHR access point multi-link logical entity has a seamless transition capability.

43. The method according to any one of claims 24 to 42, wherein: The method further comprises: The non-access point multi-link logical entity sends a seventh frame to a plurality of access point multi-link logical entities of the UHR access point multi-link logical entity; and The non-access point multi-link logical entity receives an eighth frame sent by multiple access point multi-link logical entities of the UHR access point multi-link logical entity, where the eighth frame is used to determine the first access point multi-link logical entity.

44. An access point device, wherein: include: A receiving module, configured to receive a second frame from a non-access point multi-link logical entity, wherein the second frame is used to initiate a roaming request; A sending module, configured to send a first frame to a non-access point multi-link logical entity, wherein the first frame is used to indicate roaming reconfiguration; The access point device includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point multi-link logical entity.

45. A non-access point device, wherein: include: A sending module, configured to send a second frame to an ultra-high reliability UHR access point multi-link logical entity, wherein the second frame is used to initiate a roaming request; A receiving module, configured to receive a first frame from the UHR access point multi-link logical entity, wherein the first frame is used to indicate roaming reconfiguration; The UHR access point multi-link logical entity includes a first access point multi-link logical entity and a second access point multi-link logical entity, and the second access point multi-link logical entity is associated with the non-access point device.

46. ​​An access point multi-link device, wherein: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 1 to 23.

47. A non-access point multi-link device, wherein: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method as claimed in any one of claims 24 to 43.

48. A chip, wherein: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 23, or a method as claimed in any one of claims 24 to 43.

49. A computer-readable storage medium, wherein: Used to store a computer program, the computer program causing a computer to execute the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 43.

Images