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

[Amended to Article 26 of the Detailed Rules, dated November 2024] Communication methods, devices, equipment and systems in wireless local area networks

[0001] This application claims priority to Chinese Patent Application No. 202311457656.1, filed on November 3, 2023, entitled "Communication Method, Apparatus, Device and System in Wireless Local Area Network"; Chinese Patent Application No. 202311479127.1, filed on November 8, 2023, entitled "Communication Method, Apparatus, Device and System in Wireless Local Area Network"; and Chinese Patent Application No. 202311572418.5, filed on November 22, 2023, entitled "Communication Method, Apparatus, Device and System in Wireless Local Area Network", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This 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 Technology

[0003] In related technologies, when a mobile device moves from the coverage area of ​​one access point (AP) to the coverage area of ​​another AP, it needs to switch the connection between the mobile device and the different APs. However, there are many signaling interactions during the switching process, resulting in a large switching delay, which may cause data transmission interruption. Therefore, how to achieve seamless roaming to ensure the continuity of data transmission is an urgent problem to be solved.

[0004] Summary of the Invention

[0005] This application provides a communication method, apparatus, device, system, and storage medium in a wireless local area network.

[0006] This application provides a communication method in a wireless local area network, including:

[0007] The UHR access point multilink logical entity receives a second frame from a non-access point multilink logical entity, wherein the second frame is used to initiate a roaming request;

[0008] The UHR access point multilink logical entity sends a first frame to the non-access point multilink 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] This 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] Exemplary embodiments of this application provide a method for constructing a communication frame, the frame being applied to wireless network communication of an ultra-high reliability (UHR) access point multilink logical entity, comprising: generating a first indication field, the first indication field indicating that a non-access point multilink logical entity is to be switched to one or more links associated with a first access point multilink logical entity, wherein the first access point multilink logical entity is attached to the UHR access point multilink logical entity.

[0015] In some embodiments, the first indication field is used to indicate the logical entity identification information corresponding to the first access point multi-link logical entity, and the 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 further includes an 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 content of the field included in the first indication field depends on the value of the action field.

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

[0021] Exemplary embodiments of this application provide a method for constructing a communication frame, the frame being applied to wireless network communication of a multi-link logical entity of an ultra-high reliability (UHR) access point, comprising: generating a UHR mobility domain element field, the UHR mobility element field including 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 identifier 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] Various embodiments of this application provide an access point apparatus, including: a sending module configured to send a first frame to a non-AP multi-link logical entity, wherein the first frame includes first link identification information, the first link identification information indicating that the non-AP multi-link logical entity is to be switched to a target link associated with the first access point multi-link logical entity.

[0027] Various embodiments of this application provide an access point device, including:

[0028] The receiving module is used 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] The sending module is used 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, wherein the second access point multi-link logical entity is associated with the non-access point multi-link logical entity.

[0031] Various embodiments of this application provide a non-access point device, including:

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

[0033] The receiving module is configured to receive a first frame from the multi-link logical entity of the UHR access point, 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, wherein the second access point multi-link logical entity is associated with the non-access point device.

[0035] Exemplary embodiments of this application provide an access point multilink device, including: a processor and a transceiver; wherein, the processor is used to invoke a computer program to cooperate with the transceiver to implement the communication methods described in the above embodiments.

[0036] This application provides a non-access point multilink device, including a processor and a transceiver; wherein the processor is used to call a computer program to cooperate with the transceiver to implement the communication methods described in the above embodiments.

[0037] This application provides a communication system in a wireless local area network, comprising: an access point device or an access point multi-link device according to the above embodiments, and a non-access point device or a non-access point multi-link device according to the above embodiments.

[0038] Each exemplary embodiment of this application provides a computer-readable storage medium storing instructions, which, when executed by a processor, enable the processor to perform the communication method in the wireless local area network provided in the above embodiments.

[0039] Each exemplary embodiment of this application provides a computer program product, including computer program instructions that cause a computer to execute the communication method in the wireless local area network provided in the above embodiments. Attached Figure Description

[0040] To more clearly illustrate the technical solution of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other embodiments can be obtained from these drawings without creative effort.

[0041] Figure 1 shows the network architecture diagram of the application environment of the communication method in the wireless local area network provided in the embodiment of this application.

[0042] Figure 2 illustrates an application scenario of the communication method in a wireless local area network provided in an embodiment of this application.

[0043] Figure 3 shows a schematic diagram of the structure of the mobility domain element field provided in an embodiment of this application.

[0044] Figure 4 shows a schematic diagram of the structure of the seamless transition capability field of the mobility domain element field provided in the embodiment of this application.

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

[0046] Figure 6 shows a schematic diagram of the structure of the Basic Service Set (BSS) Transmit Management (BTM) roaming frame provided in the embodiments of this application.

[0047] Figure 7 shows a schematic diagram of the values ​​of the Action subfield of the BTM roaming frame provided in the embodiments of this application and their functional correspondence.

[0048] Figure 8 shows a schematic diagram of the structure of the CommonInfo subfield of the BTM roaming frame provided in the embodiments of this application.

[0049] Figure 9 shows a schematic flowchart of the network access procedure of the communication method provided in the embodiments of this application.

[0050] Figure 10 shows a schematic flowchart of the network access process of the communication method provided in the embodiment of this application.

[0051] Figure 11 shows a schematic diagram of the structure of the KDE field of the key information of the multicast key in the communication method provided in the embodiments of this application.

[0052] Figure 12 shows a schematic diagram of the structure of the FTE field of the Fast Transition protocol for the key information of the multicast key in the communication method provided in the embodiments of this application.

[0053] Figure 13 shows a schematic diagram of a communication method in a wireless local area network provided in an embodiment of this application.

[0054] Figure 14 shows a schematic diagram of another communication method in a wireless local area network provided in an embodiment of this application.

[0055] Figure 15 shows a partial flowchart of the seamless roaming process in the communication method provided in the embodiments of this application.

[0056] Figure 16 shows a schematic diagram of the remaining flow of the seamless roaming process in the communication method shown in Figure 15.

[0057] Figure 17 shows a schematic flowchart of a seamless roaming process for a communication method provided in another embodiment of this application.

[0058] Figure 18 shows a schematic flowchart of a seamless roaming process for a communication method according to another embodiment of this application.

[0059] Figure 19 illustrates the BTM request frame format of a seamless roaming procedure according to another embodiment of this application, and the structure of the Neighbor Report element in the BSS transition candidate entry field.

[0060] Figure 20 illustrates the format of the BSS transition candidate preference sub-element of the BSS transition candidate entry field in another embodiment of this application.

[0061] Figure 21 illustrates the basic multi-link element structure of the BSS transition candidate entry field according to another embodiment of this application.

[0062] Figure 22 shows a schematic flowchart of a seamless roaming process for a communication method according to another embodiment of this application.

[0063] Figure 23 illustrates the ST capability field format of the UHR mobility domain element in the network access procedure of another embodiment of this application.

[0064] Figure 24 shows the values ​​of the Seamless BSS Transition Mode of the ST capability field in another embodiment of this application and their corresponding meanings.

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

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

[0067] Figure 27 shows a block diagram of the access point multilink device provided in an embodiment of this application.

[0068] Figure 28 shows a block diagram of a non-access point multilink device provided in an embodiment of this application. Detailed Implementation

[0069] While this application allows for various forms of embodiments, embodiments of the application, including preferred embodiments, are shown in the accompanying drawings which are to be specifically described herein. It should be understood that the disclosure herein is to be considered an explanation of the principles of the application and is not intended to limit the broad aspects of the application to the one or more embodiments shown or disclosed.

[0070] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application. In the absence of conflict, the embodiments and features in the embodiments of this application can be arbitrarily combined with each other, and the technical solutions formed by any combination are still within the scope of protection sought by this application. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.

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

[0072] When using the terms "comprising," "having," and "including" as described in this application, another component may be added unless explicitly qualifying terms such as "only," "consisting of," etc. are used. Unless otherwise stated, singular terms may include plural forms and should not be construed as having only one quantity.

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

[0074] Figure 1 is a schematic diagram of an application scenario applicable to an embodiment of this 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 the number of APs involved in AP 202 is not limited; Figure 1 only uses 3 APs as an example. The APs shown in Figure 1 can be multi-link access logical entities, such as non-co-located multi-link access logical entities, all of which are attached to Ultra High Reliability (UHR) multi-link logical entities.

