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

Abstract

The invention discloses a communication method, device, equipment and system in a wireless network. The method is applied to a non-co-located control module of an ultra-high reliability (UHR) non-co-located access point multi-link logic entity, and comprises the following steps: the non-co-located control module indicates to send a first frame to a non-access point multi-link logic entity (Non-AP Multi-link logic entity), the first frame comprises first link identification information, the first link identification information comprises first link identification information, and the second link identification information comprises second link identification information; the first link identification information indicates that the non-access point multi-link logic entity is to be switched to one or more links with a first access point multi-link logic entity.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a communication method, device, equipment and system in a wireless local area network (WLAN). Background Art

[0002] 802.11be network, also known as Extremely High Throughput (EHT) network, achieves extremely high throughput through a series of system features and multiple mechanisms to enhance functions. In 802.11be network, wireless devices can support multi-link communication. A wireless device supports multi-link communication, which means that the wireless device supports communication on multiple frequency bands at the same time, or communicates on different channels of the same frequency band at the same time. A wireless device that supports multi-link communication is usually called a multi-link device (MLD). MLD has one or more stations (STA).

[0003] Currently, multi-link devices in WLAN are divided into two categories: access point (AP) multi-link devices and non-AP multi-link devices. The STA in the non-AP MLD is a non-AP STA. One or more links can be established between a non-AP multi-link device and an access point multi-link device, that is, associated links are formed. Each associated link connects a non-AP STA in the non-AP multi-link device and an AP in the access point multi-link device.

[0004] AP, non-AP STA and MLD have corresponding upper media access control (UMAC) respectively. When the APs attached to an AP MLD are co-located with each other, the AP MLD is a co-located AP MLD, otherwise, the AP MLD is a non-co-located AP MLD. The upper media access control (UMAC) of a non-co-located AP MLD and the corresponding lower media access control (LMAC) are also non-co-located.

[0005] Figure 1 An exemplary architecture diagram of an ultra high reliability (UHR) AP MLD is shown. In this example, the UHR AP MLD includes N EHT AP MLDs and UHR AP MLD UMACs that are independently connected to the N EHT AP MLDs for communication.

[0006] As shown in the figure, EHT AP MLD 1 includes N APs (AP 0 to AP N as shown in the figure), and the N APs can be associated with multiple links (Link 0 to Link N as shown in the figure). The N APs are respectively connected to the corresponding N LMACs for communication, and converge on the TID (Traffic Identifier)-to-Link mapping / Link merging (TID-to-Lin mapping / Link meraing) module. The TID-to-Link mapping / Link merging module communicates with the UMAC backhaul of the UHR AP MLD. The UHR APMLD UMAC controls and manages the link communications of EHTAP MLD 1 to EHTAP MLD N. Summary of the invention

[0007] Various exemplary embodiments of the present application provide a communication method, apparatus, device, system and storage medium in a wireless network.

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

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

[0010] In one embodiment, before the non-co-site control module instructs the first frame to be sent to the non-access point multi-link logical entity, the method also includes: the non-co-site control module instructs the second access point multi-link logical entity to disconnect the association with the one or more links, and the first access point multi-link logical entity to associate with the one or more links.

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

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

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

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

[0015] In one embodiment, the first frame further includes a second indication, where the second indication indicates whether the non-co-located control module has completed the operation requested by the second frame.

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

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

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

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

[0020] In one embodiment, the preset condition includes: the non-co-location control module indicates that a preset time has passed after the first frame is sent.

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

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

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

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

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

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

[0027] In one embodiment, after the non-co-site control module confirms that the one or more links of the non-access point multi-link logical entity have been switched to be associated with the first access point multi-link logical entity, the method also includes: the non-co-site control module shares or copies the first key information used for the UHR non-co-site access point multi-link logical entity to the first access point multi-link logical entity for use in the associated links of the first access point multi-link logical entity.

[0028] In one embodiment, the first key information is based on an upper media access control (UMAC) address of the non-co-located control module.

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

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

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

[0032] In one embodiment, before the non-co-site control module receives the second frame from the non-access point multi-link logical entity, the method also includes: the non-co-site control template sends a fifth frame to the non-access point multi-link logical entity, wherein the fifth frame is configured to request the non-access point multi-link logical entity to send the second frame.

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

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

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

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

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

[0038] In one embodiment, the method also includes: determining the multicast key information for the one or more links of the first access point multi-link logical entity based on the corresponding lower media access control (LMAC) address of the first access point multi-link logical entity; and the non-co-location control module instructs the multicast key information to be sent to the non-access point multi-link logical entity.

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

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

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

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

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

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

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

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

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

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

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

[0050] In one embodiment, the method also includes: the non-access point multi-link logical entity sends a seventh frame on multiple links associated with the UHR non-co-located access point multi-link logical entity respectively; the non-access point multi-link logical entity receives multiple eighth frames from the UHR non-co-located access point multi-link logical entity in response to the seventh frame; and the non-access point multi-link logical entity determines the one or more links of the first access point multi-link logical entity based on the multiple eighth frames.

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

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

[0053] In one embodiment, the method further includes: the non-access point multi-link logical entity receives a sixth frame from the UHR non-co-located access point multi-contact logical entity, wherein the sixth frame includes a UHR mobility domain element, and the UHR mobility domain element indicates a seamless roaming capability of the UHR non-co-located access point multi-link logical entity.

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

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

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

[0057] In one embodiment, the first indication field also includes a STA control field.

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

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

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

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

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

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

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

[0065] In one embodiment, the UHR mobility domain field reuses 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, including: a sending module configured to send a first frame to a non-access point multi-link logical entity (Non-AP Multi-link logical entity), wherein the first frame includes first link identification information, and the first link identification information indicates that the non-access point multi-link logical entity is to be switched to one or more links associated with the first access point multi-link logical entity.

[0066] Each embodiment of the present application provides a non-access point device, including: a sending module, configured to send a second frame to the UHR non-co-located access point multi-link logical entity, the second frame including second link identification information, wherein the second link identification information indicates that the non-access point multi-link logical entity is to be switched to one or more links associated with the first access point multi-link logical entity.

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

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

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

[0070] Each exemplary embodiment of the present application provides a computer-readable storage medium, on which instructions are stored. When the instructions are executed by a processor, the processor executes the communication method in a wireless network provided by each of the above embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0072] Figure 1 A network architecture diagram of an application environment of a communication method in a wireless network provided in an embodiment of the present application is shown.

[0073] Figure 2 A schematic diagram of an application scenario of a communication method in a wireless network provided in an embodiment of the present application is shown.

[0074] Figure 3 A schematic diagram of the structure of the mobility domain element field provided in an embodiment of the present application is shown.

[0075] Figure 4 A schematic diagram of the structure of the seamless roaming capability field of the mobility domain element field provided in an embodiment of the present application is shown.

[0076] Figure 5 A schematic diagram of frame structure expansion of the mobility domain element field provided in an embodiment of the present application is shown.

[0077] Figure 6 A structural diagram of a Basic Service Set (BSS) transition management (BTM) roaming frame (Roaming frame) provided in an embodiment of the present application is shown.

[0078] Figure 7 A schematic diagram showing the values ​​of the Action subfield of the BTM roaming frame provided in an embodiment of the present application and their functional correspondence is shown.

[0079] Figure 8A schematic diagram of the structure of the Common Info subfield of the BTM roaming frame provided in an embodiment of the present application is shown.

[0080] Fig. 9 A flow chart of the access procedure of the communication method provided in the embodiment of the present application is shown.

[0081] Fig.10 A flow chart showing a network access process of the communication method provided in an embodiment of the present application is shown.

[0082] Fig.11 A schematic diagram of the structure of the KDE field of the key information of the multicast key in the communication method provided in an embodiment of the present application is shown.

