Wireless communication method and communication device

Abstract

The invention provides a wireless communication method and communication equipment. The method comprises the following steps: a first device sends first indication information to a second device; the first indication information is used for indicating capability information of target equipment, the target equipment comprises the first equipment and / or third equipment, and the capability information comprises one or more of the following information of the target equipment: multi-AP coordination capability; the access capability of a secondary channel; preferentially accessing the capability of a channel; a support condition of a link adaptive function; a support condition of a relay function; a capability based on DRU transmission; mobility capability; a power supply mode; a capability related to preemption; the capability of supporting a target protocol; the roaming capability is enhanced; a support condition of a TXOP sharing function based on a non-trigger frame; the energy-saving capability is realized; the support condition of the length passive adjustment function of the A-MPDU is determined; the support condition of the PPDU is aggregated in the frequency domain of 320MHz; the support condition of the RU self-adaptive function; repeating the support condition of the transmission function; based on the capability of pluggable PPDU communication; and the communication capability on the frequency band of more than 45 GHz is realized.

Description

Wireless communication method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method and a communication device. Background Art

[0002] With the development of technology, the capabilities of communication devices are becoming more and more diverse. However, the technology that indicates capability information cannot adapt to the development of technology, making some communication technologies difficult to be well applied in actual communication scenarios.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method and a communication device. The following introduces various aspects involved in the present application.

[0005] In a first aspect, a wireless communication method is provided, including: a first device sends first indication information to a second device; wherein the first indication information is used to indicate capability information of a target device, the target device includes the first device and / or the third device, and the capability information includes one or more of the following information of the target device: capability of multiple access points (APs) coordination; capability of secondary channel access; capability of priority access channel; support for link adaptation function; support for relay function; capability based on distributed resource unit (DRU) transmission; mobility capability; power supply mode; capability related to preemption; capability to support target protocol; enhanced roaming capability; support for transmission opportunity (TXOP) sharing function based on non-triggered frames; energy saving capability; support for passive adjustment function of aggregated media access control protocol data unit (A-MPDU); support for 320MHz frequency domain aggregate physical layer protocol data unit (PPDU); support for resource unit (RU) adaptation function; support for repeated transmission function; capability based on insertable PPDU communication; and communication capability in frequency bands above 45GHz.

[0006] According to a second aspect, a wireless communication method is provided, including: a second device receives first indication information sent by a first device; wherein the first indication information is used to indicate capability information of a target device, the target device includes the first device and / or the third device, and the capability information includes one or more of the following information of the target device: capability of multi-AP coordination; capability of secondary channel access; capability of priority access channel; support for link adaptation function; support for relay function; capability based on DRU transmission; mobility capability; power supply mode; capability related to preemption; capability to support target protocol; enhanced roaming capability; support for TXOP sharing function based on non-triggered frames; energy saving capability; support for passive adjustment of A-MPDU length function; support for 320MHz frequency domain aggregated PPDU; support for RU adaptation function; support for repeated transmission function; capability based on insertable PPDU communication; communication capability in frequency bands above 45GHz.

[0007] According to a third aspect, a communication device is provided, which is a first device and includes: a sending unit for sending first indication information to a second device; wherein the first indication information is used to indicate capability information of a target device, and the target device includes the first device and / or the third device, and the capability information includes one or more of the following information of the target device: capability of multi-AP coordination; capability of secondary channel access; capability of priority access channel; support for link adaptation function; support for relay function; capability based on DRU transmission; mobility capability; power supply mode; capability related to preemption; capability to support target protocol; enhanced roaming capability; support for TXOP sharing function based on non-triggered frames; energy saving capability; support for passive adjustment of A-MPDU length function; support for 320MHz frequency domain aggregated PPDU; support for RU adaptation function; support for repeated transmission function; capability based on insertable PPDU communication; communication capability on frequency bands above 45GHz.

[0008] In a fourth aspect, a communication device is provided, which is a second device, and the communication device includes: a receiving unit for receiving first indication information sent by a first device; wherein the first indication information is used to indicate capability information of a target device, and the target device includes a first device and / or a third device, and the capability information includes one or more of the following information of the target device: capability of multi-AP coordination; capability of secondary channel access; capability of priority access channel; support for link adaptation function; support for relay function; capability based on DRU transmission; mobility capability; power supply mode; capability related to preemption; capability to support target protocol; enhanced roaming capability; support for TXOP sharing function based on non-triggered frames; energy saving capability; support for passive adjustment of A-MPDU length function; support for 320MHz frequency domain aggregated PPDU; support for RU adaptation function; support for repeated transmission function; capability based on insertable PPDU communication; communication capability on frequency bands above 45GHz.

[0009] In a fifth aspect, a communication device is provided, comprising a processor and a memory, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory to enable the communication device to perform some or all of the steps in the above-mentioned various aspects of the method.

[0010] In a sixth aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned communication device. In another possible design, the system may also include other devices that interact with the communication device in the solution provided in the embodiment of the present application.

[0011] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device to execute part or all of the steps in the methods of the above aspects.

[0012] In an eighth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0013] In a ninth aspect, an embodiment of the present application provides a chip comprising a memory and a processor, wherein the processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0014] Through the first indication information, communication devices (such as UHR devices) can effectively discover and understand the relevant capabilities of other communication devices, thereby achieving more efficient and accurate communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG1 is a schematic diagram of a wireless communication system used in an embodiment of the present application.

[0016] FIG. 2A is a diagram illustrating an example of a capability discovery process based on passive scanning.

[0017] FIG. 2B is an example diagram of a capability discovery process based on active scanning.

[0018] FIG. 2C is a diagram illustrating an example of an association-based capability discovery process.

[0019] FIG. 2D is an example diagram of a capability discovery process based on re-association.

[0020] FIG. 2E is an example diagram of an authentication-based capability discovery process.

[0021] FIG. 3A is a diagram showing an example of the format of a neighbor report element.

[0022] FIG. 3B is a diagram illustrating an example format of a capability information field in a vicinity report element.

[0023] FIG. 4 is a diagram illustrating an example of a reduced neighbor report (RNR) element format.

[0024] FIG5 is a schematic flow chart of a wireless communication method provided in an embodiment of the present application

[0025] FIG6 is a schematic diagram of a secondary channel operation element format provided in an embodiment of the present application.

[0026] FIG7A is a diagram showing an example format of a first capability element provided in an embodiment of the present application.

[0027] FIG7B is a schematic diagram showing the format of the UHR MAC capability information field.

[0028] FIG. 7C is a schematic diagram showing the format of the UHR PHY capability information field.

[0029] FIG8 is a schematic diagram of the format of a nearby report element provided in an embodiment of the present application.

[0030] FIG9 is a schematic diagram of a simplified format of a nearby reporting element provided in an embodiment of the present application.

[0031] FIG10 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0032] FIG11 is a schematic structural diagram of a communication device provided in an embodiment of the present application.

[0033] FIG12 is a schematic structural diagram of a device for communication provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] The technical solution in this application will be described below with reference to the accompanying drawings.

[0035] Communication System

[0036] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as wireless local area networks (WLAN), wireless fidelity (WiFi), high performance radio local area networks (HIPELAN), wide area networks (WAN), cellular networks, or other communication systems. For another example, the technical solutions provided in the embodiments of the present application can be applied to communication systems that adopt the 802.11 standard. For example, the 802.11 standard includes but is not limited to the 802.11ax standard, the 802.11be standard, and the next generation 802.11 standard.

[0037] FIG1 is a schematic diagram of a communication system applicable to embodiments of the present application. Referring to FIG1 , communication devices in the communication system 100 may include APs 111 and 112, and stations (STAs) 121 and 122. STA 121 may access the network through AP 111, and STA 122 may access the network through AP 112.

[0038] In some implementations, a STA may establish an association with one or more APs, after which the associated STAs and APs may communicate. For example, as shown in FIG1 , AP 111 and STA 121 may communicate after establishing an association, and AP 112 and STA 122 may communicate after establishing an association.

[0039] In some implementations, the communication in the communication system 100 may be communication between an AP and a non-AP STA, communication between a non-AP STA and a non-AP STA, or communication between a STA and a peer STA, where a peer STA may refer to a device that communicates with the STA peer, for example, the peer STA may be an AP or a non-AP STA.

[0040] It should be understood that FIG1 exemplarily shows two AP STAs and two non-AP STAs, and the communication system 100 may also include a larger number of AP STAs, or the communication system 100 may include other numbers of non-AP STAs, which is not limited in the embodiments of the present application.

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

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

[0043] In some scenarios, the aforementioned communication device may also be a "multi-link device (MLD)," i.e., a device that can communicate via multiple communication links, where the multiple communication links may include communication links in different frequency bands, such as millimeter wave bands and / or low-frequency bands. Generally, if the multi-link device is an AP, the AP may also be referred to as a "multi-link AP." If the multi-link device is a STA, the STA may also be referred to as a "multi-link STA."

[0044] In the embodiments of the present application, an AP may be a device in a wireless network. An AP may be a communication entity such as a communication server, a router, a switch, or a bridge, or the AP device may include various forms of macro base stations, micro base stations, relay stations, etc. Of course, the AP may also be a chip, circuit, or processing system in these various forms of devices, thereby realizing the methods and functions of the embodiments of the present application. The AP device can be applied to a variety of scenarios, such as sensor nodes in smart cities (e.g., smart water meters, smart electricity meters, smart air detection nodes), smart devices in smart homes (e.g., smart cameras, projectors, displays, televisions, speakers, refrigerators, washing machines, etc.), nodes in the Internet of Things, entertainment terminals (e.g., wearable devices such as AR and VR), smart devices in smart offices (e.g., printers, projectors, etc.), Internet of Vehicles devices in the Internet of Vehicles, and some infrastructure in daily life scenarios (e.g., vending machines, self-service navigation counters in supermarkets, self-service checkout devices, self-service ordering machines), etc.

[0045] In some implementations, the role of a STA in a communication system is not absolute; in some scenarios, a STA can function as an AP. For example, when a mobile phone is connected to a router, it can be a non-AP STA, while when it is acting as a hotspot for other phones, it functions as an AP.

[0046] In the embodiments of the present application, a STA device in the embodiments of the present application may be a device with wireless transceiver functions, such as a device that supports the 802.11 series of protocols and can communicate with an AP or other STAs. For example, a STA is any user communication device that allows a user to communicate with an AP and, in turn, with a WLAN. STA devices include, for example, user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.

[0047] The STA in the embodiment of the present application may also be a device that provides voice / data connectivity to users, such as a handheld device or vehicle-mounted device with wireless connection function. Examples include: mobile phones, tablet computers, laptop computers, 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, 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 wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks or future-evolved public land mobile communication networks. The terminal equipment in the network (PLMN), etc., is not limited to this in the embodiments of the present application.

[0048] By way of example and not limitation, in the embodiments of this application, the STA device may also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for wearable devices that utilize wearable technology to intelligently design and develop wearable devices, such as glasses, gloves, watches, clothing, and shoes. Examples include smart watches or smart glasses, as well as devices that focus on a specific application function and require integration with other devices, such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0049] In addition, in embodiments of the present application, the STA device can also be a terminal device in the Internet of Things (IoT) system. The IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people and machines and things. In embodiments of the present application, IoT technology can achieve massive connections, deep coverage, and terminal power saving through, for example, narrowband (NB) technology.

[0050] Furthermore, in the embodiments of the present application, the STA device may be a device in a connected vehicle system. The communication methods in a connected vehicle system are collectively referred to as V2X (where X represents everything). For example, V2X communication includes vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-network (V2N) communication.

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

[0052] In addition, the AP device in the embodiment of the present application may be a device for communicating with a STA device. The AP device may be a network device in a wireless local area network. The AP device may be used to communicate with the STA device through the wireless local area network.

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

[0054] From the perspective of STA-supported communication standards, 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 wireless local area network (WLAN) standards, including 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0055] In the embodiments of the present application, there is no limitation on the frequency bands supported by WLAN technology. In some implementations, the frequency bands supported by WLAN technology may include, but are not limited to, low frequency bands (e.g., 2.4 GHz, 5 GHz, 6 GHz) and high frequency bands (e.g., 45 GHz, 60 GHz).

[0056] It should be understood that the specific forms of STA devices and AP devices in the embodiments of the present application are not particularly limited and are merely illustrative.

[0057] Capabilities information

[0058] Due to differences in hardware, software, etc., different communication devices have different capabilities. Generally, it is necessary to perform corresponding communication processes based on the capability information of the communication devices.

[0059] Capability information may be included in one or more of the following capability elements: very high throughput (VHT capabilities), high-efficiency (HE capabilities), and extremely high throughput (EHT capabilities). These capability elements may be used to indicate capability information for corresponding technologies. For example, the VHT capability element may be used to indicate one or more capabilities related to VHT technology.

[0060] The following illustrates the capability information discovery process using Figures 2A to 2E. It should be understood that Figures 2A to 2E are merely examples, and the capability information discovery process may also be implemented through other processes.

[0061] Passive Scan

[0062] If a STA wishes to associate with an AP and establish a connection, it can discover the AP through scanning. This allows the STA to obtain information about surrounding wireless networks. Scanning can be divided into passive scanning and active scanning. The following uses passive scanning as an example.

[0063] FIG2A is an example diagram of a capability discovery process based on passive scanning. FIG2A may include step S211.

[0064] In step S211, the AP sends a beacon frame.

[0065] The beacon frame may include basic service set (BSS) basic information, such as BSS identifier (BSSID), beacon interval, etc. The beacon frame may also include AP capability information.

[0066] STAs can obtain the capability information of corresponding APs by monitoring beacon frames sent by surrounding APs.

[0067] The AP may periodically broadcast and send one or more beacon frames. Exemplarily, in the case of sending multiple beacon frames, FIG2A may further include step S212 and / or step S213.

