Wireless communication method and device

Abstract

The embodiment of the invention provides a wireless communication method and equipment, which can realize uninterrupted roaming or seamless roaming of a Non-AP MLD (Non-Access Point MLD) between different AP MLDs (Physical AP MLD) in a logic AP MLD, thereby improving the roaming performance of the Non-AP MLD between the different AP MLDs in the logic AP MLD. The wireless communication method is applied to a Non-AP MLD, the Non-AP MLD roams among different AP MLDs (physical AP MLDs) in a logical AP MLD, and the method comprises the following steps: the Non-AP MLD sends a first frame; wherein the first frame comprises a first field, and the first field is used for indicating that the first frame is used for adding or deleting a first type of links, or the first field is used for indicating that the first frame is used for adding or deleting a second type of links.

Description

Wireless communication method and device Technical Field

[0001] The present invention relates to the field of communications, and more specifically, to a method and device for wireless communications. Background Art

[0002] In wireless local area network (WLAN) communications, hitchless roaming has been introduced to improve station (STA) mobility. However, hitchless roaming in multi-link device (MLD) scenarios has not been studied or discussed in depth.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a method and device for wireless communication, which can realize uninterrupted roaming or seamless roaming of a non-AP MLD (non-AP multi-link device) between different AP MLDs (physical AP MLDs) within a logical AP MLD (logical AP multi-link device), thereby improving the roaming performance of the non-AP MLD between different AP MLDs (physical AP MLDs) within the logical AP MLD.

[0005] In a first aspect, a wireless communication method is provided, which is applied to a non-AP MLD, where the non-AP MLD roams between different AP MLDs within a logical AP MLD. The method includes:

[0006] The Non-AP MLD sends the first frame.

[0007] The first frame includes a first field, and the first field is used to indicate that the first frame is used to add or delete a first type of link, or the first field is used to indicate that the first frame is used to add or delete a second type of link.

[0008] In a second aspect, a wireless communication method is provided, which is applied to an AP MLD, where the AP MLD is a logical AP MLD. The method includes:

[0009] The AP MLD receives the first frame sent by the Non-AP MLD;

[0010] The Non-AP MLD roams between different AP MLDs within the logical AP MLD.

[0011] The first frame includes a first field, and the first field is used to indicate that the first frame is used to add or delete a first type of link, or the first field is used to indicate that the first frame is used to add or delete a second type of link.

[0012] In a third aspect, a STA is provided for executing the method in the first aspect.

[0013] Specifically, the STA includes a functional module for executing the method in the above-mentioned first aspect.

[0014] In a fourth aspect, an AP is provided for executing the method in the second aspect.

[0015] Specifically, the AP includes a functional module for executing the method in the above second aspect.

[0016] In a fifth aspect, a STA is provided, comprising a processor and a memory; the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the STA executes the method in the above-mentioned first aspect.

[0017] In a sixth aspect, an AP is provided, comprising a processor and a memory; the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the AP executes the method in the above-mentioned second aspect.

[0018] In a seventh aspect, a device is provided for implementing the method in any one of the first to second aspects above.

[0019] Specifically, the apparatus includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the apparatus executes the method in any one of the first to second aspects described above.

[0020] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the first to second aspects above.

[0021] In a ninth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the first to second aspects above.

[0022] In a tenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to second aspects above.

[0023] With the above technical solution, when a non-AP MLD roams between different AP MLDs (physical AP MLDs) within a logical AP MLD, the non-AP MLD can add or delete a first-type link based on the first field in the first frame sent by the AP MLD. Alternatively, the non-AP MLD can add or delete a second-type link based on the first field in the first frame sent by the AP MLD. This enables uninterrupted or seamless roaming between different AP MLDs (physical AP MLDs) within the logical AP MLD, thereby improving the roaming performance between different AP MLDs (physical AP MLDs) within the logical AP MLD. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] FIG1 is a schematic diagram of a communication system architecture applied in an embodiment of the present application.

[0025] FIG2 is a schematic diagram of a NAV distribution provided in this application.

[0026] FIG3 is a schematic diagram of establishing multiple links between an AP MLD and a Non-AP MLD provided by the present application.

[0027] FIG4 is a schematic diagram of a reconfiguration operation type provided by the present application.

[0028] FIG5 is a schematic diagram of a logical AP MLD composed of multiple non-co-located APs provided by the present application.

[0029] FIG6 is a schematic diagram of an MLD-level roaming operation provided by the present application.

[0030] FIG7 is a schematic diagram of a link-level roaming operation provided by the present application.

[0031] FIG8 is a schematic diagram of link switching during roaming provided by the present application.

[0032] FIG9 is a schematic diagram of a multi-AP cooperative transmission provided by the present application.

[0033] FIG10 is a schematic flowchart of a wireless communication method provided according to an embodiment of the present application.

[0034] 11 to 16 are schematic diagrams of deleting or adding links during roaming according to embodiments of the present application.

[0035] FIG17 is a schematic diagram of a multi-link operation update request frame provided according to an embodiment of the present application.

[0036] FIG18 is a schematic diagram of a frame for adding or deleting a roaming link according to an embodiment of the present application.

[0037] FIG19 is a schematic diagram of another multi-link operation update request frame provided according to an embodiment of the present application.

[0038] Figure 20 is a schematic diagram of STA roaming provided according to an embodiment of the present application.

[0039] Figure 21 is a schematic diagram of another STA roaming provided according to an embodiment of the present application.

[0040] Figure 22 is a schematic diagram of another STA roaming provided according to an embodiment of the present application.

[0041] FIG23 is a schematic block diagram of a Non-AP MLD provided according to an embodiment of the present application.

[0042] FIG24 is a schematic block diagram of an AP MLD provided according to an embodiment of the present application.

[0043] Figure 25 is a schematic block diagram of a communication device provided according to an embodiment of the present application.

[0044] Figure 26 is a schematic block diagram of a device provided according to an embodiment of the present application.

[0045] Figure 27 is a schematic block diagram of a communication system provided according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] The following will describe the technical solutions in the embodiments of this application in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. With respect to the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0047] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), or other communication systems.

[0048] Please refer to Figure 1, which shows a schematic diagram of a wireless communication system provided by an embodiment of the present application. As shown in Figure 1, the wireless communication system may include: an access point (AP) and a station (STA).

[0049] In some scenarios, an AP can be referred to as an AP STA, meaning that in a sense, an AP is also a type of STA. In some scenarios, a STA can be referred to as a non-AP STA.

[0050] In some embodiments, STAs may include AP STAs and non-AP STAs. Communication in a communication system may be between an AP and a non-AP STA, between a non-AP STA and a non-AP STA, or between a STA and a peer STA. A peer STA may refer to a device that communicates with a STA. For example, a peer STA may be an AP or a non-AP STA.

[0051] An AP acts as a bridge between wired and wireless networks, connecting wireless network clients together and then connecting the wireless network to the Ethernet. An AP can be a terminal device (such as a mobile phone) or a network device (such as a router) equipped with a Wireless Fidelity (Wi-Fi) chip.

[0052] It should be understood that the role of STA in the communication system is not absolute. For example, in some scenarios, when a mobile phone is connected to a router, the mobile phone is a non-AP STA. When the mobile phone serves as a hotspot for other mobile phones, the mobile phone plays the role of AP.

[0053] APs and non-AP STAs can be devices used in the Internet of Vehicles, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0054] In some embodiments, a non-AP STA may support 802.11be. A non-AP STA may also support various current and future 802.11 family wireless LAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0055] In some embodiments, the AP may be a device supporting the 802.11be standard. The AP may also be a device supporting various current and future 802.11 family WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0056] In the embodiment of the present application, the STA may be a mobile phone, tablet computer, computer, virtual reality (VR) device, augmented reality (AR) device, wireless device in industrial control, set-top box, wireless device in self-driving, in-vehicle communication equipment, wireless device in remote medical, wireless device in smart grid, wireless device in transportation safety, wireless device in smart city, wireless device in smart home, wireless communication chip, ASIC (Application Specific Integrated Circuit), SOC (System on Chip), etc. that supports WLAN / WIFI technology.

[0057] The frequency bands supported by WLAN technology may include but are not limited to: low frequency bands (2.4 GHz, 5 GHz, 6 GHz) and high frequency bands (45 GHz, 60 GHz).

[0058] There are one or more links between the station and the access point. In some embodiments, the station and the access point support multi-band communication. For example, communication is performed simultaneously on the 2.4 GHz, 5 GHz, 6 GHz, 45 GHz, and 60 GHz frequency bands, or communication is performed simultaneously on different channels of the same frequency band (or different frequency bands), thereby improving the communication throughput and / or reliability between devices. Such a device is generally referred to as a multi-band device, or a multi-link device (MLD), sometimes also referred to as a multi-link entity or a multi-band entity. A multi-link device can be an access point device or a station device. If the multi-link device is an access point device, the multi-link device includes one or more APs; if the multi-link device is a station device, the multi-link device includes one or more non-AP STAs.

[0059] A multi-link device including one or more APs may be referred to as an AP MLD, and a multi-link device including one or more non-AP STAs may be referred to as a non-AP MLD.

[0060] In an embodiment of the present application, the AP may include multiple APs, the Non-AP may include multiple STAs, multiple links may be formed between the APs in the AP and the STAs in the Non-AP, and data communication may be performed between the APs in the AP and the corresponding STAs in the Non-AP through the corresponding links.

[0061] An AP is a device deployed in a wireless local area network to provide wireless communication capabilities for STAs. A station may include: User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user device. Optionally, a station may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, or a wearable device, but the embodiments of the present application are not limited thereto.

[0062] Optionally, both the station and the access point support the IEEE 802.11 standard.

[0063] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0064] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0065] The terms used in the embodiments of this application are intended only to explain the specific embodiments of this application and are not intended to limit this application. The terms "first," "second," "third," and "fourth," etc. in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, not to describe a specific order. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions.

[0066] It should be understood that the "at least one or at least one" mentioned in the embodiments of the present application can mean "one or more", and the "positive integer" mentioned in the embodiments of the present application can mean "values ​​such as 1, 2, 3...", and the "non-negative integer" mentioned in the embodiments of the present application can mean "values ​​such as 0, 1, 2, 3...", and the "integer" mentioned in the embodiments of the present application can mean "values ​​such as..., -3, -2, -1, 0, 1, 2, 3,...", and can be replaced with any possible value based on the requirements of the embodiment.