[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, or laptop computer; in addition, a related client can be installed on site 201. The client can be software, such as an application (APP), browser, short video software, or web page, mini program, etc.

[0077] To facilitate understanding of the embodiments of this application, the related technologies of this application will be described.

[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 to enhance functionality. In 802.11be networks, wireless devices can support multi-link communication. Multi-link communication means that the wireless device can communicate simultaneously on multiple frequency bands, or simultaneously on different channels within the same frequency band. Wireless devices that support multi-link communication are typically called multi-link devices (MLDs). An MLD has one or more STAs (Stations).

[0079] Multi-link devices in Wireless Local Area Networks (WLANs) are divided into two categories: Access Point (AP) multi-link devices and non-Access Point (non-AP) multi-link devices. In an AP MLD (Access Point Multi-Link LD), the STA is called an AP STA, and in a Non-AP MLD, the STA is called a non-AP STA. For simplicity, AP STAs are usually referred to as APs, and non-AP STAs as STAs.

[0080] One or more links can be established between non-access point multi-link devices and access point multi-link devices, forming associated links. Each associated link connects one non-AP STA in the non-access point multi-link device and one AP in the access point multi-link device.

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

[0082] Figure 2 illustrates an exemplary architecture 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 communicates independently 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), which can be associated with multiple links (link 0 to link N as shown). The N APs communicate with the corresponding N LMACs and converge to a 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 communication of EHT AP MLD 1 to EHT AP MLD N.

[0083] In traditional Wi-Fi technology, normal roaming allows mobile devices (STAs) to switch connections between different access points (APs) when moving from one AP's coverage area to another, ensuring internet performance. However, with normal roaming, when a mobile device moves from one AP's coverage area to another, the user needs to manually disconnect 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, data transmission reliability, and a degraded user experience.

[0084] Therefore, Fast Transition (FT) roaming technology was introduced into traditional Wi-Fi technology. FT roaming technology is a fast Wi-Fi roaming technology, also known as 802.11r. It can embed the four-way key handshake process with the target AP into the re-association process when a mobile device moves from one AP to the coverage area of ​​another AP, thereby achieving the purpose of fast AP switching.

[0085] However, whether it's regular roaming or FT roaming, the following issues arise when switching access points:

[0086] 1. Mobile devices incur significant frame overhead during AP switching and require link authentication, namely 802.1X Extensible Authentication Protocol (EAP) authentication and a four-way handshake roaming handover process, resulting in substantial latency.

[0087] 2. During the mobile device roaming process, the transmission of user data may be interrupted, the continuity of data cannot be guaranteed, the reliability of data transmission decreases, and the user experience deteriorates.

[0088] The communication method provided in this application embodiment can achieve seamless roaming of mobile devices through UHR multi-link logical entities, reduce handover latency during roaming, and ensure the continuity of data transmission.

[0089] The exemplary embodiments of this application provide a communication method applied to a UHR multi-link logical entity, which enables fast roaming while ensuring the continuity of data transmission.

[0090] To this end, embodiments of this application introduce seamless roaming frames and add fields to 802.11be frames. These introduced frames and fields will be 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 this application is only an example, and they can be replaced with other names, which are not limited in this application.

[0092] Figure 3 shows a schematic diagram of the structure of a UHR mobility domain element field provided in an embodiment of this application.

[0093] UHR mobility domain element fields are used to declare either Seamless Transition Capability or Seamless Roaming Capability. For example, UHR mobility domain element fields include a Seamless Transition Capability field, which is used to declare either 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 may also include at least one of element ID, length, or mobility domain ID (MDID), wherein the MDID field is an identifier that names the UHR roaming mobility domain.

[0096] UHR mobility domain element fields can be appended to Beacon frames, Probe Response frames, Association Request frames, Association Response frames, and Authentication frames from the UHR AP MLD (or AP) to declare the seamless transition capability of the UHR AP MLD (e.g., to non-access point multilink devices). The extended structures of these frames will be further explained below.

[0097] It is understood that the UHR mobility domain element field can also be appended to frames from non-AP STA MLD (or non-AP STA). When the UHR mobility domain element field is appended to a frame from a 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 to these frames.

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

[0100] Figure 4 illustrates the structure of the Seamless Transition Capability (ST Capability) field in a UHR mobility domain element field according to an embodiment of this application. The Seamless Transition Capability field declares the seamless transition capability of an AP or non-AP STA capable of performing a Seamless Basic Service Set (BSS) transition.

[0101] The Seamless Transition Capability field may include a Seamless Basic Service Set Transition Status subfield. Optionally, 1 bit may be used to indicate the Seamless Basic Service Set Transition Status.

[0102] In some embodiments, when the MLD has seamless transition capabilities, the seamless basic service set transition status subfield can be set to 1; otherwise, it can be set to 0. Of course, more bits can also be used to indicate the seamless basic service set transition status, and this application embodiment does not limit this.

[0103] Optionally, the seamless transition capability field may also include a reserved field. The length of the reserved field can be 7 bits, or it can be any other number of bits; this embodiment of the application does not impose any particular limitation on this.

[0104] Figure 5 shows a schematic diagram of the frame structure extension field of a UHR mobility domain element field provided in an embodiment of this application.

[0105] As mentioned above, 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 the 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 Figure 5, when the value of the "dot11SeamlessBSSTransitionActivated" field is true, the UHR mobility domain element field can exist at the end of the aforementioned frames; that is, the UHR mobility domain element field can be added to the reserved fields of these frames or extended at the end of these frames.

[0106] Alternatively, the UHR mobility domain element field can also be added to other positions in the above frame, and this application embodiment does not particularly limit this.

[0107] Alternatively, the existence of a UHR mobility domain element field can be determined based on fields other than the "dot11SeamlessBSSTransition Activated" field, and this application embodiment does not particularly limit this.

[0108] Figure 6 shows a schematic diagram of the structure of a BSS Transmit Management (BTM) roaming frame provided in an embodiment of this application.

[0109] To achieve seamless roaming in the UHR AP MLD environment, BTM roaming frames are introduced for roaming message exchange between non-access point multi-link logical entities (e.g., non-AP STA MLD) and UHR AP MLD. Roaming messages include roaming requests (e.g., sent from non-AP STA MLD to UHR AP MLD), roaming link switching indications (e.g., sent from UHR AP MLD to non-AP STA MLD), and roaming link switching confirmations (e.g., sent from non-AP STA MLD to UHR AP MLD).

[0110] As shown in Figure 6, the BTM roaming frame contains an Action field. Optionally, the Action field can be 1 octet long, or more bytes, such as 2 octets, 5 octets, or 10 octets.

[0111] Optionally, as shown in Figure 6, the BTM roaming frame may also include a Category field.

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

[0113] Optionally, as shown in Figure 6, the BTM roaming frame may also include a Dialog Token field, which is a non-zero value taken by the STA that sent the BTM roaming frame to identify whether the frame type is a request frame type or a response frame type.

[0114] Figure 7 illustrates the values ​​of the Action field of a BTM roaming frame and their functional correspondences according to an embodiment of this application. Different values ​​in the Action field correspond to 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 type. When the action field value is 29, the BTM roaming frame is a roaming reconfigure frame type. When the action field value is 30, the BTM roaming frame is a roaming confirm frame type.

[0116] As shown in Figure 6, the BTM roaming frame also 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 in an embodiment of this application. When the value in the Action field is different, that is, when the type of BTM roaming frame is different (which may also indicate that the frame's sender and receiver are different), the roaming information carried in the corresponding Common Info field is also different.

[0118] The public information fields of the BTM roaming frame include at least the MLD AP ID field and the Links Info field.

[0119] Optionally, the public information field may also include a length field, which is used to indicate the length of fields other than the length field in the public information field.

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

[0121] When the BTM roaming frame is a BTM roaming confirmation frame, the public information field may also 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 Links Info field, a Status Code field, and a STA Control field.

[0123] The length field indicates the length of the fields in the public information field other than the length field itself. The length field can be 1 octet, and in other embodiments, the length field can be longer, such as 2 octets, 5 octets, or 10 octets. This application does not impose any particular limitation on this.

[0124] The MLD AP ID field indicates the identifier of the requested AP MLD, i.e., the identifier of the MLD AP to which the user is requested to switch. The length of the MLD AP identifier field is 1 octet. In other embodiments, the length of the MLD AP identifier field may also be longer, such as 2 octets, 5 octets, or 10 octets. This application does not impose any particular limitation on this.

[0125] The Link Information field indicates the link information of the target link, specifically the link information of the target link that the non-AP MLD is expected to disconnect from the original MLD AP and associate with the new MLD AP. The length of the Link Information field is variable, 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 Figure 8, the link information field may include a link number field and one or more link identification information fields. The link number field indicates the number of links for which a switchover (or disconnection request) is requested, or in other words, the number of target links. The link identification information field indicates the link identifier of the link for which a switchover is requested, or in other words, 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 repeated here. 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, such as 2 octets, 5 octets, or 10 octets. This application does not make any particular limitation on this.

[0128] Optionally, as shown in Figure 8, the STA control field described above may include a Link Deletion Mode field. The length of the Link Deletion Mode field can be 8 bits. In other embodiments, the length of the Link Deletion Mode field can also be other values, such as 4 bits, 12 bits, or 16 bits.

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

[0130] For example, when the link deletion mode field is 1 bit, setting it to 0 immediately disconnects (or deletes, switches) the requested link. Setting it to 1 allows waiting for a specified time period before disconnecting (or deleting, switching) the requested link.

[0131] Alternatively, when the link deletion field is 2 bits, if the link deletion mode field is set to 0, the association with the link can be immediately disconnected. If the link deletion mode field is set to 1, 2, or 3, the association with the link will be 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 Deletion Count field to indicate the delay duration for delayed disconnection. The Link Deletion Count field may indicate the time to wait for a specified number of Time Units (TUs) after receiving a corresponding frame before disconnecting (or deleting, switching) the requested link. The Link Deletion Count field may also indicate other physical quantities to control the waiting time for disconnecting (or deleting, switching) the requested link. The length of the Link Deletion Count field can be 8 bits; in other embodiments, the length may also be other values, such as 4 bits, 12 bits, or 16 bits.

[0133] Figure 9 shows a schematic diagram of an access process for a communication method provided in an embodiment of this application.

[0134] As shown in Figure 9, during the network access process, after completing probing, multi-link authentication, and association, non-AP STA MLDs and / or UHR AP MLDs can calculate and generate unicast keys (e.g., paired transition keys (PTKs)) through EAPOL key frames. 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 generated during the network access procedure and then shared with multiple AP MLDs of the UHR AP MLD. Alternatively, the PTK can be generated during the network access procedure, stored in the UHR AP MLD UMAC, and then shared with a designated AP MLD by the UHR AP MLD UMAC during the seamless roaming process.

[0136] In addition, multicast keys (e.g., group ephemeral key (GTK), integrated group ephemeral key (IGTK), Beacon integrated group ephemeral 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 will calculate these multicast keys and send or instruct them to the corresponding non-AP STA MLD, which will then store these multicast keys. These multicast keys can be calculated by the UHR AP MLD UMAC and sent by the UHR AP MLD UMAC, or they can be calculated by 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, or they can be sent back to the UHR AP MLD UMAC first and then sent to the corresponding non-AP STA MLD through 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] Alternatively or alternatively, when a non-AP STA MLD is in or before a seamless roaming process, the UHR AP MLD will send or instruct the multicast key to that non-AP STA MLD.

[0140] Optionally, in some embodiments, the identification information of the AP MLD corresponding to the corresponding link can be added to these multicast key information to avoid confusion of co-frequency links of different AP MLDs in non-co-located environments, which will be explained in detail in later embodiments.

[0141] Based on this design of unicast and multicast keys, in the UHR AP MLD architecture, during the seamless roaming process of a non-AP STA MLD switching from MLD1 to MLD2, when the non-AP STA 10MLD switches to the new AP MLD, there is no need to re-authenticate, re-associate, and perform a 4-way handshake on the key again. This shortens the frame overhead of seamless roaming and reduces the roaming authentication latency caused by the FT roaming mechanism.

[0142] The working principle of unicast and multicast keys during seamless roaming will be described in the following detailed implementation.

[0143] Figure 10 shows a schematic flowchart of the network access process of a communication method provided in another embodiment of this application.

[0144] In step S1500, after the Non-AP STA powers on, it first enters passive scanning mode, listening for beacons on the supported links. Then, the Non-AP STA enters active scanning mode, actively sending ordinary probe request frames on each link. The UHR AP MLD receives these ordinary probe request frames and controls the EHT AP MLD LMAC to send back ordinary probe responses. The send and receive addresses for these ordinary probe frames are set to the addresses bound to the links to avoid misunderstandings with other links on the same frequency. Therefore, the TA (Transmission Address) of the probe response frame is filled with the Link Mac Address of the EHT AP MLD LMAC, and the RA (Range Address) is filled with the Link Mac Address of the Non-AP STA.

[0145] In step S1510, after the Non-AP STA completes the scan, it integrates all the scan results and selects the optimal 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 scanning. At the same time, the STA Control carries information about other links in the Link Info.

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

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

[0149] In step S1550, the UHR AP MLD responds 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, carrying other link information.

[0151] In step S1570, the UHR AP MLD responds to the Multi-Link Assoc Response on the received Link and responds to whether the association was successful or failed on the corresponding Non-AP STA request Link.

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

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

[0154] Figure 11 shows a schematic diagram of the structure of the KDE field of the key information of the multicast key in the communication method provided in the embodiments of this application.

[0155] For each associated link, the UHR AP MLD and non-AP STA MLD use different multicast keys for broadcasting, such as GTK\IGTK\BIGTK. That is, the multicast key is designed and calculated at the link level. For example, GTK\IGTK\BIGTK is calculated through 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. To ensure the execution of the four-step handshake during the network access process, this embodiment extends the EAPOK key KDE (e.g., GTK KDE, IGTK KDE, and BIGTK KDE) with new fields, such as the AP MLD ID field. The AP MLD ID field is used to identify the AP MLD corresponding to the link ID. Therefore, in a co-located UHR AP MLD architecture, the AP MLD ID field, combined with the link ID field, can distinguish co-frequency links of different AP MLDs.

[0157] Figure 12 shows a schematic diagram of the structure of the FTE field of the FT protocol for the key information of the multicast key in the communication method provided in the embodiments of this application.

[0158] Similarly, to ensure the execution of the four-step handshake during the network access process, this application embodiment extends the FTE field of the FT protocol in a similar way. For example, it adds an AP MLD identifier field to the MLOGTK, MLO IGTK, and MLO BIGTK sub-elements. This AP MLD identifier field, combined with the Link ID Info field, can distinguish co-frequency links with different AP MLDs.

[0159] Figure 13 shows a flowchart of a communication method in a wireless local area network provided in an embodiment of this application.

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

[0161] S210, the UHR access point multilink logical entity sends a first frame to the non-access point multilink logical entity, wherein the first frame includes first link identification information, which is used to indicate the target link of the first access point multilink logical entity (i.e., the target access point multilink logical entity, such as the target AP MLD) to which the non-access point multilink 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 multilink logical entity may be a UHR AP MLD. The UHR access point multilink logical entity includes a first access point multilink logical entity (e.g., EHT AP MLD2, hereinafter referred to as AP MLD2) and a second access point multilink logical entity (e.g., EHT AP MLD1, hereinafter referred to as AP MLD1) attached to the UHR AP MLD. The second access point multilink logical entity includes multiple links (e.g., Link0 and Link1) associated with a non-access point multilink logical entity (e.g., a non-AP STA MLD, hereinafter referred to as STA MLD).

[0164] It is understood that the UHR access point multilink logical entity can send frames to the non-access point multilink logical entity through the access point multilink entity (i.e., the second access point multilink logical entity, or the original AP MLD, serving AP MLD) associated with the non-access point multilink logical entity in the UHR access point multilink logical entity, or through the UHR control module (e.g., the non-collocated control module) in the UHR access point multilink logical entity, or the UHR control module instructs the second access point multilink logical entity to send them.

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

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

[0167] In some embodiments, the first frame may be a BTM roaming frame, for example, a BTM roaming reconfigure frame.

[0168] In some embodiments, BTM roaming reconfiguration frames may include UHR mobility domain elements to indicate whether the UHR multilink 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, sending a first frame from a UHR access point multilink logical entity to a non-access point multilink logical entity may include:

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

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

[0173] The UHR control module instructs the first frame to be sent to the non-access point multilink logical entity.

[0174] In some embodiments, the target link for a non-access point multilink logical entity to switch to a first access point multilink logical entity may refer to: the non-access point multilink logical entity expects to disconnect the target link (e.g., Link0) from the second access point multilink logical entity (i.e., the original AP MLD, such as AP MLD1), and expects to associate the target link with the first access point multilink entity (i.e., the target AP MLD, such as AP MLD2) attached to the same UHR AP LMD.

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

[0176] Optionally, the first link identification information can be carried in the public information field of the BTM roaming frame.

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

[0178] Optionally, the public 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 which the user is to switch, and the link information field is used to indicate the link information of the target link.

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

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

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

[0182] Optionally, the switching method can be immediate switching.

[0183] Optionally, the switching method can be a delayed switching. Optionally, in this case, the first indication can also indicate the delay duration of the delayed switching.

[0184] In one specific embodiment, the first indication is used to indicate a link deletion mode, or a link deletion mode and a link deletion count, thereby enabling delayed disconnection.

[0185] In some embodiments of this application, before the UHR access point multilink logical entity sends the first frame to the non-access point multilink 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, sending a second frame from a non-access point multi-link logical entity to the UHR access point multi-link logical entity may include:

[0188] The non-access point multi-link logical entity sends the 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, which is used to indicate the link of the access point multilink logical entity to which the non-access point multilink logical entity requests to switch.

[0191] For example, after receiving the second frame, the UHR access point multilink logical entity learns that the non-access point multilink logical entity expects to switch the target link from the second access point multilink logical entity to the first access point multilink logical entity. Therefore, the UHR AP MLD UMAC can instruct (including indirect instruction or direct control) to disconnect the association between the second access point multilink logical entity and the target link, and instruct (including indirect instruction or direct control) to associate the first access point multilink logical entity with the target link; that is, the first access point multilink logical entity and the non-access point multilink logical entity are associated through the target link.

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

[0193] Optionally, the second link identification information can be carried in the public information field of the 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. The MLD AP ID field indicates 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 indicates the 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 following: number of links, link identifier, link handover order, and link priority.

[0195] Optionally, the BTM roaming request frame may also include a UHR mobility domain element to indicate whether the non-access point multilink logical entity has UHR radio transition capability.

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

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

[0198] The UHR control module instructs the second access point multilink logical entity to disconnect the association with the target link, and the second access point multilink 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 multilink logical entity to disconnect from the target link (e.g., Link0), and indirectly instruct or directly control the first access point multilink 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 obtained based on the UMAC address of the UHR AP MLD stored in the UHR AP MLD UMAC to the first access point multilink logical entity, thereby enabling the non-access point multilink logical entity and the first access point multilink logical entity to no longer need to handshake and negotiate the unicast key when switching links in wireless roaming, reducing frame overhead and roaming latency.

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

[0202] Under preset conditions, the UHR access point multilink logical entity determines that the target link of the non-access point multilink logical entity has been switched to be associated with the first access point multilink logical entity.

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

[0204] In some embodiments, the preset conditions include at least one of the following:

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

[0206] The UHR access point multi-link logical entity sent the first frame after a preset time.

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

[0208] Optionally, the fourth frame can 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 after a preset time, it is considered that the non-access point multi-link logical entity has retransmitted the link reconfiguration.

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

[0211] Optionally, the fourth indication can be carried in the status code field of the 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 cached downlink data to the non-access point multi-link logical entity, wherein the cached downlink data is the downlink data already cached on the target link before the handover.

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

[0215] The UHR access point multi-link logical entity sends the cached 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 cached downlink data to the first access point multi-link logical entity, and the first access point multi-link logical entity sends the cached downlink data to the non-access point multi-link logical entity.

[0217] For example, after the target link of a 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 switchover to the non-access point multi-link logical entity through the original AP MLD. For example, after the target link of a 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 cached on the target link before the switchover through at least one associated link other than the target link after the switchover, wherein 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 will send the cached downlink data to the non-access point multi-link logical entity.

[0219] In some embodiments, the switching of the target link of the non-access point multi-link logical entity to be associated with the first access point multi-link logical entity may include: the target link to be switched associated with the non-access point multi-link logical entity has completed the disconnection of its association with 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's instruction to send cached downlink data for the target link before the handover through at least one associated link other than the target link after the handover can mean that, since at least one or more links that have completed the handover on the UHR AP MLD side need to continue sending cached downlink data to the non-access point multi-link logical entity through other still associated links of the second access point multi-link logical entity before the handover, the new data acquired by the UHR AP MLD for sending to the non-access point multi-link logical entity can be sent by the newly associated first access point multi-link logical entity through the newly associated link, as instructed by the UHR AP MLD UMAC.

[0221] In some embodiments, the UHR control module instructs the transmission of cached downlink data intended for the target link prior to the handover via at least one associated link other than the target link after the handover, including:

[0222] The UHR control module makes the cached downlink data accessible to at least one associated link other than the target link after the handover; and the UHR control module instructs the cached downlink data to be sent through the at least one associated link.

[0223] In some embodiments, the UHR control module makes the cached downlink data accessible to 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 at least one associated link outside the target link after the switchover;

[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 the cached downlink data to be sent to the UHR control module.

[0227] For example, the UHR control module can instruct the access point multilink logical entity that caches the downlink data to send the corresponding downlink data back to the UHR control module, and the UHR control module can instruct other access point multilink logical entities associated with non-access point multilink logical entities to continue forwarding this downlink data.

[0228] Alternatively or alternatively, the UHR control module may instruct the access point multilink logical entity that caches the downlink data to allow other links associated with non-access point multilink logical entities to continue transmitting the corresponding downlink data by means of direct transmission, sharing, or copying.

[0229] Alternatively or additionally, the UHR control module may instruct the access point multilink 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 then send it to a non-access point multilink 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 multilink logical entity to preferentially receive uplink data from the non-access point multilink 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 the data received after the target link is switched, with the target address being the non-access point multi-link logical entity, to be sent 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, the fifth frame including fifth link identification information;

[0236] The fifth link identification information is used to indicate switching one or more remaining links of the non-access point multi-link logical entity to the associated first access point multi-link logical entity. 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, used to complete the roaming handover of all links of a non-access point multi-link logical entity.

[0238] In some embodiments, the fifth frame may be sent by the UHR access point multilink logical entity through the access point multilink logical entity of the remaining unswitched link (e.g., the second access point multilink logical entity), or it may be sent through the access point multilink logical entity corresponding to the target link (i.e., the first access point multilink logical entity).

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

[0240] The UHR access point multi-link logical entity determines its first key information based on its Upper Media Access Control (UMAC) address. The first key information may include unicast key information, such as a 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 includes:

[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 the associated links of the first access point multi-link logical entity.

[0245] In some embodiments, the first key information may be shared, copied, or sent by the UHR control module to multiple access point multi-link logical entities during the network access phase, or it may be shared, copied, or sent to the access point multi-link logical entity to which the user is to be switched during the link switching process of the AP MLD in the wireless roaming process, such as the first access point multi-link logical entity.

[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 includes:

[0248] The UHR access point multilink logical entity sends the unicast key information of the UHR access point multilink logical entity to the non-access point multilink logical entity.

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

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

[0251] The UHR access point multilink logical entity determines the multicast key information of one or more links of the first access point multilink logical entity based on one or more Lower Media Access Control (LMAC) addresses of the first access point multilink logical entity.

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

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

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

[0255] In some embodiments of this 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 multilink logical entity sends a ninth frame to the non-access point multilink logical entity, the ninth frame being configured to request the non-access point multilink logical entity to send the second frame.

[0257] Optionally, the ninth frame can be a BTM roaming inquiry frame. This BTM roaming inquiry frame is used to induce or request a non-access point multilink logical entity to send a BTM roaming request frame.

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

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

[0260] In some embodiments, the sixth frame includes a UHR mobility domain element, which 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 (e.g., to announce the seamless transition capability of UHR AP MLD to non-access point multilink logical entities).

[0263] In some embodiments, the decision for a non-access point multi-link logical entity to begin roaming may be made by the non-access point multi-link logical entity itself. For example, the non-access point multi-link logical entity may decide to begin roaming based on the current link status.

[0264] In other embodiments, the decision to initiate roaming by the non-access point multilink logical entity can also be made by the UHR access point multilink logical entity. For example, the second access point multilink logical entity can decide to trigger the non-access point multilink logical entity to start roaming based on the uplink signal quality of the non-access point multilink 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 based on the uplink signal quality sent by multiple access point multi-link logical entities of the UHR access point multi-link logical entity.

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

[0267] The non-access point multi-link logical entity sends a seventh frame to multiple 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 the eighth frame sent by multiple access point multi-link logical entities of the UHR access point multi-link logical entity, and the eighth frame is used to identify the first access point multi-link logical entity.

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

[0270] Optionally, the seventh frame can be a probe request frame, and the eighth frame can 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 plurality of eighth frames, including: the non-access point multi-link logical entity determining multiple signal qualities of multiple links corresponding to the plurality of eighth frames based on the plurality of eighth frames; and the non-access point multi-link logical entity determining the target link of the first access point multi-link logical entity based on the plurality of signal qualities.

[0272] In some embodiments, the UHR access point multilink logical entity (e.g., the UHR control module) can provide a suggested set of target links and link priorities to the non-access point multilink logical entity. The link priorities can be determined based on the link load of neighboring access point multilink logical entities of the second access point multilink logical entity. Furthermore, the UHR access point multilink logical entity (e.g., the UHR control module) can inform the non-access point multilink logical entity of the target link set and link priorities. The non-access point multilink logical entity can determine the target link based on the target link set and link priorities combined with the signal quality of the link (e.g., obtained through probe response frames).

[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. The third frame includes third link identification information, which is used to indicate to the UHR access point multi-link logical entity the non-access point multi-link logical entity should switch to a candidate access point multi-link logical entity and / or a candidate link.

[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 corresponding 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 indicates whether to recommend that the non-access point multi-link logical entity 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 the switch is recommended.

[0280] Optionally, the third field can indicate one or more suggested candidate links in a bitmap format.

[0281] The structure of the third frame will be further explained below with reference to Figures 19 to 21.

[0282] In some embodiments, the neighboring access point multilink logical entities of the second access point multilink logical entity can evaluate the uplink signal quality, for example, by obtaining the signal quality of the corresponding link through a probe 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 this application, the following description uses two AP MLDs and two associated links as an example. In other embodiments, there may be two or more AP MLDs and / or two or more associated links. Those skilled in the art should understand that in other embodiments of this application, there are many more possible link switching methods for cases with two or more AP MLDs and / or two or more associated links.

[0284] Figure 14 is a schematic flowchart of a communication method provided in an embodiment of this application.

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

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

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

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

[0289] Specifically, the second frame can be a BTM Roaming Request frame. The BTM Roaming Request frame includes indication information indicating the AP MLD to which the handover is to take place and the link to be handed over.

[0290] BTM roaming requests may also include mobility domain elements to indicate whether the STA MLD has UHR seamless transition capability.

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

[0292] Specifically, after receiving the second frame, the UHR AP MLD obtains the new AP MLD (i.e., AP MLD2) that the STA MLD expects to switch Link0 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 and STA MLD are associated through Link0.

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

[0294] Step S940: The cached downlink data used for STA MLD before the link switch is sent through the associated link other than Link0; and the new downlink data received for STA MLD after the link switch is sent through the switched link.

[0295] After the UHR AP MLD completes the Link0 handover as described above, the UHR AP MLD will continue to send the cached downlink data previously used for the non-AP STA MLD through an associated link other than Link0 (e.g., Link1) to the non-AP STA MLD. Specifically, the UHR AP MLD will send the downlink data cached before the handover and originally transmitted to the non-AP STA MLD through Link0 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 are associated with, and the link that MLD2 and the non-AP STA MLD are associated with.

[0296] In addition, the UHR AP MLD will send the new downlink data received by the non-AP STA MLD after the switchover to the non-AP STA MLD via the switched Link0.

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

[0298] Step S960: Send the first frame to 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, BTM roaming reconfiguration frames include UHR mobility domain elements to indicate whether the UHR AP MLD has seamless transition capability.

[0302] In some embodiments, the UHR AP MLD can send the first frame to the non-AP STA MLD through the original 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, the UHR AP MLD UMAC has already shared or copied the unicast key generated during the network access process for AP MLD2 to AP MLD1. Therefore, during seamless roaming, the UHR AP MLD UMAC does not need to share the unicast key with AP MLD1 again.

[0304] Alternatively, in another embodiment, during the network access phase, the UHR AP MLD UMAC does not share or copy the unicast key generated during the network access phase for AP MLD2 to APMLD 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 switched AP MLD (i.e., MLD 1) to complete the link handover on the UHR AP MLD side. This avoids the need to re-perform the four-way key handshake when the non-AP STA MLD switches to the new AP MLD during roaming, reducing frame overhead and shortening roaming latency.

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

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

[0307] The steps for adjusting the internal configuration of a non-AP STA MLD include: adjusting the AP MLD identification information in the field information corresponding to the multicast key so that the multicast key can automatically correspond to the corresponding link of the switched AP MLD, avoiding confusion of the same frequency links of different AP MLDs and saving the frame overhead of re-handshaking.

[0308] After the non-AP STA MLD configuration is adjusted, a 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 its configuration adjustment, it may not send a fourth frame. Instead, the non-AP STA MLD and UHR AP MLD determine whether they have completed the handover configuration based on a specified time period. That is, after a specified time period following the UHR AP MLD sending its 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 will be sent to inform the other party of the handover failure.

[0310] In other embodiments, additionally, after one or a group of links between the non-AP STA MLD and the original AP MLD of the UHR AP MLD have been switched over, the remaining links between the non-AP STA MLD and the original AP MLD are switched over in a similar manner, which will not be described in detail here.

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

[0312] Figure 15 shows a partial flowchart of a wireless roaming process in a communication method provided in an embodiment of this application. As shown in Figure 15, the process may include the following steps:

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

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

[0315] In step S1310, STA MLD decides whether to roam based on the current link status.

[0316] In some embodiments, the current link state 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 STA MLD on the current associated link;

[0319] The load status of the AP MLD on the current associated link;

[0320] Current link load status.

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

[0322] In other embodiments, the UHR AP MLD (e.g., UHR AP UMAC, AP MLD1, or AP MLD2) may also decide whether the STA MLD should roam, 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, within the overlapping signal coverage area, the STA MLD simultaneously or sequentially uses all links of the STA MLD to send probe request frames to adjacent AP MLDs (e.g., AP MLD2). Each adjacent AP MLD is connected to the same UHR AP MLD UMAC, or in other words, is attached to the same UHR AP MLD. Each AP MLD (e.g., AP MLD2) responds to the probe request frames from the STA MLD with a probe response frame.

[0324] In step S1330, the STA MLD determines the link status of each link based on the probe response frames returned by each link, and determines the target AP MLD (e.g., AP MLD2) to be switched to based on the link status of each link.

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

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

[0327] Figure 16 shows a schematic diagram of the remaining steps in 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 over, and sends a BTM roaming request frame to the original AP MLD (i.e., AP MLD1) associated with the target link. The BTM roaming request frame can carry the AP MLD information and link information corresponding to the target link. The BTM roaming request frame is used to request a switch 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 can send the identification information of the AP MLD to which it is to be switched and the link information of the target link to be switched to to the UHR AP MLD. For example, it can send it to any AP MLD that is already associated with the UHR AP MLD (e.g., the AP MLD that was originally associated with the target link), or it can send it to the UHR AP MLD UMAC.

[0330] Step S1350, the UHR AP MLD indicates (including indirect indication or direct control) the link switching on the AP MLD side, specifically including the following steps:

[0331] 1) The original AP MLD (i.e., AP MLD1) sends the above roaming request from the STA MLD back to the UHR AP MLD UMAC (hereinafter referred to as UHR UMAC). The UHR UMAC approves or rejects the above 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 result of approval or rejection.

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

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

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

[0335] In step S1360, after the UHR AP MLD receives the BTM roaming confirmation frame from the STA MLD, the UHR AP MLD UMAC updates the configuration of the target link (Link0).

[0336] Specifically, the UHR AP MLD can prioritize transmitting newly received downlink data after the link handover via the newly associated Link0 between the STA MLD and AP MLD2. Before the link handover is successful, the cached downlink data originally intended for transmission to the STA MLD via the pre-handover Link0 can continue to be transmitted via the remaining associated link between the UHR AP MLD and the STA MLD (i.e., the unhandled associated link). This cached downlink data can be configured by the UHR UMAC to be accessible to the AP MLD corresponding to the remaining associated link. This configuration ensures that downlink data transmission will not be interrupted during the STA MLD roaming process due to the roaming handover, guaranteeing the continuity of data transmission during roaming and improving the reliability of data transmission in wireless roaming.

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

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

[0339] 1) The original AP MLD (i.e., AP MLD1) sends the above roaming request from the STA MLD back to the UHR UMAC. The UHR UMAC approves or rejects the above 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 result of approval or rejection.

[0340] 2) When the UHR UMAC approves the above roaming request, the original AP MLD sends a BTM roaming reconfiguration frame to the STA MLD through the corresponding receiving link. The UHR AP MLD UMAC updates the configuration of the target link (Link0). The UHR AP MLD prioritizes data transmission through the new link between STA MLD's Link0 and MLD2's Link0.

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

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

[0343] In other embodiments, step 4) above can be replaced by:

[0344] 4a) The STA MLD sends a BTM roaming acknowledgment frame to the AP MLD2. This BTM roaming acknowledgment frame indicates whether the STA MLD's Link0 has been successfully reconfigured. When the STA MLD's Link0 is successfully reconfigured, the STA MLD sends a BTM roaming acknowledgment frame to the AP MLD2 through the switched link (from the STA MLD's Link0 to the AP MLD2's Link0) to notify the UHR AP MLD that the STA MLD has successfully completed the reconfiguration.

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

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

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

[0348] Step S1370 completes the handover of the remaining links between the STA MLD and the original AP MLD. This may include, for example, the following steps:

[0349] 1) The UHR AP MLD UMAC determines to perform a handover of 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 (e.g., Link1 of AP MLD1 or Link0 of AP MLD2).

[0350] 2) After receiving the BTM roaming reconfiguration frame, the STA MLD reconfigures the link, switching 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, STA MLD sends a BTM roaming confirmation frame to AP MLD2 through the remaining link after the switch (e.g., Link1).

