A wireless communication method and device, storage medium

Abstract

This application provides a wireless communication method, device, and storage medium. The method includes: a non-access point multi-link device receiving or transmitting a first frame, the first frame being 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.

Description

[0001] Case Analysis This application is a divisional application of Chinese patent application No. 202380097938.7, entitled "A Wireless Communication Method, Device, and Storage Medium", which entered the Chinese national phase of PCT international patent application PCT / CN2023 / 110853, filed on August 2, 2023. Technical Field

[0002] This application relates to the field of mobile communication technology, specifically to a wireless communication method and device, and a storage medium. Background Technology

[0003] The wireless LAN industry is one of the fastest-growing sectors in the entire data communication field. As a supplement and extension to traditional wired LANs, wireless LAN solutions have gained popularity among home network users, small and medium-sized office users, a wide range of enterprise users, and telecommunications operators due to their advantages such as flexibility, mobility, scalability, and lower investment costs, leading to their rapid adoption.

[0004] In multi-link operation, multiple links can be established between Access Point Multi-Link Devices (APMLDs) and Non-AP MLDs on multiple different frequency bands / channels. As a Station (STA) moves, a Basic Service Set (BSS) transition occurs; that is, the STA disconnects from its currently connected 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 critical technical problem that needs to be solved. Summary of the Invention

[0005] This application provides a wireless communication method, device, and storage medium.

[0006] The wireless communication method provided in this application includes: The non-access point multi-link device receives or sends a first frame, which 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. The third access point multi-link device is a logical access point multi-link device.

[0007] The wireless communication method provided in this application includes: The access point multi-link device sends or receives a first frame, which 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 either the first access point multi-link device or the second access point multi-link device.

[0008] The non-access point multi-link device provided in this application embodiment includes: The first communication unit is configured to receive or send a first frame. 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.

[0009] The access point multi-link device provided in this application embodiment includes: The second communication unit is configured to send or receive a first frame, which 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 either the first access point multi-link device or the second access point multi-link device.

[0010] The non-access point multilink device provided in this application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the non-access point multilink device performs the above-described wireless communication method.

[0011] The access point multilink device provided in this application includes a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory, so that the non-access point multilink device performs the above-described wireless communication method.

[0012] The chip provided in this application embodiment is used to implement the above-described wireless communication method.

[0013] Specifically, the chip includes a processor for calling and running a computer program from a memory, causing a device equipped with the chip to perform the aforementioned wireless communication method.

[0014] The computer-readable storage medium provided in this application embodiment is used to store a computer program, the execution of which causes the computer to perform the above-described wireless communication method.

[0015] The computer program product provided in this application includes computer program instructions, the execution of which causes a computer to perform the above-described wireless communication method.

[0016] The computer program provided in this application embodiment, when run on a computer, causes the computer to perform the aforementioned wireless communication method.

[0017] Through the above technical solution, the non-access point multi-link device can switch 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 different third access point multi-link devices. In this architecture, where a third access point multi-link device is set on top of the first access point multi-link device and the second access point multi-link device, the device can switch or switch the communication 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, which is oriented towards data continuity, to switch or switch between the first access point multi-link device and the second non-access point multi-link device. Attached Figure Description

[0018] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1 This is an optional schematic diagram of an application scenario according to an embodiment of this application; Figure 2A This is an optional schematic diagram of an application scenario according to an embodiment of this application; Figure 2B This is an optional schematic diagram of an application scenario according to an embodiment of this application; Figure 3 This is an optional schematic diagram of an application scenario according to an embodiment of this application; Figure 4 This is an optional schematic diagram of the application scenario of the logical AP MLD in this application embodiment; Figure 5 This is an optional flowchart illustrating the wireless communication method according to an embodiment of this application; Figure 6This is an optional flowchart illustrating the wireless communication method according to an embodiment of this application; Figure 7 This is a schematic diagram of an optional location for a third access point multi-link device according to an embodiment of this application; Figure 8 This is a schematic diagram illustrating an application scenario of a non-access point multi-link device switching between different access point multi-link devices attached to a third access point multi-link device, according to an embodiment of this application. Figure 9 This is an optional schematic diagram of the high-level architecture of the mobile domain AP MLD in an embodiment of this application; Figure 10 This is an optional flowchart illustrating the resource request process in an embodiment of this application; Figure 11 This is a schematic diagram of the optional frame structure of the block confirmation protocol scenario elements in an embodiment of this application; Figure 12 This is a schematic diagram of the optional frame structure of the block confirmation protocol scenario parameter control field in an embodiment of this application; Figure 13 This is a schematic diagram of the optional frame structure of the block confirmation protocol scenario parameter set subfield in an embodiment of this application; Figure 14 This is a schematic diagram of the optional frame structure of the block confirmation parameter set subfield in an embodiment of this application; Figure 15 This is a schematic diagram of the optional frame structure of the subfield of the block confirmation protocol scenario parameter set for the initiator in an embodiment of this application; Figure 16 This is a schematic diagram of the optional frame structure of the subfield of the block acknowledgment protocol scenario parameter set for the receiver in an embodiment of this application; Figure 17 This is a schematic diagram of the optional frame structure of security-associated scene elements in an embodiment of this application; Figure 18 This is a schematic diagram of the optional frame structure of the security association scene parameter control domain in an embodiment of this application; Figure 19 This is a schematic diagram of the optional frame structure of the security association scenario parameter set list field in an embodiment of this application; Figure 20 This is a schematic diagram of the optional frame structure of the subdomain of the security association scenario parameter set of the receiving end in an embodiment of this application; Figure 21 This is a schematic diagram of the optional frame structure of the security association scenario parameter set subdomain of the sending end in an embodiment of this application; Figure 22 This is a schematic diagram of the optional frame structure of the conversion capability and policy domain in an embodiment of this application; Figure 23 This is a schematic diagram of the optional frame structure of the MDE in an embodiment of this application; Figure 24 This is an optional schematic diagram of the high-level architecture of the mobile domain AP MLD in an embodiment of this application; Figure 25 This is an optional flowchart illustrating the wireless communication method according to an embodiment of this application; Figure 26 This is a schematic diagram of the optional structure of a non-access point multi-link device according to an embodiment of this application; Figure 27 This is a schematic diagram of the optional structure of the access point multi-link device according to an embodiment of this application; Figure 28 This is a schematic structural diagram of a communication device provided in an embodiment of this application; Figure 29 This is a schematic structural diagram of the chip according to an embodiment of this application; Figure 30 This is a schematic block diagram of a communication system provided in an embodiment of this application. Detailed Implementation

[0019] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0020] The technical solutions of this application embodiment can be applied to various communication systems, such as Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), or other communication systems. WLAN can support frequency bands including but not limited to: low frequency bands (2.4GHz, 5GHz, 6GHz) and high frequency bands (45GHz, 60GHz).

[0021] Figure 1 This is an example of a communication system architecture applied in the embodiments of this application.

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

[0023] The AP 110 serves as a bridge connecting wired and wireless networks, primarily linking various wireless network clients together and then connecting the wireless network to the Ethernet. The AP 110 can be a terminal device with a WiFi chip (such as a mobile phone) or a network device (such as a router).

[0024] It's important to note that the role of the STA 120 in a communication system is not absolute; that is, the STA 120 can switch between the roles of AP and STA. For example, in some scenarios, when a mobile phone is connected to a router, it acts as a STA; when the phone serves as a hotspot for other mobile phones, it acts as an AP.

[0025] In some embodiments, AP 110 and STA 120 may be devices used in vehicle networking, 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.

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

[0027] In some embodiments, AP 110 and / or STA 120 can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; they can also be deployed on water (such as on ships); and they can also be deployed in the air (such as on airplanes, balloons, and satellites).

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

[0029] For example, STA 120 can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0030] It should be understood that Figure 1 These are merely examples in this application and should not be construed as limiting the scope of this application. For example, Figure 1Only one AP and two STAs are shown as an example. In some embodiments, the communication system 100 may include multiple APs and other numbers of STAs. This application does not limit this.

[0031] Figure 2A This is a schematic diagram of an application scenario according to an embodiment of this application.

[0032] like Figure 2A As shown, the 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, a smart washing machine, an air conditioner, or an electronic lock. Non-AP MLD 220 and AP MLD 210 communicate via the wireless local area network 230. AP MLD 210 can be a soft AP MLD, a mobile AP MLD, etc.

[0033] like Figure 2B As shown, in Figure 2A In the communication system described, AP MLD 210 is associated with at least two APs 2101, and non-AP MLD 220 is associated with at least two stations (STAs) 2201. Each AP is connected to a different STA in non-AP MLD 220 via a different link. An AP affiliated with AP MLD can also be referred to as an AP affiliated with AP MLD, and a STA affiliated with non-AP MLD can also be referred to as a non-AP STA affiliated with non-AP MLD or a STA affiliated with non-AP MLD.

[0034] In this embodiment, AP MLD 210 and non-AP MLD 220 can be terminal devices. Terminal devices can refer to access terminals, user equipment (UE), user units, user stations, mobile stations, mobile stations, remote stations, remote terminals, mobile devices, user terminals, terminals, wireless communication devices, user agents, or user equipment. Access terminals can 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 a wireless modem, in-vehicle devices, wearable devices, terminal devices in 5th generation (5G) networks, or terminal devices in future evolved Public Land Mobile Networks (PLMNs), etc.

[0035] exist Figure 2A The communication system 200 shown may also include network equipment, which may be access network equipment that communicates with terminal equipment. The access network equipment can provide communication coverage for a specific geographical area and can communicate with terminal equipment located within that coverage area.

[0036] Figure 2A An example is shown of 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. This application embodiment does not limit this.

[0037] It should be noted that, Figure 1 , Figure 2A , Figure 2BThis application merely illustrates the system to which this application applies; of course, the methods shown 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" in this application merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this application generally indicates that the preceding and following related objects have an "or" relationship. It should also be understood that "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a related relationship. For example, A instructing B can mean that A directly instructs B, for example, B can be obtained through A; it can also mean that A indirectly instructs B, for example, A instructs C, B can be obtained through C; or it can mean that there is a related relationship between A and B. It should also be understood that "correspondence" mentioned in the embodiments of this application can indicate a direct or indirect correspondence between two things, or an related relationship between two things, or a relationship of instruction and being instructed, configuration and being configured, etc. It should also be understood that the "predefined" or "predefined rules" mentioned in the embodiments of this application can be implemented by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices), and this application does not limit the specific implementation method. For example, predefined can refer to those defined in a protocol. It should also be understood that in the embodiments of this application, the "protocol" can refer to standard protocols in the field of communication, such as the IEEE 802.11 protocol, LTE protocol, NR protocol, and related protocols applied to future communication systems, and this application does not limit this.

[0038] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0039] Unless otherwise specified, STA refers to a Non-AP device without an attached STA.

[0040] In related technologies, multi-link operation (MLO) is defined, along with AP MLD and Non-AP MLD with MLO capability. AP MLD and Non-AP MLD establish multiple links on multiple different frequency bands / channels.

[0041] like Figure 3As shown, the non-AP MLD and AP MLD successfully establish multiple links through the following process: Non-AP STA1 in the non-AP MLD sends an association request frame to AP1 in the AP MLD, and AP1 in the AP MLD sends an association response frame to Non-AP STA1 in the non-AP MLD. The links established between the AP MLD and the 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 work simultaneously. Among them, AP 1 operating on link 1 (2.4GHz), AP 2 operating on link 2 (5GHz), and AP 3 operating on link 3 (6GHz) are called the affiliated APs of the AP MLD. Similarly, non-AP STA 1 operating on link 1 (2.4GHz), non-AP STA 2 operating on link 2 (5GHz), and non-AP STA 3 operating on link 3 (6GHz) are called the affiliated non-AP STAs of the non-AP MLD.

[0042] In related technologies, such as Figure 4 As shown, 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 as different affiliated APs of this AP MLD. This multi-link operation architecture allows the AP MLD to use different affiliated APs and different links to provide services to the STA, thus better achieving uninterrupted roaming for the STA. For example... Figure 4 As shown, STA x uses multiple links to connect to AP 1 and AP 2 respectively. When STA x moves, the link connection to AP 1 is disconnected but the link connection to AP 2 is not affected. Therefore, the mobility support of STA is improved.

