Communication methods, devices, equipment, and systems in wireless local area networks

UHR multilink logical entities with enhanced communication frames address handover delays and data interruptions in wireless networks, ensuring seamless and reliable data transmission during access point switching.

JP2026538982APending Publication Date: 2026-11-19RUIJIE NETWORKS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
JP2026522427
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-11-22
Filing Date
2024-11-04
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing wireless local area network technologies face significant handover delays and data transmission interruptions during the process of mobile devices switching between access points, leading to reduced data reliability and user experience.

Method used

The implementation of ultra-high reliability (UHR) multilink logical entities with enhanced communication frames and protocols, including UHR mobility domain elements and seamless transition capabilities, to facilitate rapid and uninterrupted roaming between access points.

Benefits of technology

This approach reduces switching delays and ensures continuous data transmission during roaming, enhancing the reliability and efficiency of wireless network connections.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026538982000001_ABST
    Figure 2026538982000001_ABST
Patent Text Reader

Abstract

A communication method, apparatus, device, and system in a wireless local area network, the method comprising: a super-high reliability UHR access point multilink logical entity receiving a second frame from a non-access point multilink logical entity for instructing a roaming request; and the UHR access point multilink logical entity transmitting a first frame to the non-access point multilink logical entity, the first frame being used to instruct a roaming reconfiguration; the UHR access point multilink logical entity comprising a first access point multilink logical entity and a second access point multilink logical entity, the second access point multilink logical entity being associated with the non-access point multilink logical entity.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to Chinese Patent Application No. 202311457656.1 filed with the China National Intellectual Property Administration on November 3, 2023 and entitled "Communication Method, Apparatus, Device and System in Wireless Local Area Network", Chinese Patent Application No. 202311479127.1 filed with the China National Intellectual Property Administration on November 8, 2023 and entitled "Communication Method, Apparatus, Device and System in Wireless Local Area Network", and Chinese Patent Application No. 202311572418.5 filed with the China National Intellectual Property Administration on November 22, 2023 and entitled "Communication Method, Apparatus, Device and System in Wireless Local Area Network", the entire contents of all of which are incorporated into this application by reference.

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

[0003] In the related art, when a mobile device moves from the coverage area of one Access Point (AP) to the coverage area of another AP, it is necessary to perform handover of the connection between the mobile device and different APs. However, since there are a relatively large number of signaling interactions in the handover process, the handover delay is relatively large, and interruption of data transmission may occur. Therefore, how to realize seamless roaming to ensure the continuity of data transmission is an urgent problem to be solved. SUMMARY OF THE INVENTION

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

[0005] The embodiments of this application provide a communication method in a wireless local area network, and this communication method is A highly reliable UHR access point multilink logical entity receives a second frame from a non-access point multilink logical entity to initiate a roaming request. The UHR access point multilink logical entity transmits a first frame to the non-access point multilink logical entity to instruct it to perform roaming reconfiguration. The UHR access point multilink logical entity includes a first access point multilink logical entity and a second access point multilink logical entity, the second access point multilink logical entity being associated with the non-access point multilink logical entity.

[0006] The embodiments of this application provide a communication method in a wireless local area network, and this communication method is A non-access point multilink logical entity sends a second frame to a highly reliable UHR access point multilink logical entity to initiate a roaming request. The non-access point multilink logical entity includes receiving a first frame from the UHR access point multilink logical entity for instructing roaming reconfiguration, The UHR access point multilink logical entity includes a first access point multilink logical entity and a second access point multilink logical entity, the second access point multilink logical entity being associated with the non-access point multilink logical entity.

[0007] Each exemplary embodiment of this application provides a method for constructing a communication frame, the frame being applied to wireless network communication of ultra-high reliability (UHR) access point multilink logical entities, the method comprising generating a first instruction field indicating that a non-access point multilink logical entity should be switched to one or more links associated with a first access point multilink logical entity belonging to the UHR access point multilink logical entity.

[0008] In some embodiments, the first instruction field is used to indicate logical entity identifier information corresponding to the first access point multilink logical entity, and link information corresponding to one or more links.

[0009] In some embodiments, the link information includes link count information and information on one or more link identifiers.

[0010] In some embodiments, the first instruction field further includes an STA control field.

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

[0012] In some embodiments, the method further includes generating an action field, the field content of which is included in the first instruction field depends on the value of the action field.

[0013] In some embodiments, the first instruction further indicates the switching sequence of the one or more links.

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

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

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

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

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

[0019] Each embodiment of the present application provides an access point device and includes a transmitting module configured to transmit a first frame to a non-AP multi-link logical entity, the first frame including first link identifier information indicating that the non-AP multi-link logical entity should be switched to a target link associated with the first access point multi-link logical entity.

[0020] Each embodiment of this application provides an access point device, and this access point device is a receiving module configured to receive a second frame for initiating a roaming request from a non-access point multi-link logical entity, and a transmitting module configured to transmit a first frame for instructing roaming reconfiguration to the non-access point multi-link logical entity The access point apparatus 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.

[0021] Each embodiment of the present application provides a non-access point apparatus, and the non-access point apparatus a transmitting module configured to transmit a second frame for initiating a roaming request to an ultra-high reliability UHR access point multi-link logical entity, a receiving module configured to receive a first frame for instructing roaming reconfiguration from the UHR access point multi-link logical entity, 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 apparatus.

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

[0023] Each embodiment of the present application provides a non-access point multi-link device, which includes a processor and a transceiver, wherein the processor is configured to invoke a computer program and cooperate with the transceiver to implement the communication method described in each of the above embodiments.

[0024] Each embodiment of the present application provides a communication system in a wireless local area network, and the communication system includes the access point apparatus or the access point multi-link device described in each of the above embodiments, and the non-access point apparatus or the non-access point multi-link device described in each of the above embodiments.

[0025] Each exemplary embodiment of the present application provides a computer-readable storage medium, wherein instructions are stored on the computer-readable storage medium, and when the instructions are executed by a processor, the processor performs the communication method in a wireless local area network according to each of the above embodiments.

[0026] Each exemplary embodiment of the present application provides a computer program product, which includes computer program instructions that cause a computer to execute the communication method in a wireless local area network according to each of the above embodiments.

[0027] To more clearly describe the technical solutions of the present application, the drawings required for describing the embodiments of the present application are briefly introduced below in conjunction with the accompanying drawings. Obviously, the drawings in the following description are only some embodiments of the present application, and those skilled in the art can also obtain drawings of other embodiments based on these drawings without creative efforts. [Brief Description of the Drawings]

[0028] [Figure 1] FIG. 1 shows a network architecture diagram of an application environment of a communication method in a wireless local area network according to an embodiment of the present application. [Figure 2]Figure 2 shows a schematic diagram illustrating the application scenario of the communication method in a wireless local area network according to the embodiment of this application. [Figure 3] Figure 3 shows a schematic diagram of the structure of a mobility domain element field according to an embodiment of this application. [Figure 4] Figure 4 shows a schematic diagram of the structure of the seamless transition capability field of the mobility domain element field according to an embodiment of this application. [Figure 5] Figure 5 shows an extended schematic diagram of the frame structure of the mobility domain element field according to an embodiment of this application. [Figure 6] Figure 6 shows a schematic diagram of the structure of the Basic Service Set (BSS), Transition Management (BSS Transmit Management, BTM), and Roaming frame according to an embodiment of this application. [Figure 7] Figure 7 shows a schematic diagram illustrating the correspondence between the values ​​of the Action subfield of the BTM roaming frame and their functions according to an embodiment of this application. [Figure 8] Figure 8 shows a schematic diagram of the structure of the Common Info subfield of a BTM roaming frame according to an embodiment of this application. [Figure 9] Figure 9 shows a flowchart of the network access procedure for a communication method according to an embodiment of this application. [Figure 10] Figure 10 shows a flowchart of the network access procedure for a communication method according to an embodiment of this application. [Figure 11] Figure 11 shows a schematic diagram of the structure of the KDE field of the multicast key information in the communication method according to the embodiment of this application. [Figure 12] Figure 12 shows a schematic diagram of the structure of the FTE field of the Fast Transition protocol for multicast key information in the communication method according to an embodiment of this application. [Figure 13]Figure 13 shows a schematic diagram of a communication method in a wireless local area network according to an embodiment of this application. [Figure 14] Figure 14 shows a schematic diagram of a communication method in another wireless local area network according to an embodiment of this application. [Figure 15] Figure 15 shows a flowchart of a portion of the seamless roaming flow in the communication method according to an embodiment of this application. [Figure 16] Figure 16 shows the remaining flowchart of the seamless roaming flow in the communication method shown in Figure 15. [Figure 17] Figure 17 shows a flowchart of the seamless roaming flow of a communication method according to another embodiment of this application. [Figure 18] Figure 18 shows a flowchart of the seamless roaming flow of a communication method according to yet another embodiment of this application. [Figure 19] Figure 19 shows the BTM request frame format for a seamless roaming flow in another embodiment of this application and the structure of the Neighbor Report element in its BSS transition candidate entry field. [Figure 20] Figure 20 shows the format of the BSS transition candidate preference sub-element of the BSS transition candidate entry field in yet another embodiment of this application. [Figure 21] Figure 21 shows the basic multi-link element structure of a BSS transition candidate entry field in yet another embodiment of this application. [Figure 22] Figure 22 shows a flowchart of the seamless roaming flow of a communication method in yet another embodiment of this application. [Figure 23] Figure 23 shows the ST capability field format of a UHR mobility domain element in a network access procedure of yet another embodiment of the present application. [Figure 24]Figure 24 shows the values ​​of the Seamless BSS Transition Mode of the ST capability field and their corresponding meanings for yet another embodiment of this application. [Figure 25] Figure 25 shows a schematic diagram of the internal structure of an access point device according to an embodiment of this application. [Figure 26] Figure 26 shows a schematic diagram of the internal structure of a non-access point device according to an embodiment of this application. [Figure 27] Figure 27 shows a block diagram of an access point multilink device according to an embodiment of this application. [Figure 28] Figure 28 shows a block diagram of a non-access point multilink device according to an embodiment of this application. [Modes for carrying out the invention]

[0029] While various forms of embodiment are possible with respect to this application, the drawings that are intended to be specifically described herein illustrate embodiments of this application, including preferred embodiments. It should be understood that the information disclosed herein should be considered an interpretation of the principles of this application and is not intended to limit the broader aspects of this application to one or more of the embodiments shown or disclosed.

[0030] To further clarify the purpose, technical proposal, and merits of this application, the technical proposal in the embodiments of this application will be described clearly and completely below with reference to the drawings of the embodiments of this application. It is obvious that the embodiments described are only a selection of embodiments of this application, not all of them. All other embodiments derived from the embodiments of this application, without the creative effort of a person skilled in the art, are all within the scope of protection of this application. Where there is no conflict, the embodiments and features of the embodiments of this application can be combined arbitrarily, and any technical proposal formed by such combinations remains within the scope of protection of this application. While the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order.

[0031] The terms “first” and “second” in the specification, claims, and drawings of this application are not intended to describe a specific order, but rather to distinguish different subjects. The term “including” and any variations thereof are intended to cover non-exclusive protection. For example, a process, method, system, product, or apparatus comprising a series of steps or units is not limited to the listed steps or units, but may optionally further include steps or units not listed, or may optionally further include other steps or units specific to those processes, methods, systems, products, or apparatus.

[0032] When using “includes,” “equipped with,” or “incorporated” as described in this application, additional components may be added unless explicit limiting terms such as “only” or “consisting of” are used. Unless otherwise stated, singular terms may include plural forms and should not be understood as being limited to one.

[0033] Unless otherwise defined in the context, the term “logical entity” in this application may refer to a functional module implemented by software, a hardware unit having a specific function implemented by hardware, or a combination of a functional module in software and a hardware unit in hardware.

[0034] Figure 1 is a schematic diagram of one application scenario to which an embodiment of the present application is applied. As shown in Figure 1, the application scenario includes a station (STA) 201 and an access point (AP) 202, where AP 202 includes three APs. It should be noted that the number of APs involved in AP 202 is not limited, and Figure 1 uses only three APs as an example. The APs shown in Figure 1 may be multilink access logical entities, such as non-colocated multilink access logical entities, and all of them belong to the ultra-high reliability (UHR) multilink logical entities.

[0035] AP 202 forms an AP wireless network environment 203 with three APs, and when STA 201 enters this AP wireless network environment 203, seamless roaming can be performed.

[0036] Station 201 may be an electronic device such as a mobile phone, smart wearable device, tablet PC, or laptop computer. Furthermore, Station 201 may have related clients installed, which may be software such as an application program (Application, APP), browser, short video software, web page, or applet.

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

[0038] 802.11be networks, also known as Extremely High Throughput (EHT) networks, achieve extremely high throughput through a set of system characteristics and various mechanisms that enhance their functionality. In 802.11be networks, wireless devices can support multi-link communication. Support for multi-link communication by a wireless device may mean 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 generally called multi-link devices (MLDs). An MLD has one or more STAs.

[0039] Multilink devices in a Wireless Local Area Network (WLAN) are divided into two types: AP multilink devices and non-AP multilink devices. In AP MLD, STA refers to AP STA, and in Non-AP MLD, STA refers to Non-AP STA. Generally, for abbreviation purposes, AP STA is called AP and non-AP STA is called STA.

[0040] One or more links can be established between a non-access point multilink device and an access point multilink device, i.e., linked links can be formed. Each linked link connects one non-AP STA in the non-access point multilink device to one AP in the access point multilink device.

[0041] In one exemplary embodiment, an AP MLD is an EHT AP MLD, and each EHT AP MLD has a corresponding EHT Up Media Access Control (UMAC). If all APs belonging to an AP MLD collate with each other, the AP MLD is a collocated AP MLD; conversely, the AP MLD is a non-collocated AP MLD.

