Communication methods and communication devices

Abstract

Provided are communication methods and communication devices. A communication method comprises: a first AP MLD communicating with a first non-AP MLD, wherein the first AP MLD comprises a first affiliated AP and a second affiliated AP, the first affiliated AP corresponding to a millimeter-wave link of the first AP MLD, and the second affiliated AP corresponding to a non-millimeter-wave link of the first AP MLD, and the first non-AP MLD comprises a first affiliated non-AP STA and a second affiliated non-AP STA, the first affiliated non-AP STA corresponding to a millimeter-wave link of the first non-AP MLD, and the second affiliated non-AP STA corresponding to a non-millimeter-wave link of the first non-AP MLD.

Description

Communication methods and communication equipment Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Technology

[0002] To reduce equipment costs and simplify implementation, millimeter-wave links can be integrated into multi-link devices (MLDs). In this scenario, the communication between non-access point MLDs (non-AP MLDs) and access point MLDs (AP MLDs) (e.g., time synchronization, link discovery, link establishment, link management) becomes a problem that needs to be solved. Summary of the Invention

[0003] This application provides a communication method and a communication device. The various aspects covered by this application are described below.

[0004] In a first aspect, a communication method is provided, comprising: a first AP MLD communicating with a first non-AP MLD, the first AP MLD including a first auxiliary AP and a second auxiliary AP, the first auxiliary AP corresponding to a millimeter-wave link of the first AP MLD, the second auxiliary AP corresponding to a non-millimeter-wave link of the first AP MLD, the first non-AP MLD including a first auxiliary non-AP STA and a second auxiliary non-AP STA, the first auxiliary non-AP STA corresponding to a millimeter-wave link of the first non-AP MLD, and the second auxiliary non-AP STA corresponding to a non-millimeter-wave link of the first non-AP MLD.

[0005] In a second aspect, a communication method is provided, comprising: a first non-AP MLD communicating with a first AP MLD, the first AP MLD including a first auxiliary AP and a second auxiliary AP, the first auxiliary AP corresponding to a millimeter-wave link of the first AP MLD, the second auxiliary AP corresponding to a non-millimeter-wave link of the first AP MLD, the first non-AP MLD including a first auxiliary non-AP STA and a second auxiliary non-AP STA, the first auxiliary non-AP STA corresponding to a millimeter-wave link of the first non-AP MLD, and the second auxiliary non-AP STA corresponding to a non-millimeter-wave link of the first non-AP MLD.

[0006] Thirdly, a communication device is provided, the communication device being a first AP MLD, the communication device comprising: a communication module for communicating with the first non-AP MLD, the first AP MLD including a first auxiliary AP and a second auxiliary AP, the first auxiliary AP corresponding to a millimeter-wave link of the first AP MLD, the second auxiliary AP corresponding to a non-millimeter-wave link of the first AP MLD, the first non-AP MLD including a first auxiliary non-AP STA and a second auxiliary non-AP STA, the first auxiliary non-AP STA corresponding to a millimeter-wave link of the first non-AP MLD, and the second auxiliary non-AP STA corresponding to a non-millimeter-wave link of the first non-AP MLD.

[0007] Fourthly, a communication device is provided, the communication device being a first non-AP MLD, the communication device comprising: a communication device for communicating with the first AP MLD, the first AP MLD including a first auxiliary AP and a second auxiliary AP, the first auxiliary AP corresponding to a millimeter-wave link of the first AP MLD, the second auxiliary AP corresponding to a non-millimeter-wave link of the first AP MLD, the first non-AP MLD including a first auxiliary non-AP STA and a second auxiliary non-AP STA, the first auxiliary non-AP STA corresponding to a millimeter-wave link of the first non-AP MLD, and the second auxiliary non-AP STA corresponding to a non-millimeter-wave link of the first non-AP MLD.

[0008] Fifthly, a communication device is provided, including a processor and a memory, the memory for storing one or more computer programs, the processor for calling the computer programs in the memory to enable some or all of the steps of the methods described in the preceding aspects of the communication device.

[0009] Sixthly, embodiments of this application provide a communication system that includes the aforementioned communication device. In another possible design, the system may further include other devices that interact with the communication device as described in the embodiments of this application.

[0010] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing a computer program that causes a communication device to perform some or all of the steps in the methods described above.

[0011] Eighthly, embodiments of this application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program operable to cause a communication device to perform some or all of the steps of the methods described in the foregoing aspects. In some implementations, the computer program product may be a software installation package.

[0012] Ninthly, embodiments of this application provide a chip including a memory and a processor, the processor being able to call and run a computer program from the memory to implement some or all of the steps described in the methods of the foregoing aspects. Attached Figure Description

[0013] Figure 1 is a system architecture example diagram of a wireless communication system applicable to the embodiments of this application.

[0014] Figure 2 is an example of the active scanning process of a non-directional multi-gigabit (DMG) site.

[0015] Figure 3 is another example of the process of active scanning at a non-DMG site.

[0016] Figure 4 is an example diagram of a probe request for a single address.

[0017] Figure 5 is an example diagram of possible frame switching sequences during multilink operation discovery and multilink establishment.

[0018] Figure 6 is an example diagram of the multi-link establishment process.

[0019] Figure 7 is an example of a probe request frame in a non-multilink probe request.

[0020] Figure 8 is an example of a multi-link probe request frame.

[0021] Figure 9 is an example of an authentication frame.

[0022] Figure 10 is an example diagram of a (re)association request frame.

[0023] Figure 11 is an example diagram of basic multilink elements in an association request frame.

[0024] Figure 12 is an example diagram of the capability information field in a beacon frame.

[0025] Figure 13 is an example diagram of a critical update operation.

[0026] Figure 14 is an example diagram of an AP carrying a silence element to emit a silence signal on another link.

[0027] Figure 15 is an example diagram of an AP carrying channel switching announcement elements to send a channel switching signal on another link.

[0028] Figure 16 is an example diagram of the AP attached to the AP MLD.

[0029] Figure 17 is an example diagram of the group address buffer unit (BU) indication sent by the AP attached to the AP MLD.

[0030] Figure 18 is a flowchart illustrating the communication method provided in an embodiment of this application.

[0031] Figure 19 is an example diagram of the first co-located AP MLD provided in an embodiment of this application.

[0032] Figure 20 is an example diagram of a first non-co-located AP MLD provided in an embodiment of this application.

[0033] Figure 21 is an example diagram of a first non-co-located AP MLD provided in another embodiment of this application.

[0034] Figure 22 is an example diagram of a beacon frame provided in an embodiment of this application.

[0035] Figure 23 is an example diagram of the transmit sector and / or beam information field provided in an embodiment of this application.

[0036] Figure 24 is an example diagram of the detection response frame provided in an embodiment of this application.

[0037] Figure 25 is an example diagram of the neighbor report element provided in an embodiment of this application.

[0038] Figure 26 is an example diagram of how the reserved bits in the basic service set identifier field of the neighbor report element indicate the second indication information according to an embodiment of this application.

[0039] Figure 27 is an example diagram of the per-site configuration fields provided in the embodiments of this application.

[0040] Figure 28 is an example diagram of the reserved bit in the capability information field indicating the third indication information provided in the embodiments of this application.

[0041] Figure 29 is a schematic diagram of the structure of a communication device provided in an embodiment of this application.

[0042] Figure 30 is a schematic diagram of the structure of a communication device provided in another embodiment of this application.

[0043] Figure 31 is a schematic structural diagram of the communication device provided in an embodiment of this application. Detailed Implementation

[0044] Communication system architecture

[0045] The technical solutions of this application can be applied to various communication systems, such as wireless local area networks (WLAN), wireless fidelity (WiFi), high-performance radio local area networks (HIPELAN), wide area networks (WAN), cellular networks, or other communication systems. For example, the technical solutions provided in this application can be applied to communication systems using the 802.11 standard. Exemplarily, the 802.11 standard includes, but is not limited to, the 802.11ax standard, the 802.11be standard, the 802.11bn standard, and the next-generation 802.11 standard (post802.11bn).

[0046] Figure 1 shows a schematic diagram of a communication system applicable to an embodiment of this application. Referring to Figure 1, the communication devices in the communication system 100 may include access points (APs) 111 and 112, as well as stations (STAs) 121 and 122. STA 121 can access the network through AP 111, and STA 122 can access the network through AP 112.

[0047] In some implementations, a STA can establish an association with one or more APs, after which the associated STAs and APs can communicate with each other. As shown in Figure 1, AP 111 and STA 121 can communicate after establishing an association, and AP 112 and STA 122 can communicate after establishing an association.

[0048] In some implementations, the communication in the communication system 100 can be communication between an AP and a non-AP STA, communication between two non-AP STAs, or communication between a STA and a peer STA. Here, a peer STA can refer to a device that communicates with the STA's counterpart. For example, a peer STA may be an AP or a non-AP STA.

[0049] It should be understood that Figure 1 exemplarily shows two AP STAs and two non-AP STAs. The communication system 100 may also include more AP STAs, or the communication system 100 may include other numbers of non-AP STAs. This application embodiment does not limit this.

[0050] In addition, the above-mentioned communication system can be applied to scenarios involving multi-device collaboration, such as multi-AP (multi-access points) collaboration or multi-site collaboration.

[0051] In the embodiments of this application, the names of AP and / or STA are not limited. In some scenarios, AP can also be called AP STA, that is, in a sense, AP is also a type of STA. In other scenarios, STA can be called non-AP STA.

[0052] In some scenarios, the aforementioned communication device can also be called an "MLD," meaning a device that can communicate through multiple communication links. These multiple communication links can include communication links in different frequency bands, such as millimeter-wave bands and / or low-frequency bands. Typically, if the multi-link device is an AP, then the AP can also be called an "AP MLD." If the multi-link device is a non-AP STA, then the non-AP STA can also be called a "non-AP MLD."

[0053] In this application embodiment, the AP can be a device in a wireless network. The AP can be a communication server, router, switch, bridge, or other communication entity. Alternatively, the AP can include various forms of macro base stations, micro base stations, relay stations, etc. Of course, the AP can also be a chip, circuit, or processing system within these various forms of devices, thereby implementing the methods and functions of this application embodiment. APs can be applied in various scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air quality monitoring nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, audio equipment, refrigerators, washing machines, etc.), nodes in the Internet of Things (IoT), entertainment terminals (e.g., AR, VR, and other wearable devices), smart devices in smart offices (e.g., printers, projectors, etc.), vehicle-to-everything (V2X) devices, and some infrastructure in daily life scenarios (e.g., vending machines, supermarket self-service navigation kiosks, self-service checkout machines, self-service ordering machines, etc.).

[0054] In some implementations, the role of the STA in the communication system is not absolute; in some scenarios, the STA can act as an AP. For example, in a scenario where a mobile phone connects to a router, the mobile phone can be a non-AP STA, while when the mobile phone acts as a hotspot for other mobile phones, it takes on the role of an AP.

[0055] In the embodiments of this application, the STA can be a device with wireless transceiver capabilities, such as one that supports the 802.11 series of protocols and can communicate with the AP or other STAs. For example, an STA is any user communication device that allows users to communicate with the AP and thus with the WLAN. STAs include, for example, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0056] In this application embodiment, the STA can also be a device that provides voice / data / image connectivity to the user, such as a handheld device, vehicle device, home device, home appliance, gaming device, etc., with wireless connection function or equipped with a wireless communication module. Examples include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, drones or aerial photography equipment, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, 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 5G networks, or future evolution of public land mobile communication networks. Terminal devices in a network (PLMN) can also be televisions, refrigerators, washing machines, kitchen appliances, door locks, fish tanks, robot vacuum cleaners, game consoles, cameras / camcorders, etc. with wireless connectivity, but this application embodiment is not limited to these.

[0057] By way of example and not limitation, in this embodiment, the STA 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. Examples include smartwatches or smart glasses, as well as devices that focus on a specific type of application function and require cooperation with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0058] Furthermore, in this embodiment, the STA can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network for human-machine interconnection and object-to-object interconnection. In this embodiment, IoT technology can achieve massive connectivity, deep coverage, and low terminal power consumption through technologies such as narrowband (NB).

[0059] Furthermore, in this embodiment, the STA can be a device in a vehicle-to-everything (V2X) system. The communication methods in a V2X system are collectively referred to as V2X (where X represents anything). For example, V2X communication includes: vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, or vehicle-to-network (V2N) communication, etc.

[0060] In addition, in the embodiments of this application, the STA may also include sensors such as smart printers, train detectors, and gas stations. Its main functions include collecting data (some terminal devices), receiving control information and downlink data from the AP, and sending electromagnetic waves to transmit data to the AP.

[0061] In addition, the AP in this application embodiment can be a device for communicating with the STA. The AP can be a network device in a wireless local area network, and the AP can be used to communicate with the STA through the wireless local area network.

[0062] From the perspective of the communication standards supported by the AP, in some implementations, the AP can be a device that supports the 802.11be standard. The AP can also be a device that supports various current and future 802.11 family WLAN standards such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0063] From the perspective of the communication standards supported by the STA, in some implementations, non-AP STAs can support the 802.11be standard. Non-AP STAs can also support various current and future 802.11 family of wireless local area networks (WLAN) standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0064] In this application embodiment, the frequency bands supported by WLAN technology are not limited. In some implementations, the frequency bands supported by WLAN technology may include, but are not limited to: low frequency bands (e.g., 2.4GHz, 5GHz, 6GHz) and high frequency bands (e.g., 45GHz, 60GHz).

[0065] It should be understood that the specific forms of STA and AP are not specifically limited in the embodiments of this application, and are merely illustrative examples.

[0066] Time synchronization

[0067] STAs in a single infrastructure BSS, PBSS, or IBSS are synchronized to a common clock using the mechanisms defined in Synchronization.

[0068] The timing synchronization function (TSF) keeps the timers synchronized for all STAs in the same BSS. All STAs with dot11OCBActivated set to false maintain a local TSF timer. STAs with dot11OCBActivated set to true may maintain a TSF timer for purposes other than synchronization.

[0069] A multi-band capable device shall maintain a local TSF timer for each channel in which the STA operates.

[0070] In an Infrastructure BSS or PBSS, the AP in the Infrastructure BSS or the Personal Basic Service Set (PBSS) control point in the PBSS should act as the time master for the TSF. In non-DMG and sub-1GHz (S1G) BSSs, the AP should periodically transmit frames called beacon frames. Beacon frames, S1G beacon frames, DMG beacon frames, and announcement frames contain the TSF timer values ​​of the AP or PCP to synchronize the TSF timers of other STAs in the BSS. A receiving STA shall accept the timing information in Beacon, S1G, DMG, and Announce frames sent from the AP or PCP servicing its BSS. (In an infrastructure BSS or a PBSS, the AP or PCP in the PBSS shall be the timing master for the TSF. In a non-DMG and non-S1G BSS, the AP shall periodically transmit frames called Beacon frames. Beacon, S1G Beacon, DMG Beacon, and Announce frames contain the value of the AP's or PCP's TSF timer in order to synchronize the TSF timers of other STAs in a BSS.)

[0071] When a non-DMG STA sends a Beacon, Timing Advertisement, or Probe Response frame, or a TIM frame with a TSF timestamp, the frame's Timestamp field should be set to the broadcast address.

[0072] It should be noted that in order for the value of the Timestamp field to match the correct TSF value, implementations need to compensate for delays along the transmit path, such as delays through the local PHY from the MAC-PHY interface to the transmit antenna connector.

[0073] Single-link discovery and association

[0074] Non-AP STAs discover APs through passive or active scanning. Specifically, non-AP STAs obtain detailed information about APs by receiving beacon frames and / or probe response frames, including timestamps, beacon intervals, service set identifiers, capability information, operating parameters, transmission power-related limitations, enhanced distributed channel access (EDCA) parameters, quality of service capabilities, robust network elements, and so on.

[0075] To become a member of a particular extended service set (ESS) using passive scanning, a STA should scan for beacon and DMG beacon frames containing that ESS's SSID, returning all beacon and DMG beacon frames matching the desired SSID in the BSSDescriptionSet parameter of the corresponding MLME-SCAN.confirm primitive with the appropriate bits in the Capability Information field or DMG Capabilities field indicating whether the beacon frame or DMG beacon frame came from an infrastructure BSS, PBSS, or IBSS.

[0076] To actively scan, the STA should send Probe Request frames containing a wildcard SSID, the desired SSID, or one or more SSID List elements. However, a DMG STA may also need to send DMG Beacon frames or perform beamforming training prior to sending the Probe Request frames.

[0077] Active scanning involves generating probe request frames and subsequently processing received probe response frames. See Figures 2 and 3. Figure 2 illustrates active scanning by a non-DMG STA with a probe request frame addressed to a specific BSSID. Figure 3 illustrates active scanning by a non-DMG STA with a probe request frame addressed to a wildcard BSSID.

[0078] A STA may send an individually addressed or broadcast Probe Request frame to a peer STA that it has determined is within range, in order to solicit information contained within a response frame. When the Probe Request frame is sent to the broadcast address, the Address 3 (BSSID) field shall be set to the MAC address of the peer STA.

[0079] It should be noted that a STA may determine that a peer STA is within range by, for example, receiving a frame from that peer STA, or, if the peer STA is an AP, by receiving a frame from another AP that corresponds to a colocated BSS of the AP.

[0080] It should also be noted that sending an individually addressed frame can provide more reliable delivery to a peer STA because it is acknowledged and retransmit procedures apply. The responding STA responds in accordance with the criteria for sending a response.

[0081] Referring to Figure 4, which illustrates an example of a probe request for a single address, both the probe request and response are addressed individually. When a STA has not yet determined that a peer STA is in range, the probe request frames it sends to discover the peer STA are transmitted in accordance with the active scanning procedures in Criteria for sending a response. For a non-DMG STA, such probe request frames are always sent to the broadcast address.

[0082] Multi-link discovery and establishment

[0083] Relevant standards define AP and STA devices with multi-link operation capabilities as AP MLD and non-AP MLD devices. AP MLD and non-AP MLD can establish multiple links on multiple different frequency bands and / or non-overlapping channels in the same frequency band.

[0084] Before initiating a multi-link setup with the AP MLD, a non-AP MLD is expected to discover an AP MLD and affiliated APs of interest. The non-AP MLD can use one or a combination of the following methods to discover these AP MLDs and affiliated APs:

[0085] —Through each of its affiliated STAs, perform passive scanning by following the procedure defined in Passive scanning procedures or active scanning by following the procedure defined in Active scanning and probing procedures.

[0086] —Through one of its affiliated STAs, transmit a multi-link probe request on any link that the AP MLD is operating on, with the frame addressed to the affiliated AP operating on that link, to obtain information about the AP MLD and its affiliated AP(s) by following the procedure defined in Use of multi-link probe request and response.

[0087] The combination of information that the non-AP MLD selects to gather is implementation-dependent and can be based on criteria such as power consumption, single-radio operation, reachability, etc. The non-AP MLD follows all the active scanning procedures for the channel on which the Probe Request frame is sent. For example, when performing active scanning on 6GHz channels, it follows the rules specified in Non-AP STA scanning behavior.

[0088] It should be noted that a non-AP MLD can discover information about an AP MLD or that of an AP affiliated with an AP MLD via other means such as BSS transition management. The frame exchange for gathering information about the AP MLD and its affiliated one or more APs, and for performing ML setup with the AP MLD, will be the same as that described in this clause.