[0067] It should be understood that the figures and / or tables shown in the embodiments of the present application are merely examples. Specifically, in some cases, some of the information contained in the figures and / or tables shown in the embodiments of the present application may independently constitute an optional embodiment. For example, each row or column in the table may independently constitute an optional embodiment. The present application does not limit this.

[0068] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0069] In the embodiments of the present application, "pre-defined" or "pre-configured" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., including STAs and network devices). The present application does not limit the specific implementation method. For example, pre-defined may refer to what is defined in the protocol.

[0070] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include a WiFi protocol and related protocols used in future WiFi communication systems, and the present application does not limit this.

[0071] To facilitate a better understanding of the embodiments of the present application, the Enhanced Distributed Channel Access (EDCA) related to the present application is described.

[0072] When a STA detects a channel transition from busy to idle during a clear channel assessment (CCA), it must continue to check for idleness within the distributed (coordination function) interframe space (DIFS). If the current random backoff counter is 0, the STA obtains channel access and immediately transmits, resetting the random backoff counter. Otherwise, the STA continues to check for idleness. Each time the channel remains idle, the STA's random backoff counter is decremented by 1 until the STA's random backoff counter reaches 0. At this point, the STA obtains channel access and immediately transmits, resetting the random backoff counter. If another STA secures the channel first during this process, the STA's random backoff counter remains unchanged. The next time CCA detects a transition from busy to idle, the STA's random backoff counter remains at the previous value. For example, the distributed coordination function interframe space (DIFS) is greater than the short interframe space (SIFS).

[0073] To facilitate a better understanding of the embodiments of the present application, the distribution of network allocation vectors (NAVs) related to the present application is described.

[0074] When a request to send (RTS) / clear to send (CTS) exchange or a CTS-to-self (CTS-to-self) frame is the first frame transmitted, its duration field indicates the total duration of the transmission (i.e., used to set the NAV value and protect the channel).

[0075] When a node needs to distribute NAV information, for example, to reserve the medium for transmission of non-basic rate frames (which other nodes in the Basic Service Set (BSS) may not hear), as shown in Figure 2, if the node is a non-directional multi-gigabit (DMG) STA, the node may first send a CTS frame (CTS-to-self) with the Receiving Address (RA) field equal to its own Media Access Control (MAC) address, or the node may send a DMG CTS frame with the RA field equal to its own MAC address. The duration value in the CTS or DMG CTS frame protects the upcoming transmission, plus a possible acknowledgment (Ack) frame.

[0076] A non-AP High Efficiency STA (Non-AP HE STA) should maintain two NAVs, and a HE AP can maintain two NAVs: a BSS internal NAV and a basic NAV.

[0077] The intra-BSS NAV is updated by the intra-BSS physical layer protocol data unit (PPDU), while the basic NAV is updated by the inter-BSS PPDU or the PPDU that cannot be classified as intra-BSS or inter-BSS.

[0078] For a High Efficiency STA (HE STA) that maintains two NAVs, if both NAV timers are 0, the virtual Carrier Sensing (CS) indication is Medium Idle; if at least one of the two NAV timers is non-zero, the virtual CS indication is Medium Busy.

[0079] That is, when a PPDU is received, the station will update its corresponding NAV value.

[0080] To facilitate a better understanding of the embodiments of the present application, the multi-link device (MLD) and multi-link operations related to the present application are described.

[0081] The AP and STA with multi-link operation capability are AP MLD and non-AP MLD respectively. Multiple links can be established between the AP MLD and the non-AP MLD on multiple different frequency bands / channels.

[0082] As shown in Figure 3, three links, called link 1, link 2, and link 3, are established between AP MLD and non-AP MLD at 2.4 GHz, 5 GHz, and 6 GHz. These links can operate simultaneously. AP 1 operating on link 1 (2.4 GHz), AP 2 operating on link 2 (5 GHz), and AP 3 operating on link 3 (6 GHz) are called AP MLD affiliated access points (affiliated APs). Similarly, AP 1 operating on link 1 (2.4 GHz), AP 2 operating on link 2 (5 GHz), and AP 3 operating on link 3 (6 GHz) are called AP MLD affiliated APs. Non-AP STA 1 operating on link 1 (2.4 GHz), non-AP STA 2 operating on link 2 (5 GHz), and non-AP STA 3 operating on link 3 (6 GHz) are respectively called affiliated (non-AP) STAs of the non-AP MLD.

[0083] To facilitate a better understanding of the embodiments of the present application, the non-AP MLD adding / deleting link related to the present application is described.

[0084] Non-AP MLD performs link add and link delete operations through the exchange of Multi-Link Operation Update Request and Multi-Link Operation Update Response frames. The Reconfiguration Operation Type field in the Reconfiguration Multi-Link element carried in these frames adds the add link / delete link type, as shown in Figure 4. It also adds parameter fields applicable to a single link: Non-Simultaneous Transmit and Receive (NSTR) Link Pair Present, NSTR Bitmap Size, and NSTR Indication Bitmap.

[0085] To facilitate a better understanding of the embodiments of the present application, a description is given of a logical AP MLD composed of multiple non-co-located APs related to the present application.

[0086] Multiple non-collocated APs are treated as a single logical AP MLD entity. When a STA connects to this AP MLD, the multiple non-collocated APs can be considered different affiliated APs of the AP MLD. This allows AP MLD to use a multi-link operation architecture to use different affiliated APs to provide services to the STA using different links, thereby achieving better STA roaming. As shown in Figure 5, STA x uses multiple links to connect to AP 1 and AP 2. When STA x sends a move signal, the link to AP 1 is disconnected, but the link to AP 2 is not affected. This improves STA mobility support.

[0087] Specifically, the MLD architecture on a physical device is transformed into a logical multi-link access point device consisting of multiple physical devices. For example, MLD-level roaming can be shown in Figure 6. For another example, link-level roaming can be shown in Figure 7. For example, different links can be distinguished using the AP MLD roaming ID (to distinguish different AP MLDs under the Roaming AP MLD) and the link ID (to distinguish different links under the same AP MLD).

[0088] For example, during roaming, one or more new links may be added at a time, and the old links may be deleted after the roaming is completed, as shown in FIG8 .

[0089] To facilitate a better understanding of the embodiments of the present application, multi-AP cooperative transmission related to the present application is described.

[0090] As shown in Figure 9, multiple APs can form a multi-AP MLD collaboration set (Multi-AP MLD Candidate Set), in which one AP acts as the master AP (Master AP, M-AP) through a wired or wireless link (also called a backhaul link (backhaul link)) to manage and control the other auxiliary APs (Slave AP, S-AP) in the Multi-AP MLD Candidate Set. Then the APs in the Multi-AP MLD Candidate Set can provide services for STAs (e.g., STA a, STA b) through collaboration.

[0091] There are many ways to cooperate with multiple APs, such as coordinated orthogonal frequency division multiple access (C-OFDMA), coordinated time division multiple access (C-TDMA), coordinated beamforming (C-BF), joint transmission (J-TX), coordinated spatial reuse (C-SR), and coordinated uplink multiple-user multiple input multiple output (C-UL MU MIMO).

[0092] To facilitate understanding of the technical solutions of the embodiments of the present application, the problems solved by the present application are described below.

[0093] Currently, the 802.11 series of Wi-Fi standards uses a fast BSS transition (FT) mechanism when roaming (i.e., moving from one BSS coverage area to another). However, the FT mechanism cannot prevent link interruptions during handover (which can last for more than 2 milliseconds).

[0094] In multi-link device roaming scenarios, when using logical AP MLD technology, link addition and deletion operations are required. Furthermore, the 11bn (Ultra High Reliability, UHR, Wi-Fi 8) protocol must be compatible with the 11be (Extremely High Throughput, EHT, Wi-Fi 7) protocol. Therefore, the link addition and deletion signaling for logical AP MLD must be distinguishable from the link addition and deletion signaling for single AP MLD (i.e., Wi-Fi 7 devices).

[0095] Furthermore, logical AP MLD technology does not specify the information that needs to be exchanged and synchronized between APs during site roaming. It also does not specify how a site performs channel access and data transmission with two APs during roaming.

[0096] Based on the above problems, the present application proposes a multi-link device roaming solution, which can improve the roaming performance of multi-link devices.

[0097] To facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the scope of protection of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0098] FIG10 is a schematic flow chart of a wireless communication method 200 according to an embodiment of the present application. As shown in FIG10 , the method is applied to a non-AP MLD, where the non-AP MLD roams between different AP MLDs (physical AP MLDs) within a logical AP MLD. The wireless communication method 200 may include at least part of the following:

[0099] S210, the Non-AP MLD sends a first frame to the AP MLD; wherein the first frame includes a first field, the first field being used to indicate that the first frame is used to add or delete a first type of link, or the first field being used to indicate that the first frame is used to add or delete a second type of link; wherein the AP MLD belongs to the logical AP MLD;

[0100] S220: The AP MLD receives the first frame sent by the Non-AP MLD.

[0101] It should be understood that FIG10 shows the steps or operations of the wireless communication method 200, but these steps or operations are merely examples, and the embodiments of the present application may also perform other operations or variations of the operations in FIG10.

[0102] In the embodiments of the present application, a "field" may also be referred to as a "field" or a "subfield." A field may occupy one or more bytes (byte / octet), or a field may occupy one or more bits (bits) or bit positions.

[0103] In the embodiment of the present application, a logical AP MLD may include multiple physical AP MLDs. For example, multiple non-co-located physical AP MLDs constitute a logical AP MLD.

[0104] In the embodiment of the present application, if the AP MLD to which the link (e.g., link 1) that sends the frame for adding or deleting a link belongs is consistent with the AP MLD to which the link to be added or deleted (e.g., link 2) belongs, then the link (i.e., link 1) can be a first-category link. Specifically, for example, a first-category link can also be referred to as a local link. That is, if the AP MLD to which the link (e.g., link 1) that sends the frame for adding or deleting a link belongs is consistent with the AP MLD to which the link to be added or deleted (e.g., link 2) belongs, then the link (i.e., link 1) is referred to as a local link (e.g., all 802.11be links are local links).