[0042] Figure 2 shows an exemplary architecture diagram of an Ultra High Reliability (UHR) AP MLD. In this example, the UHR AP MLD includes N EHT AP MLDs and a UHR AP MLD UMAC that is independently communicable to 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), and each of the N APs may be associated with multiple links (link 0 to link N, as shown in the figure). Each of the N APs is communicatively connected to N LMACs and converges to a TID (Traffic Identifier)-to-Link mapping / link merging module. The TID-to-Link mapping / link merging module communicates with the UMAC backhaul of the UHR AP MLD. The UHR AP MLD UMAC controls and manages the link communication between EHT AP MLD 1 to EHT AP MLD N.

[0043] In conventional Wi-Fi technology, when a mobile device (i.e., STA) moves from the coverage area of ​​one access point (AP) to the coverage area of ​​another AP, the roaming function ensures the mobile device's internet connectivity performance by switching between the mobile device and the different AP. However, when using conventional roaming, when a mobile device moves from the coverage area of ​​one AP to the coverage area of ​​another AP, the user must manually disconnect the current connection, re-search for available Wi-Fi networks, and manually select and connect to a new AP. Such a roaming method can lead to connection interruptions, reduced data transmission reliability, and a diminished user experience.

[0044] Therefore, Fast Transition (FT) roaming technology has been introduced to conventional Wi-Fi technology. FT roaming technology is a high-speed Wi-Fi roaming technology, also known as 802.11r. It allows a mobile device to move from the coverage area of ​​one AP to the coverage area of ​​another AP, embedding the four key handshake flows with the target AP into a re-association flow, thereby achieving the goal of rapidly switching APs.

[0045] However, whether it's regular roaming or FT roaming, the following problems exist when switching access points: 1. Mobile devices incur relatively high frame overhead when switching APs, and also require link authentication, i.e., 802.1X Extensible Authentication Protocol (EAP) authentication and a roaming switchover flow involving four handshakes, which causes relatively large latency.

[0046] 2. In mobile device roaming flows, user data transmission is interrupted, data continuity is not guaranteed, the reliability of data transmission decreases, and the user experience deteriorates.

[0047] The communication method according to the embodiment of this application enables seamless roaming of mobile devices using UHR multilink logical entities, reduces switching delays during roaming, and guarantees the continuity of data transmission.

[0048] Each exemplary embodiment of this application provides a communication method applicable to UHR multilink logical entities, enabling high-speed roaming while simultaneously ensuring continuity of data transmission.

[0049] Therefore, the embodiments of this application introduce seamless roaming frames and add fields to 802.11be frames. These introduced frames and fields will be explained below, linking Figures 3 through 12.

[0050] It should be noted that the naming of frames, fields, or elements in the embodiments of this application is merely illustrative and may be replaced with other names, and this application is not limited thereto.

[0051] Figure 3 shows a schematic diagram of the structure of a UHR mobility domain element field according to an embodiment of this application.

[0052] The UHR mobility domain element field is used to declare seamless transition capability or seamless roaming capability. For example, the UHR mobility domain element field includes a seamless transition capability field for declaring wireless roaming capability or wireless transition capability.

[0053] Selectively, the length of the seamless transition capability field is 1 octet, or longer, for example, 2 octets, 3 octets, etc.

[0054] Selectively, a UHR mobility domain element further includes an element identifier (Element ID) and at least one of either a length or a mobility domain identifier (Mobility Domain ID, MDID), where the MDID field is the identifier of the naming UHR roaming mobility domain.

[0055] The UHR Mobility Domain element field is added to Beacon Frames, Probe Response Frames, Association Request Frames, Association Response Frames, and Authentication Frames from a UHR AP MLD (or AP) to declare the seamless transition capability of the UHR AP MLD (for example, to non-access point multilink equipment). The extended structure of these frames is described further below.

[0056] To make it clear, the UHR mobility domain element field may be appended to a frame from a 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, it is used to indicate the seamless transition capability of the non-AP STA MLD (or non-AP STA).

[0057] In some embodiments, the UHR mobility domain element field may be added to these frames as a new field.

[0058] Alternatively, the UHR Mobility Domain Element field may multiplex or extend the conventional fields in these frames described above. For example, the UHR Mobility Domain Element field can extend and multiplex the FT Capability and Policy subfield in the Mobility Domain Information element (MDIE) field in the 802.11r protocol.

[0059] Figure 4 shows a schematic diagram of the structure of the seamless transition capability (ST Capability) field of the UHR mobility domain element field according to an embodiment of this application. The seamless transition capability field is used to declare the seamless transition capability of an AP or non-AP STA that can perform seamless Basic Service Set (BSS) transitions.

[0060] The seamless transition capability field may include a Seamless BSS Transition Status subfield. Selectively, one bit is used to indicate the seamless BSS transition status.

[0061] In some embodiments, if the MLD has seamless transition capability, the seamless base service set transition state subfield may be set to 1; otherwise, it may be set to 0. Of course, more bits may be used to indicate the seamless base service set transition state, and the embodiments of this application are not limited to this.

[0062] Selectively, the seamless transition capability field may further include a Reserved field. The length of the Reserved field may be 7 bits or any other number of bits, and the embodiments of this application are not particularly limited thereto.

[0063] Figure 5 shows a schematic diagram of the frame structure extension field of the UHR mobility domain element field according to an embodiment of this application.

[0064] As mentioned above, the UHR Mobility Domain Element field can be added to Beacon Frames, Probe Response Frames, Association Request Frames, Association Response Frames, and Authentication Frames from a UHR AP MLD (or AP) to declare the seamless transition capability of the UHR AP MLD (for example, to a non-access point multilink device). In the embodiment shown in Figure 5, if the value of the "dot11SeamlessBSSTransition Activated" field is true, the UHR Mobility Domain Element field may also be present at the end of the above frames, i.e., the UHR Mobility Domain Element field is added to the reserved fields of these frames or extended to the end of these frames.

[0065] Alternatively, the UHR mobility domain element field may be added to other positions in the frame described above, and the embodiments of this application are not particularly limited thereto.

[0066] Alternatively, the presence or absence of a UHR mobility domain element field may be determined based on a field other than the "dot11SeamlessBSSTransition Activated" field, and the embodiments of this application are not particularly limited to this.

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

[0068] To achieve seamless roaming in a UHR AP MLD environment, a BTM roaming frame is introduced for roaming message exchange between non-access point multilink logical entities (e.g., non-AP STA MLD) and UHR AP MLD. The roaming message includes a roaming request (e.g., sent from non-AP STA MLD to UHR AP MLD), a roaming link switch instruction (e.g., sent from UHR AP MLD to non-AP STA MLD), and a roaming link switch confirmation (e.g., sent from non-AP STA MLD to UHR AP MLD).

[0069] As shown in Figure 6, the BTM roaming frame includes an Action field. Selectively, the byte length of the Action field is 1 Octet or more bytes, such as 2 Octets, 5 Octets, or 10 Octets.

[0070] Selectively, as shown in Figure 6, the BTM roaming frame may further include a Category field.

[0071] The Category field is already defined in the older 802.11 standard. For example, setting it to 10 indicates that it is affected by Wireless Network Management (WNM).

[0072] Selectively, as shown in Figure 6, the BTM roaming frame may further include a Dialog Token field, which is a non-zero value taken by the STA sending the BTM roaming frame, thereby identifying that the frame type is a request frame type or a response frame type.

[0073] Figure 7 shows a schematic diagram illustrating the correspondence between the value of the Action field in a BTM roaming frame and its function according to an embodiment of this application. Different values ​​in the Action field result in different types of BTM roaming frames.

[0074] For example, if the value of the Action field is 28, the BTM roaming frame is of the Roaming Request frame type. If the value of the Action field is 29, the BTM roaming frame is of the Roaming Reconfigure frame type. If the value of the Action field is 30, the BTM roaming frame is of the Roaming Confirm frame type.

[0075] As shown in Figure 6, the BTM roaming frame further includes a common information field.

[0076] Figure 8 shows a schematic diagram of the structure of the Common Info field in a BTM roaming frame according to an embodiment of this application. If the value in the action field is different, that is, if the type of BTM roaming frame is different (which may also indicate that the sending and receiving ends of the frame are different), the roaming information carried in the corresponding Common Info field will also be different.

[0077] The common information fields in a BTM roaming frame include at least an MLD AP identifier (MLD AP ID) field and a Links Info field.

[0078] Selectively, the common information field may further include a length field, which is used to indicate the length of fields other than the length field in the common information field.

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

[0080] If the BTM roaming frame is a BTM roaming confirmation frame, the common information field may also include a status code field.

[0081] Selectively, in the embodiment shown in Figure 8, the common information fields of the BTM roaming frame may include a Length field, an MLD AP ID field, a Links Info field, a Status Code field, and an STA Control field.

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

[0083] The MLD AP ID field indicates the identifier of the requested AP MLD, i.e., the identifier of the MLD AP requested as the switching target. The length of the MLD AP identifier field is 1 octet, and in other embodiments, the length of the MLD AP identifier field may be longer, for example, 2 octets, 5 octets, or 10 octets, and this application is not particularly limited thereto.

[0084] The link information field indicates the link information of the target link, i.e., the link information of the target link that is expected to be detached from the original MLD AP and associated with a new MLD AP. The length of the link information field is variable and depends on the number of target links in the link information field. Therefore, the length of the common information field is also variable.

[0085] Selectively, as shown in Figure 8, the above link information field may include a Link Num field and one or more Link ID Info fields. The Link Num field indicates the number of links to request a switch (or are called to request a deactivation), or the number of target links. The Link ID Info field indicates the link identifier of the link to request a switch, or the link identifier of the target link.

[0086] The status code field is already defined in the conventional 802.11 standard and will not be described further in this application. The length of the status code field may be 1 octet, and in other embodiments, the length of the status code field may be longer, for example, 2 octets, 5 octets, or 10 octets, and this application is not particularly limited thereto.

[0087] Selectively, as shown in Figure 8, the STA control fields described above may include a Link Del Mode field. The length of the Link Del Mode field may be 8 bits, or in another embodiment, the length of the Link Del Mode field may be other values, such as 4 bits, 12 bits, or 16 bits.

[0088] The link deletion mode field may also indicate the method of deleting the link, or the method of unlinking the link, or the method of switching the link, such as immediate unlinking (or immediate deletion, immediate switching) or delayed unlinking (or delayed deletion, delayed switching).

[0089] For example, if the link deletion mode field is 1 bit, setting the link deletion mode field to 0 allows the requested link to be immediately released (or deleted, switched). If the link deletion mode field is set to 1, the system may wait for a specified time period before releasing (or deleting, switching) the requested link.

[0090] Alternatively, if the link removal field is 2 bits, setting the link removal mode field to 0 may immediately disconnect the link; setting the link removal mode field to 1, 2, or 3 may wait for the corresponding first, second, or third preset time before disconnecting the link.

[0091] Selectively, the STA control field may further include a Link Del Count field, used to indicate the delay time for de-delay release. The Link Del Count field may indicate waiting a specified number of Time Units (TUs) after receiving the corresponding frame before de-deleting (or deleting, switching) the requested link. The Link Del Count field may indicate other physical quantities to control the link wait time for de-deleting (or deleting, switching) requests. The length of the Link Del Count field may be 8 bits, and in another embodiment, the length of the Link Del Count field may be other values, such as 4 bits, 12 bits, or 16 bits.

[0092] Figure 9 shows a schematic diagram of the network access procedure of the communication method according to the embodiment of this application.

[0093] As shown in Figure 9, in the network access procedure, after completing the probe, multilink authentication, and association, non-access point multilink devices (non-AP STA MLDs) and / or ultra-high reliability access point multilink devices (UHR AP MLDs) can compute and generate a unicast key (e.g., a pairwise transition key (PTK)) using an EAPOL key frame. Since the PTK is computed based on the UMAC address of the UHR AP MLD and can be stored in the UMAC of the UHR AP MLD, the PTK can be shared by all AP MLDs belonging to the UHR AP MLD, and for each AP MLD, the PTK is the same.

[0094] Specifically, the PTK may be generated during the network access procedure generation phase and then shared among multiple AP MLDs of the UHR AP MLD. Alternatively, the PTK may be generated during the network access procedure generation phase, first stored in the UHR AP MLD UMAC, and then shared in the seamless roaming flow to AP MLDs designated and controlled by the UHR AP MLD UMAC.

[0095] Multicast keys (for example, Group Temporary Key (GTK), Integrity Group Temporary Key (IGTK), Beacon Integrity Group Temporary Key (BIGTK)) may be calculated based on the EHT AP MLD LMAC address corresponding to each link of the AP MLD belonging to the UHR AP MLD (i.e., referred to as the LMAC address corresponding to the UHR AP MLD, or the LMAC address of the corresponding EHT AP MLD).

[0096] The UHR AP MLD computes and sends these multicast keys to the corresponding non-AP STA MLD, or instructs it to do so, and the non-AP STA MLD stores these multicast keys. These multicast keys may be computed by the UHR AP MLD UMAC and sent by the UHR AP MLD UMAC, or computed 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 first backhauled to the UHR AP MLD UMAC and then sent by the UHR AP MLD UMAC to the corresponding non-AP STA MLD.

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

[0098] Additionally or alternatively, when a non-AP STA MLD is before or during a seamless roaming flow, the UHR AP MLD sends or instructs the non-AP STA MLD to send a multicast key.

[0099] In some embodiments, selectively, identifier information for the corresponding AP MLD for the corresponding link may be added to this multicast key information to avoid confusion of the same frequency link for different AP MLDs in a non-collocated environment, which will be described in detail in later embodiments.

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

[0101] The operating mechanism in the seamless roaming process between unicast and multicast keys will be described in the following specific embodiments.

[0102] Figure 10 shows a flowchart of the network access procedure for a communication method according to yet another embodiment of this application.