[0089] Figure 5 illustrates possible frame exchange sequences during MLO discovery and ML setup when the AP operating on the channel does not correspond to a nontransmitted BSSID. As shown in Figure 5, during discovery, a possible frame exchange sequence is performed between a non-AP STA affiliated with a non-AP MLD and an AP that does not correspond to a nontransmitted BSSID and is affiliated with an AP MLD.

[0090] In a Basic Multi-Link element, a complete profile of a reported STA consists of all elements and fields. These elements and fields are included in a management frame of the same subtype as the frame carrying the Basic Multi-Link element that the reporting STA transmits, as if the reported STA were to transmit that frame. It is subject to the inheritance rules of each Per-STA Profile subelement in the Basic Multi-Link element and the exceptions to fields and elements not carried in each Per-STA Profile subelement.If the conditions for (extended) channel switching and channel quieting in the per-STA profile for a reported AP apply, then the reporting AP shall include applicable elements listed in the ML procedures for (extended) channel switching and channel quieting in the per-STA profile for a reported AP in a (Re)Association Response frame.

[0091] It should be noted that the above definition of a complete profile applies only to a Basic Multi-Link element.

[0092] Each per-STA Profile subelement of the Basic Multi-Link element that is included in a Management frame transmitted by a STA affiliated with an MLD and that carries a complete profile shall consist of:

[0093] —STA control field (as defined in the STA control field format of the Basic Multi-Link element);

[0094] —STA information field (as defined in the STA information field format of the Basic Multi-Link element); and

[0095] —The STA Profile field containing fields and elements based on the following rules:

[0096] If the reporting STA is an AP, the corresponding STA Profile field is:

[0097] Fields and elements are carried in the same order and subject to the following conditions: if the fields and elements are carried in a multi-link probe response, then according to Table (Probe Response frame body); if the frame is an Association Response frame, then according to Table (Association Response frame body); if the frame is a Reassociation Response frame, then according to Table (Reassociation Response frame body).

[0098] It is subject to inheritance rules defined in the Inheritance in the Per-STA Profile sub-element of Basic Multi-Link element and exceptions specified in Fields and elements not carried in a Per-STA Profile sub-element.

[0099] If the reporting STA is a non-AP STA, the corresponding STA Profile field is:

[0100] Fields and elements are carried in the same order and subject to conditions as in, if the frame is an Association Request frame, then according to the Table Association Request frame body; if the frame is a Reassociation Request frame, then according to the Table Reassociation Request frame body.

[0101] It is subject to inheritance rules defined in the Inheritance in the Per-STA Profile sub-element of Basic Multi-Link element and exceptions specified in Fields and elements not carried in a Per-STA Profile sub-element.

[0102] If an additional element is included in the STA profile field, other than the ones listed in the tables of (PV0) Management frames, then the element shall follow all the applicable elements listed in the tables of (PV0) Management frames for the reported STA. When more than one such additional element is included, they are ordered based on their Element ID and Element ID Extension (if present).

[0103] It should also be noted that, for example, if a reported AP corresponds to an untransmitted BSSID in a set of multiple BSSIDs, then the multiple BSSID index elements of that AP will be included in the basic multilink element in each STA profile sub-element corresponding to that reported AP, and this basic multilink element is carried in the associated response frame (see Multiple BSSID Index Elements). The multiple BSSID index elements appear after all elements that satisfy the condition that the reported AP is included in each STA profile sub-element based on the table-based associated response frame body.Furthermore, if the conditions described in the multi-link procedures for (extended) channel switching and channel quieting require the reported AP to contain a maximum channel switch time element, then the maximum channel switch time element is also included and appears after the multiple BSSID-Index element.

[0104] Optionally, a non-inheritance element appears as the last element in the STA Profile field and carries a list of elements that are not inherited by the reported STA from the reporting STA (see Inheritance in the Per-STA Profile subelement of Basic Multi-Link element).

[0105] An AP affiliated with an AP MLD shall not include the following in the STA profile fields of the basic multi-link elements: Timestamp field, Beacon Interval field, AID field, BSS Max Idle Period element, MSCS Descriptor element, QoS Map element, FILS Indication element, Neighbor Report element, Reduced Neighbor Report element, Multiple BSSID element, TIM element, TID-To-Link Mapping element, or Multi-Link Traffic Indication element. element,Channel Usage element or another Multi-Link element in the STA Profile field of the Basic Multi-Link element).

[0106] It should be noted that for an NSTR mobile AP MLD, only the AP on the primary link transmits a Beacon frame. Furthermore, the TSF timer on the non-primary link is the same as that on the primary link (see NSTR mobile AP MLD operation).

[0107] It should also be noted that for an AP MLD that is not an NSTR mobile AP MLD, the Timestamp field is specific to each link, and the value for each link can be obtained by receiving a Beacon frame, a Probe Response frame, or a TIM frame on the respective link, or can be determined based on the TSF Offset subfield carried in the STA Info field corresponding to the reported AP.

[0108] It should also be noted that the contents of the TIM element for a non-AP MLD are consistent across all links. The Beacon Interval field is an explicit subfield in the STA Info field for the reported AP. The AID field and the BSS Max Idle Period element apply at the MLD level and are carried outside the Basic Multi-Link element.

[0109] An AP affiliated with an AP MLD shall not include an SSID element in the STA Profile field of the Basic Multi-Link element for a reported AP unless both of the following conditions are satisfied: The Basic Multi-Link element carries a complete profile of the reported AP; The Basic Multi-Link element is contained in a multi-link probe response transmitted by the AP corresponding to the transmitted BSSID in a multiple BSSID set in response to a multi-link probe request directed to an AP corresponding to the nontransmitted BSSID in the same multiple BSSID set.

[0110] A non-AP STA affiliated with a non-AP MLD shall not include a Listen Interval field, a Current AP Address field, an SSID element, a BSS Max Idle Period element, or another Multi-Link element in the STA Profile field of the Basic Multi-Link element.

[0111] It should be noted that the Listen Interval field and the Current AP Address field are applied at the MLD level and are carried outside the Basic Multi-Link element.

[0112] It should also be noted that all APs affiliated with the same AP MLD advertise the same SSID (see General), and therefore, the same SSID value applies to a reported (AP or non-AP) STA.

[0113] A STA affiliated with an MLD shall not include the FTE and the MDE for each reported STA in the STA's STA Profile field of the Basic Multi-Link element carried in a (Re)Association Request frame or a (Re)Association Response frame that it transmits. Also see FT initial mobility domain association in an RSN and FT reassociation.

[0114] It should be noted that the robust security network element (RSNE) / robust security network extended element (RSNXE) carried in the (re)association request frame does not include the basic multilink element because the non-AP MLD provides only one RSNE / RSNXE during multilink establishment. See general guidelines. The AP MLD may carry different management frame protection required (MFPR) in the RSNE for each AP it is associated with; in this case, the (re)association response frame includes the RSNE in the corresponding STA profile field of the basic multilink element. See RSNA Selection (No RSNE / RSNXE is included in the Basic Multi-Link element carried in a(Re)Association Request frame because there is only one RSNE / RSNXE provided by the non-AP MLD during ML(re)setup.See General.An AP MLD can have a different MFPR carried in the RSNE for each of its affiliated APs and in such case, the(Re)Association Response frame includes the RSNE in the corresponding STA Profile field of Basic Multi-Link element.See RSNA selection).

[0115] A multi-link probe request allows a non-AP STA affiliated with a non-AP MLD to request an AP(s) affiliated with an AP MLD to include the complete or partial set of capabilities, parameters, and operation elements of the AP(s) affiliated with the targeted AP MLD in the response frame. The complete and partial profiles of a requested AP are defined in the advertisement of complete or partial per-link information.

[0116] It should be noted that if an AP MLD has only one affiliated AP, a multi-link probe response will not provide additional information compared to a probe response frame that is not a multi-link probe response.

[0117] The value of the Link ID field of the Per-STA Profile subelement of the Probe Request Multi-Link element identifies the AP affiliated with an AP MLD that is requested and shall be set to the link ID that is assigned to this AP.

[0118] If the Probe Request Multi-Link element in the multi-link probe request does not contain any per-STA profiles, then all APs affiliated with the same AP MLD as the AP identified in the Address 1 or Address 3 field or AP MLD ID of the multi-link probe request shall be requested APs.

[0119] If the Probe Request Multi-Link element in the multi-link probe request includes one or more per-STA profiles, then only APs affiliated with the same AP MLD as the AP identified in the Address 1 or Address 3 field or in the AP MLD ID subfield (if present) of the multi-link probe request and whose link ID is equal to the value in the Link ID field in a per-STA profile in the Probe Request Multi-Link element in the multi-link probe request shall be requested APs.

[0120] The partial profile of a requested AP sent by a reporting AP consists of one or more elements that are requested in the Request element, Extended Request element, or both elements carried in the multi-link probe request.

[0121] A multi-link probe request allows a non-AP STA to request an AP affiliated with an AP MLD to include the complete profile of all requested APs affiliated with the targeted AP MLD if the Probe Request frame does not include the (Extended) Request element(s) in the frame body and the Probe Request Multi-Link element in the Probe Request frame does not include any per-STA profile.

[0122] A multi-link probe request allows a non-AP STA to request an AP affiliated with an AP MLD to include the same requested partial profile for all requested APs affiliated with the targeted AP MLD if the Probe Request frame includes the (Extended) Request element(s) in frame body and the Probe Request Multi-Link element in the Probe Request frame does not include any per-STA profile.

[0123] A multi-link probe response is a probe response frame.

[0124] —It is sent in response to a received multi-link probe request;

[0125] —It includes a Basic Multi-Link element which can carry complete or partial profile(s), based on the soliciting request, for each of the requested AP(s) affiliated with the targeted AP MLD.

[0126] If an AP affiliated with an AP MLD receives a multi-link probe request from a non-AP STA affiliated with a non-AP MLD requesting a complete profile for the requested AP, it shall respond with a multi-link probe response that includes a Basic Multi-Link element with a per-STA profile containing at least the requested (extended) elements, unless the requested elements are not part of the complete profile of the requested AP, and also conforms to the rules defined in the Criteria for sending a response.如果该接入点收到来自隶属于非接入点多链路设备的非接入点站点的多链路探测请求,该请求请求获取目标接入点的部分配置文件,则除非所请求的元素不属于该目标接入点的完整配置文件且需遵守“发送响应的标准”中定义的规则,否则该接入点应当响应多链路探测响应,该响应包含基本多链路元素,该元素带有单站点配置文件,且该配置文件至少包含针对目标接入点从(扩展)请求元素中请求得到的元素。

[0127] A non-AP MLD discovers an AP MLD and its affiliated APs when a non-AP STA affiliated with the non-AP MLD receives one or more of the following:

[0128] —A basic multi-link element carried in a beacon frame or probe response frame (not a multi-link probe response), transmitted by an AP affiliated with the AP MLD or by the AP corresponding to the transmitted BSSID in the same multiple BSSID set as at least one of the APs affiliated with the AP MLD;

[0129] —A multi-link probe response from an AP affiliated with the AP MLD or the AP corresponding to the transmitted BSSID in the same multiple BSSID set as at least one of the APs affiliated with the AP MLD, carrying a Basic Multi-Link element with a complete profile of one or more reported APs.

[0130] —One or more beacon, probe response, or FILS discovery frames transmitted by an AP (reporting AP) and carrying a Reduced Neighbor Report element that includes the MLD Parameters subfield in the TBTT Information field corresponding to one or more reported APs. A non-AP MLD infers the relationship between the reported AP(s) and the reporting AP by decoding the AP MLD ID subfield of the MLD Parameters subfield in the Reduced Neighbor Report element and following the rules described in AP behavior;

[0131] —A management frame that carries Neighbor Report element(s). A non-AP MLD determines that two or more APs reported in different Neighbor Report elements that include the Basic Multi-Link subelement are affiliated with the same AP MLD based on the MLD MAC Address subfield of the Common Info field of the Basic Multi-Link elements. The reported APs are affiliated with the same AP MLD if the values ​​carried in the MLD MAC Address field of the Common Info field of the Basic Multi-Link element of the reported APs are the same.

[0132] It should be noted that if a non-AP MLD receives a multi-link probe response that does not carry profile for one or more requested APs, then it can send another multi-link probe request to solicit information of the missing profile(s) that are of interest to it by including the corresponding Per-STA Profile subelement(s) in the Probe Request Multi-Link element.

[0133] A non-AP MLD can use the information it gathers from a Reduced Neighbor Report element and a Basic Multi-Link element to decide whether to perform ML setup with an AP MLD.

[0134] A non-AP MLD can use the information it receives from a Neighbor Report element to decide whether to perform ML(re)setup or BSS transition.

[0135] Figure 6 illustrates an example of the multi-link establishment process. As shown in Figure 6, in this example, the AP MLD has three affiliated APs: AP 1 operates in the 2.4 GHz band, AP 2 operates in the 5 GHz band, and AP 3 operates in the 6 GHz band. The Non-AP MLD initiates the multi-link establishment process. The non-AP STA 1, affiliated with the non-AP MLD, sends an association request frame to AP 1, affiliated with the AP MLD. Specifically, the TA field of the association request frame is set to the MAC address of the non-AP STA 1, and the RA field is set to the MAC address of AP 1. The association request frame includes a basic multilink element indicating the MLD MAC address of the non-AP MLD and the complete profiles of non-AP STA 1 (in the frame body of the association request frame), non-AP STA 2 (in the per-STA profile sub-element carried in the basic multilink element), and non-AP STA 3 (in the per-STA profile sub-element carried in the basic multilink element) to request the establishment of three links (one link between AP 1 and non-AP STA 1, one link between AP 2 and non-AP STA 2, and one link between AP 3 and non-AP STA 3). Then, in response to the requested multilink setup, AP 1, which is attached to the AP MLD, sends an association response frame to non-AP STA 1, which is attached to the non-AP MLD. Specifically, the TA field of the association response frame is set to the MAC address of AP 1, and the RA field is set to the MAC address of non-AP STA 1, indicating successful multilink setup. The association response frame includes a basic multilink element that indicates the MLD MAC address of the AP MLD and the complete profiles of AP 1 (in the frame body of the association response frame), AP 2 (in the per-STA profile sub-element carried in the basic multilink element), and AP 3 (in the per-STA profile sub-element carried in the basic multilink element). After successful multilink establishment between the non-AP MLD and the AP MLD, three links are established (link 1 between AP 1 and non-AP STA 1, link 2 between AP 2 and non-AP STA 2, and link 3 between AP 3 and non-AP STA 3). (In this example, the AP MLD has three affiliated APs: AP 1 operates in the 2.4GHz band, AP 2 operates in the 5GHz band, and AP 3 operates in the 6GHz band.)The non-AP MLD initiates the ML setup procedure and non-AP STA 1affiliated with the non-AP MLD sends an Association Request frame to AP 1affiliated with the AP MLD,i.e.,the TA field of the Association Request frame is set to the MAC address of the non-AP STA 1and the RA field of the Association Request frame is set to the MAC address of the AP 1.The Association Request frame includes a Basic Multi-Link element that indicates the MLD MAC address of the non-AP MLD and a complete profile of non-AP STA 1(in the frame body of the Association Request frame),non-AP STA 2(in a Per-STA Profile subelement carried in the Basic Multi-Link element),and non-AP STA 3(in a Per-STA Profile subelement carried in the Basic Multi-Link element)to request three links to be setup(one link between AP 1and non-AP STA 1,one link between AP 2 and non-AP STA 2,and one link between AP 3and non-AP STA 3).AP MLD then responds to the requested ML setup,and AP 1affiliated with the AP MLD sends an Association Response frame to non-AP STA 1 affiliated with the non-AP MLD,i.e.,the TA field of the Association Response frame is set to the MAC address of the AP 1and the RA field of the Association Response frame is set to the MAC address of the non-AP STA 1,to indicate successful ML setup.The Association Response frame includes a Basic Multi-Link element that indicates the MLD MAC address of the AP MLD and a complete profile of AP 1(in the frame body of the Association Response frame),AP 2(in a Per-STA Profile subelement carried in the Basic Multi-Link element),and AP 3(in a Per-STA Profile subelement carried in the Basic Multi-Link element).After successful ML setup between the non-AP MLD and AP MLD,three links are setup(link 1between AP 1and non-AP STA 1,link 2 between AP 2and non-AP STA 2,and link 3between AP 3and non-AP STA 3))。.

[0136] The following content illustrates the management frames transmitted by a non-AP STA affiliated with a non-AP MLD during MLO discovery and ML setup.

[0137] Figure 7 (Contents of a Probe Request frame that is not a multi-link probe request transmitted by a non-AP STA affiliated with a non-AP MLD during MLO discovery) shows a probe request frame that is not a multi-link probe request in a non-AP MLD.

[0138] Figure 8 (Contents of a multi-link probe request transmitted by a non-AP STA affiliated with a non-AP MLD during MLO discovery) shows a multi-link probe request frame.

[0139] Figure 9 (Contents of an authentication frame transmitted by a non-AP STA affiliated with a non-AP MLD during multi-link setup) shows an authentication frame.

[0140] Figure 10 (Contents of a (Re)Association Request frame transmitted by a non-AP STA affiliated with a non-AP MLD during multi-link setup) shows a (Re)Association Request frame.

[0141] Figure 11 is an example of a basic multi-link element in an association request frame. In Figure 11, a non-AP STA attached to a non-AP MLD transmits an association request frame containing a basic multi-link element that carries the complete profiles of two other non-AP STAs attached to the non-AP MLD (non-AP STA x and non-AP STA y). Figure 11 shows the per-STA profile of non-AP STA x. The type subfield of the multi-link control field is set to 0 to indicate that the multi-link element is a basic multi-link element. The common information field carries information applicable to the MLD level, as described in the basic multi-link element. In this example, only the common information length and MLD MAC address fields are shown. However, other fields may exist in the common information field, and their presence is indicated by subfields carried within the bitmap subfield of the multi-link control field. Each per-STA profile sub-element in the link information field carries the complete profile of the reported non-AP STA attached to the non-AP MLD and applies inheritance. Each perSTA profile sub-element carries an STA control field, followed by an STA information field and an STA profile field. In this example, only the STA information length and STA MAC address fields are shown. However, other sub-fields may exist in the STA information field, their presence indicated by sub-fields in the STA control field. The STA profile fields carry a variable number of fields and elements in the order defined in the Association Request frame body, and inheritance is applied (see Inheritance in perSTA profile sub-element). Non-inherited elements (if present) list elements that are not inherited by the reporting STA (In Figure 11 (Example of Basic Multi-Link element in an Association Request frame), a non-AP STA affiliated with a non-AP MLD transmits an Association Request frame that includes a Basic Multi-Link element that carries the complete profile of two other non-AP STAs affiliated with its non-AP MLD (non-AP STA x and non-AP STA y).The figure expands the Per-STA profile for non-AP STA x.The Type subfield of the Multi-Link Control field is set to 0to indicate that the Multi-Link element is a Basic Multi-Link element.The Common Info field carries information that applies to the MLD level as described in Basic Multi-Link element.In this example,only the Common Info Length and MLD MAC Address fields are shown.However,there can be other fields present in the Common Info field whose presence is signaled via the subfields carried within the Presence Bitmap subfield of the Multi-Link Control field.Each Per-STA Profile subelement in the Link Info field carries the complete profile,with inheritance applied,of a reported non-AP STA affiliated with the non-AP MLD.Each Per-STA Profile subelement carries the STA Control field followed by the STA Info field and the STA Profile field.In this example,only the STA Info Length and STA MAC Address fields are shown.However,there can be other subfields present in the STA Info field whose presence is signaled via the subfields in the STA Control field.The STA Profile field carries a variable number of fields and elements in the order defined in Association Request frame body with inheritance applied(see Inheritance in a Per-STA Profile subelement).The Non-inheritance element(if present)lists the elements that are not inherited by the reported STA)。.