[0352] 4) Complete the roaming switch of all links of STA MLD. STA MLD only associates with and communicates with AP MLD2.

[0353] Figure 17 shows a schematic flowchart of a seamless roaming process for a communication method provided in another embodiment of this 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 are now associated.

[0356] Step S1610: The STA determines whether 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 carrying the Multi-Link element) to each Link, and all Non-collocated APs MLD attached to the UHR reply with a Probe Response.

[0358] In step S1630, the STA determines the link handover order between the non-collocated AP MLD2 associated with the UHR and the currently associated links based on the signal quality measured by the Probe Response.

[0359] In step S1640, the STA selects a suitable Link from the associated links and sends a BTM Roaming frame (e.g., BTM roaming request) containing a Roaming Request to EHT AP MLD1 (denoted as AP MLD1). The frame carries a Multi-Link reconfigure element and informs AP MLD1 of the EHT AP MLD2 (denoted as AP MLD2) to which it wants to roam and the target switching link, i.e., 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 via the corresponding receiving link, triggering the STA to perform link 1 reconfiguration. The STA disconnects the connection between Link 1 and AP MLD1's link 1, and reconfigures to AP MLD2's link 1. After successful reconfiguration, the STA uses the newly connected Link 1 to send a BTM Roaming Confirm frame to AP MLD2 to confirm the successful reconfiguration. Throughout 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 the UHR AP MLD UMAC completes the Link1 handover, it forwards new service data destined for the STA to AP MLD2 Link1 for transmission. Downlink service data buffered in AP MLD1 Link2 can still be sent to the STA via MLD1 Link2. After the STA successfully completes the link handover, its uplink service data is preferentially transmitted via the already switched-out Link 1. During this process, the STA maintains data communication with MLD1 via Link2 and with MLD2 via Link1.