[0103] In step S1500, after power-up, the Non-AP STA first enters passive scan mode and monitors beacons on supported links. Then, the Non-AP STA enters active scan mode and actively sends normal probe request frames on each link. The UHR AP MLD receives the normal probe request frames and feeds back the normal probe response by controlling the EHT AP MLD LMAC. The send and receive addresses of the normal probe frames are set to the Link binding addresses to avoid confusion with other links at the same frequency point. Therefore, the TA of the probe response frame is entered as the Link MAC Address of the EHT AP MLD LMAC, and the RA is entered as the Link MAC Address of the Non-AP STA.

[0104] In step S1510, after completing the scan, the Non-AP STA integrates all scan results and chooses to initiate Multi-Link access on the optimal single Link.

[0105] In step S1520, the Non-AP STA sends a Multi-Link Probe Request frame, filling in address 1 (Addr1) and address 3 (Addr3) in the Probe Request frame with the Link Mac Address of the optimal EHT AP MLD selected after the scan is complete, and also transports information about other links to the STA Control in Link Info.

[0106] 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 based on the received Link.

[0107] In step S1540, the Non-AP STA MLD initiates a Multi-Link Authen Request and carries other Link information requesting association.

[0108] In step S1550, the UHR AP MLD responds to the Multi-Link Authen Response on the received Link.

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

[0110] In step S1570, the UHR AP MLD responds to the Multi-Link Assoc Response on the received Link, indicating whether the association was successful or unsuccessful on the Link requested by the corresponding Non-AP STA.

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

[0112] In step S1590, the non-AP STA MLD and the UHR AP MLD perform four handshake key negotiations on the current link. The PTK is calculated according to the UMAC address of the UHR AP MLD, and the GTK\IGTK\BIGTK is calculated according to the EHT AP MLD Link Address. Additionally, the GTK\IGTK\BIGTK of all links in the same UHR AP MLD are distributed to the non-AP STA MLD.

[0113] Figure 11 shows a schematic diagram of the structure of the KDE field of the multicast key information in the communication method according to the embodiment of this application.

[0114] For each associated link, the broadcast of interaction between the UHR AP MLD and the non-AP STA MLD uses a different multicast key, e.g., GTK\IGTK\BIGTK, where the multicast key is calculated and designed according to the link level, for example, GTK\IGTK\BIGTK is calculated using the LMAC address of each link on the AP side.

[0115] As shown in Figure 11, multicast keys are generated based on the LMAC addresses corresponding to each link on the AP side. To ensure the execution of a four-way handshake in the network access procedure, embodiments of this application extend the EAPOL key KDE (e.g., GTK KDE, IGTK KDE, and BIGTK KDE) with a new field, such as an AP MLD identifier (AP MLD ID) field. The AP MLD identifier field is used to identify the AP MLD corresponding to the Link Identifier (Link ID). Therefore, in a collated UHR AP MLD architecture, the AP MLD identifier field can be linked with the Link Identifier field to distinguish between different AP MLDs on the same frequency link.

[0116] Figure 12 shows a schematic diagram of the structure of the FTE field of the FT protocol for multicast key information in the communication method according to an embodiment of this application.

[0117] Similarly, to ensure the execution of a four-step handshake in a network access procedure, embodiments of this application make similar extensions to the FTE field of the FT protocol, adding, for example, AP MLD identifier fields to the MLOGTK sub-element, MLO IGTK sub-element, and MLO BIGTK sub-element. The AP MLD identifier field can be linked with a Link ID Info field to distinguish between different AP MLDs on the same frequency link.

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

[0119] As shown in Figure 13, the communication method in the wireless local area network may include the following steps.

[0120] In S210, the UHR access point multilink logical entity transmits a first frame to a non-access point multilink logical entity, the first frame containing first link identifier information for the non-access point multilink logical entity's point multilink logical entity to specify the target link of the first access point multilink logical entity to which it will switch (i.e., the target access point multilink logical entity, e.g., target AP MLD).

[0121] In some embodiments, the UHR access point multilink logical entity may be a UHR non-colocated multiaccess point multilink logical entity.

[0122] 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 abbreviated as AP MLD2) and a second access point multilink logical entity (e.g., EHT AP MLD1, hereinafter abbreviated as AP MLD1) belonging 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 abbreviated as STA MLD).

[0123] To make it clear, a UHR access point multilink logical entity sending a frame to a non-access point multilink logical entity may be done by the access point multilink entity associated with the non-access point multilink logical entity among the UHR access point multilink logical entities (i.e., the second access point multilink logical entity, or the original AP MLD, referred to as the service AP MLD), or by the UHR control module in the UHR access point multilink logical entity (e.g., a non-collocated control module), or the UHR control module may instruct the second access point multilink logical entity to send it.

[0124] In some embodiments, the UHR control module may be a UHR AP MLD UMAC, or it may be other hardware or software-based or standalone control device.

[0125] In some embodiments, the first frame is used to instruct roaming reconfiguration.

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

[0127] In some embodiments, the BTM roaming reconfiguration frame may include a UHR mobility domain element to indicate whether or not a UHR multilink logical entity has seamless transition capability.

[0128] Selectively, the target link includes one or more links to which the non-access point multilink logical entity is associated with the second access point multilink logical entity.

[0129] In some embodiments, a UHR access point multilink logical entity sends a first frame to a non-access point multilink logical entity. The second access point multilink logical entity sends the first frame to the non-access point multilink logical entity. The first access point multilink logical entity transmits the first frame to the non-access point multilink logical entity, or The UHR control module may also include instructing a non-access point multilink logical entity to send a first frame.

[0130] In some embodiments, switching a non-access point multilink logical entity to the target link of a first access point multilink logical entity may mean expecting the non-access point multilink logical entity to disassociate itself from the target link (e.g., Link0) of the second access point multilink logical entity (i.e., the original AP MLD, e.g., AP MLD1) and to associate the target link with the first access point multilink entity (i.e., the target AP MLD, e.g., AP MLD2) belonging to the same UHR AP LMD.

[0131] Selectively, the first link identifier information includes the logical entity identifier information of the first access point multilink logical entity and the link information of the target link.

[0132] Selectively, the first link identifier information may be placed in the common information field in the BTM roaming frame.

[0133] Selectively, the logical entity identifier information of the first access point multilink logical entity may be the MLD AP identifier of the first access point multilink logical entity. Selectively, the link information of the target link may include at least one of the number of links, the link identifier, the link switching order, and the link priority.

[0134] Selectively, the common information field may include an MLD AP ID field and a link information field, the MLD AP ID field being used to indicate the MLD AP ID of the first access point multilink logical entity to which the switchover is to take place, and the link information field being used to indicate the link information of the target link.

[0135] Selectively, the link information field may include a Link Num field and one or more Link ID fields.

[0136] In some embodiments, the first frame may include a first instruction for specifying the method of switching the target link (e.g., a release method, a deletion method).

[0137] Selectively, the first instruction may be placed in the STA control field in the BTM roaming frame.

[0138] Selectively, the switching method may be an immediate switching method.

[0139] Selectively, the switching method may be a delayed switching method, and selectively, in this case, the first instruction can specify the delay time length of the delayed switching.

[0140] In one specific embodiment, the first instruction is used to specify a link deletion mode, or a link deletion mode and a link deletion count, thereby enabling delayed release.

[0141] In some embodiments of this application, before the UHR access point multilink logical entity transmits a first frame to a non-access point multilink logical entity, the method 200: The non-access point multilink logical entity further includes sending a second frame to the UHR access point multilink logical entity to initiate a roaming request.

[0142] In some embodiments, a non-access point multilink logical entity transmits a second frame to the UHR access point multilink logical entity. A non-access point multilink logical entity sending a second frame to a second access point multilink logical entity, or This may include a non-access point multilink logical entity sending a second frame to a first access point multilink logical entity.

[0143] In some embodiments, the second frame includes second link identifier information for indicating the link of the access point multilink logical entity that the non-access point multilink logical entity requests as a switch target.

[0144] For example, after a UHR access point multilink logical entity receives a second frame, it obtains a first access point multilink logical entity that the non-access point multilink logical entity expects to switch the target link from the second access point multilink logical entity. Therefore, the UHR AP MLD UMAC may instruct (including indirect or direct control) to disassociate the second access point multilink logical entity from the target link, and to associate the first access point multilink logical entity with the target link, i.e., to associate the first access point multilink logical entity with the non-access point multilink logical entity via the target link.

[0145] Selectively, the second frame may be a BTM roaming request frame.

[0146] Selectively, the second link identifier information may be included in the common information field in the BTM roaming request frame.

[0147] Selectively, 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 being used to indicate the MLD AP ID of the access point multilink logical entity that the non-access point multilink logical entity requests as the failover target, and the link information field being used to indicate the link information of the link that the non-access point multilink logical entity requests failover for. Selectively, the link information may include at least one of the following: the number of links, a link identifier, the failover order of the links, and the priority of the links.

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

[0149] Selectively, the first link identifier information may be determined based on the second link identifier information.

[0150] In some embodiments of this application, after the UHR access point multilink logical entity transmits a first frame to a non-access point multilink logical entity, the method 200: The UHR control module further includes disassociating the second access point multilink logical entity from the target link and instructing the first access point multilink logical entity to be associated with the target link.

[0151] For example, in a wireless roaming process, the UHR AP MLD UMAC can complete the link switching on the AP side by indirectly instructing or directly controlling the second access point multilink logical entity to disassociate it from the target link (e.g., Link0), and by indirectly instructing or directly controlling the first access point multilink logical entity to establish an association with the target link.

[0152] In some embodiments, the UHR AP MLD UMAC may share or copy the unicast key stored in the UHR AP MLD UMAC, obtained based on the UMAC address of the UHR AP MLD, to the first access point multilink logical entity, thereby enabling link switching in wireless roaming. In this way, the non-access point multilink logical entity and the first access point multilink logical entity do not need to perform handshake negotiation for the unicast key, reducing frame overhead in the roaming process and lowering delay in the roaming process.

[0153] In some embodiments of this application, the method 200 is The further includes determining, if pre-defined conditions are met, that the UHR access point multilink logical entity has switched so that the target link of the non-access point multilink logical entity is already associated with the first access point multilink logical entity.

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

[0155] In some embodiments, the preset conditions are: The UHR access point multilink logical entity has received a fourth frame from the non-access point multilink logical entity, This includes at least one of the following: the UHR access point multilink logical entity has transmitted the first frame and a predetermined amount of time has elapsed.

[0156] Selectively, the fourth frame includes fourth link identifier information corresponding to the first link identifier information.

[0157] Selectively, the fourth frame may be a BTM Roaming Confirm frame.

[0158] In some embodiments, if a predetermined time has elapsed since the UHR access point multilink logical entity sent its first frame and no notification of link reconfiguration failure for the non-access point multilink logical entity has been received, then it is assumed that the link of the non-access point multilink logical entity has been successfully reconfigured.

[0159] In some embodiments, the fourth frame may include a fourth instruction for indicating whether the operation requested for the first frame is to be completed by the non-access point multilink logical entity.

[0160] Selectively, the fourth instruction may be placed in the status code field in the BTM roaming frame.

[0161] In some embodiments, after 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, the method proceeds as follows: The UHR access point multilink logical entity further includes transmitting buffered downlink data, which is downlink data already buffered on the target link before the switchover, to the non-access point multilink logical entity.

[0162] In some implementations, the UHR access point multilink logical entity transmits buffered downlink data to the non-access point multilink logical entity. The UHR access point multilink logical entity transmits the buffered downlink data to the non-access point multilink logical entity by the second access point multilink logical entity, and / or The second access point multilink logical entity transmits the buffered downlink data to the first access point multilink logical entity, and the first access point multilink logical entity transmits the buffered downlink data to the non-access point multilink logical entity.

[0163] For example, after the target link of a non-access point multilink logical entity has been switched to be associated with the first access point multilink logical entity, the UHR access point multilink logical entity can transmit downlink data buffered on the target link before the switch via the original AP MLD to the non-access point multilink logical entity. For example, after the target link of a non-access point multilink logical entity has been switched to be associated with the first access point multilink logical entity, the UHR control module may transmit downlink data buffered on the target link before the switch via at least one associated link other than the target link after the switch, where the at least one associated link is a link other than the target link to which the non-access point multilink logical entity is associated with the second access point multilink logical entity.

[0164] For example, after the target link of the non-access point multilink logical entity has been switched so that it is already associated with the first access point multilink logical entity, the UHR access point multilink logical entity may send the downlink data buffered on the target link before the switch by the original AP MLD to the target AP MLD, and the target AP MLD may then send the buffered downlink data to the non-access point multilink logical entity.

[0165] In some embodiments, the fact that the target link of the non-access point multilink logical entity has already been switched to associate with the first access point multilink logical entity may include the fact that the target link to be switched to associate with the non-access point multilink logical entity has already completed the disassociation with the second access point multilink logical entity and the association with the first access point multilink logical entity on the UHR access point multilink logical entity side.

[0166] The UHR control module instructing the UHR AP MLD to transmit the buffered downlink data used for the target link before the switchover via at least one associated link other than the target link after the switchover may indicate that the UHR AP MLD has completed the switchover of at least one or more links, and therefore, in order to complete the downlink data buffered before the switchover, it is still necessary to transmit it to the non-access point multilink logical entity via other still associated links of the second access point multilink logical entity. On the other hand, new data acquired by the UHR AP MLD for transmission to the non-access point multilink logical entity can be instructed by the UHR AP MLD UMAC to be transmitted to the non-access point multilink logical entity via the newly associated link of the first access point multilink logical entity.

[0167] In some embodiments, the UHR control module instructs that the buffered downlink data used for the target link before the switchover be transmitted over at least one associated link other than the target link after the switchover. The UHR control module includes making the buffered downlink data accessible to at least one associated link other than the switched target link, and instructing the UHR control module to transmit the buffered downlink data over the at least one associated link.