[0068] It is understandable that during the passive scanning process, the STA can obtain the capability information of the AP through the beacon frame.

[0069] Active Scan

[0070] As described above, scanning can also be achieved through an "active scanning" process. Figure 2B is an example diagram of a capability discovery process based on active scanning. Figure 2B may include steps S221 and S222.

[0071] In step S221 , the STA sends a probe request frame on a supported channel.

[0072] The probe request frame can be used to detect wireless networks in the surrounding area and can include the STA's own capability information.

[0073] After the APs around the STA receive the probe request frame, if the requirements are met, the APs may execute step S222 .

[0074] It should be noted that the probe request frame may specify a BSS identifier (ID) or may not specify any BSS identifier. If a BSS identifier is specified, the AP corresponding to the BSS identifier may execute step S222. If a BSS identifier is not specified, all APs that receive the probe request frame may execute step S222.

[0075] In step S222, the AP replies with a probe response frame.

[0076] The probe response frame may include capability information of the AP itself.

[0077] It is understandable that, during the active scanning process, the AP can obtain the capability information of the STA through the probe request frame; and the STA can obtain the capability information of the AP through the probe response frame.

[0078] association

[0079] In order to access a wireless network (eg, a WLAN network) to achieve communication, a STA may associate with a specific AP.

[0080] Fig. 2C is an example diagram of an association-based capability discovery process, which may include steps S231 and S232.

[0081] In step S231, the STA sends an association request frame to the AP.

[0082] The association request frame may carry one or more of the STA's own capability information, such as the rate, channel, and quality of service (QoS) capability supported by the STA.

[0083] After the AP receives the association request frame, it can detect the capabilities reported by the STA and execute step S232.

[0084] In step S232, the AP sends an association response frame to the STA.

[0085] The association response frame may be used to notify the STA whether the association with the STA is successful. The association response frame may carry the capability information of the AP itself.

[0086] It is understandable that, during the association process, the AP can obtain the capability information of the STA through the association request frame; and the STA can obtain the capability information of the AP through the association response frame.

[0087] Reassociation

[0088] When a STA roams within the same extended service set (ESS), association with another AP can be achieved through a reassociation process.

[0089] FIG2D is an example diagram of a capability discovery process based on re-association, which may include steps S241 and S242.

[0090] In step S241 , the STA sends a reassociation request frame to the AP.

[0091] The reassociation request frame may carry the address of the current AP and the capability information of the STA itself.

[0092] After receiving the reassociation request frame, the AP may execute step S242.

[0093] In step S242, the AP sends a reassociation response frame to the STA.

[0094] The reassociation response frame can be used to inform the STA whether the association is successful. The reassociation response frame can also carry the AP's own capability information.

[0095] It is understandable that, during the reassociation process, the AP can obtain the capability information of the STA through the reassociation request frame; and the STA can obtain the capability information of the AP through the reassociation response frame.

[0096] Certification

[0097] Figure 2E is an example diagram of a capability discovery process based on authentication. The method shown in Figure 2E may include steps S251 to S254.

[0098] In step S251, the STA sends an authentication request frame to the AP.

[0099] After receiving the authentication request frame, the AP may randomly generate a challenge code (challenge) and may also execute step S252.

[0100] In step S252, the AP sends an authentication response frame to the STA.

[0101] The authentication response frame may include a challenge code.

[0102] After receiving the challenge code, the STA can use its own key to encrypt the challenge code.

[0103] In step S253, the STA sends an authentication frame to the AP.

[0104] The authentication frame may include encrypted information, that is, the challenge code encrypted by the STA.

[0105] After receiving the encrypted information, the AP decrypts it using its own key to determine the authentication result. If the decrypted challenge code is still the AP-generated challenge code, the authentication result is successful. If the decrypted challenge code is not the AP-generated challenge code, the authentication result is failed.

[0106] In step S254, the AP sends an authentication response frame to the STA.

[0107] The authentication response frame may include the authentication result.

[0108] It should be noted that both the Authentication Request frame and the Authentication Response frame are specific types of Authentication frames. Authentication frames can be used to carry a device's own capability information. For example, an Authentication Request frame can carry a STA's own capability information. Another example is an Authentication Response frame can carry an AP's own capability information.

[0109] It is understood that based on the above process, a device can send its own capability information. In some embodiments, a device can send capability information of other devices. The following uses the Nearby Report element and the simplified Nearby Report element to illustrate how a device sends capability information of other devices.

[0110] Nearby reporting elements

[0111] The Nearby Report element can carry description information of other APs (such as neighbor APs) near the AP. Based on the Nearby Report element, a non-AP STA can understand the status of other APs in the vicinity to facilitate handover.

[0112] FIG. 3A is a diagram showing an example format of a nearby report element.

[0113] As shown in Figure 3A, the proximity report element may include one or more of the following fields: element ID, length, BSS ID, BSSID information, operating class, channel number, physical layer type, and optional subelement. Some of these fields are described below.

[0114] The Element Identifier field may be used to indicate an identifier of an element. A value of 52 in the Element Identifier field may indicate that the element is a nearby reporting element.

[0115] The Length field may be used to indicate the number of bytes in a Nearby Report element in addition to the Element Identification field and the Length field.

[0116] The BSSID field may indicate the identifier of the BSS being reported. In other words, the BSSID may be used to indicate the AP reported by the element (hereinafter referred to as the reported AP). The fields following the BSSID field in the Nearby Report element may all be related to the BSS indicated by the BSSID field.

[0117] The BSSID information may include one or more of the following fields: AP reachability, security, key scope, capabilities, mobility domain, high throughput (HT), very high throughput (VHT), fine timing measurement (FTM), high efficiency (HE), extended range BSS (ER BSS), colocated AP, unsolicited probe responses active, member of ESS with 2.4 / 5GHz colocated AP, OCT supported with reporting AP, colocated with 6GHz AP, extremely high throughput, sensing, and reservation.

[0118] The Access Point Reachable field may be used to indicate whether the reported AP and STA can interact.

[0119] If the security field is set to 1, it may indicate that the AP indicated by this BSSID (reporting AP) supports the same security configuration as the STA currently associated with it. If this bit is 0, it may indicate that the AP does not support the same security configuration or that the security information is not available at this time.

[0120] If the Key Range field is set to 1, it indicates that the AP indicated by this BSSID has the same authenticator as the AP sending the report (hereinafter referred to as the sending AP). If this bit is 0, it means that the AP has a different authenticator or the relevant information is not available.

[0121] The Capabilities field may contain selected capability information for the AP indicated by the BSSID. The 1-bit subfield in this field has the same meaning and is set to the same value as the equivalent bit in the Capabilities Information field sent by the reporting AP in the beacon. Figure 3B illustrates an example format of the Capabilities Information field. As shown in Figure 3B, the Capabilities Information field may include one or more of the following fields: Spectrum Management, QoS, Automatic Power Save Delivery (APSD), Radio Measurement, and Reservation.

[0122] The mobility domain field is set to 1 to indicate that the AP indicated by the BSSID includes a mobility domain element (MDE) in its beacon frame, and the content of the MDE is the same as the MDE advertised by the sending AP.

[0123] The High Throughput field is set to 1 to indicate that the AP indicated by this BSSID is an HT AP and that the HT Capability element (or HT Operation element) (if included as a sub-element in the report) is identical to the HT Capability element (or HT Operation element) included in the beacon frames transmitted by the reporting AP. Otherwise, this sub-field is set to 0.

[0124] The Very High Throughput field is set to 1 to indicate that the AP indicated by this BSSID is a VHT AP and that the VHT Capability element (or VHT Operation element), if included as a sub-element in the report, is identical to the VHT Capability element (or VHT Operation element) included in the beacon frames transmitted by the reporting AP. Otherwise, this sub-field is set to 0.

[0125] The FTM field is set to 1 to indicate that the AP indicated by this BSSID is an AP that has set the fine timing measurement responder field in the extended capabilities element to 1. The FTM field is set to 0 to indicate that the dot11FineTimingMsmtRespActivated parameter of the reporting AP is equal to false, or the reporting AP has not set the fine timing measurement responder field in the extended capabilities element to 1, or the fine timing measurement responder field of the reporting AP is not available for the reporting AP.

[0126] The High Efficiency field is set to 1 to indicate that the AP indicated by this BSSID is a HE AP and that the HE capability element (or HE operation element) (if included as a sub-element in the report) is the same as the HE capability element (or HE operation element) included in the beacon frame transmitted by the reported AP; otherwise, this field is set to 0.

[0127] The ER BSS field may be set to 1 to indicate that the HE AP indicated by this BSSID uses HE ER SU PPDU to send beacon frames; otherwise, this field may be set to 0.

[0128] The Co-located AP field is set to 1 to indicate that the AP reported in this element is co-located with the AP that sent the element.

[0129] The Unsolicited Probe Response Active field may indicate that if the reporting AP is part of an ESS where all APs operate in the same channel as the reporting AP, are located on the same channel and within the coverage of the STA receiving the frame, and the dot11UnsolicitedProbeResponseOptionActivated parameter is equal to true, and transmits unsolicited probe response frames once every 20 time units (TUs) or less. Otherwise, or if the reporting AP does not have this information, it may be set to 0.

[0130] The Co-located with 2.4 / 5GHz AP and ESS Member field can indicate: if the reporting AP is part of an ESS and all APs in the ESS operate in the same frequency band as the reporting AP (regardless of the operating channel in that AP), the ESS Member subfield with 2.4 / 5GHz co-located APs is set to 1 and is located on the same channel and within range of the STA receiving this frame, the dot11MemberOfColocated6GHzESSOptionActivated parameter is equal to true, and there is also a corresponding AP operating in the 2.4GHz or 5GHz frequency band in the same co-located AP set. If the reporting AP does not have this information, it can be set to 0. If the reporting AP operates in the 2.4GHz or 5GHz frequency band, the value is retained.

[0131] The reported AP supports associated tunneling field set to 1 may indicate support for exchanging MPDUs with the AP reported in the neighbor report element through OCT; otherwise, this field may be set to 0.

[0132] The Co-location with 6 GHz AP field is set to 1 to indicate that the AP reported by the neighbor report element is in the same co-location AP set as the 6 GHz AP, and the reporting AP can discover the 6 GHz AP by receiving management frames. Otherwise, it is set to 0.

[0133] The Very High Throughput field is set to 1 to indicate that the AP represented by this BSSID (reporting AP) is an EHT AP and that the EHT Capability element (or EHT Operation element) (if included as a sub-element in the report) is the same as the EHT Capability element (or EHT Operation element) included in the beacon frame transmitted by the reporting AP. Otherwise, this field is set to 0.

[0134] If the AP identified by this BSSID is a sensing STA, the Sensing field may be set to 1. If the AP identified by this BSSID is not a sensing STA or information about its support for the WLAN sensing process is not available, the Sensing field is set to 0.

[0135] Streamlined nearby reporting elements

[0136] As described above, STAs can discover APs through scanning. To reduce scanning time and avoid STAs constantly scanning channels, APs can include a simplified Nearby Report Element in management frames. This simplified Nearby Report Element carries information about nearby APs (i.e., neighboring APs). STAs receiving these management frames can establish associations with these neighboring APs based on this information.

[0137] It should be noted that, in this application, the neighbor AP and the sending AP (the AP that sends this element) can meet any of the following requirements: a neighbor AP is an AP on another link in the AP MLD where the sending AP is located; a neighbor AP is another AP detected within the working area of ​​the sending AP; a neighbor AP is an AP co-located with the sending AP; or, for example, a neighbor AP is another affiliated AP that belongs to the same AP MLD as the currently affiliated AP. Alternatively, a neighbor AP can meet other definitions, which are not specifically limited in this application.

[0138] Figure 4 is an example diagram of a simplified neighborhood report element format. As shown in Figure 4, the simplified neighborhood report element may include the following fields: element ID, length, and one or more neighbor AP information fields.

[0139] One or more neighbor AP information fields may be used to indicate the target beacon transmission time (TBTT) and other information for a group of neighboring APs on the same channel.

[0140] A neighbor AP information field may include one or more of the following fields: TBTT information header, operating class, channel number, and TBTT information set.

[0141] The operating class field and the channel number field together may indicate the channel starting frequency of the primary channel of the BSS of the AP in the neighbor AP information field.

[0142] The Channel Number field may indicate the last known primary channel of the AP in the Neighbor AP Information field.

[0143] The TBTT information header field may include one or more of the following fields: TBTT information field type, filtered neighbor AP, reserved, TBTT information count, and TBTT information length.

[0144] The TBTT Information Field Type field and the TBTT Information Length field together indicate the format of the TBTT Information Field. The value of the TBTT Information Field Type field can be 0. Values ​​1, 2, and 3 are reserved.

[0145] The Filtered Neighbor APs field may have meaning except when the RNR element is in a probe response frame sent by a VHT AP, otherwise this field is reserved.

[0146] The TBTT information count field may be used to indicate the number of TBTT information fields included in the TBTT information set field minus one.

[0147] The TBTT information length field may be used to indicate the length of each TBTT information field.

[0148] The TBTT information set includes one or more TBTT information fields. The TBTT information field may include one or more of the following fields: the neighbor AP TBTT offset, BSSID (optional), short service set identifier (short SSID), BSS parameter, and 20MHz power spectral density (PSD).

[0149] The Neighbor AP TBTT Offset field may indicate a time offset in TUs. If the reporting AP is not part of a multi-BSSID set or is a transmitted BSSID of a multi-BSSID set, then the next TBTT for the reporting AP is from the previous TBTT of the AP that transmitted this element. If the reporting AP is part of a multi-BSSID set and is a non-transmitting BSSID, then the next TBTT for the transmitted BSSID of the multi-BSSID set of the reporting AP is from the previous TBTT of the AP that transmitted this element.

[0150] The BSSID field may be used to indicate the BSSID of the AP.