[0105] In the embodiment of the present application, if the AP MLD to which the link (e.g., link 1) that sends the add or delete link frame is inconsistent with the AP MLD to which the link to be added or deleted (e.g., link 2) belongs, then the link (i.e., link 1) may be a second-category link. Specifically, for example, a second-category link may also be referred to as a roaming link. That is, if the AP MLD to which the link (e.g., link 1) that sends the add or delete link frame is inconsistent with the AP MLD to which the link to be added or deleted (e.g., link 2) belongs, then the link (i.e., link 1) is referred to as a roaming link.

[0106] For example, when the link to be added or deleted is a roaming link, backend information interaction between AP MLDs within the logical AP MLD is triggered.

[0107] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, the Non-AP MLD performs link switching in a first manner or a second manner; wherein the first manner is to first add a target link and then delete a source link, and the second manner is to first delete a source link and then add a target link.

[0108] In some embodiments, the AP MLD corresponding to the source link may indicate the link switching mode adopted by the Non-AP MLD. Of course, it may also be the link switching mode adopted by the Non-AP MLD indicated by other devices.

[0109] During roaming, the design of the first frame can be applied to a method of first adding a target link (i.e., a new link) and then deleting a source link (i.e., an old link), or it can be applied to a method of first deleting a source link (i.e., an old link) and then adding a target link (i.e., a new link).

[0110] For example, consider the process of first adding a target link (i.e., a new link) and then deleting the source link (i.e., an old link). (After roaming, a non-AP STA (i.e., STA2) affiliated with Non-AP MLD 1 simultaneously establishes a link with an affiliated AP in each of two AP MLDs (i.e., AP MLD 1 and AP MLD 2) within a logical AP MLD.) Non-AP MLD 1 first exchanges a request and response with the source AP MLD (i.e., AP MLD 1) on Link 1 (the local link) to add Link 2 (the roaming link). After this, Non-AP MLD 1 exchanges a request and response with the source AP MLD (i.e., AP MLD 1) on Link 1 (the local link). Alternatively, Non-AP MLD 1 first exchanges a request and response with the source AP MLD (i.e., AP MLD 1) on Link 1 (the local link). After this, Non-AP MLD 1 exchanges a request and response with the target AP MLD on Link 2 to delete Link 1 (the roaming link). Among them, link 1 and link 2 can be links of the same frequency band and the same channel (as shown in Figure 11), or links of the same frequency band but different channels (as shown in Figure 11), or links of different frequency bands (as shown in Figure 12).

[0111] That is, as shown in Figures 11 and 12, during link addition, link 1 is a local link (i.e., a first-type link) and link 2 is a roaming link (i.e., a second-type link). During link deletion, link 2 is a local link (i.e., a first-type link) and link 1 is a roaming link (i.e., a second-type link). In Figures 11 and 12, AP MLD 1 and AP MLD 2 are physical AP MLDs.