[0362] In step S1670, the UHR MLD UMAC decides to switch the remaining links. This can be done by sending a BTM Roaming Reconfigure frame to the STA via either Link2 of AP MLD1 or Link1 of AP MLD2, triggering a reconfiguration of Link2 on the STA. Upon receiving this frame, the STA reconfigures Link2 from AP MLD1 to AP MLD2. After successful reconfiguration, the STA sends a BTM Roaming Confirm frame to AP MLD2 via Link2 to confirm the successful reconfiguration. At this point, all links on the STA have completed the roaming handover, and the STA only maintains connection and communication with AP MLD2.

[0363] The difference between the embodiment shown in Figure 18 and the previous embodiments is that in this embodiment, the roaming is initiated by the UHR AP MLD based on the uplink signal quality.

[0364] In some embodiments, the difference from the foregoing exemplary embodiments lies in that, firstly, the UHR AP MLD UMAC determines the target link set (i.e., the set of links to be switched over) and sets the priority of the links in the target link set according to the link load of one or more neighboring APs of the original associated AP MLD. Then, the UHR AP MLD UMAC sends the target link set and link priorities to the non-AP STAMLD through the associated 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 over, based on the link priority and the link's probe response signal quality.

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

[0366] In step S1720, AP MLD1 decides to prepare the non-AP STA MLD for roaming based on uplink signal quality. AP MLD1 notifies the UHR AP MLD UMAC of this information via the backhaul link. Then, the UHR AP MLD UMAC provides a target link set and sets the priority of the links in the target link set based on the link load of AP MLD1's neighboring APs. The UHR AP MLD UMAC notifies AP MLD1 of the target link set and link priorities via the backhaul link.