[0151] The Short SSID field may be used to indicate a shortened SSID.

[0152] The BSS parameter field can be used to indicate some parameters of the BSS referred to by the BSSID. The BSS parameter field can include one or more of the following fields: OCT recommended, same SSID, multiple BSSIDs, transmitted BSSID, member of ESS with 2.4 / 5GHz co-located AP, unsolicited probe response active, co-located AP, and reserved.

[0153] The channel transparent transmission recommendation field is set to 1 to indicate that the OCT is recommended to exchange MMPDU APs with the AP identified in the TBTT information field via wireless transmission to send reduced neighbor report elements; otherwise, it can be set to 0.

[0154] The Same SSID field may be set to 1 to indicate that the sending AP and the reporting AP have the same SSID; otherwise, it may be set to 0.

[0155] The Multiple BSSI field is set to 1 to indicate that the reported AP belongs to a set of multiple BSSIDs; otherwise it can be set to 0.

[0156] The Transmitted BSSID field is set to 1 to indicate that the reported AP is a transmitted BSSID. If the reported AP is an untransmitted BSSID, it is set to 0. If the Multiple BSSIDs field is set to 0, the field is reserved.

[0157] The Co-located with 2.4 / 5GHz AP and Member of Extended Service Set field can be used to indicate that if the reporting AP is part of an ESS and all APs in the ESS operate in the same frequency band as the reporting AP (regardless of the operating channel in that AP), are located on the same channel and within range of the STA receiving this frame, set dot11MemberOfCo-located6GHzESSOptionActivated to true, and have a corresponding AP operating in the 2.4GHz or 5GHz band that is in the same co-located AP set as this AP, then this field is set to 1. Otherwise, or if the reporting AP does not have this information, then this field is set to 0. If the reporting AP operates in the 2.4GHz or 5GHz band, then this value is retained.

[0158] The Unsolicited Probe Response Active field is set to 1 to indicate that if the reporting AP is part of an ESS where all APs operate in the same channel as the reporting AP and are located on the same channel and within range of the STA receiving this frame, then dot11UnsolicitedProbeResponseOptionActivated is equal to true and unsolicited probe response frames are transmitted every 20 TUs or less. Otherwise, or if the reporting AP does not have this information, it is set to 0.

[0159] If the AP is in the same co-located AP set as the sending AP, the Co-located AP field may be set to 1; otherwise, the field may be set to 0.

[0160] If present, the 20MHzPSD field indicates the maximum transmit power for the default category. The units of PSDEIRP can be interpreted as dBm / MHz, corresponding to the primary 20MHz channel being reported. The maximum transmit power is encoded as a 2's complement signed integer. The value –128 is reserved; a value of +127 indicates that the corresponding 20MHz channel does not have a specified maximum transmit power. For all other values ​​of Y in this subfield (i.e., –127 to +126), the maximum transmit power in the 20MHz channel is Y / 2dBm / MHz (i.e., ranging from –63.5 to +63dBm / MHz).

[0161] With the development of technology, communication devices can support more and more communication technologies. In other words, the capability information of communication devices is becoming more and more diverse. However, the related technologies for indicating capability information cannot adapt to technological development, making some communication technologies difficult to be effectively applied in actual communication scenarios.

[0162] Figure 5 is a schematic flowchart of a wireless communication method provided in an embodiment of the present application to address the aforementioned issues. The method shown in Figure 5 can be performed by a first device and a second device. Both the first device and the second device can be the communication devices described above. For example, the first device can be an AP or a non-AP STA. In another example, the second device can be an AP or a non-AP STA.

[0163] The method shown in FIG. 5 may include step S510 .

[0164] Step S510: The first device sends first indication information to the second device.

[0165] The first indication information may be used to indicate capability information of the target device. The target device is described below.

[0166] Optionally, the target device may include the first device. That is, the first indication information may be used to indicate capability information of the first device itself.

[0167] Optionally, the target device may include a third device. The third device may be a device different from both the first device and the second device. For example, the third device may be another device near the first device. Alternatively, the third device may be a neighboring device of the third device. For example, the first device may include an AP, and the third device may include one or more neighboring APs of the AP.

[0168] It should be noted that the target device may include one or more devices. The target device may include an AP and / or a non-AP STA. If the target device includes an AP, the AP may be referred to as a target AP. If the target device includes a non-AP STA, the non-AP STA may be referred to as a target non-AP STA.

[0169] It is understood that capability may refer to the target device's support for a certain technology or technologies. The support status may include, for example, whether the certain technology or technologies are supported; and the supported parameters (including maximum and / or minimum parameters, etc.) for the certain technology or technologies.

[0170] The present application proposes that the capability information of the target device indicated by the first indication information may include one or more of the following information of the target device: multi-AP coordinating capability; secondary channel access capability; priority access channel capability; support for link adaptation function; support for relay function; DRU-based transmission capability; mobility capability; power supply mode; preemption-related capabilities; target protocol support capability; enhanced roaming capability; support for TXOP sharing function based on non-triggered frames; energy saving capability; support for passive adjustment of A-MPDU length function; support for 320MHz frequency-domain aggregated PPDU; support for RU adaptation function; support for repeated transmission function; capability for communication based on insertable PPDU; and communication capability in frequency bands above 45GHz. They are explained below respectively.

[0171] Multi-AP coordination technology can also be called multi-AP collaboration technology. Multi-AP coordination can allow multiple APs to share transmission resources, thereby improving the utilization of transmission resources. AP can initiate or participate in the multi-AP coordinated transmission process. The modes of multi-AP coordination may include: collaborative uplink multi-user multiple input multiple output (UL MU-MIMO) transmission, coordinated beamforming (C-BF), coordinated spatial reuse (C-SR), multi-AP joint transmission (joint transmission), coordinated time division multiple access (C-TDMA) and coordinated orthogonal frequency division multiple access (C-OFDMA) transmission, etc. Based on this, the capabilities of multi-AP coordination may include one or more of the following: whether to support multi-AP coordination function, whether to initiate a multi-AP coordinated transmission process, whether to respond to a multi-AP coordinated transmission process, supported or not supported multi-AP coordination modes, etc.

[0172] Channels can be divided into primary channels and secondary channels (or called non-primary channels, auxiliary channels, supplementary channels, and sub-channels). When the target device can access the secondary channel, the communication device can determine whether to access the secondary channel based on the channel status of the primary channel. For example, when the channel status of the primary channel is idle, the device can communicate on the primary channel. For another example, when the channel status of the primary channel is busy, the device can switch to the secondary channel for communication. Based on this, the device can have the ability to access the secondary channel. The ability to access the secondary channel will be described in detail later and will not be repeated here.

[0173] Based on some communication technologies, communication devices can prioritize access to channels. For example, devices can achieve priority access based on enhanced distributed channel access (EDCA). Based on this, the capability of the priority access channel may include whether it supports EDCA-based priority access functionality.

[0174] Some communication devices may support a link adaptation function. For devices that support the link adaptation function, the device may set corresponding link parameters based on the link conditions. The link adaptation function may be specific to a specific communication technology. For example, the link adaptation function may refer to a link adaptation function that can be supported by UHR technology, that is, the link adaptation function may include the link adaptation function of UHR. The support status of the link adaptation function may include: whether the link adaptation function is supported.

[0175] During relay-based communication, devices can communicate with each other through a relay station. For example, STA1 can communicate with STA2 through a relay station. Specifically, the relay STA can forward signals sent by STA1 with STA2 as the destination station to STA2. The relay function support status can include whether the device supports the function of a relay station.

[0176] The DRU may have discontinuous subcarriers. Similarly, multiple resource units (MRU) may correspond to distributed multiple resource units (DMRU). The communication device may support DRUs of different bandwidths, that is, it may support sending and / or receiving PPDUs of DRUs of corresponding bandwidths. For example, the communication device may support one or more of the following DRUs with bandwidths less than or equal to 80MHz, 160MHz, and 320MHz. Based on this, the capabilities based on DRU transmission may include: whether DRU-based transmission is supported, the bandwidth of the supported DRUs, whether DRUs with a bandwidth less than or equal to 80MHz are supported, whether DRUs with a bandwidth of 160MHz are supported, whether DRUs with a bandwidth of 320MHz are supported, and whether enhanced distributed resource units (EDRUs) are supported.

[0177] Mobility refers to the ability of a communication device to move and communicate while on the move. Mobility can include whether the device is mobile. It should be noted that in related technologies, APs are mostly fixed due to factors like power supply. With technological advancements, APs can become mobile. Therefore, when the target device includes a target AP, mobility can also include whether the target AP is mobile.

[0178] There may be differences in the power supply mode of the device. For example, the device may be powered by a battery. For another example, the device may be powered by a non-battery (such as an external power supply). In this regard, the power supply mode may include: whether it is powered only by a battery. In the case where the target device includes an AP, in the related art, since the AP consumes a lot of power and does not need to be moved, the AP mostly needs to be non-battery powered. In UHR technology, the AP can be powered only by a battery. Based on this, the power supply mode may include: whether the target AP is powered only by a battery.

[0179] Some devices can initiate TXOP preemption (referred to as preemption) to seize the TXOP held by other devices. A device capable of initiating preemption is referred to as a preemption initiator. The TXOP holder can respond to the preemption to determine whether the preemption was successful. A device capable of responding to the preemption is referred to as a preemption responder. If the preemption is successful, the initiator can use the preempted TXOP for active signal transmission. Capabilities related to preemption may include support for preemption initiators and responders.

[0180] The target protocol may include the UHR protocol or other protocols. Based on this, the capability of supporting the target protocol may include: whether the UHR protocol is supported.

[0181] The enhanced roaming capability may include: whether to support the enhanced roaming function.

[0182] Some communication devices can implement TXOP sharing based on non-triggered frames. For example, the communication device can implement TXOP sharing through specific control frames. For example, if the UHR AP supports TXOP sharing based on non-triggered frames, the UHR AP can respond to the specific control frame to obtain the TXOP shared by the UHR non-AP STA to the UHR AP. For another example, if the UHR non-AP STA supports TXOP sharing based on non-triggered frames, the UHR Non-AP STA can send a specific control frame to share the TXOP with the UHR AP. Based on this, the support conditions for the TXOP sharing function based on non-triggered frames may include one or more of the following: whether TXOP sharing based on non-triggered frames is supported, whether the target AP can receive non-triggered frames to obtain the TXOP shared by the non-AP STA, and whether the target non-AP STA can send non-triggered frames to share the TXOP with the AP.

[0183] Some APs (e.g., UHR APs) can support certain operating modes, resulting in higher energy efficiency than other types of APs (EHT / HE / VHT / HT APs). These APs support the AP energy saving function. Energy saving capabilities may include whether the AP energy saving function is supported.

[0184] Some communication devices can passively adjust the length of the A-MPDU they send based on signaling sent by other devices. This function can be called the passive A-MPDU length adjustment function. The support status of the passive A-MPDU length adjustment function may include: whether the passive A-MPDU length adjustment function is supported.

[0185] Some communication devices may transmit and / or receive a frequency-domain aggregated PPDU with a bandwidth of 320 MHz. The support status of the frequency-domain aggregated PPDU with a bandwidth of 320 MHz may include: whether the transmission and / or reception of the frequency-domain aggregated PPDU with a bandwidth of 320 MHz is supported.

[0186] Some communication devices can autonomously puncture one or more RUs when sending a trigger-based (TB) PPDU to avoid interference from interfering signals. This function can be called RU adaptation. Based on this, the support status of the RU adaptation function can include: whether the RU adaptation function is supported.

[0187] The retransmission function may refer to a station using different transmission resources to transmit the same data within a PPDU. Transmission resources may include one or more of the following: frequency domain resources, time domain resources, and spatial domain resources. For example, a PPDU may use different RUs and / or OFDM symbols to transmit the same data. In other words, a device supporting the retransmission function may receive and / or send PPDUs that meet one or more of the following: frequency domain repetition, time domain repetition, and spatial domain repetition. It will be appreciated that the retransmission function can improve transmission reliability. The bandwidth supported for retransmission may vary between devices. For example, a communications device may support a PPDU with a retransmission bandwidth of less than or equal to 80 MHz, 160 MHz, or 320 MHz. Support for the retransmission function may include one or more of the following: whether the retransmission function is supported, the bandwidth supported for retransmission, whether retransmission with a bandwidth less than or equal to 80 MHz is supported, whether retransmission with a bandwidth equal to 160 MHz is supported, or whether retransmission with a bandwidth equal to 320 MHz is supported.

[0188] If the PPDU transmitted between the communicating devices is an insertable PPDU, then during the interaction process, the PPDU can be interrupted to transmit other PPDUs (e.g., a PPDU carrying more urgent data). Based on this, the capabilities of insertable PPDU communication may include: whether to support receiving insertable PPDUs and whether to support sending insertable PPDUs.

[0189] If a communication device has an attached link in a frequency band above 45 GHz, then the communication device can support transmission and reception in the frequency band above 45 GHz. Based on this, the communication capability in the frequency band above 45 GHz can include: whether reception and / or transmission in the frequency band above 45 GHz is supported, and whether an attached link in the frequency band above 45 GHz exists.

[0190] In some embodiments, the capability information indicated by the first indication information may be related to UHR technology, and / or the first indication information indicates capability information of a UHR site. Therefore, the capability information indicated by the first information may also be referred to as UHR capability information.

[0191] Optionally, the capability information indicated by the first indication information may also include other UHR technology-related capabilities and / or capabilities possessed by the UHR site.

[0192] Through the first indication information, communication devices (such as UHR devices) can effectively discover and understand the relevant capabilities of other communication devices, thereby achieving more efficient and accurate communication. For example, by using the capability information of the target AP indicated by the first indication information, a non-AP STA can more quickly and accurately select an appropriate AP for association.

[0193] It should be noted that the first indication information may be included in one or more elements, one or more frames, or one or more fields.