[0142] It should be noted that, because the listen interval is applied at the MLD level, the listen interval field is not included within a STA Profile field (see Fields and elements not carried in a Per-STA Profile subelement) of the Basic Multi-Link element carried in an Association Request frame. Therefore, the Capability Information field is the only field carried in the STA Profile field of the Basic Multi-Link element carried in an Association Request frame and is followed by elements applicable to the reported STA.

[0143] Critical update flag

[0144] When the critical parameters of the BSS established by the AP MLD's affiliated AP change, it will indicate this in the Critical Update Flag field of the capability information field in the transmitted beacon frame. An example of the capability information field can be seen in Figure 12.

[0145] An AP affiliated with an AP MLD sets the Critical Update Flag subfield to 1 in the Beacon and Probe Response(s) until and including its next DTIM beacon, based on the conditions described in the BSS parameter critical update procedure.

[0146] If the Critical Update Flag subfield of the Nontransmitted BSSID Capability field (see Nontransmitted BSSID Capability element) is set to 1 in at least one Nontransmitted BSSID Profile subelement carried in the Multiple BSSID element in the same frame, then the AP affiliated with an AP MLD sets the Nontransmitted BSSID Critical Update Flag subfield to 1. Otherwise, the AP sets the Nontransmitted BSSID Critical Update Flag subfield to 0.

[0147] An AP (reporting AP) affiliated with an AP MLD that is not in a multiple BSSID set or that corresponds to a transmitted BSSID in a multiple BSSID set shall:

[0148] In the Beacon and Probe Response frames it transmits, it transmits a BSS Parameters Change Count subfield for each of all APs affiliated with the same AP MLD as the reporting AP, and in the (Re)Association Response frame it transmits, it transmits a BSS Parameters Change Count subfield for each of all APs that are requested for (re)setup in the received (Re)Association Request frame.

[0149] The BSS Parameters Change Count subfield value for each AP is initialized to 0, and shall be incremented by 1 (modulo 256, excluding the value 255) when a critical update occurs to the BSS parameters of that AP as defined in TIM Broadcast.

[0150] In Beacon and Probe Response frames, the BSS Parameters Change Count subfield for each of the other AP(s) affiliated with the AP MLD shall be carried in the MLD Parameters subfield in the TBTT Information field of the Reduced Neighbor Report element corresponding to that AP, where each of the other AP(s) is identified by the Link ID subfield of the MLD Parameters subfield.

[0151] In the (Re)Association Response frame, the BSS Parameters Change Count subfield for each of the other AP(s) that are affiliated with the AP MLD and that are requested for (re)setup in the received (Re)Association Request frame shall be carried in the STA Info subfield in the Per-STA Profile subelement of Basic Multi-Link element corresponding to that AP, where each of the other AP(s) is identified by the Link ID subfield of the STA Control field of the Per-STA Profile subelement.

[0152] The BSS Parameters Change Count subfield for the reporting AP should be included in the Common Info field of the Basic Multi-Link element, where the reporting AP is identified by the Link ID subfield of the Common Info field.

[0153] If at least one of the following conditions is met, the Critical Update Flag subfield of the Capability Information field is set to 1 in Beacon and Probe Response frames until and including the next DTIM beacon on the link on which the reporting AP is operating:

[0154] For any AP affiliated with the same AP MLD as the reporting AP, there is a change in the value carried in the BSS Parameters Change Count subfield of the MLD Parameters field in the Reduced Neighbor Report element, or a change in the value carried in the BSS Parameters Change Count subfield in the Common Info field of the Basic Multi-Link element.

[0155] A new affiliated AP is added to the AP MLD with which the reporting AP is affiliated, following the procedure defined in Adding affiliated AP(s).

[0156] The reporting AP includes or modifies a multi-link reconfiguration element by adding a new per-STA profile subelement, following the procedure defined in Removing affiliated AP(s), according to the procedure defined in Removing affiliated AP(s).

[0157] An AP affiliated with the same AP MLD becomes disabled or enabled through a new advertised TTLM defined in Advertised TTLM in Beacon and Probe Response frames.

[0158] Otherwise, set the Critical Update Flag subfield of the Capability Information field to 0.

[0159] For each reported AP affiliated with the same AP MLD as the reporting AP, if the updated elements that correspond to the latest critical update that generated a change to the value carried in the BSS Parameters Change Count subfield for the reported AP are included in the frame carrying the Reduced Neighbor Report element, and these updated elements are selected from the elements described in the multi-link procedure for (extended) channel handover and channel silencing, then all Update Included subfields in the MLD Parameters subfield of the TBTT Information field of the Reduced Neighbor Report element corresponding to the reported AP are set to 1, until the updated elements are no longer included or until the BSS Parameter Change Count subfield is further incremented due to another critical update, and otherwise set to 0. from the elements as described in ML procedures for(extended)channel switching and channel quieting,and until the updated elements are no longer included or until the BSS Parameters Change Count subfield is additionally incremented due to another critical update, and set to 0otherwise). ,

[0160] A non-AP MLD shall maintain a record of the most recently received BSS Parameters Change Count subfield value for each associated AP affiliated with the AP MLD.

[0161] When a non-AP STA attached to a non-AP MLD receives a BSS Parameters Change Count subfield for a certain AP that is affiliated with an AP MLD with which the non-AP MLD has performed an ML setup and that operates on the link that is part of the ML setup, and the value of the BSS Parameters Change Count subfield for the AP is different from the previously received value, then the non-AP MLD shall follow one of the following mechanisms:

[0162] The non-AP STA affiliated with the non-AP MLD that is associated with the AP attempts to receive a Beacon frame or a Probe Response frame from the AP.

[0163] Any non-AP STA affiliated with the non-AP MLD attempts to send a Probe Request frame to its associated AP, soliciting information about the AP.

[0164] Except that if the value in the BSS Parameters Change Count subfield is equal to the most recently received value recorded by the non-AP MLD for that AP plus 1 and if the All Updates Included subfield in the MLD Parameters subfield in the TBTT Information field of the Reduced Neighbor Report element corresponding to the AP is set to 1, no further action is needed from the non-AP MLD as the updated elements are included in the received frame.

[0165] It should be noted that the probe request frame can be either a multi-link probe request or a probe request frame that is not a multi-link probe request.

[0166] An example of a critical update operation in MLO is shown in Example of critical update operation.

[0167] Figure 13 is an example of a critical update operation. Figure 13 shows two subordinate APs attached to the same AP MLD. AP1 and AP2, attached to the AP MLD, operate on link 1 and link 2, respectively. Figure 13 shows the values ​​carried in the beacon frame transmitted by AP2 for the critical update flag subfield, BSS parameter change count subfield, and all update contain subfield corresponding to AP1 when a critical update occurs in AP1's BSS. In the example, AP1's BSS parameter change count subfield has a value of 5 in beacon 21, and the critical update flag and all update contain (corresponding to AP1) subfields are set to 0. First, AP1 announces a critical update in beacon 12 that does not correspond to an element listed in the ML procedure for (extended) channel handover and channel silencing, causing the BSS parameter change count subfield (for AP1) to increment by 1 (becoming 6) in beacon 22. Furthermore, AP2 sets the critical update flag subfield to 1 in beacon 22. Since the element corresponding to the latest critical update is not included in beacon 22, the All Update Include subfield (corresponding to AP1) is set to 0. Next, in beacon 13, AP1 includes a silence element to announce a silence interval, which causes the BSS parameter change count subfield (for AP1) to increment by 1 (becoming 7). Because this critical update corresponds to an element listed in the ML procedure for (extended) channel handover and channel silencing, AP2 includes the silence element in each STA profile corresponding to AP1 in beacon 23, setting the critical update flag and the All Update Include subfield (corresponding to AP1) to 1 and 1 respectively. The critical update flag subfield is set to 1 until the next DTIM beacon for AP2 (i.e., until beacon 25). Because these beacon frames contain elements corresponding to the last critical update, the All Update Include subfield corresponding to AP1 is set to 1 in beacons 24, 25, and 26. Finally, AP1 announced a critical update in beacon 17 that did not correspond to an element listed in the ML procedure for (extended) channel handover and channel silencing, causing AP1's BSS parameter change count subfield to increment by 1 (becoming 8). Although the silencing element is still included in the per-STA profiles corresponding to AP1 in beacons 27 and 28, the element corresponding to the latest critical update is not included in these beacon frames. Therefore, all update inclusion subfields corresponding to AP1 in beacons 27 and 28 are set to 0 (illustrates two APs affiliated with the same AP MLD. AP1 and AP2 affiliated with the AP MLD operate on Link 1 and Link 2, respectively).The figure shows the values carried in the Critical Update Flag subfield,the BSS Parameters Change Count subfield,and the All Updates Included subfield corresponding to AP1 in the Beacon frames transmitted by AP2 when critical updates occur in AP1’s BSS.In the illustration,the value of the BSS Parameters Change Count subfield for AP1 is equal to 5in Beacon 21and the Critical Update Flag and All Updates Included(corresponding to AP1)subfields are set to 0.First,a critical update that does not correspond to an element listed in ML procedures for(extended)channel switching and channel quieting is announced by AP1 in Beacon 12,which causes the BSS Parameters Change Count subfield(for AP1)to increment by one(to 6)in Beacon 22.Also,in Beacon 22AP2 sets the Critical Update Flag subfield to 1.The All Updates Included subfield(corresponding to AP1)is set to 0since the element corresponding to the latest critical update is not included in Beacon 22.Next,in Beacon 13,AP1 includes a Quiet element to advertise a quiet interval,which results in the BSS Parameters Change Count subfield(for AP1)to be incremented by one(to 7).Since this critical update corresponds to an element listed in ML procedures for(extended)channel switching and channel quieting,AP2 includes the Quiet element in the per-STA profile corresponding to AP1 in Beacon 23and sets the Critical Update Flag and All Updates Included(corresponding to AP1)subfields to 1and 1,respectively.The Critical Update Flag subfield is set to 1until the next DTIM beacon of AP2(i.e.,until Beacon 25).The All Updates Included subfield corresponding to AP1 is set to 1in Beacons 24,25,and 26since these Beacon frames include the element corresponding to the last critical update.Finally, a critical update, not corresponding to elements listed in ML procedures for (extended) channel switching and channel quieting is announced by AP1 in Beacon 17, which causes AP1's BSS Parameters Change Count subfield to increment by one (to 8). Although the Quiet element is still included in the per-STA profile corresponding to AP1 in Beacons 27and 28, the element corresponding to the latest critical update is not included in these Beacon frames. Consequently, the All Updates Included subfield corresponding to AP1 in Beacons 27and 28 is set to 0). .

[0168] Multi-link devices identify the target site in the frame.

[0169] When the target station of a frame is not the peer station of the current link, the target wake time (TWT) element or MLO Link Information element of the Link ID Bitmap field indicating the target station needs to be added to the frame.

[0170] Between an AP MLD and a non-AP MLD associated with the AP MLD, an individually addressed MMPDU that is not a TWT Setup frame that includes a Link ID Bitmap subfield in its TWT element and that is intended for one or more STA(s) affiliated with the associated MLD operating on an enabled link shall follow the procedure below:

[0171] If the individually addressed MMPDU is transmitted to another STA (other than the intended STA(s)) affiliated with the associated MLD operating on a setup link through a STA affiliated with the MLD operating on the setup link, then the individually addressed MMPDU shall include an MLO Link Information element that identifies the intended link(s) of the MMPDU as the last element but before the Vendor Specific element(s) (if present).

[0172] Otherwise, the individually addressed MMPDU may include an MLO Link Information element that identifies the intended link(s) of the MMPDU as the last element, but before the Vendor Specific element(s) (if present).

[0173] It should be noted that if the MLO Link Information element is not present in the individually addressed MMPDU, the individually addressed MMPDU cannot be retransmitted to different STAs.

[0174] Channel switching and silent operation of multi-link devices

[0175] The term "affected AP" is used to identify an AP that is subject to channel switching, extended channel switching, and channel quieting among all the APs that are affiliated with an AP MLD.

[0176] It should be noted that the corresponding procedure for an NSTR Mobile AP MLD is described in the 3NSTR mobile AP MLD ML procedures for (extended) channel switching and channel quieting.

[0177] If an AP (affected AP) affiliated with an AP MLD includes any of the following applicable elements outside the Basic Multi-Link element in the Beacon frame, Probe Response frame, or (Extended) Channel Switch Announcement frame it transmits: Channel Switch Announcement element, Extended Channel Switch Announcement element, Max Channel Switch Time element, Quiet element corresponding to quiet intervals other than quiet intervals scheduled to protect R-TWT SPs (see Quieting STAs during R-TWT SPs), Quiet Channel element. If other APs are affiliated with the same AP MLD as the affected AP, then one of the following shall apply:

[0178] If another AP (reporting AP), affiliated with the same AP MLD as the affected AP, does not correspond to a nontransmitted BSSID, then the reporting AP shall carry the corresponding element(s) in the STA Profile field of the Per-STA Profile subelement corresponding to the affected AP contained in the Basic Multi-Link element included in the Beacon frame and Probe Response frame that it transmits.

[0179] If another AP (reporting AP) is attached to the same AP MLD as the affected AP and corresponds to an untransmitted BSSID in multiple BSSID sets, then the AP corresponding to the transmitted BSSID in the same multiple BSSID sets should carry the corresponding element in the STA profile field of the corresponding per-STA profile sub-element of the basic multilink element contained in its transmitted beacon frames and probe response frames. Specifically, the corresponding element(s) should be included in the STA Profile field of the Per-STA Profile subelement corresponding to the affected AP, and also in the nontransmitted BSSID profile corresponding to the reporting AP.

[0180] The timing fields in the Channel Switch Announcement element, the Extended Channel Switch Announcement element, the Quiet element, and the Quiet Channel element shall be applied in reference to the most recent TBTT and Beacon Interval indicated in the corresponding element(s) of the affected AP, and not to the TBTT and Beacon Interval of the reporting AP.

[0181] It should be noted that the affected AP can correspond to a transmitted BSSID in a multiple BSSID set, or to an AP with dot11MultiBSSIDImplemented equal to false.

[0182] It should also be noted that the Switch Time field in the Max Channel Switch Time element carried in the per-STA profile of the reported AP is not tied to a TBTT on the affected link. Instead, it provides an estimated time when the first Beacon frame will be transmitted on the new channel of the affected link after the channel switch has occurred.

[0183] It should also be noted that all five elements apply to the Beacon and Probe Response frames. For the (Extended) Channel Switch Announcement frame, the applicable elements include the Channel Switch Announcement, Extended Channel Switch Announcement, and Max Channel Switch Time elements.

[0184] If an AP corresponding to the transmitted BSSID in a multiple BSSID set includes any of the following elements in its transmitted beacon frame or probe response frame, so that any of these elements is inherited for the affected AP in these frames: Channel Switch Announcement element, Extended Channel Switch Announcement element, Max Channel Switch Time element, Quiet element corresponding to quiet intervals other than quiet intervals scheduled to protect R-TWT SPs (see Quieting STAs during R-TWT SPs)), Quiet Channel element. element), and if the affected AP corresponding to a nontransmitted BSSID in the same multiple BSSID set is affiliated with an AP MLD with at least another AP, then one of the following shall apply:

[0185] If another AP (reporting AP), affiliated with the same AP MLD, does not correspond to a nontransmitted BSSID, then it shall carry the corresponding element(s) in the STA Profile field of the Per-STA Profile subelement corresponding to the affected AP contained in the Basic Multi-Link element included in a Beacon frame and Probe Response frame that it transmits.

[0186] If another AP (reporting AP) is attached to the same AP MLD as the affected AP and corresponds to an untransmitted BSSID in multiple BSSID sets, then the AP that has transmitted a BSSID in the same multiple BSSID sets should carry the corresponding element in the STA profile field of the multiple BSSID elements contained in its transmitted beacon frames and probe response frames. Specifically, the corresponding element(s) is included in the STA Profile field of the Per-STA Profile subelement corresponding to the affected AP, and is also included in the nontransmitted BSSID profile corresponding to the reporting AP.

[0187] The timing fields in the Channel Switch Announcement element, the Extended Channel Switch Announcement element, the Quiet element, and the Quiet Channel element shall be applied in reference to the most recent TBTT and Beacon Interval included in the corresponding element(s) of the affected AP, and not with respect to the TBTT and Beacon Interval of the reporting AP.

[0188] If an AP attached to the AP MLD (the affected AP) is switching channels, the Channel Switching Announcement element, or the Extended Channel Switching Announcement element with a Channel Switching Count field set to a non-zero value, and the Maximum Channel Switching Time element should be included in every beacon and probe response frame on all links of the AP MLD, starting from when the affected AP includes these elements in its transmitted beacon frames until the estimated target switching time. After the estimated target switching time, the Channel Switching Announcement element and the Extended Channel Switching Announcement element should not be included in each STA profile corresponding to the affected AP in the beacon and probe response frames, while the Maximum Channel Switching Time element should be included in each STA profile corresponding to the affected AP in every beacon and probe response frame on all links of the AP MLD, except for the links corresponding to the affected AP, until the affected AP resumes BSS operation on the new channel. The value carried in the switching time field of the maximum channel switching time element represents the estimated adjustment time of the first beacon frame transmitted on the new channel of the affected link after the channel switch occurs. (If an AP (affected AP) affiliated with an AP MLD is switching channel, the Channel Switch Announcement element, or the Extended Channel Switch Announcement element with the Channel Switch Count field set to a nonzero value, and the Max Channel Switch Time element shall be included in every Beacon and Probe Response frames on all links of the AP MLD from the time the affected AP includes the elements in the Beacon frame it transmits until the estimated target switch time.)After the estimated target switch time, the Channel Switch Announcement element and the Extended Channel Switch Announcement element shall not be included in the per-STA profile corresponding to the affected AP in the Beacon and Probe Response frames, and the Max Channel Switch Time element shall be included in the per-STA profile of the affected AP in every Beacon and Probe Response frame on all links of the AP MLD, except the link corresponding to the affected AP, until the affected AP resumes BSS operation on the new channel. The value carried in the Switch Time field in the Max Channel Switch Time element indicates the adjusted estimated time of the first Beacon frame transmitted on the new channel of the affected link after the channel switch has occurred).

[0189] It should be noted that the Switch Time field in the Max Channel Switch Time element is not tied to a TBTT on the affected link.

[0190] It should also be noted that if the affected AP performs a subsequent channel switch between the target time of a previous channel switch and the time at which the affected AP will start beaconing on the new channel corresponding to the previous channel switch, the reporting AP may increase the value carried in the Switch Time field of the Max Channel Switch Time element.

