Wireless communication method, and device and storage medium

Abstract

Provided in the embodiments of the present application are a wireless communication method, and a device and a storage medium. The method comprises: a non-access-point multi-link device receiving or sending a first frame, wherein the first frame is used for the non-access-point multi-link device to switch between a first access point multi-link device and a second access point multi-link device, the first access point multi-link device and the second access point multi-link device belonging to the same third access point multi-link device or different third access point multi-link devices, and the third access point multi-link device being a logical access point multi-link device.

Description

Wireless communication method, device, and storage medium Technical Field

[0001] The embodiments of the present application relate to the field of mobile communication technologies, and in particular to a wireless communication method and device, and a storage medium. Background Art

[0002] The wireless LAN industry is one of the fastest-growing sectors in the data communications sector. As a supplement and extension of traditional wired LANs, wireless LAN solutions have gained widespread adoption among home network users, small and medium-sized offices, enterprises, and telecom operators due to their flexibility, mobility, scalability, and low investment costs.

[0003] In multi-link operation, multiple links can be established between an access point multi-link device (AP MLD) and a non-AP MLD on different frequency bands / channels. As a station (STA) moves, the Basic Service Set (BSS) transitions occur. This means the STA disconnects from its current access point (AP) and establishes a connection with another AP. Therefore, minimizing the duration of connectivity loss between the STA and the Distribution System (DS), or between the non-AP MLD and the DS, during BSS transitions is a pressing technical challenge.

[0004] Summary of the Invention

[0005] Embodiments of the present application provide a wireless communication method and device, and a storage medium.

[0006] The wireless communication method provided in the embodiment of the present application includes:

[0007] A non-access point multi-link device receives or sends a first frame, where the first frame is used by the non-access point multi-link device to switch between a first access point multi-link device and a second access point multi-link device, where the first access point multi-link device and the second access point multi-link device are attached to the same third access point multi-link device or different third access point multi-link devices, and the third access point multi-link device is a logical access point multi-link device.

[0008] The wireless communication method provided in the embodiment of the present application includes:

[0009] An access point multi-link device sends or receives a first frame, where the first frame is used by the non-access point multi-link device to switch between the first access point multi-link device and the second access point multi-link device. The first access point multi-link device and the second access point multi-link device are attached to the same third access point multi-link device or different third access point multi-link devices. The third access point multi-link device is a logical access point multi-link device, and the access point multi-link device is the first access point multi-link device or the second access point multi-link device.

[0010] The non-access point multi-link device provided in the embodiment of the present application includes:

[0011] The first communication unit is configured to receive or send a first frame, where the first frame is used for the non-access point multi-link device to switch between a first access point multi-link device and a second access point multi-link device, where the first access point multi-link device and the second access point multi-link device are attached to the same third access point multi-link device or different third access point multi-link devices, and the third access point multi-link device is a logical access point multi-link device.

[0012] The access point multi-link device provided in the embodiment of the present application includes:

[0013] The second communication unit is configured to send or receive a first frame, where the first frame is used for the non-access point multi-link device to switch between a first access point multi-link device and a second access point multi-link device, where the first access point multi-link device and the second access point multi-link device are attached to the same third access point multi-link device or different third access point multi-link devices, where the third access point multi-link device is a logical access point multi-link device, and the access point multi-link device is the first access point multi-link device or the second access point multi-link device.

[0014] An embodiment of the present application provides a non-access point multi-link device, including: a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and execute the computer program stored in the memory, so that the non-access point multi-link device performs the above-mentioned wireless communication method.

[0015] An access point multi-link device provided in an embodiment of the present application includes: a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and execute the computer program stored in the memory, so that the non-access point multi-link device performs the above-mentioned wireless communication method.

[0016] The chip provided in the embodiment of the present application is used to implement the above-mentioned wireless communication method.

[0017] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above-mentioned wireless communication method.

[0018] The computer-readable storage medium provided in an embodiment of the present application is used to store a computer program, and the execution of the computer program enables a computer to execute the above-mentioned wireless communication method.

[0019] The computer program product provided in the embodiments of the present application includes computer program instructions, and the execution of the computer program instructions enables a computer to execute the above-mentioned wireless communication method.

[0020] The computer program provided in the embodiment of the present application, when executed on a computer, enables the computer to execute the above-mentioned wireless communication method.

[0021] Through the above technical solution, a non-access point multi-link device switches between a first access point multi-link device and a second access point multi-link device that are attached to the same logical access point multi-link device or a different third access point multi-link device. Thus, in an architecture in which the third access point multi-link device is disposed above the first access point multi-link device and the second access point multi-link device, conversion or switching control is performed on communications between the first access point multi-link device and the non-access point multi-link device, and between the second access point multi-link device and the non-access point multi-link device. This allows the non-access point multi-link device to switch or switch between the first access point multi-link device and the second non-access point multi-link device for data continuity. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0023] FIG1 is an optional schematic diagram of an application scenario of an embodiment of the present application;

[0024] FIG2A is an optional schematic diagram of an application scenario of an embodiment of the present application;

[0025] FIG2B is an optional schematic diagram of an application scenario of an embodiment of the present application;

[0026] FIG3 is an optional schematic diagram of an application scenario of an embodiment of the present application;

[0027] FIG4 is an optional schematic diagram of an application scenario of the logical AP MLD according to an embodiment of the present application;

[0028] FIG5 is an optional schematic flow chart of a wireless communication method according to an embodiment of the present application;

[0029] FIG6 is a schematic diagram of an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0030] FIG7 is an optional schematic diagram of a third access point multi-link device according to an embodiment of the present application;

[0031] 8 is a schematic diagram of an application scenario in which a non-access point multi-link device according to an embodiment of the present application switches between different access point multi-link devices to which a third access point multi-link device is attached;

[0032] FIG9 is an optional schematic diagram of a high-level architecture of a mobile domain AP MLD according to an embodiment of the present application;

[0033] FIG10 is an optional schematic diagram of a resource request process according to an embodiment of the present application;

[0034] FIG11 is a schematic diagram of an optional frame structure of a block acknowledgement protocol scenario element according to an embodiment of the present application;

[0035] FIG12 is a schematic diagram of an optional frame structure of a block acknowledgment protocol scenario parameter control field according to an embodiment of the present application;

[0036] FIG13 is a schematic diagram of an optional frame structure of a block acknowledgment protocol scenario parameter set subfield according to an embodiment of the present application;

[0037] FIG14 is a schematic diagram of an optional frame structure of a block acknowledgement parameter set subfield according to an embodiment of the present application;

[0038] FIG15 is a schematic diagram of an optional frame structure of a block confirmation protocol scenario parameter set subfield for the initiator according to an embodiment of the present application;

[0039] FIG16 is a schematic diagram of an optional frame structure of a block acknowledgment protocol scenario parameter set subfield for a receiver according to an embodiment of the present application;

[0040] FIG17 is a schematic diagram of an optional frame structure of a security-related scene element according to an embodiment of the present application;

[0041] FIG18 is a schematic diagram of an optional frame structure of a security-associated scenario parameter control field according to an embodiment of the present application;

[0042] FIG19 is a schematic diagram of an optional frame structure of a security association scenario parameter set list field according to an embodiment of the present application;

[0043] FIG20 is a schematic diagram of an optional frame structure of a security association scenario parameter set subfield of a receiving end according to an embodiment of the present application;

[0044] FIG21 is a schematic diagram of an optional frame structure of a security association scenario parameter set subfield of a transmitting end according to an embodiment of the present application;

[0045] FIG22 is a schematic diagram of an optional frame structure of the conversion capability and policy domain according to an embodiment of the present application;

[0046] FIG23 is a schematic diagram of an optional frame structure of an MDE according to an embodiment of the present application;

[0047] FIG24 is an optional schematic diagram of a high-level architecture of a mobile domain AP MLD according to an embodiment of the present application;

[0048] FIG25 is a schematic diagram of an optional flow chart of a wireless communication method according to an embodiment of the present application;

[0049] FIG26 is a schematic diagram of an optional structure of a non-access point multi-link device according to an embodiment of the present application;

[0050] FIG27 is a schematic diagram of an optional structure of an access point multi-link device according to an embodiment of the present application;

[0051] FIG28 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0052] FIG29 is a schematic structural diagram of a chip according to an embodiment of the present application;

[0053] Figure 30 is a schematic block diagram of a communication system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0054] 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 described embodiments are part of the embodiments of this application, not all of the embodiments. Based on 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.

[0055] 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. WLANs may support frequency bands including, but not limited to, low frequency bands (2.4 GHz, 5 GHz, and 6 GHz) and high frequency bands (45 GHz and 60 GHz).

[0056] FIG1 is an example of a communication system architecture applied in an embodiment of the present application.

[0057] As shown in FIG1 , the communication system 100 may include an AP 110 and a station (STA) 120 that accesses the network through AP 110. In some scenarios, AP 110 may be referred to as an AP STA, meaning that, in a sense, AP 110 is also a type of STA. In some scenarios, STA 120 may be referred to as a non-AP STA. In some scenarios, STA 120 may include both AP STAs and non-AP STAs. Communication in the communication system 100 may include communication between AP 110 and STA 120, communication between STA 120 and STA 120, or communication between STA 120 and a peer STA. A peer STA may refer to a device communicating with STA 120, for example, a peer STA may be an AP or a non-AP STA.

[0058] AP 110 can be used as a bridge between wired and wireless networks, connecting wireless network clients together and then connecting the wireless network to Ethernet. AP 110 can be a terminal device (such as a mobile phone) or a network device (such as a router) equipped with a WiFi chip.

[0059] It should be noted that the role of STA 120 in the communication system is not absolute. In other words, the role of STA 120 in the communication system can switch between AP and STA. For example, in some scenarios, when a mobile phone is connected to a router, the mobile phone is a STA. When the mobile phone is used as a hotspot for other mobile phones, the mobile phone plays the role of AP.

[0060] In some embodiments, AP 110 and STA 120 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.

[0061] In some embodiments, AP 110 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. In some embodiments, STA 120 may support the 802.11be standard. The STA may also support various current and future 802.11 family WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0062] In some embodiments, AP 110 and / or STA 120 can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as a ship); can also be deployed in the air (for example, on an airplane, balloon, and satellite, etc.).

[0063] In some embodiments, STA 120 may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) device, an augmented reality (AR) device, a wireless device in industrial control, a set-top box, a wireless device in self-driving, an in-vehicle communication device, a wireless device in remote medical, a wireless device in a smart grid, a wireless device in transportation safety, a wireless device in a smart city or a wireless device in a smart home, an in-vehicle communication device, a wireless communication chip / application specific integrated circuit (ASIC) / system on chip (SoC), etc. that supports WLAN / WiFi technology.

[0064] For example, STA 120 can also be a wearable device. Wearable devices can also be called wearable smart devices, which are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are full-featured, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0065] It should be understood that Figure 1 is merely an example of the present application and should not be construed as limiting the present application. For example, Figure 1 only exemplarily illustrates one AP and two STAs. In some embodiments, the communication system 100 may include multiple APs and other numbers of STAs, which are not limited in this embodiment of the present application.

[0066] FIG2A is a schematic diagram of an application scenario of an embodiment of the present application.

[0067] As shown in Figure 2A, communication system 200 may include AP MLDs 210 and 220. AP MLD 210 is an electronic device capable of forming a wireless local area network 230 based on transmitted signals, such as a router or a mobile phone with hotspot functionality. Non-AP MLD 220 is an electronic device connected to the wireless local area network 230 formed by AP MLD 210, such as a mobile phone, smart washing machine, air conditioner, or electronic lock. Non-AP MLD 220 communicates with AP MLD 210 via wireless local area network 230. AP MLD 210 may be a soft AP MLD, a mobile AP MLD, or the like.

[0068] As shown in FIG2B , in the communication system described in FIG2A , AP MLD 210 is affiliated with at least two APs 2101, and non-AP MLD 220 is affiliated with at least two STAs (STAs) 2201. Each AP is connected to a different STA in non-AP MLD 220 via a different link. An AP affiliated with an AP MLD may also be referred to as an AP affiliated with an AP MLD, and a STA affiliated with a non-AP MLD may also be referred to as a non-AP STA affiliated with a non-AP MLD or a STA affiliated with a non-AP MLD.

[0069] In the embodiments of the present application, the AP MLD 210 and the non-AP MLD 220 may be terminal devices, which may refer to access terminals, user equipment (UE), subscriber units, subscriber stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication devices, user agents, or user devices. Access terminals may be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5th generation (5G) networks, or terminal devices in future Public Land Mobile Networks (PLMNs), etc.

[0070] The communication system 200 shown in Figure 2A may also include a network device, which may be an access network device that communicates with a terminal device. The access network device may provide communication coverage for a specific geographical area and may communicate with terminal devices within the coverage area.

[0071] FIG2A exemplarily shows an AP MLD and a non-AP MLD. Optionally, the communication system 200 may include multiple non-AP MLDs connected to the wireless local area network 230 , which is not limited in this embodiment of the present application.

[0072] It should be noted that Figures 1, 2A, and 2B are merely examples of the systems to which this application applies. Of course, the methods described in the embodiments of this application can also be applied to other systems. Furthermore, the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein simply describes an association relationship between associated objects, indicating that three possible relationships can exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " herein generally indicates that the associated objects are in an "or" relationship. It should also 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 associated relationship. For example, "A indicates B" can mean that A directly indicates B, for example, B can obtain information through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can obtain information through C; it can also mean that A and B have an associated relationship. It should also be understood that the “correspondence” mentioned in the embodiments of the present application 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. It should also be understood that the “predefined” or “predefined rules” mentioned in the embodiments of the present application can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices), and the present application does not limit its specific implementation method. For example, predefined can refer to what is defined in the protocol. It should also be understood that in the embodiments of the present application, the “protocol” may refer to a standard protocol in the field of communications, for example, it may include IEEE 802.11 protocol, LTE protocol, NR protocol and related protocols used in future communication systems, and the present application does not limit this.

[0073] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0074] Unless otherwise specified, a STA refers to a non-AP device that has no attached STAs.

[0075] In related technologies, multi-link operation (MLO) and MLO-capable AP MLDs and non-AP MLDs are defined. Multiple links are established between the AP MLD and the non-AP MLD on multiple different frequency bands / channels.

[0076] As shown in Figure 3, non-AP MLD and AP MLD successfully establish multiple links through the following process: Non-AP STA1 in non-AP MLD sends an association request frame to AP1 in AP MLD, and AP1 in AP MLD sends an association response frame to non-AP STA1 in non-AP MLD. The links established between AP MLD and non-AP MLD include Link 1 on the 2.4 GHz wireless medium (WM), Link 2 on the 5 GHz WM, and Link 3 on the 6 GHz WM. These three 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 affiliated APs of the AP MLD. Similarly, 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 called affiliated non-AP STAs of the non-AP MLD.

[0077] In related technologies, as shown in Figure 4, multiple non-collocated APs are treated as a single AP MLD. This AP MLD is a logical 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 the AP MLD to use a multi-link operation architecture to use different affiliated APs to provide services to the STA using different links, thereby better enabling uninterrupted roaming for the STA. As shown in Figure 4, STA x uses multiple links to connect to AP 1 and AP 2. When STA x moves, the link to AP 1 is disconnected, but the link to AP 2 is not affected. This improves STA mobility support.

[0078] Fast BSS transition (FT)

[0079] The goal of fast BSS transition is to reduce the length of time that the STA and DS or non-AP MLD and DS lose connectivity during BSS transition. The FT protocol is part of the reassociation service and is only applicable to the transition of STA or non-AP MLD between APs or AP MLDs in the same mobility domain within the same Extended Service Set (ESS). The AP publishes functions and policies that support FT protocols and methods. Among them, the FT function is published in beacon and probe response frames by including the Mobility Domain Element (MDE). The MDE is published in beacon and probe response frames to indicate the mobility domain identifier (MDID), FT capabilities, and FT policies.

[0080] The FT protocol requires an exchange of information during the initial association (or subsequent reassociation) between a STA (called a FT initiator (fast BSS transition originator, FTO)) and an AP (called a FT responder (fast BSS transition responder, FTR)), or between a non-AP MLD (called an FTO) and an AP MLD (called an FTR). This initial exchange is called an FT initial mobility domain association. Subsequent reassociations with FTRs within the same mobility domain can use the FT protocol.

[0081] FT defines two FT protocols:

[0082] —FT protocol. This protocol is executed when the FTO is transitioned to the target FTR and does not require resource requests before the transition.

[0083] —FT Resource Request Protocol. This protocol is executed when FTO needs a resource request before its transition.

[0084] For an FTO to move to a target FTR using the FT protocol, the message exchange is performed using one of two methods:

[0085] Wireless. The FTO communicates directly with the target FTR, using IEEE 802.11 authentication and the FT authentication algorithm.

[0086] Over-the-DS (DS) communication. The FTO communicates with the target FTR through the current FTR. Communication between the FTO and the target FTR occurs in FT Action frames between the FTO and the current FTR. Communication between the current FTR and the target FTR occurs using the encapsulation method described in "Remote Request / Response Frame Definition." The current AP converts between the two encapsulations.

[0087] Although the current FT can reduce the duration of connectivity loss between STAs and DSs, or between non-AP MLDs and DSs, during BSS transitions, it cannot maintain data continuity between STAs and DSs, or between non-AP MLDs and DSs, because the STA (or non-AP MLD) needs to reassociate and reestablish data transmission and reception protocols and scenarios when transitioning to the target AP (or target AP MLD).

[0088] While logical AP MLD theoretically supports multiple APs in different locations attached to a single logical AP MLD using different links to provide services to the same non-AP MLD, achieving non-AP MLD roaming without interruption, when multiple APs in different locations attached to a single logical AP MLD communicate with the same non-AP MLD over different links, synchronization of data communication status and confirmation of transmission and reception between APs based on the non-AP MLD imposes high communication quality requirements on the backhaul link between the APs, making synchronization and confirmation of data communication status based on the non-AP MLD difficult to achieve.