[0194] It should be noted that if the capabilities indicated by one or more fields of the first indication information are only capabilities that an AP can possess, the values ​​of the one or more fields may be retained when the target device is a non-AP STA. Similarly, if the capabilities indicated by one or more fields of the first indication information are only capabilities that a non-AP STA can possess, the values ​​of the one or more fields may be retained when the target device is an AP.

[0195] The following describes in detail the capabilities of secondary channel access.

[0196] In some embodiments, the secondary channel access capability may include one or more of the following capabilities of the target device: whether the secondary channel access function is supported; the physical layer version of the supported secondary channel access function; the number of secondary channels supported for access; information about the first channel supported for access; energy saving information used to perform secondary channel access; the delay in switching channels; the recommended secondary channel; the ability to send and / or receive PPDU on the secondary channel; whether it is possible to broadcast beacon frames on the secondary channel; whether it is possible to receive probe request frames on the secondary channel; and whether it is possible to reply to probe response frames on the secondary channel.

[0197] The physical layer versions of the supported secondary channel access functions may include, for example, one or more of the following: HT PHY, VHT PHY, HE PHY, EHT PHY, UHR PHY, etc.

[0198] Optionally, the physical layer versions of the supported secondary channel access functions may be represented by a bitmap. One or more bits in the bitmap may correspond one-to-one to one or more physical layer versions. For example, the bitmap may include 8 bits. Among them, B0 may indicate HT PHY; B1 may indicate VHT PHY; B2 may indicate HE PHY; B3 may indicate EHT PHY; B4 may indicate UHR PHY; and B5-B7 may be reserved.

[0199] For example, a value of 1 for the first bit in the bitmap may indicate that the target device supports the secondary channel access function of the corresponding PHY version; a value of 0 for the first bit may indicate that the target device supports the secondary channel access function of the corresponding PHY version. For example, a bitmap of 10101000 may indicate support for HT PHY, HE PHY, and UHR PHY; and not support for VHT PHY and EHT PHY.

[0200] For example, a value of 0 for the first bit in the bitmap may indicate that the target device supports the secondary channel access function of the corresponding PHY version; a value of 1 for the first bit may indicate that the target device supports the secondary channel access function of the corresponding PHY version. For example, a bitmap of 10101000 may indicate that HT PHY, HE PHY, and UHR PHY are not supported, and VHT PHY and EHT PHY are supported.

[0201] The recommended secondary channel is the secondary channel that is preferentially recommended when the primary channel is busy. If multiple secondary channels are recommended, the first, last, or any one of the recommended secondary channels may be preferentially used.

[0202] Energy conservation can include: communications devices reducing energy consumption in active states by intermittently dormant. Energy conservation information used for secondary channel access can indicate one or more of the following: whether the target device is using energy conservation on the secondary channel; the energy conservation mode used by the target device on the secondary channel; and the time window during which the target device is active in energy conservation mode. Energy conservation modes may include, for example, periodic dormancy and random dormancy. The time window can be a period of time. The time window can be represented by one or more of the following: start time, duration, end time, period, etc.

[0203] If the target device supports one or more of the following: broadcasting beacon frames on the secondary channel, receiving probe frames on the secondary channel, and replying probe response frames on the secondary channel, other devices can scan for the target device on the secondary channel. If the first indication information indicates the secondary channel access capability, other non-AP STAs can scan for the target device on the secondary channel, thereby more quickly scanning for the target device.

[0204] The channel switching delay may refer to the time required for the target device to switch the working channel. This application does not limit the unit of the channel switching delay. For example, the unit may be microseconds or milliseconds.

[0205] The secondary channel access capability may include the capability of accessing one or more secondary channels. The one or more secondary channels may be sub-channels that support access, that is, the number of the one or more sub-channels may be the number of sub-channels that support access. The one or more secondary channels may include a primary channel. In other words, the information of the primary channel may include information about a sub-channel that the target device supports accessing. For example, the first indication information may indicate information about each sub-channel that the target device supports accessing.

[0206] The information of the first channel may include one or more of the following information of the first channel: an identifier; a bandwidth; second indication information; a center frequency; and information of included punctured channels.

[0207] The identifier can be used to distinguish different secondary channels. That is, the primary channel can have a unique identifier to distinguish it from other channels.

[0208] The bandwidth of the first channel can be 20 MHz, 40 MHz, 80 MHz, 160 MHz, or 320 MHz. The bandwidth of the first channel can be indicated by an index. For example, an index value of 0 can indicate a bandwidth of 20 MHz; a value of 1 can indicate a bandwidth of 40 MHz; a value of 2 can indicate a bandwidth of 80 MHz; a value of 3 can indicate a bandwidth of 160 MHz; a value of 4 can indicate a bandwidth of 320 MHz; and values ​​5-7 are reserved.

[0209] Similarly, the center frequency of the first sub-channel can be indicated by an index.

[0210] The second indication information may be used to indicate whether it is recommended to give priority to using the first channel.

[0211] The first channel may include punctured channels (or sub-channels). Exemplarily, the channels within the first channel may be punctured with a granularity of 20 MHz. That is, the bandwidth of the first channel may be divided into one or more 20 MHz sub-channels. The information of the first channel may respectively indicate the puncturing conditions of one or more 20 MHz sub-channels. For example, the information of the punctured channels contained in the first channel may be identified by a bitmap. One or more bits in the bitmap may correspond one-to-one to one or more sub-channels contained in the first channel. Exemplarily, the bitmap may be 16 bits. The lowest numbered bit in the bitmap may correspond to the 20 MHz sub-channel with the lowest frequency within the bandwidth of the first channel. For subsequent bits, each consecutive bit may correspond to the next higher frequency 20 MHz sub-channel. Bits in the bitmap that exceed the bandwidth of the first channel may be reserved. The first bit in the bitmap is set to 1 to indicate that the corresponding 20 MHz sub-channel is punctured, and is set to 0 to indicate that the corresponding 20 MHz sub-channel is not punctured. Alternatively, the first bit in the bitmap is set to 0 to indicate that the corresponding 20 MHz sub-channel is punctured, and is set to 1 to indicate that the corresponding 20 MHz sub-channel is not punctured.

[0212] In some embodiments, the capability of secondary channel access may be included in a secondary channel operation element.

[0213] FIG6 is a schematic diagram of a secondary channel operation element format provided in an embodiment of the present application.

[0214] As shown in Figure 6, the secondary channel operation element may include one or more of the following fields: element identifier, length, element identifier extension, PHY support, number of secondary channels, secondary channel set, power save mode, available window, channel switch delay, and optional sub-elements. Each of these fields is described below.

[0215] The element identifier can be used to indicate the identifier of the secondary channel operation element. The value of the element identifier can be 255, indicating that the element is an extended element and needs to be combined with the element extension identifier to determine the type of the element.

[0216] The length field is used to indicate the number of bytes in the element in addition to the element identifier and length fields.

[0217] The Element Identification Extension field is used to indicate the element extension identifier. The value of the Element Identification Extension field can be any integer between 135 and 255, thereby indicating that the element is a secondary channel operation element in conjunction with the Element Identification field. For example, the value of the Element Identification Extension field can be 158.

[0218] The Physical Layer Support field can be used to indicate the physical layer version of the secondary channel access function supported by the target device. The Physical Layer Support field can be in the form of a bitmap. In the bitmap, each bit with a value of 1 indicates support for the corresponding PHY version, and a value of 0 indicates non-support of the corresponding PHY version. As an example, B0 can indicate HT PHY, B1 can indicate VHT PHY, B2 can indicate HE PHY, B3 can indicate EHT PHY, B4 can indicate UHR PHY, and B5-B7 are reserved.

[0219] The Secondary Channel Number field may indicate the number of secondary channels supported by the target device. In other words, the Secondary Channel Number field may indicate the number of secondary channels included in this element, that is, the number of secondary channels indicated in the Secondary Channel Set field.

[0220] The secondary channel set field may indicate specific information about one or more secondary channels. One or more secondary channels may be secondary channels that the target device supports access to. The secondary channel set field may include information fields for one or more secondary channels. The number of secondary channel information fields included in the secondary channel set field may be consistent with the indication of the secondary channel number field. The secondary channel information field may include one or more of the following fields: control, channel center frequency (represented by CCFS in FIG6 ), and disabled subchannel bitmap.

[0221] The control field may include one or more of the following fields: channel ID, channel bandwidth, suggested secondary channels, and reserved.

[0222] The channel identification field may indicate an identifier of a secondary channel, for example, a unique identifier of a secondary channel. The information field of the secondary channel indicates information of the secondary channel identified by the channel identification field.

[0223] The Channel Bandwidth field may indicate the bandwidth of the corresponding secondary channel. For example, the correspondence between the Channel Bandwidth field value and the bandwidth may be: a value of 0 indicates 20 MHz; a value of 1 indicates 40 MHz; a value of 2 indicates 80 MHz; a value of 3 indicates 160 MHz; a value of 4 indicates 320 MHz; and values ​​5-7 are reserved.

[0224] The Recommended Secondary Channel field may indicate whether this channel is recommended for priority use. For example, a value of 1 in the Recommended Secondary Channel field may indicate yes (i.e., recommended for priority use), while a value of 0 in the Recommended Secondary Channel field may indicate no (i.e., not recommended for priority use). For another example, a value of 0 in the Recommended Secondary Channel field may indicate yes, while a value of 1 in the Recommended Secondary Channel field may indicate no.

[0225] The CCFS field may indicate the index of the center frequency of the current channel.

[0226] The Disable Subchannel Bitmap field may indicate information about the punctured channels within this subchannel. The Disable Subchannel Bitmap may be a 16-bit bitmap. The lowest numbered bit may correspond to the 20 MHz subchannel with the lowest frequency within the secondary channel bandwidth. Each consecutive bit in the bitmap corresponds to the next higher frequency 20 MHz subchannel. A bit in the bitmap within the secondary channel bandwidth may be set to 1 to indicate that the corresponding 20 MHz subchannel is punctured, and may be set to 0 to indicate that the corresponding 20 MHz subchannel is not punctured. Bits in the bitmap that exceed the secondary channel bandwidth may be reserved.

[0227] The Energy Saving Mode field can indicate whether the target device is using energy saving mode on the secondary channel, or the type of energy saving mode used. A value of 0 indicates that energy saving mode is not used, a value of 1 indicates energy saving mode 1 (e.g., periodic sleep), a value of 2 indicates energy saving mode 2 (e.g., random sleep), and other values ​​are reserved.

[0228] When the energy saving mode field indicates that the target device is in a certain energy saving mode, the available window field may indicate a time window in which the target device is in an active state in the energy saving mode.

[0229] The Channel Switching Delay field indicates the time required for the target device to switch its operating channel. The unit can be microseconds or milliseconds.

[0230] The optional Capabilities element field can be used to indicate the target device's capabilities when sending or receiving PPDUs on a secondary channel. This field allows the target device's capabilities for receiving PPDUs on both the secondary and primary channels to be indicated separately. This allows accurate capability indication even when the target device's capabilities on the secondary channel differ from those on the primary channel.

[0231] For example, the optional Capabilities Element field may contain one or more elements detailing the capabilities of the target device on a secondary channel. Each element in Table 1 indicates the capabilities of a station when transmitting or receiving a PPDU on a secondary channel, which may differ from the capabilities of the station when transmitting or receiving a PPDU on a primary channel.

[0232] The capability-related elements may include one or more of the following: HT capability element, VHT capability element, HE capability element, EHT capability element, UHR capability element, basic multi-link. The definition or format of these capability elements may be as described in this application or related technologies.

[0233] The corresponding relationship between the subelement ID and the capability-related elements may be shown in Table 1.

[0234] Table 1

[0235] It should be noted that some of the contents in Table 1 can be implemented independently. In other words, some of the contents in Table 1 can be deleted and then implemented. In addition, contents can be added to Table 1. This application does not impose any restrictions on this.

[0236] The secondary channel operation element can be included in one or more of the following frames: a beacon frame, an association request frame, an association response frame, a reassociation request frame, a reassociation response frame, a probe request frame, and a probe response frame. It is understood that all frames involved in the capability discovery process described above can include a secondary channel operation element. In other words, the discovery process for secondary channel access capabilities can be implemented through the capability discovery process described above.

[0237] As noted above, the target device may include a first device, i.e., the first indication information may indicate its own capability information. In this case, some or all of the information in the first indication information may be included in the first capability element. As described above, the capability information indicated by the first indication information may be related to UHR technology. Therefore, in some embodiments, the first capability element may also be referred to as a UHR capability element, i.e., an element used to indicate capabilities related to UHR.

[0238] The first capability element may be used to indicate whether the first device supports one or more of the following: multi-AP coordination function; secondary channel access function; initiator in the preemption function; responder in the preemption function; priority channel access function; link adaptation function; relay function; enhanced roaming function; TXOP sharing function based on non-triggered frames; AP energy saving function; passive adjustment of A-MPDU length function; 320MHz frequency domain aggregation PPDU; distributed RU; enhanced distributed RU; RU adaptation function; repeated transmission function; receiver in the insertable PPDU function; sender in the insertable PPDU function; and transmission and reception in frequency bands above 45GHz. The above information is described in detail above and will not be repeated here.

[0239] Optionally, the capability information indicated by the first capability element may include MAC capability information and / or PHY capability information. The MAC capability information may be related to the capability of the MAC of the first device. For example, the MAC capability information may be used to indicate whether the first device supports one or more of the following: multi-AP coordination function; secondary channel access function; initiator in the preemption function; responder in the preemption function; priority channel access function; link adaptation function; relay function; enhanced roaming function; TXOP sharing function based on non-triggered frames; AP energy saving function; A-MPDU length passive adjustment function; 320MHz frequency domain aggregation PPDU. The PHY capability information may be related to the capability of the PHY of the first device. For example, the PHY capability information may be used to indicate whether the first device indicates one or more of the following: distributed RU; enhanced distributed RU; RU adaptation function; repeated transmission function; receiver that can be inserted into PPDU function; sender that can be inserted into PPDU function; transceiver in frequency bands above 45GHz.