[0168] In some embodiments, the UHR control module makes the buffered downlink data accessible to at least one associated link other than the switched target link. The UHR control module instructs the system to share or copy the buffered downlink data to at least one associated link other than the target link after the switchover. The UHR control module instructs the buffered downlink data to be transmitted to the external storage device, provided that at least one associated link is communicatively connected to the external storage device, and / or This includes instructing the UHR control module to transmit the buffered downlink data to the UHR control module.

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

[0170] Additionally or alternatively, the UHR control module may instruct the access point multilink logical entity that caches the downlink data to allow the continuation of transmission on other links associated with the non-access point multilink logical entity by directly transmitting, sharing, or copying the corresponding downlink data.

[0171] Additionally or alternatively, the UHR control module may instruct the access point multilink logical entity that caches the downlink data to send the buffered downlink data to an external storage device (e.g., a cloud server or local server) and for the external storage device to continue sending it to the non-access point multilink logical entity.

[0172] In some embodiments, after 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, the method proceeds as follows: The UHR control module further includes instructing the second access point multilink logical entity to preferentially receive uplink data from the non-access point multilink logical entity via the switched-out target link.

[0173] In some embodiments, after 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, the method proceeds as follows: The UHR control module further includes instructing the non-access point multilink logical entity to transmit data received after the target link switchover, where the target address is the non-access point multilink logical entity, via the switched-over target link.

[0174] In some embodiments, after 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, the method 200 proceeds as follows: The UHR access point multilink logical entity transmits a fifth frame to the non-access point multilink logical entity, wherein the fifth frame further includes fifth link identifier information. The fifth link identifier information is used to instruct the system to switch one or more remaining links of the non-access point multilink logical entity to be associated with the first access point multilink logical entity, the one or more remaining links including one or more links other than the target link among the links associated with the non-access point multilink logical entity and the second access point multilink logical entity.

[0175] In some embodiments, the fifth frame may be a BTM roaming reconfiguration frame for completing the roaming switchover of all links of a non-access point multilink logical entity.

[0176] In some embodiments, the fifth frame may be transmitted by an access point multilink logical entity (e.g., a second access point multilink logical entity) whose remaining links have not been switched by the UHR access point multilink logical entity, or it may be transmitted via an access point multilink logical entity corresponding to the target link (i.e., a first access point multilink logical entity).

[0177] In some embodiments of this application, the method 200 is The UHR access point multilink logical entity further includes determining a first key information of the UHR access point multilink logical entity based on the higher media access control UMAC address of the UHR access point multilink logical entity. The first key information may include unicast key information, such as a PTK.

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

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

[0180] In some embodiments, the method is The UHR control module further includes sharing, copying, or transmitting the first key information to the first access point multilink logical entity for the associated links of the first access point multilink logical entity.

[0181] In some embodiments, the first key information may be shared, copied, or transmitted by the UHR control module to multiple access point multilink logical entities during the network access phase, and may also be shared, copied, or transmitted to the target access point multilink logical entity, for example, the first access point multilink logical entity, during the link switching process of the AP MLD in the wireless roaming process.

[0182] In some embodiments, the first key information is obtained by calculation based on the UHR AP MLD UMAC address, for example, the PTK key information is obtained by calculation based on the UHR AP MLD UMAC address.

[0183] In some embodiments, the method is The UHR access point multilink logical entity transmits the unicast key information of the UHR access point multilink logical entity to the non-access point multilink logical entity, The UHR access point multilink logical entity further includes transmitting multicast key information for one or more links of the first access point multilink logical entity to the non-access point multilink logical entity.

[0184] In some embodiments of this application, the method is The UHR access point multilink logical entity further includes determining multicast key information for one or more links of the first access point multilink logical entity based on the lower media access control LMAC addresses of one or more of the first access point multilink logical entities.

[0185] In some embodiments, the multicast key information may include a fifth instruction for indicating link information corresponding to the multicast key information.

[0186] In some embodiments, the fifth instruction may be placed in the AP MLD ID field in the MLO GTK KDE, MLO IGTK KDE, and MLO BIGTK KDE fields.

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

[0188] In some embodiments of this application, before the non-access point multilink logical entity transmits a second frame to the UHR access point multilink logical entity, the method 200: The UHR access point multilink logical entity further includes transmitting a ninth frame to a non-access point multilink logical entity, the ninth frame being configured to request the non-access point multilink logical entity to transmit the second frame.

[0189] Selectively, the ninth frame may be a BTM roaming query frame. This BTM roaming query frame is used to prompt or request a non-access point multilink logical entity to send a BTM roaming request frame.

[0190] In some embodiments of this application, before the UHR access point multilink logical entity transmits a first frame to a non-access point multilink logical entity, the method 200: The UHR access point multilink logical entity further includes transmitting 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.

[0191] In some embodiments, the sixth frame includes a UHR mobility domain element to indicate that the UHR access point multilink logical entity has seamless transition capabilities.

[0192] In some embodiments, the sixth frame is It may include at least one of the following: Beacon Frame, Probe Response Frame, Association Request Frame, AssociationResponse Frame, and Authentication Frame, and is used to declare the seamless transition capability of the UHR AP MLD (for example, to a non-access point multilink logical entity).

[0193] In some embodiments, the decision of whether a non-access point multilink logical entity initiates roaming may be made by the non-access point multilink logical entity itself, for example, the non-access point multilink logical entity may decide to initiate roaming based on the current link state.

[0194] In some other embodiments, the initiation of roaming by a non-access point multilink logical entity may be determined by the UHR access point multilink logical entity, for example, a second access point multilink logical entity may decide to trigger the non-access point multilink logical entity to initiate roaming based on the uplink signal quality of the non-access point multilink logical entity.

[0195] In some embodiments, the target link may be determined by a non-access point multilink logical entity, for example, a multi-access point multilink logical entity, which is determined based on the uplink signal quality transmitted by multiple access point multilink logical entities of the UHR access point multilink logical entity.

[0196] In some embodiments, the method is The non-access point multilink logical entity transmits a seventh frame to multiple access point multilink logical entities of the UHR access point multilink logical entity, The non-access point multilink logical entity receives an eighth frame transmitted by a plurality of access point multilink logical entities of the UHR access point multilink logical entity, the eighth frame being used to determine the first access point multilink logical entity.

[0197] In some embodiments, the non-access point multilink logical entity transmits a seventh frame on a plurality of links associated with each of the UHR access point multilink logical entities, the non-access point multilink logical entity receives 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 determines the target link of the first access point multilink logical entity to which it is to switch based on the plurality of eighth frames.

[0198] Selectively, the seventh frame may be a probe request frame, and the eighth frame may be a probe response frame.

[0199] In some embodiments, the non-access point multilink logical entity determining the target link of the first access point multilink logical entity based on the plurality of eighth frames includes the non-access point multilink logical entity determining a plurality of signal qualities for a plurality of links corresponding to each of the plurality of eighth frames based on the plurality of eighth frames, and the non-access point multilink logical entity determining the target link of the first access point multilink logical entity based on the plurality of signal qualities.

[0200] In some embodiments, a UHR access point multilink logical entity (e.g., a UHR control module) can provide a non-access point multilink logical entity with a proposed target link set and link priority, the link priority of which may be determined based on the link load of adjacent access point multilink logical entities of the second access point multilink logical entity. Furthermore, the UHR access point multilink logical entity (e.g., a UHR control module) can notify the non-access point multilink logical entity of the target link set and link priority, and the non-access point multilink logical entity can determine the target link by associating the signal quality of the link (e.g., obtained by probe response frames) with the target link set and link priority.

[0201] In some embodiments, before the non-access point multilink logical entity transmits a second frame to the UHR access point multilink logical entity, the method The non-access point multilink logical entity further includes receiving a third frame from the UHR access point multilink logical entity, the third frame including third link identifier information, the third link identifier information is used by the UHR access point multilink logical entity to indicate a candidate access point multilink logical entity and / or candidate link proposed as a switch destination to the non-access point multilink logical entity.

[0202] In some embodiments, the third frame includes a candidate list field, the candidate list field includes at least one sub-element, each sub-element corresponding to a candidate access point multilink logical entity, and each sub-element is used to indicate one or more candidate links of the corresponding candidate access point multilink logical entity. The aforementioned sub-element is, A first field for indicating the address information of the candidate access point multilink logical entity, A second field for indicating whether the non-access point multilink logical entity proposes switching to all candidate links of the candidate access point multilink logical entity, It includes at least one of the following: a third field for indicating one or more candidate links of the candidate access point multilink logical entities proposed as the switching destination.

[0203] Selectively, the third field may indicate one or more proposed candidate links by bitmap format.

[0204] The structure of the third frame will be further explained below, linking Figures 19 through 21.

[0205] In some embodiments, the adjacent access point multilink logical entity 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 via a probe request frame, and further report the link signal quality to the UHR control module, which can then determine the target link based on the link signal quality and link load.

[0206] To facilitate understanding of the embodiments of this application, two AP MLDs and two associated links are described below as examples. In other embodiments, there may be two or more AP MLDs and / or two or more associated links. As those skilled in the art will see, in other embodiments of this application, there may be even more possible link switching methods for cases of two or more AP MLDs and / or two or more associated links.

[0207] Figure 14 is a schematic flowchart of the communication method according to the embodiment of this application.

[0208] In this embodiment, the UHR AP MLD includes a first access point multilink logical entity belonging to the UHR AP MLD (e.g., EHT AP MLD2, hereinafter abbreviated as AP MLD2) and a second access point multilink logical entity (e.g., EHT AP MLD1, hereinafter abbreviated as AP MLD1). 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 abbreviated as STA MLD).

[0209] To make it clear, Link0 and Link1 have different frequency bands or different channels in the same frequency band. For example, the frequency band of Link0 may be 2.4 GHz and the frequency band of Link1 may be 5 GHz, or the frequency band of Link0 may be 5 GHz and the frequency band of Link1 may be 2.4 GHz. In some embodiments, Link2 may be further associated between MLD1 and STA MLD, and its frequency band may be, for example, 6 GHz.

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

[0211] In step S900, the second frame from STA MLD is received.

[0212] Specifically, the second frame may be a BTM Roaming Request frame. The BTM Roaming Request frame contains instruction information that specifies the AP MLD to be switched to and the link to be switched to.

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

[0214] In step S920, the link with STA MLD is switched from AP MLD1 to AP MLD2, and the association between AP MLD1 and the link is removed.

[0215] Specifically, after receiving the second frame, the UHR AP MLD acquires a new AP MLD (i.e., AP MLD2) expecting the STA MLD to switch Link0 from the original AP MLD (i.e., AP MLD1). Therefore, the UHR AP MLD disassociates AP MLD1 from Link0 and associates AP MLD2 with Link0, meaning AP MLD2 and the STA MLD are associated via Link0.

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

[0217] In step S940, the downlink data buffered for STA MLD before the link switchover is transmitted via an already associated link other than Link0, and the new downlink data for STA MLD received after the link switchover is transmitted via the switched-over link.

[0218] After the UHR AP MLD completes the switching of Link0 in the above step, the UHR AP MLD continues to transmit buffered downlink data used for the non-AP STA MLD before the switchover to the non-AP STA MLD via other associated links (e.g., Link1). Specifically, the UHR AP MLD transmits downlink data that was already buffered before the switchover and originally transmitted to the non-AP STA MLD via Link0 before the switchover via other links that are still associated with the non-AP STA MLD, including the link that maintains the association between MLD1 and the non-AP STA MLD, and the link that maintains the association between MLD2 and the non-AP STA MLD.

[0219] Furthermore, the UHR AP MLD transmits newly received downlink data, which will be used by the non-AP STA MLD after the switchover, to the non-AP STA MLD via Link0 after the switchover.

[0220] By continuing to transmit data to the non-AP STA MLD using the above-described method after the switchover, we ensured that both pre- and post-switchover data could be transmitted to the non-AP STA MLD without interruption, thereby guaranteeing the continuity of data transmission in the seamless roaming process and ensuring the reliability of wireless communication transmission.

[0221] In step S960, the first frame is sent to the STA MLD.

[0222] The UHR AP MLD notifies the STA MLD by sending the first frame after completing the link switchover.

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

[0224] In some embodiments, the BTM roaming reconfiguration frame includes a UHR mobility domain element to indicate whether the UHR AP MLD has seamless transition capability.

[0225] In some embodiments, the UHR AP MLD may distribute the first frame to the non-AP STA MLD via the original associated AP MLD1, via other links associated with the non-AP STA MLD, or directly via the UHR AP MLD UMAC.

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

[0227] Alternatively, in another embodiment, during the network access phase, the UHR AP MLD UMAC does not share or copy the unicast key for AP MLD2, which was generated during the network access procedure phase, to AP MLD 1. Therefore, in the seamless roaming process, selectively, before step S960, the UHR AP MLD UMAC needs to share or copy the stored unicast key to the switched-out AP MLD (i.e., MLD 1) to complete the link switch on the UHR AP MLD side, thereby reducing frame overhead during roaming and shortening roaming delays, as it would otherwise require four key handshakes to be performed again when a non-AP STA MLD is switched to a new AP MLD during the roaming process.

[0228] In step S980, the fourth frame from STA MLD is received.

[0229] After receiving the first frame, the STA MLD coordinates the management of the link for receiving downlink data from the UHR AP MLD and the link for sending uplink data to the UHR AP MLD (for example, the STA MLD disassociates itself from AP MLD1 on Link0), thereby enabling seamless roaming.

[0230] The step of adjusting the internal configuration in a non-AP STA MLD includes adjusting the AP MLD identifier information in the field information corresponding to the multicast key, so that the multicast key can automatically correspond to the corresponding link of the AP MLD after the switchover, avoiding confusion of the same frequency link of different AP MLDs and eliminating the frame overhead of having to re-handshake.