[0089] 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 above related technologies can be combined arbitrarily with the technical solutions of the embodiments of the present application as optional solutions, and all of them 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.

[0090] The wireless communication method provided in an embodiment of the present application is applied to a non-access point multi-link device, as shown in FIG5 , including:

[0091] S501. A non-access point multi-link device receives or sends a first frame, where the first frame is used by the non-access point multi-link device to switch between a first access point multi-link device and a second access point multi-link device. The first access point multi-link device and the second access point multi-link device are attached to the same third access point multi-link device or different third access point multi-link devices, and the third access point multi-link device is a logical access point multi-link device.

[0092] The wireless communication method provided in an embodiment of the present application is applied to an access point multi-link device, as shown in FIG6 , and includes:

[0093] S601. An access point multi-link device sends or receives a first frame, where the first frame is used by a non-access point multi-link device to switch between a first access point multi-link device and a second access point multi-link device. The first access point multi-link device and the second access point multi-link device are attached to the same third access point multi-link device or different third access point multi-link devices. The third access point multi-link device is a logical access point multi-link device, and the access point multi-link device is the first access point multi-link device or the second access point multi-link device.

[0094] Next, the wireless communication method shown in FIG. 5 or FIG. 6 will be described.

[0095] The first access point multi-link device and the second access point multi-link device are two access point multi-link devices that are not in the same location (non-collocated).

[0096] The non-access point multi-link device switches between the first access point multi-link device and the second access point multi-link device, including one of the following:

[0097] Transition scenario 1: When the Non-AP MLD is associated with a third access point multi-link device, and the first access point multi-link device and the second access point multi-link device are both attached to the same third access point multi-link device, the non-AP multi-link device performs a transition (or handover) between the first access point multi-link device and the second access point multi-link device at the access point multi-link device level association to which the third access point multi-link device is attached;

[0098] In transition scenario 2, when the Non-AP MLD is associated only with the first access point multi-link device or the second access point multi-link device, where the first access point multi-link device and the second access point multi-link device are not attached to the same logical access point multi-link device, the non-AP multi-link device switches (or switches) its association between the first access point multi-link device and the second access point multi-link device.

[0099] The transition in the embodiment of the present application may also be described as switching.

[0100] For conversion scenario 1, the conversion (or switching) of the access point multi-link device-level association to which the third access point multi-link device belongs means that before the conversion, the non-AP MLD is associated with the third AP MLD and a multi-link is established between the non-AP MLD and an AP MLD affiliated with the third AP MLD (i.e., the link established between the non-AP MLD and the third AP MLD is entirely or partially a link between the non-AP MLD and an AP MLD affiliated with the third AP MLD); after the conversion, the non-AP MLD is still associated with the third AP MLD and a multi-link is established between the non-AP MLD and another AP MLD affiliated with the third AP MLD (i.e., the link established between the non-AP MLD and the third AP MLD is entirely or partially a link between the non-AP MLD and another AP MLD affiliated with the third AP MLD).

[0101] [Corrected 23.08.2023 in accordance with Rule 91] As shown in FIG7 , the first access point multi-link device and the second access point multi-link device are subordinate access point multi-link devices or subordinate access point multi-link devices of the same third access point multi-link device. The subordinate access point multi-link devices of the third access point multi-link device may or may not include other access point multi-link devices in addition to the first access point multi-link device and the second access point multi-link device.

[0102] In the embodiment of the present application, the third access point multi-link device is a logical entity composed of multiple access point multi-link devices, including the first access point multi-link device and the second access point multi-link device. It is understandable that the multiple access point multi-link devices constituting the third access point multi-link device belong to the same mobility domain. The third access point multi-link device can be the access point multi-link device corresponding to the mobility domain and can be defined as a mobility domain multi-link device (MD AP MLD).

[0103] It can be understood that the first access point multi-link device is the access point multi-link device before the conversion, and the second access point multi-link device is the access point multi-link device after the conversion. As shown in Figure 8, before the conversion, the non-access point multi-link device is associated with the first access point multi-link device affiliated with the third access point multi-link device, and the link between the non-access point multi-link device and the third access point multi-link device includes the first link between the non-access point multi-link device and the first access point multi-link device. After the conversion, the non-access point multi-link device is associated with the second access point multi-link device affiliated with the third access point multi-link device, and the link between the non-access point multi-link device and the third access point multi-link device includes the second link between the non-access point multi-link device and the third access point multi-link device. Therefore, when the non-access point multi-link device is associated with the first access point multi-link device affiliated with the third access point multi-link device, as the non-access point multi-link device moves, it associates or re-associates with the second access point multi-link device affiliated with the third access point multi-link device and continues to transmit data transmitted on the first link with the first access point multi-link device via the second link with the second access point multi-link device, thereby maintaining session continuity and data persistence when the access point multi-link device associates with different affiliated access point multi-link devices of the third access point multi-link device due to roaming.

[0104] For the second conversion scenario, the non-access point multi-link device associates with an access point multi-link device attached to a different logical access point multi-link device before and after the conversion or switching, thereby performing the association conversion or switching.

[0105] For a third access point multi-link device to which the first access point multi-link device is attached, the third access point multi-link device is attached to a plurality of access point multi-link devices including the first access point multi-link device.

[0106] With respect to the third access point multi-link device to which the second access point multi-link device is attached, the third access point multi-link device is attached to a plurality of access point multi-link devices including the second access point multi-link device.

[0107] During the switching process between a first access point multi-link device and a second access point multi-link device affiliated with the same third access point multi-link device or a different third access point multi-link device, a frame communicated between a non-access point multi-link device and a first access point multi-link device or a second access point multi-link device is called a first frame.

[0108] The conversion provided in the embodiment of the present application may include BSS conversion or fast BSS transition (FT), seamless BSS conversion or seamless fast conversion in BSS switching.

[0109] BSS transition or BSS handover is the switching (or handover) of a station or non-AP MLD from being associated with one BSS or a first AP MLD to being associated with another BSS or a second AP MLD in the same Extended Service Set (ESS).

[0110] Fast BSS transition (FT) is a BSS transition that minimizes the loss of data connection to the distribution system (DS).

[0111] Seamless BSS transition, that is, a BSS transition that can maintain data connectivity with the distributed system DS.

[0112] Seamless fast BSS transition, that is, a BSS transition that can maintain data connectivity with the distributed system DS and reduce the time of BSS transition.

[0113] In a wireless communication method provided in an embodiment of the present application, a non-access point multi-link device switches between a first access point multi-link device and a second access point multi-link device that are attached to the same logical access point multi-link device or a different third access point multi-link device. Thus, in an architecture in which the third access point multi-link device is disposed above the first access point multi-link device and the second access point multi-link device, conversion or switching control is performed on communications between the first access point multi-link device and the non-access point multi-link device, and between the second access point multi-link device and the non-access point multi-link device. This allows the non-access point multi-link device to switch between the first access point multi-link device and the second non-access point multi-link device for data continuity.

[0114] It should be noted that the method in Figure 5 or Figure 6 is the conversion or switching of Non AP MLD from the first AP MLD to the second AP MLD in the scenario of mobile domain AP MLD. The wireless communication method provided in the embodiment of the present application is also applicable to the conversion or switching of non-MLD STA from the first AP to the second AP in the scenario of mobile domain AP MLD.

[0115] In some embodiments, the first access point multi-link device is an access point multi-link device whose affiliated access point AP is located at the same location; the second access point multi-link device is an access point multi-link device whose affiliated AP is located at the same location.

[0116] The non-access point multi-link device is associated with a third access point multi-link device (logical access point multi-link device), the first access point multi-link device is an access point multi-link device whose attached AP is located at the same location (called collocated AP MLD or co-located AP MLD), and the second access point multi-link device is an access point multi-link device whose attached AP is located at the same location; the first access point multi-link device and the second access point multi-link device are AP MLDs located at different locations.

[0117] In some embodiments, the third access point multi-link device is used for at least one of the following:

[0118] Function 1: Provide connection service between the non-access point multi-link device or the auxiliary access point multi-link device and the distributed system DS;

[0119] Function 2: maintaining data continuity of the non-access point multi-link device during roaming when switching between the first access point multi-link device and the second access point multi-link device;

[0120] Function three: authentication and / or association or re-association of the non-access point multi-link device;

[0121] Function 4: security association of the non-access point multi-link device;

[0122] Function 5: Distribution of all or part of the security association information of the non-access point multi-link device;

[0123] Function 6: Synchronize all or part of the status and / or buffer information of the upper layer of the MAC of the attached access point multi-link device;

[0124] Function seven: managing the distribution of authentication information of the non-access point multi-link device link;

[0125] Function eight: managing the association or re-association between the non-access point multi-link device and the auxiliary access point multi-link device at the auxiliary access point multi-link device level;

[0126] Function nine: for a target access point multi-link device that has at least one attached access point multi-link device and has established a multi-link with the non-access point multi-link device, select a MAC address corresponding to the target access point multi-link device for data transmission;

[0127] Function 10: Synchronize first data between different attached access point multi-link devices, where the first data is used to maintain data continuity in communication between the non-access point multi-link device and the attached access point multi-link device or DS;

[0128] Function 11: Exchange or indicate MLD-level information through the MAC sublayer of the attached access point multi-link device.

[0129] In the embodiment of the present application, the subordinate access point multi-link device may be understood as a subordinate access point multi-link device of the third access point multi-link device.

[0130] For function 1, the third access point multi-link device provides a DS access function for its subordinate access point multi-link device and the non-AP MLD associated with its subordinate access point multi-link device. Its subordinate access point multi-link device and the non-AP MLD associated with its subordinate access point multi-link device access the DS, so that the non-AP MLD can directly call or call one or more distributed system services (DSS) through the subordinate access point multi-link device.

[0131] For function 2, maintain data continuity of the non-AP MLD during roaming when switching between the first access point multi-link device and the second access point multi-link device, and achieve seamless switching of the non-AP MLD between the first access point multi-link device and the second access point multi-link device.

[0132] Function three: The third access point multi-link device is used for authentication and / or association or reassociation with the non-access point multi-link device. This can be understood as when the non-access point multi-link device is associated or reassociated with the third access point multi-link device, the non-access point multi-link device is associated or reassociated with the access point multi-link device to which the third access point multi-link device is attached.

[0133] When the non-access point multi-link device is associated with a subordinate access point multi-link device of the third access point multi-link device, the non-access point multi-link device is associated with the third access point multi-link device. In this embodiment of the present application, if the non-access point multi-link device is associated with the subordinate access point multi-link device of the third access point multi-link device, an association relationship exists between the non-access point multi-link device and the subordinate access point multi-link device of the third access point multi-link device. At this time, an association relationship also exists between the non-access point multi-link device and the third access point multi-link device, enabling the non-access point multi-link device to invoke DSS.

[0134] When the third access point multi-link device is capable of authenticating the non-access point multi-link device associated with its subordinate access point multi-link device.

[0135] The type of security association in function four may include at least one of the following: Pairwise Master Key Security Association (PMKSA) and Pairwise Temporary Key Security Association (PTKSA).

[0136] Function 5: The third access point multi-link device is used to distribute security association information of the non-access point multi-link device.

[0137] A security association may be established between the non-access point multi-link device and the subordinate access point multi-link device of the third access point multi-link device, and the third access point multi-link device distributes all or part of the security association information.

[0138] The security association information includes information used when transmitting data over the established security association.

[0139] For function six, the subordinate access point multi-link device of the third access point multi-link device may include an upper layer MAC and a lower layer MAC, and the upper layer of the upper layer MAC of the subordinate access point multi-link device of the third access point multi-link device, i.e., the MAC general sublayer, synchronizes all or part of the status and / or buffer information of the upper layer MAC of the subordinate access point multi-link device.

[0140] In some embodiments, the synchronization method includes at least one of the following: copying or migrating.

[0141] For function seven, the authentication information of the link includes at least one of the following: a group temporary key (GTK), an intact GTK (IGTK), and a beacon IGTK (BIGTK).

[0142] The association or re-association at the secondary access point multi-link device level in function eight refers to the non-AP MLD establishing or re-establishing a multi-link with the third access point multi-link device. That is, the non-AP MLD associates or re-associates with the third access point multi-link device, and at least one link established (or re-established) between the non-AP MLD and the third access point multi-link device is a link between the non-AP MLD and the third AP MLD-affiliated access point multi-link device.

[0143] In some embodiments, when a non-access point multi-link device associates or re-associates with a subordinate access point multi-link device of a third access point multi-link device, and an association request frame sent by the non-access point multi-link device carries indication information indicating the third access point multi-link device, the non-access point multi-link device can associate with the subordinate access point multi-link device of the third access point multi-link device.

[0144] It is understandable that when a non-access point multi-link device is associated with a subordinate access point multi-link device of a third access point multi-link device, the non-access point multi-link device can also be associated or re-associated with other subordinate access point multi-link devices of the third access point multi-link device.

[0145] With respect to function nine, the third access point multi-link device is configured to select, for data transmission, a MAC address corresponding to a target access point multi-link device to which the non-access point multi-link device among at least one of the subordinate access point multi-link devices is associated or to which a multi-link is established, the target access point multi-link device. It is understandable that the MAC addresses of all subordinate access point multi-link devices of the third access point multi-link device are connected to the third access point multi-link device, and the access point multi-link device associated with the non-access point multi-link device among the subordinate access point multi-link devices of the third access point multi-link device is the target access point multi-link device. When the non-access point multi-link device communicates data with the target access point multi-link device, the third access point multi-link device selects the MAC address of the target access point multi-link device from the MAC addresses of all the subordinate access point multi-link devices for data communication.

[0146] Regarding function ten, the third access point multi-link device is used to synchronize first data between different subordinate access point multi-link devices of the third access point multi-link device, so that different subordinate access point multi-link devices of the third access point multi-link device can synchronize first data for data communication with the same non-access point multi-link device. It is understandable that when a non-access point multi-link device and a subordinate access point multi-link device of the third access point multi-link device use the first data for data communication, the third access point multi-link device can synchronize the first data to another subordinate access point multi-link device of the third access point multi-link device, so that the subordinate access point multi-link device can continue data communication with the non-access point multi-link device based on the first data, thereby maintaining data communication continuity.

[0147] The third access point multi-link device is also used for synchronizing the first data to the DS. The synchronization of the first data to the DS can be understood as synchronization of the first data between different access point multi-link devices.

[0148] Regarding function seven, the third access point multi-link device is configured to exchange MLD-level information between different subordinate access point multi-link devices via the MAC sublayers of the different subordinate access point multi-link devices, or the third access point multi-link device indicates information to the MAC sublayer of the subordinate access point multi-link device, thereby indicating the MLD-level information to the subordinate access point multi-link device. It is understood that the MLD-level information is information about the AP MLD to which the third access point multi-link device is subordinate or a non-AP MLD associated with the subordinate AP MLD.

[0149] In some embodiments, when the first access point multi-link device or the second access point multi-link device is an AP MLD, it includes an upper MAC sublayer and a lower MAC sublayer. The third access point multi-link device is a common MAC sublayer. The upper MAC sublayer provides a MAC service access point (SAP) to communicate with the common MAC sublayer. The common MAC sublayer provides a MAC SAP to communicate with the upper MAC sublayer of the subordinate access point multi-link device. The lower MAC sublayer of the subordinate access point multi-link device may include at least one subordinate AP included in the subordinate access point multi-link device.

[0150] Assume that the first access point multi-link device is AP MLD1, the second access point multi-link device is AP MLD2, and the third access point multi-link device is AP MLD3. The high-level architecture of the third access point multi-link device and its subordinate first access point multi-link device and subordinate second access point multi-link device is shown in FIG9. The MLD MAC address of AP MLD1 is M, and its subordinate APs include: AP1 with a MAC address of w and AP2 with a MAC address of x; the MLD MAC address of AP MLD2 is N, and its subordinate APs include: AP3 with a MAC address of r and AP4 with a MAC address of s; the MLD MAC address of AP MLD3 is Q. Among them, AP MLD3 serves as the MLD general MAC sublayer, AP MLD1 includes the subordinate MLD upper MAC sublayer, lower MAC sublayer, and subordinate MLD lower MAC sublayer, AP MLD2 includes the subordinate MLD upper MAC sublayer, lower MAC sublayer, and subordinate MLD lower MAC sublayer, and the subordinate MLD upper MAC sublayer provides a MAC SAP and a MAC of the MLD general MAC sublayer. The SAP is used for communication, and the MAC sublayer below the subordinate MLD provides the subordinate AP of the subordinate AP MLD. The upper MAC sublayer of the subordinate MLD to which the MLD universal MAC sublayer is connected can switch between the upper MAC sublayer of the subordinate MLD of AP MLD1 and the upper MAC sublayer of AP MLD2. This switching enables synchronization of first data between the upper MAC sublayer of the subordinate MLD of AP MLD1 and the upper MAC sublayer of AP MLD2. As shown in Figure 9, AP MLD1 and AP MLD2 can also communicate with the DS via the MAC SAP of the MLD universal MAC sublayer.

[0151] In some embodiments, the first access point multi-link device and the second access point multi-link device belong to the same MD in the same extended service set, and the third access point multi-link device is an MD AP MLD.

[0152] The first access point multi-link device and the second access point multi-link device belong to the same MD in the same extended service set. The transition of the access point multi-link device between the first access point multi-link device and the second access point multi-link device can be defined as a transition between different BSSs of the same MD in the same ESS, that is, a transition from the BSS of one access point multi-link device to the BSS of another access point multi-link device. It is understandable that a transition between non-access point multi-link devices can be defined as an FT transition.

[0153] In the case where the third access point multi-link device is an MD AP MLD, the switching of the non-access point multi-link device between the first access point multi-link device and the second access point multi-link device can be understood as the rapid switching of the non-access point multi-link device between the first access point multi-link device and the second access point multi-link device in the MD AP MLD scenario.

[0154] The mobility domain AP MLD (MD AP MLD) can be understood as a roaming AP MLD or an access point multi-link device whose attached APs are not located at the same location (non-collocated AP MLD).

[0155] In some embodiments, the first frame includes first information, and the first information includes at least one of the following:

[0156] first indication information, where the first indication information is used to indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD;

[0157] Second indication information, where the second indication information is used to indicate the third access point multi-link device.

[0158] If the first indication information indicates that the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD, then the non-access point multi-link device can switch between the two subordinate access point multi-link devices of the same MD AP MLD. If the first indication information indicates that the non-access point multi-link device does not support or is allowed to switch between the two subordinate access point multi-link devices of the same MD AP MLD, then the non-access point multi-link device cannot switch between the two subordinate access point multi-link devices of the same MD AP MLD.

[0159] The first indication information can indicate, based on different values, whether the non-access point multi-link device supports or is allowed to switch between two access point multi-link devices affiliated with the same MD AP MLD. In one example, if the value of the first indication information is 1, it indicates that switching between two AP MLDs affiliated with the same mobility domain AP MLD is supported or allowed; if the value of the first indication information is 0, it indicates that fast switching between two AP MLDs affiliated with the same mobility domain AP MLD is not supported or allowed. In this case, the terminal device can switch between two AP MLDs belonging to different mobility domain AP MLDs.

[0160] In the embodiment of the present application, the first indication information may be identified as FT within the mobile domain MLD (FtinMobileDomainMLD).

[0161] It is understandable that the mobility domain MLD can be replaced by the mobility domain APMLD.

[0162] The second indication information is used to indicate the third access point multi-link device. Wherein, if the non-access point multi-link device switches between two subordinate access point multi-link devices of the third access point multi-link device, the second indication information may be defined as the MD AP MLD to which the two subordinate access point multi-link devices undergoing the switching are subordinate.

[0163] In the embodiment of the present application, the second indication information may be identified as mobile domain MLD information (MobileDomainMLD Info).

[0164] In the embodiment of the present application, the first indication information and the second indication information in the first frame can indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of an MD AP MLD.

[0165] In some embodiments, the first frame includes at least one of the following:

[0166] a first switching frame, wherein the first switching frame is used to start the non-access point multi-link device from switching from the first access point multi-link device to the second access point multi-link device;

[0167] a second switching frame, where the first access point multi-link device is used to synchronize second data to the second access point multi-link device, where the second data is used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device, so as to maintain sustainability of data communication after the non-access point multi-link device switches to the second access point multi-link device;

[0168] A third conversion frame is used for the non-access point multi-link device to associate or re-associate with the second access point multi-link device.

[0169] In the embodiment of the present application, the first conversion frame is sent or received earlier than the second conversion frame; the second conversion frame is sent or received earlier than the third conversion frame.

[0170] For the first switching frame, the non-access point multi-link device and the second access point multi-link device initiate switching of the non-access point multi-link device from the first access point multi-link device to the second access point multi-link device by transmitting the first switching frame.

[0171] The non-access point multi-link device may directly transmit the first conversion frame to the second access point multi-link device, or may transmit the first conversion frame to the second access point multi-link device through the first access point multi-link device.

[0172] In the embodiment of the present application, the non-access point multi-link device may directly transmit the first conversion frame to the second access point multi-link device, or may transmit the first conversion frame to the second access point multi-link device through the first access point multi-link device.

[0173] In some embodiments, the first conversion frame includes:

[0174] a switch request frame sent by the non-access point multi-link device to the second access point multi-link device, the switch request frame being used to request a switch from the first access point multi-link device to the second access point multi-link device;

[0175] A switch response frame sent by the second access point multi-link device to the non-access point multi-link device, where the switch response frame is used to respond to the switch request frame.

[0176] In some embodiments, the transition request frame may be a fast transition request (FT Request) frame, and the transition response frame may be a fast transition response (FT Response) frame.

[0177] In the case where the non-access point multi-link device directly transmits the first switch frame to the second access point multi-link device, the non-access point multi-link device sends a switch request frame to the second access point multi-link device, and the second access point multi-link device sends a switch response frame to the non-access point multi-link device in response to the received switch request frame.

[0178] When the non-access point multi-link device transmits a first switch frame to the second access point multi-link device through the first access point multi-link device, the non-access point multi-link device sends a switch request frame to the second access point multi-link device through the first access point multi-link device. In response to the received switch request frame, the second access point multi-link device sends a switch response frame to the non-access point multi-link device through the first access point multi-link device.

[0179] For the second conversion frame, the non-access point multi-link device and the first access point multi-link device or the second access point multi-link device synchronize the second data of the first access point multi-link device to the second access point multi-link device through transmission of the second conversion frame, so that the non-access point multi-link device and the second access point multi-link device continue to perform data communication between the non-access point multi-link device and the first access point multi-link device.

[0180] The second data synchronization method may include: copying or migration.

[0181] In some embodiments, the second conversion frame includes at least one of the following:

[0182] a first switch confirmation frame sent by the non-access point multi-link device to the first access point multi-link device, wherein the first switch confirmation frame is used to request the first access point multi-link device to synchronize the second data to the second access point multi-link device;

[0183] a second switch confirmation frame sent by the first access point multi-link device to the second access point multi-link device, where the second switch confirmation frame is used by the first access point multi-link device to synchronize the second data to the second access point multi-link device;

[0184] a first conversion response frame sent by the first access point multi-link device to the non-access point multi-link device, the first conversion response frame being used to feedback a synchronization status of the second data;

[0185] A second switch response frame sent by the second access point multi-link device to the first access point multi-link device, where the second switch response frame is used to feed back a synchronization status of the second data to the first access point multi-link device.

[0186] In the embodiment of the present application, for a non-access point multi-link device, the second conversion frame received or sent includes:

[0187] a first switch confirmation frame sent by the non-access point multi-link device to the first access point multi-link device, wherein the first switch confirmation frame is used to request the first access point multi-link device to synchronize the second data to the second access point multi-link device;

[0188] A first conversion response frame sent by the first access point multi-link device to the non-access point multi-link device, where the first conversion response frame is used to feed back a synchronization status of the second data.

[0189] In the embodiment of the present application, as shown in FIG10 , the non-access point multi-link device sends a first conversion confirmation frame to the first access point multi-link device; the first access point multi-link device sends a second conversion confirmation frame to the second access point multi-link device in response to the received first conversion confirmation frame; the second access point multi-link device sends a second conversion response frame to the first access point multi-link device in response to the received second conversion confirmation frame; and the first access point multi-link device sends a first conversion response frame to the non-access point multi-link device in response to the received second conversion response frame.

[0190] The first transition confirmation frame and the second transition confirmation frame are transition confirmation frames sent on different links. In some embodiments, the transition confirmation frame can be understood as a fast transition confirmation (FT Confirm) frame.

[0191] The first conversion response frame and the second conversion response frame are conversion response frames sent on different links. In some embodiments, the conversion response frame can be understood as a fast conversion response (FT ACK) frame.

[0192] The first conversion response frame and the second conversion response frame may carry synchronization status indication information to indicate the synchronization status of the second data, and may also carry the second data synchronized by the second access point multi-link device to indicate the synchronization status of the second data.

[0193] In the embodiment of the present application, through the process shown in Figure 10, the second data of the first access point multi-link device used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device is synchronized to the second access point multi-link device. The synchronized second data here can be understood as the requested resources. Therefore, the process shown in Figure 10 can be understood as a resource request process.

[0194] In some embodiments, the first conversion confirmation frame carries third data of the non-access point multi-link device, the third data is used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device, and the third data is also used by the first access point multi-link device to determine the second data.

[0195] In the process shown in FIG10 , a first conversion confirmation frame sent by a non-access point multi-link device to a first access point multi-link device carries third data on the non-access point multi-link device side. The first access point multi-link device receives the first conversion confirmation frame and, in response to the first conversion confirmation frame, sends a second conversion confirmation frame to a second access point multi-link device, wherein the second conversion confirmation frame carries second data. The second data carried in the second conversion confirmation frame can be determined by the first access point multi-link device based on the received third data.

[0196] In one example, a first conversion confirmation frame sent by the Non AP MLD to the first access point multi-link device carries scenario information of the Non AP MLD end corresponding to the BA confirmation protocol established between the Non AP MLD and the first access point multi-link device, and a second conversion confirmation frame sent by the first access point multi-link device to the second access point multi-link device carries scenario information of the AP MLD end corresponding to the BA confirmation protocol established between the Non AP MLD and the first access point multi-link device, i.e., the first access point multi-link device end.

[0197] In one example, a first conversion confirmation frame sent by the Non AP MLD to the first access point multi-link device carries scenario information of the Non AP MLD end corresponding to the security association mechanism established between the Non AP MLD and the first access point multi-link device, and a second conversion confirmation frame sent by the first access point multi-link device to the second access point multi-link device carries scenario information of the AP MLD end corresponding to the security association mechanism established between the Non AP MLD and the first access point multi-link device, i.e., the first access point multi-link device end.

[0198] In some embodiments, the second data includes at least one of the following:

[0199] second information, where the second information is information about a Block Ack Agreement context of the first access point multi-link device;

[0200] The third information is information about a security association scenario of the first access point multi-link device.

[0201] The block confirmation protocol scenario can also be described as a block confirmation protocol context, a block confirmation protocol scenario (Block Ack context), or a block confirmation context, which is information about the maintained block confirmation process.

[0202] The security association scenario can also be described as a security association context, which is the information maintained during the security association process.

[0203] In the embodiment of the present application, the second conversion confirmation frame indicates the second information and / or the third information.

[0204] The first conversion response frame and / or the second conversion response frame may also indicate the second information and / or the third information.

[0205] In some embodiments, the first conversion confirmation frame may indicate information used for the block confirmation protocol scenario and / or the security association scenario in the non-access point multi-link device, so that the first access point multi-link device determines the second data synchronized to the second access point multi-link device based on the information used for the block confirmation protocol scenario and / or the security association scenario in the non-access point multi-link device indicated in the received first conversion confirmation frame.

[0206] The third conversion frame is used to transmit the third conversion frame between the non-access point multi-link device and the second access point multi-link device to associate or reassociate with the second access point multi-link device. In this embodiment of the present application, the third conversion frame is used for association or reassociation at the secondary access point multi-link device level.

[0207] In some embodiments, the third conversion frame includes at least one of the following:

[0208] an association request frame or a reassociation request frame sent by the non-access point multi-link device to the second access point multi-link device;

[0209] An association response frame or a reassociation response frame sent by the second access point multi-link device to the non-access point multi-link device.

[0210] After synchronizing the second data between the first access point multi-link device and the second access point multi-link device, the non-access point multi-link device is associated or re-associated with the second access point multi-link device through a third conversion frame, thereby achieving association or re-association at the subordinate access point multi-link device level.

[0211] The non-access point multi-link device sends an association request (Association Request) frame or a reassociation request (Re Association Request) frame to the second access point multi-link device. In response to the received association request (Association Request) frame or reassociation request (Re Association Request) frame, the second access point multi-link device sends an association response (Association Reponse) frame or a reassociation response (Re Association Reponse) frame to the non-access point multi-link device.

[0212] The non-access point multi-link device transmits data after associating or re-associating with the second access point multi-link device, wherein data transmission between the non-access point multi-link device and the first access point multi-link device may be continued based on the second data synchronized by the second conversion frame.

[0213] The following describes the frame format of the second conversion frame provided in the embodiment of the present application.

[0214] The second data used for synchronization in the second conversion frame may include: information of a block acknowledgement protocol scenario and / or information of a security association scenario.

[0215] In the scenario where the second data for synchronization in the second conversion frame includes information of the block confirmation protocol scenario

[0216] In some embodiments, the second conversion frame includes: a block acknowledgement protocol scenario element, wherein the block acknowledgement protocol scenario element is used to indicate information about a block acknowledgement protocol scenario.

[0217] For the first switch confirmation frame, the block acknowledgement protocol scenario element in the first switch confirmation frame is used to indicate information about the block acknowledgement protocol scenario of the non-access point multi-link device.

[0218] For the second switch confirmation frame, the block acknowledgement protocol scenario element in the second switch confirmation frame is used to indicate information about the block acknowledgement protocol scenario of the first access point multi-link device.

[0219] For the second conversion response frame or the first conversion response frame, the block acknowledgment protocol scenario element in the second conversion response frame or the first conversion response frame is used to indicate information about the block acknowledgment protocol scenario of the second access point multi-link device. Here, the information about the block acknowledgment protocol scenario of the second access point multi-link device is information about the block acknowledgment protocol scenario of the synchronized first access point multi-link device.

[0220] In the embodiment of the present application, the block acknowledgment protocol scenario element includes information about a block acknowledgment protocol scenario that a specific MLD has established and maintained with one or more peer MLDs. It is understood that the block acknowledgment protocol scenario can also be described as a block acknowledgment protocol state, or a block acknowledgment protocol scenario or state.

[0221] In some embodiments, the block acknowledgement protocol scenario element includes a block acknowledgement protocol scenario parameter control subfield and a block acknowledgement protocol scenario parameter set list subfield.

[0222] In one example, as shown in Figure 11, the Block Acknowledgement Protocol Scenario element includes the following subfields: Element ID, Length, Element ID Extension, Block Acknowledgement Protocol Scenario Parameter Control, and Block Acknowledgement Protocol Scenario Parameter Set List. The Element ID, Length, and Element ID Extension fields in the Block Acknowledgement Protocol Scenario element follow the common definitions of the relevant elements in the relevant protocols.

[0223] In some embodiments, the block acknowledgement protocol scenario element includes a block acknowledgement protocol scenario parameter control field, wherein the block acknowledgement protocol scenario parameter control field is used to indicate at least one of:

[0224] The device where the block confirmation protocol scenario described by the block confirmation protocol scenario element is located;

[0225] Whether the peer device targeted by the block acknowledgment protocol scenario of the device described by the block acknowledgment protocol scenario element is the same device;

[0226] When the opposite device targeted by the block confirmation protocol scenario of the device described by the block confirmation protocol scenario element is the same device, the opposite device targeted by the block confirmation protocol scenario;

[0227] The block confirmation protocol scenario element includes the number of block confirmation protocol scenario parameter sets.

[0228] The device where the block confirmation protocol scenario described by the block confirmation protocol scenario element resides may be the MAC address of the corresponding device.

[0229] The device where the block acknowledgement protocol scenario described by the block acknowledgement protocol scenario element resides can be indicated by the first field in the block acknowledgement protocol scenario parameter control field. The first field in the block acknowledgement protocol scenario parameter control field can be defined as an MLD MAC address subfield indication.

[0230] The first field of the block acknowledgement protocol scenario parameter control field in the first conversion acknowledgement frame indicates a non-access point multi-link device.

[0231] The first field of the block acknowledgement protocol scenario parameter control field in the second conversion acknowledgement frame indicates the first access point multi-link device.

[0232] The first field of the block acknowledgement protocol scenario parameter control field in the second conversion response frame or the first conversion response frame indicates the second access point multi-link device.

[0233] Whether the opposite-end device targeted by the block acknowledgment protocol scenario of the device described by the block acknowledgment protocol scenario element is the same device may be indicated by the second field in the block acknowledgment protocol scenario parameter control field.

[0234] In one example, when the value of the second field in the block confirmation protocol scenario parameter control domain is 0, it indicates that the block confirmation protocol scenario of the MLD described by the block confirmation protocol scenario element targets the same MLD for the opposite end. When the value of the second field is 1, it indicates that the block confirmation protocol scenario of the MLD described by the block confirmation protocol scenario element targets different MLDs for the opposite end, that is, the opposite end includes multiple MLDs.

[0235] The second field in the block acknowledgement protocol scenario parameter control field may be defined as whether the peer device is in the same device subdomain.

[0236] In one example, it is assumed that a STA switches from AP MLD1 to AP MLD2. In the FT confirm frame sent by the STA to AP MLD1, the device described by the block confirmation protocol scenario element is the STA, and the opposite device targeted by the block confirmation protocol scenario includes AP MLD1. In the FT confirm frame sent by AP MLD1 to AP MLD2, the device described by the block confirmation protocol scenario element includes AP MLD1, and the opposite device targeted by the block confirmation protocol scenario includes the STA. In the FT ACK frame sent by AP MLD2 to AP MLD1, the device described by the block confirmation protocol scenario element is AP MLD2, and the opposite device targeted by the block confirmation protocol scenario includes the STA. In the FT ACK frame sent by AP MLD1 to the STA, the device described by the block confirmation protocol scenario element is AP MLD2, and the opposite device targeted by the block confirmation protocol scenario includes the STA.

[0237] When the opposite device targeted by the block acknowledgment protocol scenario of the device described by the block acknowledgment protocol scenario element is the same device, the opposite device targeted by the block acknowledgment protocol scenario can be indicated by the third field in the block acknowledgment protocol scenario parameter control field.

[0238] When the block confirmation protocol scenario of the device described by the block confirmation protocol scenario element targets the same device, the third field in the block confirmation protocol scenario parameter control field indicates the opposite device; when the block confirmation protocol scenario of the device described by the block confirmation protocol scenario element targets multiple devices, the block confirmation protocol scenario parameter control field may not include the third field.

[0239] The third field in the block acknowledgment protocol scenario parameter control field may be defined as a peer device MAC address subfield or a peer MLD MAC subfield (Peer MLD MAC).

[0240] The number of individual block acknowledgment protocol scenario parameter set subfields in the block acknowledgment protocol scenario parameter set list field in the block acknowledgment protocol scenario element may be indicated by the fourth field in the block acknowledgment protocol scenario parameter control field.

[0241] The fourth field in the block confirmation protocol scenario parameter control field can also be understood as indicating the number of single block confirmation protocol scenario parameter set subfields in the block confirmation protocol scenario parameter set list field in the block confirmation protocol scenario element, wherein a single block confirmation protocol scenario parameter set subfield in a block confirmation protocol scenario parameter set list field indicates a block confirmation protocol scenario parameter set.

[0242] In one example, as shown in FIG12 , the block acknowledgment protocol scenario parameter control field includes the following subfields: MLD MAC address, whether the peer MLD is the same MLD, peer MLD MAC address, number of single block acknowledgment protocol scenario parameter sets, and reservation.