[0112] For example, consider the process of first deleting the source link (i.e., the old link) and then adding the target link (i.e., the new link). (After roaming, the two non-AP STAs affiliated with non-AP MLD 1 each have a link with an AP affiliated with two AP MLDs (i.e., AP MLD 1 and AP MLD 2). Non-AP MLD 1 first exchanges a request and response with the source AP MLD on Link 1 (the local link) to delete Link 1 (the local link). After this, Non-AP MLD 1 exchanges a request and response with the source AP MLD on Link 2 (the local link) to add Link 3 (the roaming link). Links 1 and 2 are on different frequency bands. Links 1 and 3 can be on the same frequency band and channel (as shown in Figure 13), on the same frequency band but different channels (as shown in Figure 13), or on different frequency bands (as shown in Figure 14).

[0113] 13 and 14 , link 1 and link 2 are local links (i.e., first-type links), and link 3 is a roaming link (i.e., second-type link). In FIG13 and FIG14 , AP MLD 1 and AP MLD 2 are physical AP MLDs.

[0114] In the embodiment of the present application, when adding or deleting a link, the Non-AP MLD maintains at least one link in an enabled state, such as link 3 shown in Figures 11 and 12, and link 2 shown in Figures 13 and 14. That is, the Non-AP MLD can also maintain link connection during roaming without interrupting data transmission. This can achieve uninterrupted roaming or seamless roaming between different AP MLDs within a logical AP MLD, thereby improving the roaming performance of the Non-AP MLD between different AP MLDs within the logical AP MLD.

[0115] In some embodiments, as shown in FIG15 , AP MLD 1 (physical AP MLD) and AP MLD 2 (physical AP MLD) belong to the same logical AP MLD. Non-AP MLD 1 currently establishes link 1 and link 2 with AP MLD 1. During the process of Non-AP MLD 1 roaming to AP MLD 2, Non-AP MLD 1 can send a first frame to AP MLD 1 (i.e., the source AP MLD) to add link 3 with AP MLD 2 (i.e., the target AP MLD) (link 3 does not belong to AP MLD 1 that received the first frame, so link 3 is a second-type link (i.e., a roaming link)). After a period of time (i.e., after link 3 is successfully added), Non-AP MLD 1 sends a first frame to AP MLD 2 (i.e., the target AP MLD) to delete link 1 with AP MLD 1 (i.e., the source AP MLD) (link 1 does not belong to AP MLD 1 that received the first frame). 2, so link 1 is a second-type link (i.e., a roaming link). Alternatively, after a period of time (i.e., after link 3 is successfully added), Non-AP MLD 1 sends a first frame to AP MLD 1 (i.e., the source AP MLD) to delete link 1 between it and AP MLD 1 (i.e., the source AP MLD). (Link 1 belongs to AP MLD 1 that received the first frame, so link 1 is a first-type link (i.e., a local link).

[0116] In some embodiments, as shown in FIG16 , AP MLD 1 (physical AP MLD) and AP MLD 2 (physical AP MLD) belong to the same logical AP MLD. Non-AP MLD 1 currently establishes Link 1 and Link 2 with AP MLD 1. During the process of Non-AP MLD 1 roaming to AP MLD 2, Non-AP MLD 1 may send a first frame to AP MLD 1 (i.e., the source AP MLD) to delete Link 1 with AP MLD 1 (i.e., the source AP MLD). (Link 1 belongs to AP MLD 1 that received the first frame, so Link 1 is a first-type link (i.e., a local link).) After a period of time (i.e., after Link 1 is deleted), Non-AP MLD 1 may send a first frame to AP MLD 1 (i.e., the source AP MLD) to add Link 3 with AP MLD 2 (i.e., the target AP MLD). (Link 3 does not belong to AP MLD 1 that received the first frame, so Link 3 is a second-type link (i.e., a roaming link).

[0117] In some embodiments, the first field is a roaming identifier presence field of a target AP MLD, wherein the roaming identifier presence field of the target AP MLD is used to indicate whether a roaming identifier field of the target AP MLD exists in the first element of the first frame, and the roaming identifier field of the target AP MLD is used to indicate a roaming identifier of the target AP MLD;

[0118] In the case where the roaming flag presence field of the target AP MLD is used to indicate that the roaming flag field of the target AP MLD does not exist in the first element of the first frame, the first frame is used to add or delete a first-category link; and / or in the case where the roaming flag presence field of the target AP MLD is used to indicate that the roaming flag field of the target AP MLD exists in the first element of the first frame, the first frame is used to add or delete a second-category link.

[0119] In some embodiments, the first element is a Reconfiguration Multi-Link element. In this case, for example, the first frame is a Multi-Link Operation Update Request frame.

[0120] For example, the multi-link operation update request frame sent by the non-AP MLD can be as shown in Figure 17, where the reconfiguration multi-link element includes N link information fields, where each link information field in the N link information fields includes a site control field and a site information field, and the site control field includes an operation update type field and a roaming identifier existence field of the target AP MLD. The operation update type field is used to indicate the addition of a link, or the operation update type field is used to indicate the deletion of a link, and the roaming identifier existence field of the target AP MLD is used to indicate whether the roaming identifier field of the target AP MLD exists in the site information field.

[0121] As shown in Figure 17, the Operation Update Type field occupies 4 bits; for example, a value of 0000 indicates adding a link, and a value of 0001 indicates deleting a link; or, a value of 0001 indicates adding a link, and a value of 0000 indicates deleting a link; or, other values ​​indicate adding or deleting a link, respectively. Alternatively, the Operation Update Type field occupies 1 bit; for example, a value of 0 indicates adding a link, and a value of 1 indicates deleting a link; or, a value of 1 indicates adding a link, and a value of 0 indicates deleting a link.

[0122] As shown in Figure 17, the roaming flag presence field of the target AP MLD occupies one bit. For example, a value of 0 indicates that the roaming flag field of the target AP MLD exists in the site information field, and a value of 1 indicates that the roaming flag field of the target AP MLD does not exist in the site information field. Alternatively, a value of 1 indicates that the roaming flag field of the target AP MLD exists in the site information field, and a value of 0 indicates that the roaming flag field of the target AP MLD does not exist in the site information field.

[0123] As shown in FIG17 , the site control field also includes some other fields, such as a Non Simultaneous Transmit and Receive (NSTR) link pair existence field and an NSTR bitmap size field.

[0124] As shown in Figure 17, the site information field also includes some other fields, such as an operation parameter field and an NSTR indication bitmap field, wherein the existence indication field in the operation parameter field includes the Medium Access Control protocol data unit (MPDU) maximum length existence field and the Aggregate Media Access Control Service Data Unit (A-MSDU) maximum length existence field, and the operation parameter information field in the operation parameter field includes the MPDU maximum length field and the A-MSDU maximum length field.

[0125] In some embodiments, the first element is a Basic Multi-Link element. In this case, for example, the first frame is a frame used to add or delete a roaming link. That is, the first frame is a frame specifically used to add or delete a roaming link. Of course, the first frame can also be other frames, and this embodiment of the present application is not limited to this.

[0126] For example, a new frame for adding or deleting a roaming link is added (for example, the value of the protected EHT action subclass field is 10), as shown in Figure 18 . In this frame for adding or deleting a roaming link, a Basic Multi-Link element is used instead of a Reconfiguration Multi-Link element (the roaming function is similar to the association function, and the Basic Multi-Link element is used in the association frame). As shown in Figure 18 , the Basic Multi-Link element includes N link information fields, where each of the N link information fields includes a site control field and a site information field. The site control field includes a roaming identifier presence field of the target AP MLD. The roaming identifier presence field of the target AP MLD is used to indicate whether the roaming identifier field of the target AP MLD is present in the site information field.

[0127] As shown in Figure 18, the roaming flag presence field of the target AP MLD occupies one bit. For example, a value of 0 indicates that the roaming flag field of the target AP MLD exists in the site information field, and a value of 1 indicates that the roaming flag field of the target AP MLD does not exist in the site information field. Alternatively, a value of 1 indicates that the roaming flag field of the target AP MLD exists in the site information field, and a value of 0 indicates that the roaming flag field of the target AP MLD does not exist in the site information field.

[0128] As shown in Figure 18, the common information field in the basic multi-link element may include at least one of the following: a common information length field, an MLD MAC address field, a link identification information field, a BSS parameter change count field, a media synchronization delay information field, an Enhanced Multi-Link (EML) capability field, an MLD capability and operation field, an AP MLD identification field, and an extended MLD capability and operation field.

[0129] As shown in Figure 18, the site control field in the basic multilink element may also include some other fields, such as the time synchronization function (TSF) offset existence field, the delivery traffic indication message (DTIM) information existence field, and the NSTR bitmap size field.

[0130] As shown in FIG18 , the site information field in the basic multilink element may also include some other fields, such as a TSF offset field, a DTIM information field, and an NSTR indication bitmap field.

[0131] In some embodiments, the first field takes a first value to indicate that the first field is a reserved field and that the first frame is used to add or delete a local link; and / or the first field takes a second value to indicate a roaming identifier of the target AP MLD and that the first frame is used to add or delete a roaming link. Specifically, for example, the first value is zero and the second value is non-zero. Of course, the first and second values ​​may also be other values, and this is not limited in the present embodiment.

[0132] In some embodiments, the first frame is a Multi-Link Operation Update Request frame. That is, the existing Multi-Link Operation Update Request frame is used to add / delete links, and a reserved field in the Site Information field of the Reconfigured Multi-Link Element is used to indicate the Target AP MLD Roaming ID, as shown in FIG19 . In this manner, a value of 0 cannot be a valid value for the Target AP MLD Roaming ID. A value of 0 is used to indicate that the field is a reserved field, meaning that the frame is used to add or delete a local link. A non-zero value indicates both the Target AP MLD Roaming ID and the frame to add or delete a roaming link.

[0133] In some embodiments, the first field is an operation update type field; wherein, the operation update type field is used to indicate that the first frame is used to add a first type link, or, or, the operation update type field is used to indicate that the first frame is used to delete a first type link, or, the operation update type field is used to indicate that the first frame is used to add a second type link, or, the operation update type field is used to indicate that the first frame is used to delete a second type link.

[0134] In some embodiments, the first frame is a multi-link operation update request frame (Multi-Link Operation Update Request).

[0135] For example, as shown in Figures 17 or 19, the Operation Update Type field occupies 4 bits; wherein the value 0000 indicates an Operation Parameter Update, the value 0001 indicates deletion of a local link, the value 0010 indicates addition of a local link, the value 0011 indicates deletion of a roaming link, and the value 0100 indicates addition of a roaming link; or, the value 0000 indicates an Operation Parameter Update, the value 0001 indicates deletion of a roaming link, the value 0010 indicates addition of a roaming link, the value 0011 indicates deletion of a local link, and the value 0100 indicates addition of a local link. Of course, other values ​​may also be used to indicate addition or deletion of a local link or addition or deletion of a roaming link.

[0136] For another example, a Multi-Link Operation Update Request frame is used to add / delete links, and a new Operation Update Type value is added to indicate adding or deleting a roaming link. For example, 0 indicates an Operation Parameter Update, 1 indicates deleting a local link, 2 indicates adding a local link, 3 indicates deleting a roaming link, and 4 indicates adding a roaming link.

[0137] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, a target link corresponding to a first Non-AP STA in the Non-AP MLD is in the same frequency band as a source link.

[0138] For example, as shown in FIG11 , during roaming between AP MLD 1 and AP MLD 2 within the logical AP MLD, the target link (i.e., link 2) corresponding to STA 2 and the source link (i.e., link 1) are in the same frequency band (i.e., 2.4 GHz).

[0139] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, a target link and a source link corresponding to a first Non-AP STA in the Non-AP MLD are in different frequency bands.

[0140] For example, as shown in Figure 12, during roaming between AP MLD 1 and AP MLD 2 within the logical AP MLD, the target link (i.e., link 2) corresponding to STA 2 and the source link (i.e., link 1) are in different frequency bands. The target link (i.e., link 2) corresponding to STA 2 is at 6 GHz, and the source link (i.e., link 1) corresponding to STA 2 is at 5 GHz.

[0141] For example, during non-AP MLD roaming, the source AP and target AP (i.e., the old and new APs) belong to different AP MLDs but the same logical AP MLD. If a new link (i.e., the target link) is added before the old link (i.e., the source link) is deleted, the new link (i.e., the target link) and the old link (i.e., the source link) coexist for a period of time. The new link (i.e., the target link) and the old link (i.e., the source link) may be links in the same frequency band and channel, or links in the same frequency band but different channels.

[0142] In some embodiments, during roaming between different AP MLDs within the logical AP MLD in the Non-AP MLD, if a source link and a target link corresponding to a first non-AP STA in the Non-AP MLD are links of the same frequency band but different channels, and both the source link and the target link corresponding to the first non-AP STA are in an enabled state, the first non-AP STA performs the following operations:

[0143] If the first non-AP STA has resided on the target link for more than a first duration without obtaining a transmission opportunity, and the target AP corresponding to the target link has not initiated a transmission with the first non-AP STA, the first non-AP STA switches from the target link to the source link;

[0144] and / or,

[0145] If the first Non-AP STA has resided on the source link for more than the second duration without obtaining a transmission opportunity, and the source AP corresponding to the source link has not initiated transmission with the first Non-AP STA, the first Non-AP STA switches from the source link to the target link.

[0146] Specifically, the source link and the target link corresponding to the first Non-AP STA are both in an enabled state, that is, the first Non-AP STA is connected to the source link and the target link at the same time.

[0147] In some embodiments, the first duration is the sum of the duration of the first timer and a distributed inter-frame spacing (DIFS); wherein the first timer is started when the first Non-AP STA switches to the target link, and the first timer is stopped when the first Non-AP STA receives a beacon frame within the first duration.

[0148] For example, the duration of the first timer is less than or equal to 72 microseconds.

[0149] In some embodiments, the duration of the first timer and the start and stop conditions of the first timer are agreed upon by a protocol, or the duration of the first timer and the start and stop conditions of the first timer are configured by a source AP MLD, or the duration of the first timer and the start and stop conditions of the first timer are configured by a target AP MLD.

[0150] In some embodiments, the second duration is the sum of the duration of the second timer and DIFS;

[0151] The second timer is started when the first Non-AP STA switches to the source link, and the second timer is stopped when the first Non-AP STA receives a beacon frame within the second time period.

[0152] For example, the duration of the second timer is less than or equal to 72 microseconds.

[0153] In some embodiments, the duration of the second timer and the start and stop conditions of the second timer are agreed upon by a protocol, or the duration of the second timer and the start and stop conditions of the second timer are configured by a source AP MLD, or the duration of the second timer and the start and stop conditions of the second timer are configured by a target AP MLD.

[0154] In some embodiments, the DIFS is agreed upon by a protocol, or the DIFS is configured by the source AP MLD, or the DIFS is configured by the target AP MLD.

[0155] For example, if the new link and the old link are links in the same frequency band but different operating channels (primary channels), the station may lose media synchronization when switching channels because it has not received the most recent beacon frame. To address this issue, as shown in Figure 20, STA3 is required to perform the following operations: When STA 3 switches from link 1 to link 2, STA 3 starts a first timer and performs a clear channel assessment (CCA) within a first duration. If a beacon frame is received within the first duration, the first timer is stopped and channel contention is performed normally. If no beacon frame is received, channel contention is performed normally after the first timer expires. Furthermore, if STA 3 has not obtained a transmission opportunity after staying on link 2 for more than a first duration (for example, the duration of the first timer + DIFS), and AP 2 corresponding to link 2 has not initiated a transmission with STA3, STA 3 switches from link 2 to link 1 again. To address this issue, as shown in Figure 20, STA3 is required to perform the following operations: when STA 3 switches from link 2 to link 1, STA 3 starts a second timer, and performs a clear channel assessment (CCA) within the second duration. If a beacon frame is received within the second duration, STA 3 stops the second timer and performs channel contention normally. If no beacon frame is received, STA 3 waits for the second timer to expire before performing channel contention normally. Furthermore, if STA 3 has resided on link 1 for more than the second duration (for example, the duration of the second timer + DIFS) without obtaining a transmission opportunity, and the AP1 corresponding to link 1 has not initiated transmission with STA3, STA 3 switches from link 1 to link 2 again.

[0156] In some embodiments, during roaming between different AP MLDs within the logical AP MLD in the Non-AP MLD, if a source link and a target link corresponding to a first Non-AP STA in the Non-AP MLD are links of the same frequency band and the same channel, and both the source link and the target link corresponding to the first Non-AP STA are in an enabled state, the first Non-AP STA adjusts the transmit power of an overlapping area. After the transmit power adjustment, both the AP corresponding to the source link (i.e., the source AP) and the AP corresponding to the target link (i.e., the target AP) can receive the uplink signal of the first Non-AP STA. The overlapping area is an area that can be covered by both the AP corresponding to the source link (i.e., the source AP) and the AP corresponding to the target link (i.e., the target AP).

[0157] For example, if the new link (i.e., the target link) and the old link (i.e., the source link) are links with the same frequency band and the same channel, the transmission power of STA3 in the overlapping area needs to be adjusted so that AP1 (source AP) and AP2 (target AP) can both receive STA3's signal (because STA3 can receive the downlink signals of two APs in the overlapping area, but both APs may not be able to receive STA3's uplink signal) to ensure that when STA3 obtains the transmission opportunity, the BSS where the two APs are located can correctly set the Network Allocation Vector (NAV), that is, to avoid the conflict shown in Figure 21.

[0158] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, if the source link and the target link corresponding to a first Non-AP STA in the Non-AP MLD are links of the same frequency band and the same channel, and both the source link and the target link corresponding to the first Non-AP STA are in an enabled state, the AP corresponding to the source link (i.e., the source AP) and the AP corresponding to the target link (i.e., the target AP) coordinate downlink transmission for the first Non-AP STA.

[0159] For example, if the new link (i.e., the target link) and the old link (i.e., the source link) are links with the same frequency band and the same channel, when transmitting to the roaming site (i.e., STA3), the new and old APs (i.e., AP1 and AP2) need to coordinate downlink to avoid the conflict shown in Figure 22. Specifically, this can be achieved using the joint transmission (JT) and / or coordinated orthogonal frequency division multiple access (C-OFDMA) and / or transmission opportunity sharing (TXOP Sharing, TXS) mechanism in the multi-AP collaboration mode.

[0160] In some embodiments, the target AP MLD within the logical AP MLD synchronizes the capability information and / or operating parameter information of the non-AP MLD with the source AP MLD. That is, during non-AP MLD roaming, the target AP MLD within the logical AP MLD synchronizes the non-AP MLD related information with the source AP MLD.

[0161] Specifically, similar to establishing an association between a non-AP MLD and an AP MLD, during non-AP MLD roaming, the new AP MLD (i.e., the target AP MLD) needs to understand the non-AP MLD's capability information and operating parameters, specifically including multi-link device (MLD)-level capability information and operating parameters, and link-level capability information and operating parameters. This information can be synchronized from the old AP MLD (i.e., the source AP MLD) to the new AP MLD (i.e., the target AP MLD) via backhaul, and synchronization can occur at different times.

[0162] In some embodiments, the capability information and / or operating parameter information of the Non-AP MLD includes at least one of the following:

[0163] MLD-level capability information and / or operating parameter information, link-level capability information and / or operating parameter information.

[0164] In some embodiments, the MLD-level capability information and / or operating parameter information includes at least one of the following: a first information set, a second information set, a block acknowledgement (BA) parameter, and flow identifier-to-link mapping information;

[0165] The first information set includes at least one of the following: pairwise transient key security association (PTKSA), MLD MAC address, enhanced multi-link (EML) capability information, MLD capabilities and operations, and extended MLD capabilities and operations;

[0166] The second information set includes at least one of the following: a stream classification service (SCS) and a mirrored stream classification service (MSCS).

[0167] In some embodiments, the first information set is synchronized from the source AP MLD to all AP MLDs within the logical AP MLD by the logical AP MLD when the Non-AP MLD establishes an association with the logical AP MLD; or, the first information set is synchronized from the source AP MLD to the target AP MLD when the Non-AP MLD adds a roaming link.

[0168] For example, a portion of the capability information and operation parameter information (i.e., the first information set) of the multi-link device level of the Non-AP MLD, for example, the first information set includes at least one of the following: PTKSA, MLD MAC address, EML capability (including enhanced multi-link multi-radio (EMLMR) and / or enhanced multi-link single radio (EMLSR)), MLD capability and operation, and extended MLD capability and operation. For example, the first information set can be pre-synchronized, that is, when the Non-AP MLD establishes an association with the logical AP MLD corresponding to the roaming domain through a certain AP MLD (physical AP MLD), the logical AP MLD controls the AP MLD to synchronize the first information set to all AP MLDs in the logical AP MLD (in this way, the backhaul link load is higher and there is a certain redundancy, but the time consumption of the backhaul link during roaming can be reduced). For another specific example, when a new link (roaming link) is added to the Non-AP MLD, the first information set can be synchronized from the old AP MLD (source AP MLD) to the new AP MLD (target AP MLD) (in this way, the return link redundancy is less, but the time consumption of the return link during roaming is slightly higher).

[0169] In some embodiments, the second information set is synchronized from the source AP MLD to all AP MLDs within the logical AP MLD by the logical AP MLD after the Non-AP MLD establishes an association with the logical AP MLD; or, the second information set is synchronized from the source AP MLD to the target AP MLD by the Non-AP MLD when a roaming link is added.

[0170] For example, a portion of the multi-link device-level operating parameter information (i.e., the second information set) of the Non-AP MLD includes at least one of the following: Stream Classification Service (SCS) and Mirrored Stream Classification Service (MSCS). Interaction between the Non-AP MLD and the logical AP MLD is optional only after the Non-AP MLD establishes an association. Therefore, similarly, during SCS negotiation and / or MSCS negotiation, the logical AP MLD can control the AP MLD to synchronize the operating parameters to all AP MLDs in the logical AP MLD. Alternatively, when a new link (roaming link) is added to the Non-AP MLD, the old AP MLD (source AP MLD) can synchronize the operating parameters to the new AP MLD (target AP MLD).

[0171] In some embodiments, the BA parameter is synchronized by the source AP MLD to the target AP MLD when the Non-AP MLD adds a roaming link.

[0172] For example, some multi-link device-level operational parameter information for Non-AP MLD, such as block acknowledgment (BA) parameters, and the specific parameter values ​​involved (e.g., the Receive Reordering Buffer Control per TA / TID WinStart value and / or the Scoreboard Context Control WinStart value for each transport address and each flow identifier) ​​are updated as interactions progress. That is, when roaming occurs, the values ​​of these parameters are different from those during BA negotiation (i.e., the exchange of ADDBA Request and ADDBA Response frames). This operational parameter information may be frequently updated and is not suitable for synchronization during related negotiations (e.g., BA negotiation). Furthermore, because this operational parameter information is multi-link device-level information, it should not be renegotiated during roaming for Non-AP MLD. Therefore, it should be synchronized from the old AP MLD (source AP MLD) to the new AP MLD (target AP MLD) when a new link (roaming link) is added to the Non-AP MLD.

[0173] In some embodiments, the mapping information of the flow identifier to the link is broadcast by the target AP MLD when the Non-AP MLD adds a roaming link, or the mapping information of the flow identifier to the link is associated with all default flow identifiers TID, or the mapping information of the flow identifier to the link is determined by negotiation between the Non-AP MLD and the target AP MLD.

[0174] For example, some multi-link device-level operational parameter information of the Non-AP MLD, such as the TID-to-link mapping, is related to the current existence or non-existence or enabled or disabled status of the link and is not suitable for pre-synchronization. Therefore, when the Non-AP MLD adds a new link (roaming link), it should adopt the mandatory mapping advertised by the target AP MLD (if any). Alternatively, it should use the default mapping of all traffic identifiers (TIDs) in the upstream and downstream to the new link. Alternatively, the old AP MLD (the source AP MLD) can set the TID-to-link mapping element field in the Add Roaming Link Response frame sent to the Non-AP MLD based on information obtained from the new AP MLD (the target AP MLD), thereby suggesting a specific TID-to-link mapping. The Non-AP MLD then explicitly negotiates the TID-to-link mapping with the new AP MLD (the target AP MLD) based on the suggestion.

[0175] In some embodiments, the link-level capability information and / or operating parameter information includes at least one of the following: a third information set, a fourth information set, a fifth information set;

[0176] The third information set includes at least one of the following: a station MAC address, non-simultaneous transmit and receive (NSTR) link pair information, a roaming identifier of a target AP MLD, a link identifier, a link capability information field, link high throughput (HT) capability, link very high throughput (VHT) capability, link high efficiency (HE) capability, link extreme high throughput (EHT) capability, link HT operating parameters, link VHT operating parameters, link HE operating parameters, and link EHT operating parameters;

[0177] The fourth information set includes at least one of the following: a group temporary key (Group Temporal Key, GTK), an integrity group temporary key (Integrity Group Temporal Key, IGTK), and a beacon integrity group temporary key (Beacon Integrity Group Temporal Key, BIGTK);

[0178] The fifth information set includes at least one of the following: target wake time (TWT), restricted target wake time (R-TWT).

[0179] In some embodiments, the third information set is synchronized by the source AP MLD to the target AP MLD when the Non-AP MLD adds a roaming link.

[0180] For example, a portion of the link-level capability information and operating parameter information (i.e., the third information set) of the Non-AP MLD includes at least one of the following: the station MAC address, NSTR link pair information (including whether a non-simultaneous transceiver link pair exists, the non-simultaneous transceiver bitmap size, and the non-simultaneous transceiver indication bitmap), the target AP MLD's roaming identifier, link identifier, link capability information field, link HT capability, link VHT capability, link HE capability, link EHT capability, link HT operating parameters, link VHT operating parameters, link HE operating parameters, and link EHT operating parameters. The third information set should be synchronized from the old AP MLD (source AP MLD) to the new AP MLD (target AP MLD) when a new link (roaming link) is added to the Non-AP MLD.

[0181] In some embodiments, the fourth information set is obtained by the source AP MLD from the target AP MLD and sent to the Non-AP MLD, or the fourth information set is sent by the target AP MLD to the Non-AP MLD through a group key handshake protocol after the Non-AP MLD adds a roaming link.

[0182] For example, a portion of the link-level operational parameter information of the Non-AP MLD (i.e., the fourth information set), such as the fourth information set including at least one of the following: a group transient key (GTK), an integrity group transient key (IGTK), and a beacon integrity group transient key (BIGTK), should be obtained by the old AP MLD (source AP MLD) from the new AP MLD (target AP MLD) and carried in a response frame for adding a roaming link sent to the Non-AP MLD; or, after completing the addition of the roaming link, the new AP MLD (target AP MLD) should send the fourth information set to the Non-AP MLD through the group key handshake protocol.

[0183] A portion of the link-level operating parameter information of the Non-AP MLD (ie, the fifth information set), for example, the fifth information set includes at least one of the following: TWT, R-TWT. The fifth information set should be that the old AP MLD (source AP MLD) sends a negotiation request with the new AP MLD (target AP MLD) instead of the Non-AP MLD based on the TWT and / or R-TWT that have been negotiated with the Non-AP MLD on the current link, and carries the received TWT and / or R-TWT negotiation response information of the new AP MLD (target AP MLD) in the response frame for adding a roaming link sent to the Non-AP MLD; or the Non-AP MLD carries the TWT and / or R-TWT negotiation request information in the request frame for adding a roaming link, and the old AP MLD (source AP MLD) forwards the TWT and / or R-TWT negotiation request information to the new AP MLD (target AP MLD), and carries the TWT and / or R-TWT negotiation response information received from the new AP MLD (target AP MLD) in the response frame for adding a roaming link sent to the Non-AP MLD.

[0184] Therefore, in an embodiment of the present application, when a Non-AP MLD roams between different AP MLDs within a logical AP MLD, the Non-AP MLD can add or delete a first-type link based on the first field in the first frame sent by the AP MLD, or the Non-AP MLD can add or delete a second-type link based on the first field in the first frame sent by the AP MLD. This can achieve uninterrupted roaming or seamless roaming between different AP MLDs within the logical AP MLD, thereby improving the roaming performance of the Non-AP MLD between different AP MLDs within the logical AP MLD.

[0185] The above text, in combination with Figures 10 to 22, describes in detail the method embodiment of the present application. The following text, in combination with Figures 23 to 27, describes in detail the device embodiment of the present application. It should be understood that the device embodiment and the method embodiment correspond to each other, and similar descriptions can refer to the method embodiment.

[0186] FIG23 shows a schematic block diagram of a Non-AP MLD 300 according to an embodiment of the present application. The Non-AP MLD 300 roams between different AP MLDs within a logical AP MLD. As shown in FIG23 , the Non-AP MLD 300 includes:

[0187] The communication unit 310 is configured to send a first frame;

[0188] The first frame includes a first field, and the first field is used to indicate that the first frame is used to add or delete a first type of link, or the first field is used to indicate that the first frame is used to add or delete a second type of link.

[0189] In some embodiments, the first field is a roaming identifier presence field of a target AP MLD, wherein the roaming identifier presence field of the target AP MLD is used to indicate whether a roaming identifier field of the target AP MLD exists in the first element of the first frame, and the roaming identifier field of the target AP MLD is used to indicate a roaming identifier of the target AP MLD;

[0190] In the case where the roaming flag presence field of the target AP MLD is used to indicate that the roaming flag field of the target AP MLD does not exist in the first element of the first frame, the first frame is used to add or delete a first-category link; and / or in the case where the roaming flag presence field of the target AP MLD is used to indicate that the roaming flag field of the target AP MLD exists in the first element of the first frame, the first frame is used to add or delete a second-category link.

[0191] In some embodiments, the first element is a reconfiguration multilink element, or the first element is a basic multilink element.

[0192] In some embodiments, when the first element is a reconfigure multilink element, the first frame is a multilink operation update request frame.

[0193] In some embodiments, when the first element is a basic multi-link element, the first frame is a frame used to add or delete a roaming link.

[0194] In some embodiments, the first field takes a first value to indicate that the first field is a reserved field, and the first frame is used to add or delete a local link; and / or, the first field takes a second value to indicate a roaming identifier of a target AP MLD, and the first frame is used to add or delete a roaming link.

[0195] In some embodiments, the first value is zero and the second value is non-zero.

[0196] In some embodiments, the first field is an operation update type field;

[0197] Among them, the operation update type field is used to indicate that the first frame is used to add a first type of link, or, or, the operation update type field is used to indicate that the first frame is used to delete a first type of link, or, the operation update type field is used to indicate that the first frame is used to add a second type of link, or, the operation update type field is used to indicate that the first frame is used to delete a second type of link.

[0198] In some embodiments, the first frame is a multi-link operation update request frame.

[0199] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, the Non-AP MLD performs link switching in a first manner or a second manner; wherein the first manner is to first add a target link and then delete a source link, and the second manner is to first delete a source link and then add a target link.

[0200] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, a target link and a source link corresponding to a first non-AP STA in the Non-AP MLD are in the same frequency band.

[0201] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, a target link and a source link corresponding to a first Non-AP STA in the Non-AP MLD are in different frequency bands.

[0202] In some embodiments, during roaming between different AP MLDs within the logical AP MLD in the Non-AP MLD, if a source link and a target link corresponding to a first non-AP STA in the Non-AP MLD are links of the same frequency band but different channels, and both the source link and the target link corresponding to the first non-AP STA are in an enabled state, the first non-AP STA performs the following operations:

[0203] If the first Non-AP STA has resided on the target link for more than a first duration without obtaining a transmission opportunity, and the target access point AP corresponding to the target link has not initiated a transmission with the first Non-AP STA, the first Non-AP STA switches from the target link to the source link; and / or,

[0204] If the first Non-AP STA has resided on the source link for more than the second duration without obtaining a transmission opportunity, and the source AP corresponding to the source link has not initiated transmission with the first Non-AP STA, the first Non-AP STA switches from the source link to the target link.

[0205] In some embodiments, the first duration is the sum of the duration of the first timer and the distributed interframe space DIFS;

[0206] The first timer is started when the first Non-AP STA switches to the target link, and the first timer is stopped when the first Non-AP STA receives a beacon frame within the first duration.

[0207] In some embodiments, the second duration is the sum of the duration of the second timer and DIFS;

[0208] The second timer is started when the first Non-AP STA switches to the source link, and the second timer is stopped when the first Non-AP STA receives a beacon frame within the second time period.

[0209] In some embodiments, during roaming between different AP MLDs within the logical AP MLD in the Non-AP MLD, if a source link and a target link corresponding to a first Non-AP STA in the Non-AP MLD are links of the same frequency band and the same channel, and both the source link and the target link corresponding to the first Non-AP STA are in an enabled state, the first Non-AP STA adjusts the transmit power of an overlapping area. After the transmit power adjustment, both the AP corresponding to the source link and the AP corresponding to the target link can receive the uplink signal of the first Non-AP STA. The overlapping area is an area that can be covered by both the AP corresponding to the source link and the AP corresponding to the target link.

[0210] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, if a source link and a target link corresponding to a first Non-AP STA in the Non-AP MLD are links of the same frequency band and the same channel, and both the source link and the target link corresponding to the first Non-AP STA are in an enabled state, the AP corresponding to the source link and the AP corresponding to the target link coordinate downlink transmission for the first Non-AP STA.

[0211] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0212] It should be understood that the Non-AP MLD 300 according to the embodiment of the present application may correspond to the Non-AP MLD in the method embodiment of the present application, and the above-mentioned and other operations and / or functions of each unit in the Non-AP MLD 300 are respectively for implementing the corresponding process of the Non-AP MLD in the method 200 shown in Figure 10. For the sake of brevity, they are not further described here.

[0213] FIG24 shows a schematic block diagram of an AP MLD 400 according to an embodiment of the present application. The AP MLD 400 is a logical AP MLD. As shown in FIG24 , the AP MLD 400 includes:

[0214] The communication unit 410 is configured to receive a first frame sent by a non-access point multi-link device Non-AP MLD;

[0215] The Non-AP MLD roams between different AP MLDs within the logical AP MLD.

[0216] The first frame includes a first field, and the first field is used to indicate that the first frame is used to add or delete a first type of link, or the first field is used to indicate that the first frame is used to add or delete a second type of link.

[0217] In some embodiments, the first field is a roaming identifier presence field of a target AP MLD, wherein the roaming identifier presence field of the target AP MLD is used to indicate whether a roaming identifier field of the target AP MLD exists in the first element of the first frame, and the roaming identifier field of the target AP MLD is used to indicate a roaming identifier of the target AP MLD;

[0218] In the case where the roaming flag presence field of the target AP MLD is used to indicate that the roaming flag field of the target AP MLD does not exist in the first element of the first frame, the first frame is used to add or delete a first-category link; and / or in the case where the roaming flag presence field of the target AP MLD is used to indicate that the roaming flag field of the target AP MLD exists in the first element of the first frame, the first frame is used to add or delete a second-category link.

[0219] In some embodiments, the first element is a reconfiguration multilink element, or the first element is a basic multilink element.

[0220] In some embodiments, when the first element is a reconfigure multilink element, the first frame is a multilink operation update request frame.

[0221] In some embodiments, when the first element is a basic multi-link element, the first frame is a frame used to add or delete a roaming link.

[0222] In some embodiments, the first field takes a first value to indicate that the first field is a reserved field, and the first frame is used to add or delete a local link; and / or, the first field takes a second value to indicate a roaming identifier of a target AP MLD, and the first frame is used to add or delete a roaming link.

[0223] In some embodiments, the first value is zero and the second value is non-zero.

[0224] In some embodiments, the first field is an operation update type field;

[0225] Among them, the operation update type field is used to indicate that the first frame is used to add a first type of link, or, or, the operation update type field is used to indicate that the first frame is used to delete a first type of link, or, the operation update type field is used to indicate that the first frame is used to add a second type of link, or, the operation update type field is used to indicate that the first frame is used to delete a second type of link.

[0226] In some embodiments, the first frame is a multi-link operation update request frame.

[0227] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, the Non-AP MLD performs link switching in a first manner or a second manner; wherein the first manner is to first add a target link and then delete a source link, and the second manner is to first delete a source link and then add a target link.

[0228] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, a target link and a source link corresponding to a first non-AP STA in the Non-AP MLD are in the same frequency band.

[0229] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, a target link and a source link corresponding to a first Non-AP STA in the Non-AP MLD are in different frequency bands.

[0230] In some embodiments, during roaming between different AP MLDs within the logical AP MLD in the Non-AP MLD, if a source link and a target link corresponding to a first non-AP STA in the Non-AP MLD are links of the same frequency band but different channels, and both the source link and the target link corresponding to the first non-AP STA are in an enabled state, the first non-AP STA performs the following operations:

[0231] If the first Non-AP STA has resided on the target link for more than a first duration without obtaining a transmission opportunity, and the target access point AP corresponding to the target link has not initiated a transmission with the first Non-AP STA, the first Non-AP STA switches from the target link to the source link; and / or,

[0232] If the first Non-AP STA has resided on the source link for more than the second duration without obtaining a transmission opportunity, and the source AP corresponding to the source link has not initiated transmission with the first Non-AP STA, the first Non-AP STA switches from the source link to the target link.

[0233] In some embodiments, the first duration is the sum of the duration of the first timer and the distributed interframe space DIFS;

[0234] The first timer is started when the first Non-AP STA switches to the target link, and the first timer is stopped when the first Non-AP STA receives a beacon frame within the first duration.

[0235] In some embodiments, the second duration is the sum of the duration of the second timer and DIFS;

[0236] The second timer is started when the first Non-AP STA switches to the source link, and the second timer is stopped when the first Non-AP STA receives a beacon frame within the second time period.

[0237] In some embodiments, during roaming between different AP MLDs within the logical AP MLD in the Non-AP MLD, if a source link and a target link corresponding to a first Non-AP STA in the Non-AP MLD are links of the same frequency band and the same channel, and both the source link and the target link corresponding to the first Non-AP STA are in an enabled state, the first Non-AP STA adjusts the transmit power of an overlapping area. After the transmit power adjustment, both the AP corresponding to the source link and the AP corresponding to the target link can receive the uplink signal of the first Non-AP STA. The overlapping area is an area that can be covered by both the AP corresponding to the source link and the AP corresponding to the target link.

[0238] In some embodiments, during roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, if a source link and a target link corresponding to a first Non-AP STA in the Non-AP MLD are links of the same frequency band and the same channel, and both the source link and the target link corresponding to the first Non-AP STA are in an enabled state, the AP corresponding to the source link and the AP corresponding to the target link coordinate downlink transmission for the first Non-AP STA.

[0239] In some embodiments, the communication unit may be a communication interface or a transceiver, or an input / output interface of a communication chip or a system on chip. The processing unit may be one or more processors.

[0240] It should be understood that the AP MLD 400 according to the embodiment of the present application may correspond to the AP MLD in the method embodiment of the present application, and the above-mentioned and other operations and / or functions of each unit in the AP MLD 400 are respectively for implementing the corresponding process of the AP MLD in the method 200 shown in Figure 10. For the sake of brevity, they are not further described here.

[0241] Figure 25 is a schematic structural diagram of a communication device 500 provided in an embodiment of the present application. The communication device 500 shown in Figure 25 includes a processor 510, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0242] In some embodiments, as shown in FIG25 , the communication device 500 may further include a memory 520. The processor 510 may call and execute a computer program from the memory 520 to implement the method in the embodiment of the present application.