[0191] When an AP (affected AP) affiliated with an MLD is switching from an initial operating class / channel to a target operating class / channel at a target switch time using channel switch announcement procedure or extended channel switch announcement procedure, and if another AP is affiliated with the same AP MLD as the affected AP, then:

[0192] The other AP (reporting AP) affiliated with the AP MLD shall set the Operating Class and Channel Number fields corresponding to the affected AP that is reported in the Reduced Neighbor Report element in Beacon and Probe Response frames to the initial operating class / channel before the target switch time (or, if the reporting AP corresponds to a nontransmitted BSSID, the BSSID transmitted by the reporting AP in the same set of multiple BSSIDs).

[0193] The other AP (reporting AP) affiliated with the AP MLD shall set the Operating Class and Channel Number fields corresponding to the affected AP that is reported in the Reduced Neighbor Report element in Beacon and Probe Response frames to the target operating class / channel at and after the target switch time.

[0194] Between the target switch time and the time at which the AP will start beaconing in the target operating class / channel, the Neighbor AP TBTT Offset subfield for the corresponding AP in the Reduced Neighbor Report element shall be set to 255.

[0195] It should be noted that if the affected AP performs a subsequent channel switch after the target switch time, the reporting AP may change the Operating Class and Channel Number fields corresponding to the affected AP.

[0196] If an AP (affected / reporting AP) attached to an AP MLD is using a Channel Switching Announcement or Extended Channel Switching Announcement procedure to switch from the initial working class / channel to the target working class / channel at the target switching time, and includes the maximum channel switching time element in its sent beacon and probe response frames, and another AP (reporting AP) attached to the AP MLD, if any, receives a (re)association request frame to perform multilink establishment with the AP MLD, where the AP (affected / reporting AP) is a requested link, then the other AP (reporting AP) should include the basic multilink element corresponding to the AP (affected / reporting AP)'s per-STA profile in its (re)association response frame in response to the (re)association request, indicating the target working class / channel and the maximum channel switching time element, to indicate when the AP (affected / reporting AP) will resume BSS operation, if the (re)association response frame is sent between the last beacon on the initial working class / channel and the first beacon on the target working class / channel. Otherwise, other APs (reporting APs), if any, should not include a Max Channel Switch Time element or an Extended Channel Switch Announcement element in the (Re)Association Request frame.then the other AP(reporting AP)shall include the complete profile for the AP indicating the target operating class / channel and a Max Channel Switch Time element in the per-STA profile corresponding to the AP(affected / reported AP)in the Basic Multi-Link element included in the(Re)Association Response frame it sends in response to indicate the time at which the AP(affected / reported AP)will resume BSS operation,if the(Re)Association Response frame is sent between the last beacon on the initial operating class / channel and the first beacon on the target operating class / channel.Otherwise,the other AP(reporting AP),if any,should not include a Max Channel Switch Time element or(Extended)Channel Switch Announcement element in(Re)Association Response frames)。,

[0197] If an AP (affected AP) associated with an AP MLD is switching channels, the AP MLD should ensure that the new channel is selected so that none of its associated non-AP MLDs have multiple setup links located on overlapping operating channels.

[0198] When an AP (affected / reporting AP) attached to an AP MLD has announced a silence interval other than the silence interval arranged to protect R-TWT SPs (see Silencing STAs during R-TWT SPs) using a silence element and an optional silence channel element, and another AP (reporting AP) of the same AP MLD, if any, receives a (re)association request frame to perform multilink establishment with the AP MLD, where the AP (affected / reporting AP) is a requested link, then the other AP (reporting AP), if any, should include the corresponding silence element and silence channel element (if present) in the basic multilink element of the per-STA profile of the AP (affected / reporting AP) in its (re)association response frame in response to the (re)association request.Otherwise, other APs (reporting APs) shall not include the Quiet element and Quiet Channel element in the (Re)Association Response frame (When an AP (affected / reported AP) affiliated with an AP MLD has announced quiet intervals other than the quiet intervals scheduled to protect R-TWT SPs (see Quieting STAs during R-TWT SPs) by using a Quiet element and optionally a Quiet Channel element, and another AP (reporting AP) of the same AP MLD, if any, receives a (Re)Association Request frame to perform ML setup with the AP MLD with the AP (affected / reported AP) as a requested link, then the other AP (reporting AP), if any, shall include the corresponding Quiet element and Quiet Channel element (if present) in the per-STA profile corresponding to the AP (affected / reported AP) in the Basic Multi-Link element included in the (Re)Association Response frame it sends in response.Otherwise,the other AP(reporting AP)should not include a Quiet element and Quiet Channel element in (Re)Association Response frames).

[0199] Examples of advertising quieting or channel switching information of a link on another link are shown in Example of advertising quieting or channel switching information of a link on another link.

[0200] Figure 14 is an example diagram of an AP carrying a silence element to signal silence on another link. Figure 14 shows two APs, AP 1 and AP 2, attached to the same AP MLD and operating on link 1 and link 2 respectively. AP 1 (the affected AP) includes a silence element in its transmitted beacon frame to indicate the planned silence interval on link 1. From this point until the start of the silence interval on link 1, AP 2 (the reporting AP) includes a silence element in the per-STA profile sub-element of the basic multi-link element carried in its transmitted beacon frames, corresponding to AP 1. Although not shown in Figure 14, the silence element is also included in each STA profile sub-element of the probe response frame transmitted by AP 2, corresponding to the basic multi-link element of AP 1. The values ​​of the silence count field, silence offset field, and silence duration field in the silence element are set by AP 2 with reference to link 1. Because the beacon interval value of AP 2 is greater than that of AP 1, the silence count field corresponding to the silence element in each STA profile sub-element of AP 1, transmitted by AP 2 in each subsequent beacon, decreases at a faster rate (i.e., 2 in this example). Non-AP STAs attached to the non-AP MLD, if capable of operating on link 2, send a (re)association request frame (not shown in the diagram) to AP 2 to perform a multi-link setup. The multi-link setup includes link 1 as one of the links. Since the (re)association response frame is transmitted by AP 2 after the silence interval begins on link 1, AP 2 includes the silence element corresponding to each STA profile of AP 1 in its transmitted (re)association response frame. The silence count field of the silence element carried in the (re-)association response frame is set to 128 to indicate that the silence interval on Link 1 begins in the beacon interval that occurred in the past TBTT (Target Beacon Transmission Time) on Link 1 (see Silence element). (Figure 14 illustrates two APs, AP 1 and AP 2, that are affiliated with the same AP MLD and operate on Link 1 and Link 2, respectively. The Beacon frame transmitted by AP 1 (the affected AP) includes a Quiet element to indicate a scheduled quiet interval on Link 1.)From this point onward and until the quiet interval begins on Link 1,AP 2(the reporting AP)includes a Quiet element in the Per-STA Profile subelement corresponding to AP 1in the Basic Multi-Link element carried in its Beacon frames.Although not shown in the figure 14,Quiet element will also be included in the Per-STA Profile subelement of the Basic Multi-Link element corresponding to AP 1carried in the Probe Response frames transmitted by AP 2.The values of the Quiet Count field,Quiet Offset field,and the Quiet Duration field of the Quiet element carried on Link 2are set by AP 2with reference to Link 1.As the value of the Beacon Interval for AP 2is greater than the value of beacon interval for AP 1,the Quiet Count field of the Quiet element carried in the Per-STA Profile subelement corresponding to AP 1is decremented at a faster rate(i.e.,2in this example)in every subsequent beacon transmitted by AP 2.A non-AP STA affiliated with a non-AP MLD,which is capable of operating on Link 2,transmits a(Re-)Association Request frame to AP 2(not shown in the figure),in order to perform ML setup.The ML setup includes Link 1as one of the links.Since the(Re)Association Response frame is transmitted by AP 2after the quiet interval has started on Link 1,AP 2includes the Quiet element in the per-STA profile corresponding to AP 1in the(Re)Association Response frame it transmits.The Quiet Count field of the Quiet element carried in the(Re)Association Response frame is set to 128to indicate that the quiet interval on Link 1started in the beacon interval that occurred one TBTT in the past on Link 1(see Quiet element))。.

[0201] Figure 15 is an example diagram of an AP carrying a channel handover announcement element to signal a channel handover on another link. Figure 15 shows two APs, AP 1 and AP 2, attached to the same AP MLD and operating on link 1 and link 2 respectively. AP 1 (the affected AP) transmits a channel handover announcement element in its beacon frame to indicate that the channel on link 1 will be switched. From this point until the channel handover on link 1, AP 2 (the reporting AP) includes a channel handover announcement element in the per-STA profile sub-element of the Basic Multilink Element carried in its transmitted beacon frames, corresponding to AP 1. When AP 1 begins to include channel handover announcement elements in its beacon frames, the BSS parameter change count sub-field of the Simplified Neighbor Report element carried in AP 2's beacon frames, corresponding to AP 1's TBTT information field, is incremented by 1. The value of the channel handover count field in the channel handover announcement element carried on link 2 is set by AP 2 with reference to link 1. Because the beacon spacing of AP 2 is twice that of AP 1, the channel handover count field of the channel handover announcement element transmitted by AP 2 in each subsequent beacon is decremented by 2. If AP 1 carries an extended channel handover announcement element and a maximum channel handover time element in its transmitted beacon frames, AP 2 will also include the extended channel handover announcement element and the maximum channel handover time element in the per-STA profile corresponding to AP 1 for the basic multilink element carried in its transmitted beacon frames. Although not shown in the figure, the channel handover announcement element, the extended channel handover announcement element (if included by AP 1), and the maximum channel handover time element (if included by AP 1) will also be included in the per-STA profile sub-element corresponding to the basic multilink element of AP 1 in the probe response frame transmitted by AP 2. The non-AP STA attached to the non-AP MLD, operating on link 2, sends a (re)association request frame (not shown in the figure) to AP 2, requesting that link 1 be included as one of the links in the multilink setup. Since the (re)association response frame is transmitted by AP 2 after the last beacon frame of the initial working class / channel on Link 1 and before the first beacon transmission of the new working class / channel, AP 2 includes in its transmitted (re)association response frame the maximum channel switch time element corresponding to the per-STA profile of AP 1. The value carried in the maximum channel switch time element provides the estimated time of the first TBTT of the new channel on Link 1. Non-AP STAs attached to the non-AP MLD and operating on Link 1 will not transmit frames until they hear the first beacon frame of AP 1 on Link 1 (Figure 15 (Example of an AP carrying a Channel Switch Announcement element to signal channel)).switching on another link)illustrates two APs,AP 1and AP 2,that are affiliated with the same AP MLD and operate on Link 1and Link 2,respectively.The Beacon frame transmitted by AP 1(the affected AP)includes a Channel Switch Announcement element to indicate that the channel on Link 1will be switched.From this point onward and until the channel on Link 1switches,AP 2(the reporting AP)includes a Channel Switch Announcement element in the per-STA profile corresponding to AP 1in the Basic Multi-Link element carried in the Beacon frame it transmits.When AP 1begins to include the Channel Switch Announcement element in its Beacon frames,the BSS Parameters Change Count subfield in the TBTT Information field corresponding to AP 1in the Reduced Neighbor Report element carried in AP 2’s Beacon frames is incremented by 1.The values of the Channel Switch Count field of the Channel Switch Announcement element carried on Link 2are set by AP 2with reference to Link 1.As the value of the beacon intervalfor AP 2is twice the value of beacon interval for AP 1,the Channel Switch Count field of the Channel Switch Announcement element is decremented by 2in every subsequent beacon transmitted by AP 2.If AP 1carries the Extended Channel Switch Announcement element and the Max Channel Switch Time element in the Beacon frame its transmits,AP 2also includes the Extended Channel Switch Announcement element and the Max Channel Switch Time element in the per-STA profile corresponding to AP 1in the Basic Multi-Link element in the Beacon frames it transmits.Although not shown in the figure,the Channel Switch Announcement element,Extended Channel Switch Announcement element(if included by AP 1),and Max Channel Switch Time element(if included by AP 1)will also be included in the Per-STA Profile subelement of the Basic Multi-Link element corresponding to AP 1carried in the Probe Response frames transmitted by AP 2.A non-AP STA affiliated with a non-AP MLD,that operates on Link 2,transmitsa (Re)Association Request frame to AP 2 (not shown in the figure) requesting Link 1 as one of the links for ML setup. Since the (Re)Association Response frame is transmitted by AP 2 after the last Beacon frame on the initial operating class / channel on Link 1 and before the first beacon on the new operating class / channel is transmitted, AP 2 includes the Max Channel Switch Time element in the per-STA profile corresponding to AP 1 in the (Re)Association Response frame it transmits. The value carried in Max Channel Switch Time element provides an estimate of time until the first TBTT on the new channel on Link 1. The non-AP STA affiliated with the non-AP MLD operating on Link 1 does not transmit a frame until it hears the first Beacon frame from AP 1 on Link 1).

[0202] Frame with multi-link aggregation addressing

[0203] Each AP affiliated with an AP MLD shall schedule: the transmission of the buffered group addressed Management frames (see Bufferable MMPDUs) independently from the transmission of buffered group addressed Management frames of other AP(s) affiliated with the same AP MLD; and the transmission of the buffered group addressed Data frames that are expected to be received by a non-AP MLD in all the enabled links setup with the non-AP MLD.

[0204] An example of a cross-link group addressed BU indication is shown in Example of cross-link group address BU indication.

[0205] Figure 16 is an example diagram of APs attached to AP MLD. Each attached AP shown in Figure 16 belongs to multiple BSSID sets. Figure 17 is an example diagram of group address BU indications in a partial virtual bitmap corresponding to transmitted BSSIDs in multiple BSSID sets sent by APs attached to AP MLD. Figures 16 and 17 show an example of group address BU indications in a partial virtual bitmap sent by AP (AP-11) attached to AP MLD (AP MLD 1). In this example, AP MLD 1 has three attached APs: AP-11, AP-12, and AP-13. AP-11 operates on link 1 and corresponds to transmitted BSSIDs (denoted by [T]) in multiple BSSID sets including AP-21 attached to AP MLD 2 and AP-31 attached to AP MLD 3, and the maximum possible number of BSSIDs (2^n) in this multiple BSSID set is equal to 4. AP-12 operates on link 2 and is in a multiple BSSID set that also includes AP-32 attached to AP MLD 3. AP-13 operates on link 3 and is in a set of multiple BSSIDs that also includes AP-23, which is attached to AP MLD 2. The Group Address BU Indicator Index is contained in the Group Address BU Indicator Index subfield of the EHT Operation Parameters field sent by AP-11; it is equal to 1, and then N = 2^(Group Address BU Indicator Index + 1) - 1 = 3. As shown in Figure 17, bits 1 and 2 of the bitmap (values ​​0 or 1, marked "x") are used to indicate that one or more group address frames have been buffered for AP-21 and AP-31, corresponding to BSSIDs that have not been transmitted. Bits 4 and 5 of the bitmap (values ​​x, x = 0 or 1) are used to indicate that one or more group address frames have been buffered for AP-12 and AP-13, which are attached to AP MLD 1. Bit 7 of the bitmap (values ​​0 or 1, marked "x") is used to indicate that one or more group address frames have been buffered for AP-23, which is attached to AP MLD 2. Bit 10 of the bitmap is used to indicate that one or more group address frames are buffered by AP-32, which is associated with AP MLD 3. The other bits of the bitmap, used to indicate group addresses (BUs), are set to 0 (reserved). (Figure 16 and Figure 17 show an example of group addressed BU indication in a Partial Virtual Bitmap field sent by an AP (AP-11) associated with an AP MLD (AP MLD 1). In this example, AP MLD 1 has three affiliated APs: AP-11, AP-12, and AP-13.)AP-11operates on link 1,and corresponds to the transmitted BSSID(shown with[T])of a multiple BSSID set that also includes AP-21 affiliated with AP MLD 2and AP-31affiliated with AP MLD 3,and the maximum possible number of BSSIDs(2n)in this multiple BSSID set is equal to 4.AP-12operates on link 2,and is in a multiple BSSID set that also includes AP-32affiliated with AP MLD 3.AP-13operates on link 3,and in a multiple BSSID set that also includes AP-23affiliated with AP MLD 2.The group addressed BU indication exponent is carried in the Group Addressed BU Indication Exponent subfield of the EHT Operation Parameters field sent by AP-11and it is equal to 1,then N=2^(Group Addressed BU Indication Exponent+1)–1=3.As shown in Figure 17,the bits 1to 2(with a value of 0or 1,marked as“x”)of the bitmap are used to indicate that one or more group addressed frames are buffered for AP-21and AP-31corresponding to a nontransmitted BSSID,respectively.Bits 4 and 5 (with the value of x, x=0 or 1) of the bitmap are used to indicate that one or more group addressed frames are buffered for AP-12 and AP-13 affiliated with AP MLD 1, respectively. Bit 7 (with a value of 0 or 1, marked as "x") of the bitmap is used to indicate that one or more group addressed frames are buffered for AP-23 affiliated with AP MLD 2. Bit 10 of the bitmap is used to indicate that one or more group addressed frames are buffered for AP-32 affiliated with AP MLD 3. The other bits of the bitmap for the indication of group addressed BUs are set to 0 (reserved)).

[0206] Integrated millimeter-wave link

[0207] This amendment defines the amendments to IEEE Std 802.11 TMStandardization modifications to the physical layer and IEEE Std 802.11 MAC allow WLANs to use non-independent operation based on single-user (SU) orthogonal frequency division multiplexing (OFDM) transmissions in the unlicensed frequency bands from 42 GHz to 71 GHz. The amendment requires that IEEE 802.11-compliant devices also support at least one of the unlicensed frequency bands from 2.4 GHz to 7.25 GHz (sub-7.25 GHz). The amendment extends the multi-link operation defined in the sub-7.25 GHz band specification to support non-independent operation in the 42 GHz to 71 GHz unlicensed frequency bands. TM physical layer(PHY)and the IEEE Std 802.11 Medium Access Control(MAC)that allows Wireless Local Area Network(WLAN)non-standalone operation in unlicensed bands between 42GHz and 71GHz using single-user(SU)Orthogonal Frequency Division Multiplexing(OFDM)based transmissions.The amendment requires that an IEEE 802.11device supporting this amendment also supports at least one of the 2.4GHz to 7.25GHz (sub-7.25GHz) unlicensed bands. The amendment expands the multi-link operation defined in the sub-7.25GHz band specifications to support non-standalone operation in the unlicensed bands between 42GHz and 71GHz).

[0208] This amendment leverages or reuses existing PHY and MAC specifications defined for operation in the sub-7.25 GHz bands, such as the single-user transmission PHY Protocol Data Unit (PPDU) format and MAC frames, and defines bandwidth modes operating in non-overlapping channels.

[0209] This amendment provides coexistence mechanisms with legacy IEEE 802 devices operating in the unlicensed bands between 42 GHz and 71 GHz.

[0210] Integrating sub-7GHz and millimeter-wave technologies is necessary to reduce connection loss / increase reliability (e.g., due to millimeter-wave link blockage) and to save power.

[0211] One approach is to define a light beacon on the millimeter-wave link. The light beacon is not used for association or BSS management. Instead, it is used for reachability decisions, channel selection for millimeter-wave APs, and smooth roaming.