[0083] Fig.12 A schematic diagram of the structure of the FTE field of the Fast Transition protocol of the key information of the multicast key in the communication method provided in an embodiment of the present application is shown.

[0084] Fig.13 A flow chart of a communication method in a wireless network provided in an embodiment of the present application is shown.

[0085] Fig.14 A partial flow chart of a seamless roaming process in a communication method provided in an embodiment of the present application is shown.

[0086] Fig.15 Shows Fig.14 The remaining process diagram of the seamless roaming process in the communication method is shown.

[0087] Fig.16 A flow chart of a seamless roaming process of a communication method provided in another embodiment of the present application is shown.

[0088] Fig.17 A flow chart showing a seamless roaming process of a communication method according to another embodiment of the present application is shown.

[0089] Fig.18 The BTM request frame format of the seamless roaming process of another embodiment of the present application and the structure of the neighbor report element (Neighbor Report element) in the BSS transition candidate table field are shown.

[0090] Fig.19 The format of the BSS transition candidate preference sub-element of the BSS transition candidate entry field according to another embodiment of the present application is shown.

[0091] Fig. 20The Basic Multi-Link Element structure of the BSS transition candidate entry field of another embodiment of the present application is shown.

[0092] Fig.21 A flow chart showing a seamless roaming process of a communication method according to another embodiment of the present application is shown.

[0093] Fig. 22 The ST capability field format of the UHR mobility domain element of the network entry process according to another embodiment of the present application is shown.

[0094] Fig.23 The value of the seamless BSS transition mode (Seamless BSS Transition Mode) of the ST capability field of another embodiment of the present application and its corresponding meaning are shown.

[0095] Fig.24 A schematic diagram of the internal structure of an access point device provided in an embodiment of the present application is shown.

[0096] Fig.25 A schematic diagram of the internal structure of a non-access point device provided in an embodiment of the present application is shown.

[0097] Fig.26 A block diagram of an access point multi-link device provided in an embodiment of the present application is shown.

[0098] Fig. 27 A block diagram of an access point multi-link device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0099] Although the present invention allows for various forms of embodiments, embodiments of the present invention including preferred embodiments are shown in the accompanying drawings to be described in detail herein, and it should be understood that the contents disclosed herein will be considered as explanations of the principles of the present invention, and are not intended to limit the broad aspects of the present invention to one or more embodiments shown or disclosed. As used herein, the term "present invention" is not intended to limit the scope of the claimed invention, but is a term used to discuss exemplary embodiments for the purpose of explanation only.

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

[0101] The terms "first" and "second" in the specification and claims of this application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any variation thereof are intended to cover non-exclusive protection. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally includes steps or units that are not listed, or optionally includes other steps or units inherent to these processes, methods, products or devices.

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

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

[0104] In traditional Wi-Fi technology, the normal roaming function is used to switch between mobile devices and different AP connections when a mobile device (or device terminal) moves from the coverage area of ​​one AP to the coverage area of ​​another AP to ensure the Internet access performance of the mobile terminal. However, when using normal roaming, when a mobile device moves from one AP to the range of another AP, it is necessary to manually reconnect to the new AP. This roaming method requires the user to manually disconnect the current connection, re-search for available Wi-Fi networks, and manually select a new AP to connect. This roaming method may cause connection interruption, data transmission reliability and user experience to decrease.

[0105] Therefore, the traditional technology provides the Fast Transition (FT) roaming technology. FT roaming technology is a fast Wi-Fi roaming technology, also known as 802.11r. It can embed the 4-way key handshake process with the target AP into the reassociation process when the mobile device moves from one wireless access point (AP) to another AP, thereby achieving the purpose of fast AP switching.

[0106] However, whether it is common roaming or FT roaming, the following problems may occur when switching APs:

[0107] 1. When the mobile terminal switches APs, there will be more frame overhead and link authentication (Authe), that is, 802.1X Extensible Authentication Protocol (EAP) authentication and the 4-way handshake roaming switching process will have a long delay.

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

[0109] Each exemplary embodiment of the present application provides a communication method in a wireless network. The method is applicable to Figure 1 The non-co-located UHR AP MLD architecture shown in the figure is applicable to Figure 2 The application scenario shown.

[0110] like Figure 1 As shown, the LMAC (e.g., UHR AP MLD LMAC) of non-co-located EHT AP MLD 1 and EHT AP MLD N is connected to the UHR AP MLD UMAC communication via wired or wireless backhaul. The UHR AP MLD UMAC includes a UHR APMLD UMAC controller, which manages the EHT AP MLD attached to the UHR AP MLD, including the association management of the links between the non-AP STA MLD and the EHTAP MLD attached to the UHR AP MLD.

[0111] In this architecture, UHR AP MLD UMAC is different from UHR AP MLD LMAC.

[0112] It can be understood that, in other embodiments, the UHR AP MLD may also include more than two EHT AP MLDs, such as 3 or 4, and this application does not specifically limit this.

[0113] UHR AP MLD UMAC is a logical entity, that is, it can be in the form of a software function module, or in the form of a hardware unit, or it can be a combination of the two. In addition, UHR AP MLD UMAC can be a logical entity in an independent device, or it can be integrated in a device of EHT AP MLD attached to UHR AP MLD UMAC, for example, it can be integrated in the device of EHTAP MLD1, and this application does not specifically limit this.

[0114] exist Figure 1 In the illustrated embodiment, EHT AP MLD1 and EHT AP MLD N both include EHT AP MLD UMAC, and each EHT AP MLD UMAC is directly connected to the distributed system (DS). It can be understood that EHT AP MLD UMAC may not be set for UHR AP MLD. The EHT AP MLD UMACs of the EHT AP MLDs attached to the UHR AP MLD are different from each other. Optionally, the UHR AP MLD UMAC may be the same as one of the EHT AP MLD UMACs. Alternatively, the UHR AP MLD UMAC is different from the EHT AP MLD UMAC.

[0115] like Figure 2 As shown, the scenario includes a terminal device 201 and an AP 202, wherein the AP 202 includes three APs. It should be noted that the number of APs involved in the AP 202 is not limited. Figure 2 Only three APs are described. Figure 2 The APs shown may be non-co-located multi-link access logical entities, which are all attached to the UHR non-co-located multi-link logical entity.

[0116] AP 202 forms an AP wireless network environment 203 with three APs. When the terminal device 201 enters the AP wireless network environment 203, seamless roaming can be performed.

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

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

[0119] To this end, each exemplary embodiment of the present application introduces a BTM seamless roaming frame and adds a field to the frame existing in 802.11be. Figures 3 to 8 These introduced frames and fields are introduced.

[0120] Figure 3 A schematic structural diagram of a UHR mobility domain element (Mobility Domain element) field provided in an embodiment of the present application is shown.

[0121] The UHR mobility domain element field (or mobility domain element field) is used to declare seamless transition capability (Seamless Transition Capability) or seamless roaming capability (Seamless Roaming Capability), including the Seamless Transition Capability (Seamless Transition Capability) field.

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

[0123] Optionally, the mobility domain element further includes an element identification (Element ID) field and / or a length (Length) field, both of which have been defined in the 802.11 standard and are not described in detail here.

[0124] Optionally, the mobility domain element further includes a mobility domain identification (Mobility Domain ID, MDID) field, and the MDID field is used to identify the UHR roaming mobility domain.

[0125] The UHR mobility domain element field can be attached to the frame sent by the AP MLD (or AP) or the frame sent by the non-AP MLD (or non-AP STA). These frames can be frames defined in 802.11 or newly defined frames.

[0126] Specifically, the UHR mobility domain element field can be attached to the Beacon Frame, Probe Response Frame, Association Request Frame, Association Response Frame, and Authentication Frame from the UHR AP MLD (or AP) to declare the seamless transition capability of the UHR AP MLD (for example, to a non-access point multi-link device). The extended structure of these frames will be further described below.