[0240] It should be noted that, in the case where the first capability element indicates a secondary channel access function, the first capability element may include the secondary channel operation element described above.

[0241] The first capability element may also indicate other capability information. For example, the first capability element may also indicate one or more of the following information of the first device: the supported combinations of UHR-MCS and number of spatial streams (NSS) for reception and transmission; the nominal physical layer packet extension (PPE) value for specific RU, MRU, DRU, and EDRU allocations and specific NSS in the UHR PPDU.

[0242] FIG7A is a diagram showing an example format of a first capability element provided in an embodiment of the present application.

[0243] As shown in Figure 7A, the first capability element may include one or more of the following fields: element identifier, length, element identifier extension, UHR MAC capability information (UHR MAC capabilities information), UHR PHY capability information (UHR PHY capabilities information), supported UHR-MCS and spatial stream number set (supported UHR-MCS And NSS set), UHR packet fill threshold (UHR PPE thresholds).

[0244] The element identification field can be used to indicate the identifier of the first capability element. The value of the element identification field can be 255 to indicate that the element is an extended element, that is, the element identification field and the element identification extension field need to be combined to indicate the element.

[0245] The length field may be used to indicate the number of bytes in the first capability element excluding the element identification field and the length field.

[0246] The Element Identification Extension field can be used to indicate an element extension identifier. The Element Identification Extension field can be combined with the Element Identification field to indicate that the element is a first capability element. The value of the Element Identification Extension field can be any integer between 135 and 255. For example, the value of the Element Identification Extension field can be 155.

[0247] The UHR MAC capability information field may indicate MAC capability information of the first device.

[0248] The UHR PHY capability information field may indicate PHY capability information of the first device.

[0249] The Supported UHR-MCS and Spatial Stream Sets field may indicate a combination of UHR-MCS and the number of spatial streams supported for reception and transmission by the first device.

[0250] The UHR Packet Filling Amount Threshold field may indicate the nominal packet filling value for a specific RU, MRU, DRU, and EDRU allocation and a specific NSS in a UHR PPDU.

[0251] The formats of the UHR MAC capability information field and the UHR PHY capability information field are described in detail below with reference to FIG. 7B and FIG. 7C .

[0252] FIG7B is a schematic diagram showing the format of the UHR MAC capability information field.

[0253] As shown in Figure 7B, the UHR MAC capability information field may include one or more of the following fields: maximum MPDU length, maximum A-MPDU length exponent extension, UHR link adaptation support, multi-AP coordination support, secondary channel access support, priority access support, UHR relay support, enhanced roaming support, non-triggered TXOP sharing support, AP power save mode support, A-MPDU length adaptation support, and frequency aggregation PPDU (BW=320MHz).

[0254] The UHR Link Adaptation Support field may be used to indicate whether the first device supports UHR link adaptation functionality. In some embodiments, a value of 1 for the UHR Link Adaptation Support field may indicate that the first device supports UHR link adaptation. A value of 0 for the UHR Link Adaptation Support field may indicate that the first device does not support UHR link adaptation. In some embodiments, a value of 0 for the UHR Link Adaptation Support field may indicate that the first device supports UHR link adaptation. A value of 1 for the UHR Link Adaptation Support field may indicate that the first device does not support UHR link adaptation.

[0255] The multi-AP coordination support field can be used to indicate whether the first device supports the multi-AP coordination function. In some embodiments, when the first device is a UHR AP site, the multi-AP coordination support field value 1 can indicate that the UHR AP can support the multi-AP coordination function. The multi-AP coordination support field value 0 can indicate that the UHR AP cannot support the multi-AP coordination function. In some embodiments, when the first device is a UHR AP site, the multi-AP coordination support field value 0 can indicate that the UHR AP can support the multi-AP coordination function. The multi-AP coordination support field value 1 can indicate that the UHR AP cannot support the multi-AP coordination function. When the first device is a UHR non-AP STA, the multi-AP coordination support field can be retained.

[0256] The Secondary Channel Access Support field may be used to indicate whether the first device supports the secondary channel access function. In some embodiments, a value of 1 in the Secondary Channel Access Support field may indicate that the first device is capable of supporting the secondary channel access function. A value of 0 in the Secondary Channel Access Support field may indicate that the first device is not capable of supporting the secondary channel access function. In some embodiments, a value of 0 in the Secondary Channel Access Support field may indicate that the first device is capable of supporting the secondary channel access function. A value of 1 in the Secondary Channel Access Support field may indicate that the first device is not capable of supporting the secondary channel access function.

[0257] The Priority Access Support field may be used to indicate whether the first device supports the priority channel access function. In some embodiments, a value of 1 in the Priority Access Support field may indicate that the first device is capable of supporting the priority access function based on EDCA. A value of 0 in the Priority Access Support field may indicate that the first device is not capable of supporting the priority access function based on EDCA. In some embodiments, a value of 0 in the Priority Access Support field may indicate that the first device is capable of supporting the priority access function based on EDCA. A value of 1 in the Priority Access Support field may indicate that the first device is not capable of supporting the priority access function based on EDCA.

[0258] The UHR Relay Support field may be used to indicate whether the first device supports relay functionality. In some embodiments, a value of 1 in the UHR Relay Support field may indicate that the first device can serve as a relay site. A value of 0 in the UHR Relay Support field may indicate that the first device cannot serve as a relay site. In some embodiments, a value of 0 in the UHR Relay Support field may indicate that the first device can serve as a relay site. A value of 1 in the UHR Relay Support field may indicate that the first device cannot serve as a relay site.

[0259] The Enhanced Roaming Support field may be used to indicate whether the first device supports enhanced roaming functionality. In some embodiments, a value of 1 in the Enhanced Roaming Support field may indicate that the first device is capable of supporting enhanced roaming functionality. A value of 0 in the Enhanced Roaming Support field may indicate that the first device is not capable of supporting enhanced roaming functionality. In some embodiments, a value of 0 in the Enhanced Roaming Support field may indicate that the first device is capable of supporting enhanced roaming functionality. A value of 1 in the Enhanced Roaming Support field may indicate that the first device is not capable of supporting enhanced roaming functionality.

[0260] The non-triggered-based TXOP sharing support field may be used to indicate whether the first device supports a non-triggered frame-based TXOP sharing function.

[0261] In some embodiments, when the first device is a UHR AP, a value of 1 in the Untriggered TXOP Sharing Support field may indicate that the UHR AP can respond to specific control frames, thereby obtaining the TXOP time shared by the UHR Non-AP STA with the UHR AP; a value of 0 in the Untriggered TXOP Sharing Support field may indicate that the UHR AP cannot respond to specific control frames, that is, cannot obtain the TXOP time shared by the UHR Non-AP STA with the UHR AP. When the first device is a UHR AP, a value of 0 in the Untriggered TXOP Sharing Support field may indicate that the UHR AP can respond to specific control frames, thereby obtaining the TXOP time shared by the UHR Non-AP STA with the UHR AP; a value of 1 in the Untriggered TXOP Sharing Support field may indicate that the UHR AP cannot respond to specific control frames, that is, cannot obtain the TXOP time shared by the UHR Non-AP STA with the UHR AP.

[0262] In some embodiments, when the first device is a UHR Non-AP STA, a value of 1 in the Non-triggered TXOP Sharing Support field may indicate that the UHR non-AP STA can send specific control frames, thereby sharing the TXOP time with the UHR AP; a value of 0 in the Non-triggered TXOP Sharing Support field may indicate that the UHR non-AP STA cannot send specific control frames, that is, cannot share the TXOP time with the UHR AP. When the first device is a UHR Non-AP STA, a value of 0 in the Non-triggered TXOP Sharing Support field may indicate that the UHR non-AP STA can send specific control frames, thereby sharing the TXOP time with the UHR AP; a value of 1 in the Non-triggered TXOP Sharing Support field may indicate that the UHR non-AP STA cannot send specific control frames, that is, cannot share the TXOP time with the UHR AP.

[0263] The AP Energy Saving Mode Support field can be used to indicate whether the first device supports the AP energy saving function. In some embodiments, when the station is a UHR AP, the AP Energy Saving Mode Support field takes a value of 1, indicating that the UHR AP can support the AP energy saving function; the AP Energy Saving Mode Support field takes a value of 0, indicating that the UHR AP cannot support the AP energy saving function. In some embodiments, when the station is a UHR AP, the AP Energy Saving Mode Support field takes a value of 0, indicating that the UHR AP can support the AP energy saving function; the AP Energy Saving Mode Support field takes a value of 1, indicating that the UHR AP cannot support the AP energy saving function. When the first device is a UHR Non-AP STA, the AP Energy Saving Mode Support field can be retained.

[0264] The A-MPDU Length Adaptation Support field may be used to indicate whether the first device supports the A-MPDU length passive adjustment function. In some embodiments, a value of 1 in the A-MPDU Length Adaptation Support field may indicate that the first device can support the A-MPDU length passive adjustment function. A value of 0 in the A-MPDU Length Adaptation Support field may indicate that the first device cannot support the A-MPDU length passive adjustment function. In some embodiments, a value of 0 in the A-MPDU Length Adaptation Support field may indicate that the first device can support the A-MPDU length passive adjustment function. A value of 1 in the A-MPDU Length Adaptation Support field may indicate that the first device cannot support the A-MPDU length passive adjustment function.

[0265] The 320MHz Frequency Domain Aggregation PPDU Support field may be used to indicate whether the first device supports 320MHz frequency domain aggregation PPDUs. In some embodiments, a value of 1 in the 320MHz Frequency Domain Aggregation PPDU Support field may indicate that the first device is capable of supporting the transmission or reception of frequency domain aggregation PPDUs with a bandwidth of 320MHz. A value of 0 in the 320MHz Frequency Domain Aggregation PPDU Support field may indicate that the first device is not capable of supporting the transmission or reception of frequency domain aggregation PPDUs with a bandwidth of 320MHz. In some embodiments, a value of 0 in the 320MHz Frequency Domain Aggregation PPDU Support field may indicate that the first device is capable of supporting the transmission or reception of frequency domain aggregation PPDUs with a bandwidth of 320MHz. A value of 1 in the 320MHz Frequency Domain Aggregation PPDU Support field may indicate that the first device is not capable of supporting the transmission or reception of frequency domain aggregation PPDUs with a bandwidth of 320MHz.

[0266] FIG7C is a schematic diagram of the format of a UHR PHY capability information field provided in an embodiment of the present application.

[0267] As can be seen from Figure 7C, the UHR PHY capability information field may include one or more of the following fields: support for DRU (BW≤80MHz) with a bandwidth less than or equal to 80MHz, support for DRU (BW=160MHz) with a bandwidth equal to 160MHz, support for DRU (BW=320MHz), support for EDRU, replication (BW≤80MHz) with a bandwidth less than or equal to 80MHz, replication (BW=160MHz) with a bandwidth equal to 320MHz, replication (BW=320MHz), RU adaptation, rx inserted PPDU support, tx inserted PPDU support, auxiliary link above 45GHz, and reserved. These fields are described below.

[0268] The DRU Support field with bandwidth less than or equal to 80 MHz is used to indicate whether the first device supports sending and / or receiving PPDUs for DRUs with bandwidth less than or equal to 80 MHz. In some embodiments, a value of 1 for the DRU Support field with bandwidth less than or equal to 80 MHz may indicate that the first device supports sending and / or receiving PPDUs for DRUs with bandwidth less than or equal to 80 MHz. A value of 0 for the DRU Support field with bandwidth less than or equal to 80 MHz may indicate that the first device does not support sending and / or receiving PPDUs for DRUs with bandwidth less than or equal to 80 MHz. In some embodiments, a value of 0 for the DRU Support field with bandwidth less than or equal to 80 MHz may indicate that the first device supports sending and / or receiving PPDUs for DRUs with bandwidth less than or equal to 80 MHz. A value of 1 for the DRU Support field with bandwidth less than or equal to 80 MHz may indicate that the first device does not support sending and / or receiving PPDUs for DRUs with bandwidth less than or equal to 80 MHz.

[0269] The DRU Support field with bandwidth equal to 160 MHz is used to indicate whether the first device supports sending and / or receiving PPDUs for DRUs with bandwidth equal to 160 MHz. In some embodiments, a value of 1 for the DRU Support field with bandwidth equal to 160 MHz may indicate that the first device supports sending and / or receiving PPDUs for DRUs with bandwidth equal to 160 MHz. A value of 0 for the DRU Support field with bandwidth equal to 160 MHz may indicate that the first device does not support sending and / or receiving PPDUs for DRUs with bandwidth equal to 160 MHz. In some embodiments, a value of 0 for the DRU Support field with bandwidth equal to 160 MHz may indicate that the first device supports sending and / or receiving PPDUs for DRUs with bandwidth equal to 160 MHz. A value of 1 for the DRU Support field with bandwidth equal to 160 MHz may indicate that the first device does not support sending and / or receiving PPDUs for DRUs with bandwidth equal to 160 MHz.

[0270] The DRU Support field with bandwidth equal to 320 MHz is used to indicate whether the first device supports sending and / or receiving PPDUs for DRUs with bandwidth equal to 320 MHz. In some embodiments, a value of 1 for the DRU Support field with bandwidth equal to 320 MHz may indicate that the first device supports sending and / or receiving PPDUs for DRUs with bandwidth equal to 320 MHz. A value of 0 for the DRU Support field with bandwidth equal to 320 MHz may indicate that the first device does not support sending and / or receiving PPDUs for DRUs with bandwidth equal to 320 MHz. In some embodiments, a value of 0 for the DRU Support field with bandwidth equal to 320 MHz may indicate that the first device supports sending and / or receiving PPDUs for DRUs with bandwidth equal to 320 MHz. A value of 1 for the DRU Support field with bandwidth equal to 320 MHz may indicate that the first device does not support sending and / or receiving PPDUs for DRUs with bandwidth equal to 320 MHz.