[0043] Fast BSS transition (FT) The goal of fast BSS transition is to reduce the duration of connection loss between STAs and DSs, or between non-AP MLDs and DSs, during BSS transition. The FT protocol, part of the reassociation service, applies only to transitions between APs or AP MLDs within the same Extended Service Set (ESS) and the same mobile domain. APs publish features and policies supporting the FT protocol and methods. FT features are published in beacon and probe response frames, including a Mobility Domain Element (MDE). The MDE, published in beacon and probe response frames, indicates the mobility domain identifier (MDID), FT capabilities, and FT policies.

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

[0045] The FT defines two FT protocols: —FT protocol. This protocol is executed when the FTO is converted to the target FTR, and no resource request is required before the conversion.

[0046] —FT Resource Request Protocol. This protocol is executed when the FTO needs to request resources before its transformation.

[0047] For an FTO that moves to a target FTR using the FT protocol, message exchange is performed using one of the following two methods: Wireless. The FTO communicates directly with the target FTR, is IEEE 802.11 certified, and uses the FT authentication algorithm.

[0048] Based on DS (Over-the-DS). The FTO communicates with the target FTR via the current FTR. Communication between the FTO and the target FTR takes place in FT Action frames between the FTO and the current FTR. Communication between the current FTR and the target FTR is performed using the encapsulation method described in the "Remote Request / Response Frame Definition". The current AP performs conversion between the two encapsulations.

[0049] Although the current FT can reduce the duration of lost connectivity between STA and DS or between non-AP MLD and DS during BSS transition, it cannot maintain data continuity between STA and DS or between non-AP MLD and DS because the transition from STA (or Non-AP MLD) to target AP (or target AP MLD) requires re-association and re-establishment of data transmission and reception protocols and scenarios.

[0050] While a logical AP MLD theoretically supports multiple APs located in different locations attached to a single logical AP MLD using different links to provide services to the same non-AP MLD, thus achieving uninterrupted roaming for the non-AP MLD, the synchronization and acknowledgment of data communication status between APs based on the non-AP MLD are challenging. This is because the APs attached to the logical AP MLD are in different locations, placing high demands on the communication quality of the backhaul links between APs. Therefore, achieving such synchronization and acknowledgment is difficult.

[0051] To facilitate understanding of the technical solutions of the embodiments of this application, the technical solutions of this application are described in detail below through specific embodiments. The above-mentioned related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0052] The wireless communication method provided in this application embodiment is applied to non-access point multi-link devices, such as... Figure 5 As shown, it includes: S501. The non-access point multi-link device receives or sends a first frame, which 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. The third access point multi-link device is a logical access point multi-link device.

[0053] The wireless communication method provided in this application embodiment is applied to access point multi-link devices, such as... Figure 6 As shown, it includes: S601. The access point multi-link device sends or receives a first frame, which 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.

[0054] Below, regarding the above Figure 5 or Figure 6 The wireless communication method shown is explained.

[0055] The first access point multilink device and the second access point multilink device are two access point multilink devices that are not located in the same place (non-collocated).

[0056] The non-access point multi-link device performs a switching between the first access point multi-link device and the second access point multi-link device, including one of the following: Scenario 1: When the Non-AP MLD is associated with a third access point multi-link device, and both the first and second access point multi-link devices are attached to the same third access point multi-link device, the non-access point multi-link device performs a conversion (or switch) of the access point multi-link device-level association between the first and second access point multi-link devices. Scenario 2: When the Non-AP MLD is only associated with the first access point multi-link device or the second access point multi-link device, wherein 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-access point multi-link device performs association conversion (or switching) between the first access point multi-link device and the second access point multi-link device.

[0057] The term "transition" in the embodiments of this application can also be replaced by "switching".

[0058] For the first conversion scenario, the conversion (or handover) of the multi-link device-level association of the third access point multi-link device refers to the following: before the conversion, the non-AP MLD is associated with the third AP MLD and the non-AP MLD establishes multiple links with an AP MLD attached to the third AP MLD (i.e., all or part of the links established between the non-AP MLD and the third AP MLD belong to the links between the non-AP MLD and the AP MLD attached to the third AP MLD). After the conversion, the non-AP MLD is still associated with the third AP MLD and the non-AP MLD establishes multiple links with another AP MLD attached to the third AP MLD (i.e., all or part of the links established between the non-AP MLD and the third AP MLD belong to the links between the non-AP MLD and the other AP MLD attached to the third AP MLD).

[0059] like Figure 7 As shown, the first access point multi-link device and the second access point multi-link device are auxiliary access point multi-link devices or auxiliary access point multi-link devices of the same third access point multi-link device. The auxiliary access point multi-link devices of the third access point multi-link device may or may not include other access point multi-link devices besides the first and second access point multi-link devices.

[0060] In this embodiment, the third access point multilink device is a logical entity composed of multiple access point multilink devices, including the first access point multilink device and the second access point multilink device. It is understood that the multiple access point multilink devices constituting the third access point multilink device belong to the same mobile domain. The third access point multilink device can be the access point multilink device corresponding to that mobile domain, and can be defined as a mobile domain multilink device (MD AP MLD).

[0061] Understandably, 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. For example... Figure 8As shown, before the conversion, the non-access point multi-link device is associated with the first access point multi-link device attached to 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 attached to 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 second access point multi-link device. Therefore, when the non-access point multi-link device is associated with the first access point multi-link device attached to the third access point multi-link device, as the location moves, it will be associated with or re-associated with the second access point multi-link device attached to the third access point multi-link device, and will continue to transmit the data transmitted with the first access point multi-link device through the second link between the non-access point multi-link device and the first access point multi-link device, thereby maintaining the continuity of the session and the persistence of data during the process of the access point multi-link device associating with different attached access point multi-link devices of the third access point multi-link device due to roaming.

[0062] For the second conversion scenario, the non-access point multilink device associates with access point multilink devices attached to different logical access point multilink devices before and after the conversion or switch, thereby performing the associated conversion or switch.

[0063] For a third access point multilink device attached to a first access point multilink device, the third access point multilink device is attached to multiple access point multilink devices including the first access point multilink device.

[0064] For a third access point multilink device attached to a second access point multilink device, the third access point multilink device is attached to multiple access point multilink devices including the second access point multilink device.

[0065] During the transition between a non-access point multilink device and a first access point multilink device or a second access point multilink device attached to the same third access point multilink device or different third access point multilink devices, the frame used for communication with the first access point multilink device or the second access point multilink device is called the first frame.

[0066] The conversions provided in the embodiments of this application may include fast BSS transition (FT), seamless BSS transition, or seamless fast transition in BSS transition or BSS switching.

[0067] BSS transition is the process by which a site or non-APMLD (non-APMLD) transitions (or switches) within the same Extended Service Set (ESS) from a BSS or first access point multi-link device (AP MLD) to a BSS or second access point multi-link device (AP MLD).

[0068] Fast BSS transition (FT) is a type of BSS transition that minimizes the time it takes for data to be lost when connected to the distribution system (DS).

[0069] Seamless BSS transformation is a type of BSS transformation that maintains data connectivity with the distributed system DS.

[0070] Seamless and fast BSS transformation is a type of BSS transformation that maintains data connectivity with the distributed system (DS) and reduces the time required for BSS transformation.

[0071] The wireless communication method provided in this application embodiment allows a non-access point multilink device to switch between a first access point multilink device and a second access point multilink device that are attached to the same logical access point multilink device or different third access point multilink devices. In an architecture where a third access point multilink device is provided on top of the first access point multilink device and the second access point multilink device, the method performs conversion or switching control on communication between the first access point multilink device and the non-access point multilink device, and on communication between the second access point multilink device and the non-access point multilink device. This enables the non-access point multilink device, which is oriented towards data continuity, to switch or switch between the first access point multilink device and the second non-access point multilink device.

[0072] It should be noted that, Figure 5 or Figure 6 The method is the conversion or handover from the first AP MLD to the second AP MLD in the scenario of a Non-AP MLD in the mobile domain AP MLD. The wireless communication method provided in the embodiments of this application is also applicable to the conversion or handover from the first AP to the second AP in the scenario of a non-MLD STA in the mobile domain AP MLD.

[0073] In some embodiments, the first access point multi-link device is an access point multi-link device in which the associated access points (APs) are located in the same location; the second access point multi-link device is an access point multi-link device in which the associated APs are located in the same location.

[0074] 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 located in the same location as the affiliated APs (referred to as a collocated AP MLD or co-located AP MLD). The second access point multi-link device is an access point multi-link device located in the same location as the affiliated APs. The first access point multi-link device and the second access point multi-link device are AP MLDs located in different locations.

[0075] In some embodiments, the third access point multilink device is used for at least one of the following: Function 1: Provide connection services between the non-access point multi-link device or the auxiliary access point multi-link device and the distributed system DS; Function 2: Maintain the 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; Function 3: Authentication and / or association or reassociation of the non-access point multi-link devices; Function 4: Security association of the non-access point multi-link devices; Function 5: Distribution of all or part of the security association information of the non-access point multi-link device; Function 6: Synchronization of all or part of the status and / or buffer information of the upper layer MAC of the auxiliary access point multi-link device; Function 7: Manage the distribution of authentication information for the non-access point multi-link devices; Function 8: Manage the association or re-association at the subordinate access point multilink device level between the non-access point multilink device and the subordinate access point multilink device; Function 9: For a target access point multilink device that establishes a multilink between at least one affiliated access point multilink device and the non-access point multilink device, select the MAC address corresponding to the target access point multilink device for data transmission; Function 10: Synchronization of first data between different auxiliary access point multilink devices, wherein the first data is used to maintain the data continuity of communication between the non-access point multilink device and the auxiliary access point multilink device or DS; Function 11: Exchange or indicate MLD-level information through the MAC sublayer of the auxiliary access point multi-link device.

[0076] In this embodiment of the application, the auxiliary access point multilink device can be understood as an auxiliary access point multilink device of the third access point multilink device.

[0077] For Function 1, the third access point multilink device provides DS access functionality to its affiliated access point multilink device and the non-access point multilink device (non-AP MLD) associated with its affiliated access point multilink device. Its affiliated access point multilink device and the non-access point multilink device (non-AP MLD) associated with its affiliated access point multilink device access DS, thereby enabling the non-AP MLD to directly call or call one or more distributed system services (DSS) through the affiliated access point multilink device.

[0078] For Function 2, maintain the data continuity of the non-APMLD during the roaming process when switching between the first and second access point multi-link devices, and achieve seamless switching between the first and second access point multi-link devices.

[0079] Function 3: The third access point multi-link device is used for authentication and / or association or reassociation of the non-access point multi-link device. This can be understood as the non-access point multi-link device associating or reassociating with the third access point multi-link device when the non-access point multi-link device is associated or reassociated with the access point multi-link device attached to the third access point multi-link device.

[0080] 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 is also associated with the third access point multi-link device. In this embodiment, if 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, then there is an association 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, there is also an association 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 the DSS.

[0081] When a third access point multilink device is able to authenticate non-access point multilink devices associated with its subordinate access point multilink devices.

[0082] The types of security associations in Function 4 may include at least one of the following: Pairwise Master Key Security Association (PMKSA) and Pairwise Security Association (PTKSA).

[0083] Function 5: The third access point multi-link device is used for distributing security association information of the non-access point multi-link device.

[0084] A security association can be established between a non-access point multi-link device and an auxiliary access point multi-link device of a third access point multi-link device, and the third access point multi-link device can distribute all or part of the security association information.

[0085] Security association information includes information used when data is transmitted over an established security association.

[0086] For function six, the auxiliary access point multilink device of the third access point multilink device may include upper-layer MAC and lower-layer MAC. The higher layer of the upper-layer MAC of the auxiliary access point multilink device of the third access point multilink device, namely the MAC general sublayer, synchronizes all or part of the status and / or buffer information of the upper-layer MAC of the auxiliary access point multilink device.