[0243] In some embodiments, the block confirmation protocol scenario element includes a block confirmation protocol scenario parameter set list field, the block confirmation protocol scenario parameter set list field includes at least one block confirmation protocol scenario parameter set subfield, i.e., a single block confirmation protocol scenario parameter set subfield, and one block confirmation protocol scenario parameter set subfield is used to indicate a block confirmation protocol scenario parameter set.

[0244] The block acknowledgement protocol scenario parameter set list field may include not only a block acknowledgement protocol scenario parameter set subfield but also a padding subfield.

[0245] In an example, as shown in FIG13 , the block acknowledgement protocol scenario parameter set subfield includes a plurality of single block acknowledgement protocol scenario parameter set subfields and a padding subfield.

[0246] In some embodiments, the block acknowledgement protocol scenario parameter set subfield is used to indicate at least one of the following:

[0247] The role of the device in the corresponding block confirmation protocol scenario;

[0248] The corresponding block confirmation protocol scenario targets the peer device;

[0249] Block confirmation parameter set;

[0250] Block confirmation timeout value.

[0251] The roles of the device in the corresponding block confirmation protocol scenario may include: initiator and receiver.

[0252] The role of the device in the corresponding block acknowledgment protocol scenario in the block acknowledgment protocol scenario can be indicated by the fifth field in the block acknowledgment protocol scenario parameter set subfield. The fifth field in the block acknowledgment protocol scenario parameter set subfield can also be defined as a device role field or an MLD role field.

[0253] In one example, when the value of the MLD role field is 0, it indicates that the MLD in the block confirmation protocol scenario described by the single block confirmation protocol scenario parameter set plays the role of the initiator MLD in the block confirmation protocol; when the value of the MLD role field is 1, it indicates that the MLD in the block confirmation protocol scenario described by the single block confirmation protocol scenario parameter set plays the role of the receiver MLD in the block confirmation protocol.

[0254] The opposite-end device targeted by the corresponding block acknowledgment protocol scenario may be indicated by the sixth field in the block acknowledgment protocol scenario parameter set subfield.

[0255] If the device described in the block acknowledgment protocol scenario is a Non-AP MLD, the peer device targeted by the block acknowledgment protocol scenario is the first AP MLD or a third AP MLD affiliated with the first AP MLD.

[0256] If the device described in the block acknowledgment protocol scenario is the first AP MLD or a third AP MLD affiliated with the first AP MLD, the peer device targeted by the block acknowledgment protocol scenario is a non-AP MLD.

[0257] The sixth field of the block acknowledgment protocol scenario parameter set subfield may be defined as a Peer MLD MAC address, indicating the MAC address of the peer device targeted by the corresponding block acknowledgment protocol scenario.

[0258] The relevant parameter set of the established block confirmation protocol corresponding to the corresponding block confirmation protocol scenario can be indicated by the seventh field in the block confirmation protocol scenario parameter set subfield.

[0259] The block confirmation timeout value is used to indicate the duration of the information of the current block confirmation protocol scenario. If the information of the current block confirmation protocol scenario is not frame-exchanged within the duration, the information of the current block confirmation protocol scenario becomes invalid.

[0260] The block confirmation timeout value may be indicated by the eighth field in the block confirmation protocol scenario parameter set subfield. The eighth field in the block confirmation protocol scenario parameter set subfield may also be defined as a confirmation timeout value field.

[0261] In one example, the ACK Timeout Value field contains a duration, in time units (TUs), after which the Block Ack protocol will terminate if no frame exchange sequence occurs using the Block Ack protocol within this duration. This field is set to 0 to disable the timeout.

[0262] In some embodiments, the block confirmation parameter set includes at least one of the following:

[0263] Third indication information indicating whether aggregated MAC service data units are supported;

[0264] Block confirmation strategy;

[0265] Flow ID;

[0266] Buffer size.

[0267] The third indication information may be indicated by the first subfield in the seventh field of the block acknowledgment protocol scenario parameter set subfield, and the first subfield in the seventh field of the block acknowledgment protocol scenario parameter set subfield may be defined as an A-MSDU support subfield.

[0268] In one example, when the value of the A-MSDU Supported field is 0, the number of bytes that each buffer can accommodate is equal to the maximum size of the MSDU. When the value of the A-MSDU Supported field is 1, the number of bytes that each buffer can accommodate is equal to the maximum size of the A-MSDU supported by the STA.

[0269] The block acknowledgment policy may be indicated by the second subfield in the seventh field of the block acknowledgment protocol scenario parameter set subfield, and the second subfield may be defined as a Block Ack Policy subfield.

[0270] The stream identifier may be indicated by the third subfield in the seventh field of the block acknowledgment protocol scenario parameter set subfield, and the third subfield may be defined as a stream identifier (TID) field.

[0271] The buffer size may be indicated by the fourth subfield in the seventh field of the block confirmation protocol scenario parameter set subfield, and the fourth subfield may be defined as a buffer size field.

[0272] In one example, as shown in FIG14 , the block acknowledgment parameter set subfield includes the following subfields: A-MSDU Supported, Block Ack Policy, Stream Identifier (TID), and Buffer Size.

[0273] In some embodiments, if the block acknowledgment protocol scenario parameter set subfield is used to indicate that the role of the device in the corresponding block acknowledgment protocol scenario is an initiator in the block acknowledgment protocol scenario, the block acknowledgment protocol scenario parameter set subfield is further used to indicate at least one of the following:

[0274] Send window starting sequence number;

[0275] Send window size.

[0276] The send window starting sequence number and send window size are send buffer control parameters.

[0277] The send window size can be understood as the number of buffers available for the corresponding TID.

[0278] In some embodiments, the block acknowledgment protocol scenario parameter set subfield may further include: a ninth field and a tenth field, wherein the ninth field is used to indicate a sending window starting sequence number, and the tenth field is used to indicate a sending window size.

[0279] The ninth field in the block acknowledgment protocol scenario parameter set subfield may be defined as a send window start sequence number (WinStartO) field.

[0280] The tenth field in the block acknowledgment protocol scenario parameter set subfield may be defined as a send window size (WinSizeO) field.

[0281] In one example, for the initiator, as shown in Figure 15, the block confirmation protocol scenario parameter set subfield includes the following fields: MLD role (initiator MLD), Peer MLD (RA, MLD MAC address), block confirmation parameter set (Block Ack Parameter Set), block confirmation timeout value (Block Ack Timeout), send window starting sequence number (WinStartO), send window size (WinSizeO).

[0282] In some embodiments, if the block acknowledgment protocol scenario parameter set subfield is used to indicate that the role of the device in the corresponding block acknowledgment protocol scenario is a receiver in the block acknowledgment protocol scenario, the block acknowledgment protocol scenario parameter set subfield is further used to indicate at least one of the following:

[0283] Receive buffer starting sequence number;

[0284] Receive window size;

[0285] Record the starting sequence number of the bitmap;

[0286] Record the maximum sequence number of the bitmap;

[0287] Record the bitmap size.

[0288] The receive buffer starting sequence number (WinStartB) is a receive reordering buffer (Receive Reordering Buffer) control parameter, indicating the value of the sequence number subfield of the first MSDU or A-MSDU (arranged in ascending sequence number order) that has not yet been received.

[0289] The receive buffer start sequence number (WinStartB) may be indicated by the eleventh field in the block confirmation protocol scenario parameter set subfield, and the eleventh field may be defined as the WinStartB field.

[0290] The receive window size (WinSizeB) is a receive reordering buffer (Receive Reordering Buffer) control parameter, indicating the receive window size.

[0291] The receiving window size (WinSizeB) may be indicated by the twelfth field in the block acknowledgment protocol scenario parameter set subfield, and the twelfth field may be defined as the WinStartB field.

[0292] The record bitmap start sequence number (WinStartR) is a Scoreboard Context Control parameter, a 12-bit unsigned integer start sequence number, which represents the lowest sequence number position in the block confirmation record bitmap (indexed by sequence number).

[0293] The record bitmap start sequence number may be indicated by the thirteenth field in the block confirmation protocol scenario parameter set subfield. The thirteenth field may be defined as the WinStartR field.

[0294] Record the maximum sequence number of the bitmap (WinEndR), which indicates the highest sequence number of the current transmission window.

[0295] The maximum sequence number of the record bitmap is indicated by the fourteenth field in the block confirmation protocol scenario parameter set subfield, and the fourteenth field can be defined as the WinEndR field.

[0296] Record bitmap size (WinSizeR), which is a Scoreboard Context Control parameter, the maximum transmission window size, is set to the smaller of the bitmap length (BitmapLength) and the Buffer size field of the relevant response frame of the Establish Block Return protocol.

[0297] The record bitmap size is indicated by the fifteenth field in the block confirmation protocol scenario parameter set subfield, and the fifteenth field can be defined as the WinSizeR field.

[0298] In one example, for the receiver, as shown in Figure 16, the block acknowledgment protocol scenario parameter set subfield includes the following fields: MLD role (initiator MLD), Peer MLD (RA, MLD MAC address), block acknowledgment parameter set (Block Ack Parameter Set), block acknowledgment timeout value (Block Ack Timeout), receive buffer starting sequence number (WinStartB), receive window size (WinSizeB), record bitmap starting sequence number (WinStartR), record bitmap maximum sequence number (WinEndR), record bitmap size (WinSizeR).

[0299] In the scenario where the second data used for synchronization in the second conversion frame includes information about the security association scenario

[0300] In some embodiments, the second conversion frame includes: a security association scenario element, where the security association scenario element is used to indicate information about a security association scenario.

[0301] The security association context element includes information such as data encryption / decryption and / or integrity protection for security association established and maintained by a specific MLD with one or more peer MLDs, the verified sender PN configuration, PN counter status information, and / or the receiver replay detection context and replay counter status information.

[0302] In some embodiments, the security association scenario element includes a security association scenario parameter control field and a security association scenario parameter set list field.

[0303] In one example, as shown in FIG17 , the security association context element includes the following subfields: Element ID, Length, Element ID Extension, SA Context Parameters Control, and SA Context Parameters Set List.

[0304] In some embodiments, the security association scenario element includes a security association scenario parameter control field, and the security association scenario parameter control field is used to indicate at least one of the following:

[0305] The device where the security association scenario described by the security association scenario element is located;

[0306] Whether the peer device targeted by the security association scenario of the device described by the security association scenario element is the same device;

[0307] When the opposite device targeted by the security association scenario of the device described by the security association scenario element is the same device, the opposite device targeted by the security association scenario;

[0308] The number of security association scenario parameter sets included in the security association scenario element.

[0309] The device where the security association scenario described by the security association scenario element resides may be the MAC address of the corresponding device.

[0310] The device where the security association scenario described by the security association scenario element resides can be indicated by the first field in the security association scenario parameter control field. The first field in the security association scenario parameter control field can be defined as an MLD MAC address subfield indication.

[0311] The first field of the security association scenario parameter control field in the first conversion confirmation frame indicates a non-access point multi-link device.

[0312] The first field of the security association scenario parameter control field in the second conversion confirmation frame indicates the first access point multi-link device.

[0313] The first field of the security association scenario parameter control field in the second conversion response frame or the first conversion response frame indicates a second access point multi-link device.

[0314] Whether the opposite-end device targeted by the security association scenario of the device described by the security association scenario element is the same device may be indicated by the second field in the security association scenario parameter control field.

[0315] In one example, when the value of the second field of the security association scenario parameter control domain is 0, it indicates that the security association scenario of the MLD described by the security association scenario element targets the same MLD for the opposite end. When the value of the second field of the security association scenario parameter control domain is 1, it indicates that the security association scenario of the MLD described by the security association scenario element targets multiple MLDs for the opposite end.

[0316] The second field of the security association scenario parameter control field may be defined as whether the peer device is in the same device subdomain.

[0317] In one example, it is assumed that a STA switches from AP MLD1 to AP MLD2. In the FT confirm frame sent by the STA to AP MLD1, the device described by the security association scenario element is the STA, and the opposite device targeted by the security association scenario includes AP MLD1. In the FT confirm frame sent by AP MLD1 to AP MLD2, the device described by the security association scenario element is AP MLD1, and the opposite device targeted by the security association scenario includes the STA. In the FT ACK frame sent by AP MLD2 to AP MLD1, the device described by the security association scenario element is AP MLD2, and the opposite device targeted by the security association scenario includes the STA. In the FT ACK frame sent by AP MLD1 to the STA, the device described by the security association scenario element is AP MLD2, and the opposite device targeted by the security association scenario includes the STA.

[0318] When the opposite device targeted by the security association scenario of the device described by the security association scenario element is the same device, the opposite device targeted by the security association scenario can be indicated by the third field in the security association scenario parameter control field.

[0319] When the opposite device targeted by the security association scenario of the device described by the security association scenario element is the same device, the third field of the security association scenario parameter control domain indicates the opposite device; when the opposite device targeted by the security association scenario of the device described by the security association scenario element is multiple devices, the security association scenario parameter control domain may not include the third field.

[0320] The third field of the security association scenario parameter control field may be defined as a peer device MAC address subfield or a peer MLD MAC subfield (Peer MLD MAC).

[0321] The number of security association scenario parameter set subfields in the security association scenario parameter set list field in the block security association scenario element may be indicated by the fourth field in the security association scenario parameter control field.

[0322] The fourth field of the security association scenario parameter control domain can also be understood as indicating the number of security association scenario parameter set subdomains in the security association scenario parameter set list domain in the security association scenario element, wherein a security association scenario parameter set subdomain in a security association scenario parameter set list domain indicates a security association scenario parameter set.

[0323] In one example, as shown in FIG18 , the security association scenario parameter control field includes the following subfields: MLD MAC address, whether the peer MLD is the same MLD, peer MLD MAC address, number of security association scenario parameter sets, and reservation.

[0324] In some embodiments, the security association scenario element includes a security association scenario parameter set list field, the security association scenario parameter set list field includes at least one security association scenario parameter set subfield, and one of the security association scenario parameter set subfields is used to indicate a security association scenario parameter set.

[0325] In one example, as shown in FIG19 , the security association scenario parameter set list field includes multiple security association scenario parameter set sub-fields.

[0326] In some embodiments, the security association scenario parameter set subfield is used to indicate at least one of the following:

[0327] The role of the device in the corresponding security association scenario;

[0328] The peer device targeted by the corresponding security association scenario;

[0329] The security association type of the corresponding security association scenario.

[0330] The roles of the device in the corresponding security association scenario may include: a receiving end and a sending end.

[0331] The role of the device in the corresponding security association scenario in the security association scenario can be indicated by the fifth field in the security association scenario parameter set subfield. The fifth field in the security association scenario parameter set subfield can also be defined as a device role field or an MLD role field.

[0332] In one example, when the value of the MLD role field is 0, it means that the MLD where the security association scenario described by the security association scenario parameter set is located plays the role of the receiving end MLD, that is, it describes the receiving end replay scenario parameter set; when the value of the MLD role field is 1, it means that the MLD where the security association scenario described by the security association scenario parameter set is located plays the role of the sending end MLD, that is, it describes the sending end PN counter scenario parameter set.

[0333] The opposite device targeted by the corresponding security association scenario may be indicated by the sixth field in the security association scenario parameter set subfield.

[0334] The sixth field of the security association scenario parameter set subfield may be defined as a Peer MLD MAC address, indicating the MAC address of the peer device targeted by the corresponding security association scenario.

[0335] If the device described in the security association protocol scenario is a Non-AP MLD, the peer device targeted by the security association scenario is the first AP MLD or a third AP MLD affiliated with the first AP MLD.

[0336] If the device described in the security association is the first AP MLD or the third AP MLD affiliated with the first AP MLD, the peer device targeted by the security association scenario is the Non-AP MLD.

[0337] The security association type of the security association scenario includes one of the following: PTKSA, GTKSA, and TPKSA.

[0338] The security association type of the corresponding security association scenario can be indicated by the seventh field in the security association scenario parameter set subfield. The seventh field in the security association scenario parameter set subfield can be defined as a PTKSA / GTKSA / TPKSA field.

[0339] The PTKSA / GTKSA / TPKSA field indicates the security association type corresponding to the playback scenario described by the Playback Scenario Parameter Set subfield. In one example, as shown in Table 1, different values ​​in the PTKSA / GTKSA / TPKSA field represent different security association types. For example, if the PTKSA / GTKSA / TPKSA subfield indicates PTKSA, the Playback Count subfield in the Playback Scenario Parameter Set subfield corresponds to the PTKSA Playback Count value.

[0340] Table 1 PTKSA / GTKSA / TPKSA domain values ​​and their meanings

[0341] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the role of the device in the corresponding security association scenario is a receiving end in the security association scenario; the security association scenario parameter set subfield is further used to indicate at least one of the following:

[0342] Replay counter number;

[0343] TID;

[0344] The count of the replay counter for the TID.

[0345] The number of replay counters may be indicated by the eighth field in the security association scenario parameter set subfield, and the eighth field may be defined as the number of replay counters field.

[0346] The TID may be indicated by the ninth field in the security association scenario parameter set subfield, and the ninth field may be defined as a TID field.

[0347] The count of the replay counter for the TID may be indicated by the tenth field in the security association scenario parameter set subfield, and the tenth field may be defined as the count of replay counter field.

[0348] In the embodiment of the present application, according to the number of replay counters indicated by the security association scenario parameter set subfield, the security association scenario parameter set subfield includes a corresponding number of TIDs and counts of the replay counters for the TIDs.

[0349] In one example, for the receiving end, as shown in Figure 20, the security association scenario parameter set subfield includes the following fields: MLD role, Peer MLD (RA, MLD MAC address), PTKSA / GTKSA / TPKSA, the number of replay counters, TID, the count of replay counter,..., TID, the count of replay counter.

[0350] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the role of the device in the corresponding security association scenario is a sender in the security association scenario; the security association scenario parameter set subfield is further used to indicate at least one of the following:

[0351] Packet number counter quantity;

[0352] TID;

[0353] The count of the packet number counter for the TID.

[0354] The number of packet number counters may be indicated by the eleventh field in the security association scenario parameter set subfield, and the eleventh field may be defined as the number of PN counters field.