[0231] After the non-AP STA MLD has completed its configuration, a fourth frame is sent to the UHR AP MLD. This fourth frame may be a BTM Roaming Confirmation frame.

[0232] In another embodiment, after the non-AP STA MLD's adjustment configuration is complete, the non-AP STA MLD does not need to send a fourth frame. The non-AP STA MLD and the UHR AP MLD determine whether both have completed their switchover configuration based on a specified time period; that is, by default, the non-AP STA MLD completes the switchover after a specified time period following the UHR AP MLD sending its first frame. If the configuration cannot be completed within the specified time period, a notification is sent to inform the other party that the switchover has failed.

[0233] In another embodiment, after one or a set of links between the non-AP STA MLD and the original AP MLD of the UHR AP MLD have completed switching, the remaining link switching between the non-AP STA MLD and the original AP MLD is completed according to similar method steps, which are not described further herein.

[0234] In another embodiment, an EHT AP MLD belonging to a UHR AP MLD may further include a corresponding EHT AP MLD UMAC, which is directly connected to the DS and configured to be compatible with other communication networks (e.g., Wi-Fi 7).

[0235] Figure 15 shows a flowchart of a portion of the wireless roaming flow in a communication method according to an embodiment of this application. As shown in Figure 15, the following steps may be included.

[0236] In step S1300, an association is established in the network access procedure such that Link0 of non-AP STA MLD (hereinafter abbreviated as STA MLD) is associated with Link0 of EHT AP MLD1 (hereinafter abbreviated as AP MLD1), and Link1 of STA MLD is associated with Link1 of EHT AP MLD1.

[0237] To make it easier to understand, when STA MLD's Link0 is associated with MLD1's Link0, it means that both ends of Link0 are associated with STA MLD and AP MLD1, respectively.

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

[0239] In some embodiments, the current link state is: The signal quality of the link associated with AP MLD1 and STA MLD, The current distance between AP MLD and STA MLD related links, The current load status of AP MLD for related links, This includes at least one of the following: the current link load status.

[0240] Selectively, the link state may further include other parameters that affect the signal quality of the associated link between the AP MLD and the STA MLD, and this application is not limited thereto.

[0241] In another embodiment, the UHR AP MLD (e.g., by UHR AP UMAC, AP MLD1, or AP MLD2) may determine whether or not the STA MLD should roam, or prompt 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 links, prompting the STA MLD to decide whether or not to roam.

[0242] In step S1320, in the overlapping region covered by the signals, the STA MLD uses all of its links simultaneously or sequentially to send probe request frames to neighboring AP MLDs (e.g., AP MLD2). Each neighboring AP MLD is connected to the same UHR AP MLD UMAC or belongs to the same UHR AP MLD. Each AP MLD (e.g., AP MLD2) responds to the probe request frame from the STA MLD with a probe response frame.

[0243] In step S1330, the STA MLD determines the link state of each link based on the probe response frames returned from each link, and then determines the target AP MLD to switch to (e.g., AP MLD2) based on the link state of each link.

[0244] Selectively, the link state may include at least one of the following: the signal quality of the link between the AP MLD and the STA MLD determined based on the probe response frame; the distance between the AP MLD and the STA MLD; the load status of the AP MLD; and the load status of the link.

[0245] Selectively, in S1330, the STA MLD can further determine the link switching order in a seamless roaming process that switches to AP MLD2, for example, by first switching Link0 from AP MLD1 to AP MLD2, that is, the STA MLD disassociates AP MLD1 from Link0 and associates it with AP MLD2 from Link0.

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

[0247] In step S1340, the STA MLD selects an appropriate link from the associated links as the target link to be switched, and sends a BTM roaming request frame to the original AP MLD associated with the target link (i.e., AP MLD1), the BTM roaming request frame can carry 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).

[0248] Selectively, after determining the target link, the STA MLD may send identifier information indicating the AP MLD to be switched to and link information of the target link to the UHR AP MLD, for example, to any associated AP MLD belonging to the UHR AP MLD (e.g., the AP MLD to which the target link was originally associated), or to the UHR AP MLD UMAC.

[0249] In step S1350, the UHR AP MLD instructing the AP MLD to switch links (including indirect instruction or direct control) specifically includes the following steps:

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

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

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

[0253] 4) After the STA MLD completes link reconfiguration, it sends a BTM roaming confirmation frame to AP MLD2 via the switched-over link (from STA MLD's Link0 to AP MLD2's Link0) to notify the UHR AP MLD that the STA MLD has successfully completed link reconfiguration.

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

[0255] Specifically, the UHR AP MLD may preferentially transmit newly received downlink data after link switching via the newly associated Link0 between the STA MLD and the AP MLD2. Before the link switching is successfully completed, the buffered downlink data that was buffered by the UHR AP MLD and originally used to be transmitted to the STA MLD via the pre-switching Link0 can continue to be transmitted via the remaining associated links between the UHR AP MLD and the STA MLD (i.e., the unswitched associated links). These buffered downlink data can be set by the UHR UMAC to be accessible by the AP MLD corresponding to the remaining associated links. With such a configuration, in the STA MLD roaming flow, the transmission of downlink data will not experience transmission interruption caused by roaming switching, which ensures the continuity of data transmission in the roaming process and improves the reliability of data transmission for wireless roaming.

[0256] In some other embodiments, with respect to step S1350 and step S1360, alternatively, the communication method may include the following steps.

[0257] In step S1352, the UHR AP MLD controls link switching on the AP side, which specifically includes the following steps.

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

[0259] 2) When the UHR UMAC approves the above roaming request, the original AP MLD transmits a BTM roaming reconfiguration frame to the STA MLD via the corresponding reception link. The UHR AP MLD UMAC updates the configuration of the target link (Link0). The UHR AP MLD preferentially transmits data via the new link between Link0 of the STA MLD and Link0 of MLD2.

[0260] 3) When receiving the BTM roaming reconfiguration frame, the STA MLD triggers link reconfiguration of the corresponding link (Link0) of the STA MLD (that is, non-AP side link switching, for example, switching from the association between STA MLD Link0 and AP MLD1 Link0 to the association between STA MLD Link0 and AP MLD2 Link0).

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

[0262] In some other embodiments, for the above step 4), alternatively 4a) The STA MLD transmits a BTM roaming confirmation frame to the AP MLD2, which indicates whether the reconfiguration of Link0 of the STA MLD is successful. When the Link0 reconfiguration of the STA MLD is successful, the STA MLD transmits the BTM roaming confirmation frame to the AP MLD2 via the switched link (from Link0 of the STA MLD to Link0 of AP MLD2), to notify the UHR AP MLD that the STA MLD has successfully completed the reconfiguration.

[0263] In some other embodiments, after the above step 4), optionally, the communication method further comprises: 5a) If the UHR AP MLD does not receive a BTM roaming confirmation frame sent by the STA MLD after a predetermined time interval, the STA MLD confirms that the reconfiguration was successful.

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

[0265] In step S1370, the switching of the remaining links between the STA MLD and the original AP MLD is completed. For example, this may include the following steps:

[0266] 1) The UHR AP MLD UMAC decides to switch the remaining links. Selectively, the reconfiguration of the remaining links of the STA MLD may be triggered by a BTM roaming reconfiguration frame received over an existing associated link (e.g., Link1 of AP MLD1 or Link0 of AP MLD2).

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

[0268] 3) After reconfiguration, the STA MLD sends a BTM roaming confirmation frame to the AP MLD2 via the remaining link after the switchover (e.g., Link1).

[0269] 4) Complete the roaming switchover for all links of the STA MLD, and the STA MLD will communicate only with AP MLD2.

[0270] Figure 17 shows a flowchart of the seamless roaming flow of a communication method according to another embodiment of this application.

[0271] As shown in the diagram, the seamless roaming flow of the communication method may include the following steps.

[0272] In step S1600, STA has already completed the network access connection with AP1, and all links are associated.

[0273] In step S1610, the STA determines that roaming is necessary based on the current network conditions and decides to initiate roaming.

[0274] In step S1620, the STA sends a Probe Request (not carrying a Multi-Link element) on each Link, and all Non-collocated AP MLDs belonging to the UHR return a Probe Response.

[0275] In step S1630, the STA measures the signal quality based on the Probe Response and determines the link switching order between the Non-collocated AP MLD2 belonging to the roaming destination UHR and the currently associated link.

[0276] In step S1640, the STA selects an appropriate Link from among the associated links and sends a BTM Roaming frame (e.g., BTM roaming request) containing a Roaming Request to EHT AP MLD1 (referred to as AP MLD1), carrying a Multi-Link reconfigure element and informing AP MLD1 of the EHT AP MLD2 (referred to as AP MLD2) to which it intends to roam and switch, and the target switching link, i.e., the link to be reconfigured, e.g., Link ID.

[0277] In step S1650, AP MLD1 sends a BTM Roaming Reconfigure frame to STA on the corresponding received Link, triggering STA to perform Link1 reconfiguration. STA disconnects Link1 from AP MLD1's Link1 and reconfigures it to AP MLD2's Link1. After successful reconfiguration, STA sends a BTM Roaming Confirm frame to AP MLD2 on the newly connected Link1 to confirm that Link1 reconfiguration was successful. Throughout this process, STA Link2 maintains connection and communication with AP MLD1's Link2.

[0278] In step S1660, seamless data transmission is performed during the switching process. After the Link1 switchover is complete, the UHR AP MLD UMAC forwards and transmits new service data with target address STA to AP MLD2 Link1, while downlink service data buffered in AP MLD1 Link2 can still be transmitted to STA via MLD1 Link2. After the link switchover is successful, STA's uplink service data is preferentially transmitted via Link 1, which has already completed the switchover. In this process, STA maintains data communication with MLD1 via Link2 and with MLD2 via Link1.

[0279] In step S1670, the UHR MLD UMAC determines to switch the remaining links, which may be via Link2 of AP MLD1 or via Link1 of AP MLD2, and transmits a BTM Roaming ReConfigure frame to the STA to trigger reconfiguration of STA Link2. After receiving the frame, the STA reconfigures Link 2 from AP MLD1 to AP MLD2. After the reconfiguration is successful, the STA transmits a BTM Roaming Confirm frame to AP MLD2 on Link2 to confirm that the Link2 reconfiguration is successful. Up to this point, all Links of the STA have completed roaming switching, and the STA connects and communicates only with AP MLD2.

[0280] The difference between the embodiment shown in FIG. 18 and the aforementioned embodiment is that in this embodiment, the UHR AP MLD determines to start roaming based on uplink signal quality.

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

[0282] Referring to Figure 18, this embodiment can be applied to a UHR AP logical entity architecture that has already completed network access procedure step 1710, namely, the non-AP STA MLD and the AP MLD1 of the UHR AP MLD are associated by link Link0, and the non-AP STA MLD and the AP MLD1 of the UHR AP MLD are associated by link Link1. The roaming flow of this embodiment includes the following steps.

[0283] In step S1720, AP MLD1 decides that the non-AP STA MLD should prepare for roaming based on the uplink signal quality. AP MLD1 notifies the UHR AP MLD UMAC of this information via the backhaul link. The UHR AP MLD UMAC then provides a target link set and sets the link priority 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 priority via the backhaul link.

[0284] In step S1730, AP MLD1 notifies 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.

[0285] BTM request frames can trigger non-AP STA MLD roaming flows along with downlink quality.

[0286] In step S1740, the non-AP STA MLD sends probe requests to one or more neighboring AP MLDs (e.g., AP MLD2) one by one through all of its links and receives corresponding probe responses. All neighboring AP MLDs belong to the same UHR AP MLD UMAC. The neighboring AP MLDs (e.g., AP MLD2) send 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 for the links in the target link set. The non-AP STA MLD determines the target link for roaming (e.g., link 0 of AP MLD2) based on a combination of link priority and the probe response signal quality for the link. That is, in this step, the non-AP STA MLD determines the target link (e.g., link 0 between the non-AP STA MLD and AP MLD2).

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

[0288] Figure 19 shows 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 byte length of which is variable.

[0289] The BSS transition candidate entry field may contain zero or more neighbor report elements. These neighbor report elements contain a subelement field. The length of the subelement field may be variable, for example, 3 octets, 5 octets, or other lengths.

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

[0291] As shown in Figure 20, a BSS transition candidate preference sub-element includes a preference field, the length of which may be 1 octet, 2 octets, or other lengths.

[0292] In one embodiment, the value of the preference field is used to indicate the preferred order of the BSS. For example, a value of 255 in the preference field indicates the most preferred candidate, i.e., the most preferred AP MLD. A value of 1 in the preference field indicates the least preferred candidate, i.e., the least preferred AP MLD.

[0293] Figure 21 shows the basic multi-link element structure of a BSS transition candidate entry field in yet another embodiment of this application.

[0294] When an AP MLD does not have a specific AP to which it belongs, and it attempts to provide a preference for the reported AP MLD, all subfields in the Presence bitmap field can be set to 0, and the basic multilink element does not contain any Per-STA Profile subfields.

[0295] When an AP MLD has only one subset of APs to which it belongs, and attempts to provide preferences to the reported AP MLD, the common information of the basic multilink element includes a Link ID Info field, and the value of the Link ID Info field is set to correspond to the value of the corresponding field of the AP reported in the neighboring report element.

[0296] The difference between the embodiment shown in Figure 22 and the exemplary embodiment described above is that the roaming trigger method is different; specifically, the AP MLD initiates roaming based on the uplink signal.

[0297] A further difference between the embodiment shown in Figure 22 and the exemplary embodiment described above is the method of determining the target link (i.e., the link to be switched). 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 identifies the target link based on the combination of link load status and uplink signal quality.

[0298] In the embodiment shown in Figure 22, this embodiment is applied to the UHR AP logical entity architecture of network access procedure step S2010, namely, the non-AP STA MLD and the AP MLD1 of the UHR AP MLD are associated by link Link0, and the non-AP STA MLD and the AP MLD1 of the UHR AP MLD are associated by link Link1. The roaming flow of this embodiment includes the following steps.