[0243] The memory 520 may be a separate device independent of the processor 510 , or may be integrated into the processor 510 .

[0244] In some embodiments, as shown in FIG. 25 , the communication device 500 may further include a transceiver 530 , and the processor 510 may control the transceiver 530 to communicate with other devices. Specifically, the transceiver 530 may send information or data to other devices, or receive information or data sent by other devices.

[0245] The transceiver 530 may include a transmitter and a receiver. The transceiver 530 may further include an antenna, and the number of antennas may be one or more.

[0246] In some embodiments, the processor 510 may implement the functions of a processing unit in a Non-AP MLD, or the processor 510 may implement the functions of a processing unit in an AP MLD, which will not be described in detail here for the sake of brevity.

[0247] In some embodiments, the transceiver 530 may implement the function of a communication unit in the Non-AP MLD, which will not be described in detail here for the sake of brevity.

[0248] In some embodiments, the transceiver 530 may implement the functions of the communication unit in the AP MLD, which will not be described in detail here for the sake of brevity.

[0249] In some embodiments, the communication device 500 may specifically be the AP MLD of the embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the AP MLD in each method of the embodiment of the present application, which will not be described here for the sake of brevity.

[0250] In some embodiments, the communication device 500 may specifically be the Non-AP MLD of the embodiment of the present application, and the communication device 500 may implement the corresponding processes implemented by the Non-AP MLD in each method of the embodiment of the present application, which will not be described here for the sake of brevity.