[0127] The mobility domain element field may also be attached to the frame from the non-AP STA MLD. When the mobility domain element field is attached to the frame from the non-AP STA MLD, the mobility domain element field indicates the seamless transition capability of the non-AP STA MLD (or non-APSTA), that is, the seamless roaming capability.

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

[0129] Alternatively, the UHR mobility domain element field may also reuse or extend the existing fields in the above frames.

[0130] For example, the UHR mobility domain element field can extend and reuse the FT Capability and Policy subfield in the Mobility Domain Information element (MDIE) field in the 802.11r protocol. Specifically, the UHR mobility domain element field can reuse the reserved field in the FT Capability and Policy subfield.

[0131] Figure 4 A structural diagram of the seamless roaming capability (STCapability) field of the mobility domain element field provided in an embodiment of the present application is shown.

[0132] The Seamless Roaming Capability field is used to declare the seamless roaming capability of an AP or non-AP STA that can perform seamless BSS transition.

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

[0134] Specifically, in one embodiment, when the AP MLD has seamless roaming capability, the seamless basic service set transition state subfield is set to 1, otherwise it is set to 0. Of course, more bits can also be used to indicate the seamless basic service set transition state / mode, for example, 2 bits can be used to identify 4 seamless basic service set transition states / modes, which is not limited in the embodiments of the present application.

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

[0136] Figure 5 A structural diagram of a frame structure extension field of a mobility domain element field provided in an embodiment of the present application is shown.

[0137] As described above, the UHR Mobility Domain Element field can be attached to the Beacon Frame, Probe Response Frame, Association Request Frame, Association Response Frame, and Authentication Frame from the UHR AP MLD (or AP) to declare the seamless transition capability of the UHR AP MLD (for example, to a non-access point multi-link device), or vice versa.

[0138] exist Figure 5 In the illustrated embodiment, when the value of the "dotllSeamlessBSSTransition Activated" field is true, the UHR mobility domain element field may be present at the end of the above-mentioned frames, that is, the UHR mobility domain element field is added to the reserved fields at the end of these frames, or extended after the end of these reserved fields.

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

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

[0141] Figure 6A structural diagram of a Basic Service Set (BSS) transition management (BTM) roaming frame (Roaming trame) provided in an embodiment of the present application is shown.

[0142] In order to achieve seamless roaming in a non-co-located UHR access point multi-link logical entity (e.g., non-co-located UHR AP MLD) environment, a BTM roaming frame is introduced for roaming message exchange between the non-access point multi-link logical entity (e.g., non-AP STA MLD) and the non-co-located UHR AP MLD. The roaming message may include a BTM roaming request (e.g., a BTM roaming request frame sent from the non-AP STAMLD to the non-co-located UHR AP MLD), a roaming link switching indication (e.g., a BTM roaming reconfiguration frame sent from the non-co-located UHRAP MLD to the non-AP STA MLD), and a roaming link switching confirmation (e.g., a BTM roaming confirmation frame sent from the non-APSTA MLD to the non-co-located UHR AP MLD).

[0143] The BTM roaming frame may include an action field, and the byte length of the action field may be 1 octet, or more, such as 2 octets, 5 octets, or 10 octets.

[0144] like Figure 6 As shown, the BTM roaming frame may additionally include a Category field.

[0145] The Category field is already defined in the existing 802.11 standard. For example, when the Category field is set to 10, the BTM roaming frame will be applicable to Wireless Network Management (WNM).

[0146] Optionally, the BTM roaming frame further includes a Dialog Token field. The Dialog Token field can be used to identify the frame type. For example, the Dialog Token field can be a non-zero value taken by the STA sending the BTM roaming frame to identify the frame type as a request frame type or a response frame type.

[0147] Figure 7 A schematic diagram showing the values ​​of the action field of the BTM roaming frame provided in an embodiment of the present application and their functional correspondence is shown.

[0148] The type of the BTM roaming frame may be based on the value of the action field. That is, the type of the BTM roaming frame may be different depending on the value of the action field.

[0149] For example, when the action field takes a value of 28, the BTM roaming frame may be a BTM roaming request (Roaming Request) frame type.

[0150] When the action field value is 29, the BTM roaming frame may be a BTM roaming reconfigure frame type.

[0151] When the action field value is 30, the BTM roaming frame may be a BTM roaming confirmation (Roaming Confirm) frame type.

[0152] In other embodiments, the BTM roaming request frame, the BTM roaming reconfiguration frame and the BTM roaming confirmation frame may be defined separately, instead of distinguishing the frame types through the action field in the BTM roaming frame.

[0153] The BTM roaming frame also includes a common information field.

[0154] Figure 8 A schematic diagram of the structure of the Common Info field of the BTM roaming frame provided in an embodiment of the present application is shown.

[0155] When the value in the action field is different, that is, when the type of the BTM roaming frame is different (additionally or alternatively, it also means that the transmitting and receiving ends of the frame are different), correspondingly, the roaming information carried by the common information field is also different.

[0156] The common information field of the BTM roaming frame includes at least the MLD AP ID field and the Links Info field. The MLD AP ID field can be used to indicate the AP MLD to which the seamless roaming process is expected to switch, and the Links Info field is used to indicate the link to be switched.

[0157] Additionally, the common information field may further include a length field indicating a field length of the common information field excluding the length field.

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

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

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

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

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

[0163] The Link Information field indicates information about the target handover link, i.e., the link information of the link that the non-AP MLD is expected to disconnect from the original MLD AP and associate with the new MLD AP. The length of the Link Information field is variable, which depends on the number of target handover links in the Link Information field. Therefore, the length of the Common Information field is also variable.

[0164] As shown in the figure, additionally, the link information field may include a link quantity (Link Num) field and one or more link identification information (Link ID Info) fields. The link quantity field indicates the number of links requested to be switched (or called requested to be disconnected). The link identification information field indicates the link identification of the link requested to be switched. Additionally, the link information field may also indicate the switching order of the one or more link identifications indicated by the one or more link identification information fields.

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

[0166] As shown in the figure, additionally, the above STA control field may include a Link Del Mode field. The length of the Link Del Mode field may be 8 bits. In other embodiments, the length of the Link Del Mode field may also be other values, such as 4 bits, 12 bits, or 16 bits.

[0167] The link deletion mode field can indicate the deletion method of the deleted link. For example, when the link deletion mode field is 1 bit, when the link deletion mode field is set to 0, the requested link can be deleted (or disconnected) immediately. When the link deletion mode field is set to 1, the requested link can be deleted after waiting for a specified period of time.

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

[0169] Additionally or alternatively, the STA control field may also include a Link Del Count field. The Link Del Count field may indicate that after receiving the corresponding frame, the requested link is deleted after waiting for a specified number of time units (TU). The Link Del Count field may also indicate other physical quantities to control the waiting time for deleting the requested link. The length of the Link Del Count field may be 8 bits. In other embodiments, the length of the Link Del Count field may also be other values, for example, 4 bits, 12 bits, or 16 bits.

[0170] Fig. 9 A flow chart of the access process of the communication method provided in the embodiment of the present application is shown.

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

[0172] Specifically, the PTK can be shared with multiple APMLDs of the UHR AP MLD after it is generated in the generation phase of the network access process. Alternatively, the PTK can be stored in the UHR AP MLD UMAC after it is generated in the generation phase of the network access process, and shared with the designated AP MLD under the control of the UHR AP MLD UMAC in the seamless roaming process.

[0173] In addition, multicast keys (e.g., group temporary key (GTK), integrated group temporary key (IGTK), and Beacon integrated group temporary key (BIGTK)) are calculated based on the EHT AP MLD LMAC address corresponding to each link of the AP MLD attached to the UHR AP MLD (i.e., the corresponding LMAC address of the UHR AP MLD, or the LMAC address of the corresponding EHT AP MLD).