[0299] In step S2020, the original AP MLD (e.g., AP MLD1) prepares the non-AP STA MLD for roaming based on the uplink signal quality. The original AP MLD sends a roaming preparation message to one or more neighboring AP MLDs (e.g., AP MLD2) via the UHR AP MLD UMAC. After receiving the packet, 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 of the MLD roaming preparation packet by using a BTM request frame.

[0300] In step S2030, the BTM request frame triggers a roaming flow for a non-AP STA MLD. The non-AP STA MLD uses all of its links one by one to send probe request signals to one or more neighboring AP MLDs (e.g., AP MLD2, AP MLD3, etc.), all of which belong to the same UHR AP MLD UMAC.

[0301] In step S2040, 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 the 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, the link between the non-AP STA MLD and AP MLD 2).

[0302] In the embodiment shown in Figure 22, on the one hand, the probe signal quality is evaluated by the AP MLD rather than the non-AP STA MLD, thereby reducing the burden on the non-AP STA MLD. On the other hand, in this embodiment, the non-AP MLD does not need to notify the original AP MLD on the target link, and the AP MLD does not need to send probe responses to the non-AP STA MLD, thereby reducing frame overhead and improving seamless roaming efficiency.

[0303] Figures 23 and 24 show yet another example of the format of a UHR mobility domain field according to the embodiment of this application.

[0304] As shown in the figures, the difference between the embodiment shown in Figure 3 and Figure 4 is that in the ST capability field of the UHR mobility domain field, the length of the seamless BSS transition mode field is 2 bits, and the reserved field is 6 bits. When the length of the seamless BSS transition mode field is 2, the value of the field may have a different meaning, as shown in Figure 24.

[0305] A value of 0 for the Seamless BSS Transition Mode indicates that the Seamless Roaming Mode does not have seamless transition capability. A value of 1 for the Seamless BSS Transition Mode indicates that the Seamless Roaming Mode initiates seamless roaming via a non-AP STA MLD. A value of 2 for the Seamless BSS Transition Mode indicates that the Seamless Roaming Mode initiates seamless roaming via an AP MLD and determines the roaming target link (e.g., the link to be switched to roaming) via a non-AP STA MLD. A value of 3 for the Seamless BSS Transition Mode indicates that the Seamless Roaming Mode initiates seamless roaming via an AP MLD and determines the roaming target link via a UHR AP MLD UMAC.

[0306] The communication method described in this application will be further explained below.

[0307] Each embodiment of the present application provides a method for communication in a wireless network, applicable to a non-collocated control module of an ultra-high reliability (UHR) non-collocated access point multi-link logical entity, the method comprising instructing the UHR control module to transmit a first frame containing first link identifier information, the first link identifier information indicating that the non-access point multi-link logical entity should be switched to one or more links associated with the first access point multi-link logical entity.

[0308] In one embodiment, the first link identifier information includes logical entity identifier information corresponding to the first access point multilink logical entity and link information corresponding to one or more links.

[0309] In one embodiment, before the UHR control module instructs the non-access point multilink logical entity to transmit the first frame, the method further includes instructing the UHR control module to disassociate the second access point multilink logical entity from the one or more links, and to associate the first access point multilink logical entity with the one or more links.

[0310] In one embodiment, before the UHR control module instructs the non-access point multilink logical entity to transmit the first frame, the method further includes the UHR control module receiving a second frame from the non-access point multilink logical entity, the second frame comprising second link identifier information, the first link identifier information corresponding to the second link identifier information.

[0311] In one embodiment, each of the one or more links is associated with the non-access point multilink logical entity and the second access point link logical entity.

[0312] In one embodiment, the first frame further includes a first instruction that indicates a method for releasing one or more links.

[0313] In one embodiment, the release method is a delayed release, and the first instruction further indicates the delay time length of the delayed release.

[0314] In one embodiment, the first frame further includes a second instruction indicating whether the operation requested for the second frame is to be completed by the UHR control module.

[0315] In one embodiment, after the UHR control module instructs the non-access point multilink logical entity to transmit the first frame, the method: In response to the fulfillment of pre-defined conditions, the UHR control module further includes confirming that one or more links of the non-access point multilink logical entity have been switched to be associated with the first access point multilink logical entity.

[0316] In one embodiment, the preset condition includes the UHR control module receiving a fourth frame from the non-access point multilink logical entity, the fourth frame including fourth link identifier information corresponding to the first link identifier information.

[0317] In one embodiment, the fourth frame further includes a fourth instruction indicating whether the operation requested for the first frame is to be completed by the non-access point multilink logical entity.

[0318] In one embodiment, the preset condition includes indicating that a preset time has elapsed since the UHR control module transmitted the first frame.

[0319] In one embodiment, after one or more links of the non-access point multilink logical entity have been switched to be associated with the first access point multilink logical entity, the method further includes instructing the UHR control module to transmit buffered downlink data used for one or more links before the switch over at least one associated link other than the one or more links after the switch, the at least one associated link being associated with the non-access point multilink logical entity and the second access point multilink logical entity, respectively.

[0320] In one embodiment, instructing the UHR control module to transmit buffered downlink data used on one or more links before the switchover via at least one associated link other than the one or more links after the switchover includes making the buffered downlink data accessible to the at least one associated link other than the one or more links after the switchover, and instructing the UHR control module to transmit the buffered downlink data via the at least one associated link.

[0321] In one embodiment, making the buffered downlink data accessible to at least one associated link other than the one or more links after the switchover includes instructing the UHR control module to share or copy the buffered downlink data to at least one associated link other than the one or more links after the switchover, and instructing the UHR address control module to transmit the buffered downlink data to an external storage device, wherein the at least one associated link is able to communicate with the external storage device, or instructing the UHR control module to transmit the buffered downlink data to the UHR control module.

[0322] In one embodiment, after one or more links of the non-access point multilink logical entity have been switched to be associated with the first access point multilink logical entity, the method further includes instructing the UHR control module to preferentially receive uplink data from the non-access point multilink logical entity via the switched one or more links.

[0323] In one embodiment, after one or more links of the non-access point multilink logical entity have been switched so that they are already associated with the first access point multilink logical entity, the method further includes instructing the UHR control module to transmit data received after the one or more links switch, whose target address is the non-access point multilink logical entity, to the non-access point multilink logical entity via the switched one or more links.

[0324] In one embodiment, after one or more links of the non-access point multilink logical entity have been switched to be associated with the first access point multilink logical entity, the method further includes instructing the UHR control module to transmit a fifth frame containing fifth link identifier information, the fifth link identifier information indicating that the non-access point multilink logical entity should be switched to one or more remaining links associated with the first access point multilink logical entity.

[0325] In one embodiment, after the UHR control module has confirmed that one or more links of the non-access point multilink logical entity have been switched to be associated with the first access point multilink logical entity, the method The UHR control module further includes sharing or copying first key information for the UHR access point multilink logical entity to the first access point multilink logical entity for the associated links of the first access point multilink logical entity.

[0326] In one embodiment, the first key information is a higher-level media access control (UMAC) address based on the UHR control module.

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

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

[0329] In one embodiment, the types of multicast key information include group ephemeral keys (GTK), integrated group ephemeral keys (IGTK), and beacon integrated group ephemeral keys (BIGTK).

[0330] 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, the ninth frame being configured to request the non-access point multilink logical entity to send the second frame.

[0331] In one embodiment, the UHR control module is configured to store first key information used for the UHR access point multilink logical entity.

[0332] In one embodiment, before the UHR control module instructs the non-access point multilink logical entity to transmit the first frame, the method further includes instructing the UHR control module to transmit a sixth frame including a UHR mobility domain field element, the UHR mobility domain element indicating the seamless transition capability of the UHR access point multilink logical entity.

[0333] In one embodiment, the method further includes determining a first key information to be used for the UHR access point multilink logical entity based on the UMAC address of the UHR control module, wherein the first key information is stored in the UHR control module.

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

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

[0336] In one embodiment, the method further includes determining multicast key information for one or more links used by 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 instructing the UHR control module to transmit the multicast key information to the non-access point multilink logical entity.

[0337] Each embodiment of the present application provides a communication method in a wireless local area network applicable to a non-access point multilink logical entity, wherein the non-access point multilink logical entity is associated with a non-collocated control module of an ultra-high reliability (UHR) non-collocated access point multilink logical entity, and the method comprises the non-access point multilink logical entity transmitting a second frame to the UHR access point multilink logical entity, wherein the second frame includes second link identifier information, which indicates that the non-access point multilink logical entity should be switched to one or more links associated with a first access point multilink logical entity.

[0338] In one embodiment, the second link identifier information includes logical entity identifier information corresponding to the first access point multilink logical entity and link information corresponding to one or more links.

[0339] In one embodiment, each of the one or more links is associated with the non-access point multilink logical entity and the second access point link logical entity.

[0340] Specifically, the one or more links may be one or more links that require the non-access point multilink logical entity to disassociate from the second access point link logical entity.

[0341] Alternatively, the one or more links may be one or more links that the UHR control module requests to be disassociated from the non-access point multilink logical entity.

[0342] In one embodiment, after the non-access point multilink logical entity transmits the second frame to the UHR access point multilink logical entity, the method further includes the non-access point multilink logical entity receiving a first frame from the UHR access point multilink logical entity, the first frame comprising first link identifier information, and the second link identifier information corresponding to the first link identifier information.

[0343] In one embodiment, after the non-access point multilink logical entity has received the first frame from the UHR access point multilink logical entity, the method further includes the non-access point multilink logical entity transmitting a fourth frame to the UHR access point multilink logical entity, the fourth frame comprising a fourth link identifier information corresponding to the first link identifier information.

[0344] In one embodiment, the fourth frame further includes a fourth instruction indicating whether the operation requested for the first frame is to be completed by the non-access point multilink logical entity.

[0345] In one embodiment, after the non-access point multilink logical entity receives the first frame from the UHR access point multilink logical entity, the method further includes the non-access point multilink logical entity disassociating itself with the second access point multilink logical entity on the one or more links, and the non-access point multilink logical entity associating itself with the first access point multilink logical entity on the one or more links to complete the switching of the one or more links.

[0346] In one embodiment, after the non-access point multilink logical entity and the first access point multilink logical entity are associated on the one or more links, the method further includes the non-access point multilink logical entity preferentially transmitting uplink data to the first access point multilink logical entity via the switched-out one or more links.

[0347] In one embodiment, after the non-access point multilink logical entity has been associated with the first access point multilink logical entity on one or more links, the method further includes the non-access point multilink logical entity receiving buffered downlink data from the UHR access point multilink logical entity on at least one associated link other than the one or more links after the switchover, wherein the buffered downlink data is buffered downlink data used on the one or more links before the switchover.

[0348] In one embodiment, the method further includes the non-access point multilink logical entity transmitting a seventh frame on a plurality of links each 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.

[0349] In one embodiment, the non-access point multilink logical entity determining one or more links of the first access point multilink logical entity based on the plurality of eighth frames includes the non-access point multilink logical entity determining multiple signal qualities of multiple links corresponding to each of the plurality of eighth frames based on the plurality of eighth frames, and the non-access point multilink logical entity determining one or more links of the first access point multilink logical entity based on the multiple signal qualities.

[0350] 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 a corresponding lower media access control (LMAC) address based on the access point multilink logical entity.

[0351] In one embodiment, the method further comprises the non-access point multilink logical entity receiving a sixth frame from the UHR access point multilink logical entity, the sixth frame including a UHR mobility domain field element indicating the seamless transition capability of the UHR access point multilink logical entity.

[0352] Each exemplary embodiment of this application provides a method for constructing a communication frame, which is applied to wireless network communication of ultra-high reliability (UHR) non-colocated access point multilink logical entities, and the method includes generating a first instruction field indicating that the non-access point multilink logical entity should be switched to one or more links associated with a first access point multilink logical entity belonging to the UHR access point multilink logical entity.

[0353] In one embodiment, the first instruction field includes logical entity identifier information corresponding to the first access point multilink logical entity and link information corresponding to one or more links.

[0354] In one embodiment, the link information includes link count information and information on one or more link identifiers.

[0355] In one embodiment, the first instruction field further includes an STA control field.

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

[0357] In one embodiment, the method further includes generating an action field, the field content included in the first instruction field depends on the value of the action field.

[0358] In one embodiment, the first instruction further indicates the switching sequence of the one or more links.

[0359] Each exemplary embodiment of this application provides a method for constructing a communication frame, which is applied to wireless network communications of ultra-high reliability (UHR) non-colocated access point multilink logical entities. This includes generating a mobility domain element field, the UHR mobility element field including a seamless transition capability field.

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

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

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

[0363] In one embodiment, the UHR mobility domain field multiplexes the FT Capability and Policy subfield in the Mobility Domain Information element (MDIE) field. Each embodiment of the present application provides an access point device and includes a transmission module configured to transmit a first frame to a non-AP multi-link logical entity, the first frame including first link identifier information indicating that the non-AP multi-link logical entity should be switched to one or more links associated with the first access point multi-link logical entity.

[0364] Figure 25 is a schematic diagram of the structure of an access point device 400 according to an embodiment of this application. The access point device 400 may also be an access point multilink device 202 in a WLAN as shown in Figure 1. As shown in Figure 25, the access point device 400 is A receive module 410 for receiving a second frame from a non-access point multilink logical entity to initiate a roaming request, Includes a transmit module 420 for sending a first frame to a non-access point multilink logical entity, The access point device 400 includes a first access point multilink logical entity and a second access point multilink logical entity, the second access point multilink logical entity being associated with the non-access point multilink logical entity.

[0365] In some embodiments, the first frame includes first link identifier information for indicating the target link of the first access point multilink logical entity to which the non-access point multilink logical entity will be switched.