[0087] In some embodiments, synchronization may be achieved by at least one of the following methods: copying or migration.

[0088] For Function 7, the authentication information of the link includes at least one of the following: Group Temporal Key (GTK), Complete GTK (IGTK), and Beacon IGTK (BIGTK).

[0089] For the association or re-association at the auxiliary access point multi-link device level in Function 8, it refers to the establishment or re-establishment of multiple links between the non-AP MLD and the auxiliary access point multi-link device of the third access point multi-link device. That is, the non-AP MLD is associated or re-associated with the third access point multi-link device, and at least one of the links established (or re-established) between the non-AP MLD and the third access point multi-link device belongs to the link between the non-AP MLD and the auxiliary access point multi-link device of the third AP MLD.

[0090] In some embodiments, when a non-access point multi-link device is associated with or reassociated with a subordinate access point multi-link device of a third access point multi-link device, and the 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.

[0091] Understandably, when a non-access point multilink device is associated with a subordinate access point multilink device of a third access point multilink device, the non-access point multilink device can also be associated with or reassociated with other subordinate access point multilink devices of the third access point multilink device.

[0092] For function nine, the third access point multilink device is used to select the MAC address corresponding to the target access point multilink device for data transmission for a target access point multilink device associated with or having established a multilink with at least one of the subordinate access point multilink devices. It can be understood that the MAC addresses of all subordinate access point multilink devices of the third access point multilink device are connected to the third access point multilink device. The access point multilink device associated with the non-access point multilink device among the subordinate access point multilink devices of the third access point multilink device is the target access point multilink device. When the non-access point multilink device communicates with the target access point multilink device, the third access point multilink device selects the MAC address of the target access point multilink device from the MAC addresses of all subordinate access point multilink devices for data communication.

[0093] For Function Ten, the third access point multilink device is used for synchronizing first data between different auxiliary access point multilink devices of the third access point multilink device, enabling the different auxiliary access point multilink devices of the third access point multilink device to synchronize the first data for data communication with the same non-access point multilink device. Understandably, when a non-access point multilink device communicates with a subordinate access point multilink device of the third access point multilink device using the first data, the third access point multilink device can synchronize the first data to another subordinate access point multilink device of the third access point multilink device, allowing that subordinate access point multilink device to continue data communication with the non-access point multilink device based on the first data, thereby maintaining the continuity of data communication.

[0094] The third access point multilink device is also used for the synchronization of the first data to the DS. The synchronization of the first data to the DS can be understood as the synchronization of the first data between different access point multilink devices.

[0095] For Function Seven, the third access point multi-link device is used to exchange MLD-level information between different affiliated access point multi-link devices through the MAC sublayer of different affiliated access point multi-link devices, or, the third access point multi-link device indicates information to the MAC sublayer of the affiliated access point multi-link device, thereby indicating MLD-level information to that affiliated access point multi-link device. Understandably, MLD-level information refers to information about the AP MLD attached to the third access point multi-link device or the Non-AP MLD associated with the affiliated AP MLD.

[0096] In some embodiments, when the first or 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 auxiliary access point multi-link device. The lower MAC sublayer of the auxiliary access point multi-link device may include at least one auxiliary AP included in the auxiliary access point multi-link device.

[0097] Assuming 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 and second access point multi-link devices is as follows: Figure 9 As shown, AP MLD1 has an MLD MAC address of M, and its affiliated APs include AP1 with MAC address w and AP2 with MAC address x; AP MLD2 has an MLD MAC address of N, and its affiliated APs include AP3 with MAC address r and AP4 with MAC address s; AP MLD3 has an MLD MAC address of Q; AP MLD3 serves as the general MAC sublayer of MLD. AP MLD1 includes an upper MAC sublayer, a lower MAC sublayer, and a lower MAC sublayer of affiliated MLD. AP MLD2 includes an upper MAC sublayer, a lower MAC sublayer, and a lower MAC sublayer of affiliated MLD. The upper MAC sublayer of affiliated MLD provides a MAC SAP for communication with the general MAC sublayer of MLD. The lower MAC sublayer of affiliated MLD provides the affiliated APs of the affiliated AP MLD. The MLD general MAC sublayer connected to the auxiliary MLD MAC sublayer can switch between the auxiliary MLD MAC sublayer of AP MLD1 and the auxiliary MLD MAC sublayer of AP MLD2, and through this switching, the first data can be synchronized between the auxiliary MLD MAC sublayer of AP MLD1 and the auxiliary MLD MAC sublayer of AP MLD2. Figure 9 As shown, AP MLD1 and APMLD2 can also communicate with DS through the MAC SAP of the MLD general MAC sublayer.

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

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

[0100] When the third access point multi-link device is an MD AP MLD, the switching between the non-access point multi-link device and the first and second access point multi-link devices can be understood as the rapid switching between the non-access point multi-link device and the first and second access point multi-link devices in the MDAP MLD scenario.

[0101] A mobile domain AP MLD (MD AP MLD) can be understood as a roaming AP MLD or a non-collocated AP MLD, which is an access point multi-link device whose affiliated APs are not located in the same place.

[0102] In some embodiments, the first frame includes first information, which includes at least one of the following: First indication information, the first indication information is used to indicate whether the non-access point multilink device supports or is allowed to switch between two auxiliary access point multilink devices in the same MD AP MLD; The second indication information is used to indicate the third access point multi-link device.

[0103] If the first indication information indicates that the non-access point multilink device supports or is permitted to switch between two subordinate access point multilink devices within the same MD AP MLD, then the non-access point multilink device is capable of switching between the two subordinate access point multilink devices within an MD AP MLD. If the first indication information indicates that the non-access point multilink device does not support or is permitted to switch between two subordinate access point multilink devices within the same MD AP MLD, then the non-access point multilink device is unable to switch between the two subordinate access point multilink devices within an MD AP MLD.

[0104] The first indication information can indicate, based on different values, whether a non-access point multilink device supports or is permitted to switch between two affiliated access point multilink devices within the same MD AP MLD. In one example, if the first indication information is 1, it indicates that switching between two AP MLDs belonging to the same mobile domain AP MLD is supported or permitted; if the first indication information is 0, it indicates that fast switching between two AP MLDs belonging to the same mobile domain AP MLD is not supported or permitted. In this case, the terminal device can switch between two AP MLDs belonging to different mobile domain AP MLDs.

[0105] In this embodiment of the application, the first indication information can be identified as FT (FtinMobileDomainMLD) within the mobile domain MLD.

[0106] Understandably, Mobile Domain MLD can be replaced with Mobile Domain APMLD.

[0107] The second indication information is used to indicate the third access point multilink device. Wherein, if the non-access point multilink device performs a switching between two affiliated access point multilink devices of the third access point multilink device, the second indication information can be defined as the MD AP MLD attached to the two affiliated access point multilink devices performing the switching.

[0108] In this embodiment of the application, the second indication information can be identified as MobileDomainMLDInfo.

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

[0110] In some embodiments, the first frame includes at least one of the following: A first conversion frame is used to initiate the conversion of the non-access point multi-link device from a first access point multi-link device to a second access point multi-link device; The second conversion frame is used by the first access point multi-link device to synchronize second data to the second access point multi-link device. The second data is used to maintain the 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 is converted to the second access point multi-link device. The third conversion frame is used to associate or reassociate the non-access point multilink device with the second access point multilink device.

[0111] In this embodiment of the application, the transmission or reception of the first conversion frame is earlier than the transmission or reception of the second conversion frame; the transmission or reception of the second conversion frame is earlier than the transmission or reception of the third conversion frame.

[0112] For the first transition frame, the non-access point multi-link device initiates the transition from the first access point multi-link device to the second access point multi-link device through the transmission of the first transition frame.

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

[0114] In this embodiment of the application, the non-access point multi-link device can directly transmit the first conversion frame with the second access point multi-link device, or it can transmit the first conversion frame with the second access point multi-link device through the first access point multi-link device.

[0115] In some embodiments, the first conversion frame includes: A conversion request frame sent from the non-access point multi-link device to the second access point multi-link device, the conversion request frame being used to request a conversion from the first access point multi-link device to the second access point multi-link device; A conversion response frame sent from the second access point multilink device to the non-access point multilink device, the conversion response frame being used to respond to the conversion request frame.

[0116] In some embodiments, the conversion request frame may be a Fast Conversion Request (FT Request) frame, and the conversion response frame may be a Fast Conversion Response (FT Response) frame.

[0117] When a non-access point multi-link device directly transmits a first conversion frame with a second access point multi-link device, the non-access point multi-link device sends a conversion request frame to the second access point multi-link device, and the second access point multi-link device responds to the received conversion request frame by sending a conversion response frame to the non-access point multi-link device.

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

[0119] For the second conversion frame, the transmission of the second conversion frame between the non-access point multilink device and the first access point multilink device or the second access point multilink device enables the synchronization of the second data of the first access point multilink device to the second access point multilink device, so that the non-access point multilink device and the second access point multilink device can continue to perform data communication between the non-access point multilink device and the first access point multilink device.

[0120] The second method of data synchronization can include: copying or migration.

[0121] In some embodiments, 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 with the second 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. The second conversion confirmation frame is used by the first access point multi-link device to synchronize the second data with the second access point multi-link device. A first conversion response frame sent from the first access point multilink device to the non-access point multilink device, the first conversion response frame being used to feedback the synchronization status of the second data; A second conversion response frame is sent from the second access point multilink device to the first access point multilink device. The second conversion response frame is used to feed back the synchronization status of the second data to the first access point multilink device.

[0122] In this embodiment of the application, for a non-access point multi-link device, the second conversion frame received or sent includes: 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 with the second access point multi-link device; A first conversion response frame sent from the first access point multilink device to the non-access point multilink device, the first conversion response frame being used to feedback the synchronization status of the second data.

[0123] In the embodiments of this application, such as Figure 10As shown, the non-access point multi-link device sends a first conversion confirmation frame to the first access point multi-link device; in response to the received first conversion confirmation frame, 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 second 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 response frame, the first access point multi-link device sends a first conversion response frame to the non-access point multi-link device.

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

[0125] The first transition response frame and the second transition response frame are transition response frames sent on different links. In some embodiments, the transition response frame can be understood as a Fast Transition Response (FT ACK) frame.

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

[0127] In this embodiment of the application, by means of Figure 10 The process shown involves synchronizing the second data used by the first access point multi-link device to maintain data communication between the non-access point multi-link device and either the first or third access point multi-link device to the second access point multi-link device. This synchronized second data can be understood as the requested resource. Therefore... Figure 10 The process shown can be understood as a resource request process.

[0128] In some embodiments, the first conversion confirmation frame carries third data of the non-access point multi-link device, the third data being 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 being used by the first access point multi-link device to determine the second data.

[0129] exist Figure 10 In the illustrated process, the first conversion confirmation frame sent by the non-access point multi-link device to the first access point multi-link device carries third data from the non-access point multi-link device. Upon receiving the first conversion confirmation frame, the first access point multi-link device, in response, sends a second conversion confirmation frame to the second access point multi-link device, carrying second data in the second conversion confirmation frame. 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.

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

[0131] In one example, the first conversion confirmation frame sent by the Non AP MLD to the first access point multi-link device carries the 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. The second conversion confirmation frame sent by the first access point multi-link device to the second access point multi-link device carries the 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.

[0132] In some embodiments, the second data includes at least one of the following: The second information is the information of the Block Ack Agreement context of the first access point multi-link device; The third information is information about the security association scenario of the multi-link device at the first access point.

[0133] The block acknowledgment protocol scenario can also be described as the block acknowledgment protocol context, block acknowledgment protocol scenario (Block Ackcontext), or block acknowledgment context, which is information about the block acknowledgment process that is maintained.

[0134] Security association scenarios can also be described as security association contexts, which provide information about the security association process being maintained.

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

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

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

[0138] The third conversion frame is used for association or reassociation between the non-access point multi-link device and the second access point multi-link device. In this embodiment, the third conversion frame is used for association or reassociation at the subordinate access point multi-link device level.