[0212] Another approach is to not define a millimeter-wave beacon: Reachability decision through a non-mmWave link; Beamforming before association; No beacon on the mmWave link; TSF defined based on another active link or without the beacon transmission.

[0213] The absence of a defined millimeter-wave beacon can be understood as assuming that there is no beacon-like MGMT frame on mmWave AP(s).

[0214] A sub-7 GHz beacon frame provides a millimeter-wave band for association by non-AP STAs. Association is only permitted from a specific millimeter-wave band.

[0215] A sub-7-GHz beacon frame provides a millimeter-wave band for non-AP STAs to receive a parameter (or token or security code). The non-AP STA uses this parameter for association in any of the links.

[0216] As described above, in scenarios where millimeter-wave links are integrated into multi-link devices, the AP MLD may not send beacon frames on the millimeter-wave link, or it may send light beacon frames (or SMS beacon frames). Therefore, how the non-AP MLD communicates with the AP MLD in this scenario becomes a problem to be solved. For example, in the scenario where the AP MLD does not send beacon frames on the millimeter-wave link, how the non-AP MLD obtains the AP MLD's millimeter-wave link capability information and operating parameters is a problem that needs to be solved. As another example, in the scenario where the AP MLD sends light beacon frames on the millimeter-wave link, how to implement link management is a problem that needs to be solved.

[0217] To address the aforementioned issues, this application provides a technical solution for communication between AP MLD and non-AP MLD in scenarios where millimeter-wave links are integrated in multi-link devices. The method embodiments of this application will be described below first.

[0218] Figure 18 is a flowchart illustrating the communication method provided in an embodiment of this application. The method shown in Figure 18 is described from the perspective of the interaction between the first AP MLD and the first non-AP MLD. The method shown in Figure 18 includes step S1810, which will be described below.

[0219] In step S1810, the first AP MLD communicates with the first non-AP MLD.

[0220] In this embodiment, the first AP MLD can support the millimeter-wave band. Alternatively, the first AP MLD is a multi-link device that supports the millimeter-wave band.

[0221] In some embodiments, to reduce equipment costs and simplify implementation, the first AP MLD can be implemented as an AP MLD comprising one or more auxiliary APs corresponding to one or more millimeter-wave links and one or more auxiliary APs corresponding to one or more non-millimeter-wave links. For example, the first AP MLD can be implemented as an AP MLD comprising one AP corresponding to one millimeter-wave link and one AP corresponding to one non-millimeter-wave link. As another example, the first AP MLD can be implemented as an AP MLD comprising one AP corresponding to one millimeter-wave link and multiple auxiliary APs corresponding to multiple non-millimeter-wave links. As another example, the first AP MLD can be implemented as an AP MLD comprising multiple auxiliary APs corresponding to multiple millimeter-wave links and one AP corresponding to one non-millimeter-wave link. As another example, the first AP MLD can be implemented as an AP MLD comprising multiple auxiliary APs corresponding to multiple millimeter-wave links and multiple auxiliary APs corresponding to multiple non-millimeter-wave links.

[0222] In some embodiments, a first AP MLD may include multiple auxiliary APs. Some of these auxiliary APs correspond to millimeter-wave links, while others correspond to non-millimeter-wave links. For example, a first AP MLD may include a first auxiliary AP and a second auxiliary AP. The first auxiliary AP corresponds to the millimeter-wave link of the first AP MLD. The second auxiliary AP corresponds to the non-millimeter-wave link of the first AP MLD.

[0223] In some embodiments, the first affiliated AP may include one or more APs.

[0224] In some embodiments, the second auxiliary AP may include one or more APs.

[0225] In some embodiments, the first non-AP MLD may support millimeter-wave bands. Alternatively, the first non-AP MLD is a multi-link device that supports millimeter-wave bands.

[0226] In some embodiments, to reduce equipment costs and simplify implementation, the first non-AP MLD can be implemented as a non-AP MLD comprising one or more subsidiary non-AP STAs corresponding to one or more millimeter-wave links and one or more subsidiary non-AP STAs corresponding to one or more non-millimeter-wave links. For example, the first non-AP MLD can be implemented as a non-AP MLD comprising one subsidiary non-AP STA corresponding to one millimeter-wave link and one subsidiary non-AP STA corresponding to one non-millimeter-wave link. As another example, the first non-AP MLD can be implemented as a non-AP MLD comprising one subsidiary non-AP STA corresponding to one millimeter-wave link and multiple subsidiary non-AP STAs corresponding to multiple non-millimeter-wave links. As yet another example, the first non-AP MLD can be implemented as a non-AP MLD comprising multiple subsidiary non-AP STAs corresponding to multiple millimeter-wave links and one non-AP STA corresponding to one non-millimeter-wave link. For example, the first non-AP MLD can be implemented as a non-AP MLD that includes multiple auxiliary non-AP STAs corresponding to multiple millimeter-wave links and multiple auxiliary non-AP STAs corresponding to multiple non-millimeter-wave links.

[0227] In some embodiments, a first non-AP MLD may include a plurality of subsidiary non-AP STAs. Some of these subsidiary non-AP STAs correspond to millimeter-wave links, while others correspond to non-millimeter-wave links. For example, a first non-AP MLD may include a first subsidiary non-AP STA and a second subsidiary non-AP STA. The first subsidiary non-AP STA corresponds to the millimeter-wave link of the first non-AP MLD. The second subsidiary non-AP STA corresponds to the non-millimeter-wave link of the first non-AP MLD.

[0228] In some embodiments, the first associated non-AP STA may include one or more non-AP STAs.

[0229] In some embodiments, the second associated non-AP STA may include one or more non-AP STAs.

[0230] In some embodiments, the millimeter-wave link may include a high-frequency link.

[0231] In some embodiments, the millimeter-wave link may include a link operating in a frequency band higher than 7.25 GHz. For example, the millimeter-wave link may include a link operating in the 42 GHz to 71 GHz frequency band.

[0232] As an example, millimeter-wave links can include links in the 60 GHz band.

[0233] As another example, millimeter-wave links can include links in the 28 GHz band.

[0234] In some embodiments, a non-millimeter-wave link may include a low-frequency link. For example, a non-millimeter-wave link may include a link in a frequency band below 7.25 GHz (i.e., sub-7.25 GHz). Exemplarily, a non-millimeter-wave link may include one or more of the following: a link in the 2.4 GHz band, a link in the 5 GHz band, and a link in the 6 GHz band.

[0235] As an example, non-millimeter wave links can include links in the 2.4 GHz band.

[0236] As another example, non-millimeter-wave links can include links in the 5GHz band.

[0237] As yet another example, non-millimeter-wave links can include links in the 6 GHz band.

[0238] As yet another example, non-millimeter-wave links can include links in the 2.4 GHz band and links in the 5 GHz band.

[0239] As yet another example, non-millimeter-wave links can include links in the 2.4 GHz band and links in the 6 GHz band.

[0240] As yet another example, non-millimeter-wave links can include links in the 5 GHz band and links in the 6 GHz band.

[0241] As yet another example, non-millimeter-wave links can include links in the 2.4 GHz band, links in the 5 GHz band, and links in the 6 GHz band.

[0242] In some embodiments, the first and second affiliated APs included in the first AP MLD belong to the same physical device or are located in the same physical location. That is, all affiliated APs included in the first AP MLD (including affiliated APs corresponding to millimeter-wave links and those not corresponding to millimeter-wave links) belong to the same physical device or are located in the same physical location. In this case, the first AP MLD can also be called or understood as the first co-located AP MLD. Deploying the first AP MLD as the first co-located AP MLD is simple to implement and flexible in deployment.

[0243] Figure 19 shows an example diagram of a first co-located AP MLD. As shown in Figure 19, the first co-located AP MLD includes N affiliated APs (i.e., AP 1 to AP N). AP 1 is an affiliated AP corresponding to a non-millimeter-wave link. AP N is an affiliated AP corresponding to a millimeter-wave link. APs not shown in Figure 19 can be affiliated APs corresponding to millimeter-wave links or affiliated APs corresponding to non-millimeter-wave links. AP 1 to AP N shown in Figure 19 all belong to the same physical device or are located in the same physical location.

[0244] In some embodiments, multiple first co-located AP MLDs can coordinate the management of one or more APs corresponding to millimeter-wave links. In this case, a first AP MLD can dynamically perform one or more of the following operations: add one or more affiliated APs corresponding to millimeter-wave links that do not belong to the same physical device (or are not located in the same physical location) and / or belong to one or more affiliated APs corresponding to millimeter-wave links of another first AP MLD; delete one or more affiliated APs corresponding to millimeter-wave links that do not belong to the same physical device (or are not located in the same physical location) and / or belong to one or more affiliated APs corresponding to millimeter-wave links of another first AP MLD; enable one or more affiliated APs corresponding to millimeter-wave links that do not belong to the same physical device (or are not located in the same physical location) and / or belong to one or more affiliated APs corresponding to millimeter-wave links of another first AP MLD; disable one or more affiliated APs corresponding to millimeter-wave links that do not belong to the same physical device (or are not located in the same physical location) and / or belong to one or more affiliated APs corresponding to millimeter-wave links of another first AP MLD.

[0245] Because millimeter waves have weak penetration and short transmission distances, while non-millimeter wave links (such as low-frequency links) have longer transmission distances, the actual deployment density of APs corresponding to millimeter wave links is higher than that of APs corresponding to non-millimeter wave links. If one or more non-millimeter wave link APs must always be deployed in the same physical device when deploying APs corresponding to millimeter wave links, it leads to higher usage costs. Therefore, to reduce costs, in some embodiments, one or more APs corresponding to non-millimeter wave links (such as low-frequency links) can be combined with one or more APs corresponding to millimeter wave links that are not in the same physical device or in the same physical location to form a first AP MLD. In this case, the first AP MLD can also be called or understood as a first non-co-located AP MLD.

[0246] Figures 20 and 21 show example diagrams of a first non-co-located AP MLD. As shown in Figure 20, the first non-co-located AP MLD includes M affiliated APs (i.e., AP 1 to AP M). AP 1 to AP N are affiliated APs corresponding to non-millimeter-wave links. AP M is an affiliated AP corresponding to a millimeter-wave link. AP 1 to AP N can belong to the same physical device or be located in the same physical location, while AP M does not belong to the same physical device or be located in the same physical location as AP 1 to AP N. As shown in Figure 21, the first non-co-located AP MLD includes M affiliated APs (i.e., AP 1 to AP M). AP 1 is an affiliated AP corresponding to a non-millimeter-wave link. AP N is an affiliated AP corresponding to a millimeter-wave link. The other APs between AP 1 and AP N can be affiliated APs corresponding to millimeter-wave links or affiliated APs corresponding to non-millimeter-wave links. AP M is an affiliated AP corresponding to a millimeter-wave link. AP 1 to AP N can belong to the same physical device or be located in the same physical location, while AP M does not belong to the same physical device or be located in the same physical location as AP 1 to AP N.

[0247] In some embodiments, the first auxiliary AP (i.e., the millimeter-wave link AP) does not transmit beacon frames. In other embodiments, the first auxiliary AP is used to transmit beacon frames on the millimeter-wave link corresponding to the first auxiliary AP. For example, the first auxiliary AP may transmit short beacon frames or light beacon frames on the millimeter-wave link corresponding to the first auxiliary AP. The following describes the scenarios where the first auxiliary AP does not transmit beacon frames and where the first auxiliary AP transmits short beacon frames or light beacon frames.

[0248] Example 1: The first auxiliary AP does not send beacon frames.

[0249] In some embodiments, to simplify implementation and reduce equipment costs, the first auxiliary AP does not send beacon frames.

[0250] In some embodiments, the first auxiliary AP is not used to implement one or more of the following functions: time synchronization, link discovery, link establishment, and link management. For example, if the first auxiliary AP does not send beacon frames, it is not used to implement functions related to time synchronization, link discovery, link establishment, and link management. Similarly, if the first auxiliary AP does not send beacon frames, it is not used to implement functions related to time synchronization, link discovery, and link establishment. Furthermore, if the first auxiliary AP does not send beacon frames, it is not used to implement time synchronization. It should be noted that the first auxiliary AP may not implement any one or more of the above functions; for the sake of brevity, they will not be listed here.

[0251] In some embodiments, the first auxiliary AP is not used to send (or does not send) one or more of the following frames: beacon frame, probe response frame, association response frame, reassociation response frame, authentication frame, deauthentication frame, deassociation frame, channel switch announcement frame, extended channel switch announcement frame, operating mode notification frame, etc.

[0252] Accordingly, the first auxiliary non-AP STA is not used to receive (or does not receive) one or more of the following frames: beacon frame, probe response frame, association response frame, reassociation response frame, authentication frame, deauthentication frame, deassociation frame, channel switching notification frame, extended channel switching notification frame, and operation mode notification frame.

[0253] For example, the first auxiliary AP is not used to transmit beacon frames. Accordingly, the first auxiliary non-AP STA is not used to receive beacon frames.

[0254] For example, the first auxiliary AP is not used to send probe response frames. Accordingly, the first auxiliary non-AP STA is not used to receive probe response frames.

[0255] For example, the first auxiliary AP is not used to transmit beacon frames and associated response frames. Accordingly, the first auxiliary non-AP STA is not used to receive beacon frames and associated response frames.

[0256] For example, the first auxiliary AP is not used to transmit beacon frames, channel handover notification frames, extended channel handover notification frames, and operation mode notification frames. Accordingly, the first auxiliary non-AP STA is not used to receive beacon frames, channel handover notification frames, extended channel handover notification frames, and operation mode notification frames.

[0257] It should be noted that the first auxiliary AP may not be used to transmit any one or more of the above frames, and correspondingly, the first auxiliary non-AP STA may not be used to receive any one or more of the above frames. For the sake of brevity, they will not be listed here one by one.

[0258] In some embodiments, the first auxiliary non-AP STA is not used to send one or more of the following frames: probe request frame, association request frame, reassociation request frame, authentication frame, deauthentication frame, deassociation frame, operation mode notification frame, etc.

[0259] Accordingly, the first auxiliary AP is not used to receive one or more of the following frames: probe request frame, association request frame, reassociation request frame, authentication frame, deauthentication frame, deassociation frame, operation mode notification frame, etc.

[0260] For example, the first affiliated non-AP STA is not used to send probe request frames. Accordingly, the first affiliated AP is not used to receive probe request frames.

[0261] For example, the first affiliated non-AP STA is not used to send reassociation request frames. Accordingly, the first affiliated AP is not used to receive reassociation request frames.

[0262] For example, the first auxiliary non-AP STA is not used to send probe request frames and operation mode notification frames. Accordingly, the first auxiliary AP is not used to receive probe request frames and operation mode notification frames.

[0263] For example, the first affiliated non-AP STA is not used to send association request frames, reassociation request frames, and deassociation frames. Accordingly, the first affiliated AP is not used to receive association request frames, reassociation request frames, and deassociation frames.

[0264] It should be noted that the first affiliated non-AP STA may not be used to transmit any one or more of the above frames, and correspondingly, the first affiliated AP may not be used to receive any one or more of the above frames. For the sake of brevity, they will not be listed here one by one.

[0265] It should also be noted that the above "not used for transmission" and / or "not used for reception" can be understood as the first auxiliary AP and / or the first non-AP STA not having the function (or capability) to transmit and / or receive the above frames on the millimeter-wave link.

[0266] Example 2: The first auxiliary AP sends a beacon frame.

[0267] In some embodiments, the first auxiliary AP can be used to transmit beacon frames on the millimeter-wave link corresponding to the first auxiliary AP, that is, the first auxiliary AP has the function (or capability) to transmit beacon frames on the millimeter-wave link corresponding to the first auxiliary AP.

[0268] In some embodiments, the beacon frames transmitted by the first auxiliary AP on the millimeter-wave link are short message beacon frames or light beacon frames to simplify implementation and reduce equipment costs.

[0269] This application does not limit the structure of the beacon frame in its embodiments. For example, Figure 22 shows an example of a beacon frame (such as a text message beacon frame or a light beacon frame). As shown in Figure 22, the beacon frame may include one or more of the following fields: frame control field, duration field, Basic Service Set Identifier (BSSID) field, frame body field, and frame check sequence (FCS) field.

[0270] In some embodiments, a beacon frame (such as the frame body of a beacon frame) may include one or more of the following fields: timestamp field, beacon interval field, transmit sector and / or beam information field, transmit power control element (TPC Report element), service set identifier element (SSID element), country element, power constraint element, QoS capability element, robust security network element (RSNE), enhanced distributed access parameter set element (EDCA Parameter Set element), extended capabilities element, transmit power envelope element, reduced neighbor report element, robust security network extension element (RSN extension element, RSNXE), integrated millimeter wave capabilities element (IMMW Capabilities element), integrated millimeter wave operation element (IMMW Operation element), vendor specific element, and management frame message integrity verification element (MME).

[0271] For example, a beacon frame (such as the beacon frame body) includes: a timestamp field, a beacon interval field, a transmit sector and / or beam information field, a transmit power control element, a service set identifier element, an integrated millimeter wave capability element, and an integrated millimeter wave operation element.

[0272] For example, a beacon frame (such as the beacon frame body) includes: a timestamp field, a beacon interval field, a transmit sector and / or beam information field, a transmit power control element, a service set identifier element, a robust and secure network element, an enhanced distributed access parameter set element, an integrated millimeter wave capability element, and a vendor-defined element.

[0273] For example, a beacon frame (such as the beacon frame body) includes: a timestamp field, a beacon interval field, a transmit sector and / or beam information field, a transmit power control element, a service set identifier element, a country element, a power limit element, a quality of service capability element, a robust and secure network element, an enhanced distributed access parameter set element, an extended capability element, a transmit power envelope element, a simplified neighbor report element, a robust and secure network extension element, an integrated millimeter wave capability element, an integrated millimeter wave operation element, a vendor-defined element, and a management frame message integrity check element.

[0274] Taking a beacon frame as an example of a text message label frame, in some embodiments, the frame body of the text message label frame may carry one or more of the following: timestamp field, beacon interval field, vendor-defined element, management frame message integrity verification element, transmission sector and / or beam information field, and transmission power control element.

[0275] For example, the frame body of an SMS beacon frame can carry a timestamp field and a beacon interval field, but not the capability information and operating parameters of the corresponding auxiliary access point.

[0276] For example, the frame body of an SMS frame can carry a timestamp field, a beacon interval field, vendor-defined elements, and elements for managing frame message integrity verification.

[0277] For example, the frame body of a text message frame may carry a timestamp field, a beacon interval field, a transmission sector and / or beam information field, and a transmission power control element.

[0278] For example, the frame body of a text message frame may carry a timestamp field, a beacon interval field, a transmission sector, and / or a beam information field.

[0279] For example, the frame body of an SMS frame can carry a timestamp field, a beacon interval field, and a transmission power control element.

[0280] Figure 23 illustrates an example of a transmit sector and / or beam information field. As shown in Figure 23, the transmit sector and / or beam information field may include one or more of the following subfields: Direction subfield, countdown (CDOWN) subfield, sector ID subfield, antenna ID subfield, quasi-omni TX subfield, next beacon subfield, and transmit sector sweep (TXSS) span subfield.

[0281] The direction subfield can be used to indicate the sender of the SMS frame. As one implementation, if the direction subfield is set to the first value (e.g., 0), it indicates that the SMS frame was sent by the initiator of beamforming; if the direction subfield is set to the second value (e.g., 1), it indicates that the SMS frame was sent by the responder of beamforming.