[0271] The EDRU Support field is used to indicate whether the first device supports EDRUs. In some embodiments, a value of 1 in the EDRU Support field may indicate support for sending and / or receiving PPDUs for enhanced DRUs. A value of 0 in the EDRU Support field may indicate that sending and / or receiving PPDUs for enhanced DRUs is not supported. In some embodiments, a value of 0 in the EDRU Support field may indicate support for sending and / or receiving PPDUs for enhanced DRUs. A value of 1 in the EDRU Support field may indicate that sending and / or receiving PPDUs for enhanced DRUs is not supported.

[0272] The repetition transmission field with bandwidth less than or equal to 80 MHz can be used to indicate whether the first device supports the repetition transmission function less than or equal to 80 MHz. In some embodiments, the repetition transmission field with bandwidth less than or equal to 80 MHz taking a value of 1 can indicate that the first device supports sending and / or receiving PPDUs with bandwidth less than or equal to 80 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, spatial domain repetition. The repetition transmission field with bandwidth less than or equal to 80 MHz taking a value of 0 can indicate that the first device does not support sending and / or receiving PPDUs with bandwidth less than or equal to 80 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, spatial domain repetition. In some embodiments, the repetition transmission field with bandwidth less than or equal to 80 MHz taking a value of 0 can indicate that the first device supports sending and / or receiving PPDUs with bandwidth less than or equal to 80 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, spatial domain repetition. The value 1 of the Repeat Transmission field with bandwidth less than or equal to 80 MHz may indicate that the first device does not support sending and / or receiving PPDU with bandwidth less than or equal to 80 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, and spatial domain repetition.

[0273] The Repeat Transmission field with a bandwidth equal to 160 MHz can be used to indicate whether the first device supports the repeat transmission function equal to 160 MHz. In some embodiments, a value of 1 in the Repeat Transmission field with a bandwidth equal to 160 MHz can indicate that the first device supports sending and / or receiving PPDUs with a bandwidth equal to 160 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, and spatial domain repetition. A value of 0 in the Repeat Transmission field with a bandwidth equal to 160 MHz can indicate that the first device does not support sending and / or receiving PPDUs with a bandwidth equal to 160 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, and spatial domain repetition. In some embodiments, a value of 0 in the Repeat Transmission field with a bandwidth equal to 160 MHz can indicate that the first device supports sending and / or receiving PPDUs with a bandwidth equal to 160 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, and spatial domain repetition. A value of 1 in the Repeat Transmission field with a bandwidth equal to 160 MHz can indicate that the first device does not support sending and / or receiving PPDUs with a bandwidth equal to 160 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, and spatial domain repetition.

[0274] The Repeat Transmission with Bandwidth Equal to 320 MHz field can be used to indicate whether the first device supports the repeat transmission function equal to 320 MHz. In some embodiments, a value of 1 in the Repeat Transmission with Bandwidth Equal to 320 MHz field can indicate that the first device supports sending and / or receiving PPDUs with a bandwidth equal to 320 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, and spatial domain repetition. A value of 0 in the Repeat Transmission with Bandwidth Equal to 320 MHz field can indicate that the first device does not support sending and / or receiving PPDUs with a bandwidth equal to 320 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, and spatial domain repetition. In some embodiments, a value of 0 in the Repeat Transmission with Bandwidth Equal to 320 MHz field can indicate that the first device supports sending and / or receiving PPDUs with a bandwidth equal to 320 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, and spatial domain repetition. A value of 1 in the Repeat Transmission with Bandwidth Equal to 320 MHz field can indicate that the first device does not support sending and / or receiving PPDUs with a bandwidth equal to 320 MHz and meeting one or more of the following: frequency domain repetition, time domain repetition, and spatial domain repetition.

[0275] The RU Adaptation field is used to indicate whether the first device supports RU adaptation. In some embodiments, a value of 1 in the RU Adaptation field may indicate support for sending and / or receiving PPDUs with adaptive RUs (TB punctured PPDUs). A value of 0 in the RU Adaptation field may indicate support for sending and / or receiving PPDUs with adaptive RUs. In some embodiments, a value of 0 in the RU Adaptation field may indicate support for sending and / or receiving PPDUs with adaptive RUs. A value of 1 in the RU Adaptation field may indicate support for sending and / or receiving PPDUs with adaptive RUs.

[0276] The Receive Insertable PPDU Support field may be used to indicate whether the first device supports the receiver in the Insertable PPDU function. In some embodiments, a value of 1 in the Receive Insertable PPDU Support field may indicate that the first device supports receiving inserted PPDUs. A value of 0 in the Receive Insertable PPDU Support field may indicate that the first device does not support receiving inserted PPDUs. In some embodiments, a value of 0 in the Receive Insertable PPDU Support field may indicate that the first device supports receiving inserted PPDUs. A value of 1 in the Receive Insertable PPDU Support field may indicate that the first device does not support receiving inserted PPDUs.

[0277] The Send Insertable PPDU Support field may be used to indicate whether the first device supports the sender in the Insertable PPDU function. In some embodiments, a value of 1 in the Send Insertable PPDU Support field may indicate that the first device supports sending inserted PPDUs. A value of 0 in the Send Insertable PPDU Support field may indicate that the first device does not support sending inserted PPDUs. In some embodiments, a value of 0 in the Send Insertable PPDU Support field may indicate that the first device supports sending inserted PPDUs. A value of 1 in the Send Insertable PPDU Support field may indicate that the first device does not support sending inserted PPDUs.

[0278] The Auxiliary Link Above 45 GHz field can be used to indicate whether the first device supports transmission and reception in the frequency band above 45 GHz. In some embodiments, the value of 1 in the Auxiliary Link Above 45 GHz field can indicate that there is an auxiliary link in the frequency band above 45 GHz, that is, the first device supports reception and / or transmission in the frequency band above 45 GHz. The value of 0 in the Auxiliary Link Above 45 GHz field can indicate that there is no auxiliary link in the frequency band above 45 GHz, that is, the first device does not support reception and / or transmission in the frequency band above 45 GHz. In some embodiments, the value of 0 in the Auxiliary Link Above 45 GHz field can indicate that there is an auxiliary link in the frequency band above 45 GHz. The value of 1 in the Auxiliary Link Above 45 GHz field can indicate that there is no auxiliary link in the frequency band above 45 GHz.

[0279] The first capability element may be included in one or more of the following frames: a beacon frame, an association request frame, an association response frame, a reassociation request frame, a reassociation response frame, a probe request frame, or a probe response frame. In other words, the capability information indicated in the first capability element may be transmitted to the peer end through the capability discovery process described above.

[0280] As mentioned above, the target device may include a third device, that is, the first device may indicate capability information of other devices through the first indication information. In the case where the target device includes the third device, the first indication information may include a proximity report element and / or a simplified proximity report element.

[0281] In the case where the first indication information is included in a nearby report element, the third device may correspond to the AP indicated by the BSSID field in the element, ie, the AP reported by the element (hereinafter referred to as reported AP).

[0282] In some embodiments, the Nearby Report element can be used to indicate one or more of the following information about the third device: whether it supports the target protocol; whether it supports multi-AP coordination; whether it supports communication above the 45 GHz band; whether it supports secondary channel access; whether it supports distributed RU-based transmission; whether it is a mobile AP; and the power supply mode. The above information is described in detail above and will not be repeated here.

[0283] For example, the first device may be an AP, and the second device may be a non-AP STA. The AP may use a Nearby Report element to inform the non-AP STA of information about other nearby APs, thereby helping the non-AP STA understand its surrounding APs. Compared to related technologies, the Nearby Report element contains more comprehensive information about neighboring AP capabilities, thus enabling more accurate and efficient handover for the non-AP STA.

[0284] FIG8 is a schematic diagram of the format of a nearby report element provided in an embodiment of the present application.

[0285] As shown in Figure 8, the BSSID information field may include one or more of the following fields: ultra high reliability, multi-AP coordiantion, colocated with above 45GHz, secondary channel, mobile AP, power source, DRU, and reserved.

[0286] The Ultra High Reliability field can be used to indicate whether the reporting AP supports the target protocol (Figure 8 takes the target protocol as UHR as an example), that is, whether the AP is a UHR AP. In addition, the Ultra High Reliability field can indicate whether the UHR capability element (or UHR operation element) (if included as a sub-element in the report) is the same as the UHR capability element (or UHR operation element) included in the beacon frame transmitted by the reporting AP.

[0287] In some embodiments, the Ultra High Reliability field being set to 1 may indicate that the reporting AP supports UHR, and the UHR Capabilities element (or UHR Operations element), if included as a sub-element in the report, is identical to the contents of the UHR Capabilities element (or UHR Operations element) included in the beacon frames transmitted by the reporting AP. The Ultra High Reliability field being set to 0 may indicate that the reporting AP does not support UHR, or the UHR Capabilities element (or UHR Operations element), if included as a sub-element in the report, is identical to the contents of the UHR Capabilities element (or UHR Operations element) included in the beacon frames transmitted by the reporting AP. In some embodiments, the Ultra High Reliability field being set to 0 may indicate that the reporting AP supports UHR, and the UHR Capabilities element (or UHR Operations element), if included as a sub-element in the report, is identical to the contents of the UHR Capabilities element (or UHR Operations element) included in the beacon frames transmitted by the reporting AP. The Ultra High Reliability field set to 1 may indicate that the reporting AP does not support UHR, or that the UHR Capability element (or UHR Operation element) (if included as a sub-element in the report) is identical to the content of the UHR Capability element (or UHR Operation element) included by the reporting AP in the beacon frames it transmits.

[0288] The multi-AP coordination field can be used to indicate whether the reported AP supports multi-AP coordination. The multi-AP coordination field can also indicate whether the content of the multi-AP element (if included as a sub-element in the report) is the same as that of the multi-AP element included in the beacon frame transmitted by the reported AP.

[0289] In some embodiments, the multi-AP coordination field is set to 1 to indicate that the reported AP has multi-AP coordination capability, and the multi-AP element (if included in the report as a sub-element) is the same as the content of the multi-AP element contained in the beacon frame transmitted by the reported AP. The multi-AP coordination field is set to 0 to indicate that the reported AP does not have multi-AP coordination capability, or the multi-AP element (if included in the report as a sub-element) is the same as the content of the multi-AP element contained in the beacon frame transmitted by the reported AP. In some embodiments, the multi-AP coordination field is set to 0 to indicate that the reported AP has multi-AP coordination capability, and the multi-AP element (if included in the report as a sub-element) is the same as the content of the multi-AP element contained in the beacon frame transmitted by the reported AP. The multi-AP coordination field is set to 1 to indicate that the reported AP does not have multi-AP coordination capability, or the multi-AP element (if included in the report as a sub-element) is the same as the content of the multi-AP element contained in the beacon frame transmitted by the reported AP.

[0290] The Co-location 45 GHz and above field can be used to indicate whether the reported AP supports communications above 45 GHz. In other words, the Co-location 45 GHz and above field can be used to indicate whether the reported AP and the 45 GHz and above AP are located in the same co-location AP set.

[0291] In some embodiments, the Co-location Above 45 GHz field may be set to 1 to indicate that the reporting AP is in the same co-located AP set as the APs above 45 GHz. The Co-location Above 45 GHz field may be set to 0 to indicate that the reporting AP is not in the same co-located AP set as the APs above 45 GHz. In some embodiments, the Co-location Above 45 GHz field may be set to 0 to indicate that the reporting AP is in the same co-located AP set as the APs above 45 GHz. The Co-location Above 45 GHz field may be set to 1 to indicate that the reporting AP is not in the same co-located AP set as the APs above 45 GHz.

[0292] The Secondary Channel field may be used to indicate whether the reporting AP supports secondary channel access. Additionally, the Secondary Channel field may also indicate whether the Secondary Channel Operation element (if included as a sub-element in the report) is identical to the Secondary Channel Operation element included in the beacon frames transmitted by the reporting AP.

[0293] In some embodiments, the SecondaryChannel field being set to 1 may indicate that the reporting AP is capable of secondary channel access, and the SecondaryChannel Operation element (if included as a sub-element in the report) is the same as the content of the SecondaryChannel Operation element included in the beacon frames transmitted by the reporting AP. The SecondaryChannel field being set to 0 may indicate that the reporting AP is not capable of secondary channel access, or the SecondaryChannel Operation element (if included as a sub-element in the report) is different from the content of the SecondaryChannel Operation element included in the beacon frames transmitted by the reporting AP. In some embodiments, the SecondaryChannel field being set to 0 may indicate that the reporting AP is capable of secondary channel access, and the SecondaryChannel Operation element (if included as a sub-element in the report) is the same as the content of the SecondaryChannel Operation element included in the beacon frames transmitted by the reporting AP. The SecondaryChannel field being set to 1 may indicate that the reporting AP is not capable of secondary channel access, or the SecondaryChannel Operation element (if included as a sub-element in the report) is different from the content of the SecondaryChannel Operation element included in the beacon frames transmitted by the reporting AP.

[0294] The Mobile AP field can be used to indicate whether the reported AP is a mobile AP. In some embodiments, setting the Mobile AP field to 1 can indicate that the reported AP is a mobile AP. Setting the Mobile AP field to 0 can indicate that the reported AP is a non-mobile AP. In some embodiments, setting the Mobile AP field to 0 can indicate that the reported AP is a mobile AP. Setting the Mobile AP field to 1 can indicate that the reported AP is a non-mobile AP.