[0139] In some embodiments, the third conversion frame includes at least one of the following: An association request frame or reassociation request frame sent by the non-access point multilink device to the second access point multilink device; The associated response frame or reassociation response frame sent by the second access point multilink device to the non-access point multilink device.

[0140] 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 and the second access point multi-link device are associated or reassociated through the third conversion frame, thereby realizing the association or reassociation at the subordinate access point multi-link device level.

[0141] The non-access point multi-link device sends an association request frame or a re-association request frame to the second access point multi-link device. In response to the received association request frame or re-association request frame, the second access point multi-link device sends an association response frame or a re-association response frame to the non-access point multi-link device.

[0142] After the non-access point multi-link device is associated or reassociated with the second access point multi-link device, data transmission can be carried out. Among them, the data transmission between the non-access point multi-link device and the first access point multi-link device can continue based on the second data synchronized by the second conversion frame.

[0143] The frame format of the second conversion frame provided in the embodiments of this application will be described below.

[0144] The second data used for synchronization in the second conversion frame may include: information from the block acknowledgment protocol scenario and / or information from the security association scenario.

[0145] In the scenario where the second data used for synchronization in the second conversion frame includes information about the block acknowledgment protocol scenario. In some embodiments, the second conversion frame includes a block confirmation protocol scenario element, which is used to indicate information about the block confirmation protocol scenario.

[0146] For the first transition confirmation frame, the block confirmation protocol scenario element in the first transition confirmation frame is used to indicate information about the block confirmation protocol scenario of the non-access point multilink device.

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

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

[0149] In this embodiment of the application, the block confirmation protocol scenario element contains information about a specific MLD having established and maintained block confirmation protocol scenarios with one or more peer MLDs. It is understood that a block confirmation protocol scenario can also be described as a block confirmation protocol state, or a block confirmation protocol scenario or state.

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

[0151] In one example, such as Figure 11 As shown, the block confirmation protocol scenario element includes the following subfields: Element ID, Length, Element ID Extension, block confirmation protocol scenario parameter control, and block confirmation protocol scenario parameter set list. The Element ID field, Length field, and Element ID Extension field in the block confirmation protocol scenario element adopt the general definitions of relevant elements in related protocols.

[0152] In some embodiments, the block confirmation protocol scenario element includes a block confirmation protocol scenario parameter control field, which is used to indicate at least one of the following: The device in which 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 described by the block confirmation protocol scenario element is the same device; When the peer device targeted by the block confirmation protocol scenario described by the block confirmation protocol scenario element is the same device, the peer device targeted by the block confirmation protocol scenario is the same device. The number of block confirmation protocol scenario parameter sets included in the block confirmation protocol scenario element.

[0153] The device in which the block confirmation protocol scenario described by the block confirmation protocol scenario element is located can be the MAC address of the corresponding device.

[0154] The device containing the block confirmation protocol scenario described by the block confirmation protocol scenario element can be indicated by the first field in the block confirmation protocol scenario parameter control field. The first field in the block confirmation protocol scenario parameter control field can be defined as an MLDMAC address subfield indicator.

[0155] The first field of the block confirmation protocol scenario parameter control field in the first conversion confirmation frame indicates the non-access point multilink device.

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

[0157] The first field of the block acknowledgment protocol scenario parameter control field in the second transition response frame or the first transition response frame indicates the second access point multilink device.

[0158] Whether the peer device targeted by the block confirmation protocol scenario described by the block confirmation protocol scenario element is the same device can be indicated by the second field in the block confirmation protocol scenario parameter control field.

[0159] In one example, when the value of the second field in the block confirmation protocol scenario parameter control field is 0, it means that the peer MLD targeted by the block confirmation protocol scenario of the MLD described by the block confirmation protocol scenario element is the same MLD. When the value of the second field is 1, it means that the peer MLD targeted by the block confirmation protocol scenario of the MLD described by the block confirmation protocol scenario element is not the same MLD, that is, the peer includes multiple MLDs.

[0160] The second field in the block confirmation protocol scenario parameter control field can be defined as whether the peer device is in the same device subdomain.

[0161] In one example, assuming the 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 peer 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 is AP MLD1, and the peer 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 peer 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 peer device targeted by the block confirmation protocol scenario includes the STA.

[0162] When the peer device targeted by the block confirmation protocol scenario described by the block confirmation protocol scenario element is the same device, the peer device targeted by the block confirmation protocol scenario can be indicated by the third field in the block confirmation protocol scenario parameter control field.

[0163] When 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, the third field in the block confirmation protocol scenario parameter control field indicates the peer device; when the peer device targeted by the block confirmation protocol scenario of the device described by the block confirmation protocol scenario element is multiple devices, the third field may not be included in the block confirmation protocol scenario parameter control field.

[0164] The third field in the Block Acknowledgment Protocol Scenario Parameter Control Field can be defined as the peer device MAC address subfield or the peer MLD MAC subfield (Peer MLD MAC).

[0165] The number of individual block confirmation protocol scenario parameter set subfields in the block confirmation protocol scenario parameter set list field of the block confirmation protocol scenario element can be indicated by the fourth field in the block confirmation protocol scenario parameter control field.

[0166] The fourth field in the Block Confirmation Protocol Scenario Parameter Control Field can also be understood as indicating the number of individual Block Confirmation Protocol Scenario Parameter Set Subfields in the Block Confirmation Protocol Scenario Parameter Set List Field of the Block Confirmation Protocol Scenario Element, wherein an individual 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.

[0167] In one example, such as Figure 12As shown, the block confirmation 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 parameters in a single block confirmation protocol scenario parameter set, and reservations.

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

[0169] In addition to the block confirmation protocol scenario parameter set subfield, the block confirmation protocol scenario parameter set list field may also include a padding subfield.

[0170] In one example, such as Figure 13 As shown, the Block Confirmation Protocol Scenario Parameter Set Subfield includes multiple Individual Block Confirmation Protocol Scenario Parameter Set Subfields and Padding Subfields.

[0171] In some embodiments, 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; The corresponding block confirmation protocol scenario targets the peer device; Block confirmation parameter set; Block confirmation timeout value.

[0172] The roles of the devices in the corresponding block confirmation protocol scenarios can include initiator and receiver.

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

[0174] In one example, when the value of the MLD role field is 0, it means 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 means 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.

[0175] The peer device targeted by the corresponding block confirmation protocol scenario can be indicated by the sixth field in the subfield of the block confirmation protocol scenario parameter set.

[0176] If the device described in the block confirmation protocol scenario is a Non AP MLD, the peer device targeted by the block confirmation protocol scenario is the first AP MLD or the third AP MLD attached to the first AP MLD.

[0177] If the device described in the block confirmation protocol scenario is the first AP MLD or the third AP MLD attached to the first AP MLD, the peer device targeted by the block confirmation protocol scenario is the Non AP MLD.

[0178] The sixth field of the Block Acknowledgment Protocol (BAP) scenario parameter set subfield can be defined as the Peer MLD MAC address, indicating the MAC address of the peer device targeted by the corresponding BAP scenario.

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

[0180] The block acknowledgment timeout value is used to indicate the duration of information in the current block acknowledgment protocol scenario. If no frame exchange is performed within the duration of information in the current block acknowledgment protocol scenario, then the information in the current block acknowledgment protocol scenario is invalid or invalid.

[0181] The block acknowledgment timeout value can be indicated by the eighth field in the subfield of the block acknowledgment protocol scenario parameter set. The eighth field of the block acknowledgment protocol scenario parameter set subfield can also be defined as the acknowledgment timeout value field.

[0182] In one example, the acknowledgment timeout value field contains the duration in units of time (TU). If no frame exchange sequence occurs within this duration using the block acknowledgment protocol, the block acknowledgment protocol will terminate after this duration. Setting this field to 0 indicates a disabled timeout.

[0183] In some embodiments, 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 identifier; Buffer size.

[0184] The third indication information can be indicated by the first subfield of the seventh field of the Block Confirmation Protocol Scenario Parameter Set subfield, and the first subfield of the seventh field of the Block Confirmation Protocol Scenario Parameter Set subfield can be defined as the A-MSDU support subfield.

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

[0186] The block acknowledgment policy can be indicated by the second subfield in the seventh field of the Block Acknowledgment Protocol Scenario Parameter Set subfield, which can be defined as the Block Ack Policy subfield.

[0187] The flow identifier can be indicated by the third subfield in the seventh field of the Block Acknowledgment Protocol Scenario Parameter Set subfield, which can be defined as the Flow Identifier (TID) field.

[0188] The buffer size can be indicated by the fourth subfield in the seventh field of the block acknowledgment protocol scenario parameter set subfield, which can be defined as the buffer size field.

[0189] In one example, such as Figure 14 As shown, the block acknowledgment parameter set subfields include the following subfields: A-MSDU Supported, Block Ack Policy, Stream Identifier (TID), and Buffer Size.

[0190] In some embodiments, if the block confirmation protocol scenario parameter set subfield is used to indicate that 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 start sequence number; Send window size.

[0191] The starting sequence number of the sending window and the size of the sending window are sending buffer control parameters.

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

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

[0194] The ninth field in the block confirmation protocol scenario parameter set subfield can be defined as the sending window start sequence number (WinStartO) field.

[0195] The tenth field in the block confirmation protocol scenario parameter set subfield can be defined as the sending window size (WinSizeO) field.

[0196] In one example, for the initiator, such as Figure 15 As shown, 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 Acknowledgment Timeout, Sending Window Start Sequence Number (WinStartO), and Sending Window Size (WinSizeO).

[0197] In some embodiments, if the block confirmation protocol scenario parameter set subfield is used to indicate that the device in the corresponding block confirmation protocol scenario plays the role of 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 start 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.

[0198] The Receive Buffer Start Sequence Number (WinStartB) is a control parameter for the Receive Reordering Buffer, representing the value of the sequence number subfield of the first MSDU or A-MSDU (arranged in ascending order of sequence number) that has not yet been received.

[0199] The receive buffer start sequence number (WinStartB) can be indicated by the eleventh field in the block acknowledgment protocol scenario parameter set subfield, which can be defined as the WinStartB field.

[0200] The receive window size (WinSizeB) is a control parameter for the receive reordering buffer, indicating the size of the receive window.

[0201] The receive window size (WinSizeB) can be indicated by the twelfth field in the Block Acknowledgment Protocol Scenario Parameter Set subfield, which can be defined as the WinStartB field.

[0202] The record bitmap start sequence number (WinStartR) is a Scoreboard ContextControl parameter, a 12-bit unsigned integer start sequence number that represents the lowest sequence number position in the block acknowledgment record bitmap (indexed by sequence number).

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

[0204] Record the maximum sequence number of the bitmap (WinEndR), which represents the highest sequence number of the current transmission window. The maximum sequence number of the record bitmap is indicated by the fourteenth field in the block confirmation protocol scenario parameter set subfield, which can be defined as the WinEndR field.

[0205] Record bitmap size (WinSizeR) is a Scoreboard Context Control parameter, the maximum transmit window size, set to the smaller of the values ​​of the Bitmap Length and the Buffer size field of the relevant response frame in the Block Return Protocol.

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

[0207] In one example, for the receiver, such as Figure 16 As shown, the Block Ack Parameter Set subfield of the Block Ack Protocol scenario includes the following fields: MLD role (Initiator MLD), Peer MLD (RA, MLD MAC address), Block Ack Parameter Set, Block Ack Timeout, Receive Buffer Start Sequence Number (WinStartB), Receive Window Size (WinSizeB), Record Bitmap Start Sequence Number (WinStartR), Record Bitmap Maximum Sequence Number (WinEndR), and Record Bitmap Size (WinSizeR).

[0208] In scenarios where the second data used for synchronization in the second conversion frame includes information about the security-related scenario. In some embodiments, the second conversion frame includes a security-associated scene element, which is used to indicate information about a security-associated scene.

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

[0210] In some embodiments, a security-associated scenario element includes a security-associated scenario parameter control field and a security-associated scenario parameter set list field.