[0282] The CDOWN subfield is a down counter indicating the number of remaining beacon frame transmissions by the end of the transmit sector sweep (TXSS) procedure. This subfield is set to 0 in the last beacon transmission. Possible values ​​for this subfield range from 0 to 511.

[0283] The Sector ID subfield is set to indicate the sector number through which the frame containing this SSW field is transmitted.

[0284] The Antenna ID subfield can be used to indicate the antenna the transmitter is currently using for this transmission.

[0285] The Quasi-Omnidirectional Transmit subfield can be used to indicate the antenna mode applicable to the SMS frame. In one implementation, the Quasi-Omnidirectional Transmit subfield is set to a first value (e.g., 1) to indicate that the frame containing this field is transmitted using a quasi-omnidirectional antenna mode; the Quasi-Omnidirectional Transmit subfield is set to a second value (e.g., 0) to indicate that the frame is not transmitted using a quasi-omnidirectional antenna mode.

[0286] The next beacon subfield can be used to indicate the number of beacon intervals after the current beacon interval when a beacon frame will not be transmitted.

[0287] The TXSS span subfield can be used to indicate the number of beacon intervals required for the STA transmitting the beacon frame to complete the TXSS procedure. In some embodiments, the value of the TXSS span subfield is always greater than or equal to 1.

[0288] In some embodiments, light beacon frames may not be used for association and / or BSS management.

[0289] In some embodiments, light beacon frames can be used for one or more of the following: reachability decisions, channel selection for millimeter-wave APs, smooth roaming, etc.

[0290] In some embodiments, the first auxiliary AP may be used to implement one or more of the following functions: time synchronization, partial or full link discovery, and reachability.

[0291] As an example, the first auxiliary AP is used to implement time synchronization functionality.

[0292] As another example, the first auxiliary AP is used to implement time synchronization and some link discovery functions.

[0293] As yet another example, the first auxiliary AP is used to implement time synchronization and full link discovery functions.

[0294] As yet another example, the first auxiliary AP is used to implement time synchronization, full link discovery, and reachability functions.

[0295] It should be noted that the first auxiliary AP can be used to implement any one or more of the above functions, and for the sake of brevity, they will not be listed here.

[0296] In some embodiments, the first auxiliary AP may not be used to implement one or more of the following functions: some or all of the link discovery function, reachability function, link establishment function, and link management function.

[0297] As an example, the first auxiliary AP is not used to implement link management functions.

[0298] As another example, the first auxiliary AP is not used to implement link establishment and link management functions. For instance, in a scenario where the first auxiliary AP is used to implement time synchronization, full link discovery, and reachability functions, the first auxiliary AP is not used to implement link establishment and link management functions.

[0299] As another example, the first auxiliary AP is not used to implement partial link discovery, reachability, link establishment, and link management functions. For instance, in a scenario where the first auxiliary AP is used to implement time synchronization and partial link discovery functions, it is not used to implement partial link discovery, reachability, link establishment, and link management functions.

[0300] As another example, the first auxiliary AP is not used to implement all link discovery, reachability, link establishment, and link management functions. For instance, in a scenario where the first auxiliary AP is only used to implement time synchronization, it is not used to implement all link discovery, reachability, link establishment, and link management functions.

[0301] It should be noted that the first auxiliary AP may not be used to implement any one or more of the above functions; for the sake of brevity, they will not be listed here.

[0302] In some embodiments, the first auxiliary AP used to implement partial link discovery functionality may include: the first auxiliary AP is used to implement basic link discovery functionality, but not to implement specific link capability discovery functionality.

[0303] In some embodiments, the first affiliated non-AP STA may send a probe request frame to the first affiliated AP. Correspondingly, the first affiliated AP may receive the probe request frame sent by the first affiliated non-AP STA. For example, when the first affiliated AP is used to implement time synchronization and full link discovery functions, or when the first affiliated AP is used to implement time synchronization, full link discovery, and reachability functions, the first affiliated non-AP STA may send a probe request frame to the first affiliated AP.

[0304] In some embodiments, the first affiliated AP may send a probe response frame to the first affiliated non-AP STA. Correspondingly, the first affiliated non-AP STA may receive the probe response frame sent by the first affiliated AP. For example, when the first affiliated AP is used to implement time synchronization and full link discovery functions, or when the first affiliated AP is used to implement time synchronization, full link discovery, and reachability functions, the first affiliated AP may send a probe response frame to the first affiliated non-AP STA.

[0305] As an example, if the first auxiliary AP is used to implement time synchronization and full link discovery functions, but does not implement link establishment and link management related functions, after the first auxiliary non-AP STA sends a probe request frame to the first auxiliary AP, the first auxiliary AP can send a probe response frame to the first auxiliary non-AP STA.

[0306] This application embodiment does not limit the fields included in the above-mentioned probe request frame. Exemplarily, the probe request frame includes one or more of the following fields: Service Set Identifier (SSID) element, Request element, Extended Capabilities element, Extended Request element, Integrated Millimeter Wave Capabilities element, Integrated Millimeter Wave Operation element, and Vendor Specific element. For example, the probe request frame includes a Service Set Identifier element. Another example is that the probe request frame includes an Extended Capabilities element. Yet another example is that the probe request frame includes a Service Set Identifier element, a Request element, and an Integrated Millimeter Wave Capabilities element. Yet another example is that the probe request frame includes a Service Set Identifier element, a Request element, an Extended Capabilities element, an Extended Request element, an Integrated Millimeter Wave Capabilities element, an Integrated Millimeter Wave Operation element, and a Vendor Specific element. It should be noted that the probe request frame may include any one or more of the above fields; for the sake of brevity, they will not be listed individually here.

[0307] This application embodiment does not limit the fields included in the above-mentioned probe response frame. For example, Figure 24 shows an example of a probe response frame. As shown in Figure 24, the probe response frame may include one or more of the following fields: frame control field, duration field, address 1 field, address 2 field, address 3 field, sequence control field, address 4 field, high throughput control field, frame body field, and frame sequence check field.

[0308] This application embodiment does not limit the fields included in the frame body of the probe response frame. For example, the probe response frame (such as the frame body of the probe response frame) may include one or more of the following fields: timestamp field, beacon interval field, capability information field, service set identifier element, country element, power limitation element, quality of service capability element, simplified neighbor report element, robust security network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, robust security network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and requested elements.

[0309] As an example, a probe response frame (such as the frame body of a probe response frame) includes a timestamp field, a beacon interval field, a capability information field, an integrated millimeter-wave capability element, and an integrated millimeter-wave operation element.

[0310] As another example, a probe response frame (such as the frame body of a probe response frame) includes a timestamp field, a beacon interval field, a capability information field, a service set identifier element, a country element, a power limit element, an integrated millimeter wave capability element, and a requested element.

[0311] As yet another example, a probe response frame (such as the frame body of a probe response frame) includes a timestamp field, a beacon interval field, a capability information field, a service set identifier element, a country element, a power limit element, a quality of service capability element, a simplified neighbor report element, a robust secure network element, an enhanced distributed access parameter set element, an extended capability element, a transmit power envelope element, a robust secure network extension element, an integrated millimeter wave capability element, an integrated millimeter wave operation element, a vendor-defined element, and a requested element.

[0312] It should be noted that the above examples are merely illustrations, and the probe response frame (such as the frame body of the probe response frame) can include any one or more of the above. For the sake of brevity, they will not be listed one by one here.

[0313] For ease of understanding, the following description will exemplarily illustrate Embodiment 2 by using the different functions implemented by the first auxiliary AP.

[0314] Example 2.1: The first auxiliary AP implements time synchronization function

[0315] To simplify implementation and reduce costs, the first auxiliary AP implements time synchronization but not link discovery, link establishment, or link management functions. For example, the first auxiliary AP sends short message beacon frames or light beacon frames, but does not send probe response frames, association response frames, reassociation response frames, authentication frames, deauthentication frames, deassociation frames, channel handover notification frames, extended channel handover notification frames, operating mode notification frames, etc. Correspondingly, the first auxiliary non-AP STA also does not send probe request frames, association request frames, reassociation request frames, authentication frames, deauthentication frames, deassociation frames, operating mode notification frames, etc.

[0316] In Example 2.1, the frame body of the SMS frame may carry a timestamp field and a beacon interval field, but not the capability information and operating parameters of the first auxiliary AP.

[0317] In Example 2.1, the frame body of the SMS frame may carry a timestamp field, a beacon interval field, a vendor-defined element, and an MME.

[0318] Example 2.2: The first auxiliary AP implements time synchronization and partial link discovery (or reachability) functions.

[0319] In some embodiments, to enable a first affiliated non-AP STA to discover a first affiliated AP, the first affiliated AP implements time synchronization and basic link discovery (or reachability) functions, but does not implement functions related to link capability discovery, link establishment, and link management. For example, in a scenario where the first affiliated AP is an affiliated AP of a non-co-located AP MLD (and similar scenarios apply where the first affiliated AP is an affiliated AP of a co-located AP MLD), the first affiliated AP implements time synchronization and basic link discovery (or reachability) functions, but does not implement functions related to link capability discovery, link establishment, and link management. Exemplarily, the first affiliated AP sends a short message beacon frame or a light beacon frame, but does not send probe response frames, association response frames, reassociation response frames, authentication frames, deauthentication frames, deassociation frames, channel switching notification frames, extended channel switching notification frames, operating mode notification frames, etc. Accordingly, the first affiliated non-AP STA also does not send probe request frames, association request frames, reassociation request frames, authentication frames, deauthentication frames, deassociation frames, operation mode notification frames, etc.

[0320] In some embodiments, the first auxiliary AP may periodically perform a TXSS procedure, sending a short message flag frame once in each sector during each TXSS procedure. The frame body of the short message flag frame may include, for example, a timestamp field, a beacon interval field, a transmission sector and / or beam information field, and a transmission power control element.

[0321] Example 2.3: The first auxiliary AP implements time synchronization and full link discovery functions.

[0322] In some embodiments, to enable the first affiliated non-AP STA to discover the first affiliated AP, the first affiliated AP implements time synchronization and link discovery functions (i.e., full link discovery functions), but does not implement link establishment and link management related functions. For example, in a scenario where the first affiliated AP is an affiliated AP of a non-co-located AP MLD (of course, the scenario where the first affiliated AP is an affiliated AP of a co-located AP MLD also applies), to enable the first affiliated non-AP STA to discover the first affiliated AP, the first affiliated AP implements time synchronization and link discovery functions (i.e., full link discovery functions), but does not implement link establishment and link management related functions. Exemplarily, the first affiliated AP sends a signal beacon frame (or light beacon frame) and / or a probe response frame, but does not send association response frames, reassociation response frames, authentication frames, deauthentication frames, deassociation frames, channel switching notifications, operating mode notifications, etc. Correspondingly, the first affiliated non-AP STA sends a probe request frame, but does not send association request frames, reassociation request frames, authentication frames, deauthentication frames, deassociation frames, operating mode notification frames, etc.

[0323] In some embodiments, the frame body of the SMS label frame and / or probe response frame and / or probe request frame carries basic capability information and operating parameters of the corresponding affiliated AP or affiliated non-AP STA, but does not carry link management related information. For example, the frame body of the SMS label frame and / or probe response frame and / or probe request frame does not carry one or more of the following: Channel Switch Announcement element, Extended Channel Switch Announcement element, Operating Mode Notification element, Target Wake-up Time element (TWT element), Traffic Indication Map element (TIM element), Multiple Basic Service Set Identifier (BSSID element), Multi-Link element, etc.

[0324] In Example 2.3, the frame body of the SMS tag frame may carry one or more of the following: timestamp field, beacon interval field, transmit sector and / or beam information field, transmit power control element, service set identifier element, country element, power limit element, quality of service capability element, robust security network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, simplified neighbor report element, robust security network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and MME.

[0325] In Example 2.3, the frame body of the probe response frame may carry one or more of the following: timestamp field, beacon interval field, capability information field, service set identifier element, country element, power limit element, quality of service capability element, simplified neighbor report element, robust security network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, robust security network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and requested element.

[0326] In Example 2.3, the frame body of the probe request frame may carry one or more of the following: service set identifier element, request element, extended capability element, extended request element, integrated millimeter wave capability element, integrated millimeter wave operation element, and vendor-defined element.

[0327] In some embodiments, the first auxiliary AP may periodically perform a TXSS procedure, sending a short message flag frame once in each sector during each TXSS procedure. The frame body of the short message flag frame may include, for example, a timestamp field, a beacon interval field, a sending sector and / or beam information field, a transmission power control element, a service set identifier element, a country element, a power limit element, a quality of service capability element, a robust security network element, an enhanced distributed access parameter set element, an extended capability element, a transmit power envelope element, a simplified neighbor report element, a robust security network extension element, an integrated millimeter wave capability element, an integrated millimeter wave operation element, a vendor-defined element, and an MME.

[0328] In some embodiments, the first AP MLD can send a first key to the first non-AP MLD via a second affiliated AP. This first key can be used for integrity protection of beacon frames (such as SMS beacon frames or light beacon frames) on the millimeter-wave link. As one implementation, the first AP MLD can send the first key to a second affiliated non-AP STA via the second affiliated AP, so that the first non-AP MLD can use the first key to perform integrity protection of beacon frames on the millimeter-wave link.

[0329] In some embodiments, the first key may include a beacon integrity group temporal key (BIGTK).

[0330] The previous section introduced whether the first auxiliary AP sends beacon frames on the millimeter-wave link. The following section introduces how to establish and manage the link.

[0331] In some embodiments, the first affiliated AP does not send link establishment-related frames. To establish a millimeter-wave link, the first non-AP MLD needs to send link establishment-related frames on the corresponding non-millimeter-wave link via the second affiliated non-AP STA. As one implementation, the method of this application may include: the second affiliated non-AP STA sending a first frame to the second affiliated AP. Correspondingly, the second affiliated AP receives the first frame sent by the second affiliated non-AP STA.

[0332] The first frame is a frame related to link establishment for the millimeter-wave link. Exemplarily, the first frame may include one or more of the following: an authentication frame, an association request frame, and a reassociation request frame. For example, the first frame may include an authentication frame. Or, for example, the first frame may include an association request frame. Or, for example, the first frame may include a reassociation request frame.

[0333] Correspondingly, the first AP MLD needs to transmit link establishment-related frames on the corresponding non-millimeter-wave link through the second affiliated AP. As one implementation, the method of this application may include: the second affiliated AP sending a second frame to the second affiliated non-AP STA. Correspondingly, the second affiliated non-AP STA receives the second frame sent by the second affiliated AP.

[0334] The second frame is a frame related to link establishment for the millimeter-wave link. Exemplarily, the second frame may include one or more of the following: an authentication frame, an association response frame, and a reassociation response frame. For example, the second frame may include an authentication frame. Another example is that the second frame may include an association response frame. Yet another example is that the second frame may include a reassociation response frame.

[0335] In some embodiments, the first frame transmitted by the second affiliated non-AP STA may include a multi-link element. This multi-link element may include one or more of the following: a complete profile of the first affiliated non-AP STA, or information for requesting a complete profile of the first affiliated AP. For example, the multi-link element may include a complete profile of the first affiliated non-AP STA. Alternatively, the multi-link element may include information for requesting a complete profile of the first affiliated AP. Yet another example is that the multi-link element includes both a complete profile of the first affiliated non-AP STA and information for requesting a complete profile of the first affiliated AP.

[0336] In some embodiments, the multi-link element includes the complete configuration of the first affiliated non-AP STA, so that the first AP MLD can obtain the complete configuration information of the first affiliated non-AP STA in the first non-AP MLD, including link management related information.

[0337] In some embodiments, the information described above for requesting the complete configuration of the first auxiliary AP is intended to allow the first AP MLD to send the complete configuration of the first auxiliary AP to the first non-AP MLD. For example, the information described above for requesting the complete configuration of the first auxiliary AP is intended to allow the first AP MLD to carry the complete configuration of the first auxiliary AP in the second frame.

[0338] In some embodiments, the second frame sent by the second affiliated AP may include a multi-link element. This multi-link element may include the complete configuration of the first affiliated AP. The inclusion of the complete configuration of the first affiliated AP in the multi-link element of the second frame sent by the second affiliated AP is intended to allow the first non-AP MLD to obtain the complete configuration information of the first affiliated AP, including link management related information, from the first AP MLD.

[0339] In some embodiments, the first affiliated AP does not send link management-related frames, such as one or more of the following: channel handover notification frames, extended channel handover notification frames, and operation mode notification frames. In this case, to manage the millimeter-wave link, the first AP MLD can send link management-related frames on the corresponding non-millimeter-wave link via the second affiliated AP. As one implementation, the method of this application may include: the second affiliated AP sending a third frame to the second affiliated non-AP STA. The third frame is a link management-related frame for the millimeter-wave link. The embodiments of this application do not limit the third frame. Exemplarily, the third frame may include one or more of the following: a channel handover notification frame, an extended channel handover notification frame, and an operation mode notification frame. For example, the third frame includes a channel handover notification frame. Another example is that the third frame includes an extended channel handover notification frame. Yet another example is that the third frame includes an operation mode notification frame.

[0340] In some embodiments, to avoid affecting legacy sites on non-millimeter-wave links, it is necessary to define new channel switch announcement frames (IMMW) for indicating channel switching on millimeter-wave links and operating mode notification frames (IMMW) for indicating operating mode switching on millimeter-wave links, such as defining new action frames.

[0341] In some embodiments, to indicate one or more specific millimeter-wave links, the third frame may include first indication information. This first indication information can be used to indicate a first affiliated AP (i.e., the target site). As one implementation, the third frame may include a Multi-Link Operation Link Information (MLO) element. This MLO element may contain the first indication information. Exemplarily, the MLO element may include a link identifier bitmap field containing the first indication information. However, this application embodiment is not limited to using a bitmap to indicate the first indication information; other methods, such as directly using a subfield to carry the first indication information (i.e., indicating the target site), are also possible.

[0342] In some embodiments, the second auxiliary AP needs to include a basic multilink element in the transmitted beacon frames and / or probe response frames. In some embodiments, the basic multilink element includes a per-STA profile subelement corresponding to the millimeter-wave link. The per-STA profile subelement may include a STA profile field. The STA profile field may carry one or more of the following: a channel handover notification element, an extended channel handover notification element, and an operating mode notification element.

[0343] In some embodiments, the individually addressed MMPDU should include a multi-link operation link information element. This multi-link operation link information element can be used to identify the intended link of the MMPDU and is placed as the last element, but before any vendor-defined elements (if any).

[0344] In some embodiments, other management frames used for group addressing of millimeter-wave links also require similar processing.

[0345] In some embodiments, the first non-AP MLD always sends a separately addressed millimeter-wave link operation mode notification frame, indicating a switch to the millimeter-wave link operation mode, to the first AP MLD on the corresponding non-millimeter-wave link via a second affiliated non-AP STA. That is, in some embodiments, the method of this application may include: the second affiliated non-AP STA sending a separately addressed fourth frame to the second affiliated AP. The fourth frame is the millimeter-wave link operation mode notification frame.

[0346] For ease of understanding, the following section provides an illustrative introduction to individual addressing and group addressing.