[0174] The UHR AP MLD calculates and sends these multicast keys or instructs them to be sent to the corresponding non-AP STA MLD, which stores these multicast keys. These multicast keys can be calculated by the UHR AP MLD UMAC and sent by the UHR AP MLD UMAC, or calculated by the EHT AP MLD UMAC to which the EHT AP MLD belongs and directly sent by the EHTAP MLD to the corresponding non-AP STA MLD, or first sent back to the UHR AP MLD UMAC and then sent to the corresponding non-AP STA MLD through the UHR AP MLD UMAC.

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

[0176] Additionally or alternatively, when a non-AP STA MLD is before or during seamless roaming, the UHAP MLD sends a multicast key or indicates it to the non-AP STA MLD.

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

[0178] Based on the above-mentioned design of unicast key and multicast key, in the non-co-located UHR AP MLD architecture, during the seamless roaming process when the non-APSTA MLD switches from MLD1 to MLD2, when the non-AP STA MLD switches to the new AP MLD, there is no need to re-authenticate, re-associate and perform 4-way handshake on the key, thereby shortening the frame overhead of seamless roaming and reducing the roaming authentication delay caused by the FT roaming mechanism.

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

[0180] Fig.10 A flow chart showing a network access process of a communication method provided in yet another embodiment of the present application is shown.

[0181] Step S1500, after the Non-AP STA is powered on, it first enters the passive scanning mode and listens to beacon information under the supported Link. The Non-AP STA then enters the active scanning mode and actively sends ordinary probe request detection frames under each Link. The UHR AP MLD receives the ordinary probe request detection frame and feeds back an ordinary probe response by controlling the EHT AP MLD LMAC. The sending and receiving addresses of ordinary frames are set to the Link binding address to avoid confusion with other Links to the frequency point. Therefore, the TA of the frame is filled in with the Link Mac Address of the EHT AP MLD LMAC, and the RA is filled in with the Link Mac Address of the Non-AP STA.

[0182] Step S1510: After the Non-AP STA completes the scan, it integrates all the scan results and selects the best link to initiate Multi-Link access.

[0183] Step S1520: Send a Multi-Link Probe Request frame, where Addr1 and Addr3 in the Probe Request frame are filled with the Link Mac Address of the optimal EHT AP MLD selected after scanning, and the information of other links is carried on the STA Control in LinkInfo.

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

[0185] Step S1540: The Non-AP STA MLD initiates a Multi-Link Authen Request, and carries other link information associated with the request.

[0186] Step S1550 , the UHR AP MLD replies with a multi-link Authen Response on the received Link.

[0187] Step S1560: The non-AP STA MLD initiates a Multi-Link Assoc Request and carries other link information.

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

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

[0190] In step S1590, the non-AP STA MLD and the UHR AP MLD perform a 4-way handshake key negotiation on the current link, wherein the PTK is calculated according to the UHR AP MLD address, the GTK\IGTK\BIGTK is calculated according to the EHT AP MLD Link Address, and the GTK\IGTK\BIGTK of the LINK under all EHT AP MLDs belonging to the same UHR AP MLD is sent to the non-AP STA MLD.

[0191] Fig.11 A schematic diagram of the structure of the KDE field of the key information of the multicast key in the communication method provided in an embodiment of the present application is shown.

[0192] For each associated Link, the broadcasts interacting between the UHR AP MLD and the non-AP STA MLD use different GTK\IGTK\BIGTK, that is, the multicast key is designed and calculated at the link level, and the GTK\IGTK\BIGTK is calculated by the Low MAC address of each Link on the AP side.

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

[0194] Fig.12 A schematic diagram of the structure of the FTE field of the Fast Transition (FT) protocol of the key information of the multicast key in the communication method provided in an embodiment of the present application is shown.

[0195] Similarly, in order to ensure the execution of the 4-step handshake in the network access process, this embodiment similarly extends the FTE field of the FT protocol, that is, adds an AP MLD identification field to the MLO GTK sub-element, the MLO IGTK sub-element, and the MLO BIGTK sub-element. The AP MLD identification field is combined with the link identification information (Link ID Info) field to distinguish the same-frequency links of different AP MLDs.

[0196] Fig.13 A flow chart of a communication method in a wireless network provided in an embodiment of the present application is shown.

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

[0198] It is understandable that Link0 and Link1 have different frequency bands or different channels of the same frequency band. For example, the frequency band of Link0 may be 2.4 GHz, 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 associated with the UHR AP MLD and the STA MLD, and its frequency band may be, for example, 6 GHz.

[0199] Combination Fig.13 In the seamless roaming application scenario of this embodiment, the STA MLD determines that it needs to roam from MLD1 to MLD2 due to the movement of the location. The communication method of seamless roaming includes the following steps.

[0200] Step S900: receiving a second frame from the STA MLD.

[0201] Optionally, the second frame may be a BTM Roaming Request frame. The BTM Roaming Request frame includes indication information, where the indication information indicates the AP MLD to be switched to and the link to be switched.

[0202] Optionally, the BTM roaming request frame may further include a mobility field element to indicate whether the non-AP STA MLD has UHR seamless roaming capability.

[0203] Step S910: the link to be switched is switched from MLD1 to MLD2.

[0204] Specifically, switching the link to be switched, which is associated with MLD1 and non-AP STA MLD, from MLD1 to MLD2 means switching the link originally associated with MLD1 of UHR AP MLD and non-AP STA MLD to the same-frequency or same-channel link associated with MLD2 of UHR AP MLD and non-AP STA MLD.

[0205] Optionally, step S910 may specifically include the following steps.

[0206] Step S920: disconnect MLD1 from the link, and associate the link with MLD2.

[0207] Specifically, after receiving the second frame, the UHR AP MLD obtains the new AP MLD (i.e., MLD2) to which the non-AP STA MLD expects to switch Link0 from the original APMLD (i.e., MLD1). Therefore, the UHR AP MLD UMAC instructs MLD1 (including indirect instruction or direct control of MLD1) to disconnect MLD1 from Link0, and instructs MLD2 (including indirect instruction or direct control of MLD1) to associate MLD2 with Link0, that is, MLD2 is associated with the non-AP STA MLD through Link0.

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

[0209] Step S960: Send the first frame to the non-AP STA MLD.

[0210] After completing the link association switch from MLD1 to MLD2, the UHR AP MLD sends a first frame to the non-AP STA MLD to notify the non-AP STA MLD.

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

[0212] In some embodiments, the first frame is a BTM roaming frame.

[0213] For example, the first frame may be a BTM Roaming Reconfigure frame.

[0214] In this embodiment, the BTM roaming reconfiguration frame may include a UHR mobility field element to indicate whether the non-co-located UHR APMLD has seamless roaming capability.

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

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

[0217] Step S980: receiving a third frame from the non-AP STA MLD.

[0218] After receiving the second frame, the non-AP STA MLD adjusts the link management for sending and receiving uplink data and downlink data from the UHR AP MLD accordingly (for example, the non-AP STA MLD completes internal configuration to disconnect the association with MLD1 on Link0) to achieve seamless roaming.

[0219] The adjustment step of the internal configuration of the non-AP STA MLD includes adjusting the identification information of the AP MLD 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 switch, avoiding confusion of the same-frequency links of different AP MLDs, and saving the frame overhead of re-handshake.

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

[0221] In other embodiments, the non-AP STA MLD may not send the third frame, but the non-AP STA MLD and the UHR AP MLD determine whether the switching configuration is completed by both parties according to the specified time period, that is, after the specified time period after the UHR AP MLD sends the first frame, the non-AP STA MLD completes the switching by default. If the configuration cannot be completed within the specified time period, a notification will be sent to inform the other party that the switching failed.

[0222] In other embodiments, additionally, when one or a group of links between the non-AP STA MLD and the original AP MLD of the UHR AP MLD are switched, similar method steps are followed to complete the switching of the remaining links between the non-AP STA MLD and the original AP MLD, which will not be described in detail herein.