[0355] The TID may be indicated by the twelfth field in the security association scenario parameter set subfield, and the twelfth field may be defined as a TID field.

[0356] The count of the packet number counter for the TID may be indicated by the thirteenth field in the security association scenario parameter set subfield, and the thirteenth field may be defined as the count of the PN Counter field.

[0357] In the embodiment of the present application, according to the number of packet number counters indicated by the security association scenario parameter set subfield, the security association scenario parameter set subfield includes a corresponding number of TIDs and counts of the packet number counters for the TIDs.

[0358] In one example, for the sending end, as shown in Figure 21, the security association scenario parameter set subfield includes the following fields: MLD role, Peer MLD (RA, MLD MAC address), PTKSA / GTKSA / TPKSA, the number of PN counters, TID, the count of PN counter,..., TID, the count of PN counter.

[0359] In some embodiments, the second conversion frame further includes at least one of the following:

[0360] Fourth indication information, where the fourth indication information is used to indicate that the second data includes information of a block confirmation protocol scenario and / or a security association scenario.

[0361] The fourth indication information may be used to indicate the resource type requested by the second conversion frame. Here, the resource requested by the second conversion frame may be understood as the resource type of the information included in the second data packet. The resource type may include: block acknowledgement protocol scenario and / or security association scenario.

[0362] If the resource type indicated by the fourth indication information includes the block acknowledgement protocol scenario, then:

[0363] Including a block confirmation protocol scenario element in the resource request frame (the first conversion confirmation frame and the second conversion confirmation frame);

[0364] The resource response frame (the first conversion response frame and the second conversion response frame) includes a block acknowledgement protocol scenario element.

[0365] The non-access point multi-link device serving as the FTO sends a resource request frame carrying a block acknowledgment protocol scenario element to the first access point multi-link device, requesting the second access point multi-link device to establish a block acknowledgment protocol scenario (or state). After receiving the resource request frame, the first access point multi-link device copies or migrates the corresponding block acknowledgment protocol scenario (or state) currently held by the first access point multi-link device to the second access point multi-link device, and based on the establishment status of the block acknowledgment protocol scenario (or state) performed by the second access point multi-link device, replies a resource response to the first access point multi-link device, providing feedback on the establishment status of the block acknowledgment protocol scenario (or state).

[0366] If the resource type indicated by the fourth indication information includes a security association scenario, then:

[0367] Including a security association scenario element in the resource request frame (the first conversion confirmation frame and the second conversion confirmation frame);

[0368] The resource response frame (the first conversion response frame and the second conversion response frame) includes a security association scenario element.

[0369] The non-access point multi-link device serving as the FTO sends a resource request frame carrying a security-associated scenario element to the first access point multi-link device, requesting the second access point multi-link device to establish a security-associated scenario (or state). After receiving the resource request frame, the first access point multi-link device copies or migrates the corresponding security-associated scenario (or state) currently held by the first access point multi-link device to the second access point multi-link device, and responds to the first access point multi-link device with a resource response based on the establishment status of the security-associated scenario (or state) performed by the second access point multi-link device, providing feedback on the establishment status of the security-associated scenario (or state).

[0370] In some embodiments, based on the wireless communication method shown in FIG5 , the method further includes:

[0371] The non-access point multi-link device receives or sends a second frame, where the second frame is used for the non-access point multi-link device to associate or re-associate with the first access point multi-link device.

[0372] In some embodiments, based on the wireless communication method shown in FIG6 , if the access point multi-link device is the first access point multi-link device, the method further includes:

[0373] The access point multi-link device sends or receives a second frame, where the second frame is used for the non-access point multi-link device to associate or re-associate with the first access point multi-link device.

[0374] Here, before switching from the first access point multi-link device to the second access point multi-link device, the non-access point multi-link device associates or re-associates with the first access point multi-link device by interacting with the second frame of the first access point multi-link device.

[0375] In some embodiments, the second frame includes first information, and the first information includes at least one of the following:

[0376] first indication information, where the first indication information is used to indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD;

[0377] Second indication information, where the second indication information is used to indicate the third access point multi-link device.

[0378] Here, the description of the first information can refer to the description of the first information included in the above-mentioned first frame, and will not be repeated here.

[0379] In some embodiments, the first information is located in a mobile domain element MDE.

[0380] In the embodiment of the present application, the first frame includes MDE and / or the second frame may include MDE.

[0381] The first indication information in the first frame is used to determine whether the current non-access point multi-link device indicates or is allowed to switch between different subordinate access point multi-link devices of the same mobility domain access point multi-link device, i.e., the third access point multi-link device. The second indication information in the second frame is used to determine whether the first access point multi-link device and the second access point multi-link device are subordinate to the same mobility domain access point multi-link device, i.e., the third access point multi-link device, or are capable of associating with and then re-associating with the second access point multi-link device, thereby managing or controlling the switching of the non-access point multi-link device based on the third access point multi-link device.

[0382] The first information in the second frame is used to determine whether the non-access point multi-link device is associated or re-associated with the third access point multi-link device, thereby associating or re-associating with the first access point multi-link device to which the third access point multi-link device is attached.

[0383] In some embodiments, the first indication information is located in the conversion capability and policy field of the MDE.

[0384] In one example, as shown in FIG22 , the transition capability and policy domain includes the following sub-domains: fast BSS transition through DS, resource request protocol capability, whether FT is in the same mobile domain AP MLD (FTinMobileDomainMLD), and reservation.

[0385] In some embodiments, the second indication information includes at least one of the following:

[0386] The device identifier of the third access point multi-link device;

[0387] The MAC address of the third access point multi-link device.

[0388] In the embodiment of the present application, the second indication information is optional. In some embodiments, if the first access point multi-link device and the second access point multi-link device are attached to the same third access point multi-link device, the first information includes the second indication information.

[0389] In one example, as shown in FIG23 , the MDE includes the following fields: Element ID, Length, MD ID, FT Capability and Policy, MD AP MLD ID, and MD AP MLD MAC address.

[0390] It is understandable that each field included in a frame format provided in an embodiment of the present application can exist independently, and fields or domains can be added, modified or deleted based on the provided frame format according to actual needs.

[0391] The following further describes the wireless communication method provided in the embodiments of the present application.

[0392] This application proposes a method for converting non-AP MLD (or STA) from the current AP MLD (or AP) to the target AP MLD (or AP) based on the mobile domain AP MLD architecture. By optimizing the FT protocol and utilizing the replication, migration, or update of related communication scenarios and states, the data continuity between STA and DS or between non-AP MLD and DS is maintained.

[0393] High-level architecture of the mobile domain AP MLD and its subordinate AP MLDs

[0394] The high-level architecture of the mobility domain AP MLD and its subordinate AP MLDs provided in an embodiment of the present application is shown in FIG24 . Based on the architecture shown in FIG9 , the access point multi-link device is a Non-AP MLD, the MLD address of the Non-AP MLD is P, and the subordinate Non-AP SSTAs include: Non-AP STA1 with a MAC address of y and Non-AP STA2 with a MAC address of z. The Non-AP MLD includes an MLD upper MAC sublayer and an MLD lower MAC sublayer. The subordinate Non-AP STAs are located in the MLD lower MAC sublayer, and different subordinate Non-AP STAs establish links with the subordinate APs in subordinate AP MLD1 and subordinate AP MLD2 via different links. The link between Non-AP STA1 attached to Non-AP SMLD and AP1 attached to AP MLD1 is link 1. The link between Non-AP STA2 attached to Non-AP SMLD and AP2 attached to AP MLD1 is link 2. The link between Non-AP STA1 attached to Non-AP SMLD and AP3 attached to AP MLD2 is link 3. The link between Non-AP STA2 attached to Non-AP SMLD and AP4 attached to AP MLD2 is link 4.

[0395] In the embodiment of the present application, when link 1 or link 2 is connected, link 3 and link 4 are not connected. As the Non-AP SMLD moves, link 1 or link 2 is not connected, and link 3 and link 4 are connected, thereby achieving the conversion of the Non-AP SMLD from AP MLD1 to AP MLD2.

[0396] The common MAC sublayer functions of the mobile domain AP MLD include:

[0397] 1. Provide the distributed system access function (DSAF) to the subordinate AP MLD of the mobility domain AP MLD;

[0398] 2. Authentication, association, and reassociation between non-AP MLD and mobile domain AP MLD;

[0399] 3. Security associations (such as PMKSA, PTKSA) and management of GTK / IGTK / BIGTK distribution;

[0400] 4. Manage the partial association and reassociation between the non-AP MLD and the AP MLD corresponding to the mobility domain AP MLD;

[0401] 5. For the subordinate AP MLD associated with the non-AP MLD, select the MAC address of the subordinate AP MLD for data transmission;

[0402] 6. Synchronize (copy or migrate) all or part of the upper-UMAC state and buffer information of the MLD-affiliated upper-UMAC of the mobility domain AP MLD.

[0403] 7. MLD-level management information exchange / indication is performed through the MAC sublayer of the MLD-attached network.

[0404] The entire or partial upper-UMAC state and buffer information of the MLD-affiliated upper-MAC of the mobility domain AP MLD are synchronized (copied or migrated), including:

[0405] For a specific non-AP MLD associated with a mobility domain AP MLD, synchronization (copying or migrating) is performed between the current mobility domain AP MLD-affiliated AP MLD associated with the non-AP MLD and the target mobility domain AP MLD-affiliated AP MLD. This involves synchronization of all or part of the upper layer (Upper-UMAC) status and buffer information of the upper layer MAC of the current subordinate AP MLD, thereby maintaining the continuity of data communication sessions and the persistence of transmitted data during the process of the non-AP MLD being associated with different subordinate AP MLDs of the mobility domain AP MLD due to roaming.

[0406] All or part of the upper-UMAC state and buffer information of the upper-layer MAC of the mobility domain AP MLD, namely, the session or protocol state and buffer information maintained for data exchange with a specific non-AP MLD (for a specific non-AP MLD):

[0407] (1) SN / PN allocation status and related buffer data of unicast frames;

[0408] (2) SN allocation status and related buffer data of group-addressed MAC Service Data Unit (MSDU);

[0409] (3) buffer data for energy saving in individually addressed frames;

[0410] (4) Block Ack session status and related duplicate detection and reordering buffer data;

[0411] (5) The PN counter status of the sending end and the replay detection status and related buffer data of the receiving end.

[0412] Block confirmation and security association scenarios and state definitions

[0413] To enable a non-AP MLD (or STA) to quickly transition from its current AP MLD (or AP) to its target AP MLD (or AP) for data connectivity, the system defines communication context and state-related elements or domains, including Block Ack context or state elements and Security Association context or state elements. These elements are used to replicate, migrate, or update Block Ack and Security Association context and state during the FT process, respectively.

[0414] FT protocol optimization and interactive frame type and format definition and function update

[0415] Frame type and format definitions and functional updates for the FT protocol and interactions for data connectivity within the mobile domain AP MLD architecture. This includes updates to the Mobility Domain Element (MDE), association and reassociation protocol, association and reassociation frames, and FT request and response protocol, FT resource request and response protocol, FT request frame (FT Request), FT response frame (FT Response), FT confirmation frame (FT Confirm), and FT acknowledgment frame (FT ACK).

[0416] The FT protocol based on data persistence includes the following processes:

[0417] (1) Non-AP MLD is associated with the current AP MLD and then associated with the mobility domain AP MLD scenario or the FT initial mobility domain AP MLD scenario;

[0418] (2) Non-AP MLD initiates the FT process from the current AP MLD to the target AP MLD in the mobility domain AP MLD scenario;

[0419] (3) For Non-AP MLD, the context and state of the mobility domain AP MLD and / or all or part of the context, state, and buffer of the corresponding subordinate MLD of the mobility domain AP MLD are copied or migrated from the current AP MLD to the target AP MLD.

[0420] (4) Non-AP MLD is reassociated with the target AP MLD in the mobile domain AP MLD scenario

[0421] The so-called associating a non-AP MLD with an AP MLD in the mobility domain AP MLD scenario (or associating a non-AP MLD with an AP MLD affiliated with a mobility domain AP MLD) refers to establishing a mapping relationship between the AP MLD affiliated with the mobility domain AP MLD and the non-AP MLD (including the mapping relationship between the mobility domain AP MLD and the AP MLD, and the mapping relationship between the AP MLD and the non-AP MLD), so that the non-AP MLD can be called (DSS). The non-AP MLD establishes a security association (such as PMKSA and PTKSA) with the mobility domain AP MLD. When the non-AP MLD switches from the current AP MLD affiliated with the mobility domain AP MLD to the target AP MLD affiliated with the mobility domain AP MLD in the mobility domain AP MLD scenario, the PMKSA and PTKSA can remain unchanged. That is, the non-AP MLD maintains a single unicast key, including the same pairwise master key (PMK) and pairwise transient key (PTK), when switching from the current AP MLD affiliated with the mobility domain AP MLD to the target AP MLD affiliated with the mobility domain AP MLD in the mobility domain AP MLD scenario.

[0422] The wireless communication method provided in the embodiments of the present application can be implemented as including but not limited to the following embodiments.

[0423] An AP MLD attached to a specific mobility domain AP MLD carries information about the mobility domain AP MLD to which it is attached (such as the identifier of the mobility domain AP MLD or the MAC address of the mobility domain AP MLD) in management frames such as beacon frames or probe frames it sends, and / or carries an MDE to indicate whether it supports BSS transition in the same mobility domain AP MLD scenario.

[0424] In this embodiment of the present application, the non-AP MLD and the current AP MLD are authenticated, as shown in FIG25 , including:

[0425] S2511. The Non-AP MLD sends an authentication request (Authentication-Request) frame to the current AP MLD (FTR).

[0426] S2512: The current AP MLD (FTR) sends an authentication response (Authentication-Reponse) frame to the Non-AP MLD.

[0427] Frame type and format definitions and functional updates for the FT protocol and interactions for data connectivity within the mobile domain AP MLD architecture. This includes updates to the Mobility Domain Element (MDE), association and reassociation protocol, association and reassociation frames, FT request and response protocol, FT resource request and response protocol, and frame definitions for the FT request, FT response, FT confirm, and FT acknowledgment frames.

[0428] (1) Non-AP MLD is associated with the current AP MLD and then associated with the mobility domain AP MLD scenario or the FT initial mobility domain AP MLD scenario. As shown in Figure 25, this includes:

[0429] S2521. The Non-AP MLD sends an association request frame or a reassociation request frame to the current AP MLD (FTR).

[0430] S2522: The current AP MLD (FTR) feeds back an association response frame or a reassociation response frame to the Non-AP MLD.

[0431] The association or reassociation request frame and the association or reassociation response frame include MDE and a basic multi-link element (Basic Multi-Link element), wherein the MDE can be marked as MDE (FTinMobileDomainMLD, MobileDomainMLD Info), indicating that the MDE carries the first indication information FTinMobileDomainMLD and the second indication information MobileDomainMLD Info.

[0432] It can be understood that the association request frame or the reassociation request frame carries an updated MDE (FTinMobileDomainMLD, MobileDomainMLD Info information field), instructing the non-AP MLD to associate with the AP MLD in the mobile domain AP MLD scenario (or the non-AP MLD is associated with the AP MLD affiliated with the mobile domain AP MLD), and indicates that fast switching between two AP MLDs affiliated with the same mobile domain AP MLD is supported or allowed.

[0433] The non-AP MLD is associated with the current AP MLD in the mobility domain AP MLD scenario and can successfully establish a session and data transmission with the current AP MLD.

[0434] (2) Non-AP MLD initiates the FT process from the current AP MLD to the target AP MLD in the mobility domain AP MLD scenario.

[0435] When Non-AP MLD (FTO) determines that it needs to switch from the current AP MLD to the target AP MLD in the mobility domain AP MLD scenario, FTO sends a fast switch request frame to the target FTR through the current FTR. Then, the target AP MLD (FTR) feeds back a fast switch response frame to Non-AP MLD through the current AP MLD (FTR).

[0436] As shown in Figure 25, it includes:

[0437] S2531 : The Non-AP MLD sends an FT request frame to the target AP MLD through the current AP MLD.

[0438] The FT request frame is FT Request (FTO, TargetAP, MDE (FTinMobileDomainMLD, MobileDomainMLD Info), Basic Multi-Link element).

[0439] S2532: The target AP MLD sends an FT response frame to the Non-AP MLD via the current AP MLD.

[0440] Among them, FT Response(FTO,TargetAP,MDE(FTinMobileDomainMLD,MobileDomainMLD Info),Basic Multi-Link element).

[0441] The FT request frame and the FT response frame carry an updated MDE (FTinMobileDomainMLD, MobileDomainMLD Info information field) to indicate support or permission for fast switching between two AP MLDs attached to the same mobility domain AP MLD.

[0442] (3) For Non-AP MLD, the context and state of the mobility domain AP MLD and / or all or part of the context, state, and buffer of the corresponding subordinate MLD of the mobility domain AP MLD are copied or migrated from the current AP MLD to the target AP MLD.

[0443] FTO sends an FT Confirm frame to the target FTR through the current FTR. Then, the target AP MLD (FTR) feeds back an FT ACK frame to the non-AP MLD through the current AP MLD (FTR).

[0444] As shown in Figure 25, it includes:

[0445] S2541: The Non-AP MLD sends an FT confirmation frame to the current AP MLD, and the current AP MLD sends an FT confirmation frame to the target AP MLD.

[0446] Among them, the FT confirmation frame is FT Confirm (FTO, TargetAP, MDE (FTinMobileDomainMLD, MobileDomainMLD Info), Resource information container (RIC)-Request (Block Ack Context element, SA context element), Basic Multi-Link element), indicating that the FT confirmation frame is used to request resources, and the requested resources are carried in the RIC-Request.

[0447] For the FT acknowledgment frame sent by the non-AP MLD to the current AP MLD, the Block Ack Context element carries the non-AP MLD-side context information corresponding to the BA acknowledgment protocol used by the non-AP MLD to request context information synchronization from the current AP MLD to the target AP MLD. The SA context element carries the non-AP MLD-side context information corresponding to the security association mechanism used by the non-AP MLD to request context information synchronization from the current AP MLD to the target AP MLD.