[0347] In some embodiments, the receiver address (RA) field or address 1 field in the frame header indicates a separate address, i.e., the MAC address of a specific STA. Such a frame is called a separately addressed frame. When applied to a MAC service data unit (MSDU), it is an MSDU with a separate address as the destination address (DA). When applied to a MAC protocol data unit (MPDU), it is an MPDU with a separate address in the address 1 field. This separate address is a MAC address in which the group bit is 0.

[0348] In some embodiments, the RA field or address 1 field in the frame header indicates the group address. Such a frame is called a group-addressed frame, also known simply as a multicast frame. When applied to an MSDU, it is an MSDU with a group address as the destination address. When applied to an MPDU, it is an MPDU with a group address in the Address 1 field. (Syn:multicast.) The aforementioned group address is the MAC address with the group bit value of 1, also known as a multicast address.

[0349] In some embodiments, during multi-link operation, group-addressed management frames are transmitted independently on each link, as described in the "Group-Addressed Frames in Multi-Link" section above. In other words, group-addressed management frames for one link are not transmitted on another link.

[0350] In some embodiments, one or more of the aforementioned channel switching notification frame, extended channel switching notification frame, and operation mode notification frame are group-addressed management frames, for example, the Address 1 field of the frame is set to the broadcast address.

[0351] In some embodiments, in order to make it easier for the first non-AP MLD to discover that the first AP MLD has a first affiliated AP, the first AP MLD may carry a Neighbor Report element in the fifth frame sent by the second affiliated AP. An example of the Neighbor Report element can be seen in Figure 25.

[0352] In some embodiments, the neighbor reporting element may include second indication information. This second indication information can be used to indicate that the first AP MLD supports millimeter-wave link operation or has (or has) a millimeter-wave link. As one implementation, the neighbor reporting element includes a BSSID information field, within which the second indication information is located; or, in other words, the BSSID information field contains the second indication information. Referring to the example in Figure 26, one of the nine reserved bits in the BSSID information field of the neighbor reporting element can be reserved to indicate support for millimeter-wave link operation or the presence of a millimeter-wave link.

[0353] This application does not limit the implementation of the second indication information indicating whether millimeter-wave link operation is supported or whether a millimeter-wave link is present. As one implementation, the second indication information may take a first value (e.g., 1) to indicate that millimeter-wave link operation is supported or a millimeter-wave link is present; or it may take a second value (e.g., 2) to indicate that millimeter-wave link operation is not supported or a millimeter-wave link is not present.

[0354] The embodiments of this application do not limit the fifth frame. Exemplarily, the fifth frame may include one or more of the following: association response frame, reassociation response frame, authentication frame, neighbor report response, BSS transition management response frame, BSS transition management request frame, and BSS transition management response frame.

[0355] In some embodiments, the fifth frame may include any of the above. For example, the fifth frame may include an associated response frame. Another example is that the fifth frame may include an authentication frame. Yet another example is that the fifth frame may include a BSS conversion management query frame.

[0356] In some embodiments, the fifth frame may include multiple components described above. For example, the fifth frame may include an association response frame and a re-association response frame. As another example, the fifth frame may include an association response frame, an authentication frame, and a neighbor report response. As another example, the fifth frame may include an association response frame, a re-association response frame, a BSS translation management query frame, a BSS translation management request frame, and a BSS translation management response frame. As another example, the fifth frame may include an association response frame, a re-association response frame, an authentication frame, a neighbor report response, a BSS translation management query frame, a BSS translation management request frame, and a BSS translation management response frame.

[0357] It should be noted that the above examples are merely illustrations, and the fifth frame may include any one or more of the above examples. For the sake of brevity, they will not be listed here one by one.

[0358] In some embodiments, when key parameters of the BSS established by the first affiliated AP change, it is necessary to notify the first affiliated non-AP STA associated with the first affiliated AP. If the first affiliated AP does not send a beacon frame or the sent beacon frame does not include link management information, this change information can be communicated to the first non-AP MLD by the second affiliated AP. Therefore, in some embodiments, the method of this application may include: the second affiliated AP sending a sixth frame to the second affiliated non-AP STA. The sixth frame may contain third indication information. This third indication information can be used to indicate that key parameters of the millimeter-wave link have been updated.

[0359] The embodiments of this application do not limit the sixth frame. Exemplarily, the sixth frame may be a beacon frame and / or a probe response frame.

[0360] This application does not limit the method by which the sixth frame indicates the third indication information. As one possible implementation, referring to FIG27, the sixth frame may include a per-STA profile field corresponding to the first affiliated AP. This per-STA profile field may include a capability information field. The critical update identifier field in this capability information field may contain the third indication information, that is, the critical update identifier field in the capability information field may indicate that the millimeter-wave link has a critical update. As another possible implementation, the sixth frame may include a capability information field, which may contain the third indication information. For example, referring to FIG28, a reserved bit in the capability information field may be used to indicate the third indication information, that is, a reserved bit in the capability information field may be used to indicate that the millimeter-wave link has a critical update.

[0361] This application does not limit the way in which the third indication information indicates that the key parameters of the millimeter-wave link have been updated. For example, if the value of the third indication information is a first value (such as 1), it means that the key parameters of the millimeter-wave link have been updated; if the value of the third indication information is a second value (such as 0), it means that the key parameters of the millimeter-wave link have not been updated.

[0362] The method embodiments of this application have been described in detail above. The apparatus embodiments of this application are described in detail below. It should be understood that the descriptions of the method embodiments correspond to the descriptions of the apparatus embodiments. Therefore, any parts not described in detail can be referred to the foregoing method embodiments.

[0363] Figure 29 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device 2900 shown in Figure 29 is a first AP MLD. The communication device 2900 includes a communication module 2910. The communication module 2910 can be used to communicate with the first non-AP MLD. The first AP MLD includes a first auxiliary AP and a second auxiliary AP. The first auxiliary AP corresponds to the millimeter-wave link of the first AP MLD, and the second auxiliary AP corresponds to the non-millimeter-wave link of the first AP MLD. The first non-AP MLD includes a first auxiliary non-AP STA and a second auxiliary non-AP STA. The first auxiliary non-AP STA corresponds to the millimeter-wave link of the first non-AP MLD, and the second auxiliary non-AP STA corresponds to the non-millimeter-wave link of the first non-AP MLD.

[0364] In this embodiment, the communication device 2900 can be used to execute some or all of the method steps performed by the first AP MLD in the above method embodiments. The communication device 2900 includes units or modules for executing the aforementioned method steps. The method flow has been described in detail in the foregoing embodiments. The modules in this embodiment have the same function or perform the same steps, and will not be described again here. However, those skilled in the art should know that the textual descriptions corresponding to the foregoing method embodiments can be incorporated into this embodiment and correspond to the modules in the communication device 2900.

[0365] In some embodiments, the communication module 2910 may be a transceiver 3130. The communication device 2900 may also include a processor 3110 and a memory 3120, as shown in FIG31.

[0366] Figure 30 is a schematic diagram of a communication device provided in another embodiment of this application. The communication device 3000 shown in Figure 30 is a first non-AP MLD. The communication device 3000 includes a communication module 3010. The communication module 3010 can be used to communicate with the first AP MLD. The first AP MLD includes a first auxiliary AP and a second auxiliary AP. The first auxiliary AP corresponds to the millimeter-wave link of the first AP MLD, and the second auxiliary AP corresponds to the non-millimeter-wave link of the first AP MLD. The first non-AP MLD includes a first auxiliary non-AP STA and a second auxiliary non-AP STA. The first auxiliary non-AP STA corresponds to the millimeter-wave link of the first non-AP MLD, and the second auxiliary non-AP STA corresponds to the non-millimeter-wave link of the first non-AP MLD.

[0367] In this embodiment, the communication device 3000 can be used to execute some or all of the method steps performed by the first non-AP MLD in the above method embodiments. The communication device 3000 includes units or modules for executing the aforementioned method steps. The method flow has been described in detail in the foregoing embodiments. The modules in this embodiment have the same function or perform the same steps, and will not be described again here. However, those skilled in the art should know that the textual descriptions corresponding to the foregoing method embodiments can be incorporated into this embodiment and correspond to the modules in the communication device 3000.

[0368] In some embodiments, the communication module 3010 may be a transceiver 3130. The communication device 3000 may also include a processor 3110 and a memory 3120, as shown in FIG31.

[0369] Figure 31 is a schematic structural diagram of a communication apparatus according to an embodiment of this application. The dashed lines in Figure 31 indicate that the unit or module is optional. The apparatus 3100 can be used to implement the methods described in the above method embodiments. The apparatus 3100 can be a chip or a communication device.

[0370] The apparatus 3100 may include one or more processors 3110. The processor 3110 may support the apparatus 3100 in implementing the methods described in the preceding method embodiments. The processor 3110 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0371] The apparatus 3100 may further include one or more memories 3120. The memories 3120 store a program that can be executed by the processor 3110, causing the processor 3110 to perform the methods described in the preceding method embodiments. The memories 3120 may be independent of the processor 3110 or integrated within the processor 3110.

[0372] The device 3100 may also include a transceiver 3130. The processor 3110 can communicate with other devices or chips via the transceiver 3130. For example, the processor 3110 can send and receive data with other devices or chips via the transceiver 3130.

[0373] This application also provides a computer-readable storage medium for storing a program. This computer-readable storage medium can be applied to the communication device provided in this application, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0374] This application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in this application embodiment, and the program causes a computer to execute the methods performed by the communication device in various embodiments of this application.

[0375] This application also provides a computer program. This computer program can be applied to the communication device provided in this application, and causes the computer to execute the methods performed by the communication device in various embodiments of this application.

[0376] It should be understood that the terms "system" and "network" in this application can be used interchangeably. Furthermore, the terminology used in this application is only for explaining specific embodiments of the application and is not intended to limit the application. The terms "first," "second," "third," and "fourth," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. In addition, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion.

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

[0378] The field names defined in the embodiments of this application are merely examples, and the field may have other names.

[0379] In the embodiments of this application, the term "instruction" can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0380] In the embodiments of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean that B is determined solely based on A; B can also be determined based on A and / or other information.

[0381] In the embodiments of this application, the term "correspondence" can indicate a direct or indirect correspondence between two things, or an association between two things, or a relationship such as instruction and being instructed, configuration and being configured.

[0382] In this application embodiment, "predefined" or "preconfigured" 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 AP and STA). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0383] In the embodiments of this application, the term "and / or" is merely a description of 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 document generally indicates that the preceding and following related objects have an "or" relationship.

[0384] In the embodiments of this application, "comprising" can refer to direct inclusion or indirect inclusion. Optionally, "comprising" mentioned in the embodiments of this application can be replaced with "indicating" or "used to determine". For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B".

[0385] In the various embodiments of this application, the order of the above-mentioned processes 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.

[0386] In this application embodiment, the "protocol" may refer to a standard protocol in the field of communication, such as the WiFi protocol and related protocols applied to future WiFi communication systems, and this application does not limit it.

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

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

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

[0390] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can read or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs) or semiconductor media (e.g., solid-state disks, SSDs), etc.

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