[0223] Optionally, before step S960, the communication method also includes step S940: sending the cached downlink data for non-APSTA MLD before link switching through an associated link other than Link0; and sending the new downlink data for non-AP STA MLD received after link switching through the switched link.

[0224] After the UHR AP MLD completes the switching of Link0 in the above steps, the UHR AP MLD continues to send the cached downlink data used for the non-APSTA MLD before the switching to the non-APSTA MLD through an associated link other than Link0 (for example, Link1). Specifically, the UHR AP MLD sends the downlink data that was cached before the switching and originally transmitted to the non-AP STAMLD through Link0 before the switching through other links that are still associated with the non-AP STA MLD. These still associated links include the link that MLD1 and the non-AP STA MLD remain associated with and the link that MLD2 and the non-AP STA MLD remain associated with.

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

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

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

[0228] Above Fig.13 The embodiment is only exemplary. For ease of understanding, only two AP MLDs and two associated links are used as examples in this embodiment. In other embodiments, there may be more than two AP MLDs and / or more than two associated links. Those skilled in the art should know that in other embodiments of the present application, for the situation of more than two AP MLDs and / or more than two associated links, there may be more possible link switching modes.

[0229] The following will further describe two AP MLDs (ie, MLD1 and MLD2) and three links (ie, Link0, Link1, and Link2).

[0230] In this embodiment, the indication information in the second frame sent by the non-AP STA MLD indicates the APMLD (MLD2) to be switched to and two links (Link0 and Link1) to be switched.

[0231] When the UHR AP MLD switches, Link0 and Link1 may be switched in sequence according to the switching order in the indication information, or Link0 and Link1 may be used as a group of links to be switched and switched simultaneously. In other words, the UHR AP MLD may switch Link1 after completing the switching of Link0, or may complete the switching of Link0 and Link1 simultaneously.

[0232] Fig.14 A partial flow chart of a seamless roaming process in a communication method provided in an embodiment of the present application is shown.

[0233] As shown in the figure, the seamless roaming process of this embodiment includes the following steps of a network access process of a non-AP STA MLD terminal device entering a non-co-located UHR AP MLD wireless network.

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

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

[0236] Step S1310, the STA MLD decides whether to roam based on the current link status.

[0237] The current link status may include at least one of the signal quality of the link associated between AP MLD1 and STA MLD judged by the current STA MLD, the distance between the AP MLD and STA MLD of the currently associated link, the load condition of the AP MLD of the currently associated link, and the load condition of the current link. The link status may also include other parameters that affect the signal quality of the link associated between AP MLD and STA MLD, which will not be described in detail in this application.

[0238] In other embodiments, additionally or alternatively, the UHR AP MLD (e.g., the UHR AP UMAC controller, AP MLD1, or AP MLD2) may decide whether to roam, or induce the STA MLD to initiate roaming. For example, the UHRAP UMAC controller may send a BTM roaming inquiry frame to the STA MLD according to the link status of the associated link, so as to induce the STA MLD to decide to roam.

[0239] Step S1320: In the overlapping area of ​​signal coverage, the STA MLD sends a probe request frame to each associated AP MLD simultaneously or sequentially through each associated link, for example, sending a probe request frame to the adjacent MLD 2. Each AP MLD (for example, MLD 2) responds to the probe request frame from the STA MLD through a probe response frame.

[0240] Step S1330: The STA MLD determines the link status according to the probe response frame returned by each link, and determines the target AP MLD to be switched to according to the link status.

[0241] The link status may include at least one of the signal quality of the link associated between AP MLD1 and STA MLD determined according to the detection response frame, the distance between the AP MLD currently associated with the link and the STA MLD, the load condition of the AP MLD currently associated with the link, and the load condition of the current link.

[0242] Additionally, in this step, STA MLD can also detect the link status determined by the response frame to determine the link switching order during the seamless roaming process of switching to APMLD, for example, first switching Link0 from MLD1 to MLD2, that is, STA MLD disconnects the association with Link0 of MLD1 and disconnects the association with Link0 of MLD2.

[0243] Fig.15 Shows Fig.14 The remaining process diagram of the seamless roaming process in the communication method is shown.

[0244] Fig.15 include Fig.14 The following remaining steps of the communication method are shown.

[0245] Step S1340: The STA MLD selects a suitable link from the associated links as the handover link, and sends a BTM roaming request frame carrying the AP MLD information corresponding to the link and the link information to the APMLD originally associated with the link.

[0246] In this step, the STA MLD determines a switching link that meets the conditions to be switched according to the determined link status of each link, and requests switching to the associated link of the new AP MLD.

[0247] Specifically, after determining the switching link, the STA MLD will send the identification information of the AP MLD to be switched and the link information of the link to be switched to the UHR AP MLD. For example, it can be sent to any associated AP MLD attached to the UHR AP MLD (for example, the AP MLD originally associated with the link), or directly to the UHR AP UMAC.

[0248] Step S1350: The UHR AP MLD instructs (including indirectly instructing or directly controlling) the AP MLD to perform link switching.

[0249] Specifically, step S1350 may include the following steps.

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

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

[0252] 3) When the STA MLD receives the BTM roaming reconfiguration frame, the roaming reconfiguration frame triggers link reconfiguration of the corresponding link (Link0) of the STA MLD (ie, link switching on the non-AP side).

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

[0254] Step S1360: After the UHR AP MLD receives the BTM roaming confirmation frame from the STA MLD, the UHR AP MLD updates the configuration of the target link (Link0) using DUMAC.

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

[0256] In another embodiment, with respect to step S1350 and step S1360, alternatively, the communication method may include the following steps:

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

[0258] 1) The original AP MLD (MLD1) sends the roaming request back to the UHR UMAC. The UHR UMAC approves or rejects the roaming request based on the target link (Link0) status (e.g., load status) of the target AP MLD (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 sends a BTM roaming reconfiguration frame to the STA MLD through the corresponding receiving link. The UHR AP MLD UMAC updates the configuration of the target link (Link0). The UHR AP MLD preferentially transmits data through the new link between Link0 of STAMLD and Link0 of MLD2.

[0260] 3) When the STA MLD receives the BTM roaming reconfiguration frame, the roaming reconfiguration frame triggers link reconfiguration of the corresponding link (Link0) of the STA MLD (ie, link switching on the non-AP side).

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

[0262] In another embodiment, for the above step 4), alternatively:

[0263] 4a) STA MLD sends a BTM roaming confirmation frame to MLD2, which indicates whether the reconfiguration of Link0 of STA MLD is successful. When the BTM roaming confirmation frame indicates that the reconfiguration of Link0 of STA MLD is successful, a BTM roaming confirmation frame is sent to MLD2 through the switched link (from Link0 of STAMLD to Link0 of MLD2) to notify UHR AP MLD that STA MLD has successfully completed the reconfiguration.

[0264] In another embodiment, after the above step 4), additionally, the communication method further includes:

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

[0266] In another embodiment, after the above step 4), additionally, the communication method further includes:

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

[0268] During seamless roaming, the link other than Link0 of the STA MLD (eg, Link1) maintains connection and communication with MLD1.

[0269] Step S1370: Complete the switching of the remaining links between the STA MLD and the original AP MLD.

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

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

[0272] 3) After reconfiguration, STA MLD sends a BTM roaming confirmation frame to MLD2 through the remaining link after switching (eg, Link1).

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

[0274] Fig.16 A flow chart of a seamless roaming process of a communication method provided in another embodiment of the present application is shown.

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

[0276] Step S1600: STA has completed network connection with AP1, and all links have been associated.

[0277] Step S1610, the STA considers that the current network status requires roaming and decides to start roaming.

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

[0279] Step S1630, the STA measures the signal quality according to the Probe Response, and decides the switching order of the Non-collocated AP MLD2 attached to the UHR to be roamed and the currently associated link.