[0366] In some embodiments, the second frame includes second link identifier information for indicating the link of the access point multilink logical entity that the non-access point multilink logical entity requests as a switch target.

[0367] Selectively, the access point device 400 may be an access point multilink logical entity, such as a UHR access point multilink logical entity.

[0368] In some embodiments, the transmitting module 420 further, It is used to transmit a first frame to the non-access point multilink logical entity by the first access point multilink logical entity or the second access point multilink logical entity.

[0369] In some embodiments, the receiving module 410 further, It is used to receive a second frame from the non-access point multilink logical entity by the first access point multilink logical entity or the second access point multilink logical entity.

[0370] In some embodiments, the first link identifier information includes identifier information for the first access point multilink logical entity and link information for the target link.

[0371] In some embodiments, the first frame includes a common information field, and the first link identifier information is carried to the common information field.

[0372] In some embodiments, the first frame further includes a first instruction for indicating the switching method of the target link.

[0373] In some embodiments, the first instruction is used to instruct an immediate switchover, or the first instruction is used to instruct a delayed switchover, and the first instruction is further used to instruct the delay time length of the delayed switchover.

[0374] In some embodiments, before receiving a second frame from the non-access point multilink logical entity, the transmitting module 420 further: A third frame is used to transmit a third frame to the non-access point multilink logical entity, the third frame containing third link identifier information, which the access point device 400 uses to indicate to the non-access point multilink logical entity a candidate access point multilink logical entity and / or a candidate link proposed as a switching destination.

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

[0376] In some embodiments, the sub-element is A first field for indicating the address information of the candidate access point multilink logical entity, A second field for indicating whether the non-access point multilink logical entity proposes switching to all candidate links of the candidate access point multilink logical entity, It includes at least one of the following: a third field for indicating one or more candidate links of the candidate access point multilink logical entities proposed as the switching destination.

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

[0378] In some embodiments, the access point device 400 is The system further includes a processing module for determining that, when pre-defined conditions are met, 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, The aforementioned pre-set conditions are: The reception of a fourth frame from the non-access point multilink logical entity, wherein the fourth frame includes a fourth link identifier information, and the fourth link identifier information corresponds to the first link identifier information. This includes at least one of the following: a predetermined amount of time has elapsed since the transmission of the first frame.

[0379] In some embodiments, after 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, the transmitting module 420 further: Used to transmit a fifth frame to the aforementioned non-access point multilink logical entity, wherein the fifth frame includes fifth link identifier information. The fifth link identifier information is used to instruct the system to switch one or more remaining links of the non-access point multilink logical entity to be associated with the first access point multilink logical entity, the one or more remaining links including one or more links other than the target link among the links associated with the non-access point multilink logical entity and the second access point multilink logical entity.

[0380] In some embodiments, after 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, the transmitting module 420 further: This method involves transmitting buffered downlink data to the non-access point multilink logical entity, wherein the buffered downlink data is downlink data that was already buffered on the target link before the switchover.

[0381] In some embodiments, the transmitting module 420 further, The second access point multilink logical entity is used to transmit the buffered downlink data to the non-access point multilink logical entity.

[0382] In some embodiments, the transmitting module 420 further, The second access point multilink logical entity transmits the buffered downlink data to the first access point multilink logical entity, This is used to transmit the buffered downlink data from the first access point multilink logical entity to the non-access point multilink logical entity.

[0383] In some embodiments, the access point device 400 is The system includes a processing module for determining the unicast key information of the access point device 400 based on the higher-level media access control UMAC address of the access point device 400.

[0384] The processing module is further used to share, copy, or transmit the unicast key information of the access point device 400 to the first access point multilink logical entity. The transmission module 420 is further used to transmit unicast key information of the access point device 400 to the non-access point multilink logical entity.

[0385] In some embodiments, the access point device 400 is The system further includes a processing module for determining multicast key information for each link of one or more of the first access point multilink logical entities based on the lower media access control LMAC addresses of one or more of the first access point multilink logical entities.

[0386] In some embodiments, the transmitting module 420 is further used to transmit multicast key information for one or more links of the first access point multilink logical entity to the non-access point multilink logical entity.

[0387] In some embodiments, before sending the first frame to a non-access point multilink logical entity, the transmitting module 420 further: The method involves transmitting 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 capabilities.

[0388] In some embodiments, the sixth frame includes an ultra-high reliability UHR mobility domain element, which is used to indicate that the UHR access point multilink logical entity has seamless transition capabilities.

[0389] In some embodiments, the receiving module 410 is further used to receive a seventh frame transmitted by the non-access point multilink logical entity by a plurality of access point multilink logical entities, and The transmitting module 420 is further used by the plurality of access point multilink logical entities to transmit an eighth frame in response to the seventh frame to the non-access point multilink logical entity, the eighth frame being used to determine the first access point multilink logical entity.

[0390] The access point device 400 may further include other modules to perform the communication methods of each of the above embodiments. Each of the above exemplary embodiments of the communication methods, and any improvements, modifications, and variations obtained based on these embodiments where a person skilled in the art does not exert creative effort, may be used to limit the access point device 400, and this application will not describe them further.

[0391] Figure 26 is a schematic diagram of the structure of a non-access point device 500 according to an embodiment of this application. The non-access point device 500 may also be a terminal 201 in the WLAN shown in Figure 1. As shown in Figure 26, the non-access point device 500 is Transmitting module 510 to send a second frame to initiate a roaming request to an ultra-high reliability UHR access point multilink logical entity, Includes a receiving module 520 for receiving a first frame from the UHR access point multilink logical entity to instruct roaming reconfiguration, The UHR access point multilink logical entity includes a first access point multilink logical entity and a second access point multilink logical entity, the second access point multilink logical entity being associated with the non-access point device 500.

[0392] In some embodiments, the first frame includes first link identifier information for indicating the target link of a first access point multilink logical entity to which the non-access point device 500 will be switched.

[0393] In some embodiments, the second frame includes second link identifier information for indicating the link of the access point multilink logical entity that the non-access point device 500 requests as a switching target.

[0394] Selectively, the non-access point device 500 may be a non-access point multilink logical entity.

[0395] In some embodiments, the receiving module 520 is further described below. It is used to receive a first frame transmitted by the first access point multilink logical entity or the second access point multilink logical entity of the UHR access point multilink logical entity.

[0396] In some embodiments, the first link identifier information includes identifier information for the first access point multilink logical entity and link information for the target link.

[0397] In some embodiments, the first frame includes a common information field, and the first link identifier information is carried to the common information field.

[0398] In some embodiments, the first frame further includes a first instruction for indicating the switching method of the target link.

[0399] In some embodiments, the first instruction is used to instruct an immediate switchover, or the first instruction is used to instruct a delayed switchover, and the first instruction is further used to instruct the delay time length of the delayed switchover.

[0400] In some embodiments, the access point multilink logical entity and link indicated by the second link identifier 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 belonging to the UHR access point multilink logical entity.

[0401] In some embodiments, before sending a second frame to the UHR access point multilink logical entity, the method The receiving module 520 is further used to receive a third frame from the UHR access point multilink logical entity, the third frame including third link identifier information, the third link identifier information is used by the UHR access point multilink logical entity to indicate to the non-access point device 500 a candidate access point multilink logical entity and / or candidate link to be switched to.

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

[0403] In some embodiments, the sub-element is A first field for indicating the address information of the candidate access point multilink logical entity, A second field for indicating whether the non-access point device 500 proposes switching to all candidate links of the candidate access point multilink logical entity, or It includes at least one of the following: a third field for indicating one or more candidate links of the candidate access point multilink logical entities proposed as the switching destination.

[0404] In some embodiments, the access point multilink logical entity and link indicated by the second link identifier information are determined by the non-access point device 500 based on the link quality of the candidate link of the candidate access point multilink logical entity indicated by the third link identifier information.

[0405] 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 multilink logical entity, the receiving module 520 further: Used to receive a fifth frame containing fifth link identifier information from the aforementioned UHR access point multilink logical entity, The fifth link identifier information is used to instruct the system to switch one or more remaining links of the non-access point multilink logical entity to be associated with the first access point multilink logical entity, wherein 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 multilink logical entity.

[0406] 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 multilink logical entity, the receiving module 520 further: The method involves receiving buffered downlink data from the UHR access point multilink logical entity, wherein the buffered downlink data is downlink data that was already buffered on the target link before the switchover.

[0407] In some embodiments, the receiving module 520 is further used by the UHR access point multilink logical entity to receive the buffered downlink data transmitted by the second access point multilink logical entity.

[0408] In some embodiments, the receiving module 520 is further used by the UHR access point multilink logical entity to receive the buffered downlink data transmitted by the first access point multilink logical entity, and the buffered downlink data is transferred by the second access point multilink logical entity to the first access point multilink logical entity.

[0409] In some embodiments, the receiving module 520 is further used to receive unicast key information of the UHR access point multilink logical entity from the UHR access point multilink logical entity, the unicast key information being determined based on the upper media access control UMAC address of the UHR access point multilink logical entity.

[0410] In some embodiments, the receiving module 520 is further used to receive multicast key information for one or more links of the first access point multilink logical entity from the UHR access point multilink logical entity, the multicast key information for one or more links is determined based on the lower media access control LMAC addresses of one or more of the first access point multilink logical entities.

[0411] In some embodiments, the receiving module 520 is further used 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.

[0412] In some embodiments, the sixth frame includes an ultra-high reliability UHR mobility domain element, which is used to indicate that the UHR access point multilink logical entity has seamless transition capabilities.

[0413] In some embodiments, the transmitting module 510 is further used to transmit a seventh frame to multiple access point multilink logical entities of the UHR access point multilink logical entity, and The receiving module 520 is further used to receive an eighth frame transmitted by multiple access point multilink logical entities of the UHR access point multilink logical entity, the eighth frame being used to determine the first access point multilink logical entity.

[0414] The non-access point device 500 may further include other modules to perform the communication methods of each of the above embodiments. Each of the above exemplary embodiments of the communication method, and any improvements, modifications, and variations obtained therefrom where a person skilled in the art would not exert creative effort, may be used to limit the non-access point device 500, and this application will not describe them further.

[0415] Embodiments of this application provide an access point multilink device including a processor and a transceiver. The processor is used to call a computer program and, in cooperation with the transceiver, to realize the actions performed by the access point multilink device in the embodiment of the above method.

[0416] Exemplary, Figure 27 is a block diagram of an access point multilink device according to an embodiment of the present 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 actions of the access point multilink device in the embodiment of the method under the control of the processor 601.

[0417] Selectively, the access point multilink device 600 further includes a memory 603, a communication bus 604, and a communication interface 605.

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

[0419] The communication bus 604 may include one passage and transmit information between the assemblies.

[0420] Memory 603 may be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions, random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions, electrically erasable programmable read-only memory (EEPROM), compactdisc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital multipurpose discs, Blu-ray discs, etc.), magnetic disks or other magnetic storage devices, or any other medium that can be used to carry or store expected program code having an instruction or data structure format and is accessible by a computer. Memory 603 may exist independently or be connected to processor 601 via communication bus 604. Memory 603 may be integrated with processor 601.

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

[0422] In a concrete implementation, one embodiment may include multiple processors in an access point multilink device. 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 a processing core for processing one or more devices, circuits, and / or data (e.g., computer program instructions).

[0423] In practical implementation, the access point multilink device may be a router or a switch, etc.

[0424] Selectively, the access point multilink device is an access point multilink device. Multiple APs included in the access point multilink device are independent of each other in the LMAC layer and PHY layer, and also independent of each other in the UMAC layer. Alternatively, multiple STAs included in the access point multilink device are independent of each other in the low MAC layer and PHY layer, and share the UMAC layer. The embodiments of this application are not limited to the internal structure of the access point multilink device. Exemplarily, the UMAC layer or the LMAC layer may both be implemented by one processor in the chip system of the access point multilink device, or they may each be implemented by different processors in the chip system.

[0425] Embodiments of this application provide a non-access point multilink device, which includes a processor and a transceiver. The processor is used to call a computer program and, in cooperation with the transceiver, to perform the actions that the non-access point multilink device in the embodiment of the above method performs.

[0426] Exemplary, Figure 28 is a block diagram of a non-access point multilink device according to an embodiment of the present 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 transmit and receive actions performed by the non-access point multilink device in the embodiment of the method under the control of the processor 701.

[0427] Selectively, the access point multilink device 700 further includes a memory 703, a communication bus 704, and a communication interface 705.

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

[0429] The communication bus 704 may include one passage and transmit information between the assemblies.

[0430] Memory 703 may be ROM or other types of static storage devices capable of storing static information and instructions, RAM or other types of dynamic storage devices capable of storing information and instructions, EEPROM, CD-ROM or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital multipurpose discs, Blu-ray discs, etc.), magnetic disks or other magnetic storage devices, or any other medium that can be used to carry or store expected program code having instruction or data structure format and is accessible by a computer. Memory 703 may exist independently or be connected to processor 701 via communication bus 704. Memory 703 may be integrated with processor 701.

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

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

[0433] In a concrete implementation, one embodiment may include a non-access point multilink device that comprises 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 a processing core for processing one or more devices, circuits, and / or data (e.g., computer program instructions).

[0434] In practical implementation, the non-access point multilink device may be a wireless terminal such as a mobile phone, computer, or smart wearable device.

[0435] Selectively, the non-access point multilink device is a non-access point multilink device. Multiple non-AP STAs included in the non-access point multilink device are independent of each other in the LMAC layer and PHY layer, and also independent of each other in the UMAC layer. Alternatively, multiple non-AP STAs included in the non-access point multilink device are independent of each other in the LMAC layer and PHY layer, and share a UMAC layer. The embodiments of this application do not limit the internal structure of the non-access point multilink device. Exemplarily, the high MAC layer or the low MAC layer may both be implemented by a single processor in the chip system of the non-access point multilink device, or they may each be implemented by different processors in the chip system.