[0211] In one example, such as Figure 17 As shown, the security context element includes the following subfields: Element ID, Length, Element ID Extension, Security Context Parameters Control, and Security Context Parameters SetList.

[0212] In some embodiments, the security-associated scenario element includes a security-associated scenario parameter control field, which 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 peer device targeted by the security association scenario described by the security association scenario element is the same device; When the peer device targeted by the security association scenario described by the security association scenario element is the same device, the peer device targeted by the security association scenario is the same device. The number of security association scenario parameter sets included in the security association scenario element.

[0213] The device in which the security association scenario described by the security association scenario element is located can be the MAC address of the corresponding device.

[0214] The device containing the security association scenario described by the security association scenario element 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.

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

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

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

[0218] Whether the peer device targeted by the security association scenario described by the security association scenario element is the same device can be indicated by the second field in the security association scenario parameter control field.

[0219] In one example, when the value of the second field of the security association scenario parameter control field is 0, it means that the peer MLD targeted by the security association scenario of the MLD described by the security association scenario element is the same MLD. When the value of the second field of the security association scenario parameter control field is 1, it means that the peer MLD targeted by the security association scenario of the MLD described by the security association scenario element is multiple MLDs.

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

[0221] In one example, assuming the 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 peer 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 peer 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 peer 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 peer device targeted by the security association scenario includes the STA.

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

[0223] When the peer 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 field indicates the peer device; when the peer device targeted by the security association scenario of the device described by the security association scenario element is multiple devices, the third field may not be included in the security association scenario parameter control field.

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

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

[0226] The fourth field of the security-related scenario parameter control field can also be understood as indicating the number of security-related scenario parameter set subfields in the security-related scenario parameter set list field of the security-related scenario element, wherein one security-related scenario parameter set subfield in one security-related scenario parameter set list field indicates one security-related scenario parameter set.

[0227] In one example, such as Figure 18 As shown, the security association scenario parameter control domain includes the following subdomains: MLD MAC address, whether the peer MLD is the same MLD, peer MLD MAC address, number of security association scenario parameter sets, and reservations.

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

[0229] In one example, such as Figure 19 As shown, the list field of security-related scenario parameter sets includes multiple subfields of security-related scenario parameter sets.

[0230] In some embodiments, the security-associated scenario parameter set subdomain is used to indicate at least one of the following: The role of the device in the corresponding security association scenario; The corresponding security-related scenarios target the peer devices; The corresponding security association types for security association scenarios.

[0231] The role of the device in the corresponding security association scenario can include: receiver and sender.

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

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

[0234] The corresponding security association scenario targets a peer device, which can be indicated by the sixth field in the subfield of the security association scenario parameter set.

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

[0236] 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 attached to the first AP MLD.

[0237] If the device described in the security association is the first AP MLD or the third AP MLD attached to the first AP MLD, the peer device targeted by the security association scenario is a Non AP MLD.

[0238] The security association types for security association scenarios include one of the following: PTKSA, GTKSA, and TPKSA.

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

[0240] The PTKSA / GTKSA / TPKSA fields indicate the security association type corresponding to the replay scenario described by the replay scenario parameter set subfield. In one example, as shown in Table 1, different values ​​for the PTKSA / GTKSA / TPKSA fields represent different security association types. For instance, when the PTKSA / GTKSA / TPKSA subfield indicates PTKSA, the replay count value subfield in the replay scenario parameter set subfield corresponds to the PTKSA replay count value.

[0241] Table 1. PTKSA / GTKSA / TPKSA Field Values ​​and Their Meanings

[0242] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the device in the corresponding security association scenario plays the role of a receiver in the security association scenario; the security association scenario parameter set subfield is also used to indicate at least one of the following: Number of replay counters; TID; The count of the replay counter for the TID.

[0243] The number of replay counters can be indicated by the eighth field in the subfield of the security-associated scenario parameter set, which can be defined as the number of replay counters field.

[0244] The TID can be indicated by the ninth field in the subdomain of the security-associated scenario parameter set, which can be defined as the TID field.

[0245] The count of the replay counter for the TID can be indicated by the tenth field in the subfield of the security-associated scenario parameter set, which can be defined as the count of replay counter field.

[0246] In this embodiment of the application, the number of replay counters indicated by the subdomain of the security-associated scene parameter set includes a corresponding number of TIDs and a count of the replay counter for the TIDs.

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

[0248] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the device in the corresponding security association scenario plays the role of 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: Package number counter count; TID; The counting of the package number counter for the TID.

[0249] The number of packet counters can be indicated by the eleventh field in the subfield of the security-associated scenario parameter set, which can be defined as the number of PN counters field.

[0250] The TID can be indicated by the twelfth field in the subdomain of the security-associated scenario parameter set, which can be defined as the TID field.

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

[0252] In this embodiment of the application, the number of packet number counters indicated by the subfield of the security association scenario parameter set includes a corresponding number of TIDs and a count of the packet number counter for the TIDs.

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

[0254] In some embodiments, the second conversion frame further includes at least one of the following: The fourth indication information is used to indicate that the second data includes information on block confirmation protocol scenarios and / or security association scenarios.

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

[0256] If the resource type indicated by the fourth indication information includes a block acknowledgment protocol scenario, then: The resource request frame (first conversion confirmation frame and second conversion confirmation frame) contains block confirmation protocol scenario elements; The resource response frame (first transition response frame and second transition response frame) contains block acknowledgment protocol scenario elements.

[0257] As a non-access point multi-link device (FTO), it sends a resource request frame carrying block acknowledgment protocol (BACK) scenario elements to the first access point multi-link device, requesting the second access point multi-link device to establish a BACK scenario (or state). After receiving the resource request frame, the first access point multi-link device copies or migrates the corresponding BACK scenario (or state) it currently possesses to the second access point multi-link device. Based on the establishment status of the BACK scenario (or state) by the second access point multi-link device, it replies with a resource response to the first access point multi-link device, providing feedback on the establishment status of the BACK scenario (or state).

[0258] If the resource type indicated by the fourth instruction information includes a security-related scenario, then: The resource request frame (first conversion confirmation frame and second conversion confirmation frame) contains security-related scenario elements; The resource response frames (first conversion response frame and second conversion response frame) contain security-related scenario elements.

[0259] As a non-access point multi-link device (FTO), it sends a resource request frame carrying security-associated scenario elements to the first access point multi-link device, requesting that a security-associated scenario (or state) be established on the second access point multi-link device. After receiving the resource request frame, the first access point multi-link device copies or migrates the corresponding security-associated scenario (or state) currently possessed by the first access point multi-link device to the second access point multi-link device, and replies with a resource response to the first access point multi-link device based on the establishment status of the relevant security-associated scenario (or state) by the second access point multi-link device, providing feedback on the establishment status of the security-associated scenario (or state).

[0260] In some embodiments, based on Figure 5 The wireless communication method shown further includes: The non-access point multi-link device receives or sends a second frame, which is used for the non-access point multi-link device to associate or reassociate with the first access point multi-link device.

[0261] In some embodiments, based on Figure 6 The wireless communication method shown, if the access point multi-link device is the first access point multi-link device, further includes: The access point multi-link device sends or receives a second frame, which is used for the non-access point multi-link device to associate or reassociate with the first access point multi-link device.

[0262] Here, before switching from the first access point multilink device to the second access point multilink device, the non-access point multilink device associates or reassociates with the first access point multilink device through the interaction of the second frame with the first access point multilink device.

[0263] In some embodiments, the second frame includes first information, which includes at least one of the following: First indication information, the first indication information is used to indicate whether the non-access point multilink device supports or is allowed to switch between two auxiliary access point multilink devices in the same MD AP MLD; The second indication information is used to indicate the third access point multi-link device.

[0264] For a description of the first information, please refer to the description of the first information included in the first frame above, which will not be repeated here.

[0265] In some embodiments, the first information is located in the Mobile Domain Element (MDE).

[0266] In this embodiment of the application, the first frame may include an MDE and / or the second frame may include an MDE.

[0267] 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 affiliated access point multi-link devices of the same mobile 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 affiliated to the same mobile domain access point multi-link device, i.e., the third access point multi-link device, or can be associated with the second access point multi-link device and then re-associated, so as to manage or control the switching of the non-access point multi-link device based on the third access point multi-link device.

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

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

[0270] In one example, such as Figure 22 As shown, the conversion capabilities and policy domains include the following subdomains: fast BSS conversion via DS, resource request protocol capabilities, whether FT is in the same mobile domain AP MLD (FTinMobileDomainMLD), and reservations.

[0271] In some embodiments, 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.

[0272] In this embodiment, 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.

[0273] In one example, such as Figure 23 As shown, the MDE includes the following fields: Element ID, Length, Mobile Domain ID, FT Capability and Policy, Mobile Domain AP MLD ID, and Mobile Domain AP MLD MAC address.

[0274] It is understood that each field in the frame format provided in this application embodiment can exist independently, and fields or domains can be added, modified or deleted based on the provided frame format according to actual needs.

[0275] The wireless communication method provided in the embodiments of this application will be further described below.

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

[0277] High-level architecture of mobile domain AP MLD and its affiliated AP MLD The high-level architecture of the mobile domain AP MLD and its associated AP MLD provided in this application embodiment is as follows: Figure 24 As shown, in Figure 9Based on the architecture shown, the access point multi-link device is a Non-AP MLD, with the MLD address being P. The associated Non-AP SSTAs include Non-AP STA1 with MAC address y and Non-AP STA2 with MAC address z. The Non-AP MLD includes an upper MAC sublayer and a lower MAC sublayer. The associated Non-AP STAs are located in the lower MAC sublayer, and different associated Non-AP STAs establish links with the associated APs in associated AP MLD1 and associated AP MLD2 through different links. The link between Non-AP STA1 (associated with Non-AP MLD) and associated AP1 of AP MLD1 is Link 1; the link between Non-AP STA2 (associated with Non-AP MLD) and associated AP2 of AP MLD1 is Link 2; the link between Non-AP STA1 (associated with Non-AP MLD) and associated AP3 of AP MLD2 is Link 3; and the link between Non-AP STA2 (associated with Non-AP MLD) and associated AP4 of AP MLD2 is Link 4.

[0278] In this embodiment, 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, while link 3 and link 4 are connected, thereby realizing the conversion of the Non AP SMLD from AP MLD1 to APMLD2.

[0279] Mobile domain AP MLD common MAC sublayer functions include: 1. Provide distributed system access function (DSAF) to the auxiliary AP MLD of the mobile domain AP MLD. 2. Authentication, association, and re-association functions between non-AP MLDs and mobile domain AP MLDs; 3. Security association (such as PMKSA, PTKSA) and management of GTK / IGTK / BIGTK distribution; 4. Manage partial association and re-association functions between non-AP MLDs and corresponding subordinate AP MLDs of mobile domain AP MLDs; 5. For the auxiliary AP MLD associated with the non-AP MLD, select the MAC address of the corresponding auxiliary AP MLD for data transmission; 6. Synchronize (copy or migrate) all or part of the state and buffer information of the upper-UMAC of the mobile domain AP MLD's upper-layer MAC. 7. Exchange / instructions for MLD-level management information through the MAC sub-layer of the attached MLD.

[0280] Among them, the synchronization (copying or migration) of all or part of the state and buffer information of the upper-UMAC of the mobile domain AP MLD's upper-layer MAC includes: For a specific non-AP MLD associated with a mobile domain AP MLD, the process involves synchronizing (copying or migrating) all or part of the state and buffer information of the upper-level MAC of the current mobile domain AP MLD associated with the non-AP MLD to the associated target mobile domain AP MLD. This is to maintain the continuity of data communication sessions and the persistence of data transmission during the process of a non-AP MLD associating with different affiliated AP MLDs of a mobile domain AP MLD due to roaming.