[0280] Step S1640, the STA selects a suitable link from the associated links and sends a BSS Transition Management (BTM) Roaming frame (BTM roaming request) containing a Roaming Request to the EHT AP MLD1 (MLD1), carrying a Multi-Link reconfiaure element, informing MLD1 of the information of the EHT AP MLD1 (MLD2) to which it wants to roam and the target switching Link ID, that is, the Link ID to be reconfigured.

[0281] Step S1650, MLD1 sends a BTM Roaming ReConfiaure frame to STA on the corresponding received link, triggering the reconfiguration of STA Link1. STA cuts off the connection between Link1 and MLD1's Link1 and reconfigures to MLD2 Link1. After the reconfiguration is successful, STA sends a BTM Roaming Confirm frame to MLD2 using the newly connected Link1 to confirm the successful reconfiguration of Link1. During this process, STA Link2 always maintains the connection and communication with MLD1 Link2.

[0282] Step S1660, seamless data transmission is performed during the switching process. After completing the switching of Link1, UHR AP MLD UMAC forwards the new service data with the target address of STA to MLD2 Link1 for transmission, and the downlink service data cached in MLD1 Link2 can still be sent to STA through MLD1 Link2. After the link switching of STA is successful, its uplink service data is preferentially transmitted through Link 1 that has completed the switching. During this process, STA maintains data communication with MLD1 through Link2 and with MLD2 through Link1 respectively.

[0283] Step S1670, UHR MLD UMAC decides to switch the remaining links, and sends a BTM Roaming ReConfigure frame to STA through Link2 of MLD1 or Link1 of MLD2 to trigger STA Link2 reconfiguration. After receiving the frame, STA reconfigures Link 2 from MLD1 to MLD2. After the reconfiguration is successful, STA sends a BTM RoamingConfirm frame to MLD2 on Link2 to confirm that Link2 reconfiguration is successful. At this point, all Links of STA complete roaming switching, and STA only connects and communicates with MLD2.

[0284] Fig.17 The illustrated embodiment is different from the aforementioned exemplary embodiments in that, in this embodiment, the UHR AP MLD initiates roaming based on uplink signal quality.

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

[0286] Reference Fig.17This embodiment is applied to the non-co-located UHRAP logical entity architecture that has completed step S1710 of the network access process, that is, the non-AP STA MLD and the AP MLD1 of the UHR AP MLD are associated through the link Link0, and the non-AP STA MLD and the AP MLD1 of the UHR AP MLD are associated through the link Link1. The roaming process of this embodiment includes the following steps.

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

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

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

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

[0291] After the non-AP STA MLD determines the target link, the subsequent roaming steps refer to the description in any other embodiment, which will not be repeated here.

[0292] Fig.18Shows Fig.17 BTM request frame format in the embodiment: The BTM request frame format has been described in the existing 802.11 standard and will not be described in detail herein. The BTM request frame in this embodiment is improved based on the frame format described in 802.11.

[0293] For example, the BTM request frame includes a BSS transition candidate table entry field, and the byte length of the field is optional.

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

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

[0296] like Fig.19 As shown, the BSS transition candidate preference sub-element includes a preference field, and the length of the preference field can be 1 Octet, 2 Octets, or other lengths.

[0297] In one embodiment, the value of the preference field is used to indicate the preferred order of the BSS. For example, when the value of the preference field is 255, it indicates the most preferred candidate. When the value of the preference field is 1, it indicates the least preferred candidate.

[0298] Fig. 20 The Basic Multi-Link Element structure of the BSS transition candidate entry field of another embodiment of the present application is shown.

[0299] When the AP MLD intends to provide preference to the reported AP MLD when there is no suggestion from a specifically affiliated AP, all subfields in the Presence bitmap field shall be set to 0 and no Per-STA Profile subfield shall be included in the Basic Multilink Element.

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

[0301] Fig.21The illustrated embodiment differs from the aforementioned exemplary embodiments in that the roaming triggering method is different, that is, the AP MLD initiates the roaming based on the uplink signal.

[0302] Fig.21 The embodiment shown is also different from the aforementioned exemplary embodiment in that the method for confirming the target link (i.e., the link to be switched) is different. In this embodiment, the neighbor AP MLD first evaluates the signal quality of the probe request (uplink) and reports the uplink signal quality and link load to the UHR AP MLD UMAC. The UHR AP MLD confirms the target link based on the link load status and the uplink signal quality set.

[0303] exist Fig.21 In the illustrated embodiment, the embodiment is applied to the non-co-located UHRAP logical entity architecture of step S2010 of the network access process, that is, non-AP STA MLD and AP MLD1 of UHR AP MLD are associated through link Link0, and non-AP STAMLD and AP MLD1 of UHR AP MLD are associated through link Link1. The roaming process of this embodiment includes the following steps.

[0304] 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 UHR AP MLD UMAC. After receiving the message, the neighboring AP MLD reserves time to measure the detection request signal from the non-AP STA MLD. The original AP MLD notifies the non-AP STA MLD of the roaming preparation message via a BTM request frame.

[0305] Step S2030: The BTM request frame triggers the roaming process of the non-AP STA MLD. The non-AP STA MLD uses all its links to send a detection request to one or more adjacent AP MLDs (e.g., AP MLD2, AP MLD3, etc.), wherein these adjacent AP MLDs are all attached to the same UHR AP MLD UMAC.

[0306] Step 2040, the neighbor APMLD of the original APMLD evaluates the signal quality of the probe response of each link. The neighbor APMLD reports the link signal quality and link load to the UHR AP MLD UMAC. The UHR AP MLD UMAC determines the roaming target link based on a combination of the link load status and the probe signal quality. The UHR AP MLD UMAC notifies the original AP MLD (e.g., APMLD1) of the roaming target link (e.g., Link 0 between the non-AP STA MLD and AP MLD 2).

[0307] pass Fig.21 In the embodiment shown, on the one hand, the quality of the detection signal is evaluated by the AP MLD instead of the non-AP STA AP, thereby reducing the burden on the non-AP STA MLD. On the other hand, in this embodiment, the non-AP MLD does not need to notify the original AP MLD of the target link, nor does the AP MLD need to send a detection response to the non-AP STA MLD, thereby reducing frame overhead and improving seamless roaming efficiency.

[0308] Fig. 22 and Fig.23 Yet another embodiment of the UHR Mobility Domain field is shown.

[0309] As shown in the figure, Figure 3 and Figure 4 The difference of the embodiment shown 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 this field can be as follows: Fig.23 As shown, have different meanings.

[0310] When the value of seamless BSS transition mode is 0, it may indicate that the seamless roaming mode is that MLD does not have seamless roaming capability. When the value of seamless BSS transition mode is 1, it may indicate that the seamless roaming mode is that seamless roaming is initiated by non-AP STA MLD. When the value of seamless BSS transition mode is 2, it may indicate that the seamless roaming mode is that seamless roaming is initiated by AP MLD, and the roaming target link (for example, the roaming link to be switched) is determined by non-AP STA MLD. When the value of seamless BSS transition mode is 3, it may indicate that the seamless roaming mode is that seamless roaming is initiated by AP MLD, and the roaming target link is determined by UHR AP MLD UMAC.

[0311] The communication method provided by this application will be further described below.

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

[0313] The UHR non-co-located access point multi-link logical entity may be a UHR AP MLD. The non-co-located control module may be a UHRAP MLD UMAC, or other hardware or software, integrated or independent control device. The non-access point multi-link logical entity may be a non-AP MLD. The first access point multi-link logical entity may be an EHT AP MLD (e.g., EHT AP MLD 2) attached to the UHR AP MLD.