[0448] For the FT acknowledgment frame sent by the current AP MLD to the target AP MLD, the Block Ack Context element carries the context information of the AP MLD side corresponding to the BA acknowledgment protocol used to complete context information synchronization from the current AP MLD to the target AP MLD in response to the non-AP MLD request. The SA Context element carries the context information of the AP MLD side corresponding to the security association mechanism used to complete context information synchronization from the current AP MLD to the target AP MLD in response to the non-AP MLD request.

[0449] S2542: The target AP MLD sends an FT response frame to the current AP MLD, and the current AP MLD sends an FT response frame to the Non-AP MLD.

[0450] The FT response frame is FT ACK (FTO, TargetAP, MDE (FTinMobileDomainMLD, MobileDomainMLD Info), time element (TIE) (reassociation deadline (ReassociationDeadline)), RIC-Response (Block Ack Context element, SA Context element), Basic Multi-Link element), indicating the time limit for the FT response frame to respond to resources and reassociate. The response resources are carried in the RIC-Response.

[0451] FT Confirm and FT ACK carry Block Ack Context element and SA Context element, indicating related block confirmation protocol scenario (or state) information and security association scenario (or state) information.

[0452] In the FT ACK frame, the Block Ack Context element carries the context information of the AP MLD side corresponding to the BA acknowledgment protocol that completes the synchronization of context information from the current AP MLD to the target AP MLD in response to the non-AP MLD request. The SA Context element carries the context information of the AP MLD side corresponding to the security association mechanism that completes the synchronization of context information from the current AP MLD to the target AP MLD in response to the non-AP MLD request, thereby providing feedback on the synchronization result.

[0453] (4) Non-AP MLD is reassociated with the target AP MLD in the mobile domain AP MLD scenario

[0454] The non-AP MLD sends an association request frame or a reassociation request frame to the target AP MLD (FTR). The target AP MLD (FTR) then responds with an association response frame or a reassociation response frame. A successful reassociation occurs only if the time between the sending of the FT request frame and the sending of the reassociation request frame does not exceed the reassociation deadline.

[0455] As shown in Figure 25, it includes:

[0456] S2551. The Non-AP MLD sends an association request frame or a reassociation request frame to the target AP MLD (FTR).

[0457] The association request frame or reassociation request frame is (Re)Association Request (MDE (FTinMobileDomainMLD, MobileDomainMLD Info), Basic Multi-Link element);

[0458] S2552: The target AP MLD (FTR) feeds back an association response frame or a reassociation response frame to the Non-AP MLD.

[0459] The association response frame or the re-association response frame is (Re)Association Response (MDE (FTinMobileDomainMLD, MobileDomainMLD Info), Basic Multi-Link element).

[0460] The association request frame or reassociation request frame carries the updated MDE (FTinMobileDomainMLD, MobileDomainMLD Info information field), instructing the non-AP MLD to associate with the target AP MLD in the mobile domain AP MLD scenario (or the non-AP MLD is associated with the target AP MLD affiliated with the mobile domain AP MLD), and indicating support for fast switching between two AP MLDs affiliated with the same mobile domain AP MLD.

[0461] The so-called associating a non-AP MLD with an AP MLD in the mobility domain AP MLD scenario (or associating a non-AP MLD with an AP MLD affiliated with a mobility domain AP MLD) refers to establishing a mapping relationship between the AP MLD affiliated with the mobility domain AP MLD and the non-AP MLD (including the mapping relationship between the mobility domain AP MLD and the AP MLD, and the mapping relationship between the AP MLD and the non-AP MLD), so that the non-AP MLD can invoke DSSs. The non-AP MLD establishes a security association (such as PMKSA and PTKSA) with the mobility domain AP MLD. When the non-AP MLD switches from the current AP MLD affiliated with the mobility domain AP MLD to the target AP MLD affiliated with the mobility domain AP MLD in the mobility domain AP MLD scenario, the PMKSA and PTKSA can remain unchanged. That is, the non-AP MLD maintains the same unicast key, including the same pairwise master key (PMK) and pairwise transient key (PTK), when switching from the current AP MLD affiliated with the mobility domain AP MLD to the target AP MLD affiliated with the mobility domain AP MLD in the mobility domain AP MLD scenario.

[0462] Although current fast BSS transition (FT) can reduce the duration of connectivity loss between STAs and DSs, or between non-AP MLDs and DSs, during BSS transitions, data continuity between the STA (or Non-AP MLD) and DSs, or between non-AP MLDs and DSs, cannot be maintained because the STA (or Non-AP MLD) needs to reassociate and reestablish data transmission and reception protocols and scenarios when transitioning to the target AP (or target AP MLD). This patent proposes a method for transitioning a non-AP MLD (or STA) from the current AP MLD (or AP) to the target AP MLD (or AP) in a mobile domain AP MLD architecture. By optimizing the FT protocol and utilizing the replication, migration, or update of related communication scenarios and states, data continuity between the STA and DSs, or between non-AP MLDs and DSs, is maintained.

[0463] In the embodiment of the present application, in the embodiment shown in FIG25 , the current AP MLD and the target AP MLD belong to the same mobility domain AP MLD. The transition (FT) mechanism shown in FIG25 is also applicable to the transition of the non-AP MLD from the current AP MLD to the target AP MLD when the current AP MLD and the target AP MLD belong to different mobility domain AP MLDs. The difference is that, when the current AP MLD and the target AP MLD belong to the same mobility domain AP MLD, the second data is synchronized between different subordinate AP MLDs of the same mobility domain AP MLD. If the current AP MLD and the target AP MLD belong to different mobility domain AP MLDs, the second data is synchronized between the subordinate AP MLDs of different mobility domain AP MLDs.

[0464] It should be noted that the above embodiment describes the transition (FT) mechanism of non-AP MLD from the current AP MLD to the target AP MLD in the mobile domain AP MLD scenario. The wireless communication method provided in this application is also applicable to the transition (FT) mechanism of non-MLD sites from the current AP to the target AP in the mobile domain AP MLD scenario.

[0465] Although the current FT can reduce the length of time that connectivity is lost between a STA and a DS, or between a non-AP MLD and a DS, during a BSS transition, the STA (or Non-AP MLD) needs to reassociate and reestablish the data transmission and reception protocol and scenario when transitioning to a target AP (or target AP MLD). Therefore, data continuity between the STA and the DS, or between the non-AP MLD and the DS, cannot be maintained. In the wireless communication method provided in an embodiment of the present application, based on a method for transitioning a non-AP MLD (or STA) from a current AP MLD (or AP) to a target AP MLD (or AP) under a mobile domain AP MLD architecture, data continuity between the STA and the DS, or between the non-AP MLD and the DS, is maintained by optimizing the FT protocol and utilizing the replication, migration, or update of relevant communication scenarios and states.

[0466] The wireless communication method provided in the embodiment of the present application:

[0467] 1. A high-level architecture for the mobility domain AP MLD and its subordinate AP MLDs and non-AP MLDs is proposed, enabling fast data connectivity-oriented transition of non-AP MLDs (or STAs) from their current AP MLD (or AP) to their target AP MLD (or AP).

[0468] 2. To enable a non-AP MLD (or STA) to quickly transition from its current AP MLD (or AP) to its target AP MLD (or AP) for data connectivity, this protocol defines communication context and state-related elements or domains. These elements primarily include the Block Ack context or state element and the Security Association context or state element, which are used to replicate, migrate, or update the Block Ack and Security Association contexts and states during the FT process.

[0469] 2. Proposes frame type and format definitions and functional updates for the FT protocol and interaction for data connectivity in the mobile domain AP MLD architecture. These include: updates to the definition of the Mobility Domain Element (MDE), the association and reassociation protocol, the association and reassociation frames, the FT request and response protocol, the FT resource request and response protocol, and the FT request, response, confirmation, and acknowledgment frames.

[0470] The preferred embodiments of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above embodiments. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will not further explain the various possible combinations. For another example, the various different embodiments of the present application can also be arbitrarily combined, as long as they do not violate the idea of ​​the present application, they should also be regarded as the contents disclosed in the present application. For another example, under the premise of no conflict, the various embodiments and / or the technical features in each embodiment described in the present application can be arbitrarily combined with the prior art, and the technical solution obtained after the combination should also fall within the scope of protection of the present application.

[0471] It should also be understood that in the various method embodiments of the present application, the sequence numbers of the above-mentioned processes do not imply a precedence in the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data, where "downlink" is used to indicate the first direction of transmission of signals or data from a site to a user equipment in a cell, "uplink" is used to indicate the second direction of transmission of signals or data from a user equipment in a cell to a site, and "sidelink" is used to indicate the third direction of transmission of signals or data from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is merely a description of the association relationship between associated objects, indicating that three relationships can exist. Specifically, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0472] FIG26 is a schematic diagram of the structure of a non-access point multi-link device provided in an embodiment of the present application. As shown in FIG26 , the non-access point multi-link device 2600 includes:

[0473] The first communication unit 2601 is configured to receive or send a first frame, where the first frame is used by the non-access point multi-link device to switch between a first access point multi-link device and a second access point multi-link device, where the first access point multi-link device and the second access point multi-link device are attached to a third access point multi-link device, and the third access point multi-link device is a logical access point multi-link device.

[0474] It is understandable that the non-access point multi-link device further includes a processing unit and a storage unit. The processing unit is configured to parse the first frame or generate the first frame, and the storage unit is configured to store information carried by the first frame.

[0475] In some embodiments, the first access point multi-link device is an access point multi-link device whose affiliated access point AP is located at the same location; the second access point multi-link device is an access point multi-link device whose affiliated AP is located at the same location.

[0476] In some embodiments, the third access point multi-link device is used for at least one of the following:

[0477] Providing a connection service between the non-access point multi-link device or the auxiliary access point multi-link device and the distributed system DS;

[0478] maintaining data continuity of the non-access point multi-link device during roaming when switching between the first access point multi-link device and the second access point multi-link device;

[0479] authentication and / or association or reassociation of the non-access point multi-link device;

[0480] security association of said non-access point multi-link device;

[0481] distribution of all or part of the security association information of the non-access point multi-link device;

[0482] Synchronize all or part of the status and / or buffer information of the upper layer of the MAC layer of the attached access point multi-link device;

[0483] Managing the distribution of authentication information for links of non-access point multi-link devices;

[0484] Managing an association or re-association at an accessory access point multi-link device level between the non-access point multi-link device and the accessory access point multi-link device;

[0485] For a target access point multi-link device that has established a multi-link with the non-access point multi-link device among at least one attached access point multi-link device, selecting a MAC corresponding to the target access point multi-link device for transmission;

[0486] synchronization of first data between attached different access point multi-link devices, the first data being used to maintain data continuity in communications between the non-access point multi-link device and the attached access point multi-link device or DS;

[0487] The exchange or indication of MLD level information is performed via the MAC sublayer of the attached access point multi-link device.

[0488] In some embodiments, the first access point multi-link device and the second access point multi-link device belong to the same mobility domain MD in the same extended service set, and the third access point multi-link device is an MD AP MLD.

[0489] In some embodiments, the first frame includes first information, and the first information includes at least one of the following:

[0490] first indication information, where the first indication information is used to indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD;

[0491] Second indication information, where the second indication information is used to indicate the third access point multi-link device.

[0492] In some embodiments, the first frame includes at least one of the following:

[0493] a first switching frame, wherein the first switching frame is used to start the non-access point multi-link device from switching from the first access point multi-link device to the second access point multi-link device;

[0494] a second switching frame, where the first access point multi-link device is used to synchronize second data to the second access point multi-link device, where the second data is used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device, so as to maintain sustainability of data communication after the non-access point multi-link device switches to the second access point multi-link device;

[0495] A third conversion frame is used for the non-access point multi-link device to associate or re-associate with the second access point multi-link device.

[0496] In some embodiments, the first conversion frame includes at least one of the following:

[0497] a switch request frame sent by the non-access point multi-link device to the second access point multi-link device, the switch request frame being used to request a switch from the first access point multi-link device to the second access point multi-link device;

[0498] A switch response frame sent by the second access point multi-link device to the non-access point multi-link device, where the switch response frame is used to respond to the switch request frame.

[0499] In some embodiments, the second conversion frame includes at least one of the following:

[0500] a first switch confirmation frame sent by the non-access point multi-link device to the first access point multi-link device, wherein the first switch confirmation frame is used to request the first access point multi-link device to synchronize the second data to the second access point multi-link device;

[0501] A first conversion response frame sent by the first access point multi-link device to the non-access point multi-link device, where the first conversion response frame is used to feed back a synchronization status of the second data.

[0502] In some embodiments, the first conversion confirmation frame carries third data of the non-access point multi-link device, the third data is used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device, and the third data is also used by the first access point multi-link device to determine the second data.

[0503] In some embodiments, the third conversion frame includes at least one of the following:

[0504] an association request frame or a reassociation request frame sent by the non-access point multi-link device to the second access point multi-link device;

[0505] An association response frame or a reassociation response frame sent by the second access point multi-link device to the non-access point multi-link device.

[0506] In some embodiments, the second data includes at least one of the following:

[0507] second information, where the second information is block acknowledgment protocol scenario information of the first access point multi-link device;

[0508] The third information is security association scenario information of the first access point multi-link device.

[0509] In some embodiments, the second conversion frame includes: a block acknowledgement protocol scenario element, wherein the block acknowledgement protocol scenario element is used to indicate information about a block acknowledgement protocol scenario.

[0510] In some embodiments, the block acknowledgement protocol scenario element includes a block acknowledgement protocol scenario parameter control field, wherein the block acknowledgement protocol scenario parameter control field is used to indicate at least one of:

[0511] The device where the block confirmation protocol scenario described by the block confirmation protocol scenario element is located;

[0512] Whether the peer device targeted by the block acknowledgment protocol scenario of the device described by the block acknowledgment protocol scenario element is the same device;

[0513] When the opposite device targeted by the block confirmation protocol scenario of the device described by the block confirmation protocol scenario element is the same device, the opposite device targeted by the block confirmation protocol scenario;

[0514] The block confirmation protocol scenario element includes the number of block confirmation protocol scenario parameter sets.

[0515] In some embodiments, the block confirmation protocol scenario element includes a block confirmation protocol scenario parameter set list field, the block confirmation protocol scenario parameter set list field includes at least one block confirmation protocol scenario parameter set subfield, and one block confirmation protocol scenario parameter set subfield is used to indicate a block confirmation protocol scenario parameter set.

[0516] In some embodiments, the block acknowledgement protocol scenario parameter set subfield is used to indicate at least one of the following:

[0517] The role of the device in the corresponding block confirmation protocol scenario;

[0518] The corresponding block confirmation protocol scenario targets the peer device;

[0519] Block confirmation parameter set;

[0520] Block confirmation timeout value.

[0521] In some embodiments, if the block acknowledgment protocol scenario parameter set subfield is used to indicate that the role of the device in the corresponding block acknowledgment protocol scenario is an initiator in the block acknowledgment protocol scenario, the block acknowledgment protocol scenario parameter set subfield is further used to indicate at least one of the following:

[0522] Send window starting sequence number;

[0523] Send window size.

[0524] In some embodiments, if the block acknowledgment protocol scenario parameter set subfield is used to indicate that the role of the device in the corresponding block acknowledgment protocol scenario is a receiver in the block acknowledgment protocol scenario, the block acknowledgment protocol scenario parameter set subfield is further used to indicate at least one of the following:

[0525] Receive buffer starting sequence number;

[0526] Receive window size;

[0527] Record the starting sequence number of the bitmap;

[0528] Record the maximum sequence number of the bitmap;

[0529] Record the bitmap size.

[0530] In some embodiments, the block confirmation parameter set includes at least one of the following:

[0531] Third indication information indicating whether aggregated MAC service data units are supported;

[0532] Block confirmation strategy;

[0533] Flow ID;

[0534] Buffer size.

[0535] In some embodiments, the second conversion frame includes: a security association scenario element, where the security association scenario element is used to indicate information about a security association scenario.

[0536] In some embodiments, the security association scenario element includes a security association scenario parameter control field, and the security association scenario parameter control field is used to indicate at least one of the following:

[0537] The device where the security association scenario described by the security association scenario element is located;

[0538] Whether the peer device targeted by the security association scenario of the device described by the security association scenario element is the same device;

[0539] When the opposite device targeted by the security association scenario of the device described by the security association scenario element is the same device, the opposite device targeted by the security association scenario;

[0540] The number of security association scenario parameter sets included in the security association scenario element.

[0541] In some embodiments, the security association scenario element includes a security association scenario parameter set list field, the security association scenario parameter set list field includes at least one security association scenario parameter set subfield, and one of the security association scenario parameter set subfields is used to indicate a security association scenario parameter set.

[0542] In some embodiments, the security association scenario parameter set subfield is used to indicate at least one of the following:

[0543] The role of the device in the corresponding security association scenario;

[0544] The peer device targeted by the corresponding security association scenario;

[0545] The security association type of the corresponding security association scenario.

[0546] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the role of the device in the corresponding security association scenario is a receiving end in the security association scenario; the security association scenario parameter set subfield is further used to indicate at least one of the following:

[0547] Replay counter number;

[0548] TID;

[0549] The count of the replay counter for the TID.

[0550] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the role of the device in the corresponding security association scenario is a sender in the security association scenario; the security association scenario parameter set subfield is further used to indicate at least one of the following:

[0551] Packet number counter quantity;

[0552] TID;

[0553] The count of the packet number counter for the TID.

[0554] In some embodiments, the second conversion frame further includes at least one of the following:

[0555] Fourth indication information, where the fourth indication information is used to indicate that the second data includes information of a block confirmation protocol scenario and / or a security association scenario.

[0556] In some embodiments, the first communication unit 2601 is further configured to:

[0557] A second frame is received or sent, where the second frame is used for the non-access point multi-link device to associate or re-associate with the first access point multi-link device.