[0281] All or part of the state and buffer information of the upper-UMAC of the mobile domain AP MLD's upper-layer MLD, i.e., the session or protocol state and buffer information maintained when exchanging data with a specific non-AP MLD (for a specific non-AP MLD): (1) SN / PN allocation status and related buffer data of unicast frames; (2) SN allocation status and related buffer data of group-addressed MAC Service Data Unit (MSDU); (3) Energy-saving buffer data for individually addressed frames; (4) Block Ack session status and related duplicate detection and reordering buffer data; (5) The PN counter status of the transmitting end and the replay detection status and related buffer data of the receiving end.

[0282] Block confirmation and security-related scenarios and state definitions For non-AP MLDs (or STAs) with data connectivity to quickly transition from the current AP MLD (or AP) to the target AP MLD (or AP), communication scenarios and state-related elements or fields are defined, including block acknowledgment scenarios or state elements and security-related scenarios or state elements, which are used for copying, migrating or updating block acknowledgment and security-related scenarios and states during the FT process.

[0283] FT protocol optimization and frame type and format definitions and function updates for interaction Based on the Mobile Domain AP MLD architecture, the frame type and format definitions and function updates for the FT protocol and interaction for data connectivity are as follows: the definitions of Mobile Domain Element (MDE), association and reassociation protocol, association frame and reassociation frame are updated, and the definitions of frames such as FT request and response protocol, FT resource request and response protocol, FT request frame, FT response frame, FT confirm frame, and FT ACK frame are updated.

[0284] The FT protocol based on data persistence includes the following processes: (1) Associate the current AP MLD with the Non-AP MLD and perform mobile domain AP MLD scene association or FT initial mobile domain AP MLD scene association; (2) Non-AP MLD initiates the FT process from the current AP MLD to the target AP MLD in the mobile domain AP MLD scenario; (3) For Non-AP MLD, copy or migrate the mobile domain AP MLD context, state, and / or all or part of the context, state, and buffer of the corresponding MLD of the mobile domain AP MLD from the current AP MLD to the target AP MLD.

[0285] (4) Non-AP MLD reassociation with target AP MLD in mobile domain AP MLD scenario The so-called non-AP MLD associated with the AP MLD in the mobile domain AP MLD scenario (or non-AP MLD associated with the AP MLD attached to the mobile domain AP MLD) refers to establishing a mapping relationship between the AP MLD attached to the mobile domain AP MLD and the non-AP MLD (including the mapping relationship between the mobile domain AP MLD and the AP MLD, as well as the mapping relationship between the AP MLD and the non-AP MLD), so that the non-AP MLD can be invoked (DSS). In this context, a non-AP MLD establishes a security association with a mobile domain AP MLD (such as PMKSA, PTKSA). When a non-AP MLD transitions from the current AP MLD attached to the mobile domain AP MLD to the target AP MLD attached to the mobile domain AP MLD in a mobile domain AP MLD scenario, PMKSA and PTKSA can remain unchanged. That is, when a non-AP MLD transitions from the current AP MLD attached to the mobile domain AP MLD to the target AP MLD attached to the mobile domain AP MLD in a mobile domain AP MLD scenario, it maintains a unicast key, including maintaining the same pair of master keys (PMK) and the same pair of temporary keys (PTK).

[0286] The wireless communication method provided in this application can be implemented in ways including but not limited to the following embodiments.

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

[0288] In this embodiment of the application, the Non-AP MLD is authenticated with the current AP MLD, such as... Figure 25 As shown, it includes: S2511, Non-AP MLD sends an Authentication-Request frame to the current AP MLD (FTR).

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

[0290] Based on the Mobile Domain AP MLD architecture, the frame type and format definitions and function updates for the FT protocol and interaction for data connectivity are as follows: the definitions of Mobile Domain Elements (MDE), association and reassociation protocols, association frames and reassociation frames are updated, as are the FT request and response protocols and FT resource request and response protocols, and the frame definitions of FT request frames, FT response frames, FT confirm frames, and FT ACK frames are updated.

[0291] (1) Non-AP MLD is associated with the current AP MLD and mobile domain AP MLD scene association is performed, or FT initial mobile domain AP MLD scene association is performed; where, such as Figure 25 ,include: S2521, Non-AP MLD sends an association request frame or reassociation request frame to the current AP MLD (FTR).

[0292] S2522, The current AP MLD (FTR) sends an associated response frame or a reassociated response frame back to the Non-AP MLD.

[0293] The association or reassociation request frame and the association or reassociation response frame include an MDE and a Basic Multi-Link element. The MDE can be labeled as MDE (FTinMobileDomainMLD, MobileDomainMLDInfo), which indicates that the MDE carries the first indication information FTiMobileDomainMLD and the second indication information MobileDomainMLDInfo.

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

[0295] The non-AP MLD is associated with the current AP MLD in the mobile domain AP MLD scenario, and can establish a successful session and data transmission with the current AP MLD.

[0296] (2) Non-AP MLD starts the FT process from the current AP MLD to the target AP MLD in the mobile domain AP MLD scenario.

[0297] When a Non-AP MLD (FTO) determines that a transition from the current AP MLD to the target AP MLD is needed in a mobile domain AP MLD scenario, the FTO sends a fast transition request frame to the target FTR through the current FTR. Then, the target AP MLD (FTR) sends a fast transition response frame back to the Non-AP MLD through the current AP MLD (FTR). like Figure 25 As shown, it includes: S2531, Non-AP MLD sends an FT request frame to the target AP MLD through the current AP MLD.

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

[0299] S2532, The target AP MLD sends an FT response frame to the Non-AP MLD through the current AP MLD.

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

[0301] The FT request frame and FT response frame carry an updated MDE (FTinMobileDomainMLD, MobileDomainMLDInfo information field) indicating that fast switching is supported or permitted between two AP MLDs belonging to the same mobile domain AP MLD.

[0302] (3) For Non-AP MLD, copy or migrate the mobile domain AP MLD context, state, and / or all or part of the context, state, and buffer of the corresponding MLD of the mobile domain AP MLD from the current AP MLD to the target AP MLD.

[0303] The FTO sends an FT Confirm frame to the target FTR through the current FTR, and then the target AP MLD (FTR) sends an FT ACK frame back to the Non-AP MLD through the current AP MLD (FTR).

[0304] like Figure 25 As shown, it includes: S2541, Non-AP MLD sends FT acknowledgment frame to the current AP MLD, and the current AP MLD sends FT acknowledgment frame to the target AP MLD.

[0305] 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-Linkelement), indicating that the FT confirmation frame is used to request resources, and the requested resources are carried in RIC-Request.

[0306] For the FT acknowledgment frame sent by the Non-AP MLD to the current AP MLD, the Block Ack Context element carries the scene information of the non-AP MLD corresponding to the BA acknowledgment protocol in which the non-AP MLD requests scene information synchronization from the current AP MLD to the target AP MLD; the SA context element carries the scene information of the non-AP MLD corresponding to the security association mechanism in which the non-AP MLD requests scene information synchronization from the current AP MLD to the target AP MLD.

[0307] For the FT acknowledgment frame sent by the current AP MLD to the target AP MLD, the Block Ack Context element carries the scene information of the AP MLD corresponding to the BA acknowledgment protocol that responds to the non-AP MLD request to complete the scene information synchronization from the current AP MLD to the target AP MLD; the SA context element carries the scene information of the AP MLD corresponding to the security association mechanism that responds to the non-AP MLD request to complete the scene information synchronization from the current AP MLD to the target AP MLD.

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

[0309] The FT response frame consists of FT ACK (FTO, TargetAP, MDE (FTinMobileDomainMLD, MobileDomainMLD Info), Time Element (TIE) (ReassociationDeadline), RIC-Response (Block Ack Context element, SA Context element), Basic Multi-Linkelement), indicating the time limit for the FT response frame to respond to and reassociate resources. The resources in the response are carried in the RIC-Response. FT Confirm and FT ACK carry Block Ack Context element and SA Context element, indicating the relevant block confirmation protocol scenario (or state) information and security association scenario (or state) information.

[0310] For the FT ACK frame, the Block Ack Context element carries the scene information of the AP MLD corresponding to the BA acknowledgment protocol that responds to the non-AP MLD request to complete the scene information synchronization from the current AP MLD to the target AP MLD; the SAcontext element carries the scene information of the AP MLD corresponding to the security association mechanism that responds to the non-AP MLD request to complete the scene information synchronization from the current AP MLD to the target AP MLD, thereby providing feedback on the synchronization result.

[0311] (4) Non-AP MLD reassociation with target AP MLD in mobile domain AP MLD scenario The Non-AP MLD sends an association request frame or a reassociation request frame to the target AP MLD (FTR), and then the target AP MLD (FTR) sends an association response frame or a reassociation response frame back to the Non-AP MLD. Successful reassociation will only occur if the time between the transmission of the FT request frame and the transmission of the reassociation request frame does not exceed the reassociation deadline.

[0312] like Figure 25 As shown, it includes: S2551, Non-AP MLD sends an association request frame or reassociation request frame to the target AP MLD (FTR).

[0313] Among them, the association request frame or reassociation request frame is (Re)Association Request (MDE(FTinMobileDomainMLD, MobileDomainMLD Info), Basic Multi-Link element); S2552, the target AP MLD (FTR) sends an associated response frame or a reassociated response frame back to the Non-AP MLD.

[0314] Among them, the associated response frame or re-associated response frame is (Re)Association Response (MDE(FTinMobileDomainMLD, MobileDomainMLD Info), Basic Multi-Link element).

[0315] The association request frame or reassociation request frame carries an updated MDE (FTinMobileDomainMLD, MobileDomainMLD Info 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 attached to the mobile domain AP MLD), and indicating support for fast switching between two AP MLDs attached to the same mobile domain AP MLD.

[0316] In this context, the so-called non-AP MLD associated with an AP MLD in a mobile domain AP MLD scenario (or non-AP MLD associated with an AP MLD attached to a mobile domain AP MLD) refers to establishing a mapping relationship between an AP MLD attached to a mobile domain AP MLD and a non-AP MLD (including the mapping relationship between mobile domain AP MLDs and AP MLDs, as well as the mapping relationship between the AP MLD and the non-AP MLD), enabling the non-AP MLD to invoke DSSs. Specifically, a security association (such as PMKSA, PTKSA) is established between the non-AP MLD and the mobile domain AP MLD. When the non-AP MLD transitions from the current AP MLD attached to the mobile domain AP MLD to the target AP MLD attached to the mobile domain AP MLD in a mobile domain AP MLD scenario, PMKSA and PTKSA remain unchanged. That is, when the non-AP MLD transitions from the current AP MLD attached to the mobile domain AP MLD to the target AP MLD attached to the mobile domain AP MLD in a mobile domain AP MLD scenario, it maintains a unicast key, including maintaining the same paired master key (PMK) and the same paired temporary key (PTK).

[0317] While current Fast BSS Transition (FT) can reduce the duration of connectivity loss between STA and DS, or between non-AP MLD and DS, during BSS transition, it cannot maintain data continuity between STA and DS, or between non-AP MLD and DS, because the transition from STA (or Non-AP MLD) to target AP (or target AP MLD) requires re-association and re-establishment of data transmission and reception protocols and scenarios. 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) under a mobile domain AP MLD architecture. By optimizing the FT protocol and utilizing the replication, migration, or updating of relevant communication scenarios and states, data continuity between STA and DS, or between non-AP MLD and DS, is maintained.

[0318] In the embodiments of this application, Figure 25 In the illustrated embodiment, the current AP MLD and the target AP MLD belong to the same mobile domain AP MLD. Figure 25 The Transition (FT) mechanism shown also applies to the transition from the current AP MLD to the target AP MLD when the current AP MLD and the target AP MLD are attached to different mobile domain AP MLDs. The difference is that when the current AP MLD and the target AP MLD are attached to the same mobile domain AP MLD, the second data is synchronized between different attached AP MLDs of the same mobile domain AP MLD. If the current AP MLD and the target AP MLD are attached to different mobile domain AP MLDs, the second data is synchronized between the attached AP MLDs of the different mobile domain AP MLDs.

[0319] It should be noted that the above embodiments illustrate the conversion (FT) mechanism from the current AP MLD to the target AP MLD in the mobile domain AP MLD scenario for non-AP MLDs. The wireless communication method provided in this application is also applicable to the conversion (FT) mechanism from the current AP to the target AP in the mobile domain AP MLD scenario for non-MLD sites.