[0295] The Energy field can be used to indicate the power mode of the reporting AP. For example, the Energy field can indicate whether the reporting AP is powered solely by battery. In some implementations, setting the Energy field to 1 can indicate that the reporting AP is powered solely by battery. Setting the Energy field to 0 can indicate that the reporting AP is not powered solely by battery. In some implementations, setting the Energy field to 0 can indicate that the reporting AP is powered solely by battery. Setting the Energy field to 1 can indicate that the reporting AP is not powered solely by battery.

[0296] The DRU field may be used to indicate whether the reporting AP supports DRU-based transmission. In some embodiments, setting the DRU field to 1 may indicate that the reporting AP supports sending and / or receiving UHR PPDUs containing DRUs. Setting the DRU field to 0 may indicate that the reporting AP does not support sending and / or receiving UHR PPDUs containing DRUs. In some embodiments, setting the DRU field to 0 may indicate that the reporting AP supports sending and / or receiving UHR PPDUs containing DRUs. Setting the DRU field to 1 may indicate that the reporting AP does not support sending and / or receiving UHR PPDUs containing DRUs.

[0297] As shown in Figure 8, the Nearby Report element may also include other fields. The BSSID Information field may also include other fields. Other fields may have the same functions as those in the related art and will not be described in detail here.

[0298] In some embodiments, the proximity report element may be included in one or more of the following frames: a beacon frame, an association response frame, a reassociation response frame, an authentication frame.

[0299] When the first indication information is included in a simplified proximity report element, the first device may be an AP and the second device may be a non-AP STA. The AP may use the simplified proximity report element to inform the non-AP STA of information about beacon frames broadcast by other nearby APs (i.e., the target device), thereby helping the non-AP STA quickly scan for other APs.

[0300] In the case where the first indication information is included in a simplified nearby reporting element, the simplified nearby reporting element can be used to indicate whether the third device supports one or more of: broadcasting beacon frames on the secondary channel; receiving probe request frames on the secondary channel; and replying probe response frames on the secondary channel.

[0301] FIG9 is a schematic diagram of a simplified format of a nearby reporting element provided in an embodiment of the present application.

[0302] As shown in FIG9 , the simplified vicinity report element may include a secondary channel scan field.

[0303] The secondary channel scan field may be used to indicate whether the third device supports one or more of the following: broadcasting beacon frames on the secondary channel, receiving probe request frames on the secondary channel, and replying probe response frames on the secondary channel.

[0304] In some embodiments, the Secondary Channel Scan field is set to 1 to indicate that the reporting AP will broadcast beacon frames on the secondary channel, and / or the reporting AP will receive probe request frames and reply probe response frames on the secondary channel. The Secondary Channel Scan field is set to 0 to indicate that the reporting AP will not broadcast beacon frames on the secondary channel, and / or the reporting AP will not receive probe request frames and reply probe response frames on the secondary channel. In some embodiments, the Secondary Channel Scan field is set to 0 to indicate that the reporting AP will broadcast beacon frames on the secondary channel, and / or the reporting AP will receive probe request frames and reply probe response frames on the secondary channel. The Secondary Channel Scan field is set to 1 to indicate that the reporting AP will not broadcast beacon frames on the secondary channel, and / or the reporting AP will not receive probe request frames and reply probe response frames on the secondary channel.

[0305] The reduced proximity reporting element may be included in one or more of the following frames: a beacon frame, a probe response frame.

[0306] It should be noted that the names in the embodiments of the present application (including but not limited to field names, element names, frame names, etc.) are only examples. In other words, the names in the present application can be modified or replaced.

[0307] It should be noted that the location, existence, and length of the fields contained in the fields, elements, frames, etc. in the embodiments are all examples and are not limited in this application.

[0308] The method embodiments of the present application are described in detail above, and the device embodiments of the present application are described in detail below. It should be understood that the description of the method embodiments corresponds to the description of the device embodiments, so for parts not described in detail, reference can be made to the above method embodiments.

[0309] FIG10 is a schematic structural diagram of a communication device 1000 provided in an embodiment of the present application. The communication device 1000 may be a first device and may include a sending unit 1010.

[0310] The sending unit 1010 is used to send first indication information to the second device; wherein the first indication information is used to indicate capability information of the target device, the target device includes the first device and / or the third device, and the capability information includes one or more of the following information of the target device: capability of multi-AP coordination; capability of secondary channel access; capability of priority access channel; support for link adaptation function; support for relay function; capability based on DRU transmission; mobility capability; power supply mode; capability related to preemption; capability to support target protocol; enhanced roaming capability; support for TXOP sharing function based on non-triggered frames; energy saving capability; support for passive adjustment of A-MPDU length function; support for 320MHz frequency domain aggregated PPDU; support for RU adaptation function; support for repeated transmission function; capability based on insertable PPDU communication; communication capability in frequency bands above 45GHz.

[0311] In an optional embodiment, the sending unit 1010 may be a transceiver 1230. The communication device 1000 may further include a processor 1210 and a memory 1220, as specifically shown in FIG12 .

[0312] FIG11 is a schematic structural diagram of a communication device 1100 provided in an embodiment of the present application. The communication device 1100 may be a second device and may include a receiving unit 1110.

[0313] The receiving unit 1110 can be used to receive first indication information sent by the first device; wherein the first indication information is used to indicate capability information of the target device, the target device includes the first device and / or the third device, and the capability information includes one or more of the following information of the target device: capability of multi-AP coordination; capability of secondary channel access; capability of priority access channel; support for link adaptation function; support for relay function; capability based on DRU transmission; mobility capability; power supply mode; capability related to preemption; capability to support target protocol; enhanced roaming capability; support for TXOP sharing function based on non-triggered frames; energy saving capability; support for passive adjustment of A-MPDU length function; support for 320MHz frequency domain aggregated PPDU; support for RU adaptation function; support for repeated transmission function; capability based on insertable PPDU communication; communication capability in frequency bands above 45GHz.

[0314] In an optional embodiment, the receiving unit 1110 may be a transceiver 1230. The communication device 1100 may further include a processor 1210 and a memory 1220, as specifically shown in FIG12 .

[0315] Figure 12 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 12 indicate that the unit or module is optional. The device 1200 can be used to implement the method described in the above method embodiment. The device 1200 can be a chip or a communication device.

[0316] The device 1200 may include one or more processors 1210. The processor 1210 may support the device 1200 to implement the method described in the above method embodiment. The processor 1210 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 another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0317] The apparatus 1200 may further include one or more memories 1220. The memories 1220 store programs that can be executed by the processor 1210, causing the processor 1210 to perform the methods described in the above method embodiments. The memories 1220 may be independent of the processor 1210 or integrated into the processor 1210.

[0318] The apparatus 1200 may further include a transceiver 1230. The processor 1210 may communicate with other devices or chips via the transceiver 1230. For example, the processor 1210 may transmit and receive data with other devices or chips via the transceiver 1230.

[0319] The present invention also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present invention, and the program enables a computer to execute the method performed by the communication device in each embodiment of the present invention.

[0320] The present 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 the present application, and the program causes a computer to execute the method performed by the communication device in each embodiment of the present application.

[0321] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided in the embodiments of the present application, and the computer program enables a computer to execute the method executed by the communication device in each embodiment of the present application.

[0322] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

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

[0324] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

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

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

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

[0328] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0329] In the embodiments of this application, the term "include" can refer to direct inclusion or indirect inclusion. Alternatively, the term "include" in the embodiments of this application can be replaced with "indicates" or "is used to determine." For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B."

[0330] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

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

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

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

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

[0335] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part 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, the process or function described in the embodiment of the present application is generated in whole or in part. 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 computer-readable storage medium. 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 a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

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

Claims

1. A wireless communication method, characterized in that, Including: The first device sends first indication information to the second device; Wherein, the first indication information is used to indicate the capability information of a target device, the target device includes the first device and / or a third device, and the capability information includes one or more of the following information of the target device: the capability of multi-access point (AP) coordination; the capability of secondary channel access; the capability of preferential access to a channel; the support situation of link adaptation function; the support situation of relay function; the capability of transmission based on distributed resource unit (DRU); the mobility; the power supply mode; the capability related to preemption; the capability of supporting a target protocol; the capability of enhanced roaming; the support situation of transmission opportunity (TXOP) sharing function based on non-triggered frames; the energy saving capability; the support situation of the passive adjustment function of the length of aggregated media access control protocol data unit (A-MPDU); the support situation of 320MHz frequency-domain aggregated physical layer protocol data unit (PPDU); the support situation of resource unit (RU) adaptation function; the support situation of repeat transmission function; the capability of communication based on insertable PPDU; the communication capability in a frequency band above 45GHz.

2. The method according to claim 1, characterized in that, The capability of the secondary channel access includes one or more of the following capabilities of the target device: Whether it supports the secondary channel access function; The physical layer version of the supported secondary channel access function; The number of secondary channels supported for access; The information of the first secondary channel supported for access; The energy saving information used for performing secondary channel access; The time delay of switching channels; The recommended secondary channel to be used; The capability of sending or receiving PPDU on the secondary channel; Whether it can broadcast beacon frames on the secondary channel; Whether it can receive probe request frames on the secondary channel; Whether it can reply probe response frames on the secondary channel.

3. The method according to claim 2, characterized in that, The information of the first secondary channel includes one or more of the following information of the first secondary channel: Identifier; Bandwidth; Second indication information, used to indicate whether it is recommended to preferentially use the first secondary channel; Center frequency; The information of the punctured channels included.

4. The method according to claim 2 or 3, characterized in that, The physical layer version of the supported secondary channel access function is represented by a bitmap, and one or more bits in the bitmap correspond to one or more physical layer versions one by one.

5. The method according to any one of claims 2 - 4, characterized in that, The energy saving information includes one or more of the following information: The energy saving mode of the target device on the secondary channel; In the energy saving mode, the time window when the target device is in an active state.

6. The method according to any one of claims 2 - 5, characterized in that, The capability of the secondary channel access is included in the secondary channel operation element.

7. The method according to claim 6, characterized in that, The secondary channel operation element is included in one or more of the following frames: beacon frame, association request frame, association response frame, re-association request frame, re-association response frame, probe request frame, probe response frame.

8. The method according to any one of claims 1 - 7, characterized in that, When the target device includes the third device, the first indication information is included in the nearby report element and / or the reduced nearby report element.

9. The method according to claim 8, characterized in that, When the first indication information is included in the nearby report element, the nearby report element is used to indicate one or more of the following information of the third device: Whether it supports the target protocol; Whether it supports multi-AP coordination; Whether it supports communication in a frequency band above 45GHz; Whether it supports secondary channel access; Whether it supports transmission based on distributed RUs; Whether it is a movable AP; Power supply mode.

10. The method according to claim 8 or 9, characterized in that, The nearby report element is included in one or more of the following frames: beacon frame, association response frame, re-association response frame, authentication frame.

11. The method according to any one of claims 8 - 10, characterized in that, When the first indication information is included in the streamlined nearby report element, the streamlined nearby report element is used to indicate whether the third device supports one or more of the following: Broadcast a beacon frame on the secondary channel; Receive a probe request frame on the secondary channel; Reply to a probe response frame on the secondary channel.

12. The method according to any one of claims 8 - 11, characterized in that, The streamlined nearby report element is included in one or more of the following frames: beacon frame, probe response frame.

13. The method according to any one of claims 1 - 12, characterized in that, When the target device includes the first device, the first indication information is included in the first capability element.

14. The method according to claim 13, characterized in that, The first capability element is used to indicate whether the first device supports one or more of the following: Multi-AP coordination function; Secondary channel access function; Initiator in the preemption function; Responder in the preemption function; Priority channel access function; Link adaptation function; Relay function; Enhanced roaming function; TXOP sharing function based on non-triggered frames; AP energy saving function; A-MPDU length passive adjustment function; 320MHz frequency domain aggregated PPDU; Distributed RU; Enhanced distributed RU; RU adaptation function; Repeated transmission function; Receiver in the insertable PPDU function; Sender in the insertable PPDU function; Transceiving in the frequency band above 45GHz.

15. The method according to claim 13 or 14, characterized in that, The first capability element is included in one or more of the following frames: beacon frame, association request frame, association response frame, re-association request frame, re-association response frame, probe request frame, probe response frame.

16. The method according to any one of claims 1-15, characterized in that, The target protocol includes the ultra-high reliability UHR protocol.

17. The method according to any one of claims 1-16, characterized in that, The capability information is used to indicate the capabilities related to UHR technology.

18. A wireless communication method, characterized in that, Including: The second device receives the first indication information sent by the first device; Wherein, the first indication information is used to indicate the capability information of the target device, the target device includes the first device and / or the third device, and the capability information includes one or more of the following information of the target device: multi-access point AP coordination capability; secondary channel access capability; priority access channel capability; support for link adaptation function; support for relay function; capability for transmission based on distributed resource unit DRU; mobility; power supply mode; capability related to preemption; capability to support the target protocol; enhanced roaming capability; support for TXOP sharing function based on non-triggered frames; energy saving capability; support for A-MPDU length passive adjustment function of aggregated media access control protocol data unit; support for 320MHz frequency domain aggregated physical layer protocol data unit PPDU; support for RU adaptation function; support for repeated transmission function; capability for communication based on insertable PPDU; communication capability in the frequency band above 45GHz.

19. The method according to claim 18, characterized in that, The secondary channel access capability includes one or more of the following capabilities of the target device: Whether it supports the secondary channel access function; Physical layer version of the supported secondary channel access function; Number of supported secondary channels for access; Information of the first secondary channel supported for access; Energy-saving information used for performing secondary channel access; Delay of switching channels; Suggested secondary channels to be used; Capability of sending or receiving PPDU on secondary channels; Whether it is capable of broadcasting beacon frames on secondary channels; Whether it is capable of receiving probe request frames on secondary channels; Whether it is capable of replying probe response frames on secondary channels.