[0367] In step S1730, AP MLD1 notifies the non-AP STA MLD of the target link set and the priority of the links in the target link set via a BTM request frame.

[0368] BTM request frames, along with downlink quality, can trigger a roaming process for non-AP STA MLD.

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

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

[0371] Figure 19 illustrates the BTM request frame format applicable to the embodiment described in Figure 18. For example, the BTM request frame includes a BSS transition candidate entry field, the length of which is variable in bytes.

[0372] The BSS transition candidate entry field can include zero or more neighbor report elements. Each neighbor report element includes a subelement field. The length of the subelement field can be variable, for example, 3 octets, 5 octets, or other lengths.

[0373] Sub-element fields may include BSS transition candidate preference sub-element fields and / or basic multi-link elements.

[0374] As shown in Figure 20, the BSS transition candidate preference sub-element includes a preference field, the length of which can be 1 Octet, 2 Octets, or other lengths.

[0375] In one embodiment, the value of the preference field is used to indicate the preferred order of the BSSs. For example, when the preference field is 255, it indicates the most preferred candidate, i.e., the most preferred AP MLD. When the preference field is 1, it indicates the least preferred candidate, i.e., the least preferred AP MLD.

[0376] Figure 21 illustrates the basic multi-link element structure of the BSS transition candidate entry field according to another embodiment of this application.