[0251] Figure 26 is a schematic structural diagram of an apparatus according to an embodiment of the present application. The apparatus 600 shown in Figure 26 includes a processor 610, which can call and execute a computer program from a memory to implement the method according to the embodiment of the present application.

[0252] In some embodiments, as shown in FIG26 , the apparatus 600 may further include a memory 620. The processor 610 may call and execute a computer program from the memory 620 to implement the method in the embodiment of the present application.

[0253] The memory 620 may be a separate device independent of the processor 610 , or may be integrated into the processor 610 .

[0254] In some embodiments, the processor 610 may implement the functions of a processing unit in a Non-AP MLD, or the processor 610 may implement the functions of a processing unit in an AP MLD, which will not be described in detail here for the sake of brevity.

[0255] In some embodiments, the apparatus 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips. Optionally, the processor 610 may be located inside or outside the chip.

[0256] In some embodiments, the input interface 630 may implement the function of a communication unit in a Non-AP MLD, or the input interface 630 may implement the function of a communication unit in an AP MLD.

[0257] In some embodiments, the apparatus 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips. Optionally, the processor 610 may be located inside or outside the chip.

[0258] In some embodiments, the output interface 640 may implement the function of a communication unit in a Non-AP MLD, or the output interface 640 may implement the function of a communication unit in an AP MLD.