[0436] It should be noted that the electronic device according to the embodiment of this application can implement all the method steps realized by the embodiment of the method and achieve the same technical effects, and the same parts and beneficial effects as those of the embodiment of the method will not be specifically described here.

[0437] Embodiments of this application further provide a computer-readable storage medium in which computer-executable instructions are stored, and the computer-executable instructions are used to cause a computer to execute the terminal roaming induction method in the above embodiment.

[0438] Embodiments of this application further provide a computer program product in which, when the computer program product is invoked by a computer, the computer is instructed to execute the terminal roaming guidance method in the above embodiment.

[0439] As those skilled in the art will see, embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application may take the form of complete hardware embodiments, complete software embodiments, or embodiments combining software and hardware. Furthermore, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, magnetic disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

[0440] This application is described with reference to flowcharts and / or block diagrams of the methods, apparatus (systems) and computer program products described herein. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and combinations of flows and / or blocks in the flowcharts and / or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, a dedicated computer, an embedded processor, or other programmable data processing device to generate a machine. The instructions executed by the processor of the computer or other programmable data processing device thereby generate an apparatus for implementing the functions specified in one or more flows in the flowchart and / or one or more blocks in the block diagram.

[0441] These computer program instructions may be stored in computer-readable memory that can operate a computer or other programmable data processing device in a specific manner. The instructions stored in the computer-readable memory generate a product including an instruction unit. This instruction unit implements the functions specified in one or more flows in a flowchart and / or one or more blocks in a block diagram.

[0442] These computer program instructions may be installed on a computer or other programmable data processing device. This allows a series of operational steps to be performed on the computer or other programmable device to generate processing realized by the computer. Thus, the instructions executed on the computer or other programmable device provide steps to realize a function specified in one or more flows in a flowchart, and / or one or more blocks in a block diagram.

Claims

1. A communication method in a wireless local area network, A highly reliable UHR access point multilink logical entity receives a second frame from a non-access point multilink logical entity to initiate a roaming request. The UHR access point multilink logical entity transmits a first frame to the non-access point multilink logical entity to instruct it to perform a roaming reconfiguration. The UHR access point multilink logical entity includes a first access point multilink logical entity and a second access point multilink logical entity. The second access point multilink logical entity is associated with the non-access point multilink logical entity, and is a communication method in a wireless local area network.

2. The transmission of a first frame by the UHR access point multilink logical entity to the non-access point multilink logical entity is: The method according to claim 1, wherein the UHR access point multilink logical entity transmits a first frame to the non-access point multilink logical entity by the first access point multilink logical entity or the second access point multilink logical entity.

3. The first frame includes first link identifier information for indicating the target link of the first access point multilink logical entity to which the non-access point multilink logical entity will be switched, and / or The method according to claim 1 or 2, wherein the second frame includes second link identifier information for indicating the link of the access point multilink logical entity that the non-access point multilink logical entity requests as a switching target.

4. The method according to claim 3, wherein the first link identifier information includes identifier information of the first access point multilink logical entity and link information of the target link.

5. The method according to claim 3 or 4, wherein the first frame further includes a first instruction for indicating the switching method of the target link.

6. The first instruction is used to instruct an immediate switch, or The method according to claim 5, wherein the first instruction is used to instruct a delay switch, and the first instruction is further used to instruct the delay time length of the delay switch.

7. The aforementioned ultra-high reliability UHR access point multilink logical entity receiving a second frame from a non-access point multilink logical entity means that The method according to any one of claims 1 to 6, wherein the UHR access point multilink logical entity receives a second frame by the first access point multilink logical entity or the second access point multilink logical entity.

8. Before the ultra-high reliability UHR access point multilink logical entity receives a second frame from a non-access point multilink logical entity, the method The UHR access point multilink logical entity further includes transmitting a third frame to the non-access point multilink logical entity. The third frame includes third link identifier information, The method according to any one of claims 1 to 7, wherein the third link identifier information is used by the UHR access point multilink logical entity to indicate a candidate access point multilink logical entity and / or candidate link proposed as a switching target for the non-access point multilink logical entity.

9. The third frame includes a candidate list field, The candidate list field includes at least one sub-element, The method according to claim 8, wherein the at least one sub-element corresponds to at least one candidate access point multilink 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 multilink logical entity.

10. The aforementioned sub-element is, A first field for indicating the address information of the candidate access point multilink logical entity, A second field for indicating whether the non-access point multilink logical entity proposes switching to all candidate links of the candidate access point multilink logical entity, The method according to claim 9, further comprising at least one of the following: a third field for indicating one or more candidate links of the candidate access point multilink logical entities proposed as a switching destination.

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

12. The method further includes determining, if a predetermined condition is met, that the UHR access point multilink logical entity has switched so that the target link of the non-access point multilink logical entity is already associated with the first access point multilink logical entity. The aforementioned pre-set conditions are: The UHR access point multilink logical entity has received a fourth frame from the non-access point multilink logical entity, wherein the fourth frame includes fourth link identifier information, and the fourth link identifier information corresponds to the first link identifier information in the first frame, or The method according to any one of claims 1 to 11, comprising at least one of the following: the UHR access point multilink logical entity transmits the first frame and a predetermined amount of time has elapsed.

13. After 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, the method further includes the UHR access point multilink logical entity transmitting a fifth frame to the non-access point multilink logical entity, wherein the fifth frame includes fifth link identifier information. The method according to any one of claims 1 to 12, wherein the fifth link identifier information is used to instruct one or more remaining links of the non-access point multilink logical entity to be switched to associate with the first access point multilink 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 multilink logical entity and the second access point multilink logical entity.

14. After the target link of the non-access point multilink logical entity is switched to be associated with the first access point multilink logical entity, the method The method according to any one of claims 1 to 13, further comprising the UHR access point multilink logical entity transmitting buffered downlink data, which is downlink data already buffered on the target link before switching, to the non-access point multilink logical entity.

15. The UHR access point multilink logical entity transmits buffered downlink data to the non-access point multilink logical entity. The method according to claim 14, wherein the UHR access point multilink logical entity transmits the buffered downlink data to the non-access point multilink logical entity by the second access point multilink logical entity.

16. The UHR access point multilink logical entity transmits buffered downlink data to the non-access point multilink logical entity. The second access point multilink logical entity transmits the buffered downlink data to the first access point multilink logical entity. The method according to claim 14 or 15, further comprising the first access point multilink logical entity transmitting the buffered downlink data to the non-access point multilink logical entity.

17. The method according to any one of claims 1 to 16, further comprising the UHR access point multilink logical entity determining unicast key information of the UHR access point multilink logical entity based on the upper media access control UMAC address of the UHR access point multilink logical entity.

18. The UHR access point multilink logical entity shares, copies, or transmits its unicast key information to the first access point multilink logical entity, or The method according to claim 17, further comprising at least one of the following: the UHR access point multilink logical entity transmits the unicast key information of the UHR access point multilink logical entity to the non-access point multilink logical entity.

19. The method according to any one of claims 1 to 18, further comprising the UHR access point multilink logical entity determining multicast key information for one or more links of the first access point multilink logical entity based on the lower media access control LMAC addresses of one or more of the first access point multilink logical entities.

20. The aforementioned method, The method according to claim 19, further comprising the UHR access point multilink logical entity transmitting multicast key information for one or more links of the first access point multilink logical entity to the non-access point multilink logical entity.

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

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

23. Multiple access point multilink logical entities of the UHR access point multilink logical entity receive a seventh frame transmitted by the non-access point multilink logical entity, The further includes that a plurality of access point multilink logical entities of the UHR access point multilink logical entity transmit an eighth frame in response to the seventh frame to the non-access point multilink logical entity, The method according to any one of claims 1 to 22, wherein the eighth frame is used to determine the first access point multilink logical entity.

24. A communication method in a wireless local area network, A non-access point multilink logical entity sends a second frame to a highly reliable UHR access point multilink logical entity to initiate a roaming request. The non-access point multilink logical entity includes receiving a first frame from the UHR access point multilink logical entity for instructing roaming reconfiguration, A method of communication in a wireless local area network, wherein the UHR access point multilink logical entity includes a first access point multilink logical entity and a second access point multilink logical entity, the second access point multilink logical entity being associated with the non-access point multilink logical entity.

25. The non-access point multilink logical entity receiving the first frame from the UHR access point multilink logical entity means that The method according to claim 24, wherein the non-access point multilink logical entity receives a first frame transmitted from the first access point multilink logical entity or the second access point multilink logical entity of the UHR access point multilink logical entity.

26. The first frame includes first link identifier information for indicating the target link of the first access point multilink logical entity to which the non-access point multilink logical entity will be switched, and / or The method according to claim 24 or 25, wherein the second frame includes second link identifier information for indicating the link of the access point multilink logical entity that the non-access point multilink logical entity requests as a switch-to.

27. The method according to claim 26, wherein the first link identifier information includes identifier information of the first access point multilink logical entity and link information of the target link.

28. The method according to claim 26 or 27, wherein the first frame further includes a first instruction for indicating the switching method of the target link.

29. The method according to claim 28, wherein the first instruction is used to instruct an immediate switchover, or the first instruction is used to instruct a delayed switchover, and the first instruction is further used to instruct the delay time length of the delayed switchover.

30. The transmission of a second frame by the aforementioned non-access point multilink logical entity to the ultra-high reliability UHR access point multilink logical entity is: The method according to any one of claims 24 to 29, wherein the non-access point multilink logical entity transmits a second frame to the first access point multilink logical entity or the second access point multilink logical entity of the UHR access point multilink logical entity.

31. The method according to claim 26, wherein the link between the access point multilink logical entity and the access point multilink logical entity indicated by the second link identifier information is determined based on the signal quality of the downlink signal of at least one access point multilink logical entity belonging to the UHR access point multilink logical entity.

32. Before the non-access point multilink logical entity transmits a second frame to the ultra-high reliability UHR access point multilink logical entity, the method The non-access point multilink logical entity further includes receiving a third frame from the UHR access point multilink logical entity, The third frame includes third link identifier information, The method according to any one of claims 24 to 31, wherein the third link identifier information is used by the UHR access point multilink logical entity to indicate a candidate access point multilink logical entity and / or candidate link proposed as a switching target for the non-access point multilink logical entity.

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

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

35. After 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, the method The non-access point multilink logical entity further includes receiving a fifth frame from the UHR access point multilink logical entity, which includes fifth link identifier information. The method according to any one of claims 24 to 34, wherein the fifth link identifier information is used to instruct one or more remaining links of the non-access point multilink logical entity to be switched to be associated with the first access point multilink 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 multilink logical entity and the second access point multilink logical entity.

36. After 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, the method The method according to any one of claims 24 to 35, wherein the non-access point multilink logical entity receives buffered downlink data from the UHR access point multilink logical entity, further comprising the buffered downlink data being downlink data already buffered on the target link before the switchover.

37. The non-access point multilink logical entity receiving buffered downlink data from the UHR access point multilink logical entity means that The method according to claim 36, wherein the non-access point multilink logical entity receives the buffered downlink data transmitted by the second access point multilink logical entity by the UHR access point multilink logical entity.

38. The non-access point multilink logical entity receiving buffered downlink data from the UHR access point multilink logical entity includes the non-access point multilink logical entity receiving the buffered downlink data transmitted by the first access point multilink logical entity by the UHR access point multilink logical entity, The method according to claim 36 or 37, wherein the buffered downlink data is transferred to the first access point multilink logical entity by the second access point multilink logical entity.

39. The non-access point multilink logical entity further includes receiving unicast key information of the UHR access point multilink logical entity from the UHR access point multilink logical entity, The method according to any one of claims 24 to 38, wherein the unicast key information is determined based on the upper media access control UMAC address of the UHR access point multilink logical entity.

40. The non-access point multilink logical entity further includes receiving multicast key information for one or more links of the first access point multilink logical entity from the UHR access point multilink logical entity. The method according to any one of claims 24 to 39, wherein the multicast key information for one or more links is determined based on one or more lower media access control LMAC addresses of the first access point multilink logical entities.

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

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

43. The non-access point multilink logical entity transmits a seventh frame to multiple access point multilink logical entities of the UHR access point multilink logical entity, The method according to any one of claims 24 to 42, further comprising the non-access point multilink logical entity receiving an eighth frame transmitted by a plurality of 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.

44. An access point device, A receive module for receiving a second frame from a non-access point multilink logical entity to initiate a roaming request, It includes a transmit module for sending a first frame to a non-access point multilink logical entity to instruct it to roam reconfigure, The access point device includes a first access point multilink logical entity and a second access point multilink logical entity. The second access point multilink logical entity is an access point device associated with the non-access point multilink logical entity.

45. Non-access point device, A transmit module for sending a second frame to initiate a roaming request to a super-high reliability UHR access point multilink logical entity, Includes a receiving module for receiving a first frame from the UHR access point multilink logical entity for instructing roaming reconfiguration, The UHR access point multilink logical entity includes a first access point multilink logical entity and a second access point multilink logical entity. The aforementioned second access point multilink logical entity is a non-access point device associated with the aforementioned non-access point device.

46. Access point multilink equipment, Including the processor and memory, An access point multilink device, wherein the memory is used to store computer programs, and the processor is used to call and execute computer programs stored in the memory and to perform the method according to any one of claims 1 to 23.

47. Non-access point multilink equipment, Including the processor and memory, A non-access point multilink device, wherein the memory is used to store computer programs, and the processor is used to call and execute computer programs stored in the memory and to perform the method according to any one of claims 24 to 43.

48. It's a tip, A chip comprising a processor that causes a device on which the chip is mounted to perform the method according to any one of claims 1 to 23 or the method according to any one of claims 24 to 43 by calling and executing a computer program from memory.

49. A computer-readable storage medium, A computer-readable storage medium used for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 23 or the method according to any one of claims 24 to 43.