[0377] When an AP MLD intends to provide preferences to a reported AP MLD without a specific affiliated AP's recommendation, it can set all subfields in the Presence bitmap field to 0 and not include any Per-STA Profile subfields in the underlying multi-link element.

[0378] When an AP MLD intends to provide preferences to the reported AP MLD when it has only a subset of suggested subordinate APs, it will include a Link ID Info field in the common information of the underlying multilink element. The value of the Link ID Info field will be set to correspond to the corresponding field value of the AP reported in the neighbor reporting element.

[0379] The embodiment shown in Figure 22 differs from the aforementioned exemplary embodiment in that the roaming triggering method is different; that is, roaming is initiated by the AP MLD based on the uplink signal.

[0380] The embodiment shown in Figure 22 differs from the aforementioned exemplary embodiments in that the method for determining the target link (i.e., the link to be switched) is different. In this embodiment, the neighboring 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 confirms the target link based on a combination of link load status and uplink signal quality.

[0381] In the embodiment shown in Figure 22, this embodiment applies to the UHR AP logical entity architecture in the network access process step S2010. That is, the non-AP STA MLD and the AP MLD1 of the UHR AP MLD are associated through link Link0, and the non-AP STA MLD and the AP MLD1 of the UHR AP MLD are associated through 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 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. Upon 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 procedure for the non-AP STA MLD. The non-AP STA MLD sends probe request signals one by one to one or more adjacent AP MLDs (e.g., AP MLD2, AP MLD3, etc.) using all of its links, where these adjacent AP MLDs are all attached to the same UHR AP MLD UMAC.

[0384] Step 2040: The neighboring AP MLDs of the original AP MLD evaluate the signal quality of the probe request signals for each link. The neighboring AP MLDs report 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., Link0 between the non-AP STA MLD and AP MLD2).

[0385] In the embodiment shown in Figure 22, on the one hand, the quality of the probe signal is evaluated by the AP MLD instead of the non-AP STA AP, thereby reducing the burden on the non-AP STA MLD. On the other hand, this embodiment does not require 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, thereby reducing frame overhead and improving seamless roaming efficiency.

[0386] Figures 23 and 24 illustrate another example of the format of a UHR mobility field provided in an embodiment of this application.

[0387] As shown in the figure, the difference between this embodiment and those shown in Figures 3 and 4 is that in the ST capability field of the UHR mobility domain field, the seamless BSS transition mode field has a length of 2 bits, and the reserved field has a length of 6 bits. When the length of the seamless BSS transition mode field is 2 bits, the value of this field can have different meanings, as shown in Figure 24.

[0388] When the Seamless BSS Transition Mode value is 0, it indicates that the seamless roaming mode is not available for the MLD. When the Seamless BSS Transition Mode value is 1, it indicates that the seamless roaming mode is initiated by the non-AP STA MLD. When the Seamless BSS Transition Mode value is 2, it indicates that the seamless roaming mode is initiated by the APMLD, and the non-AP STA MLD determines the roaming target link (e.g., the roaming link to be switched). When the Seamless BSS Transition Mode value is 3, it indicates that the seamless roaming mode is initiated by the APMLD, and the UHR AP MLD UMAC determines the roaming target link.

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

[0390] This application provides a communication method in a wireless network, applied to a non-collocated control module of an ultra-reliable (UHR) non-collocated access point multi-link logical entity, comprising: the UHR control module instructing the transmission of a first frame to the non-AP multi-link logical entity, wherein the first frame includes first link identification information, the first link identification information indicating that the non-AP 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 multi-link logical entity of the first access point, and link information corresponding to the one or more links.

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

[0393] 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 receiving 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, which indicates the disconnection mode of the one or more links.

[0396] In one embodiment, the disconnection method is a delayed disconnection, and the first indication also indicates the delay duration of the delayed disconnection.

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

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

[0399] In response to the fulfillment of preset conditions, the UHR control module confirms that 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 conditions include: the UHR control module receives a fourth frame from the non-access point multi-link logical entity, the fourth frame including fourth link identification information corresponding to the first link identification information.

[0401] In one embodiment, the fourth frame further includes a fourth indication indicating whether the non-access point multilink logical entity has completed the operation requested by the first frame.

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

[0403] In one embodiment, after 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 cached downlink data used for the one or more links before the switch to be sent through at least one associated link other than the one or more links after the switch, 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 that cached downlink data for one or more links prior to the handover be transmitted via at least one associated link other than the one or more links after the handover, including: the UHR control module making the cached downlink data accessible to the at least one associated link other than the one or more links after the handover; and the UHR control module instructing the cached downlink data to be transmitted via the at least one associated link.

[0405] In one embodiment, making the cached downlink data accessible to the at least one associated link outside the one or more links after the handover includes: the UHR control module instructing the cached downlink data to be shared or copied to the at least one associated link outside the one or more links after the handover; 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 is 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 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 switched one or more links.

[0407] In one embodiment, after 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 data received after the one or more links have been switched, with the target address being the non-access point multi-link logical entity, to be sent to the non-access point multi-link logical entity through the switched one or more links.

[0408] In one embodiment, after 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 non-access point multi-link logical entity to send a fifth frame, wherein the fifth frame includes fifth link identification information, the fifth link identification information indicating 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 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 by the UHR access point multi-link logical entity to the first access point multi-link logical entity for use in the associated links of the first access point multi-link logical entity.

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

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

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

[0414] In one embodiment, the multicast key information includes group ephemeral keys (GTK), integrated group ephemeral keys (IGTK), and Beacon integrated group ephemeral keys (BIGTK).

[0415] In one embodiment, before the UHR control module receives the second frame from the non-access point multilink logical entity, the method further includes: the UHR control template sending a ninth frame to the non-access point multilink logical entity, wherein the ninth frame is configured to request the non-access point multilink 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 transmission of the first frame to the non-access point multilink logical entity, the method further includes: the UHR control module instructing the transmission of a sixth frame to the non-access point multilink logical entity, wherein the sixth frame includes a UHR mobility domain element, the UHR mobility domain element indicating the seamless transition capability of the UHR access point multilink logical entity.