[0259] In some embodiments, the device may be applied to the AP MLD in the embodiments of the present application, and the device may implement the corresponding processes implemented by the AP MLD in the various methods in the embodiments of the present application, which will not be described in detail here for the sake of brevity.

[0260] In some embodiments, the device can be applied to the Non-AP MLD in the embodiments of the present application, and the device can implement the corresponding processes implemented by the Non-AP MLD in each method of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0261] In some embodiments, the device mentioned in the embodiments of the present application may also be a chip, such as a system-on-chip, a system-on-chip, a chip system, or a system-on-chip chip.

[0262] FIG27 is a schematic block diagram of a communication system 700 provided in an embodiment of the present application. As shown in FIG27 , the communication system 700 includes a Non-AP MLD 710 and an AP MLD 720 .

[0263] The Non-AP MLD 710 can be used to implement the corresponding functions implemented by the Non-AP MLD in the above method, and the AP MLD 720 can be used to implement the corresponding functions implemented by the AP MLD in the above method, which will not be described in detail for brevity.

[0264] It should be understood that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above-mentioned method embodiment can be completed by hardware integrated logic circuits in the processor or by software instructions. The above-mentioned processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The various methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of the present application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium mature in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above-mentioned method.

[0265] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0266] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0267] An embodiment of the present application also provides a computer-readable storage medium for storing a computer program.

[0268] In some embodiments, the computer-readable storage medium can be applied to the AP MLD in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the AP MLD in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0269] In some embodiments, the computer-readable storage medium may be applied to the Non-AP MLD in the embodiments of the present application, and the computer program enables a computer to execute the corresponding processes implemented by the Non-AP MLD in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here in detail.

[0270] An embodiment of the present application also provides a computer program product, including computer program instructions.

[0271] In some embodiments, the computer program product can be applied to the AP MLD in the embodiments of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the AP MLD in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0272] In some embodiments, the computer program product can be applied to the Non-AP MLD in the embodiments of the present application, and the computer program instructions enable a computer to execute the corresponding processes implemented by the Non-AP MLD in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0273] The embodiment of the present application also provides a computer program.

[0274] In some embodiments, the computer program can be applied to the AP MLD in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the AP MLD in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here.

[0275] In some embodiments, the computer program can be applied to the Non-AP MLD in the embodiments of the present application. When the computer program runs on a computer, the computer executes the corresponding processes implemented by the Non-AP MLD in the various methods of the embodiments of the present application. For the sake of brevity, they are not further described here.

[0276] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0277] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0278] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0279] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0280] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0281] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. In view of this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0282] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: Applied to a non-access point multi-link device Non-AP MLD, the Non-AP MLD roams between different AP MLDs in a logical access point multi-link device AP MLD, the method comprising: The Non-AP MLD sends a first frame; The first frame includes a first field, and the first field is used to indicate that the first frame is used to add or delete a first type of link, or the first field is used to indicate that the first frame is used to add or delete a second type of link.

2. The method according to claim 1, characterized in that The first field is a roaming identifier existence field of the target AP MLD, wherein the roaming identifier existence field of the target AP MLD is used to indicate whether the roaming identifier field of the target AP MLD exists in the first element of the first frame, and the roaming identifier field of the target AP MLD is used to indicate the roaming identifier of the target AP MLD; In which, when the roaming identification field of the target AP MLD is used to indicate that the roaming identification field of the target AP MLD does not exist in the first element of the first frame, the first frame is used to add or delete a first-category link; and / or, when the roaming identification field of the target AP MLD is used to indicate that the roaming identification field of the target AP MLD exists in the first element of the first frame, the first frame is used to add or delete a second-category link.

3. The method according to claim 2, characterized in that The first element is a reconfiguration multilink element, or the first element is a basic multilink element.

4. The method according to claim 3, characterized in that In the case where the first element is a reconfiguration multilink element, the first frame is a multilink operation update request frame.

5. The method according to claim 3, characterized in that In the case where the first element is a basic multi-link element, the first frame is a frame used to add or delete a roaming link.

6. The method according to claim 1, characterized in that The first field takes a first value to indicate that the first field is a reserved field, and the first frame is used to add or delete a local link; and / or, the first field takes a second value to indicate a roaming identifier of a target AP MLD, and the first frame is used to add or delete a roaming link.

7. The method according to claim 6, characterized in that The first value is zero and the second value is non-zero.

8. The method according to claim 1, characterized in that The first field is an operation update type field; Among them, the operation update type field is used to indicate that the first frame is used to add a first type of link, or, or, the operation update type field is used to indicate that the first frame is used to delete a first type of link, or, the operation update type field is used to indicate that the first frame is used to add a second type of link, or, the operation update type field is used to indicate that the first frame is used to delete a second type of link.

9. The method according to any one of claims 6 to 8, characterized in that The first frame is a multi-link operation update request frame.

10. The method according to any one of claims 1 to 9, characterized in that During roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, the Non-AP MLD performs link switching in a first manner or a second manner; wherein the first manner is to first add a target link and then delete a source link, and the second manner is to first delete a source link and then add a target link.

11. The method according to any one of claims 1 to 10, characterized in that During the roaming process of the Non-AP MLD between different AP MLDs in the logical AP MLD, the target link corresponding to the first non-AP STA in the Non-AP MLD is in the same frequency band as the source link.

