Communication apparatus and communication method for enhanced client discovery
By introducing communication methods that enhance client discovery in wireless networks, non-AP STA or non-AP MLD can obtain potential link information from AP or AP MLD, solving the problem of waste of link discovery resources in the prior art and achieving more Efficient link discovery and measurement requests.
Patent Information
- Application Number
- CN202380036690.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-05-18
- Filing Date
- 2023-03-06
- Publication Date
- 2024-12-06
AI Technical Summary
In a multi-AP Wi-Fi environment, the existing technology has huge overhead when clients discover information about potential links, especially when blindly measuring and reporting all possible links during the SBP reporting stage, resulting in waste of resources and SBP initiators Limited knowledge of potential links.
By introducing communication methods and devices that enhance client discovery in a wireless network, non-AP STA or non-AP MLD can obtain information about potential links from AP or AP MLD, and request relevant information by generating and sending request frames to achieve more Fine link discovery and reporting.
It effectively reduces resource waste in wireless networks, improves the accuracy and efficiency of link discovery, enables non-AP STAs or non-AP MLDs to perform sensing measurement requests more appropriately, and reduces the overhead of wireless links.
Smart Images

Figure CN119096600A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a communication device and method for client discovery, and more particularly to a communication device and method for enhancing client discovery. Background Art
[0002] Wireless local area network (WLAN) sensing is being developed by the Institute of Electrical and Electronics Engineers (IEEE) 802.11bf task group. In the task group, sensing by proxy (SBP) is proposed, which enables a client to obtain sensing measurements using multiple radio links, but the details of the protocol / procedure for obtaining information of one or more non-access point (non-AP) stations (STAs) have not yet been discussed. At the same time, the IEEE 802.11be task group is developing the multi-link operation (MLO) / multi-link device (MLD) specification, in which multiple stations can be attached to the MLD.
[0003] Although whole house / office Wi-Fi coverage with multiple APs is very common nowadays, blindly measuring and reporting all possible links during the SBP reporting phase will result in a huge overhead of Wi-Fi links for reporting. In addition, for example, in the case of links between an AP (or AP MLD) and other non-AP STAs (other non-AP MLDs) and links between a STA associated with an AP (or non-AP MLD associated with an AP MLD) and other STAs / APs, the SBP initiator may be limited to not knowing the potential links for sensing measurements. Such a problem can be summarized as the client discovery problem.
[0004] Therefore, there is a need for a communication device and method for enhancing client discovery, which provides a feasible technical solution to solve these problems, and more specifically, enables a non-AP STA (or non-AP MLD) to obtain information about potential links from an AP (or AP MLD). For example, the non-AP MLD (or non-AP MLD) is an SBP initiator that needs to obtain information about potential links from the AP (or AP MLD) in order to make appropriate requests for the SBP procedure.
[0005] Furthermore, other desirable features and characteristics will become apparent from the subsequent detailed description and the appended claims, taken in conjunction with the accompanying drawings and this background of the disclosure. Summary of the invention
[0006] Non-limiting and exemplary embodiments facilitate providing a communication apparatus and a communication method for enhanced client discovery in a wireless network.
[0007] In a first aspect, the present disclosure provides a first communication device, comprising: a circuit, generating a first frame; and a transmitter, sending the first frame to a second communication device to request information of a third communication device.
[0008] In a second aspect, the present disclosure provides a second communication device, comprising: a receiver, receiving a request frame requesting information of a third communication device from a first communication device; a circuit, processing the request frame and generating a response frame including the information; and a transmitter, sending the response frame to the first communication device.
[0009] In a third aspect, the present disclosure provides a communication method implemented by a first communication device, comprising: generating a first frame; and sending the first frame to a second communication device to request information of a third communication device.
[0010] In a fourth aspect, the present disclosure provides a communication method implemented by a second communication device, comprising: receiving a request frame requesting information of a third communication device from a first communication device; processing the request frame; generating a response frame including the information; and sending the response frame to the first communication device.
[0011] It should be noted that the general or specific embodiments may be implemented as a system, a method, an integrated circuit, a computer program, a storage medium, or any selective combination thereof.
[0012] Additional benefits and advantages of the disclosed embodiments will become apparent from the description and drawings. Benefits and / or advantages may be obtained individually from the various embodiments and features of the description and drawings, and these embodiments and features do not need to be provided in full in order to obtain one or more such benefits and / or advantages. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Through the following written description, which is taken as an example only and in conjunction with the accompanying drawings, one of ordinary skill in the art will better understand the embodiments of the present disclosure, and the embodiments of the present disclosure will be apparent to one of ordinary skill in the art, in which:
[0014] Figure 1 Depicted is a schematic diagram illustrating single user (SU) communication between an access point (AP) and a station (STA) in a MIMO (Multiple Input Multiple Output) wireless network.
[0015] Figure 2 Depicted is a schematic diagram illustrating downlink multi-user (MU) communications between an AP and multiple STAs in a MIMO wireless network.
[0016] Figure 3 Depicted is a schematic diagram illustrating trigger-based (TB) uplink MU communication between an AP and multiple STAs in a MIMO wireless network.
[0017] Figure 4 Depicted is a schematic diagram illustrating the communication between a STA (Client 0) and an AP for a basic SBP procedure.
[0018] Figure 5 Depicted is a schematic diagram illustrating three wireless links between an AP MLD and a non-AP MLD.
[0019] Fig. 6A Shows the format of the Neighbor Report element.
[0020] Figure 6B The format of a simplified neighbor report element is shown.
[0021] Figure 6C Shows Figure 6B The format of the neighbor AP information field in .
[0022] Figure 7 A schematic diagram showing a floor plan and the equipment located therein is shown.
[0023] Figure 8 A schematic diagram of a communication device according to the present disclosure is depicted.
[0024] Fig. 9 A flow chart illustrating a communication method implemented by a first communication device according to various embodiments of the present disclosure is shown.
[0025] Fig.10 A flow chart illustrating a communication method implemented by a second communication device, such as an SBP responder, according to various embodiments of the present disclosure is shown.
[0026] Fig.11 A flow chart illustrating example level 1 and level 2 enhanced client discovery procedures between a non-AP STA and an AP is shown.
[0027] Fig.12 A flow chart illustrating an example level 1 and level 2 enhanced client discovery procedure between a non-AP MLD and an AP MLD is shown.
[0028] Fig.13 Depicted is a flowchart illustrating an enhanced client discovery procedure between an AP and a non-AP STA according to a first embodiment of the present disclosure.
[0029] Fig.14 Depicted is a flowchart illustrating an enhanced client discovery procedure between an AP MLD and a non-AP MLD according to a first embodiment of the present disclosure.
[0030] Fig.15 Example visualizations of level 1 and level 2 enhanced client discovery results are shown.
[0031] Fig.16 An example format of a Multi-Link Element (MLE) for basic discovery according to an embodiment of the present disclosure is shown.
[0032] Fig.17 An example format of a multi-link load element used by an AP MLD for basic discovery according to an embodiment of the present disclosure is shown.
[0033] Fig.18 An example format of a protected client discovery query frame for a level 1 client discovery query according to an embodiment of the present disclosure is shown.
[0034] Fig.19 An example format of a protected authorization verification request frame according to an embodiment of the present disclosure is shown.
[0035] Fig. 20 An example format of a protected authorization verification response frame according to an embodiment of the present disclosure is shown.
[0036] Fig.21 An example format of a level 1 client discovery response frame according to an embodiment of the present disclosure is shown.
[0037] Fig. 22 Another example format of a level 1 client discovery response frame according to an embodiment of the present disclosure is shown.
[0038] Fig.23 Shows Fig. 22 An example format of the MLD information element field of a protected client discovery response frame is depicted in FIG.
[0039] Fig.24 An example format of a protected client discovery query frame for a level 2 client discovery query according to an embodiment of the present disclosure is shown.
[0040] Fig.25 An example format of a Level 2 Client Discovery Response frame according to an embodiment of the present disclosure is shown.
[0041] Fig.26 Another example format of a level 2 client discovery response frame according to an embodiment of the present disclosure is shown.
[0042] Fig. 27 Shows Fig.26 An example format of the MLD information element field of a protected client discovery response frame is depicted in FIG.
[0043] Fig.28 A flow chart illustrating a level 3 client discovery procedure triggered by an AP according to an embodiment of the present disclosure is shown.
[0044] Fig.29 A flow chart illustrating a level 3 client discovery procedure triggered by AP MLD according to an embodiment of the present disclosure is shown.
[0045] Fig.30 A schematic diagram illustrating a multi-AP network deployment according to an embodiment of the present disclosure is shown.
[0046] Fig.31 A schematic diagram illustrating a tunneled enhanced client discovery procedure according to a third embodiment of the present disclosure is shown.
[0047] Fig.32 A flowchart illustrating a tunnel-enhanced client discovery procedure between non-AP STA1 and non-AP STA2 according to the third embodiment of the present disclosure is shown.
[0048] Fig.33A An example format of an enhanced client discovery Ethertype 89-0d data frame according to the third embodiment of the present disclosure is shown.
[0049] Fig.33B It shows that according to the embodiment Fig.33A Example contents of the payload field described in .
[0050] Fig.34 An example configuration of a communication device is shown.
[0051] Fig.35 Another example configuration of a communication device is shown.
[0052] Those skilled in the art will appreciate that the elements in the drawings are shown for simplicity and clarity and are not necessarily drawn to scale. For example, the size of some elements in the diagrams, block diagrams or flow charts may be exaggerated relative to other elements to help accurately understand the present embodiment. DETAILED DESCRIPTION
[0053] Some embodiments of the present disclosure will be described by way of example only with reference to the accompanying drawings. Like reference numerals and characters in the drawings represent like elements or equivalents.
[0054] In the following paragraphs, certain exemplary embodiments are explained with reference to access points (APs) and stations (STAs) for enhanced client discovery, particularly in multiple-input multiple-output (MIMO) wireless networks.
[0055] In the context of IEEE 802.11 (Wi-Fi) technology, a station, interchangeably referred to as a STA, is a communication device capable of using the 802.11 protocol. Based on the IEEE 802.11-2016 definition, a STA can be any device that includes an IEEE 802.11-compliant medium access control (MAC) and physical layer (PHY) interface to a wireless medium (WM).
[0056] For example, a STA can be a laptop, desktop personal computer (PC), personal digital assistant (PDA), access point, or Wi-Fi phone in a wireless local area network (WLAN) environment. A STA can be fixed or mobile. In a WLAN environment, the terms "STA", "wireless client", "user", "user equipment", and "node" are often used interchangeably.
[0057] Likewise, an AP (which may be interchangeably referred to as a wireless access point (AP) in the context of IEEE 802.11 (Wi-Fi) technology) is a communication device that allows STAs in a WLAN to connect to a wired network. An AP is typically connected to a router (via a wired network) as a standalone device, but it may also be integrated with or used in a router.
[0058] As described above, a STA in a WLAN can be used as an AP at different times, and vice versa. This is because a communication device in the context of IEEE 802.11 (Wi-Fi) technology can include both STA hardware components and AP hardware components. In this way, the communication device can switch between STA mode and AP mode based on actual WLAN conditions and / or requirements.
[0059] In a MIMO wireless network, "multi" refers to multiple antennas used for transmission and multiple antennas used for reception simultaneously on a radio channel. In this regard, "multiple inputs" refers to multiple transmitter antennas that input radio signals into a channel, and "multiple outputs" refers to multiple receiver antennas that receive radio signals from a channel and enter a receiver. For example, in an N×M MIMO network system, N is the number of transmitter antennas, M is the number of receiver antennas, and N may or may not be equal to M. For simplicity, the respective numbers of transmitter antennas and receiver antennas are not further discussed in this disclosure.
[0060] In a MIMO wireless network, single-user (SU) communication and multi-user (MU) communication may be deployed for communication between communication devices such as APs and STAs. MIMO wireless networks have benefits such as spatial multiplexing and spatial diversity, which achieve higher data rates and robustness by using multiple spatial streams. According to various embodiments, the term "spatial stream" may be used interchangeably with the term "space-time stream" (or STS).
[0061] Figure 1A schematic diagram illustrating SU communication 100 between an AP 102 and a STA 104 in a MIMO wireless network is depicted. As shown, the MIMO wireless network may include one or more STAs (e.g., STA 104, STA 106, etc.). If the SU communication 100 in a channel is performed over the entire channel bandwidth, it is referred to as full-bandwidth SU communication. If the SU communication 100 in a channel is performed over a portion of the channel bandwidth (e.g., one or more 20 MHz sub-channels within the channel are punctured), it is referred to as punctured SU communication. In the SU communication 100, the AP 102 uses multiple antennas (e.g., Figure 1 ) to transmit multiple space-time streams, where all space-time streams are directed to a single communication device (ie, STA 104). For simplicity, multiple space-time streams directed to STA 104 are shown as packet data transmission arrows 108 directed to STA 104.
[0062] SU communication 100 may be configured for bidirectional transmission. Figure 1 As shown in FIG. 1 , in SU communication 100, STA 104 may use multiple antennas (e.g., Figure 1 102) to transmit multiple space-time streams, where all space-time streams are directed to AP 102. For simplicity, the multiple space-time streams directed to AP 102 are shown as packet data transmission arrows 110 directed to AP 102.
[0063] therefore, Figure 1 The SU communication 100 depicted in FIG. 1 implements both uplink SU transmissions and downlink SU transmissions in a MIMO wireless network.
[0064] Figure 2A schematic diagram illustrating downlink MU (multi-user) communication 200 between an AP 202 and multiple STAs 204, 206, 208 in a MIMO wireless network is depicted. The MIMO wireless network may include one or more STAs (e.g., STA 204, STA 206, STA 208, etc.). The MU communication 200 may be an OFDMA (orthogonal frequency division multiple access) communication or a MU-MIMO communication. For OFDMA communication in a channel, the AP 202 simultaneously transmits multiple streams to the STAs 204, 206, 208 in the network at different resource units (RUs) within the channel bandwidth. For MU-MIMO communication in a channel, the AP 202 simultaneously transmits multiple streams to the STAs 204, 206, 208 at the same RU within the channel bandwidth using multiple antennas via spatial mapping or precoding techniques. If the RUs where the OFDMA or MU-MIMO communication occurs occupy the entire channel bandwidth, the OFDMA or MU-MIMO communication is referred to as full-bandwidth OFDMA or MU-MIMO communication. If the RU in which OFDMA or MU-MIMO communication occurs occupies a portion of the channel bandwidth (e.g., one or more 20MHz subchannels within the channel are punctured), then OFDMA or MU-MIMO communication is referred to as punctured OFDMA or MU-MIMO communication. For example, two space-time streams may be directed to STA 206, another space-time stream may be directed to STA 204, and yet another space-time stream may be directed to STA 208. For simplicity, the two space-time streams directed to STA 206 are shown as packet data transmission arrows 212, the space-time stream directed to STA 204 is shown as data transmission arrows 210, and the space-time stream directed to STA 208 is shown as data transmission arrows 214.
[0065] To achieve uplink MU transmission, trigger-based communication is provided to the MIMO wireless network. In this regard, Figure 3 A schematic diagram illustrating trigger-based (TB) uplink MU communication 300 between an AP 302 and a plurality of STAs 304, 306, 308 in a MIMO wireless network is depicted.
[0066] Since there are multiple STAs 304 , 306 , 308 that respectively participate in the triggered uplink MU communication, the AP 302 needs to coordinate simultaneous transmissions of the multiple STAs 304 , 306 , 308 .
[0067] For this reason, Figure 3As shown in FIG, AP 302 simultaneously sends trigger frames 310, 314, 318 to STAs 304, 306, 308, respectively, to indicate user-specific resource allocation information (e.g., the number of space-time streams, the starting STS number, and the allocated RUs) that each STA can use. In response to the trigger frames, STAs 304, 306, 308 can then simultaneously send their respective space-time streams to AP 302 according to the user-specific resource allocation information indicated in the trigger frames 310, 314, 318. For example, two space-time streams can be directed from STA 306 to AP 302, another space-time stream can be directed from STA 304 to AP 302, and yet another space-time stream can be directed from STA 308 to AP 302. For simplicity, two space-time streams directed from STA 306 to AP 302 are shown as packet data transmission arrows 316, the space-time stream directed from STA 304 to AP 302 is shown as data transmission arrow 312, and the space-time stream directed from STA 308 to AP 302 is shown as data transmission arrow 320.
[0068] Due to the packet / PPDU (physical layer protocol data unit) based transmission and distributed MAC (medium access control) scheme in 802.11 WLAN, there is no time scheduling (e.g., TDMA-like (time division multiple access) periodic time slot allocation for data transmission) in 802.11 WLAN. Frequency and space resource scheduling is performed on a packet basis. In other words, resource allocation information is based on PPDU.
[0069] According to various embodiments, WLAN supports Figure 1 The non-trigger based communication shown and Figure 2 In non-trigger-based communication, a communication device sends a PPDU to one or more other communication devices in an unsolicited manner. In trigger-based communication, a communication device sends a PPDU to one or more other communication devices only after receiving a solicitation trigger frame.
[0070] According to the present disclosure, the term "sensing initiator" refers to a device that initiates a sensing session with a STA (referred to herein as a "client") and requests sensing results from the STA. The term "sensing responder" is a STA that responds to the sensing initiator and participates in the sensing session. In the various embodiments below, unless otherwise specified, the terms "initiator" and "responder" refer to "sensing initiator" and "sensing responder", respectively. Typically (for example, in trigger-based (TB) sensing measurements), the initiator is the AP and the responder is a non-AP STA; however, this need not always be the case, and sometimes a non-AP STA may also be an initiator, and an AP may be a responder (for example, in non-TB sensing measurements or fine timing measurements (FTM) / ranging).
[0071] Compared to "sensing initiator" and "sensing responder", the term "sensing by proxy (SBP) initiator" refers to a STA that initiates the SBP procedure and requests a device (e.g., an AP or a sensing initiator) as a proxy to initiate a sensing session and request sensing results from another STA (e.g., a client of the device) on its behalf. The term "SBP responder" refers to a device that responds to the SBP initiator and agrees to participate in the SBP procedure to become a proxy sensing initiator. Note that the SBP initiator can be a sensing responder or one of multiple sensing responders of an SBP responder (sensing initiator).
[0072] As mentioned previously, SBP was introduced in IEEE 802.11bf, which enables a client to obtain sensing measurements using multiple radio links. Figure 4 A schematic diagram 400 is depicted illustrating the communication between a STA (Client 0) and an AP for a basic SBP procedure. According to the basic concept, the sensing procedure through the proxy includes SBP procedure establishment, sensing measurements, SBP procedure reporting, and SBP procedure termination. During the SBP procedure establishment, the client (e.g., Client 0) requests the AP to obtain sensing measurements. The AP acts as a proxy initiator for the requesting client. In the various embodiments shown in the present disclosure, such a requesting client is referred to as an SBP requesting STA or an SBP initiator, and the AP is referred to as a proxy AP or an SBP responder. The proxy is established by exchanging SBP request / response frames 412 between the SBP initiator and the SBP responder. The AP then performs sensing measurements with one or more clients (e.g., Clients 1 and 2), for example, by exchanging measurement setup request / response frames to establish a session and / or measurement report frames 414a, 414b during (one or more) measurement instances. In Figure 4In the example of , the SBP initiator is one of the clients, and the AP may also perform sensing measurements with the SBP initiator by exchanging related frames 414c. During the SBP procedure report, the AP that obtains the measurement reports of the clients then reports them to the SBP initiator, for example, by sending an SBP report frame 414. After the SBP procedure report, the SBP procedure may be terminated at any time by the SBP initiator or the SBP responder by sending an SBP terminate frame (not shown).
[0073] In addition, 802.11be has introduced the concept of multi-link device (MLD), where multiple stations can be attached to an MLD, allowing seamless communication between two MLDs over multiple wireless links. Figure 5 A schematic diagram 500 illustrating three wireless links between an AP MLD and a non-AP MLD is depicted. Specifically, three APs (AP1, AP2, AP3) operating at 2.4 GHz, 5 GHz, and 6 GHz frequencies, respectively, are attached to the AP MLD, and three non-AP STAs (non-AP STA1, non-AP STA2, non-AP STA3) operating at 2.4 GHz, 5 GHz, and 6 GHz frequencies, respectively, are attached to the non-AP MLD. AP1 and non-AP STA1 operating at 2.4 GHz communicate with each other through link 1; AP2 and non-AP STA2 operating at 5 GHz communicate with each other through link 2; and AP3 and non-AP STA3 operating at 6 GHz communicate with each other through link 3.
[0074] In addition, according to 802.11be_D1.5, EHT APs should set dot11MultiLinkActivated to true and should be affiliated with AP MLD, and EHT APs and their affiliated AP MLDs follow the rules defined in 35.3 (Multi-link Operation). This means that all EHT APs are affiliated with AP MLD, and there are no standalone EHT APs. In other words, in the context of EHT WLAN, MLD will participate in SBP (e.g., as SBP initiator or SBP responder). However, there is no relevant discussion about this in 11bf.
[0075] Regarding obtaining AP information, in addition to announcing its own information, IEEE 802.11 also provides a container (e.g., a signal frame) for AP to announce its neighbor AP information. For example, AP can include a neighbor report element or a simplified neighbor report element in its beacon, probe response frame, etc. to announce its neighbor AP information. Fig. 6AThe format of a neighbor report element 600 is shown. The neighbor report element includes an element identifier (ID) field, a length field, a basic service set ID (BSSID) information field, an operating class (Operating Class) field, a channel number field, a PHY type field, and optional sub-elements, which consist of 1, 1, 6, 5, 1, 1, 1, and a variable number of octets, respectively.
[0076] Figure 6B The format of a simplified neighbor report element 610 is shown. The simplified neighbor report element 610 includes an element ID field, a length field, and a neighbor AP information field 620, consisting of 1, 1, and a variable number of octets, respectively. Figure 6C Shows Figure 6B The format of the neighbor AP information field 620 in the . Each neighbor AP information field 620 may include a target beacon transmission time (TBTT) information header field, a working class field, a channel number field, and a TBTT information set field, which are composed of 2, 1, 1, and a variable number of octets, respectively. However. These report elements 610, 620 are limited to the announcement and discovery of APs.
[0077] As mentioned before, there is a client discovery problem in the SBP procedure. Since it is very common nowadays to have whole house / office / building / entity coverage with multi-AP Wi-Fi (e.g., with mesh Wi-Fi or enterprise Wi-Fi networks), blindly measuring and reporting all possible links during the SBP reporting phase will result in a huge overhead of Wi-Fi links for reporting. Figure 7 A schematic diagram 700 is shown showing a floor plan of an office and the devices located therein. In the figure, non-AP MLD-1 is an SBP initiator 702 that performs human presence detection or tracking of people within the office premises (e.g., people entering the floor from any entrance (e.g., door 704)). There may be 15 possible links between the devices, as shown using lines between the devices, but for a people tracking sensing application focused on human presence detection near door 704, only 5 links 706-710 (between STA-5, phone-1, APMLD1, and non-AP MLD-1) are of interest.
[0078] Furthermore, for example, in the case of links between an AP (or AP MLD) and other non-AP STAs (other non-AP MLDs) and links between a STA associated with an AP (or a non-AP MLD associated with an AP MLD) and other STAs / APs, the SBP initiator typically has limited or no knowledge of potential links for sensing measurements. Blindly requesting sensing measurements on all possible links will result in a huge overhead in a wireless network, where in reality sensing measurements in many links may be of little or no interest to sensing applications. Although WLAN sensing is considered here as an example where information of other non-AP STAs will be useful to another non-AP STA, the utility is not limited to sensing applications and may benefit many other applications, such as network visualization / troubleshooting, load balancing, etc.
[0079] The present disclosure shows enhanced client discovery, which enables a non-AP STA (or non-AP MLD) to obtain information about potential links from an AP (or APMLD). The link can be an AP to STA link (e.g., initiator to responder (I2R) or responder to initiator (R2I)) or a STA to STA link (e.g., responder to responder (R2R)). The present disclosure also seeks to propose related signaling and frame formats for enhanced client discovery.
[0080] Note that the various embodiments below use SBP to illustrate enhanced client discovery to solve client discovery problems and questions. It should be understood that this enhanced client discovery that enables non-AP STAs (or non-AP MLDs) to access information about other non-AP STAs can be applied to and benefit many other applications with other similar client discovery problems, such as SBP setting wireless network visualization for administrators to perform network planning and troubleshooting, Wi-Fi load balancing.
[0081] Figure 8 A schematic diagram of a communication device 800 according to the present disclosure is depicted. The communication device 800 may also be implemented as a sensing initiator, a sensing responder, an SBP initiator, or an SBP responder.
[0082] like Figure 8 As shown, the communication device 800 may include a circuit 814, at least one radio transmitter 802, at least one radio receiver 804, and at least one antenna 812 (for simplicity, for the purpose of illustration, Figure 8Only one antenna is depicted in FIG. 8 ). The circuit 814 may include at least one controller 806 for software and hardware-assisted execution of the tasks that the at least one controller 806 is designed to perform, including controlling communications with one or more other communication devices in the MIMO wireless network. The circuit 814 may also include at least one transmit signal generator 808 and at least one receive signal processor 810. The at least one controller 806 may control the at least one transmit signal generator 808 to generate MAC frames and PPDUs to be sent to one or more other communication devices via the at least one radio transmitter 802, wherein the MAC frame may be, for example, a client discovery query / request / response frame, a polling trigger frame, a detection trigger frame, an NFRP trigger frame; and, for example, the PPDU may be a PPDU for non-trigger-based communication, a PPDU for a triggered detection procedure, a PPDU for a triggered downlink transmission (if the communication device 800 is an AP), or a PPDU for a triggered uplink transmission (if the communication device 800 is a STA). At least one controller 806 may control at least one receive signal processor 810 to process MAC frames and PPDUs received from one or more other communication devices through at least one radio receiver 804 under the control of at least one controller 806, wherein the MAC frame may be, for example, a client discovery query / request / response frame, a polling trigger frame, a detection trigger frame, an NFRP trigger frame; and, for example, the PPDU may be a PPDU for non-trigger-based communication, a PPDU for a trigger-based detection procedure, a PPDU for a trigger-based uplink transmission (if the communication device 800 is an AP), or a PPDU for a trigger-based downlink transmission (if the communication device 800 is a STA). At least one transmit signal generator 808 and at least one receive signal processor 810 may be independent modules of the communication device 800, which communicate with at least one controller 806 for the above functions, such as Figure 8 As shown. Alternatively, at least one transmit signal generator 808 and at least one receive signal processor 810 may be included in at least one controller 806. It will be appreciated by those skilled in the art that the arrangement of these functional modules is flexible and may vary depending on actual needs and / or requirements. Data processing, storage and other related control devices may be provided on appropriate circuit boards and / or in chipsets. In various embodiments, at least one radio transmitter 802, at least one radio receiver 804 and at least one antenna 812 may be controlled by at least one controller 806.
[0083] The communication device 800 provides the functions required for enhancing client discovery. For example, the communication device 800 may be an SBP initiator, and the circuit 814 (e.g., at least one transmit signal generator 808 of the circuit 814) may generate a first frame, and the at least one radio transmitter 802 may then transmit the first frame to the SBP responder to request the sensing responder's information.
[0084] In one embodiment, in the event that one or more potential sensing responders exist, the circuitry 814 may also generate a second frame, and the at least one radio transmitter 802 may then transmit the second frame to request information of the particular potential sensing responders.
[0085] In another embodiment, at least one radio receiver 804 may receive a verification request frame to request verification information indicating that the communication device 800 is authorized to obtain information of the sensing responder. The circuit 814 (e.g., at least one receive signal processor 810 and at least one transmit signal generator 808 of the circuit 814, respectively) may process and generate a verification response frame including the verification information. Then, the at least one radio transmitter 802 may transmit the verification response frame.
[0086] The communication device 800 may be a sensing SBP responder, and at least one radio receiver 804 receives a request frame requesting information of another non-AP STA (e.g., a sensing responder) from a non-AP STA (e.g., an SBP initiator). The circuit 814 (e.g., at least one receive signal processor 810 and at least one transmit signal generator 808 of the circuit 814, respectively) processes the request frame and generates a response frame including the information. The at least one radio transmitter 802 may then send the response frame to the SBP initiator.
[0087] In one embodiment, the circuit 814 (e.g., at least one transmit signal generator 808 of the circuit 814) may also generate an authentication request frame to request authentication information, the authentication information indicating that the requesting non-AP STA (e.g., SBP initiator) is authorized to obtain information of the target non-AP STA (e.g., sensing responder). Then, the at least one radio receiver 804 receives an authentication response frame including the authentication information from the SBP initiator.
[0088] Fig. 9 A flow chart 900 illustrating a communication method implemented by a first communication device such as an SBP initiator according to various embodiments of the present disclosure is shown. In step 902, a step of generating a first frame is performed. In step 904, a step of sending the first frame generated in step 902 to a second communication device such as an SBP responder to request information of a third communication such as a sensing responder is performed.
[0089] Fig.10 A flow chart 1000 illustrating a communication method implemented by a second communication device such as an SBP responder according to various embodiments of the present disclosure is shown. In step 1002, a step of receiving a request for information of a third communication device such as an inductive responder from a first communication device such as an SBP initiator is performed. In step 1004, a step of processing the request frame received in step 1002 and generating a response frame including the information is performed. In step 1006, a step of sending the response frame generated in step 1004 to the first communication device is performed.
[0090] According to various embodiments of the present disclosure, the enhanced client discovery procedure consists of a client discovery query procedure and a client discovery responder procedure, and there may be many levels of enhanced client discovery procedures. A non-AP STA (eg, an SBP initiator) may perform any one or more levels for client discovery.
[0091] For level 1 client discovery query, the non-AP STA requests the AP to provide a list of non-AP STAs (associated non-AP STAs and optionally non-associated non-AP STAs). In the request, the non-AP STA may optionally specify discovery criteria, such as (i) STA capabilities (PHY version (11ax, 11be, etc.), supported features (11bf, SBP, etc.), etc., (ii) link metrics (minimum downlink / uplink received channel power indicator (RCPI) / received signal strength indicator (RSSI), maximum data rate, etc.). Note that the STA requesting enhanced client discovery does not need to be associated with the AP.
[0092] For level 1 client discovery response, in response to a level 1 client discovery query, the AP provides information of a list of all its associated non-AP STAs (e.g., MAC addresses or association identifiers (AIDs)) and optional information of its non-associated non-AP STAs (e.g., non-association identifiers (UIDs)). If discovery criteria are provided in the query, the AP may provide a list of non-AP STAs that meet the discovery criteria.
[0093] For level 2 client discovery queries, a non-AP STA can request detailed information for a specific non-AP STA by indicating its ID (e.g., MAC address or association identifier (AID) or unassociation identifier (UID)) in the query. Such an ID can be obtained through the level 1 client discovery query and response steps. In the request, the requesting non-AP STA can indicate whether information about other devices within the radio range of the specifically indicated non-AP STA is required. It should be noted that the non-AP STA requesting enhanced client discovery does not need to be associated with an AP.
[0094] For Level 2 Client Discovery Response, in response to a Level 2 Client Discovery Query, the AP provides detailed information about the indicated non-AP STA, such as (i) STA capabilities (PHY version (11ax, 11be, etc.), supported features (11bf, SBP, etc.), etc.), (ii) link metrics (minimum downlink / uplink RCPI / RSSI, maximum data rate, etc.), and (iii) a list of other non-AP STAs and APs within the radio range of the indicated non-AP STA (if so requested in the query).
[0095] There is also level 3 client discovery. More information about level 3 client discovery queries and responses is explained below.
[0096] Essentially, regardless of its level, the enhanced client discovery procedure described in this disclosure is different from the above and Fig. 6A The existing neighbor AP discovery procedure shown in -C is aimed at the advertisement and discovery of APs. The main goal of the enhanced client discovery described in this disclosure involves the discovery of non-AP STAs.
[0097] Fig.11 A flowchart 1100 illustrating an example level 1 and level 2 enhanced client discovery procedure between a non-AP STA and an AP is shown. The non-AP STA may first perform level 1 enhanced client discovery by sending a client discovery query frame specifying discovery criteria to the AP. No target client (i.e., non-AP STA or sensing responder) is specified. The AP then sends a client discovery response frame with a list of the AP's clients that meet the discovery criteria. With the information of the AP's clients, the non-AP STA may then perform level 2 enhanced client discovery by sending another client discovery query frame specifying the client ID. A field (in this case, the neighbor field) is set to 1 to indicate that information about neighbor clients / devices (AP or non-AP) of the specified client (i.e., clients / devices within a radio range of the specified client) is also requested. The AP then sends another client discovery response frame, which includes detailed information of the specified client and other clients within the radio range of the specified client. Optionally, discovery criteria for neighboring devices / clients (such as (i) STA capabilities (PHY version (11ax, 11be, etc.), supported features (11bf, SBP, etc.), etc.) and (ii) link metrics (minimum downlink / uplink RCPI / RSSI, maximum data rate, etc.)) may also be included in the client discovery query frame, so that the AP can send detailed information only for the specified client and other clients that are within the radio range of the specified client and meet the discovery criteria.
[0098] Fig.12A flowchart 1200 illustrating an exemplary level 1 and level 2 enhanced client discovery procedure between a non-AP MLD and an AP MLD is shown. For the enhanced client discovery procedure between MLDs, a client discovery query may indicate one or more subordinate APs of an AP MLD (or a BSS provided by an AP MLD) and be addressed to any subordinate AP of the AP MLD through any link of the AP MLD.
[0099] In addition to the discovery criteria, the client discovery query frame may also indicate a list of affiliated APs of the MLD to perform an enhanced client discovery procedure. In this case, STA1 affiliated with a non-AP MLD may perform level 1 enhanced client discovery by sending a client discovery query frame to AP2 affiliated with an AP MLD. The client discovery query frame may specify the discovery criteria and indicate a list of affiliated APs (e.g., AP1, AP2). The AP then sends a client discovery response frame, which includes the non-MLD clients of the indicated AP (e.g., clients of AP1, clients of AP2) and a list of non-AP MLDs associated with the AP MLD and meeting the discovery criteria.
[0100] With the information of the AP's clients, the non-AP STA can then perform level 2 enhanced client discovery by sending another client discovery query frame specifying the client ID to the AP MLD again (via AP2). A specific non-AP STA or non-AP MLD may be associated with another AP of the AP MLD (e.g., a client of AP1). The field (in this case, the neighbor field) is set to 1 to indicate that information about neighbor clients / devices (APs or non-APs) of the specified client that are within the radio range of the specified client is also requested. The AP MLD (via the affiliated AP) then sends another client discovery response frame that includes detailed information about the specified client and other clients within the radio range of the specified client.
[0101] In the following paragraphs, a first embodiment of the present disclosure in which an enhanced client discovery procedure between an AP and a non-AP STA (or an AP MLD and a non-AP MLD) is described.
[0102] Fig.13A flowchart 1300 illustrating an enhanced client discovery procedure between an AP and a non-AP STA according to a first embodiment of the present disclosure is depicted. The AP uses a beacon frame to advertise its ability to support enhanced client discovery and basic information about associated non-AP STAs (e.g., count / number of associated STAs, etc.). The non-AP STA may perform basic discovery and discover the AP's support for enhanced client discovery and the number of STAs associated with the AP. Subsequently, the non-AP STA may perform association and security association (SA) establishment (or pre-association security negotiation) with the AP.
[0103] The non-AP STA then sends a protected client discovery query frame to request basic information of other non-AP STAs associated with the AP. The protected client discovery query frame has its level field set to 1 to indicate a level 1 enhanced client discovery query and includes discovery criteria. The AP may perform additional authorization verification by sending an authorization verification request frame back to the non-AP STA to request verification information or authorization proof (e.g., a shared password) that the non-AP STA is authorized to obtain information of other non-AP STAs. Then, in response, the non-AP STA sends an authorization verification response frame including verification information or authorization proof (e.g., a password) to prove that it is authorized for enhanced client discovery to obtain information of other non-AP STAs.
[0104] If the authorization verification is successful, the steps shown in box 1302 are executed; otherwise, the steps shown in box 1304 are executed. Specifically, if the authorization verification is successful, the AP then sends a protected client discovery response frame to the non-AP STA, and the protected client discovery response frame includes information of a list of clients of the AP that meet the discovery criteria. In addition, the non-AP STA may also send a second protected client discovery query frame to the AP to request detailed information of a specific non-AP STA (client) associated with the AP. The second protected client discovery query frame has its level field set to 2 to indicate a level 2 enhanced client discovery query, and indicates a client ID to identify the non-AP STA (client), and has its neighbor field set to 1 to indicate information of neighboring devices / clients within a range of the client.
[0105] Although not shown in the figure, upon receiving the level 2 client discovery query frame, the AP can trigger a neighbor client discovery request to each of its associated non-AP STAs to discover information of its neighboring STAs and APs. The AP then sends a protected client discovery response frame back to the non-AP STA, which includes detailed information of the indicated client and its neighboring STAs and the AP of the indicated client.
[0106] If the authorization verification is unsuccessful, the AP does not provide information about its associated non-AP STAs, but will send a protected client discovery response frame with a status field indicating that the authorization verification is unsuccessful.
[0107] In one example, if the AP has other means to verify the authorization of the non-AP STA to obtain information about other non-AP STAs, the exchange of the authorization verification request / response frame can be skipped. For example, the AP can maintain a list of authorized devices, or it can consult a list of authorized devices from a database on a server, etc.
[0108] Fig.14 A flowchart 1400 illustrating an enhanced client discovery procedure between an AP MLD and a non-AP MLD according to a first embodiment of the present disclosure is depicted. The AP MLD uses a beacon frame to advertise its ability to support enhanced client discovery and basic information about associated non-AP MLDs and non-AP STAs (e.g., count / number of associated STAs, etc.). The non-AP MLD may perform basic discovery and discover the AP MLD's support for enhanced client discovery and the number of MLDs / STAs associated with the AP MLD. Subsequently, the non-AP MLD may perform association and security association (SA) establishment (or pre-association security negotiation) with the AP MLD.
[0109] Then, the non-AP MLD (e.g., via STA1) sends a protected client discovery query frame to the AP MLD (e.g., via AP2) to request basic information of other non-AP MLD / STAs associated with the AP MLD or any of its subordinate APs. The protected client discovery query frame has its level field set to 1 to indicate a level 1 enhanced client discovery query, and includes discovery criteria and a list of subordinate APs (one or more subordinate APs) and via any of the subordinate APs. The AP MLD may perform additional authorization verification by sending an authorization verification request frame back to the non-AP MLD to request verification information or authorization proof (e.g., a shared password) that the non-AP MLD is authorized to obtain basic information of other non-AP MLD / STAs. Then, in response, the non-AP MLD sends an authorization verification response frame including the verification information or authorization proof (e.g., a password) to prove that it is authorized for enhanced client discovery to obtain information of other non-AP MLD / STAs.
[0110] If the authorization verification is successful, the steps shown in box 1402 are executed; otherwise, the steps shown in box 1404 are executed. Specifically, if the authorization verification is successful, the AP MLD sends a protected client discovery response frame to the non-AP MLD, and the protected client discovery response frame includes information of a list of clients of the AP MLD that meet the discovery criteria. In addition, the non-AP MLD may also send a second protected client discovery query frame to the AP MLD to request detailed information of a specific non-AP MLD / STA (client) associated with the AP MLD or any of its affiliated APs. The second protected client discovery query frame has its level field set to 2 to indicate a level 2 enhanced client discovery query, and indicates a client ID to identify the non-AP MLD / STA (client), and has its neighbor field set to 1 to indicate information of neighboring devices / clients within a range of the client.
[0111] Although not shown in the figure, upon receiving the level 2 client discovery query frame, the AP MLD may trigger a neighbor client discovery request to each of its associated non-AP MLD / STAs to discover information of their neighboring STAs and APs. The AP MLD then sends a protected client discovery response frame back to the non-AP MLD, which includes detailed information of the indicated client and its neighboring STAs and the AP of the indicated client.
[0112] If the authorization verification is unsuccessful, the AP MLD does not provide information about its associated non-AP MLD / STA, but will send a protected client discovery response frame with a status field indicating that the authorization verification is unsuccessful.
[0113] This procedure may also be applicable to the case where the non-AP STA is MLD aware (i.e., it understands MLO related signaling, e.g., multi-link elements, etc.), and requests information about its associated non-AP MLD and non-AP STAs associated with its affiliated AP from the AP MLD.
[0114] Fig.15An example visualization of level 1 and level 2 enhanced client discovery results is shown. Such a visualization can be displayed on the screen of a laptop, smartphone, or any electronic device. In this example, the SBP initiator (not shown) can perform level 1 client discovery and can only display a list of APs / AP MLDs (in this case, four different APs (AP MLD1, AP MLD2, AP4, AP3)). Each AP then sends their discovery results to the SBP initiator, which include a list of STAs (and / or MLDs) associated with the AP and their basic information. The results can be sorted in descending order according to their link quality. Optionally, a list of non-associated STAs (and / or MLDs) known to the AP is also provided by the AP. In this example, AP MLD1 provides information of non-AP MLD1, STA5, and phone 1; AP MLD2 provides information of non-AP MLD2 and STA1; AP4 provides information of STA4 and STA6; and AP3 provides information of STA2 and STA3. The SBP initiator can additionally or alternatively perform level 2 client discovery. This level 2 client discovery can be triggered when a specific STA or non-AP MLD is selected. In this example, non-AP MLD1 may be selected, and the SBP initiator performs level 2 client discovery on non-AP MLD1, and a client discovery query frame including the ID of non-AP MLD1 is sent to AP MLD1. Therefore, AP MLD1 then provides information of non-AP MLD1 and its neighboring APs, AP MLDs, STAs, non-AP MLDs (in this case, STA5, Phone 1, STA1, AP4, AP MLD2, and STA4) within the radio range of the affiliated STAs of non-AP MLD1, as shown in block 1502.
[0115] Fig.16 An example format of a multilink element (MLE) 1600 for basic discovery according to an embodiment of the present disclosure is shown. The MLE 1600 includes an element ID field, a length field, an element ID extension field, a multilink control field, a common information field, and a link information field. The multilink control field includes a type subfield set to "basic" and a presence bitmap subfield. The common information field may include an MLD capability subfield, and in the case of an AP MLD, may include an associated non-AP MLD count subfield. The associated non-AP MLD count subfield is used to announce the total number of non-AP MLDs associated with the AP MLD. The MLD capability subfield includes an AP Assisted Request (AAR) support subfield and an enhanced client discovery subfield. The AP MLD announces its support for enhanced client discovery in the enhanced client discovery subfield within the MLD capability subfield.
[0116] The link information field includes one or more per-STA profile sub-element sub-fields corresponding to one or more links (corresponding to the attached STA / AP), each per-STA profile sub-element field including a sub-element ID field, a length field, a STA control field, a STA information field, and a STA profile field. The STA control field includes a link ID sub-field. The STA profile field includes an extended capability element sub-field, and in the case of an AP MLD, includes a BSS load element sub-field. The BSS load element sub-field includes an element ID field, a length field, and a station count field. The station count field is used to announce the total number of STAs (non-MLDs) associated with the attached AP working on the link. The extended capability element sub-field includes an element ID field, a length field, and an extended capability including an enhanced client discovery sub-field. The attached STA / AP of the STA or MLD announces its support for enhanced client discovery in the enhanced client discovery sub-field within the extended capability field of the extended capability element sub-field.
[0117] For a STA / AP that is not an MLD, or an AP that is attached to an AP MLD that is a reporting STA / AP (i.e., a STA / AP that is sending a frame carrying a basic multilink element (MLE), the Extended Capabilities Element subfield and the BSS Load Element subfield are carried in the frame body (instead of in the basic MLE). For a non-AP MLD or an attached STA / AP of an AP MLD, that is, not a reporting AP (i.e., the STA / AP is a reporting STA / AP), the Extended Capabilities Element subfield and the BSS Load Element subfield are carried in the Link Information field of the basic MLE. For an AP / AP MLD, these elements are carried in a beacon, a probe response, a (re)association response frame, etc. For a non-AP STA / MLD, this element is carried in a probe request, a (re)association request frame, etc.
[0118] Fig.17An example format of a multi-link load element 1700 used by an AP MLD for basic discovery according to an embodiment of the present disclosure is shown. Instead of using MLE for basic discovery, an AP MLD may use a multi-link load element 1700 carried in a beacon, a probe response, a (re)association response frame, etc. to announce the number of associated non-AP MLDs and the number of non-MLD STAs associated with each of its affiliated APs. The multi-link load element includes an element ID field, a length field, an element ID extension field, an associated non-AP MLD count field, a link ID bitmap field, and one or more link load fields. The associated non-AP MLD count field is used to announce the total number of associated non-AP MLDs. Each link load field includes a total STA count subfield, a channel utilization subfield, an enabled STA count subfield, and a BSS utilization subfield. The total STA count subfield is used to announce the number of STAs (non-MLDs) associated with the affiliated APs working on the link.
[0119] Fig.18 An example format of a protected client discovery query frame 1800 for a level 1 client discovery query according to an embodiment of the present disclosure is shown. The protected client discovery query frame 1800 includes a MAC header (frame control field, duration field, receiver address (RA) field, and sender address (TA) field), a category field set to "protected discovery", an action field set to "protected client discovery query", a dialog token field, a client discovery mode field, a client discovery request element field, and a frame check sequence (FCS) field. Client discovery can be set to 0, 1, or 2 to indicate level 1, 2, or 3 client discovery, respectively. In this case, since the protected client discovery query frame 1800 is used for a level 1 client discovery query, the client discovery mode field is set to 0.
[0120] The client discovery request element field includes an element ID field, a length field, an element ID extension field, a discovery standard bitmap field, a PHY version bitmap field, a supported feature bitmap field, a link metric field, an operating channel width field, an MLD information field, and a BSSID list field. The discovery standard bitmap field includes a target STA information presence subfield, a PHY version presence subfield, a supported feature presence subfield, a link metric presence subfield, an operating channel width presence subfield, an MLD information presence subfield, and a BSSID list presence subfield, indicating the presence of an additional field used as a criterion for selecting a STA / non-AP MLD. The target STA information presence subfield is set to 0 in level 1 client discovery. The PHY version bitmap field includes a high throughput (HT) subfield, a very high throughput (VHT) subfield, a high efficiency (HE) subfield, and an extremely high throughput (EHT) subfield to indicate the PHY version supported by the STA / non-AP MLD. The bitmap of supported features indicates the features to be supported by the target non-AP STA, and includes a Tunnel Direct Link Setup (TDLS) support subfield, a WLAN sensing subfield, and an SBP subfield, etc., to indicate the features supported by the STA / non-AP MLD. The link metric field includes a minimum RSSI / RCPI subfield and a minimum data rate subfield to indicate the link metrics supported by the STA / non-AP MLD. The link metric is measured between the STA and the associated AP. The operating channel width field indicates the operating channel width of the STA to be discovered. The MLD information field exists only when the frame is addressed to an AP attached to an AP MLD, and includes an MLD ID subfield carrying the MLD ID of the AP MLD and a link ID bitmap subfield carrying the link for which information is requested.
[0121] If the BSSID List field is present, information about non-AP STAs associated with all BSSIDs is requested. If the BSSID List field is not present, then by default, a non-MLD AP will only provide information about its own associated non-AP STAs, while an AP MLD will provide information about non-AP STAs associated with all its subordinate APs (in addition to information about associated non-AP MLDs).
[0122] In addition, the discovery criteria bitmap field may also include a "Device Location" bit (not shown), which, when set, indicates that a device location element (as defined in IEEE 802.11-2020) and coverage area information (e.g., signal strength radius) are included in the client discovery query frame, and indicates a target geographic location where a non-AP STA or non-AP MLD is expected to be located (e.g., within a -62dBm RSSI / RCPI radius). The discovery criteria bitmap field may also include an "Include Only Associated STAs" bit (not shown) to indicate that information about non-AP STAs / MLDs that are not associated with an AP / AP MLD is not requested when this bit is set to 1, or that an AP / AP MLD may include information about non-AP STAs / MLDs that are not associated with an AP / AP MLD in a client discovery response when this bit is set to 0.
[0123] Fig.19 An example format of a protected authorization verification request frame 1900 according to an embodiment of the present disclosure is shown. The protected authorization verification request frame 1900 includes a MAC header (frame control field, duration field, RA field, and TA field), a category field set to "protected discovery", an action field set to "protected authorization verification request frame", a dialog token field, a verification mode field, and an FCS field. The verification mode field can be set to 0 to indicate a plaintext password and set to 1 to indicate a hashed password.
[0124] Fig. 20 An example format of a protected authorization verification response frame 2000 according to an embodiment of the present disclosure is shown. The protected authorization verification response frame 2000 includes a MAC header (frame control field, duration field, RA field, and TA field), a category field set to "protected discovery", an action field set to "protected authorization verification response frame", a dialog token field, a verification mode field, a verification information field, and an FCS field. The verification information field includes a PN / TSF field, a length field, and a verification text field. The PN / TSF field carries a packet number or a time synchronization function used as a salt to prevent replay attacks. The length field indicates the length of the verification text carried in the verification text field, and the verification text field carries a plain text password or a hashed password based on the verification mode field.
[0125] As previously described, if the AP has other means to verify the authorization of the non-AP STA to obtain information about other non-AP STAs, the authorization verification request / response can be skipped; for example, the AP can maintain a list of authorized devices, or it can consult a list of authorized devices from a database on a server, etc.
[0126] For example, the hash password is SHA-256(key, PN / TSF||plaintext password), where key is a public private secret key known to both parties, such as a PTK generated during a security association, or it can be a separate application-specific secret key (e.g., passed by an upper layer application) whose only purpose is to enhance client discovery, "||" is a cascading action, and PN / TSF is the value of the PN / TSF field, and the sender should ensure that the same value is never used twice to prevent replay attacks. For example, it can be a monotonically increasing number, or it can contain the current value of the sender's time synchronization function (TSF).
[0127] Fig.21 An example format of a level 1 client discovery response frame 2100 according to an embodiment of the present disclosure is shown. The client discovery response frame 2100 is transmitted between a non-MLD SBP initiator and a responder. The client discovery response frame 2100 includes a MAC header (frame control field, duration field, RA field, and TA field), a category field set to "protected discovery", an action field set to "protected client discovery response", a dialog token field, a client discovery mode field set to 0 to indicate level 1 client discovery, a status code field, a client information element field, and an FCS field. The client information element field includes an element ID field, a length field, an element ID extension field, a STA information control field, and a STA information list field. The STA information control field includes a STA count subfield, a neighbor STA bit, and a presence bitmap subfield. The STA count subfield indicates the number of STA information fields (1 for each non-AP STA) present in the STA information list field. The neighbor STA bit is set to 0 to indicate that the STA information list carries information of associated STAs (and optionally, non-associated non-AP STAs within a range of an AP). The presence bitmap subfield indicates the fields present in the STA information field, and includes a MAC address presence subfield, an Internet Protocol (IP) address presence subfield, an operating channel width presence subfield, a UL RSSI / RCPI presence subfield, a data rate presence subfield, and a BSSID presence subfield. The STA information list field includes one or more STA information fields. Each STA information field carries information of each associated non-AP STA that meets the discovery criteria indicated in the client discovery query frame, and includes a MAC address subfield carrying the MAC address of the non-AP STA, an Internet Protocol (IP) address subfield, an operating channel width subfield, a UL RSSI / RCPI subfield, and a BSSID subfield carrying the BSSID of the associated AP.
[0128] In addition, the STA information field may also include the capabilities and operating parameters of the STA (not shown) (e.g., basic, HT, VHT, HE, EHT, WLAN sensing capability element, HT, VHT, HE, EHT operating element, etc.). The STA information may also include a device type field (e.g., laptop, PC, smart phone, smart home appliance, etc.) and a device location element field (as defined in IEEE802.11-2020), which indicates the geographical location where the non-AP STA or non-AP MLD is located (e.g., within a 10ms radius). When the STA information carries the information of a DMG (directional multi-gigabit, i.e., 802.11ad) or EDMG (enhanced directional multi-gigabit, i.e., 802.11ay) STA, the STA information field may also carry a sector selection subfield (not shown), which contains the value of the sector ID subfield of the SSW field in the frame received with the best quality in the immediately preceding sector scan. The sector ID subfield is set to indicate the sector number by which the frame containing the SSW field is sent.
[0129] If the discovery criteria bitmap in the query frame also includes an "include associated STAs only" bit, then when this bit is set to 1, information about non-AP STAs that are not associated with the AP is not included in the client discovery response frame, and when this bit is set to 0, the AP may include information about non-AP STAs that are not associated with the AP in the client discovery response frame. Note that the AP may maintain a list of non-associated non-AP STAs with which any frame exchange (e.g., probe request / response) has been previously performed, or which have attempted to associate with the AP, or which have been disassociated from the AP within a certain time window (e.g., 30 minutes, etc.).
[0130] Fig. 22Another example format of a level 1 client discovery response frame 2200 according to an embodiment of the present disclosure is shown. The client discovery response frame 2200 is transmitted between an MLD SBP initiator (e.g., a non-AP MLD) and an AP MLD. The client discovery response frame 2200 includes a MAC header (frame control field, duration field, RA field, and TA field), a category field set to "protected discovery", an action field set to "protected client discovery response", a dialog token field, a client discovery mode field set to 0 to indicate level 1 client discovery, a status code field, an MLD information element field 2202, a client information element field, a client information ML element field, and an FCS field. The MLD information element field 2202 carries information of an associated non-AP MLD whose at least one affiliated STA meets the discovery criteria. The client information element field carries information of a non-AP STA provided by an affiliated AP that sends the response frame 2200. The client information ML element field is a new "client information" variant of the ML element, which carries information of a non-AP STA provided by an affiliated AP other than the AP that sends the response frame 2200.
[0131] Fig.23 Shows Fig. 22 2200 . The MLD information element field 2202 includes an element ID field, a length field, an element ID extension field, an MLD information control field, and an MLD information list field. The MLD information control field includes an MLD count subfield, a neighbor MLD bit, and a presence bitmap subfield. The MLD count subfield indicates the number of MLD information fields (1 per non-APMLD) present in the STA information list field. The neighbor MLD bit is set to 0 to indicate that the MLD information list carries information of the associated MLD (as opposed to the neighbor MLD). The presence bitmap subfield includes an MLD MAC address presence subfield, an MLD ID presence subfield, an IP address presence subfield, a MAC address presence subfield, an operating channel width presence subfield, a UL RSSI / RCPI presence subfield, a data rate presence subfield, and a BSSID presence subfield. The MLD MAC address presence subfield, the MLD ID presence subfield, and the IP address presence subfield indicate the presence of the corresponding fields in the common information subfield of each MLD information field, while the MAC address presence subfield, the operating channel width presence subfield, the UL RSSI / RCPI presence subfield, the data rate presence subfield, and the BSSID presence subfield indicate the presence of the corresponding fields in the link information subfield of each MLD information field.
[0132] The MLD information list field includes one or more MLD information fields. Each MLD information field carries information of a non-AP MLD whose at least one affiliated STA meets the discovery criteria indicated in the client discovery query frame, and includes a common information subfield, a link ID bitmap subfield, and one or more link information subfields. The common information subfield includes an APMLD bit, an MLD MAC address subfield, an MLD ID subfield, and an IP address subfield. The AP MLD bit indicates the type of MLD. The AP MLD bit can be set to 0 to indicate a non-AP MLD, and set to 1 to indicate an AP MLD. In this case, the AP MLD bit is set to 0, indicating a non-AP MLD. The MLD MAC address subfield carries the MAC address of the non-AP MLD. The MLDID carries the MLD ID of the associated AP MLD.
[0133] The Link ID Bitmap subfield indicates the link of the MLD whose information is carried in the Link Information subfield. Each Link Information subfield carries information of each non-AP STA provided by the attached AP operating on the link and meeting the discovery criteria indicated in the Client Discovery Query frame, and includes a MAC Address subfield carrying the MAC address of the attached non-AP STA, an Operating Channel Width subfield, a UL RSSI / RCPI subfield, a Data Rate subfield, and a BSSID subfield carrying the BSSID of the associated AP.
[0134] The link information subfield of the MLD information field may also include capabilities and operating parameters (not shown) of the STA (e.g., basic, HT, VHT, HE, EHT, WLAN sensing capability element, HT, VHT, HE, EHT operating element, etc.). The common information subfield of the MLD information may also include an MLD capability element, a device type (e.g., a laptop, PC, smart phone, smart appliance, etc.), and a device location element (as defined in IEEE 802.11-2020), which indicates the geographical location where the non-AP STA or non-AP MLD is located (e.g., within a -62dBm RSSI / RCIP radius), etc.
[0135] In addition, if the discovery criteria bitmap in the query also includes the "include associated STAs only" bit, then when this bit is set to 1, information about non-AP STAs / MLDs that are not associated with the affiliated AP / AP MLD is not included in the client discovery response; but when this bit is set to 0, the AP MLD may include information about non-AP STAs / MLDs that are not associated with the affiliated AP / AP MLD in the client discovery response. Note that the AP MLD may maintain a list of non-associated non-AP STAs and / or non-AP MLDs with which any frame exchange (e.g., probe request / response) has been previously performed, or an attempt has been made to associate with the AP MLD or an affiliated AP, or a disassociation with the AP MLD or any affiliated AP within a certain time window (e.g., 30 minutes, etc.).
[0136] return Fig. 22 The client information ML element field includes an element ID field, a length field, an element ID extension field, a multilink control field, a common information field, and a link information field. The multilink control field includes a type subfield set to "client information" and a presence bitmap subfield.
[0137] Table 1 shows various multilink element variants corresponding to the value of the Type subfield.
[0138] Type subfield value Multilink element variant name 0 Basics 1 Probe Request 2 Reconfiguration 3 TDLS 4 Priority access 5 Sensing 6 Client Information
[0139] The Common Information field includes an MLD MAC Address subfield that carries the MLD MAC address of the AP MLD. The Link Information field includes one or more per-STA Profile sub-element subfields corresponding to one or more links, each per-STA Profile sub-element field including a sub-element ID field, a length field, a STA Control field, a STA Information field, and a STA Profile field. The STA Control field includes a Link ID subfield corresponding to the attached AP operating on the link. The STA Profile field carries information of non-AP STAs associated with the attached AP operating on the link.
[0140] In addition, the STA information field may also include the supported capabilities, PHY version channel width, and location (e.g., basic, HT, VHT, HE, EHT, WLAN sensing capability element, HT, VHT, HE, EHT working element, etc.) of the affiliated AP. The location information may be obtained via GPS (when outdoors) or via fine time measurement and / or ranging (when indoors), etc. When the STA information field in the client discovery response frame carries information of a DMG (directional multi-gigabit, i.e., 802.11ad) or EDMG (enhanced directional multi-gigabit, i.e., 802.11ay) STA, the STA information field may also carry a sector selection subfield, which contains the value of the sector ID subfield of the SSW field in the frame received with the best quality in the immediately preceding sector scan. The sector ID subfield indicates the sector number by which the frame containing the SSW field is sent. When selecting a sensing responder STA in a DMG / EDMG STA, the AP may consider the information of the sector number. The STA Profile field carries a Client Information Element that carries information of a non-AP STA associated with the affiliated AP operating on the link.
[0141] If the discovery criteria bitmap in the query frame also includes the "include associated STAs only" bit, then when this bit is set to 1, the AP may not include information about non-AP STAs that are not associated with the AP in the client discovery response frame, and when this bit is set to 0, the AP may include information about non-AP STAs that are not associated with the AP in the client discovery response frame. Note that the AP may maintain a list of non-associated non-AP STAs with which it has previously performed any frame exchange (e.g., probe request / response), or attempted to associate with the AP, or disassociated from the AP within a certain time window (e.g., 30 minutes, etc.).
[0142] Fig.24 An example format of a protected client discovery query frame 2400 for a level 2 client discovery query according to an embodiment of the present disclosure is shown. The protected client discovery query frame 2400 includes a MAC header (frame control field, duration field, RA field, and TA) field, a category field set to "protected discovery", an action field set to "protected client discovery query", a dialog token field, a client discovery mode field, a client discovery request element field, and an FCS field. Client Discovery is set to 1 to indicate a level 2 client discovery query.
[0143] The client discovery request element fields include an element ID field, a length field, an element ID extension field, a discovery standard bitmap field, a target STA information field, a minimum RSSI / RCPI field, and a BSSID field.
[0144] The PHY version bitmap field, the supported features bitmap field, the link metric field, the operating channel width field, the MLD information field, and the BSSID list field. The discovery criteria bitmap field includes the target STA information presence subfield, the PHY version presence subfield, the supported features presence subfield, the link metric presence subfield, the operating channel width presence subfield, the MLD information presence subfield, and the BSSID list presence subfield. The subfield is set to 1 to indicate the presence of an additional field used as a criterion for selecting a non-AP STA or an affiliated STA for the requested non-AP MLD. The target STA information presence subfield is set to 1 in level 2 client discovery.
[0145] The PHY version bitmap field includes an HT subfield, a VHT subfield, a HE subfield, and an EHT subfield to indicate the PHY version supported by the STA / non-AP MLD. The bitmap of supported features indicates the features to be supported by the target non-AP STA, and includes a tunnel direct link establishment (TDLS) support subfield, a WLAN sensing subfield, and an SBP subfield to indicate the features supported by the STA / non-AP MLD. The link metric field includes a minimum RSSI / RCPI subfield and a minimum data rate subfield to indicate the link metrics supported by the STA / non-AP MLD. Link metrics are measured between the STA and the associated AP. The operating channel width field indicates the operating channel width of the STA to be discovered. The MLD information field only exists when the frame is addressed to an AP attached to an AP MLD, and includes an MLD ID subfield carrying the MLD ID of the AP MLD and a link ID bitmap subfield carrying the link for which information is requested.
[0146] If the BSSID List field is present, information about non-AP STAs associated with all BSSIDs is requested. If the BSSID List field is not present, then by default, a non-MLD AP will only provide information about its own associated non-AP STAs, while an AP MLD will provide information about non-AP STAs associated with all its subordinate APs (in addition to information about associated non-AP MLDs).
[0147] The Target STA Information field carries the information of the requested / indicated non-AP STA or non-AP MLD (i.e., the STA or MLD of interest), and includes a Target MAC Address subfield, a Neighbor Information Request subfield, and a Minimum RSSI / RCPI Existence subfield. The Target MAC Address subfield carries the MAC address of the requested non-AP STA, or the MLD MAC address of the requested non-AP MLD. Alternatively, an AID or UID may be provided instead of a MAC address. If information about neighboring devices is also requested, the Neighbor Information Request subfield is set to 1.
[0148] The Minimum RSSI / RCPI field indicates the link metric supported by the link with the neighboring device. The link metric is measured between the target STA and its neighboring STAs that are within a radio range of the target STA. The BSSID list (if present), the neighboring STAs are restricted to STAs associated with the APs corresponding to the BSSIDs in the list.
[0149] In addition, the discovery criteria bitmap may also include an "Exclude AP" bit, which, when set to 1, indicates that information about the AP / AP MLD is not requested, or, when set to 0, indicates that non-AP STA / non-AP MLD may also include information about the AP / AP-MLD in the client discovery response.
[0150] Fig.25An example format of a level 2 client discovery response frame 2500 according to an embodiment of the present disclosure is shown. The client discovery response frame 2500 is transmitted between a non-MLD SBP initiator and an SBP responder. The client discovery response frame 2500 includes a MAC header (frame control field, duration field, RA field, and TA field), a category field set to "protected discovery", an action field set to "protected client discovery response", a dialog token field, a client discovery mode field set to 1 to indicate level 2 client discovery, a status code field, a client information element field, and an FCS field. The client information element field includes an element ID field, a length field, an element ID extension field, a STA information control field, and a STA information list field. The STA information control field includes a STA count subfield, a neighbor STA bit, and a presence bitmap subfield. The STA count subfield indicates the number of STA information fields (1 for each neighboring non-AP STA) present in the STA information list field. The neighbor STA bit is set to 1 to indicate that the STA information list carries information of neighboring STAs. The presence bitmap subfields include a MAC address presence subfield (set to 0), an Internet Protocol (IP) address presence subfield (set to 0), an operating channel width presence subfield (set to 0), a UL RSSI / RCPI presence subfield, a data rate presence subfield (set to 0), and a BSSID presence subfield.
[0151] The STA information list field includes one or more STA information fields. Each STA information field carries information about each neighboring non-AP STA that meets the discovery criteria indicated in the client discovery query frame, and includes a MAC address subfield carrying the MAC address of the neighboring non-AP STA, a UL RSSI / RCPI subfield, and a BSSID subfield, which carries the BSSID of the BSS with which the neighboring non-AP STA is associated or the BSSID of the AP itself. If the MAC address field and the BSSID field are the same, it indicates that this is an AP. The UL RSSI / RCPI field indicates the RSSI / RCPI observed on the direct link between the non-AP STA and its neighboring non-AP STA, or the RSSI / RCPI observed on the link between the non-AP STA and its neighboring AP.
[0152] In addition, the STA information field may include the STA's supported capabilities, PHY version, channel width, and the STA's location. The location information may be obtained via GPS (when outdoors) or via fine time measurement and / or ranging (when indoors), etc. When the STA information field in the client discovery response frame carries information of a DMG (directional multi-gigabit, i.e., 802.11ad) or EDMG (enhanced directional multi-gigabit, i.e., 802.11ay) STA, the STA information field may also carry a sector selection subfield, which contains the value of the sector ID subfield of the SSW field in the frame received with the best quality in the immediately preceding sector scan. The sector ID subfield indicates the sector number, by which the frame containing the SSW field is sent. When selecting a sensing responder STA in a DMG / EDMG STA, the AP may use information that takes the sector number into consideration.
[0153] When the discovery criteria bitmap in the query includes the "Exclude AP" bit, when this bit is set to 1, information about the AP is not included in the client discovery response, and when this bit is set to 0, non-AP STA / non-AP MLD can also include information about the AP in the client discovery response.
[0154] Fig.26 Another example format of a level 2 client discovery response frame 2600 according to an embodiment of the present disclosure is shown. The client discovery response frame 2600 is transmitted between an MLD SBP initiator (e.g., non-AP MLD) and a responder (AP MLD). The client discovery response frame 2600 includes a MAC header (frame control field, duration field, RA field, and TA field), a category field set to "protected discovery", an action field set to "protected client discovery response", a dialog token field, a client discovery mode field set to 1 to indicate level 2 client discovery, a status code field, an MLD information element field, a client information element (neighbor STA) field, an MLD information element (neighbor MLD) field, a client information ML element field, and an FCS field. The MLD information element field carries information of the requested non-AP MLD (i.e., if the neighbor MLD bit is set to 0, the response frame 2600 carries only a single MLD information element field without any MLD information element (neighbor MLD) field. The client information element (neighbor STA) field carries information of the AP and neighbor STAs of the affiliated STA that sent the response frame 2600 and meets the link metric criteria indicated in the client discovery query frame. The MLD information element (neighbor MLD) field carries information of the neighbor MLD (i.e., when the neighbor MLD bit is set to 1).
[0155] Fig. 27 Shows Fig.2626. An example format of the MLD information element field of the protected client discovery response frame 2600 depicted in FIG. The MLD information element field includes an element ID field, a length field, an element ID extension field, an MLD information control field, and an MLD information list field. The MLD information control field includes an MLD count subfield, a neighbor MLD bit, and a presence bitmap subfield. The MLD count subfield indicates the number of MLD information fields (1 for each non-AP MLD) present in the STA information list field. The neighbor MLD bit is set to 1 to indicate that the MLD information list carries information of neighboring MLDs. The presence bitmap subfield includes an MLD MAC address presence subfield, an MLD ID presence subfield, an IP address presence subfield, a MAC address presence subfield, an operating channel width presence subfield, an UL RSSI / RCPI presence subfield, a data rate presence subfield, and a BSSID presence subfield. The MLD MAC address presence subfield, the MLD ID presence subfield, and the IP address presence subfield indicate the presence of the corresponding field in the common information subfield of each MLD information field. All bits except the MLD MAC address presence bit are set to 0. The MAC address exists subfield, the operating channel width exists subfield, the UL RSSI / RCPI exists subfield, the data rate exists subfield, and the BSSID exists subfield indicate the existence of the corresponding fields in the link information subfield of each MLD information field. All bits except the UL RSSI / RCPI exists bit are set to 0.
[0156] The MLD information list field includes one or more MLD information fields. Each MLD information field carries information of neighboring MLDs whose at least one affiliated STA meets the discovery criteria indicated in the client discovery query frame, and includes a common information subfield, a link ID bitmap subfield, and one or more link information subfields. The common information subfield includes an APMLD bit, an MLD MAC address subfield, an MLD ID subfield, and an IP address subfield. The AP MLD bit indicates the type of MLD. The AP MLD bit can be set to 0 to indicate a non-AP MLD, and set to 1 to indicate an AP MLD. The MLD MAC address subfield carries the MAC address of the MLD.
[0157] The Link ID Bitmap subfield indicates the link whose information is carried in the Link Information subfield. Each Link Information subfield carries information of a STA attached to a neighbor MLD and includes a MAC Address subfield carrying the MAC address of the attached STA, a UL RSSI / RCPI subfield, and a BSSID subfield carrying the BSSID of the associated AP of the attached non-AP STA of the non-AP MLD. For AP MLD, the BSSID subfield does not exist.
[0158] In addition, the link information subfield may also include the capabilities and operating parameters of the STA (e.g., basic, HT, VHT, HE, EHT, WLAN sensing capability element, HT, VHT, HE, EHT operating element, etc.). When the link information subfield carries the information of a DMG (directional multi-gigabit, i.e., 802.11ad) or EDMG (enhanced directional multi-gigabit, i.e., 802.11ay) STA, the STA information field may also carry a sector selection subfield, which contains the value of the sector ID subfield of the SSW field in the frame received with the best quality in the immediately preceding sector scan. The sector ID subfield is set to indicate the sector number by which the frame containing the SSW field is sent.
[0159] The common information subfield of the MLD information field may also include an MLD capability element, and a device location element (as defined in IEEE 802.11-2020) is included in the client discovery request element and indicates the geographic location where the MLD is located (e.g., within a 10ms radius or within a -62dBm RSSI / RCPI radius), etc.
[0160] return Fig.26 The Client Info ML element carries information of the AP and neighbor STAs of the affiliated non-AP STAs except the non-AP STA that sends the response frame, and includes an element ID field, a length field, an element ID extension field, a multi-link control field, a common information field, and a link information field. The multi-link control field includes, for example, a type subfield set to "client information" according to Table 1 and a presence bitmap subfield.
[0161] The Common Information field includes an MLD MAC Address subfield that carries the MLD MAC address of the requested non-AP MLD. The Link Information field includes one or more per-STA Profile sub-element subfields corresponding to one or more links, each per-STA Profile sub-element field including a sub-element ID field, a length field, a STA Control field, a STA Information field, and a STA Profile field. The STA Control field includes a Link ID subfield. The STA Profile field carries a Client Information Element with its Neighbor STA bit set to 1 and carries information of neighboring non-AP STAs and APs of affiliated non-AP STAs operating on the link.
[0162] In addition, the discovery standard bitmap may also include an "Exclude AP" bit, which, when set to 1, indicates that information about AP / AP MLD is not included in the client's discovery response frame 2600, and when the bit is set to 0, indicates that non-AP STA / non-AP MLD may also include information about AP / AP-MLD in the client discovery response.
[0163] In one embodiment of the present disclosure, the level 3 client discovery procedure may be triggered by the AP, for example, upon receiving a level 2 client discovery query from an associated non-AP STA, to discover neighboring non-AP STAs of the associated non-AP STA. Fig.28 A flowchart 2800 illustrating a level 3 client discovery procedure triggered by an AP according to an embodiment of the present disclosure is shown. Non-APSTA1 is an SBP initiator that initiates a level 2 client discovery query and requests detailed information of a specific non-AP STA (in this case, non-AP STA2) associated with the AP by sending a protected client discovery query frame to the AP. The protected client discovery query frame includes a level field set to 2 (or a client discovery mode set to 1) to indicate level 2 client discovery, a target client ID (i.e., a target MAC address field) set to the ID (MAC address) of non-AP STA2, and a neighbor information request field set to 1 to indicate that information of neighboring clients of the indicated STA (i.e., STAs and APs within a radio range of the indicated STA) is also requested. Upon receiving the level 2 client discovery query, the AP then initiates a level 3 client discovery query with the indicated non-AP STA (non-AP STA2) by sending a protected client discovery query frame to the indicated non-AP STA2. The protected client discovery query frame includes a Level field set to 3 (or a Client Discovery Mode field set to 2) to indicate Level 3 client discovery, a Target STA Information Presence field set to 1, and a Neighbor Information Request field set to 1. The discovery criteria included in the Level 2 Client Discovery Query frame transmitted by the non-AP STA1 will also be included in the Level 3 Client Discovery Query frame.
[0164] Upon receiving the level 3 client discovery query frame, non-AP STA2 collects information of its neighboring STAs and APs based on the provided discovery criteria, and then sends a protected client discovery response frame to provide the AP with detailed information of non-AP STA2 and its neighboring clients (e.g., non-AP STAs and APs). The AP then forwards the information received from the indicated non-AP STA2 to non-AP STA1.
[0165] The format and content of the protected client discovery query frame and protected client discovery response frame for level 3 client discovery are similar to those in Figure 24-27 The same as shown for Client 2 Client Discovery, except that for Level 3, the Client Discovery Mode field is set to 2 (instead of 1) and frames are sent in the opposite direction (i.e., the query is from the AP to the non-AP STA, and the response is from the non-AP STA to the AP).
[0166] A non-AP STA can collect information about its neighboring non-AP STAs and APs in various ways. In one way, it can passively listen to frames sent by its neighboring non-AP STAs and APs and record their details (MAC address from TA field, observed RSSI / RCPI, BSSID from BSSID field, etc.). In another approach, it may actively attempt to exchange frames with its neighbor non-AP STAs and APs, for example, (i) by sending TDLS discovery request frames to them (via the associated AP) and recording details from the TDLS discovery response frames received on the direct link (MAC address from the TA field, observed RSSI / RCPI, associated AP from the BSSID field, etc.); (ii) by exchanging ANQP request / response frames (group address GAS request / response frames) with the neighbor non-AP STAs on the direct path and recording details (MAC address from the TA field, observed RSSI / RCPI, BSSID from the BSSID field, etc.); or (iii) by exchanging probe request / response frames with the neighbor APs and recording details (MAC address from the TA field, observed RSSI / RCPI, BSSID from the BSSID field, etc.).
[0167] This level 3 client discovery can also be triggered by AP MLD. It is similar to that of non-MLD, except that the requested non-AP MLD collects information of neighboring STAs, APs of all subordinate STAs associated with the AP listed in the BSSID List field of the Client Discovery Request element, and information of neighboring non-AP MLDs and AP MLDs. In addition, for neighbor MLDs, non-AP MLDs also collect MLD related information, such as MLD MAC address.
[0168] Fig.29A flowchart 2900 illustrating a level 3 client discovery procedure triggered by an AP MLD according to an embodiment of the present disclosure is shown. A non-AP MLD or its subordinate STA is an SBP initiator, which initiates a level 2 client discovery query and requests detailed information of a specific non-AP STA associated with an AP (in this case, a non-AP STA subordinate to non-AP MLD2) by sending a protected client discovery query frame to the AP MLD. The protected client discovery query frame includes a level field set to 2 (or a client discovery mode field set to 1) to indicate level 2 client discovery, a client ID set to the client ID of non-AP MLD2, and a neighbor information request field set to 1 to indicate that information of neighboring clients of the indicated STA is also requested. Upon receiving the level 2 client discovery query, the AP MLD then initiates a level 3 client discovery query with the indicated non-AP MLD (non-AP MLD2) by sending a protected client discovery query frame to the indicated non-AP MLD2. The protected client discovery query frame includes a Level field set to 3 (or a Client Discovery Mode field set to 2) to indicate Level 3 client discovery, a Target STA Information Presence field set to 1, and a Neighbor Information Request field set to 1. The discovery criteria included in the Level 2 Client Discovery Query frame sent by non-AP MLD1 will also be included in the Level 3 Client Discovery Query frame.
[0169] Upon receiving the level 3 client discovery query frame, non-AP MLD2 collects information of the non-AP STA to which it belongs and the AP and neighboring STA of the neighbor MLD based on the provided discovery criteria, and then sends a protected client discovery response frame to provide detailed information of non-AP STA2 and its neighboring clients (e.g., MLD, non-AP STA, and AP) to AP MLD. AP MLD then forwards the information received from the indicated non-AP MLD2 to non-AP MLD1.
[0170] In the following paragraphs, a second embodiment of the present disclosure is described, in which an enhanced client discovery procedure is performed when an AP or AP MLD is part of a multi-AP network.
[0171] Fig.30 A schematic diagram 3000 illustrating a multi-AP network deployment according to a second embodiment of the present disclosure is shown. If the AP or AP MLD is part of a multi-AP network (e.g., EasyMesh), the non-AP STA or non-AP MLD may also request information about non-AP STAs associated with other APs of the multi-AP network (independent or affiliated with the AP MLD) and any non-associated non-AP STAs known to the AP.
[0172] The format and content of the protected client discovery query frame and the protected client discovery response frame are the same as those of the first embodiment and Fig.18 and Figure 21-27 The same as those shown in. Provide a list of requested APs in the BSSID list field. When a client discovery query frame is received by an AP or AP MLD within a multi-AP network, the AP or AP MLD can provide non-AP STA and non-AP MLD information associated with other APs or AP MLDs in a multi-AP network.
[0173] In the following paragraphs, a third embodiment of the present disclosure is described, in which an enhanced client discovery procedure is performed using a data frame.
[0174] The AP may not support enhanced client discovery. In this case, the non-AP STA (or non-AP MLD) can directly request information from the target non-AP STA (or non-AP MLD) (similar to level 2 client discovery) by exchanging client discovery frames and authorization verification frames, encapsulating them in enhanced client discovery Ethernet type 89-0d data frames, and having the commonly associated AP forward them to the target non-AP STA. By encapsulating the discovery frame and the authorization verification frame in the data frame, the AP does not need to decode the message. The decoding of the frame will be performed by the target non-AP STA (or non-AP MLD). This process may be referred to as tunnel discovery or tunnel enhanced d client discovery.
[0175] Fig.31 A schematic diagram 3100 illustrating a tunnel-enhanced client discovery procedure according to a third embodiment of the present disclosure is shown. Fig.32 A flowchart 3200 is shown illustrating a tunnel-enhanced client discovery procedure between non-AP STA1 and non-AP STA2 according to a third embodiment of the present disclosure. Non-AP STA1 may first send a protected client discovery query frame to request information of another non-AP STA (e.g., non-AP STA2) via an AP. The protected client discovery query frame has a level field set to 2 (or a client discovery mode field set to 1) to indicate a level 2 discovery query, a client ID set to the ID of non-AP STA2, and a neighbor information request field set to 1 to indicate that information of neighboring clients of the indicated STA (i.e., STAs and APs within a radio range of the indicated STA) is also requested. According to the third embodiment, the client discovery query frame is encapsulated in a data frame. The AP receiving the data frame addressed to non-AP STA2 will directly forward the data frame including the client discovery query frame to non-AP STA2.
[0176] In one example, additional authorization verification may be triggered by non-AP STA2. Non-AP STA2 may then send an authorization verification request frame back to non-AP STA1 via the AP to request verification information or authorization proof (e.g., a shared password, etc.). In response, non-AP STA1 sends an authorization verification response frame to non-AP STA2 via the AP to provide verification information or authorization proof (e.g., a password) that it is authorized to perform enhanced client discovery. Similarly, the authorization verification frame is encapsulated in a data frame, and the AP receiving the data frame forwards it to the visited address and facilitates the exchange of verification frames accordingly.
[0177] If the authorization verification succeeds, the steps shown in block 3202 are executed; otherwise, the steps shown in block 3204 are executed. Specifically, if the authorization verification succeeds, the non-AP STA2 then collects information of its neighboring STAs and APs based on the discovery criteria provided in the client discovery query frame, and sends a protected client discovery response frame including detailed information of the non-AP STA2, its neighboring STAs, and the AP to the non-AP STA1 via the AP.
[0178] If the authorization verification is unsuccessful, the non-AP STA2 does not provide information about itself and its neighboring devices, but sends back a protected client discovery response frame having a status field indicating that the authorization verification is unsuccessful to the non-AP STA1 via the AP.
[0179] A similar frame exchange sequence may be performed between two non-AP MLDs to implement the same enhanced client discovery procedure, except that the associated AP-MLD may forward the frame to the peer non-AP MLD on any available link (i.e., links other than the original link used by the sending non-AP MLD).
[0180] A new Ethertype 89-0d payload type is defined to encapsulate enhanced client discovery frames. Fig.33AAn example format of an enhanced client discovery Ethernet type 89-0d data frame 3300 according to the third embodiment of the present disclosure is shown. The enhanced client discovery Ethernet type 89-0d data frame includes a frame control field, a duration field, three address fields (address field 1, address field 2, address field 3), a sequence control field, an address 4 field, a quality of service (QoS) control field, an HT control field, a frame body, and an FCS field. The frame control field, the duration field, the three address fields (address field 1, address field 2, address field 3), the sequence control field, the address field 4 field, the quality of service (QoS) control field, and the HT control field may be grouped into a MAC header. The address 3 (A3) field will be set according to the 802.11 source address (SA) and destination (DA). More specifically, when the data frame 3300 is sent by a non-AP STA, the A3 field is set to DA (the MAC address of the target non-AP STA), and when the data frame 3300 is sent by an AP, the A3 field is set to SA (the MAC address of the source non-AP STA).
[0181] The frame body includes a Logical Link Control (LLC) field, a SNAP field set to "Ether Type under 89-0d type", a Payload Type field, and a Payload field 3202. According to Table 2, the Payload Type field is set to "Enhanced Client Discovery", such as a Payload Type field value of 5.
[0182] Table 2 shows the payload type field values corresponding to various protocols.
[0183] Payload Type Protocol Name 1 Remote Request / Response 2 TDLS 3 FST(Fast Session Transfer) 4 RLQP (Registered Location Query Protocol) 5 Enhanced client discovery 6-255 reserve
[0184] When the client discovery frame is encapsulated in the enhanced client discovery Ethernet type 89-0d data frame, the frame body of the protected client discovery frame and the authorization verification frame are carried in the payload field of the Ethernet type 89-0d data frame.
[0185] Fig.33B It shows that according to the embodiment Fig.33A 33. The example content of the payload field 3302 is shown in FIG. The payload field in the frame body includes a protected client discovery query frame, a protected discovery response frame, an authorization verification request frame, and / or an authorization verification response frame.
[0186] In the following paragraphs, a fourth embodiment of the present disclosure is described, in which a higher layer protocol is used to perform an enhanced client discovery procedure.
[0187] Instead of using EtherType 89-0d data frames, higher layer protocols such as 1905 Topology Query / Response messages may be used to enhance client discovery. Fig.30The multi-AP deployment shown in (such as EasyMesh but not limited to EasyMesh) can be used as an example.
[0188] In a typical EasyMesh multi-AP deployment, an AP (especially an AP as part of a multi-AP controller) may already have access to information about all non-AP STAs associated with any AP in the AP as part of a multi-AP network, or even some non-AP STAs that are not associated with any AP in the AP.
[0189] To perform enhanced client discovery, a non-AP STA (associated or non-associated) or an AP sends a 1905 topology query message carrying a client discovery query type length value (TLV) to any AP in the AP that is part of a multi-AP network or to another non-AP STA to request information about the non-AP STA. An example format of a client discovery query TLV is shown in Table 3.
[0190] Upon receiving the Client Discovery Query TLV, the AP (or non-AP STA) provides requested information about the non-AP STA in a 1905 Topology Response message carrying a Client Discovery Response TLV. Table 4 shows an example format of a Client Discovery Response TLV.
[0191] In addition, the AP may send a 1905 Topology Query message carrying an Authorization Verification Request TLV to the non-AP STA to request verification information and verify whether the requesting non-AP STA is authorized to obtain information about other non-AP STAs. Table 4 shows an example format of the Authorization Verification Request TLV.
[0192] Upon receiving the Authorization Verification Request TLV from its associated AP or AP MLD, the non-AP STA may send a 1905 Topology Query message carrying an Authorization Verification Response TLV that carries verification information (e.g., a shared password) in the format requested by the AP. Table 5 shows an example format of the Authorization Verification Response TLV.
[0193] Fig.34An example configuration of a communication device 3400 is shown. According to various embodiments of the present disclosure, the communication device 3400 is implemented as a non-AP STA for enhanced client discovery. The communication device 3400 includes a power supply 3402, a memory 3404, a central processing unit (CPU) 3406 including at least one processor, a secondary memory 3408, a wired interface (I / F) 3410, and a wireless I / F 3412. The memory 3404 may be a non-transitory computer-readable storage medium having data representing instructions stored therein, which may be executed by at least one processor of the CPU 3406 to communicate with the wireless I / F 3412 to perform an enhanced client discovery procedure according to various embodiments described in the present disclosure. The wireless I / F 3412 includes a MAC layer 3414 and a PHY layer 3416. The PHY layer 3416 is connected to a radio transmitter (not shown), a radio receiver (not shown), and an antenna 3422 for sending / receiving signals to / from other communication devices (e.g., STAs). Alternatively, the communication device 3400 may transmit / receive signals to / from other communication devices (eg, STA) via the wired I / F 3410. The secondary memory 3408 may store the AID of the associated communication device.
[0194] The MAC layer 3414 also includes an enhanced client discovery module 3418, and stores information of neighboring non-AP STAs 3420. The communication device 3400 may be a non-AP STA, and the enhanced client discovery module 3418 may generate and process frames (e.g., client discovery query / response frames, authorization verification request / response frames) to perform the enhanced client discovery procedure according to the various embodiments described above. The communication device 3400 may be a sensing responder, and the enhanced client discovery module 3418 may generate and process frames (e.g., client discovery query / response frames, authorization verification request / response frames) and provide information of its neighboring non-AP STAs 3420 in response to frame reception from other communication devices.
[0195] Fig.35Another example configuration of the communication device 3500 is shown. According to the present disclosure, the communication device 3500 is implemented as an AP for enhancing client discovery. The communication device 3500 includes a power supply 3502, a memory 3504, a central processing unit (CPU) 3506 including at least one processor, an auxiliary memory 3508, a wired I / F 3510, and a wireless I / F 3512. The memory 3504 can be a non-transitory computer-readable storage medium that stores data representing instructions that can be executed by at least one processor of the CPU 3506 to communicate with the wireless I / F 3512 to perform multiple generations of random access according to various embodiments in the present disclosure. The wireless I / F 3512 includes a MAC layer 3514 and a PHY layer 3516. The PHY layer 3516 is connected to a radio transmitter (not shown) for sending / receiving signals to / from other (basic) communication devices, a radio receiver (not shown), and an antenna 3522. Alternatively, the communication device 3500 may transmit / receive signals to / from other communication devices via the wired I / F 3510 .
[0196] The MAC layer 3514 also includes an enhanced client discovery module 3518, and stores information of associated non-AP STA 3520. The enhanced client discovery module 3518 may generate and process frames (e.g., client discovery query / response frames, authorization verification request / response frames), and utilize the information of associated non-AP STA 3520 to perform the enhanced client discovery procedure according to the various embodiments described above.
[0197] As described above, embodiments of the present disclosure provide an advanced communication system, a communication method, and a communication device for an enhanced client discovery procedure in a MIMO WLAN network.
[0198] The present disclosure can be implemented by software, hardware or software in collaboration with hardware. Each functional block used in the description of each of the above embodiments can be implemented in part or in whole by large-scale integration (LSI) such as integrated circuits, and each process described in each embodiment can be controlled in part or in whole by the same LSI or a combination of LSIs. LSI can be formed as a chip alone, or a chip can be formed to include a part or all of the functional blocks. LSI can include data input and output coupled thereto. According to the difference in integration, the LSI here can be referred to as IC, system LSI, super LSI or ultra LSI. However, the technology for implementing integrated circuits is not limited to LSI, and can be implemented by using a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (field programmable gate array) that can be programmed after LSI manufacturing or a reconfigurable processor that can reconfigure the connection and setting of the circuit unit arranged inside the LSI can be used. The present disclosure can be implemented as digital processing or analog processing. If, as a result of the advancement of semiconductor technology or other derivative technologies, future integrated circuit technology replaces LSI, future integrated circuit technology can be used to integrate functional blocks. Biotechnology can also be applied.
[0199] The present disclosure may be implemented by any kind of equipment, device, or system having a communication function, which is referred to as a communication device.
[0200] Some non-limiting examples of such communication devices include phones (e.g., cellular (cell) phones, smart phones), tablets, personal computers (PCs) (e.g., laptops, desktops, netbooks), cameras (e.g., digital still / video cameras), digital players (digital audio / video players), wearable devices (e.g., wearable cameras, smart watches, tracking devices), game consoles, digital book readers, telemedicine / telemedicine (remote health and medicine) devices, and vehicles providing communication capabilities (e.g., cars, airplanes, ships), and various combinations thereof.
[0201] Communication devices are not limited to portable or movable, and may also include any kind of device, equipment, or system that is non-portable or fixed, such as smart home devices (e.g., appliances, lighting, smart meters, control panels), vending machines, and any other "things" in the network of the "Internet of Things (IoT)".
[0202] Communications may include exchanging data via, for example, cellular systems, wireless LAN systems, satellite systems, etc., and various combinations thereof.
[0203] The communication device may include a device such as a controller or a sensor that is coupled to the communication device that performs the communication functions described in the present disclosure. For example, the communication device may include a controller or a sensor that generates a control signal or a data signal used by the communication device that performs the communication functions of the communication device.
[0204] The communication devices may also include infrastructure such as base stations, access points, and any other devices, equipment, or systems that communicate with or control devices such as those in the above non-limiting examples.
[0205] It shall be understood that, although some properties of the various embodiments have been described with reference to an apparatus, corresponding properties also apply to the method of the various embodiments, and vice versa.
[0206] It will be appreciated by those skilled in the art that many changes and / or modifications may be made to the disclosure shown in the specific embodiments without departing from the spirit or scope of the disclosure as broadly described. Therefore, the present embodiments are to be considered in all aspects as illustrative and not restrictive.
[0207] Table 3 shows an example format of a client discovery query TLV for enhancing client discovery according to the fourth embodiment of the present disclosure.
[0208]
[0209] Table 4 shows an example format of a client discovery response TLV for enhancing client discovery according to the fourth embodiment of the present disclosure.
[0210]
[0211] Table 5 shows an example format of an authorization verification request TLV for enhancing client discovery according to the fourth embodiment of the present disclosure.
[0212]
[0213] Table 6 shows an example format of an authorization verification response TLV for enhancing client discovery according to the fourth embodiment of the present disclosure.
[0214]
Claims
1. A first communication device, comprising: Circuit,generates the first frame; The transmitter sends the first frame to the second communication device to request information of the third communication device.
2. The first communication device according to claim 1, wherein: The information includes information of one or more neighboring communication devices of the third communication device.
3. The first communication device according to claim 1, wherein: The information includes at least one of a medium access control (MAC) address, an association identifier (AID), an identifier of an associated access point (AP), supported capabilities, a physical (PHY) version, an operating channel width, and a location of any one or both of the third communication device and a neighboring communication device of the third communication device.
4. The first communication device according to claim 1, wherein: The first frame includes a field indicating a condition for selecting the third communication device, and the condition is at least one of a supported capability, a PHY version, an operating channel width, a link quality indicator, and an associated AP of the third communication device.
5. The first communication device according to claim 1, wherein: The third communication device is one of a plurality of third communication devices, and the circuit further generates a second frame, and the transmitter transmits the second frame to request information of the plurality of third communication devices.
6. The first communication device according to claim 5, wherein: The request of the first frame and / or the request of the second frame are encapsulated in a data frame.
7. The first communication device according to claim 6, wherein: The data frame includes an Ethernet type 89-0d data frame.
8. The first communication device according to claim 1, further comprising: The receiver receives a verification request frame requesting verification information, wherein the verification information indicates that the first communication device is authorized to obtain information of the third communication device, wherein the circuit processes the verification request frame and generates a verification response frame including the verification information, and the transmitter sends the verification response frame.
9. The first communication device according to claim 1, wherein: The first communication device and the third communication device are non-access point (non-AP) stations, and the second communication device is an access point.
10. The first communication device according to claim 9, wherein: The first communication device and the third communication device are not associated with the second communication device.
11. The first communication device according to claim 9, wherein: The first communication device is attached to a non-AP multi-link device (MLD), and the second communication device is attached to an AP MLD.
12. A second communication device, comprising: a receiver, receiving a request frame from a first communication device requesting information of a third communication device; circuitry to process the request frame and generate a response frame including the information; and A transmitter sends the response frame to the first communication device.
13. The second communication device according to claim 12, wherein: The information includes information of one or more neighboring communication devices of the third communication device.
14. The second communication device according to claim 13, wherein: The request frame further requests the third communication device to collect and report information of the one or more neighboring communication devices, and the circuit generates a response frame including the information of the one or more neighboring communication devices collected and reported by the third communication device.
15. The second communication device according to claim 12, wherein: The circuit also generates an authentication request frame to request authentication information indicating that the first communication device is authorized to obtain information of the third communication device, wherein the receiver also receives an authentication response frame including the authentication information from the first communication device.
16. The second communication device according to claim 12, wherein: The first communication device and the third communication device are non-access point (non-AP) stations, and the second communication device is an access point.
17. The second communication device according to claim 16, wherein: The first communication device and the third communication device are not associated with the second communication device.
18. The second communication device according to claim 16, wherein: The first communication device is attached to a non-AP MLD, and the second communication device is attached to an AP MLD.
19. A communication method implemented by a first communication device, comprising: Generate the first frame; and The first frame is sent to the second communication device to request information of the third communication device.
20. A communication method implemented by a second communication device, comprising: receiving, from the first communication device, a request frame requesting information of the third communication device; Processing the request frame; generating a response frame including the information; and The response frame is sent to the first communication device.