[0558] In some embodiments, the second frame includes first information, and the first information includes at least one of the following:

[0559] first indication information, where the first indication information is used to indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD;

[0560] Second indication information, where the second indication information is used to indicate the third access point multi-link device.

[0561] In some embodiments, the first information is located in a mobile domain element MDE.

[0562] In some embodiments, the first indication information is located in the conversion capability and policy field of the MDE.

[0563] In some embodiments, the second indication information includes at least one of the following:

[0564] The device identifier of the third access point multi-link device;

[0565] The MAC address of the third access point multi-link device.

[0566] FIG27 is a schematic diagram of the structure of an access point multi-link device provided in an embodiment of the present application. As shown in FIG27 , the access point multi-link device 2700 includes:

[0567] The second communication unit 2701 is configured to send or receive a first frame, where the first frame is used by the non-access point multi-link device to switch between a first access point multi-link device and a second access point multi-link device, where the first access point multi-link device and the second access point multi-link device are attached to a third access point multi-link device, where the third access point multi-link device is a logical access point multi-link device, and the access point multi-link device is the first access point multi-link device or the second access point multi-link device.

[0568] It is understandable that the access point multi-link device further includes a processing unit and a storage unit. The processing unit is configured to parse the first frame or generate the first frame, and the storage unit is configured to store information carried by the first frame.

[0569] In some embodiments, the first access point multi-link device is an access point multi-link device whose affiliated access point AP is located at the same location; the second access point multi-link device is an access point multi-link device whose affiliated AP is located at the same location.

[0570] In some embodiments, the third access point multi-link device is used for at least one of the following:

[0571] Providing a connection service between the non-access point multi-link device or the auxiliary access point multi-link device and the distributed system DS;

[0572] maintaining data continuity of the non-access point multi-link device during roaming when switching between the first access point multi-link device and the second access point multi-link device;

[0573] authentication and / or association or reassociation of the non-access point multi-link device;

[0574] security association of said non-access point multi-link device;

[0575] distribution of all or part of the security association information of the non-access point multi-link device;

[0576] Synchronize all or part of the status and / or buffer information of the upper layer of the MAC layer of the attached access point multi-link device;

[0577] Managing the distribution of authentication information for links of non-access point multi-link devices;

[0578] Managing an association or re-association at an accessory access point multi-link device level between the non-access point multi-link device and the accessory access point multi-link device;

[0579] For a target access point multi-link device that has established a multi-link with the non-access point multi-link device among at least one attached access point multi-link device, selecting a MAC corresponding to the target access point multi-link device for transmission;

[0580] synchronization of first data between attached different access point multi-link devices, the first data being used to maintain data continuity in communications between the non-access point multi-link device and the attached access point multi-link device or DS;

[0581] The exchange or indication of MLD level information is performed via the MAC sublayer of the attached access point multi-link device.

[0582] In some embodiments, the first access point multi-link device and the second access point multi-link device belong to the same mobility domain MD in the same extended service set, and the third access point multi-link device is an MD AP MLD.

[0583] In some embodiments, the first frame includes first information, and the first information includes at least one of the following:

[0584] first indication information, where the first indication information is used to indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD;

[0585] Second indication information, where the second indication information is used to indicate the third access point multi-link device.

[0586] In some embodiments, the first frame includes at least one of the following:

[0587] a first switching frame, wherein the first switching frame is used to start the non-access point multi-link device from switching from the first access point multi-link device to the second access point multi-link device;

[0588] a second switching frame, where the first access point multi-link device is used to synchronize second data to the second access point multi-link device, where the second data is used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device, so as to maintain sustainability of data communication after the non-access point multi-link device switches to the second access point multi-link device;

[0589] A third conversion frame is used for the non-access point multi-link device to associate or re-associate with the second access point multi-link device.

[0590] In some embodiments, the first conversion frame includes at least one of the following:

[0591] a switch request frame sent by the non-access point multi-link device to the second access point multi-link device, the switch request frame being used to request a switch from the first access point multi-link device to the second access point multi-link device;

[0592] A switch response frame sent by the second access point multi-link device to the non-access point multi-link device, where the switch response frame is used to respond to the switch request frame.

[0593] In some embodiments, the second conversion frame includes at least one of the following:

[0594] a first switch confirmation frame sent by the non-access point multi-link device to the first access point multi-link device, wherein the first switch confirmation frame is used to request the first access point multi-link device to synchronize the second data of the first access point multi-link device to the second access point multi-link device;

[0595] a second switch confirmation frame sent by the first access point multi-link device to the second access point multi-link device, where the second switch confirmation frame is used by the first access point multi-link device to synchronize the second data to the second access point multi-link device;

[0596] a first conversion response frame sent by the first access point multi-link device to the non-access point multi-link device, wherein the first conversion response frame is used to feedback a synchronization status of the second data to the non-access point multi-link device;

[0597] A second switch response frame sent by the second access point multi-link device to the first access point multi-link device, where the second switch response frame is used to feed back a synchronization status of the second data to the first access point multi-link device.

[0598] In some embodiments, the first conversion confirmation frame carries third data of the non-access point multi-link device, the third data is used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device, and the third data is also used by the first access point multi-link device to determine the second data.

[0599] In some embodiments, the third conversion frame includes at least one of the following:

[0600] an association request frame or a reassociation request frame sent by the non-access point multi-link device to the second access point multi-link device;

[0601] An association response frame or a reassociation response frame sent by the second access point multi-link device to the non-access point multi-link device.

[0602] In some embodiments, the second data includes at least one of the following:

[0603] second information, where the second information is block acknowledgment protocol scenario information of the first access point multi-link device;

[0604] The third information is security association scenario information of the first access point multi-link device.

[0605] In some embodiments, the second conversion frame includes: a block acknowledgement protocol scenario element, wherein the block acknowledgement protocol scenario element is used to indicate information about a block acknowledgement protocol scenario.

[0606] In some embodiments, the block acknowledgement protocol scenario element includes a block acknowledgement protocol scenario parameter control field, wherein the block acknowledgement protocol scenario parameter control field is used to indicate at least one of:

[0607] The device where the block confirmation protocol scenario described by the block confirmation protocol scenario element is located;

[0608] Whether the peer device targeted by the block acknowledgment protocol scenario of the device described by the block acknowledgment protocol scenario element is the same device;

[0609] When the opposite device targeted by the block confirmation protocol scenario of the device described by the block confirmation protocol scenario element is the same device, the opposite device targeted by the block confirmation protocol scenario;

[0610] The block confirmation protocol scenario element includes the number of block confirmation protocol scenario parameter sets.

[0611] In some embodiments, the block confirmation protocol scenario element includes a block confirmation protocol scenario parameter set list field, the block confirmation protocol scenario parameter set list field includes at least one block confirmation protocol scenario parameter set subfield, and one block confirmation protocol scenario parameter set subfield is used to indicate a block confirmation protocol scenario parameter set.

[0612] In some embodiments, the block acknowledgement protocol scenario parameter set subfield is used to indicate at least one of the following:

[0613] The role of the device in the corresponding block confirmation protocol scenario;

[0614] The corresponding block confirmation protocol scenario targets the peer device;

[0615] Block confirmation parameter set;

[0616] Block confirmation timeout value.

[0617] In some embodiments, if the block acknowledgment protocol scenario parameter set subfield is used to indicate that the role of the device in the corresponding block acknowledgment protocol scenario is an initiator in the block acknowledgment protocol scenario, the block acknowledgment protocol scenario parameter set subfield is further used to indicate at least one of the following:

[0618] Send window starting sequence number;

[0619] Send window size.

[0620] In some embodiments, if the block acknowledgment protocol scenario parameter set subfield is used to indicate that the role of the device in the corresponding block acknowledgment protocol scenario is a receiver in the block acknowledgment protocol scenario, the block acknowledgment protocol scenario parameter set subfield is further used to indicate at least one of the following:

[0621] Receive buffer starting sequence number;

[0622] Receive window size;

[0623] Record the starting sequence number of the bitmap;

[0624] Record the maximum sequence number of the bitmap;

[0625] Record the bitmap size.

[0626] In some embodiments, the block confirmation parameter set includes at least one of the following:

[0627] Third indication information indicating whether aggregated MAC service data units are supported;

[0628] Block confirmation strategy;

[0629] Flow ID;

[0630] Buffer size.

[0631] In some embodiments, the second conversion frame includes: a security association scenario element, where the security association scenario element is used to indicate information about a security association scenario.

[0632] In some embodiments, the security association scenario element includes a security association scenario parameter control field, and the security association scenario parameter control field is used to indicate at least one of the following:

[0633] The device where the security association scenario described by the security association scenario element is located;

[0634] Whether the peer device targeted by the security association scenario of the device described by the security association scenario element is the same device;

[0635] When the opposite device targeted by the security association scenario of the device described by the security association scenario element is the same device, the opposite device targeted by the security association scenario;

[0636] The number of security association scenario parameter sets included in the security association scenario element.

[0637] In some embodiments, the security association scenario element includes a security association scenario parameter set list field, the security association scenario parameter set list field includes at least one security association scenario parameter set subfield, and one of the security association scenario parameter set subfields is used to indicate a security association scenario parameter set.

[0638] In some embodiments, the security association scenario parameter set subfield is used to indicate at least one of the following:

[0639] The role of the device in the corresponding security association scenario;

[0640] The peer device targeted by the corresponding security association scenario;

[0641] The security association type of the corresponding security association scenario.

[0642] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the role of the device in the corresponding security association scenario is a receiving end in the security association scenario; the security association scenario parameter set subfield is further used to indicate at least one of the following:

[0643] Replay counter number;

[0644] TID;

[0645] The count of the replay counter for the TID.

[0646] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the role of the device in the corresponding security association scenario is a sender in the security association scenario; the security association scenario parameter set subfield is further used to indicate at least one of the following:

[0647] Packet number counter quantity;

[0648] TID;

[0649] The count of the packet number counter for the TID.

[0650] In some embodiments, the second conversion frame further includes at least one of the following:

[0651] Fourth indication information, where the fourth indication information is used to indicate that the second data includes information of a block confirmation protocol scenario and / or a security association scenario.

[0652] In some embodiments, if the access point multi-link device is the first access point multi-link device, the second communication unit 2701 is further configured to:

[0653] A second frame is sent or received, where the second frame is used for the non-access point multi-link device to associate or re-associate with the first access point multi-link device.

[0654] In some embodiments, the second frame includes first information, and the first information includes at least one of the following:

[0655] first indication information, where the first indication information is used to indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD;

[0656] Second indication information, where the second indication information is used to indicate the third access point multi-link device.

[0657] In some embodiments, the first information is located in a mobile domain element MDE.

[0658] In some embodiments, the first indication information is located in the conversion capability and policy field of the MDE.

[0659] In some embodiments, the second indication information includes at least one of the following:

[0660] The device identifier of the third access point multi-link device;

[0661] The MAC address of the third access point multi-link device.

[0662] Those skilled in the art should understand that the description related to the non-access point multi-link device or access point multi-link device in the embodiments of the present application can be understood with reference to the description related to the wireless communication method in the embodiments of the present application.

[0663] Figure 28 is a schematic diagram of a communication device 2800 provided in an embodiment of the present application. The communication device can be either a non-access point multi-link device or an access point multi-link device. The communication device 2800 shown in Figure 28 includes a processor 2810, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0664] Optionally, as shown in FIG28 , the communication device 2800 may further include a memory 2820. The processor 2810 may call and execute a computer program from the memory 2820 to implement the method in the embodiment of the present application.

[0665] The memory 2820 may be a separate device independent of the processor 2810 , or may be integrated into the processor 2810 .

[0666] Optionally, as shown in FIG28 , the communication device 2800 may further include a transceiver 2830 , and the processor 2810 may control the transceiver 2830 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

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

[0668] Optionally, the communication device 2800 may be a non-access point multi-link device in an embodiment of the present application, and the communication device 2800 may implement corresponding processes implemented by a non-access point multi-link device in various methods in the embodiments of the present application. For the sake of brevity, details are not repeated here.

[0669] Optionally, the communication device 2800 may be specifically an access point multi-link device in an embodiment of the present application, and the communication device 2800 may implement the corresponding processes implemented by the access point multi-link device in each method in the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0670] Figure 29 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 2900 shown in Figure 29 includes a processor 2910, which can call and run a computer program from a memory to implement the method according to the embodiment of the present application.

[0671] Optionally, as shown in FIG29 , the chip 2900 may further include a memory 2920 , wherein the processor 2910 may call and execute a computer program from the memory 2920 to implement the method in the embodiment of the present application.

[0672] The memory 2920 may be a separate device independent of the processor 2910 or may be integrated into the processor 2910 .

[0673] Optionally, the chip 2900 may further include an input interface 2930. The processor 2910 may control the input interface 2930 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0674] Optionally, the chip 2900 may further include an output interface 2940. The processor 2910 may control the output interface 2940 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0675] Optionally, the chip may be applied to a non-access point multi-link device in the embodiments of the present application, and the chip may implement corresponding processes implemented by the non-access point multi-link device in various methods of the embodiments of the present application, which will not be described in detail here for the sake of brevity.

[0676] Optionally, the chip may be applied to the access point multi-link device in the embodiments of the present application, and the chip may implement the corresponding processes implemented by the access point multi-link device in the various methods of the embodiments of the present application, which will not be described in detail here for the sake of brevity.

[0677] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0678] Figure 30 is a schematic block diagram of a communication system 3000 provided in accordance with an embodiment of the present application. As shown in Figure 30 , the communication system 3000 includes a non-AP multi-link device 3010 and an AP multi-link device 3020. The non-AP multi-link device 3010 can be a station (a non-AP MLD or a non-AP STA) that accesses the AP multi-link device 3020.

[0679] The access point multi-link device 3020 can be used to implement the corresponding functions implemented by the access point multi-link device in the above method, which will not be described in detail here for the sake of brevity. The non-access point multi-link device 3010 can be used to implement the corresponding functions implemented by the non-access point multi-link device in the above method, which will not be described in detail here for the sake of brevity.

[0680] It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiment can be completed by hardware integrated logic circuits in the processor or software instructions. The above 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 embodied as being executed by a hardware decoding processor, or can be executed 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 completes the steps of the above method in combination with its hardware.

[0681] 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.

[0682] 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.

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

[0684] Optionally, the computer-readable storage medium may be applied to the non-access point multi-link device in the embodiments of the present application, and the execution of the computer program enables the computer to execute the corresponding processes implemented by the non-access point multi-link device in the various methods of the embodiments of the present application. For the sake of brevity, they are not further described here.

[0685] Optionally, the computer-readable storage medium may be applied to the access point multi-link device in the embodiments of the present application, and the execution of the computer program enables the computer to execute the corresponding processes implemented by the access point multi-link device in the various methods of the embodiments of the present application. For the sake of brevity, they are not further described here.

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

[0687] Optionally, the computer program product may be applied to the non-access point multi-link device in the embodiments of the present application, and the execution of the computer program instructions causes the computer to execute the corresponding processes implemented by the non-access point multi-link device in the various methods of the embodiments of the present application. For the sake of brevity, they are not further described here.

[0688] Optionally, the computer program product may be applied to the access point multi-link device in the embodiments of the present application, and the execution of the computer program instructions enables the computer to execute the corresponding processes implemented by the access point multi-link device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here in detail.

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

[0690] Optionally, the computer program may be applied to the non-access point multi-link device in the embodiments of the present application. When the computer program is executed on a computer, the computer executes the corresponding processes implemented by the non-access point multi-link device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here in detail.

[0691] Optionally, the computer program may be applied to the access point multi-link device in the embodiments of the present application. When the computer program is executed on a computer, the computer executes the corresponding processes implemented by the access point multi-link device in the various methods of the embodiments of the present application. For the sake of brevity, they are not described here in detail.

[0692] 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.

[0693] 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.

[0694] 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.

[0695] 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.

[0696] 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.

[0697] 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. Based on 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 several 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.

[0698] 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, the method comprising: A non-access point multi-link device receives or sends a first frame, wherein the first frame is used by the non-access point multi-link device to switch between a first access point multi-link device and a second access point multi-link device, wherein the first access point multi-link device and the second access point multi-link device are attached to the same third access point multi-link device or different third access point multi-link devices, and the third access point multi-link device is a logical access point multi-link device.

2. The method according to claim 1, wherein: The first access point multi-link device is an access point multi-link device whose affiliated access point AP is located at the same place; the second access point multi-link device is an access point multi-link device whose affiliated AP is located at the same place.

3. The method according to claim 1 or 2, wherein: The third access point multi-link device is used for at least one of the following: Providing a connection service between the non-access point multi-link device or the attached access point multi-link device and the distributed system DS; maintaining data continuity of the non-access point multi-link device switching between the first access point multi-link device and the second access point multi-link device during roaming; authentication and / or association or re-association of the non-access point multi-link device; security association of said non-access point multi-link device; distribution of all or part of the security association information of the non-access point multi-link device; Synchronize all or part of the status and / or buffer information of the upper layer of the upper layer MAC of the attached access point multi-link device; Managing the distribution of authentication information for links of non-access point multi-link devices; managing an association or re-association at a subordinate access point multi-link device level between the non-access point multi-link device and the subordinate access point multi-link device; For a target access point multi-link device that establishes a multi-link with the non-access point multi-link device among at least one attached access point multi-link device, selecting a MAC corresponding to the target access point multi-link device for transmission; synchronization of first data between attached different access point multi-link devices, the first data being used to maintain data continuity in communication between the non-access point multi-link device and the attached access point multi-link device or DS; The exchange or indication of MLD level information is performed by the MAC sublayer of the attached access point multi-link device.

4. The method according to any one of claims 1 to 3, wherein: The first access point multi-link device and the second access point multi-link device belong to the same mobility domain MD in the same extended service set, and the third access point multi-link device is an MD AP MLD.

5. The method according to any one of claims 1 to 4, wherein: The first frame includes first information, and the first information includes at least one of the following: first indication information, where the first indication information is used to indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD; Second indication information, where the second indication information is used to indicate the third access point multi-link device.