A communication method, characterized in that, include: The first AP MLD communicates with the first non-AP MLD. The first AP MLD includes a first auxiliary AP and a second auxiliary AP. The first auxiliary AP corresponds to the millimeter-wave link of the first AP MLD, and the second auxiliary AP corresponds to the non-millimeter-wave link of the first AP MLD. The first non-AP MLD includes a first auxiliary non-AP STA and a second auxiliary non-AP STA. The first auxiliary non-AP STA corresponds to the millimeter-wave link of the first non-AP MLD, and the second auxiliary non-AP STA corresponds to the non-millimeter-wave link of the first non-AP MLD. The method according to claim 1, characterized in that, The first auxiliary AP does not send beacon frames. The method according to claim 2, characterized in that, The first auxiliary AP is not used to perform one or more of the following functions: time synchronization, link discovery, link establishment, and link management. The method according to claim 2 or 3, characterized in that: The first auxiliary AP is not used to send one or more of the following frames: beacon frame, probe response frame, association response frame, reassociation response frame, authentication frame, deauthentication frame, deassociation frame, channel handover notification frame, extended channel handover notification frame, operation mode notification frame; and / or, The first auxiliary AP is not used to receive one or more of the following frames: probe request frame, association request frame, reassociation request frame, authentication frame, deauthentication frame, deassociation frame, and operation mode notification frame. The method according to any one of claims 2-4 is characterized in that: The first auxiliary non-AP STA is not used to send one or more of the following frames: probe request frame, association request frame, reassociation request frame, authentication frame, deauthentication frame, deassociation frame, operation mode notification frame; and / or, The first auxiliary non-AP STA is not used to receive one or more of the following frames: beacon frame, probe response frame, association response frame, reassociation response frame, authentication frame, deauthentication frame, deassociation frame, channel switching notification frame, extended channel switching notification frame, and operation mode notification frame. The method according to claim 1, characterized in that, The first auxiliary AP is used to send beacon frames on the millimeter-wave link corresponding to the first auxiliary AP. The beacon frames are short message beacon frames or light beacon frames. The method according to claim 6, characterized in that, The first auxiliary AP is used to implement one or more of the following functions: time synchronization, partial or full link discovery, and reachability. The method according to claim 6 or 7, characterized in that, The method further includes: The first auxiliary AP receives a probe request frame sent by the first auxiliary non-AP STA; and / or, The first auxiliary AP sends a probe response frame to the first auxiliary non-AP STA. The method according to claim 8, characterized in that, The probe request frame includes one or more of the following fields: service set identifier element, request element, extended capability element, extended request element, integrated millimeter wave capability element, integrated millimeter wave operation element, and vendor-defined element. The method according to claim 8 or 9, characterized in that, The probe response frame includes one or more of the following fields: timestamp field, beacon interval field, capability information field, service set identifier element, country element, power limit element, quality of service capability element, simplified neighbor report element, robust secure network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, robust secure network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and requested element. The method according to any one of claims 6-10, characterized in that, The beacon frame includes one or more of the following fields: timestamp field, beacon interval field, transmit sector and / or beam information field, transmit power control element, service set identifier element, country element, power limit element, quality of service capability element, robust security network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, simplified neighbor report element, robust security network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and management frame message integrity verification element. The method according to any one of claims 6-11, characterized in that, The method further includes: The second auxiliary AP sends a first key to the second auxiliary non-AP STA, the first key being used for integrity protection of the beacon frame. The method according to any one of claims 1-12 is characterized in that, The method further includes: The second auxiliary AP receives a first frame sent by the second auxiliary non-AP STA, the first frame being a frame related to the establishment of the millimeter-wave link. The method according to claim 13, characterized in that, The first frame includes one or more of the following: an authentication frame, an association request frame, and a reassociation request frame. The method according to claim 13 or 14 is characterized in that, The first frame includes a multi-link element, which includes one or more of the following: the complete configuration of the first affiliated non-AP STA; information for requesting the complete configuration of the first affiliated AP. The method according to any one of claims 1-15 is characterized in that, The method further includes: The second auxiliary AP sends a second frame to the second auxiliary non-AP STA, the second frame being a frame related to the establishment of the millimeter-wave link. The method according to claim 16, characterized in that, The second frame includes one or more of the following: an authentication frame, an association response frame, and a reassociation response frame. The method according to claim 16 or 17, characterized in that, The second frame includes a multi-link element, which includes the complete configuration of the first affiliated AP. The method according to any one of claims 1-18, characterized in that, The method further includes: The second auxiliary AP sends a third frame to the second auxiliary non-AP STA, the third frame being a frame related to link management of the millimeter-wave link. The method according to claim 19, characterized in that, The third frame includes one or more of the following: a channel switching notification frame, an extended channel switching notification frame, and an operation mode notification frame. The method according to claim 19 or 20 is characterized in that, The third frame includes first indication information, which is used to indicate the first auxiliary AP. The method according to claim 21, characterized in that, The third frame contains a multi-link operation link information element, which includes a link identifier bitmap field, and the link identifier bitmap field contains the first indication information. The method according to any one of claims 1-22 is characterized in that, The beacon frames and / or probe response frames sent by the second auxiliary AP include a basic multi-link element, which includes a per-site configuration sub-element field corresponding to the millimeter-wave link. The per-site configuration sub-element field includes a site configuration field, which carries one or more of a channel handover notification element, an extended channel handover notification element, and an operation mode notification element. The method according to any one of claims 1-23 is characterized in that, The method further includes: The second auxiliary AP receives a separately addressed fourth frame sent by the second auxiliary non-AP STA, the fourth frame being the operation mode notification frame of the millimeter-wave link. The method according to any one of claims 1-24 is characterized in that, The fifth frame sent by the second auxiliary AP carries a neighbor report element, which includes second indication information for indicating that the first AP MLD supports millimeter-wave link operation or has a millimeter-wave link. The method according to claim 25, characterized in that, The neighbor report element includes a BSSID information field, and the second indication information is located in the BSSID information field. The method according to any one of claims 1-26, characterized in that, The method further includes: The second auxiliary AP sends a sixth frame to the second auxiliary non-AP STA, the sixth frame containing third indication information, the third indication information being used to indicate that the key parameters of the millimeter-wave link have been updated. The method according to claim 27, characterized in that, The sixth frame is a beacon frame and / or a probe response frame. The method according to claim 27 or 28, characterized in that, The sixth frame includes a per-site configuration field corresponding to the first auxiliary AP. The per-site configuration field includes a capability information field, and the key update identifier field in the capability information field contains the third indication information. The method according to claim 27 or 28, characterized in that, The sixth frame includes a capability information field, which contains the third indication information. A communication method, characterized in that, include: The first non-AP MLD communicates with the first AP MLD. The first AP MLD includes a first auxiliary AP and a second auxiliary AP. The first auxiliary AP corresponds to the millimeter-wave link of the first AP MLD, and the second auxiliary AP corresponds to the non-millimeter-wave link of the first AP MLD. The first non-AP MLD includes a first auxiliary non-AP STA and a second auxiliary non-AP STA. The first auxiliary non-AP STA corresponds to the millimeter-wave link of the first non-AP MLD, and the second auxiliary non-AP STA corresponds to the non-millimeter-wave link of the first non-AP MLD. The method according to claim 31, characterized in that, The first auxiliary AP does not send beacon frames. The method according to claim 32, characterized in that, The first auxiliary AP is not used to perform one or more of the following functions: time synchronization, link discovery, link establishment, and link management. The method according to claim 32 or 33 is characterized in that: The first auxiliary AP is not used to send one or more of the following frames: beacon frame, probe response frame, association response frame, reassociation response frame, authentication frame, deauthentication frame, deassociation frame, channel handover notification frame, extended channel handover notification frame, operation mode notification frame; and / or, The first auxiliary AP is not used to receive one or more of the following frames: probe request frame, association request frame, reassociation request frame, authentication frame, deauthentication frame, deassociation frame, and operation mode notification frame. The method according to any one of claims 32-34 is characterized in that: The first auxiliary non-AP STA is not used to send one or more of the following frames: probe request frame, association request frame, reassociation request frame, authentication frame, deauthentication frame, deassociation frame, operation mode notification frame; and / or, The first auxiliary non-AP STA is not used to receive one or more of the following frames: beacon frame, probe response frame, association response frame, reassociation response frame, authentication frame, deauthentication frame, deassociation frame, channel switching notification frame, extended channel switching notification frame, and operation mode notification frame. The method according to claim 31, characterized in that, The first auxiliary AP is used to send beacon frames on the millimeter-wave link corresponding to the first auxiliary AP. The beacon frames are short message beacon frames or light beacon frames. The method according to claim 36, characterized in that, The first auxiliary AP is used to implement one or more of the following functions: time synchronization, partial or full link discovery, and reachability. The method according to claim 36 or 37, characterized in that, The method further includes: The first auxiliary non-AP STA sends a probe request frame to the first auxiliary AP; and / or, The first auxiliary non-AP STA receives the probe response frame sent by the first auxiliary AP. The method according to claim 38, characterized in that, The probe request frame includes one or more of the following fields: service set identifier element, request element, extended capability element, extended request element, integrated millimeter wave capability element, integrated millimeter wave operation element, and vendor-defined element. The method according to claim 38 or 39 is characterized in that, The probe response frame includes one or more of the following fields: timestamp field, beacon interval field, capability information field, service set identifier element, country element, power limit element, quality of service capability element, simplified neighbor report element, robust secure network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, robust secure network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and requested element. The method according to any one of claims 36-40, characterized in that, The beacon frame includes one or more of the following fields: timestamp field, beacon interval field, transmit sector and / or beam information field, transmit power control element, service set identifier element, country element, power limit element, quality of service capability element, robust security network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, simplified neighbor report element, robust security network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and management frame message integrity verification element. The method according to any one of claims 36-41 is characterized in that, The method further includes: The second auxiliary non-AP STA receives a first key sent by the second auxiliary AP, the first key being used for integrity protection of the beacon frame. The method according to any one of claims 31-42 is characterized in that, The method further includes: The second auxiliary non-AP STA sends a first frame to the second auxiliary AP, the first frame being a frame related to the establishment of the millimeter-wave link. The method according to claim 43 is characterized in that, The first frame includes one or more of the following: an authentication frame, an association request frame, and a reassociation request frame. The method according to claim 43 or 44 is characterized in that, The first frame includes a multi-link element, which includes one or more of the following: the complete configuration of the first affiliated non-AP STA; information for requesting the complete configuration of the first affiliated AP. The method according to any one of claims 31-45 is characterized in that, The method further includes: The second auxiliary non-AP STA receives a second frame sent by the second auxiliary AP, the second frame being a frame related to the establishment of the millimeter-wave link. The method according to claim 46, characterized in that, The second frame includes one or more of the following: an authentication frame, an association response frame, and a reassociation response frame. The method according to claim 46 or 47 is characterized in that, The second frame includes a multi-link element, which includes the complete configuration of the first affiliated AP. The method according to any one of claims 31-48 is characterized in that, The method further includes: The second auxiliary non-AP STA receives a third frame sent by the second auxiliary AP, the third frame being a frame related to link management of the millimeter-wave link. The method according to claim 49, characterized in that, The third frame includes one or more of the following: a channel switching notification frame, an extended channel switching notification frame, and an operation mode notification frame. The method according to claim 49 or 50 is characterized in that, The third frame includes first indication information, which is used to indicate the first auxiliary AP. The method according to claim 51, characterized in that, The third frame contains a multi-link operation link information element, which includes a link identifier bitmap field, and the link identifier bitmap field contains the first indication information. The method according to any one of claims 31-52 is characterized in that, The beacon frames and / or probe response frames sent by the second auxiliary AP include a basic multi-link element, which includes a per-site configuration sub-element field corresponding to the millimeter-wave link. The per-site configuration sub-element field includes a site configuration field, which carries one or more of a channel handover notification element, an extended channel handover notification element, and an operation mode notification element. The method according to any one of claims 31-53 is characterized in that, The method further includes: The second auxiliary non-AP STA sends a separately addressed fourth frame to the second auxiliary AP, the fourth frame being the operation mode notification frame of the millimeter-wave link. The method according to any one of claims 31-54 is characterized in that, The fifth frame sent by the second auxiliary AP carries a neighbor report element, which includes second indication information for indicating that the first AP MLD supports millimeter-wave link operation or has a millimeter-wave link. The method according to claim 55, characterized in that, The neighbor report element includes a BSSID information field, and the second indication information is located in the BSSID information field. The method according to any one of claims 31-56 is characterized in that, The method further includes: The second auxiliary non-AP STA receives a sixth frame sent by the second auxiliary AP, the sixth frame containing third indication information, the third indication information being used to indicate that the key parameters of the millimeter-wave link have been updated. The method according to claim 57, characterized in that, The sixth frame is a beacon frame and / or a probe response frame. The method according to claim 57 or 58 is characterized in that, The sixth frame includes a per-site configuration field corresponding to the first auxiliary AP. The per-site configuration field includes a capability information field, and the key update identifier field in the capability information field contains the third indication information. The method according to claim 57 or 58 is characterized in that, The sixth frame includes a capability information field, which contains the third indication information. A communication device, characterized in that, The communication device is a first AP MLD, and the communication device includes: A communication module is used to communicate with a first non-AP MLD. The first AP MLD includes a first auxiliary AP and a second auxiliary AP. The first auxiliary AP corresponds to the millimeter-wave link of the first AP MLD, and the second auxiliary AP corresponds to the non-millimeter-wave link of the first AP MLD. The first non-AP MLD includes a first auxiliary non-AP STA and a second auxiliary non-AP STA. The first auxiliary non-AP STA corresponds to the millimeter-wave link of the first non-AP MLD, and the second auxiliary non-AP STA corresponds to the non-millimeter-wave link of the first non-AP MLD. The communication device according to claim 61 is characterized in that, The first auxiliary AP does not send beacon frames. The communication device according to claim 62 is characterized in that, The first auxiliary AP is not used to perform one or more of the following functions: time synchronization, link discovery, link establishment, and link management. The communication device according to claim 62 or 63 is characterized in that: The first auxiliary AP is not used to send one or more of the following frames: beacon frame, probe response frame, association response frame, reassociation response frame, authentication frame, deauthentication frame, deassociation frame, channel handover notification frame, extended channel handover notification frame, operation mode notification frame; and / or, The first auxiliary AP is not used to receive one or more of the following frames: probe request frame, association request frame, reassociation request frame, authentication frame, deauthentication frame, deassociation frame, and operation mode notification frame. The communication device according to any one of claims 62-64 is characterized in that: The first auxiliary non-AP STA is not used to send one or more of the following frames: probe request frame, association request frame, reassociation request frame, authentication frame, deauthentication frame, deassociation frame, operation mode notification frame; and / or, The first auxiliary non-AP STA is not used to receive one or more of the following frames: beacon frame, probe response frame, association response frame, reassociation response frame, authentication frame, deauthentication frame, deassociation frame, channel switching notification frame, extended channel switching notification frame, and operation mode notification frame. The communication device according to claim 61 is characterized in that, The first auxiliary AP is used to send beacon frames on the millimeter-wave link corresponding to the first auxiliary AP. The beacon frames are short message beacon frames or light beacon frames. The communication device according to claim 66 is characterized in that, The first auxiliary AP is used to implement one or more of the following functions: time synchronization, partial or full link discovery, and reachability. The communication device according to claim 66 or 67 is characterized in that, The communication device also includes: The first receiving module is configured to receive a probe request frame sent by the first auxiliary non-AP STA; and / or, The first transmitting module is used to send a probe response frame to the first auxiliary non-AP STA. The communication device according to claim 68 is characterized in that, The probe request frame includes one or more of the following fields: service set identifier element, request element, extended capability element, extended request element, integrated millimeter wave capability element, integrated millimeter wave operation element, and vendor-defined element. The communication device according to claim 68 or 69 is characterized in that, The probe response frame includes one or more of the following fields: timestamp field, beacon interval field, capability information field, service set identifier element, country element, power limit element, quality of service capability element, simplified neighbor report element, robust secure network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, robust secure network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and requested element. The communication device according to any one of claims 66-70 is characterized in that, The beacon frame includes one or more of the following fields: timestamp field, beacon interval field, transmit sector and / or beam information field, transmit power control element, service set identifier element, country element, power limit element, quality of service capability element, robust security network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, simplified neighbor report element, robust security network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and management frame message integrity verification element. The communication device according to any one of claims 66-71 is characterized in that, The communication device also includes: The second transmitting module is used to transmit a first key to the second auxiliary non-AP STA, the first key being used for integrity protection of the beacon frame. The communication device according to any one of claims 61-72 is characterized in that, The communication device also includes: The second receiving module is used to receive a first frame sent by the second auxiliary non-AP STA, the first frame being a frame related to the link establishment of the millimeter-wave link. The communication device according to claim 73 is characterized in that, The first frame includes one or more of the following: an authentication frame, an association request frame, and a reassociation request frame. The communication device according to claim 73 or 74 is characterized in that, The first frame includes a multi-link element, which includes one or more of the following: the complete configuration of the first affiliated non-AP STA; information for requesting the complete configuration of the first affiliated AP. The communication device according to any one of claims 61-75 is characterized in that, The communication device also includes: The third transmitting module is used to transmit a second frame to the second auxiliary non-AP STA, the second frame being a frame related to the link establishment of the millimeter-wave link. The communication device according to claim 76 is characterized in that, The second frame includes one or more of the following: an authentication frame, an association response frame, and a reassociation response frame. The communication device according to claim 76 or 77 is characterized in that, The second frame includes a multi-link element, which includes the complete configuration of the first affiliated AP. The communication device according to any one of claims 61-78 is characterized in that, The communication device also includes: The fourth transmitting module is used to transmit a third frame to the second auxiliary non-AP STA, the third frame being a frame related to the link management of the millimeter-wave link. The communication device according to claim 79 is characterized in that, The third frame includes one or more of the following: a channel switching notification frame, an extended channel switching notification frame, and an operation mode notification frame. The communication device according to claim 79 or 80 is characterized in that, The third frame includes first indication information, which is used to indicate the first auxiliary AP. The communication device according to claim 81, characterized in that, The third frame contains a multi-link operation link information element, which includes a link identifier bitmap field, and the link identifier bitmap field contains the first indication information. The communication device according to any one of claims 61-82 is characterized in that, The beacon frames and / or probe response frames sent by the second auxiliary AP include a basic multi-link element, which includes a per-site configuration sub-element field corresponding to the millimeter-wave link. The per-site configuration sub-element field includes a site configuration field, which carries one or more of a channel handover notification element, an extended channel handover notification element, and an operation mode notification element. The communication device according to any one of claims 61-83 is characterized in that, The communication device also includes: The third receiving module is used to receive a separately addressed fourth frame sent by the second auxiliary non-AP STA, the fourth frame being the operation mode notification frame of the millimeter-wave link. The communication device according to any one of claims 61-84 is characterized in that, The fifth frame sent by the second auxiliary AP carries a neighbor report element, which includes second indication information for indicating that the first AP MLD supports millimeter-wave link operation or has a millimeter-wave link. The communication device according to claim 85 is characterized in that, The neighbor report element includes a BSSID information field, and the second indication information is located in the BSSID information field. The communication device according to any one of claims 61-86 is characterized in that, The communication device also includes: The fifth transmitting module is used to transmit a sixth frame to the second auxiliary non-AP STA, the sixth frame containing third indication information, the third indication information being used to indicate that the key parameters of the millimeter-wave link have been updated. The communication device according to claim 87 is characterized in that, The sixth frame is a beacon frame and / or a probe response frame. The communication device according to claim 87 or 88 is characterized in that, The sixth frame includes a per-site configuration field corresponding to the first auxiliary AP. The per-site configuration field includes a capability information field, and the key update identifier field in the capability information field contains the third indication information. The communication device according to claim 87 or 88 is characterized in that, The sixth frame includes a capability information field, which contains the third indication information. A communication device, characterized in that, The communication device is a first non-AP MLD, and the communication device includes: A communication module is used to communicate with a first AP MLD, the first AP MLD including a first auxiliary AP and a second auxiliary AP, the first auxiliary AP corresponding to the millimeter-wave link of the first AP MLD, the second auxiliary AP corresponding to the non-millimeter-wave link of the first AP MLD, the first non-AP MLD including a first auxiliary non-AP STA and a second auxiliary non-AP STA, the first auxiliary non-AP STA corresponding to the millimeter-wave link of the first non-AP MLD, and the second auxiliary non-AP STA corresponding to the non-millimeter-wave link of the first non-AP MLD. The communication device according to claim 91 is characterized in that, The first auxiliary AP does not send beacon frames. The communication device according to claim 92 is characterized in that, The first auxiliary AP is not used to perform one or more of the following functions: time synchronization, link discovery, link establishment, and link management. The communication device according to claim 92 or 93 is characterized in that: The first auxiliary AP is not used to send one or more of the following frames: beacon frame, probe response frame, association response frame, reassociation response frame, authentication frame, deauthentication frame, deassociation frame, channel handover notification frame, extended channel handover notification frame, operation mode notification frame; and / or, The first auxiliary AP is not used to receive one or more of the following frames: probe request frame, association request frame, reassociation request frame, authentication frame, deauthentication frame, deassociation frame, and operation mode notification frame. The communication device according to any one of claims 92-94 is characterized in that: The first auxiliary non-AP STA is not used to send one or more of the following frames: probe request frame, association request frame, reassociation request frame, authentication frame, deauthentication frame, deassociation frame, operation mode notification frame; and / or, The first auxiliary non-AP STA is not used to receive one or more of the following frames: beacon frame, probe response frame, association response frame, reassociation response frame, authentication frame, deauthentication frame, deassociation frame, channel switching notification frame, extended channel switching notification frame, and operation mode notification frame. The communication device according to claim 91 is characterized in that, The first auxiliary AP is used to send beacon frames on the millimeter-wave link corresponding to the first auxiliary AP. The beacon frames are short message beacon frames or light beacon frames. The communication device according to claim 96 is characterized in that, The first auxiliary AP is used to implement one or more of the following functions: time synchronization, partial or full link discovery, and reachability. The communication device according to claim 96 or 97 is characterized in that, The communication device also includes: The first transmitting module is configured to send a probe request frame to the first auxiliary AP; and / or, The first receiving module is used to receive the probe response frame sent by the first auxiliary AP. The communication device according to claim 98 is characterized in that, The probe request frame includes one or more of the following fields: service set identifier element, request element, extended capability element, extended request element, integrated millimeter wave capability element, integrated millimeter wave operation element, and vendor-defined element. The communication device according to claim 98 or 99 is characterized in that, The probe response frame includes one or more of the following fields: timestamp field, beacon interval field, capability information field, service set identifier element, country element, power limit element, quality of service capability element, simplified neighbor report element, robust secure network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, robust secure network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and requested element. The communication device according to any one of claims 96-100 is characterized in that, The beacon frame includes one or more of the following fields: timestamp field, beacon interval field, transmit sector and / or beam information field, transmit power control element, service set identifier element, country element, power limit element, quality of service capability element, robust security network element, enhanced distributed access parameter set element, extended capability element, transmit power envelope element, simplified neighbor report element, robust security network extension element, integrated millimeter wave capability element, integrated millimeter wave operation element, vendor-defined element, and management frame message integrity verification element. The communication device according to any one of claims 96-101 is characterized in that, The communication device also includes: The second receiving module is used to receive the first key sent by the second auxiliary AP, the first key being used to protect the integrity of the beacon frame. The communication device according to any one of claims 91-102 is characterized in that, The communication device also includes: The second transmitting module is used to transmit a first frame to the second auxiliary AP, the first frame being a frame related to the establishment of the millimeter-wave link. The communication device according to claim 103 is characterized in that, The first frame includes one or more of the following: an authentication frame, an association request frame, and a reassociation request frame. The communication device according to claim 103 or 104 is characterized in that, The first frame includes a multi-link element, which includes one or more of the following: the complete configuration of the first affiliated non-AP STA; information for requesting the complete configuration of the first affiliated AP. The communication device according to any one of claims 91-105 is characterized in that, The communication device also includes: The third receiving module is used to receive the second frame sent by the second auxiliary AP, the second frame being a frame related to the link establishment of the millimeter-wave link. The communication device according to claim 106 is characterized in that, The second frame includes one or more of the following: an authentication frame, an association response frame, and a reassociation response frame. The communication device according to claim 106 or 107 is characterized in that, The second frame includes a multi-link element, which includes the complete configuration of the first affiliated AP. The communication device according to any one of claims 91-108 is characterized in that, The communication device also includes: The fourth receiving module is used to receive a third frame sent by the second auxiliary AP, the third frame being a frame related to the link management of the millimeter-wave link. The communication device according to claim 109 is characterized in that, The third frame includes one or more of the following: a channel switching notification frame, an extended channel switching notification frame, and an operation mode notification frame. The communication device according to claim 109 or 110 is characterized in that, The third frame includes first indication information, which is used to indicate the first auxiliary AP. The communication device according to claim 111 is characterized in that, The third frame contains a multi-link operation link information element, which includes a link identifier bitmap field, and the link identifier bitmap field contains the first indication information. The communication device according to any one of claims 91-112 is characterized in that, The beacon frames and / or probe response frames sent by the second auxiliary AP include a basic multi-link element, which includes a per-site configuration sub-element field corresponding to the millimeter-wave link. The per-site configuration sub-element field includes a site configuration field, which carries one or more of a channel handover notification element, an extended channel handover notification element, and an operation mode notification element. The communication device according to any one of claims 91-113 is characterized in that, The communication device also includes: The third transmitting module is used to send a separately addressed fourth frame to the second auxiliary AP, the fourth frame being the operation mode notification frame of the millimeter-wave link. The communication device according to any one of claims 91-114 is characterized in that, The fifth frame sent by the second auxiliary AP carries a neighbor report element, which includes second indication information for indicating that the first AP MLD supports millimeter-wave link operation or has a millimeter-wave link. The communication device according to claim 115 is characterized in that, The neighbor report element includes a BSSID information field, and the second indication information is located in the BSSID information field. The communication device according to any one of claims 91-116 is characterized in that, The communication device also includes: The fifth receiving module is used to receive the sixth frame sent by the second auxiliary AP. The sixth frame contains third indication information, which is used to indicate that the key parameters of the millimeter-wave link have been updated. The communication device according to claim 117 is characterized in that, The sixth frame is a beacon frame and / or a probe response frame. The communication device according to claim 117 or 118 is characterized in that, The sixth frame includes a per-site configuration field corresponding to the first auxiliary AP. The per-site configuration field includes a capability information field, and the key update identifier field in the capability information field contains the third indication information. The communication device according to claim 117 or 118 is characterized in that, The sixth frame includes a capability information field, which contains the third indication information. A communication device, characterized in that, The device includes a transceiver, a memory, and a processor. The memory stores a program, and the processor invokes the program in the memory and controls the transceiver to receive or transmit signals so that the communication device performs the method as described in any one of claims 1-30 or 31-60. An apparatus characterized in that, Includes a processor for calling a program from memory to cause the device to perform the method as described in any one of claims 1-30 or 31-60. A chip characterized in that, Includes a processor for calling a program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1-30 or 31-60. A computer-readable storage medium, characterized in that, It contains a program that causes a computer to perform the method as described in any one of claims 1-30 or 31-60. A computer program product, characterized in that, Includes a program that causes a computer to perform the method as described in any one of claims 1-30 or 31-60. A computer program, characterized in that, The computer program causes the computer to perform the method as described in any one of claims 1-30 or 31-60.

Images