12. The method according to any one of claims 1 to 10, characterized in that During the roaming process of the Non-AP MLD between different AP MLDs in the logical AP MLD, a target link and a source link corresponding to a first Non-AP STA in the Non-AP MLD are in different frequency bands.

13. The method according to any one of claims 1 to 12, characterized in that During roaming of the Non-AP MLD between different AP MLDs in the logical AP MLD, if a source link and a target link corresponding to a first Non-AP STA in the Non-AP MLD are links of the same frequency band but different channels, and both the source link and the target link corresponding to the first Non-AP STA are in an enabled state, the first Non-AP STA performs the following operations: If the first Non-AP STA has resided in the target link for more than a first time period without obtaining a transmission opportunity, and the target access point AP corresponding to the target link has not initiated a transmission with the first Non-AP STA, the first Non-AP STA switches from the target link to the source link; and / or, If the first Non-AP STA has resided in the source link for more than a second time period without obtaining a transmission opportunity, and the source AP corresponding to the source link has not initiated transmission with the first Non-AP STA, the first Non-AP STA switches from the source link to the target link.

14. The method according to claim 13, characterized in that The first duration is the sum of the duration of the first timer and the distributed interframe space DIFS; The first timer is started when the first Non-AP STA switches to the target link, and the first timer is stopped when the first Non-AP STA receives a beacon frame within the first duration.

15. The method according to claim 13, characterized in that The second duration is the sum of the duration of the second timer and DIFS; The second timer is started when the first Non-AP STA switches to the source link, and the second timer is stopped when the first Non-AP STA receives a beacon frame within the second duration.

16. The method according to any one of claims 1 to 12, characterized in that During the roaming process of the Non-AP MLD between different AP MLDs within the logical AP MLD, if the source link and the target link corresponding to the first Non-AP STA in the Non-AP MLD are links of the same frequency band and the same channel, and the source link and the target link corresponding to the first Non-AP STA are both in an enabled state, the first Non-AP STA adjusts the transmission power of the overlapping area. After the transmission power is adjusted, the AP corresponding to the source link and the AP corresponding to the target link can both receive the uplink signal of the first Non-AP STA, and the overlapping area is an area that can be covered by the AP corresponding to the source link and the AP corresponding to the target link.

17. The method according to any one of claims 1 to 12, characterized in that During the roaming process of the Non-AP MLD between different AP MLDs within the logical AP MLD, if the source link and the target link corresponding to the first Non-AP STA in the Non-AP MLD are links of the same frequency band and the same channel, and the source link and the target link corresponding to the first Non-AP STA are both in an enabled state, the AP corresponding to the source link and the AP corresponding to the target link coordinate downlink transmission for the first Non-AP STA.

18. A wireless communication method, characterized in that: Applied to an access point multi-link device AP MLD, the AP MLD belongs to a logical AP MLD, the method includes: The AP MLD receives a first frame sent by a non-access point multi-link device Non-AP MLD; Wherein, the Non-AP MLD roams between different AP MLDs within the logical AP MLD; The first frame includes a first field, and the first field is used to indicate that the first frame is used to add or delete a first type of link, or the first field is used to indicate that the first frame is used to add or delete a second type of link.

19. The method according to claim 18, characterized in that The first field is a roaming identifier existence field of the target AP MLD, wherein the roaming identifier existence field of the target AP MLD is used to indicate whether the roaming identifier field of the target AP MLD exists in the first element of the first frame, and the roaming identifier field of the target AP MLD is used to indicate the roaming identifier of the target AP MLD; In which, when the roaming identification field of the target AP MLD is used to indicate that the roaming identification field of the target AP MLD does not exist in the first element of the first frame, the first frame is used to add or delete a first-category link; and / or, when the roaming identification field of the target AP MLD is used to indicate that the roaming identification field of the target AP MLD exists in the first element of the first frame, the first frame is used to add or delete a second-category link.

20. The method of claim 19, wherein: The first element is a reconfiguration multilink element, or the first element is a basic multilink element.

21. The method of claim 20, wherein: In the case where the first element is a reconfiguration multilink element, the first frame is a multilink operation update request frame.

22. The method of claim 20, wherein: In the case where the first element is a basic multi-link element, the first frame is a frame used to add or delete a roaming link.

23. The method of claim 18, wherein: The first field takes a first value to indicate that the first field is a reserved field, and the first frame is used to add or delete a local link; and / or, the first field takes a second value to indicate a roaming identifier of a target AP MLD, and the first frame is used to add or delete a roaming link.

24. The method of claim 23, wherein: The first value is zero and the second value is non-zero.

25. The method of claim 18, wherein: The first field is an operation update type field; Among them, the operation update type field is used to indicate that the first frame is used to add a first type of link, or, or, the operation update type field is used to indicate that the first frame is used to delete a first type of link, or, the operation update type field is used to indicate that the first frame is used to add a second type of link, or, the operation update type field is used to indicate that the first frame is used to delete a second type of link.

26. The method according to any one of claims 23 to 25, characterized in that The first frame is a multi-link operation update request frame.

27. The method according to any one of claims 18 to 26, characterized in that During roaming of the Non-AP MLD between different AP MLDs within the logical AP MLD, the Non-AP MLD performs link switching in a first manner or a second manner; wherein the first manner is to first add a target link and then delete a source link, and the second manner is to first delete a source link and then add a target link.

28. The method according to any one of claims 18 to 27, characterized in that During the roaming process of the Non-AP MLD between different AP MLDs in the logical AP MLD, the target link corresponding to the first non-AP STA in the Non-AP MLD is in the same frequency band as the source link.

29. The method according to any one of claims 18 to 27, characterized in that During the roaming process of the Non-AP MLD between different AP MLDs in the logical AP MLD, a target link and a source link corresponding to a first Non-AP STA in the Non-AP MLD are in different frequency bands.

30. The method according to any one of claims 18 to 29, characterized in that During roaming of the Non-AP MLD between different AP MLDs in the logical AP MLD, if a source link and a target link corresponding to a first Non-AP STA in the Non-AP MLD are links of the same frequency band but different channels, and both the source link and the target link corresponding to the first Non-AP STA are in an enabled state, the first Non-AP STA performs the following operations: If the first Non-AP STA has resided in the target link for more than a first time period without obtaining a transmission opportunity, and the target access point AP corresponding to the target link has not initiated a transmission with the first Non-AP STA, the first Non-AP STA switches from the target link to the source link; and / or, If the first Non-AP STA has resided in the source link for more than a second time period without obtaining a transmission opportunity, and the source AP corresponding to the source link has not initiated transmission with the first Non-AP STA, the first Non-AP STA switches from the source link to the target link.

31. The method of claim 30, wherein: The first duration is the sum of the duration of the first timer and the distributed interframe space DIFS; The first timer is started when the first Non-AP STA switches to the target link, and the first timer is stopped when the first Non-AP STA receives a beacon frame within the first duration.

32. The method of claim 30, wherein: The second duration is the sum of the duration of the second timer and DIFS; The second timer is started when the first Non-AP STA switches to the source link, and the second timer is stopped when the first Non-AP STA receives a beacon frame within the second duration.

33. The method according to any one of claims 18 to 29, characterized in that During the roaming process of the Non-AP MLD between different AP MLDs within the logical AP MLD, if the source link and the target link corresponding to the first Non-AP STA in the Non-AP MLD are links of the same frequency band and the same channel, and the source link and the target link corresponding to the first Non-AP STA are both in an enabled state, the first Non-AP STA adjusts the transmission power of the overlapping area. After the transmission power is adjusted, the AP corresponding to the source link and the AP corresponding to the target link can both receive the uplink signal of the first Non-AP STA, and the overlapping area is an area that can be covered by the AP corresponding to the source link and the AP corresponding to the target link.

34. The method according to any one of claims 18 to 29, characterized in that During the roaming process of the Non-AP MLD between different AP MLDs within the logical AP MLD, if the source link and the target link corresponding to the first Non-AP STA in the Non-AP MLD are links of the same frequency band and the same channel, and the source link and the target link corresponding to the first Non-AP STA are both in an enabled state, the AP corresponding to the source link and the AP corresponding to the target link coordinate downlink transmission for the first Non-AP STA.

35. A non-access point multi-link device Non-AP MLD, wherein the Non-AP MLD roams between different AP MLDs in a logical access point multi-link device AP MLD, and the Non-AP MLD comprises: A communication unit, configured to send a first frame; The first frame includes a first field, and the first field is used to indicate that the first frame is used to add or delete a first type of link, or the first field is used to indicate that the first frame is used to add or delete a second type of link.

36. An access point multi-link device AP MLD, the AP MLD belonging to a logical AP MLD, the AP MLD comprising: A communication unit, configured to receive a first frame sent by a non-access point multi-link device Non-AP MLD; Wherein, the Non-AP MLD roams between different AP MLDs within the logical AP MLD; The first frame includes a first field, and the first field is used to indicate that the first frame is used to add or delete a first type of link, or the first field is used to indicate that the first frame is used to add or delete a second type of link.

37. A Non-AP MLD, characterized in that: include: A processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the Non-AP MLD performs the method according to any one of claims 1 to 17.

38. An AP MLD, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, so that the AP MLD executes the method according to any one of claims 18 to 34.

39. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 17.

40. A chip, characterized in that: include: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 18 to 34.

41. A computer-readable storage medium, characterized in that Used for storing a computer program, when the computer program is executed, the method according to any one of claims 1 to 17 is implemented.

42. A computer-readable storage medium, characterized in that: For storing a computer program, when the computer program is executed, the method according to any one of claims 18 to 34 is implemented.

43. A computer program product, characterized in that The method comprises computer program instructions, and when the computer program instructions are executed, the method according to any one of claims 1 to 17 is implemented.

44. A computer program product, characterized in that The method comprises computer program instructions, when the computer program instructions are executed, the method according to any one of claims 18 to 34 is implemented.

45. A computer program, characterized in that When the computer program is executed, the method according to any one of claims 1 to 17 is implemented.

46. ​​A computer program, characterized in that When the computer program is executed, the method according to any one of claims 18 to 34 is implemented.

Images