6. The method according to any one of claims 1 to 5, wherein: The first frame includes at least one of the following: a first conversion frame, wherein the first conversion frame is used to start the non-access point multi-link device to convert from the first access point multi-link device to the second access point multi-link device; a second switching frame, wherein the second switching frame is used for the first access point multi-link device to synchronize second data to the second access point multi-link device, and the second data is used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device, so as to maintain the sustainability of data communication after the non-access point multi-link device switches to the second access point multi-link device; A third conversion frame, wherein the third conversion frame is used for the non-access point multi-link device to associate or re-associate with the second access point multi-link device.

7. The method according to claim 6, wherein: The first conversion frame includes at least one of the following: a switch request frame sent by the non-access point multi-link device to the second access point multi-link device, the switch request frame being used to request a switch from the first access point multi-link device to the second access point multi-link device; A switch response frame sent by the second access point multi-link device to the non-access point multi-link device, wherein the switch response frame is used to respond to the switch request frame.

8. The method according to claim 6, wherein: The second conversion frame includes at least one of the following: a first conversion confirmation frame sent by the non-access point multi-link device to the first access point multi-link device, the first conversion confirmation frame being used to request the first access point multi-link device to synchronize the second data to the second access point multi-link device; A first conversion response frame sent by the first access point multi-link device to the non-access point multi-link device, wherein the first conversion response frame is used to feed back synchronization status and / or synchronization information of the second data.

9. The method according to claim 8, wherein: The first conversion confirmation frame carries third data of the non-access point multi-link device, the third data is used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device, and the third data is also used by the first access point multi-link device to determine the second data.

10. The method according to claim 6, wherein: The third conversion frame includes at least one of the following: an association request frame or a reassociation request frame sent by the non-access point multi-link device to the second access point multi-link device; An association response frame or a re-association response frame sent by the second access point multi-link device to the non-access point multi-link device.

11. The method according to claim 6 or 8, wherein: The second data includes at least one of the following: second information, where the second information is block confirmation protocol scenario information of the first access point multi-link device; The third information is security association scenario information of the first access point multi-link device.

12. The method according to claim 11, wherein: The second conversion frame includes: a block confirmation protocol scenario element, and the block confirmation protocol scenario element is used to indicate information of a block confirmation protocol scenario.

13. The method according to claim 12, wherein: The block confirmation protocol scenario element includes a block confirmation protocol scenario parameter control field, and the block confirmation protocol scenario parameter control field is used to indicate at least one of: The device where the block confirmation protocol scenario described by the block confirmation protocol scenario element is located; Whether the peer device targeted by the block confirmation protocol scenario of the device described by the block confirmation protocol scenario element is the same device; When the opposite device targeted by the block confirmation protocol scenario of the device described by the block confirmation protocol scenario element is the same device, the opposite device targeted by the block confirmation protocol scenario; The block confirmation protocol scenario element includes the number of block confirmation protocol scenario parameter sets.

14. The method according to claim 12 or 13, wherein: The block confirmation protocol scenario element includes a block confirmation protocol scenario parameter set list field, the block confirmation protocol scenario parameter set list field includes at least one block confirmation protocol scenario parameter set subfield, and one block confirmation protocol scenario parameter set subfield is used to indicate a block confirmation protocol scenario parameter set.

15. The method according to claim 14, wherein: The block confirmation protocol scenario parameter set subfield is used to indicate at least one of the following: The role of the device in the corresponding block confirmation protocol scenario in the block confirmation protocol scenario; The corresponding block confirmation protocol scenario targets the peer device; Block confirmation parameter set; Block confirmation timeout value.

16. The method according to claim 15, wherein: If the block confirmation protocol scenario parameter set subfield is used to indicate that the role of the device in the corresponding block confirmation protocol scenario is the initiator in the block confirmation protocol scenario; the block confirmation protocol scenario parameter set subfield is also used to indicate at least one of the following: Send window starting sequence number; Send window size.

17. The method according to claim 15, wherein: If the block confirmation protocol scenario parameter set subfield is used to indicate that the role of the device in the corresponding block confirmation protocol scenario is a receiver in the block confirmation protocol scenario; the block confirmation protocol scenario parameter set subfield is also used to indicate at least one of the following: Receive buffer starting sequence number; Receive window size; Record the starting sequence number of the bitmap; Record the maximum sequence number of the bitmap; Record the bitmap size.

18. The method according to any one of claims 15 to 17, wherein: The block confirmation parameter set includes at least one of the following: third indication information indicating whether aggregated MAC service data units are supported; Block confirmation strategy; Stream ID; Buffer size.

19. The method according to any one of claims 11 to 18, wherein: The second conversion frame includes: a security association scenario element, and the security association scenario element is used to indicate information of a security association scenario.

20. The method according to claim 19, wherein: The security association scenario element includes a security association scenario parameter control field, and the security association scenario parameter control field is used to indicate at least one of the following: The device where the security association scenario described by the security association scenario element is located; Whether the opposite device targeted by the security association scenario of the device described by the security association scenario element is the same device; When the opposite end device targeted by the security association scenario of the device described by the security association scenario element is the same device, the opposite end device targeted by the security association scenario; The number of security association scenario parameter sets included in the security association scenario element.

21. The method according to claim 19 or 20, wherein: The security association scenario element includes a security association scenario parameter set list field, the security association scenario parameter set list field includes at least one security association scenario parameter set subfield, and one of the security association scenario parameter set subfields is used to indicate a security association scenario parameter set.

22. The method according to claim 21, wherein: The security association scenario parameter set subfield is used to indicate at least one of the following: The role of the device in the corresponding security association scenario; The peer device targeted by the corresponding security association scenario; The security association type of the corresponding security association scenario.

23. The method according to claim 22, wherein: If the security association scenario parameter set subfield is used to indicate that the role of the device in the corresponding security association scenario is a receiving end in the security association scenario; the security association scenario parameter set subfield is also used to indicate at least one of the following: Replay counter number; TID; The count of the replay counter for the TID.

24. The method according to claim 22, wherein: If the security association scenario parameter set subfield is used to indicate that the role of the device in the corresponding security association scenario is a sender in the security association scenario; the security association scenario parameter set subfield is also used to indicate at least one of the following: Packet number counter quantity; TID; The count of the packet number counter for the TID.

25. The method according to any one of claims 6, 8, 9, 11 to 24, wherein: The second conversion frame further includes at least one of the following: Fourth indication information, where the fourth indication information is used to indicate that the second data includes information of a block confirmation protocol scenario and / or a security association scenario.

26. The method according to any one of claims 1 to 25, wherein: The method further comprises: The non-access point multi-link device receives or sends a second frame, where the second frame is used for the non-access point multi-link device to associate or re-associate with the first access point multi-link device.

27. The method according to claim 26, wherein: The second frame includes first information, and the first information includes at least one of the following: first indication information, where the first indication information is used to indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD; Second indication information, where the second indication information is used to indicate the third access point multi-link device.

28. The method according to claim 5 or 27, wherein: The first information is located in the mobile domain element MDE.

29. The method according to claim 28, wherein: The first indication information is located in the conversion capability and policy domain of the MDE.

30. The method according to any one of claims 5, 27 to 29, wherein: The second indication information includes at least one of the following: The device identifier of the third access point multi-link device; The MAC address of the third access point multi-link device.

31. A wireless communication method, the method comprising: An access point multi-link device sends or receives a first frame, wherein the first frame is used for the access point multi-link device to switch between a first access point multi-link device and a second access point multi-link device, wherein the first access point multi-link device and the second access point multi-link device are attached to the same third access point multi-link device or different third access point multi-link devices, and the third access point multi-link device is a logical access point multi-link device; and the access point multi-link device is the first access point multi-link device or the second access point multi-link device.

32. The method according to claim 31, wherein: The first access point multi-link device is an access point multi-link device whose affiliated access point AP is located at the same place; the second access point multi-link device is an access point multi-link device whose affiliated AP is located at the same place.

33. The method according to claim 31 or 32, wherein: The third access point multi-link device is used for at least one of the following: Providing a connection service between the non-access point multi-link device or the attached access point multi-link device and the distributed system DS; maintaining data continuity of the non-access point multi-link device switching between the first access point multi-link device and the second access point multi-link device during roaming; authentication and / or association or re-association of the non-access point multi-link device; security association of said non-access point multi-link device; distribution of all or part of the security association information of the non-access point multi-link device; Synchronize all or part of the status and / or buffer information of the upper layer of the upper layer MAC of the attached access point multi-link device; Managing the distribution of authentication information for links of non-access point multi-link devices; managing an association or re-association at a subordinate access point multi-link device level between the non-access point multi-link device and the subordinate access point multi-link device; For a target access point multi-link device that establishes a multi-link with the non-access point multi-link device among at least one attached access point multi-link device, selecting a MAC corresponding to the target access point multi-link device for transmission; synchronization of first data between attached different access point multi-link devices, the first data being used to maintain data continuity in communication between the non-access point multi-link device and the attached access point multi-link device or DS; The exchange or indication of MLD level information is performed by the MAC sublayer of the attached access point multi-link device.

34. The method according to any one of claims 31 to 33, wherein: The first access point multi-link device and the second access point multi-link device belong to the same mobility domain MD in the same extended service set, and the third access point multi-link device is an MD AP MLD.

35. The method according to any one of claims 31 to 34, wherein: The first frame includes first information, and the first information includes at least one of the following: first indication information, where the first indication information is used to indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD; Second indication information, where the second indication information is used to indicate the third access point multi-link device.

36. The method according to any one of claims 31 to 35, wherein: The first frame includes at least one of the following: a first conversion frame, wherein the first conversion frame is used to start the non-access point multi-link device to convert from the first access point multi-link device to the second access point multi-link device; a second switching frame, wherein the second switching frame is used for the first access point multi-link device to synchronize second data to the second access point multi-link device, and the second data is used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device, so as to maintain the sustainability of data communication after the non-access point multi-link device switches to the second access point multi-link device; A third conversion frame, wherein the third conversion frame is used for the non-access point multi-link device to associate or re-associate with the second access point multi-link device.

37. The method of claim 36, wherein: The first conversion frame includes at least one of the following: a switch request frame sent by the non-access point multi-link device to the second access point multi-link device, the switch request frame being used to request a switch from the first access point multi-link device to the second access point multi-link device; A switch response frame sent by the second access point multi-link device to the non-access point multi-link device, wherein the switch response frame is used to respond to the switch request frame.

38. The method of claim 36, wherein: The second conversion frame includes at least one of the following: a first conversion confirmation frame sent by the non-access point multi-link device to the first access point multi-link device, the first conversion confirmation frame being used to request the first access point multi-link device to synchronize the second data of the first access point multi-link device to the second access point multi-link device; a second conversion confirmation frame sent by the first access point multi-link device to the second access point multi-link device, where the second conversion confirmation frame is used by the first access point multi-link device to synchronize the second data to the second access point multi-link device; a first conversion response frame sent by the first access point multi-link device to the non-access point multi-link device, wherein the first conversion response frame is used to feed back a synchronization state of the second data to the non-access point multi-link device; A second switch response frame sent by the second access point multi-link device to the first access point multi-link device, wherein the second switch response frame is used to feed back a synchronization status of the second data to the first access point multi-link device.

39. The method of claim 38, wherein: The first conversion confirmation frame carries third data of the non-access point multi-link device, the third data is used to maintain data communication between the non-access point multi-link device and the first access point multi-link device or the third access point multi-link device, and the third data is also used by the first access point multi-link device to determine the second data.

40. The method of claim 36, wherein: The third conversion frame includes at least one of the following: an association request frame or a reassociation request frame sent by the non-access point multi-link device to the second access point multi-link device; An association response frame or a re-association response frame sent by the second access point multi-link device to the non-access point multi-link device.

41. The method of claim 36 or 38, wherein: The second data includes at least one of the following: second information, where the second information is information about a block confirmation protocol scenario of the first access point multi-link device; The third information is information about a security association scenario of the first access point multi-link device.

42. The method according to claim 41, wherein: The second conversion frame includes: a block confirmation protocol scenario element, and the block confirmation protocol scenario element is used to indicate information of a block confirmation protocol scenario.

43. The method of claim 42, wherein: The block confirmation protocol scenario element includes a block confirmation protocol scenario parameter control field, and the block confirmation protocol scenario parameter control field is used to indicate at least one of: The device where the block confirmation protocol scenario described by the block confirmation protocol scenario element is located; Whether the peer device targeted by the block confirmation protocol scenario of the device described by the block confirmation protocol scenario element is the same device; When the opposite device targeted by the block confirmation protocol scenario of the device described by the block confirmation protocol scenario element is the same device, the opposite device targeted by the block confirmation protocol scenario; The block confirmation protocol scenario element includes the number of block confirmation protocol scenario parameter sets.

44. The method according to claim 42 or 43, wherein: The block confirmation protocol scenario element includes a block confirmation protocol scenario parameter set list field, the block confirmation protocol scenario parameter set list field includes at least one block confirmation protocol scenario parameter set subfield, and one block confirmation protocol scenario parameter set subfield is used to indicate a block confirmation protocol scenario parameter set.

45. The method of claim 44, wherein: The block confirmation protocol scenario parameter set subfield is used to indicate at least one of the following: The role of the device in the corresponding block confirmation protocol scenario in the block confirmation protocol scenario; The corresponding block confirmation protocol scenario targets the peer device; Block confirmation parameter set; Block confirmation timeout value.

46. ​​The method of claim 45, wherein: If the block confirmation protocol scenario parameter set subfield is used to indicate that the role of the device in the corresponding block confirmation protocol scenario is the initiator in the block confirmation protocol scenario; the block confirmation protocol scenario parameter set subfield is also used to indicate at least one of the following: Send window starting sequence number; Send window size.

47. The method of claim 45, wherein: If the block confirmation protocol scenario parameter set subfield is used to indicate that the role of the device in the corresponding block confirmation protocol scenario is a receiver in the block confirmation protocol scenario; the block confirmation protocol scenario parameter set subfield is also used to indicate at least one of the following: Receive buffer starting sequence number; Receive window size; Record the starting sequence number of the bitmap; Record the maximum sequence number of the bitmap; Record the bitmap size.

48. A method according to any one of claims 45 to 47, wherein: The block confirmation parameter set includes at least one of the following: third indication information indicating whether aggregated MAC service data units are supported; Block confirmation strategy; Stream ID; Buffer size.

49. The method according to any one of claims 39 to 48, wherein: The second conversion frame includes: a security association scenario element, and the security association scenario element is used to indicate information of a security association scenario.

50. The method of claim 49, wherein: The security association scenario element includes a security association scenario parameter control field, and the security association scenario parameter control field is used to indicate at least one of the following: The device where the security association scenario described by the security association scenario element is located; Whether the opposite device targeted by the security association scenario of the device described by the security association scenario element is the same device; When the opposite end device targeted by the security association scenario of the device described by the security association scenario element is the same device, the opposite end device targeted by the security association scenario; The number of security association scenario parameter sets included in the security association scenario element.

51. The method of claim 49 or 50, wherein: The security association scenario element includes a security association scenario parameter set list field, the security association scenario parameter set list field includes at least one security association scenario parameter set subfield, and one of the security association scenario parameter set subfields is used to indicate a security association scenario parameter set.

52. The method of claim 51, wherein: The security association scenario parameter set subfield is used to indicate at least one of the following: The role of the device in the corresponding security association scenario; The peer device targeted by the corresponding security association scenario; The security association type of the corresponding security association scenario.

53. The method of claim 52, wherein: If the security association scenario parameter set subfield is used to indicate that the role of the device in the corresponding security association scenario is a receiving end in the security association scenario; the security association scenario parameter set subfield is also used to indicate at least one of the following: Replay counter number; TID; The count of the replay counter for the TID.

54. The method of claim 52, wherein: If the security association scenario parameter set subfield is used to indicate that the role of the device in the corresponding security association scenario is a sender in the security association scenario; the security association scenario parameter set subfield is also used to indicate at least one of the following: Packet number counter quantity; TID; The count of the packet number counter for the TID.

55. The method according to any one of claims 36, 38, 39, 41 to 53, wherein: The second conversion frame further includes at least one of the following: Fourth indication information, where the fourth indication information is used to indicate that the second data includes information of a block confirmation protocol scenario and / or a security association scenario.

56. A method according to any one of claims 31 to 55, wherein: If the access point multi-link device is the first access point multi-link device, the method further includes: The access point multi-link device sends or receives a second frame, where the second frame is used for the non-access point multi-link device to associate or re-associate with the first access point multi-link device.

57. The method of claim 56, wherein: The second frame includes first information, and the first information includes at least one of the following: first indication information, where the first indication information is used to indicate whether the non-access point multi-link device supports or is allowed to switch between two subordinate access point multi-link devices of the same MD AP MLD; Second indication information, where the second indication information is used to indicate the third access point multi-link device.

58. The method of claim 35 or 57, wherein: The first information is located in the mobile domain element MDE.

59. The method of claim 58, wherein: The first indication information is located in the conversion capability and policy domain of the MDE.

60. The method according to any one of claims 35, 56 to 58, wherein: The second indication information includes at least one of the following: The device identifier of the third access point multi-link device; The MAC address of the third access point multi-link device.

61. A non-access point multi-link device, comprising: 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 non-access point multi-link device executes the method according to any one of claims 1 to 30.

62. An access point multi-link device, comprising: 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 access point multi-link device executes the method as claimed in any one of claims 31 to 60.

63. A chip, comprising: 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 30, or executes a method as claimed in any one of claims 31 to 60.

64. A computer-readable storage medium for storing a computer program, wherein the execution of the computer program enables a computer to execute the method according to any one of claims 1 to 30, or to execute the method according to any one of claims 31 to 60.

65. A computer program product, comprising computer program instructions, the execution of which causes a computer to perform the method according to any one of claims 1 to 30, or to perform the method according to any one of claims 31 to 60.

66. A computer program, wherein the execution of the computer program causes a computer to execute the method according to any one of claims 1 to 30, or the method according to any one of claims 32 to 60.

Images