20. The method according to claim 19, characterized in that, The information of the first secondary channel includes one or more of the following information of the first secondary channel: Identifier; Bandwidth; Second indication information for indicating whether it is suggested to preferentially use the first secondary channel; Center frequency; Information of the punctured channels included.

21. The method according to claim 19 or 20, characterized in that, The physical layer version of the supported secondary channel access function is represented by a bitmap, and one or more bits in the bitmap correspond to one or more physical layer versions one by one.

22. The method according to any one of claims 19-21, characterized in that, The energy-saving information includes one or more of the following information: The energy-saving mode of the target device on the secondary channel; In the energy-saving mode, the time window when the target device is in the active state.

23. The method according to any one of claims 19-22, characterized in that, The capability of the secondary channel access is included in the secondary channel operation element.

24. The method according to claim 23, wherein The secondary channel operation element is included in one or more of the following frames: beacon frame, association request frame, association response frame, re-association request frame, re-association response frame, probe request frame, probe response frame.

25. The method according to any one of claims 18 - 24, wherein When the target device includes the third device, the first indication information is included in the nearby report element and / or the simplified nearby report element.

26. The method according to claim 25, wherein When the first indication information is included in the nearby report element, the nearby report element is used to indicate one or more of the following information of the third device: Whether it supports the target protocol; Whether it supports multi-AP coordination; Whether it supports communication above the 45GHz band; Whether it supports secondary channel access; Whether it supports transmission based on distributed RUs; Whether it is a movable AP; Power supply mode.

27. The method according to claim 25 or 26, wherein The nearby report element is included in one or more of the following frames: beacon frame, association response frame, re-association response frame, authentication frame.

28. The method according to any one of claims 25 - 27, wherein When the first indication information is included in the simplified nearby report element, the simplified nearby report element is used to indicate whether the third device supports one or more of the following: Broadcasting beacon frames on secondary channels; Receiving probe request frames on secondary channels; Replying probe response frames on secondary channels.

29. The method according to any one of claims 25 - 28, wherein The simplified nearby report element is included in one or more of the following frames: beacon frame, probe response frame.

30. The method according to any one of claims 18 - 29, wherein When the target device includes the first device, the first indication information is included in the first capability element.

31. The method according to claim 30, wherein The first capability element is used to indicate whether the first device supports one or more of the following: Multi-AP coordination function; Secondary channel access function; Initiator in the preemption function; Responder in the preemption function; Priority channel access function; Link adaptation function; Relay function; Enhanced roaming function; TXOP sharing function based on non-triggered frames; AP energy-saving function; A-MPDU length passive adjustment function; 320MHz frequency-domain aggregated PPDU; Distributed RU; Enhanced distributed RU; RU adaptation function; Repeat transmission function; Receiver in the insertable PPDU function; Sender in the insertable PPDU function; Transceiving in the frequency band above 45 GHz.

32. The method according to claim 30 or 31, characterized in that, The first capability element is included in one or more of the following frames: beacon frame, association request frame, association response frame, re-association request frame, re-association response frame, probe request frame, probe response frame.

33. The method according to any one of claims 18 - 32, characterized in that, The target protocol includes the UHR protocol.

34. The method according to any one of claims 18 - 33, characterized in that, The capability information is used to indicate the capabilities related to UHR technology.

35. A communication device, characterized in that, The communication device is the first device, and the communication device includes: A sending unit, configured to send first indication information to a second device; Wherein, the first indication information is used to indicate the capability information of a target device, the target device includes the first device and / or a third device, and the capability information includes one or more of the following information of the target device: the capability of multi-access point AP coordination; the capability of secondary channel access; the capability of preferential access to a channel; the support for link adaptation function; the support for relay function; the capability of transmission based on distributed resource unit DRU; the mobility; the power supply mode; the capability related to preemption; the capability of supporting the target protocol; the capability of enhanced roaming; the support for the transmission opportunity TXOP sharing function based on non-triggered frames; the energy saving capability; the support for the passive adjustment function of the length of the aggregated media access control protocol data unit A-MPDU; the support for the 320 MHz frequency-domain aggregated physical layer protocol data unit PPDU; the resource unit RU adaptation function; the retransmission function; the capability of communication based on insertable PPDU; the communication capability in the frequency band above 45 GHz.

36. The communication device according to claim 35, characterized in that, The capability of secondary channel access includes one or more of the following capabilities of the target device: Whether to support the secondary channel access function; The physical layer version of the supported secondary channel access function; The number of secondary channels supported for access; The information of the first secondary channel supported for access; The energy saving information used for performing secondary channel access; The delay of switching channels; The recommended secondary channel to use; The capability of sending or receiving a PPDU on the secondary channel; Whether it is possible to broadcast a beacon frame on the secondary channel; Whether it is possible to receive a probe request frame on the secondary channel; Whether it is possible to reply to a probe response frame on the secondary channel.

37. The communication device according to claim 36, characterized in that, The information of the first secondary channel includes one or more of the following information of the first secondary channel: Identifier; Bandwidth; Second indication information, used to indicate whether it is recommended to preferentially use the first secondary channel; Center frequency; The information of the punctured channels included.

38. The communication device according to claim 36 or 37, characterized in that, The physical layer version of the supported secondary channel access function is represented by a bitmap, and one or more bits in the bitmap correspond to one or more physical layer versions one by one.

39. The communication device according to any one of claims 36 - 37, characterized in that, The energy saving information includes one or more of the following information: The energy saving mode of the target device on the secondary channel; In the energy saving mode, the time window during which the target device is in an active state.

40. The communication device according to any one of claims 36 - 39, characterized in that, The capability of secondary channel access is included in the secondary channel operation element.

41. The communication device according to claim 40, characterized in that, The secondary channel operation element is included in one or more of the following frames: beacon frame, association request frame, association response frame, re-association request frame, re-association response frame, probe request frame, probe response frame.

42. The communication device according to any one of claims 35 - 41, characterized in that, When the target device includes the third device, the first indication information is included in the nearby report element and / or the reduced nearby report element.

43. The communication device according to claim 42, characterized in that, When the first indication information is included in the nearby report element, the nearby report element is used to indicate one or more of the following information of the third device: Whether it supports the target protocol; Whether it supports multi-AP coordination; Whether it supports communication above the 45 GHz band; Whether it supports secondary channel access; Whether it supports transmission based on distributed RUs; Whether it is a movable AP; Power supply mode.

44. The communication device according to claim 42 or 43, characterized in that, The nearby report element is included in one or more of the following frames: beacon frame, association response frame, re-association response frame, authentication frame.

45. The communication device according to any one of claims 42 - 44, characterized in that, When the first indication information is included in the reduced nearby report element, the reduced nearby report element is used to indicate one or more of whether the third device supports: Broadcasting a beacon frame on the secondary channel; Receiving a probe request frame on the secondary channel; Replying a probe response frame on the secondary channel.

46. The communication device according to any one of claims 42 - 45, characterized in that, The reduced nearby report element is included in one or more of the following frames: beacon frame, probe response frame.

47. The communication device according to any one of claims 35 - 46, characterized in that, When the target device includes the first device, the first indication information is included in the first capability element.

48. The communication device according to claim 47, characterized in that, The first capability element is used to indicate whether the first device supports one or more of the following: Multi-AP coordination function; Secondary channel access function; The initiator in the preemption function; The responder in the preemption function; Priority channel access function; Link adaptation function; Relay function; Enhanced roaming function; TXOP sharing function based on non-triggered frames; AP energy saving function; A-MPDU length passive adjustment function; 320 MHz frequency domain aggregated PPDU; Distributed RU; Enhanced distributed RU; RU adaptation function; Repeated transmission function; The receiver in the insertable PPDU function; The sender in the insertable PPDU function; Transceiving above the 45 GHz band.

49. The communication device according to claim 47 or 48, characterized in that, The first capability element is included in one or more of the following frames: beacon frame, association request frame, association response frame, re-association request frame, re-association response frame, probe request frame, probe response frame.

50. The communication device according to any one of claims 35 - 49, characterized in that, The target protocol includes the ultra-high reliability UHR protocol.

51. The communication device according to any one of claims 35 - 50, characterized in that, The capability information is used to indicate the capabilities related to UHR technology.

52. A communication device, characterized in that, The communication device is the second device, and the communication device includes: A receiving unit, configured to receive the first indication information sent by the first device; Among them, the first indication information is used to indicate the capability information of the target device, where the target device includes the first device and / or the third device, and the capability information includes one or more of the following information of the target device: the capability of multi-access point (AP) coordination; the capability of secondary channel access; the capability of preferential access to channels; the support condition of link adaptation function; the support condition of relay function; the capability of transmission based on distributed resource unit (DRU); the mobility; the power supply mode; the capability related to preemption; the capability of supporting the target protocol; the capability of enhanced roaming; the support condition of transmission opportunity (TXOP) sharing function based on non-triggered frames; the energy saving capability; the support condition of the passive adjustment function of the length of aggregated media access control protocol data unit (A-MPDU); the support condition of 320 MHz frequency domain aggregated physical layer protocol data unit (PPDU); the support condition of resource unit (RU) adaptation function; the support condition of retransmission function; the capability of communication based on insertable PPDU; the communication capability in the frequency band above 45 GHz.

53. The communication device according to claim 52, characterized in that, The capability of secondary channel access includes one or more of the following capabilities of the target device: Whether it supports the secondary channel access function; The physical layer version of the supported secondary channel access function; The number of secondary channels supported for access; The information of the first secondary channel supported for access; The energy saving information used for performing secondary channel access; The time delay of switching channels; The recommended secondary channels to be used; The capability of sending or receiving PPDU on the secondary channel; Whether it can broadcast beacon frames on the secondary channel; Whether it can receive probe request frames on the secondary channel; Whether it can reply to probe response frames on the secondary channel.

54. The communication device according to claim 53, characterized in that,The information of the first secondary channel includes one or more of the following information of the first secondary channel: Identifier; Bandwidth; The second indication information, used to indicate whether it is recommended to preferentially use the first secondary channel; Center frequency; The information of the punctured channels included.

55. The communication device according to claim 53 or 54, characterized in that, The physical layer version of the supported secondary channel access function is represented by a bitmap, and one or more bits in the bitmap correspond to one or more physical layer versions one by one.

56. The communication device according to any one of claims 53-55, characterized in that, The energy saving information includes one or more of the following information: The energy saving mode of the target device on the secondary channel; In the energy saving mode, the time window when the target device is in the active state.

57. The communication device according to any one of claims 53-56, characterized in that, The capability of secondary channel access is included in the secondary channel operation element.

58. The communication device according to claim 57, characterized in that, The secondary channel operation element is included in one or more of the following frames: beacon frame, association request frame, association response frame, re-association request frame, re-association response frame, probe request frame, probe response frame.

59. The communication device according to any one of claims 52-58, characterized in that, In the case where the target device includes the third device, the first indication information is included in the nearby report element and / or the simplified nearby report element.

60. The communication device according to claim 59, characterized in that, In the case where the first indication information is included in the nearby report element, the nearby report element is used to indicate one or more of the following information of the third device: Whether it supports the target protocol; Whether it supports multi-AP coordination; Whether it supports communication in the frequency band above 45 GHz; Whether it supports secondary channel access; Whether it supports transmission based on distributed RU; Whether it is a movable AP; Power supply mode.

61. The communication device according to claim 59 or 60, characterized in that, The nearby reporting element is included in one or more of the following frames: beacon frame, association response frame, reassociation response frame, authentication frame.

62. The communication device according to any one of claims 59-61, characterized in that, In the case where the first indication information is included in the streamlined nearby reporting element, the streamlined nearby reporting element is used to indicate whether the third device supports one or more of the following: Broadcasting a beacon frame on a secondary channel; Receiving a probe request frame on a secondary channel; Responding to a probe response frame on a secondary channel.

63. The communication device according to any one of claims 59-62, characterized in that, The streamlined nearby reporting element is included in one or more of the following frames: beacon frame, probe response frame.

64. The communication device according to any one of claims 52-63, characterized in that,In the case where the target device includes the first device, the first indication information is included in the first capability element.

65. The communication device according to claim 64, wherein, The first capability element is used to indicate whether the first device supports one or more of the following: Multi-AP coordination function; Secondary channel access function; Initiator in the preemption function; Responder in the preemption function; Priority channel access function; Link adaptation function; Relay function; Enhanced roaming function; TXOP sharing function based on non-triggered frames; AP power saving function; A-MPDU length passive adjustment function; 320MHz frequency domain aggregated PPDU; Distributed RU; Enhanced distributed RU; RU adaptation function; Repeat transmission function; Receiver in the insertable PPDU function; Sender in the insertable PPDU function; Transceiving in the frequency band above 45GHz.

66. The communication device according to claim 64 or 65, wherein, The first capability element is included in one or more of the following frames: beacon frame, association request frame, association response frame, reassociation request frame, reassociation response frame, probe request frame, probe response frame.

67. The communication device according to any one of claims 52 - 66, wherein, The target protocol includes the UHR protocol.

68. The communication device according to any one of claims 52 - 67, wherein, The capability information is used to indicate the capabilities related to UHR technology.

69. A communication device, wherein, Including a memory and a processor, the memory is used to store programs, and the processor is used to call the programs in the memory so that the communication device executes the method according to any one of claims 18-30.

70. A device, wherein, Including a processor, used to call a program from a memory so that the device executes the method according to any one of claims 1-34.

71. A chip, wherein, Including a processor, used to call a program from a memory so that the device installed with the chip executes the method according to any one of claims 1-34.

72. A computer-readable storage medium, wherein, Having a program stored thereon, the program causes a computer to execute the method according to any one of claims 1-34.

73. A computer program product, wherein, Including a program, the program causes a computer to execute the method according to any one of claims 1-34.

74. A computer program, wherein, The computer program causes a computer to execute the method according to any one of claims 1-34.

Images