[0314] In one embodiment, the one or more links to which the non-AP STA MLD is to switch to the first access point multi-link logical entity may refer to the link (Link0) associated with the second access point multi-link logical entity (the original AP MLD, such as MLD1) that the non-AP STA MLD expects to disconnect, and expects to associate the link with the first access point multi-link logical entity (the target AP MLD, such as MLD2) attached to the same UHR AP MLD. The first frame may be a BTM roaming frame from the UHR AP MLD, which may include a BTM roaming request frame, a BTM roaming reconfiguration frame, a BTM roaming confirmation frame, or a BTM roaming inquiry frame.

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

[0316] Specifically, the first link identification information may be a public information field in a BTM roaming frame. The logical entity identification information may be identification information of an MLD IP to be switched to in a BTM roaming frame, that is, an MLD AP ID field in a public information field. The link information corresponding to the one or more links may be LinksInfo in a public information field in a BTM roaming frame.

[0317] Additionally, the link information corresponding to the one or more links may indicate an identifier of the link, the number of links, and an order of switching the links.

[0318] Specifically, the Links Info field of the common information field includes a link number (LinkNum) field and one or more link identification information (Link ID Info).

[0319] In one embodiment, before the non-co-site control module instructs the first frame to be sent to the non-access point multi-link logical entity, the method also includes: the non-co-site control module instructs the second access point multi-link logical entity to disconnect the association with the one or more links, and the first access point multi-link logical entity to associate with the one or more links.

[0320] The second access point multi-link logical entity may be an EHT AP MLD (eg, EHT AP MLD 1) that is attached to the same non-co-located UHR AP MLD as the first multi-link logical entity.

[0321] Specifically, during the seamless roaming process, UHR AP MLD UMAC indirectly instructs or directly controls EHT AP MLD 2 to disconnect from Link0, and indirectly instructs or directly controls EHT AP MLD 1 to establish association with Link, thereby completing link switching on the AP side.

[0322] Additionally, in another embodiment, the UHR AP MLD UMAC can share the unicast key obtained based on the UHR AP MLD UMAC address and stored in the UHR AP MLD UMAC with the EHT AP MLD 2, so that when the link is switched in seamless roaming, the STA MLD and the EHT MLD 2 no longer need to handshake and negotiate the unicast key, thereby reducing the frame overhead of the roaming process and reducing the delay of the roaming process.

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

[0324] Specifically, the second frame may be a BTM roaming request frame from a non-AP STA MLD. The first link identification information may be a common information field in the BTM roaming request frame. The logical entity identification information may be an MLD AP ID in a common information field in the BTM request frame, and the link information corresponding to the one or more links may be Links Info in a common information field in the BTM roaming request frame. The link information corresponding to the one or more links may indicate an identification of the link, the number of links, and an order of switching the links.

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

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

[0327] Specifically, the first indication may be a STA control field in a BTM roaming frame. The STA control field has been described in the aforementioned embodiments of this document, and will not be described again here.

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

[0329] Specifically, the first indication may include a link deletion mode, or a link deletion mode and a link deletion count, so that the delay duration of indicating the delayed disconnection can be realized. This has been described in the aforementioned embodiments of this article and will not be repeated here.

[0330] In one embodiment, the first frame further includes a second indication, where the second indication indicates whether the non-co-located control module has completed the operation requested by the second frame.

[0331] Specifically, the second indication may be a status code field of a common information field of a BTM roaming frame. The status code field has been defined in the known 802.11 standard, and will not be described in detail herein.

[0332] In one embodiment, after the non-co-site control module instructs to send the first frame to the non-access point multi-link logical entity, the method also includes: in response to satisfying a preset condition, the non-co-site control module confirms that the one or more links of the non-access point multi-link logical entity have been switched to be associated with the first access point multi-link logical entity.

[0333] The preset condition is used to indicate whether the non-AP STA MLD and the UHR AP MLD have completed the configuration preparation for link switching. Specifically, the preset condition may include: the non-co-location control module receives a third frame from the non-access point multi-link logical entity, and the third frame includes third link identification information corresponding to the first link identification information.

[0334] In one embodiment, the preset condition may further include: the non-co-location control module indicates that a preset time has passed after the first frame is sent.

[0335] After one of the non-AP STA MLD and the UHR AP MLD sends a BTM roaming reconfiguration frame, if the sender does not receive a reconfiguration failure notification from the other party after a preset time period, the receiver is deemed to have successfully reconfigured.

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

[0337] Specifically, the third indication may be a status code field in a BTM roaming frame sent by a non-AP STA MLD. The status code field has been defined in the known 802.11 standard, and will not be described in detail herein.

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

[0339] In this embodiment, the one or more links of the non-access point multi-link logical entity have been switched to be associated with the first access point multi-link logical entity, which means that the one or more links to be switched associated with the non-access point multi-link logical entity have completed the disconnection from the second access point multi-link logical entity and the association with the first access point multi-link logical entity on the UHR AP MLD side.

[0340] The non-co-location control module instructs that the cached downlink data for the one or more links before the switching be sent through at least one associated link other than the one or more links after the switching, which means that due to the at least one or more links that have been switched on the UHR APMLD side, the cached downlink data completed before the switching needs to continue to be sent to the non-access point multi-link logical entity through other still associated links of the second access point multi-link logical entity (MLD1). The new data obtained by the UHR AP MLD for sending to the non-AP STA MLD can be sent to the non-AP STA MLD through the newly associated link by the UHR AP MLD UMAC instructing the newly associated first access point multi-link logical entity.

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

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

[0343] Specifically, the non-co-location control module can instruct the access point multi-link logical entity that caches the downlink data to return the corresponding downlink data to the non-co-location control module, and the non-co-location control module instructs other access point multi-link logical entities associated with the non-access point multi-link logical entity to continue forwarding the downlink data.

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

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

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

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

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

[0349] Specifically, the fourth frame may be a BTM roaming reconfiguration frame sent by the UHR access point multi-link logical entity through the access point multi-link logical entity of the remaining unswitched links, and the roaming switching of all links of the non-access point multi-link logical entity has been completed.

[0350] In one embodiment, the method further includes: the non-co-located control module sharing or copying the first key information used for the UHR non-co-located access point multi-link logical entity to the first access point multi-link logical entity for use in an associated link of the first access point multi-link logical entity.

[0351] Specifically, the first key information is calculated based on the UHR AP MLD UMAC address. The first key information may be a pairwise transition key (PTK).

[0352] Alternatively, the first key information is generated and stored in the UHR AP MLD UMAC.

[0353] Additionally or alternatively, the first key information can be shared by the UHR AP MLD UMAC to multiple EHT AP MLDs during the network access process, and can also be shared to the AP MLD to be switched to (for example, the first access point multi-link logical entity) during the link switching process of the AP MLD in the seamless roaming process.

[0354] In one embodiment, the first key information is based on an upper media access control (UMAC) address of the non-co-located control module.

[0355] Specifically, the PTK key information may be obtained by calculation based on the UHR AP MLD UMAC address.

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

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

[0358] Specifically, the fourth indication may be an AP MLD ID field in the MLO GTK KDE, MLO IGTK KDE, and MLO BIGTK KDE fields.

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

[0360] In one embodiment, before the non-co-site control module receives the second frame from the non-access point multi-link logical entity, the method also includes: the non-co-site control template sends a fifth frame to the non-access point multi-link logical entity, wherein the fifth frame is configured to request the non-access point multi-link logical entity to send the second frame.

[0361] Specifically, the fifth frame may be a BTM roaming inquiry frame sent from the UHR AP MLD to the non-access point multi-link logical entity. The BTM roaming inquiry frame may induce or request the non-access point multi-link logical entity to send a BTM roaming request frame.

[0362] In one embodiment, the non-co-located control module is configured to store PTK key information for the UHR non-co-located access point multi-link logical entity.

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

[0364] Specifically, the sixth frame may include a Beacon frame, a Probe Response Frame, an Association Request Frame, an Association Response Frame, and an Authentication Frame to announce the seamless transition capability of the UHRAP MLD (for example, to a non-access point multi-link device).

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