[0418] In one embodiment, the method further includes: determining first key information for the UHR access point multi-link logical entity based on the 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 paired transition key (PTK) key information.

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

[0422] This application provides a communication method in a wireless local area network, applied to a non-access point multi-link logical entity, wherein the non-access point multi-link logical entity is associated with a non-collocated control module of an ultra-reliable (UHR) non-collocated access point multi-link logical entity, comprising: the non-access point multi-link logical entity sending a second frame to the UHR access point multi-link logical entity, the second frame including second link identification information, wherein the second link identification information indicates that the non-access point multi-link logical entity is to switch to one or more links associated with a first access point multi-link logical entity.

[0423] In one embodiment, the second link identification information includes logical entity identification information corresponding to the multi-link logical entity of the first access point, 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 the 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 receiving 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 sending a fourth frame to the UHR access point multi-link logical entity, the fourth frame including fourth link identification information corresponding to the first link identification information.

[0429] In one embodiment, the fourth frame further includes a fourth indication indicating whether the non-access point multilink logical entity has completed the operation requested by 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 its association with 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 handover 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 switched links.

[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 receiving 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 handover, wherein the cached downlink data is cached downlink data used for the one or more links before the handover.

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

[0434] In one embodiment, the non-access point multi-link logical entity determines one or more links of the first access point multi-link logical entity based on the plurality of eighth frames, including: the non-access point multi-link logical entity determining multiple signal qualities of multiple links corresponding to the plurality of eighth frames based on the plurality of eighth frames; and the non-access point multi-link logical entity determining 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 multilink logical entity receiving a multicast key signal from the UHR access point multilink logical entity, wherein the multicast key information is based on the corresponding lower media access control (LMAC) address of the access point multilink logical entity.

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

[0437] Exemplary embodiments of this application provide a method for constructing a communication frame, the frame being applied to wireless network communication of an ultra-high reliability (UHR) non-co-located access point multi-link logical entity, comprising: generating a first indication field, the first indication field indicating 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 multi-link logical entity of the first access point, 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 an 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 content of the first indication field depends on the value of the action field.

[0443] In one embodiment, the first indication also indicates the switching sequence of the one or more links.

[0444] Exemplary embodiments of this application provide 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, including: generating a UHR.

[0445] The mobility domain element field, wherein 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 identifier 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. Various embodiments of this application provide an access point apparatus, including: a transmitting module configured to transmit a first frame to a non-AP multi-link logical entity, wherein the first frame includes first link identification information, the first link identification information indicating that the non-AP multi-link logical entity is to be switched to one or more links associated with the first access point multi-link logical entity.

[0450] Figure 25 is a structural schematic diagram of an access point device 400 provided in an embodiment of this application. The access point device 400 can be an access point multi-link device 202 in a WLAN as shown in Figure 1. As shown in Figure 25, the access point device 400 includes...

[0451] The receiving module 410 is used 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] The sending module 420 is used 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, wherein 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, which is used to indicate the 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, which is used to indicate the link of the access point multilink logical entity to which the non-access point multilink logical entity requests to switch.

[0456] Optionally, the access point device 400 can 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] The first frame is sent to the non-access point multilink logical entity through the first access point multilink logical entity or the second access point multilink logical entity.

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

[0460] The second frame is received from the non-access point multilink logical entity through the first access point multilink logical entity or the second access point multilink logical entity.

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

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

[0463] In some embodiments, the first frame further includes a first indication, which indicates the switching mode of the target link.

[0464] In some embodiments, 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 the delay duration of the delayed switch.

[0465] In some embodiments, before receiving the second frame from the non-access point multilink 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. The third frame includes third link identification information, which is used to instruct the access point device 400 to suggest that the non-access point multi-link logical entity switch to a candidate access point multi-link logical entity and / or a candidate link.

[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 corresponding 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 indicates whether to recommend that the non-access point multi-link logical entity 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 the switch is recommended.

[0472] In some embodiments, the candidate access point multilink logical entity and / or the candidate link are determined by the UHR access point multilink logical entity based on the load status and / or signal quality of the links of the neighboring access point multilink logical entities of the second access point multilink logical entity.

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

[0474] The processing module is used to determine, under preset conditions, 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] A fourth frame is received from the non-access point multi-link logical entity, the fourth frame including fourth link identification information, the fourth link identification information corresponding to the first link identification information; or

[0477] A preset time elapsed after 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] Send a fifth frame to the non-access point multi-link logical entity, the fifth frame including fifth link identification information;

[0480] The fifth link identification information is used to indicate switching one or more remaining links of the non-access point multi-link logical entity to the associated first access point multi-link logical entity. 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] Send cached downlink data to the non-access point multi-link logical entity, wherein the cached downlink data is the downlink data already cached on the target link before the handover.

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

[0484] The cached downlink data is sent to the non-access point multilink logical entity through the second access point multilink logical entity.

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

[0486] The cached downlink data is sent from the second access point multi-link logical entity to the first access point multi-link logical entity.

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

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

[0489] The processing module is used to determine the unicast key information of the access point device 400 based on the upper media access control (UMAC) address of the access point device 400.

[0490] The processing module is also used 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 used to determine the multicast key information of one or more links of the first access point multilink logical entity based on one or more Lower Media Access Control (LMAC) addresses of the first access point multilink 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 multilink logical entity to the non-access point multilink logical entity.

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

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

[0497] In some embodiments, the sixth frame includes an ultra-high reliability UHR mobility domain element, which indicates 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 multilink logical entity through multiple access point multilink 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 multilink logic entity through the plurality of access point multilink logic entities, wherein the eighth frame is used to determine the first access point multilink logic entity.

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

[0501] Figure 26 is a structural schematic diagram of a non-access point device 500 provided in an embodiment of this application. The non-access point device 500 may be a terminal device 201 in a WLAN as shown in Figure 1. As shown in Figure 26, the non-access point device 500 includes:

[0502] The sending module 510 is used to send a second frame to the multi-link logical entity of the ultra-high reliability UHR access point, 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, which is used to indicate the 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, which 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 can 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 the identification information of the first access point multi-link logical entity and the link information of the target link.

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

[0512] In some embodiments, the first frame further includes a first indication, which indicates the switching mode of the target link.

[0513] In some embodiments, 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 the delay duration of the delayed switch.

[0514] In some embodiments, the access point multilink logical entity and link indicated by the second link identification information are determined by the non-access point device 500 based on the signal quality of the downlink signal of at least one access point multilink logical entity associated with the UHR access point multilink logical entity.

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

[0516] The receiving module 520 is further configured to receive a third frame from the UHR access point multilink logical entity, the third frame including third link identification information, the third link identification information being used to indicate to the UHR access point multilink logical entity the non-access point device 500 is advised to switch to a candidate access point multilink logical entity and / or candidate link.

[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 corresponding 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 indicates whether to recommend that the non-access point device 500 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 the switch is recommended.

[0522] In some embodiments, the access point multilink logical entity and link indicated by the second link identification information are determined by the non-access point device 500 based on the link quality of the candidate links of the candidate access point multilink 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] Receive a fifth frame from the multi-link logical entity of the UHR access point, the fifth frame including fifth link identification information;

[0525] The fifth link identification information is used to indicate switching one or more remaining links of the non-access point multi-link logic to the associated first access point multi-link logic entity. 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 device 500 and the second access point multi-link logic 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 cached downlink data from the multi-link logical entity of the UHR access point, wherein the cached downlink data is the downlink data already cached on the target link before the handover.

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

[0529] In some embodiments, the receiving module 520 is further configured 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 configured to: receive unicast key information of the UHR access point multilink logical entity from the UHR access point multilink logical entity, wherein the unicast key information is determined based on the upper media access control (UMAC) address of the UHR access point multilink logical entity.

[0531] In some embodiments, the receiving module 520 is further configured to: receive multicast key information of one or more links of the first access point multilink logical entity from the UHR access point multilink 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 multilink logical entity.

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

[0533] In some embodiments, the sixth frame includes an ultra-high reliability UHR mobility domain element, which indicates 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 multilink logical entities of the UHR access point multilink logical entity; and

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

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

[0537] This application provides an access point multi-link device, including: a processor and a transceiver;

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

[0539] For example, Figure 27 is a block diagram of an access point multilink device provided in an embodiment of this application. As shown in Figure 27, the access point multilink device 600 includes a processor 601 and a transceiver 602. The transceiver 602 is used to perform the transmit and receive operations of the access point multilink device in the above method embodiment under the control of the processor 601.

[0540] Optionally, the access point multilink device 600 also 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 used to control the execution of the program of the present application.

[0542] The communication bus 604 may include a path 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 capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or it may be an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, 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 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] The memory 603 stores program code for executing the scheme of this application, and its execution is controlled by the processor 601. The processor 601 executes 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 FIG17. The communication interface 605, using a transceiver 602, is used to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), WLAN, etc.

[0545] In a specific implementation, as one 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. Here, a processor may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0546] In practice, the access point multi-link device can be a router or a switch, etc.