[0320] While current FT (Flexible Transmission) methods can reduce the duration of connectivity loss between STA and DS, or between non-AP MLD and DS, during BSS transitions, the transition from STA (or Non-AP MLD) to target AP (or target AP MLD) requires re-association and re-establishment of data transmission protocols and scenarios, thus failing to maintain data continuity between STA and DS, or between non-AP MLD and DS. The wireless communication method provided in this application, based on a mobile domain AP MLD architecture, for a non-AP MLD (or STA) transitioning from the current AP MLD (or AP) to the target AP MLD (or AP), maintains data continuity between STA and DS, or between non-AP MLD and DS, by optimizing the FT protocol and utilizing the replication, migration, or updating of relevant communication scenarios and states.

[0321] The wireless communication method provided in the embodiments of this application is as follows: 1. A high-level architecture is proposed for mobile domain AP MLD and its affiliated AP MLD and Non-APMLD based on the mobile domain AP MLD architecture for data connectivity-oriented non-AP MLD (or STA) to quickly switch from the current AP MLD (or AP) to the target AP MLD (or AP). 2. For non-AP MLDs (or STAs) with data connectivity to quickly switch from the current AP MLD (or AP) to the target AP MLD (or AP), communication scenarios and state-related elements or fields are defined, mainly including block acknowledgment scenarios or state elements and security-related scenarios or state elements, which are used for copying, migrating or updating block acknowledgment and security-related scenarios and states during the FT process; 2. This paper proposes frame type and format definitions and function updates for FT protocols and interactions based on the mobile domain AP MLD architecture, which are geared towards data connectivity. These updates include: definitions of Mobile Domain Elements (MDEs), association and reassociation protocols, association frames, and reassociation frames; FT request and response protocols, FT resource request and response protocols, and frame definitions such as FT Request, FT Response, FT Confirm, and FT ACK.

[0322] The preferred embodiments of this application have been described in detail above with reference to the accompanying drawings. However, this application is not limited to the specific details of the above embodiments. Within the scope of the technical concept of this application, various simple modifications can be made to the technical solutions of this application, and these simple modifications all fall within the protection scope of this application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner without contradiction. To avoid unnecessary repetition, this application will not describe the various possible combinations separately. Furthermore, various different embodiments of this application can also be arbitrarily combined, as long as they do not violate the spirit of this application, they should also be considered as the content disclosed in this application. Moreover, without conflict, the various embodiments and / or the technical features in the various embodiments described in this application can be arbitrarily combined with the prior art, and the resulting technical solutions should also fall within the protection scope of this application.

[0323] It should also be understood that in the various method embodiments of this application, the sequence number of each process does not imply 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 this application. Furthermore, in the embodiments of this application, the terms "downlink," "uplink," and "sidelink" are used to indicate the transmission direction of signals or data. "Downlink" indicates that the transmission direction of signals or data is a first direction from the site to the user equipment in the cell; "uplink" indicates that the transmission direction of signals or data is a second direction from the user equipment in the cell to the site; and "sidelink" indicates that the transmission direction of signals or data is a third direction from user equipment 1 to user equipment 2. For example, "downlink signal" indicates that the transmission direction of the signal is the first direction. Additionally, in the embodiments of this application, the term "and / or" is merely a description of the association relationship between related objects, indicating that three relationships can exist. Specifically, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0324] Figure 26 This is a schematic diagram of the structural composition of the non-access point multi-link device provided in the embodiments of this application, as shown below. Figure 26 As shown, the non-access point multi-link device 2600 includes: The first communication unit 2601 is configured to receive or send a first frame. 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 third access point multi-link device, which is a logical access point multi-link device.

[0325] Understandably, non-access point multi-link devices also include a processing unit and a storage unit. The processing unit is configured to parse or generate the first frame, and the storage unit is configured to store the information carried by the first frame.

[0326] In some embodiments, the first access point multi-link device is an access point multi-link device in which the associated access points (APs) are located in the same location; the second access point multi-link device is an access point multi-link device in which the associated APs are located in the same location.

[0327] In some embodiments, the third access point multilink device is used for at least one of the following: Provide connection services between the non-access point multilink device or the auxiliary access point multilink device and the distributed system DS; Maintain the 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; The authentication and / or association or reassociation of the non-access point multi-link device; The security association of the non-access point multi-link devices; The distribution of all or part of the security association information of the non-access point multi-link device; Synchronization of all or part of the status and / or buffer information of the upper-layer MAC of the auxiliary access point multi-link device; Manages the distribution of authentication information for links in non-access point multi-link devices; Manage the association or re-association at the subordinate access point multilink device level between the non-access point multilink device and the subordinate access point multilink device; For the target access point multilink device that establishes a multilink with the non-access point multilink device in at least one affiliated access point multilink device, the MAC address corresponding to the target access point multilink device is selected for transmission; The first data is synchronized between different affiliated access point multilink devices, and the first data is used to maintain the data continuity of communication between the non-access point multilink device and the affiliated access point multilink device or DS. MLD-level information is exchanged or indicated through the MAC sublayer of the auxiliary access point multi-link device.

[0328] In some embodiments, the first access point multi-link device and the second access point multi-link device belong to the same mobile domain (MD) within the same extended service set, and the third access point multi-link device is an MD AP MLD.

[0329] In some embodiments, the first frame includes first information, which includes at least one of the following: First indication information, the first indication information is used to indicate whether the non-access point multilink device supports or is allowed to switch between two auxiliary access point multilink devices in the same MD AP MLD; The second indication information is used to indicate the third access point multi-link device.

[0330] In some embodiments, the first frame includes at least one of the following: A first conversion frame is used to initiate the non-access point multi-link device to switch from the first access point multi-link device to the second access point multi-link device; The second conversion frame is used by the first access point multi-link device to synchronize second data to the second access point multi-link device. The second data is used to maintain the 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 is converted to the second access point multi-link device. The third conversion frame is used to associate or reassociate the non-access point multilink device with the second access point multilink device.

[0331] In some embodiments, the first conversion frame includes at least one of the following: A conversion request frame sent from the non-access point multi-link device to the second access point multi-link device, the conversion request frame being used to request a conversion from the first access point multi-link device to the second access point multi-link device; A conversion response frame sent from the second access point multilink device to the non-access point multilink device, the conversion response frame being used to respond to the conversion request frame.

[0332] In some embodiments, 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 with the second access point multi-link device; A first conversion response frame sent from the first access point multilink device to the non-access point multilink device, the first conversion response frame being used to feedback the synchronization status of the second data.

[0333] In some embodiments, the first conversion confirmation frame carries third data of the non-access point multi-link device, the third data being 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 being used by the first access point multi-link device to determine the second data.

[0334] In some embodiments, the third conversion frame includes at least one of the following: An association request frame or reassociation request frame sent by the non-access point multilink device to the second access point multilink device; The associated response frame or reassociation response frame sent by the second access point multilink device to the non-access point multilink device.

[0335] In some embodiments, the second data includes at least one of the following: The second information is the block acknowledgment protocol scenario information of the first access point multi-link device; The third information is the security association scenario information of the multi-link device of the first access point.

[0336] In some embodiments, the second conversion frame includes a block confirmation protocol scenario element, which is used to indicate information about the block confirmation protocol scenario.

[0337] In some embodiments, the block confirmation protocol scenario element includes a block confirmation protocol scenario parameter control field, which is used to indicate at least one of the following: The device in which 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 described by the block confirmation protocol scenario element is the same device; When the peer device targeted by the block confirmation protocol scenario described by the block confirmation protocol scenario element is the same device, the peer device targeted by the block confirmation protocol scenario is the same device. The number of block confirmation protocol scenario parameter sets included in the block confirmation protocol scenario element.

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

[0339] In some embodiments, 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; The corresponding block confirmation protocol scenario targets the peer device; Block confirmation parameter set; Block confirmation timeout value.

[0340] In some embodiments, if the block confirmation protocol scenario parameter set subfield is used to indicate that 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 start sequence number; Send window size.

[0341] In some embodiments, if the block confirmation protocol scenario parameter set subfield is used to indicate that the device in the corresponding block confirmation protocol scenario plays the role of 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 start 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.

[0342] In some embodiments, 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 identifier; Buffer size.

[0343] In some embodiments, the second conversion frame includes a security-associated scene element, which is used to indicate information about a security-associated scene.

[0344] In some embodiments, the security-associated scenario element includes a security-associated scenario parameter control field, which 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 peer device targeted by the security association scenario described by the security association scenario element is the same device; When the peer device targeted by the security association scenario described by the security association scenario element is the same device, the peer device targeted by the security association scenario is the same device. The number of security association scenario parameter sets included in the security association scenario element.

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

[0346] In some embodiments, the security-associated scenario parameter set subdomain is used to indicate at least one of the following: The role of the device in the corresponding security association scenario; The corresponding security-related scenarios target the peer devices; The corresponding security association types for security association scenarios.

[0347] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the device in the corresponding security association scenario plays the role of a receiver in the security association scenario; the security association scenario parameter set subfield is also used to indicate at least one of the following: Number of replay counters; TID; The count of the replay counter for the TID.

[0348] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the device in the corresponding security association scenario plays the role of 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: Package number counter count; TID; The counting of the package number counter for the TID.

[0349] In some embodiments, the second conversion frame further includes at least one of the following: The fourth indication information is used to indicate that the second data includes information on block confirmation protocol scenarios and / or security association scenarios.

[0350] In some embodiments, the first communication unit 2601 is further configured to: Receive or send a second frame, the second frame being used for the non-access point multilink device to associate or reassociate with the first access point multilink device.

[0351] In some embodiments, the second frame includes first information, which includes at least one of the following: First indication information, the first indication information is used to indicate whether the non-access point multilink device supports or is allowed to switch between two auxiliary access point multilink devices in the same MD AP MLD; The second indication information is used to indicate the third access point multi-link device.

[0352] In some embodiments, the first information is located in the Mobile Domain Element (MDE).

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

[0354] In some embodiments, 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.

[0355] Figure 27 This is a schematic diagram of the structural composition of the access point multi-link device provided in the embodiments of this application, as shown below. Figure 27 As shown, the access point multi-link device 2700 includes: The second communication unit 2701 is configured to send or receive a first frame. 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 a third access point multi-link device. The third access point multi-link device is a logical access point multi-link device. The access point multi-link device is either the first access point multi-link device or the second access point multi-link device.

[0356] Understandably, the access point multi-link device also includes a processing unit and a storage unit. The processing unit is configured to parse or generate the first frame, and the storage unit is configured to store the information carried by the first frame.

[0357] In some embodiments, the first access point multi-link device is an access point multi-link device in which the associated access points (APs) are located in the same location; the second access point multi-link device is an access point multi-link device in which the associated APs are located in the same location.

[0358] In some embodiments, the third access point multilink device is used for at least one of the following: Provide connection services between the non-access point multilink device or the auxiliary access point multilink device and the distributed system DS; Maintain the 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; The authentication and / or association or reassociation of the non-access point multi-link device; The security association of the non-access point multi-link devices; The distribution of all or part of the security association information of the non-access point multi-link device; Synchronization of all or part of the status and / or buffer information of the upper-layer MAC of the auxiliary access point multi-link device; Manages the distribution of authentication information for links in non-access point multi-link devices; Manage the association or re-association at the subordinate access point multilink device level between the non-access point multilink device and the subordinate access point multilink device; For the target access point multilink device that establishes a multilink with the non-access point multilink device in at least one affiliated access point multilink device, the MAC address corresponding to the target access point multilink device is selected for transmission; The first data is synchronized between different affiliated access point multilink devices, and the first data is used to maintain the data continuity of communication between the non-access point multilink device and the affiliated access point multilink device or DS. MLD-level information is exchanged or indicated through the MAC sublayer of the auxiliary access point multi-link device.

[0359] In some embodiments, the first access point multi-link device and the second access point multi-link device belong to the same mobile domain (MD) within the same extended service set, and the third access point multi-link device is an MD AP MLD.