[0366] In one embodiment, the method also includes: determining the multicast key information for the one or more links of the first access point multi-link logical entity based on the corresponding lower media access control (LMAC) address of the first access point multi-link logical entity; and the non-co-location control module instructs the multicast key information to be sent to the non-access point multi-link logical entity.

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

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

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

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

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

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

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

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

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

[0376] In one embodiment, the method also includes: the non-access point multi-link logical entity sends a seventh frame on multiple links associated with the UHR non-co-located access point multi-link logical entity respectively; the non-access point multi-link logical entity receives multiple eighth frames from the UHR non-co-located access point multi-link logical entity in response to the seventh frame; and the non-access point multi-link logical entity determines the one or more links of the first access point multi-link logical entity based on the multiple eighth frames.

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

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

[0379] In one embodiment, the method further includes: the non-access point multi-link logical entity receives a sixth frame from the UHR non-co-located access point multi-contact logical entity, wherein the sixth frame includes a UHR mobility domain element, and the UHR mobility domain element indicates a seamless roaming capability of the UHR non-co-located access point multi-link logical entity.

[0380] Fig.24 1 is a schematic diagram of the structure of an access point device 170 provided in an embodiment of the present application. The access point device 170 may be as follows: Figure 2 The access point multi-link device 202 in the WLAN is shown. Fig.17 As shown, the access point device 170 includes:

[0381] The sending module 1710 is configured to send a first frame to a non-access point multi-link logical entity (Non-AP Multi-link logical entity), wherein the first frame includes first link identification information, and the first link identification information indicates that the non-access point multi-link logical entity is to be switched to one or more links with the first access point multi-link logical entity.

[0382] Optionally, the access point device 170 may be an access point multi-link logical entity.

[0383] The access point device 170 may also include other modules to execute the communication methods of the above embodiments. The above exemplary embodiments of the communication method, as well as improvements, modifications and variations obtained by those skilled in the art on the basis of these embodiments without creative work, may also be used to define the access point device 170, and this application will not repeat them again.

[0384] Fig.25 1 is a schematic diagram of a structure of a non-access point device 180 provided in an embodiment of the present application. The non-access point device 180 may be as follows: Figure 2 The terminal device 201 in the WLAN shown in FIG. Fig.17 As shown, the non-access point device 180 includes:

[0385] The sending module 1810 is configured to send a second frame to the UHR non-co-located access point multi-link logical entity, wherein the second frame includes second link identification information, wherein the second link identification information indicates that the non-access point multi-link logical entity is to be switched to one or more links associated with the first access point multi-link logical entity.

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

[0387] The non-access point device 180 may also include other modules to execute the communication methods of the above-mentioned embodiments. The above-mentioned exemplary embodiments of the communication method, as well as the improvements, modifications and variations obtained by those skilled in the art on the basis of these embodiments without creative work, can also be used to define the non-access point device 180, and this application will not repeat them again.

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

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

[0390] For example, Fig.26 is a block diagram of an access point multi-link device provided in an embodiment of the present application. Fig.26 As shown, the access point multi-link device 1900 includes: a processor 1901 and a transceiver 1902. The transceiver 1902 is used to perform the transceiver actions of the access point multi-link device in the above method embodiment under the control of the processor 1901.

[0391] Optionally, the access point multi-link device 1900 further includes a memory 1903 , a communication bus 1904 and a communication interface 1905 .

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

[0393] Communication bus 1904 may include a pathway for transmitting information between the above-mentioned components.

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

[0395] The memory 1903 is used to store the program code for executing the solution of the present application, and the execution is controlled by the processor 1901. The processor 1901 is used to execute the program code stored in the memory 1903. The program code may include one or more software modules. The one or more software modules may be Fig.24 The software modules provided in the embodiments.

[0396] The communication interface 1905 uses the transceiver 1902 to communicate with other devices or communication networks, such as Ethernet, radio access network (RAN), WLAN, etc.

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

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

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

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

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

[0402] For example, Fig. 27 is a block diagram of a non-access point multi-link device provided in an embodiment of the present application. Fig. 27 As shown, the non-access point multi-link device 2000 includes: a processor 2001 and a transceiver 2002. The transceiver 2002 is used to perform the transceiver actions performed by the non-access point multi-link device in the above method embodiment under the control of the processor 2001.

[0403] Optionally, the access point multi-link device 2000 further includes a memory 2003 , a communication bus 2004 and a communication interface 2005 .

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

[0405] Communication bus 2004 may include a pathway for transmitting information between the above-mentioned components.

[0406] The memory 2003 may be a ROM or other type of static storage device capable of storing static information and instructions, a RAM or other type of dynamic storage device capable of storing information and instructions, or an EEPROM, a CD-ROM or other optical disk storage, an optical disk storage (including a compressed optical disk, a laser disk, an optical disk, a digital versatile disk, a blue-ray disk, etc.), a magnetic disk or other magnetic storage device, or any other medium capable of carrying or storing a desired program code in the form of an instruction or data structure and capable of being accessed by a computer, but not limited thereto. The memory 2003 may be independent and connected to the processor 2001 via a communication bus 2004. The memory 2003 may also be integrated with the processor 2001.

[0407] The memory 2003 is used to store the program code for executing the solution of the present application, and the execution is controlled by the processor 2001. The processor 2001 is used to execute the program code stored in the memory 2003. The program code may include one or more software modules. The one or more software modules may be Fig.18 Software modules provided in .

[0408] The communication interface 2005 uses the transceiver 2002 to communicate with other devices or communication networks, such as Ethernet, RAN, WLAN, etc.

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

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

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

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

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

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

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

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

[0417] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0418] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

Claims

1. A communication method in a wireless local area network, applied to a non-collocated control module of an ultra-high reliability (UHR) non-collocated access point multi-link logical entity, comprising: The non-co-site control module instructs sending a first frame to a non-access point multi-link logical entity (Non-AP Multi-link logical entity), wherein the first frame includes first link identification information, and the first link identification information indicates that the non-access point multi-link logical entity is to be switched to one or more links associated with the first access point multi-link logical entity.

2. The method according to claim 1, wherein: The first link identification information includes logical entity identification information corresponding to the first access point multi-link logical entity and link information corresponding to the one or more links.

3. The method according to claim 1 or 2, wherein: Before the non-co-location control module instructs to send the first frame to the non-access point multi-link logical entity, the method further includes: The non-co-location control module instructs the second access point multi-link logical entity to be disconnected from the one or more links, and the first access point multi-link logical entity to be associated with the one or more links.

4. The method according to any one of claims 1 to 3, wherein: Before the non-co-location control module instructs to send the first frame to the non-access point multi-link logical entity, the method further includes: The non-co-location control module receives a second frame from the non-access point multi-link logical entity, where the second frame includes second link identification information, wherein the first link identification information corresponds to the second link identification information.

5. The method according to any one of claims 1 to 4, wherein: The one or more links are respectively associated with the non-access point multi-link logical entity and the second access point link logical entity.

6. The method according to claim 5, wherein: The first frame further includes a first indication indicating a disconnection mode of the one or more links.

7. The method according to claim 6, wherein: The disconnection mode is delayed disconnection, and the first indication further indicates the delay duration of the delayed disconnection.

8. An access point device, comprising: A sending module is configured to send a first frame to a non-access point multi-link logical entity (Non-AP Multi-link logical entity), wherein the first frame includes first link identification information, and the first link identification information indicates that the non-access point multi-link logical entity is to be switched to one or more links associated with the first access point multi-link logical entity.

9. An access point multi-link device, comprising: processors and transceivers; The processor is used to call a computer program to cooperate with the transceiver to implement the communication method according to any one of claims 1 to 7.

10. A communication system in a wireless local area network, comprising: The access point apparatus according to claim 8 or the access point multi-link device according to claim 9.

Images