[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 at the LMAC and PHY layers, and also independent at the UMAC layer. Alternatively, the multiple STAs included in the access point multi-link device are independent of each other at the LMAC and PHY layers, but share the UMAC layer. This application embodiment does not limit the internal structure of the access point multi-link device. For example, the UMAC layer or LMAC layer can be implemented by a processor in the chip system of the access point multi-link device, or it can be implemented by different processors in the chip system.

[0548] This application provides a non-access point multi-link device, including: a processor and a transceiver;

[0549] The processor is used to call a computer program to coordinate with the transceiver to implement the actions performed by the non-access point multilink device in the above method embodiments.

[0550] For example, Figure 28 is a block diagram of a non-access point multilink device provided in an embodiment of this application. As shown in Figure 28, the non-access point multilink device 700 includes a processor 701 and a transceiver 702. The transceiver 702 is used to perform the transmit and receive operations performed by the non-access point multilink device in the above method embodiment under the control of the processor 701.

[0551] Optionally, the access point multilink device 700 also includes a memory 703, a communication bus 704, and a communication interface 705.

[0552] The processor 701 can be a general-purpose CPU, an ASIC, or one or more integrated circuits used to control the execution of programs according to the present application.

[0553] The communication bus 704 may include a path 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, RAM or other type of dynamic storage device capable of storing information and instructions, or it may be an EEPROM, CD-ROM or other optical disc storage, optical disk storage (including compressed optical disks, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), 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 exist independently and be 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 stores program code for executing the scheme of this application, and its execution is controlled by the processor 701. The processor 701 executes the program code stored in the memory 703. The program code may include one or more software modules. These one or more software modules may be the software modules shown in FIG28.

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

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

[0558] In practice, non-access point multi-link devices can be wireless terminals such as mobile phones, computers, or smart wearable devices.

[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 at the LMAC layer and PHY layer, and also independent at the UMAC layer. Alternatively, the multiple non-AP STAs included in the non-access point multi-link device are independent of each other at the LMAC layer and PHY layer, but share the UMAC layer. This application embodiment does 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, or they can be implemented by different processors in the chip system.

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

[0561] This application also provides a computer-readable storage medium storing computer-executable instructions for causing a computer to execute a terminal roaming guidance method described in the above embodiments.

[0562] This application also provides a computer program product, which, when invoked by a computer, causes the computer to execute a terminal roaming guidance method described in the above embodiments.

[0563] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0564] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0565] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0566] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

Claims

1. A communication method in a wireless local area network, comprising: The 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; and The UHR access point multilink logical entity sends a first frame to the non-access point multilink 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 of claim 1, wherein, The UHR access point multilink logical entity sending a first frame to the non-access point multilink logical entity includes: the UHR access point multilink logical entity sending a first frame to the non-access point multilink logical entity through the first access point multilink logical entity or the second access point multilink logical entity.

3. The method of claim 1 or 2, wherein, The first frame includes first link identification information, which is used to indicate the 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, which is used to indicate the link of the access point multilink logical entity to which the non-access point multilink logical entity requests to switch.

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

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

6. The method of 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 the delay duration of the delayed switch.

7. The method of any one of claims 1-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 of any one of claims 1-7, wherein, Before the ultra-high reliability UHR access point multilink logical entity receives the second frame from the non-access point multilink logical entity, the method further includes: The UHR access point multilink logical entity sends a third frame to the non-access point multilink logical entity. The third frame includes third link identification information, which is used to indicate to the UHR access point multilink logical entity to recommend the non-access point multilink logical entity to switch to a candidate access point multilink logical entity and / or a candidate link.

9. The method of 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 corresponding 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 that the non-access point multi-link logical entity 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 the switch is recommended.

11. The method of any one of claims 8-10, wherein, The candidate access point multilink logical entity and / or the candidate link are determined by the UHR access point multilink logical entity based on the load status and / or signal quality of the links of the neighboring access point multilink logical entities of the second access point multilink logical entity.

12. The method of any one of claims 1-11, wherein, The method further includes: Under certain preset conditions, 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 conditions include 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, which corresponds to the first link identification information in the first frame; or The UHR access point multi-link logical entity sent the first frame after a preset time.

13. The method of any one of claims 1-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 switching one or more remaining links of the non-access point multi-link logical entity to the associated first access point multi-link logical entity. 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.

14. The method of any one of claims 1-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 cached downlink data to the non-access point multi-link logical entity, wherein the cached downlink data is the downlink data already cached on the target link before the handover.

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

16. The method of claim 14 or 15, wherein, The UHR access point multi-link logical entity sends 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 cached downlink data to the non-access point multi-link logical entity.

17. The method of any one of claims 1-16, wherein, The method further includes: The UHR access point multi-link logical entity determines the unicast key information of the UHR access point multi-link logical entity based on the upper media access control (UMAC) address of the UHR access point multi-link logical entity.

18. The method of claim 17, wherein, The method further includes 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 multilink logical entity sends its unicast key information to the non-access point multilink logical entity.

19. The method of any one of claims 1-18, wherein, The method further includes: The UHR access point multilink logical entity determines the multicast key information of one or more links of the first access point multilink logical entity based on one or more Lower Media Access Control (LMAC) addresses of the first access point multilink logical entity.

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

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

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

23. The method of any one of claims 1-22, wherein, The method further includes: The multiple 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 UHR access point multilink logical entity sends an eighth frame in response to the seventh frame to the non-access point multilink logical entity, the eighth frame being used to identify the first access point multilink logical entity.

24. A method of communication 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 of claim 24, wherein the non-access point multi-link logical entity receives a 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 of claim 24 or 25, wherein, The first frame includes first link identification information, which is used to indicate the 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, which is used to indicate the link of the access point multilink logical entity to which the non-access point multilink logical entity requests to switch.

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

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

29. The method of 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 the delay duration of the delayed switch.

30. The method of any one of claims 24-29, wherein, The non-access point multi-link logical entity sends a second frame to the 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 link indicated by the second link identification information are determined by the non-access point multi-link logical entity based on 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 of any one of claims 24-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 includes third link identification information, which is used to indicate to the UHR access point multi-link logical entity the non-access point multi-link logical entity should switch to a candidate access point multi-link logical entity and / or a candidate link.

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 of claim 32 or 33, wherein, The access point multi-link logical entity and link indicated by the second link identification information in the second frame are determined by the non-access point multi-link logical entity based on 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 of any one of claims 24-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, the fifth frame including fifth link identification information; The fifth link identification information is used to indicate switching one or more remaining links of the non-access point multi-link logical entity to the associated first access point multi-link logical entity. 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.

36. The method of any one of claims 24-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 cached downlink data from the UHR access point multi-link logical entity, wherein the cached downlink data is downlink data already cached on the target link before the handover.

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

38. The method of claim 36 or 37, the non-access point multi-link logical entity receiving buffered downlink data from the UHR access point multi-link logical entity, comprising: The non-access point multi-link logical entity receives 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 from the second access point multi-link logical entity to the first access point multi-link logical entity.

39. The method of any one of claims 24-38, wherein, The method further includes: The non-access point multi-link logical entity receives unicast key information from the UHR access point multi-link logical entity, wherein the unicast key information is determined based on the upper media access control (UMAC) address of the UHR access point multi-link logical entity.

40. The method of any one of claims 24-39, wherein, The method further includes: The non-access point multilink logical entity receives multicast key information of one or more links of the first access point multilink logical entity from the UHR access point multilink logical entity, wherein the multicast key information of the one or more links is determined according to one or more Lower Media Access Control (LMAC) addresses of the first access point multilink logical entity.

41. The method of any one of claims 24-40, wherein, Before 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 receives a sixth frame from the UHR access point multi-link logical entity, the sixth frame being used to indicate that the UHR access point multi-link logical entity has seamless transition capability.

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

43. The method of any one of claims 24-42, wherein, The method further includes: The non-access point multi-link logical entity sends a seventh frame to multiple 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 the eighth frame sent by multiple access point multi-link logical entities of the UHR access point multi-link logical entity, and the eighth frame is used to identify the first access point multi-link logical entity.

44. An access point apparatus, comprising: include: The receiving module is used 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; The sending module is used 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, wherein the second access point multi-link logical entity is associated with the non-access point multi-link logical entity.

45. A non-access point apparatus, comprising: include: The sending module is used to send a second frame to the multi-link logical entity of the ultra-high reliability UHR access point, wherein the second frame is used to initiate a roaming request; The receiving module is configured to receive a first frame from the multi-link logical entity of the UHR access point, 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, wherein 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 for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the method as described in any one of claims 1 to 23.

47. A non-access point multi-link device, wherein, include: A processor and a memory for storing computer programs, the processor for calling and running the computer programs stored in the memory to perform the method as described in any one of claims 24 to 43.

48. A chip, wherein, include: A processor for retrieving and running a computer program from memory, causing a device having the chip mounted to perform the method as claimed in any one of claims 1 to 23, or the method as claimed in any one of claims 24 to 43.

49. A computer readable storage medium, wherein, Used to store a computer program that causes a computer to perform the method as claimed in any one of claims 1 to 23, or the method as claimed in any one of claims 24 to 43.

Images