[0360] In some embodiments, the first frame includes first information, which includes at least one of the following: First indication information, the first indication information is used to indicate whether the non-access point multilink device supports or is allowed to switch between two auxiliary access point multilink devices in the same MD AP MLD; The second indication information is used to indicate the third access point multi-link device.

[0361] In some embodiments, the first frame includes at least one of the following: A first conversion frame is used to initiate the non-access point multi-link device to switch from the first access point multi-link device to the second access point multi-link device; The second conversion frame is used by the first access point multi-link device to synchronize second data to the second access point multi-link device. The second data is used to maintain the 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 is converted to the second access point multi-link device. The third conversion frame is used to associate or reassociate the non-access point multilink device with the second access point multilink device.

[0362] In some embodiments, the first conversion frame includes at least one of the following: A conversion request frame sent from the non-access point multi-link device to the second access point multi-link device, the conversion request frame being used to request a conversion from the first access point multi-link device to the second access point multi-link device; A conversion response frame sent from the second access point multilink device to the non-access point multilink device, the conversion response frame being used to respond to the conversion request frame.

[0363] In some embodiments, 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; The first access point multi-link device sends a second conversion confirmation frame to the second access point multi-link device. The second conversion confirmation frame is used by the first access point multi-link device to synchronize the second data with the second access point multi-link device. A first conversion response frame sent from the first access point multilink device to the non-access point multilink device, the first conversion response frame being used to feed back the synchronization status of the second data to the non-access point multilink device; A second conversion response frame is sent from the second access point multilink device to the first access point multilink device. The second conversion response frame is used to feed back the synchronization status of the second data to the first access point multilink device.

[0364] In some embodiments, the first conversion confirmation frame carries third data of the non-access point multi-link device, the third data being 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 being used by the first access point multi-link device to determine the second data.

[0365] In some embodiments, the third conversion frame includes at least one of the following: An association request frame or reassociation request frame sent by the non-access point multilink device to the second access point multilink device; The associated response frame or reassociation response frame sent by the second access point multilink device to the non-access point multilink device.

[0366] In some embodiments, the second data includes at least one of the following: The second information is the block acknowledgment protocol scenario information of the first access point multi-link device; The third information is the security association scenario information of the multi-link device of the first access point.

[0367] In some embodiments, the second conversion frame includes a block confirmation protocol scenario element, which is used to indicate information about the block confirmation protocol scenario.

[0368] In some embodiments, the block confirmation protocol scenario element includes a block confirmation protocol scenario parameter control field, which is used to indicate at least one of the following: The device in which 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 described by the block confirmation protocol scenario element is the same device; When the peer device targeted by the block confirmation protocol scenario described by the block confirmation protocol scenario element is the same device, the peer device targeted by the block confirmation protocol scenario is the same device. The number of block confirmation protocol scenario parameter sets included in the block confirmation protocol scenario element.

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

[0370] In some embodiments, 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; The corresponding block confirmation protocol scenario targets the peer device; Block confirmation parameter set; Block confirmation timeout value.

[0371] In some embodiments, if the block confirmation protocol scenario parameter set subfield is used to indicate that 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 start sequence number; Send window size.

[0372] In some embodiments, if the block confirmation protocol scenario parameter set subfield is used to indicate that the device in the corresponding block confirmation protocol scenario plays the role of 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 start 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.

[0373] In some embodiments, 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 identifier; Buffer size.

[0374] In some embodiments, the second conversion frame includes a security-associated scene element, which is used to indicate information about a security-associated scene.

[0375] In some embodiments, the security-associated scenario element includes a security-associated scenario parameter control field, which 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 peer device targeted by the security association scenario described by the security association scenario element is the same device; When the peer device targeted by the security association scenario described by the security association scenario element is the same device, the peer device targeted by the security association scenario is the same device. The number of security association scenario parameter sets included in the security association scenario element.

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

[0377] In some embodiments, the security-associated scenario parameter set subdomain is used to indicate at least one of the following: The role of the device in the corresponding security association scenario; The corresponding security-related scenarios target the peer devices; The corresponding security association types for security association scenarios.

[0378] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the device in the corresponding security association scenario plays the role of a receiver in the security association scenario; the security association scenario parameter set subfield is also used to indicate at least one of the following: Number of replay counters; TID; The count of the replay counter for the TID.

[0379] In some embodiments, if the security association scenario parameter set subfield is used to indicate that the device in the corresponding security association scenario plays the role of 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: Package number counter count; TID; The counting of the package number counter for the TID.

[0380] In some embodiments, the second conversion frame further includes at least one of the following: The fourth indication information is used to indicate that the second data includes information on block confirmation protocol scenarios and / or security association scenarios.

[0381] 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 as follows: Send or receive a second frame, which is used for the non-access point multilink device to associate or reassociate with the first access point multilink device.

[0382] In some embodiments, the second frame includes first information, which includes at least one of the following: First indication information, the first indication information is used to indicate whether the non-access point multilink device supports or is allowed to switch between two auxiliary access point multilink devices in the same MD AP MLD; The second indication information is used to indicate the third access point multi-link device.

[0383] In some embodiments, the first information is located in the Mobile Domain Element (MDE).

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

[0385] In some embodiments, 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.

[0386] Those skilled in the art should understand that the descriptions of the non-access point multi-link devices or access point multi-link devices in the embodiments of this application can be understood with reference to the descriptions of the wireless communication methods in the embodiments of this application.

[0387] Figure 28 This is a schematic structural diagram of a communication device 2800 provided in an embodiment of this application. The communication device can be a non-access point multi-link device or an access point multi-link device. Figure 28 The communication device 2800 shown includes a processor 2810, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0388] Optionally, such as Figure 28 As shown, the communication device 2800 may further include a memory 2820. The processor 2810 can retrieve and run computer programs from the memory 2820 to implement the methods described in this embodiment.

[0389] The memory 2820 can be a separate device independent of the processor 2810, or it can be integrated into the processor 2810.

[0390] Optionally, such as Figure 28 As shown, the communication device 2800 may also include a transceiver 2830, and the processor 2810 may control the transceiver 2830 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

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

[0392] Optionally, the communication device 2800 may specifically be a non-access point multi-link device in the embodiments of this application, and the communication device 2800 may implement the corresponding processes implemented by the non-access point multi-link device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0393] Optionally, the communication device 2800 may specifically be an access point multilink device in the embodiments of this application, and the communication device 2800 may implement the corresponding processes implemented by the access point multilink device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0394] Figure 29 This is a schematic structural diagram of the chip according to an embodiment of this application. Figure 29The chip 2900 shown includes a processor 2910, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0395] Optionally, such as Figure 29 As shown, chip 2900 may further include memory 2920. Processor 2910 can retrieve and run computer programs from memory 2920 to implement the methods described in this embodiment.

[0396] The memory 2920 can be a separate device independent of the processor 2910, or it can be integrated into the processor 2910.

[0397] Optionally, the chip 2900 may also include an input interface 2930. The processor 2910 can control the input interface 2930 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

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

[0399] Optionally, the chip can be applied to the non-access point multilink device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the non-access point multilink device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0400] Optionally, the chip can be applied to the access point multilink device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the access point multilink device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0401] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0402] Figure 30 This is a schematic block diagram of a communication system 3000 provided in an embodiment of this application. Figure 30 As shown, the communication system 3000 includes a non-access point multi-link device 3010 and an access point multi-link device 3020. The non-access point multi-link device 3010 can be a site accessing the access point multi-link device 3020: a Non-AP MLD or a Non-AP STA.

[0403] 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, and for the sake of simplicity, it will not be described in detail here. 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, and for the sake of simplicity, it will not be described in detail here.

[0404] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above 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. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0405] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0406] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this 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 memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0407] This application also provides a computer-readable storage medium for storing computer programs.

[0408] Optionally, the computer-readable storage medium can be applied to the non-access point multilink device in the embodiments of this application, and the execution of the computer program causes the computer to execute the corresponding processes implemented by the non-access point multilink device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0409] Optionally, the computer-readable storage medium can be applied to the access point multilink device in the embodiments of this application, and the execution of the computer program causes the computer to execute the corresponding processes implemented by the access point multilink device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0410] This application also provides a computer program product, including computer program instructions.

[0411] Optionally, the computer program product can be applied to the non-access point multilink device in the embodiments of this application, and the execution of the computer program instructions causes the computer to execute the corresponding processes implemented by the non-access point multilink device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0412] Optionally, the computer program product can be applied to the access point multilink device in the embodiments of this application, and the execution of the computer program instructions causes the computer to execute the corresponding processes implemented by the access point multilink device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0413] This application also provides a computer program.

[0414] Optionally, the computer program can be applied to the non-access point multilink device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the non-access point multilink device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0415] Optionally, the computer program can be applied to the access point multilink device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the access point multilink device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0416] Those skilled in the art will recognize that the units and algorithm steps of the various examples 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 implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.

[0417] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0418] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0419] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0420] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0421] If the aforementioned functions are implemented as 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 this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0422] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A wireless communication method, the method comprising: The non-access point multi-link device receives or sends a first frame, which 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 logical access point multi-link device.

2. The method according to claim 1, wherein, The logical access point multi-link device is used for at least one of the following: Provide connection services between the non-access point multilink device or the auxiliary access point multilink device and the distributed system DS; Maintain the 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; The authentication and / or association or reassociation of the non-access point multi-link device; The security association of the non-access point multi-link devices; The distribution of all or part of the security association information of the non-access point multi-link device; Synchronization of all or part of the status and / or buffer information of the upper-layer MAC of the auxiliary access point multi-link device; Manage the distribution of authentication information for the links of the non-access point multi-link devices; Manage the association or re-association at the subordinate access point multilink device level between the non-access point multilink device and the subordinate access point multilink device; For the target access point multilink device that establishes a multilink with the non-access point multilink device in at least one affiliated access point multilink device, the MAC address corresponding to the target access point multilink device is selected for transmission; The first data is synchronized between different affiliated access point multilink devices, and the first data is used to maintain the data continuity of communication between the non-access point multilink device and the affiliated access point multilink device or DS. MLD-level information is exchanged or indicated through the MAC sublayer of the auxiliary access point multi-link device.

3. The method according to claim 1 or 2, wherein, The first access point multi-link device and the second access point multi-link device belong to the same mobile domain (MD) within the same extended service set, and the logical access point multi-link device is an MDAP MLD.

4. The method according to claim 1 or 2, wherein, The first frame includes at least one of the following: A first conversion frame is used to initiate the non-access point multi-link device to switch from the first access point multi-link device to the second access point multi-link device; The second conversion frame is used by the first access point multi-link device to synchronize second data to the second access point multi-link device. The second data is used to maintain the data communication between the non-access point multi-link device and the first access point multi-link device or the logical access point multi-link device, so as to maintain the sustainability of data communication after the non-access point multi-link device is converted to the second access point multi-link device. The third conversion frame is used to associate or reassociate the non-access point multilink device with the second access point multilink device.

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

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

7. The method according to claim 6, wherein, The second conversion frame includes a block confirmation protocol scenario element, which is used to indicate information about the block confirmation protocol scenario.

8. The method according to claim 7, wherein, The block confirmation protocol scenario element includes a block confirmation protocol scenario parameter set list field, which includes at least one block confirmation protocol scenario parameter set subfield, and one of the block confirmation protocol scenario parameter set subfields is used to indicate a block confirmation protocol scenario parameter set.

9. The method according to claim 8, 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; The corresponding block confirmation protocol scenario targets the peer device; Block confirmation parameter set; Block confirmation timeout value.

10. The method according to claim 9, wherein, If the block confirmation protocol scenario parameter set subfield is used to indicate that 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 start sequence number; Send window size.

11. The method according to claim 9 or 10, 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 identifier; Buffer size.

12. A non-access point multi-link device, comprising: A processor and a memory for storing a computer program, the processor for calling and running the computer program stored in the memory, causing the non-access point multilink device to perform the method as described in any one of claims 1 to 11.

Images