Perception method and communication device

Abstract

The embodiment of the invention is applied to a wireless local area network system supporting an IEEE (Institute of Electrical and Electronic Engineers) 802.11 ax next generation Wi-Fi protocol, such as 802.11 be, Wi-Fi 7 or EHT, and then 802.11 series protocols such as 802.11 be next generation, Wi-Fi 8, UHR, Wi-Fi AI and the like, and can also be applied to a UWB-based wireless personal local area network system, a sensing system and the like. The embodiment of the invention provides a sensing method and a communication device, in the method, a first AP can send a first request frame to one or more APs, the first request frame is used for the AP to request multiple APs to perform joint sensing, and the method enables the first AP to utilize sensing results of other APs to perform joint sensing. Therefore, the situation that the sensing task fails due to the fact that the sensing result is unavailable when the first AP performs sensing independently is avoided.

Description

Technical Field

[0001] The present application relates to the field of wireless communications, and in particular, to a sensing method and a communication device. Background Art

[0002] When an access point (AP) senses a target in an overlapping basic service set (OBSS), it may be interfered by other devices in the space, such as co-frequency or adjacent frequency interference, and because the sensed target is at the edge of the basic service set (BSS), the perception performance is poor, which will lead to large errors in the measurement results. However, the AP will continue to perform perception measurements in the time window used for perception measurements as long as the communication link is not interrupted. Only after the AP obtains the perception measurement report and performs signal processing through a certain algorithm, can it know that there is a large error in the perception measurement result, and can only abandon the measurement result, causing the perception task to fail. Therefore, the AP can request multiple other APs to perform perception measurements on its behalf, that is, multiple APs perform joint perception. When the perception results of one AP are not available, the perception results of other APs can be used.

[0003] However, the current Sensing by Proxy (SBP) only allows non-access point stations (non-AP STA) to request AP to perform sensing measurements on their behalf. That is, the existing SBP can only be initiated by STA and does not support AP requesting AP proxy sensing. Therefore, based on the current SBP, it is impossible to implement a multi-AP joint proxy sensing solution. Summary of the invention

[0004] The present application provides a perception method and a communication device, which can avoid the situation where the perception task fails due to the unavailability of the perception result when the AP perceives alone.

[0005] In a first aspect, a sensing method is provided, which can be executed by a communication device, or can also be executed by a component (such as a chip or circuit) of the communication device, without limitation. For ease of description, the following description is based on an example of execution by a first AP.

[0006] The method includes: a first AP sends first request frames corresponding to N APs respectively to N APs, the first request frames are used for the AP to initiate a multi-AP joint proxy perception request, and N is a positive integer; the first AP receives first response frames from the N APs respectively, and the first response frames are used to indicate acceptance of the multi-AP joint proxy perception request.

[0007] In the above technical solution, the first AP can send a first request frame to N APs to request one or more APs to perform joint perception. This method enables the first AP to utilize the perception results of one or more APs, thereby avoiding the failure of the perception task due to the unavailability of the perception results when the first AP perceives alone.

[0008] It should be noted that the multi-AP joint proxy perception in this scheme may be multiple APs jointly perceiving the same target, or the multi-AP joint proxy perception may be respectively perceiving different parts of the same target, and the first AP may obtain the perception result of the entire target based on the perception results of different APs, or the multi-AP joint proxy perception may be a joint perception of the environment. This application does not specifically limit the perception target of the multi-AP joint perception.

[0009] In certain implementations of the first aspect, the first request frame includes first information, the first information indicating that the first request frame is a request frame for the AP to initiate multi-AP joint proxy perception, and the first information is carried in the first request frame. Included in the public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0010] It can be understood that in this technical solution, for the device that receives the first request frame, it can be determined based on the first information in the first request frame that the device type of the device that initiates the multi-AP joint proxy awareness request is an AP.

[0011] In some implementations of the first aspect, the first request frame includes second information, the second information includes parameters required for the second AP to perform multi-AP joint proxy perception, and the second AP is an AP that receives the first request frame.

[0012] In certain implementations of the first aspect, the parameters required for the second AP to perform multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP collaborative transmission type, trigger-based detection phase type, the required number of perception response sites STA, and whether the number of perception response STAs is required.

[0013] In certain implementations of the first aspect, the first response frame includes third information, the third information indicating that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP, and the third information is carried in the first response frame. Included in the public function / protected dual public function Public Action / Protected Dual of PublicAction field.

[0014] In certain implementations of the first aspect, the method further includes: the first AP receives a second request frame from the first station STA, the second request frame being used by the STA to initiate a multi-AP joint proxy awareness request; the first AP sends a second response frame to the first STA, the second response frame indicating acceptance of the multi-AP joint proxy awareness request.

[0015] It should be understood that the first request frame sent by the first AP to the N APs is sent based on the received second request frame.

[0016] In the above technical solution, the first STA can initiate a multi-AP joint proxy perception request to the first AP to instruct the first AP to initiate a multi-AP joint proxy perception request to other APs. This method enables the first AP to utilize the perception results of one or more APs, thereby avoiding the failure of the perception task when the first AP alone acts as a proxy for the first STA because the perception results are unavailable.

[0017] In certain implementations of the first aspect, the second request frame includes fourth information, the fourth information indicating that the second request frame is a request frame for STA to initiate multi-AP joint proxy perception, and the fourth information is carried in the second request frame. Included in the public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0018] It can be understood that in this technical solution, for the device that receives the second request frame, the device type of the device that initiates the multi-AP joint proxy perception request can be determined based on the fourth information in the second request frame as STA.

[0019] In some implementations of the first aspect, the second request frame includes fifth information, and the fifth information includes parameters required for multi-AP joint proxy perception.

[0020] In some implementations of the first aspect, the parameters required for multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP cooperative transmission type, trigger-based detection phase type, the number of APs required to establish multi-AP joint proxy perception, the number of APs required is required, whether the AP receiving the second request frame needs to perform perception measurement, the number of required perception response STAs, the number of perception response STAs is required, whether the AP receiving the second request frame is recommended for joint proxy perception, whether different multi-AP joint proxy perception parameters are provided for the recommended AP, and whether the first STA needs to participate in the perception measurement.

[0021] In some implementations of the first aspect, when the fifth information indicates that different perception parameters are provided for the recommended APs, the second request frame includes sixth information, and the sixth information includes the perception parameters allocated to each AP in the recommended APs.

[0022] In certain implementations of the first aspect, the sixth information includes one or more of the following parameters allocated to each AP: measurement parameters for perception, the number of required perception response STAs, whether the number of perception response STAs is mandatory, and the type of trigger-based detection phase.

[0023] In certain implementations of the first aspect, the second response frame includes seventh information, the seventh information indicating that the second response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the STA, and the seventh information is carried in the second response frame. Included in the public function / protected dual public function Public Action / Protected Dual of PublicAction field.

[0024] In certain implementations of the first aspect, the method further includes: the first AP triggering N APs to perform multi-AP joint perception measurement.

[0025] In certain implementations of the first aspect, if the second AP among the N APs is not the last AP among the N APs to be triggered to perform perception measurement, the first AP triggers the N APs to perform multi-AP joint perception measurement, including: the first AP determines that the second AP completes the perception measurement; the first AP sends a first inquiry trigger frame to a third AP among the N APs, the first inquiry trigger frame is used to trigger the third AP to perform perception measurement, the third AP is any AP among the N APs that has not been triggered to perform perception measurement; the first AP receives a first inquiry response frame from the third AP.

[0026] In the above technical solution, it can be regarded as the first AP triggering N APs to perform perception measurement in sequence. For example, after AP#1 among the N APs currently triggered by the first AP completes the perception measurement, the first AP sends an inquiry trigger frame to AP#2 among the N APs to trigger AP#2 to perform perception measurement. After AP#2 completes the perception measurement, the first AP continues to send an inquiry trigger frame to AP#3 among the N APs to trigger AP#3 to perform perception measurement, until all APs among the N APs triggered by the first AP complete the perception measurement.

[0027] For example, in this triggered measurement method, the first AP can control the perception measurements of multiple APs to be performed sequentially at very short time intervals. For example, this time length is generally in microseconds. For example, this time interval can be a SIFS interval. At this time, the perception result of each AP can be considered to be soft-synchronized. When the perception result of the first AP is unavailable due to interference or weak signal strength at the BSS edge, the perception results of N APs at the "same moment" can be used to avoid failure of the perception task.

[0028] In certain implementations of the first aspect, a first AP triggers N APs to perform multi-AP joint perception measurement, including: the first AP sends a second inquiry trigger frame to the N APs, where the second inquiry trigger frame is used to trigger the N APs to perform perception measurement based on their respective corresponding perception measurement start time and duration; the first AP receives second inquiry response frames from the N APs, where the second inquiry response frames indicate that the APs confirm to perform perception measurement based on the corresponding perception measurement start time and duration.

[0029] In the above technical solution, it can be seen that the first AP can allocate a perception measurement start time and duration for each of the N APs, and the N APs perform perception measurements based on their own perception measurement start time and duration.

[0030] In certain implementations of the first aspect, the second inquiry trigger frame includes eighth information, where the eighth information includes a start time and a duration for the N APs to perform perception measurements.

[0031] In certain implementations of the first aspect, the ninth information in the first inquiry trigger frame is used to trigger the AP that receives the first inquiry trigger frame to perform multi-AP joint perception measurement, and the ninth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based public information Trigger Dependent Comment Info field of the public information field included in the first inquiry trigger frame.

[0032] In some implementations of the first aspect, the first inquiry trigger frame includes tenth information, and the tenth information instructs the third AP to start performing perception measurement.

[0033] In certain implementations of the first aspect, the eleventh information in the second inquiry trigger frame is used to trigger N APs to perform multi-AP joint perception measurement, and the eleventh information is carried in the perception trigger subtype Sensing TriggerSubtype field of the trigger-based public information Trigger Dependent Comment Info field of the common information field included in the second inquiry trigger frame.

[0034] In some implementations of the first aspect, the second inquiry trigger frame includes twelfth information, where the twelfth information indicates that the N APs perform perception measurement based on their respective corresponding perception measurement start times and durations.

[0035] In certain implementations of the first aspect, the method further includes: the first AP sends a first report trigger frame to N APs, the first report trigger frame is used to trigger the N APs to report measurement results of multi-AP joint perception; the first AP receives measurement results from the N APs.

[0036] In certain implementations of the first aspect, the method further includes: the first AP sending measurement results of N APs to the first STA.

[0037] In certain implementations of the first aspect, the thirteenth information in the first report trigger frame is used to trigger the AP receiving the first report trigger frame to report the measurement results of multiple AP joint perception, and the thirteenth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based public information Trigger Dependent Comment Info field of the common information field included in the first report trigger frame.

[0038] In a second aspect, a communication method is provided, which can be executed by a communication device, or can also be executed by a component (such as a chip or circuit) of the communication device, without limitation. For ease of description, the following description is based on an example of execution by a second AP.

[0039] The method includes: a second AP receives a first request frame from a first AP, the first request frame is used for the AP to initiate a multi-AP joint proxy perception request, the second AP is any AP among N APs for which the first AP requests multi-AP joint proxy perception, N is an integer; the second AP sends a first response frame to the first AP, the first response frame is used to indicate acceptance of the multi-AP joint proxy perception request.

[0040] For the beneficial effects of the second aspect, please refer to the description of the first aspect and will not be repeated here.

[0041] In some implementations of the second aspect, the first request frame includes first information, the first information indicating that the first request frame is a request frame for the AP to initiate multi-AP joint proxy perception, and the first information is carried in the first request frame. Included in the public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0042] In some implementations of the second aspect, the first request frame includes second information, and the second information includes parameters required for the second AP to perform multi-AP joint proxy perception.

[0043] In some implementations of the second aspect, the parameters required for the second AP to perform multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP collaborative transmission type, trigger-based detection phase type, the required number of perception response sites STA, and whether the number of perception response STAs is required.

[0044] In certain implementations of the second aspect, the first response frame includes third information, the third information indicating that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP, and the third information is carried in the first response frame. Included in the public function / protected dual public function Public Action / Protected Dual of PublicAction field.

[0045] In certain implementations of the second aspect, the method further includes: the second AP performs multi-AP joint sensing measurement under the triggering of the first AP.

[0046] In certain implementations of the second aspect, the second AP performs multi-AP joint perception measurement under the triggering of the first AP, including: the second AP receives a third inquiry trigger frame from the first AP, the third inquiry trigger frame is used to trigger the second AP to perform perception measurement; the second AP sends a third inquiry response frame to the first AP.

[0047] In certain implementations of the second aspect, a first AP triggers N APs to perform multi-AP joint perception measurement, including: a second AP receives a second inquiry trigger frame from the first AP, the second inquiry trigger frame is used to trigger the N APs to perform perception measurement based on their respective corresponding perception measurement start time and duration; the second AP sends a second inquiry response frame to the first AP, the second inquiry response frame indicates that the second AP confirms to perform perception measurement based on the corresponding perception measurement start time and duration.

[0048] In certain implementations of the second aspect, the second inquiry trigger frame includes eighth information, where the eighth information includes a start time and a duration for the N APs to perform perception measurements.

[0049] In certain implementations of the second aspect, the fourteenth information in the third inquiry trigger frame is used to trigger the second AP to perform multi-AP joint perception measurement, and the fourteenth information is carried in the perception trigger subtype Sensing TriggerSubtype field of the trigger-based public information Trigger Dependent Comment Info field of the common information field included in the first inquiry trigger frame.

[0050] In some implementations of the second aspect, the third inquiry trigger frame includes fifteenth information, and the fifteenth information instructs the second AP to start performing perception measurement.

[0051] In certain implementations of the second aspect, the eleventh information in the second inquiry trigger frame is used to trigger N APs to perform multi-AP joint perception measurement, and the eleventh information is carried in the perception trigger subtype Sensing TriggerSubtype field of the trigger-based public information Trigger Dependent Comment Info field of the common information field included in the second inquiry trigger frame.

[0052] In some implementations of the second aspect, the second inquiry trigger frame includes twelfth information, where the twelfth information indicates that the N APs perform perception measurement based on their respective corresponding perception measurement start time and duration.

[0053] In certain implementations of the second aspect, the method further includes: the second AP receives a first report trigger frame from the first AP, the first report trigger frame is used to trigger the second AP to report a measurement result of multi-AP joint perception; and the second AP sends the measurement result to the first AP.

[0054] In certain implementations of the second aspect, the thirteenth information in the first report trigger frame is used to trigger the reception of the second AP to report the measurement results of the multi-AP joint perception, and the thirteenth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based public information Trigger Dependent Comment Info field of the common information field included in the first report trigger frame.

[0055] In a third aspect, a communication method is provided, which can be executed by a communication device, or can also be executed by a component (such as a chip or circuit) of the communication device, without limitation. For ease of description, the following is an example of execution by a first STA.

[0056] The method includes: a first STA sends a second request frame to a first access point AP, the second request frame is used for the STA to initiate a multi-AP joint proxy perception request; the first STA receives a second response frame from the first AP, the second response frame indicates acceptance of the multi-AP joint proxy perception request.

[0057] For the beneficial effects of the third aspect, please refer to the description of the first aspect and will not be repeated here.

[0058] In some implementations of the third aspect, the second request frame includes fourth information, the fourth information indicating that the second request frame is a request frame for STA to initiate multi-AP joint proxy perception, and the fourth information is carried in the second request frame. Included in the public function / protected dual public function Public Action / Protected Dual of Public Action field.

[0059] In some implementations of the third aspect, the second request frame includes fifth information, and the fifth information includes parameters required for multi-AP joint proxy perception.

[0060] In certain implementations of the third aspect, the parameters required for multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP cooperative transmission type, trigger-based detection phase type, the number of APs required to establish multi-AP joint proxy perception, the number of APs required is required, whether the AP receiving the second request frame needs to perform perception measurement, the number of perception response STAs required, whether the number of perception response STAs is required, whether the AP receiving the second request frame is recommended to perform joint proxy perception, whether different multi-AP joint proxy perception parameters are provided for the recommended AP, and whether the first STA needs to participate in the perception measurement.

[0061] In certain implementations of the third aspect, when the fifth information indicates that different perception parameters are provided for the recommended APs, the second request frame includes sixth information, and the sixth information includes the perception parameters allocated to each AP in the recommended APs.

[0062] In certain implementations of the third aspect, the sixth information includes one or more of the following parameters allocated to each AP: measurement parameters for perception, the number of required perception response STAs, whether the number of perception response STAs is mandatory, and the type of trigger-based detection phase.

[0063] In certain implementations of the third aspect, the second response frame includes seventh information, where the seventh information indicates that the second response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the STA, and the seventh information is carried in the second response frame. Included in the public function / protected dual public function Public Action / Protected Dual of PublicAction field.

[0064] In certain implementations of the third aspect, the method further includes: the first STA receiving a measurement result of multi-AP joint perception from the first AP.

[0065] In a fourth aspect, a communication device is provided, which is used to execute the method provided in any one of the first to third aspects. Specifically, the communication device may include a unit and / or module for executing the method provided in the first aspect or any one of the above-mentioned implementations of the first aspect, or include a unit and / or module for executing the method provided in the second aspect or any one of the above-mentioned implementations of the second aspect, or include a unit and / or module for executing the method provided in the third aspect or any one of the above-mentioned implementations of the third aspect, such as a processing unit and / or a transceiver unit.

[0066] In one implementation, the communication device is a device (e.g., a first station, a first access point, or a second access point). When the communication device is a device, the transceiver unit may be a transceiver, or an input / output interface; the processing unit may be at least one processor. Optionally, the transceiver may be a transceiver circuit. Optionally, the input / output interface may be an input / output circuit.

[0067] In another implementation, the communication device is a chip, a chip system or a circuit used in a device (such as a first station, a first access point, or a second access point). When the communication device is a chip, a chip system or a circuit used in a device, the transceiver unit may be an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, the chip system or the circuit; the processing unit may be at least one processor, a processing circuit or a logic circuit.

[0068] In a fifth aspect, a communication device is provided, comprising: a memory for storing programs; and at least one processor for executing computer programs or instructions stored in the memory to execute the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or to execute the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or to execute the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0069] In one implementation, the communication apparatus is a device (eg, a first station, or a first access point, or a second access point).

[0070] In another implementation, the apparatus is a chip, a chip system, or a circuit used in a device (such as a first station, a first access point, or a second access point).

[0071] In a sixth aspect, the present application provides a processor for executing the methods provided in the above aspects.

[0072] For the operations such as sending and acquiring / receiving involved in the processor, unless otherwise specified, or unless they conflict with their actual function or internal logic in the relevant description, they can be understood as operations such as processor output, reception, input, etc., or as sending and receiving operations performed by the radio frequency circuit and antenna, and this application does not limit this.

[0073] In the seventh aspect, a computer-readable storage medium is provided, which stores a program code for execution by a device, wherein the program code includes instructions for executing the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or includes instructions for executing the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or includes instructions for executing the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0074] In an eighth aspect, a computer program product comprising instructions is provided. When the computer program product runs on a computer, it enables the computer to execute the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or enables the computer to execute the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or enables the computer to execute the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0075] In the ninth aspect, a chip is provided, the chip including a processor and a communication interface, the processor reads instructions stored in a memory through the communication interface, executes the method provided by the first aspect or any one of the above-mentioned implementations of the first aspect, or executes the method provided by the second aspect or any one of the above-mentioned implementations of the second aspect, or executes the method provided by the third aspect or any one of the above-mentioned implementations of the third aspect.

[0076] Optionally, as an implementation method, the chip also includes a memory, in which a computer program or instruction is stored, and the processor is used to execute the computer program or instruction stored in the memory. When the computer program or instruction is executed, the processor is used to execute the method provided by the first aspect or any one of the above-mentioned implementation methods of the first aspect, or execute the method provided by the second aspect or any one of the above-mentioned implementation methods of the second aspect, or execute the method provided by the third aspect or any one of the above-mentioned implementation methods of the third aspect.

[0077] In a tenth aspect, a communication system is provided, comprising the first station, the first access point and the second access point mentioned above. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] Figure 1 It is a schematic diagram of a network architecture of a wireless local area network applicable to an embodiment of the present application.

[0079] Figure 2 This is a schematic diagram of the WLAN Sensing process defined by IEEE 802.11bf.

[0080] Figure 3 is a schematic diagram of the trigger-based perception measurement exchange process.

[0081] Figure 4 The figure is a schematic diagram of TB Sensing measurement exchange between AP and STA.

[0082] Figure 5 It is a flowchart of SBP.

[0083] Figure 6 It is a schematic flow chart of a perception method provided by the present application.

[0084] Figure 7 This is a schematic diagram of a possible frame structure of a first request frame proposed in this application.

[0085] Figure 8 It is a structural diagram of the Co-Sensing Parameters Control field in the first request frame proposed in this application.

[0086] Fig. 9 It is a schematic diagram of a possible frame structure of a first response frame proposed in this application.

[0087] Fig.10 This is a schematic diagram of a possible frame structure of a second request frame proposed in this application.

[0088] Fig.11 It is a schematic diagram of the structure of the Co-SBP Parameters Control field in the second request frame proposed in this application.

[0089] Fig.12 It is a schematic diagram of the structure of the MAP Parameters Control field in the second request frame proposed in this application.

[0090] Fig.13 It is a schematic diagram of a possible frame structure of a second response frame proposed in this application.

[0091] Fig.14 Schematic diagram of the multi-AP joint perception process corresponding to scenario one.

[0092] Fig.15 Schematic diagram of the multi-AP joint perception process corresponding to scenario 2.

[0093] Fig.16The diagram is a schematic diagram of joint sensing performed by multiple APs based on implementation method one.

[0094] Fig.17 This is a schematic diagram of joint sensing by multiple APs based on implementation method 2.

[0095] Fig.18 It is a schematic diagram of a possible frame structure of a Co-SBP Polling Trigger frame proposed in this application.

[0096] Fig.19 It is a schematic diagram of the structure of the User Info List field in the Co-SBP Polling Trigger frame proposed in this application.

[0097] Fig. 20 It is a schematic block diagram of a communication device 200 provided in an embodiment of the present application.

[0098] Fig.21 A schematic block diagram of a communication device 300 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0099] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0100] The embodiments of the present application can be applied to a wireless local area network (WLAN). The current standard adopted by WLAN is the Institute of Electrical and Electronics Engineers (IEEE) 802.11 series. A WLAN may include multiple basic service sets (BSSs). The network nodes in the BSSs are access points (APs) and non-access point stations (non-AP STAs) (hereinafter referred to as STAs).

[0101] Figure 1 Schematic diagram of the network architecture of the wireless local area network applicable to the embodiment of the present application. Figure 1 As shown in (a) in FIG. 1 , a BSS may include an AP and one or more STAs associated with the AP. The network architecture of a wireless LAN may also include multiple BSSs, such as Figure 1As shown in (b), the figure shows two BSSs, which partially overlap each other, namely OBSS. Among them, BSS#1 includes AP#1, STA11, STA12 and STA13, and BSS#2 includes AP#2, STA21, STA22 and STA23. STA11, STA12, STA22, and STA23 are the overlapping parts of the two BSSs. Each BSS consists of an AP and multiple STAs. Within a BSS, data can be transmitted between the AP and each STA. AP#1 and AP#2 can also communicate with each other.

[0102] Among them, the access point can be the access point for the terminal (for example, mobile phone) to enter the wired (or wireless) network. It is mainly deployed in homes, buildings and parks, with a typical coverage radius of tens to hundreds of meters. Of course, it can also be deployed outdoors. The access point is equivalent to a bridge connecting the wired network and the wireless network. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet.

[0103] Specifically, the AP may be a terminal or network device with a Wi-Fi chip, and the network device may be a server, a router, a switch, a bridge, a computer, a mobile phone, a relay station, a vehicle-mounted device, a wearable device, a network device in a 5G network, and a network device in a future 6G network or a network device in a public land mobile network (PLMN), etc., and the embodiments of the present application are not limited thereto. The access point may be a device that supports the Wi-Fi standard. For example, the access point may also support one or more standards of the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family, such as 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11ad, 802.11ay, etc.

[0104] STA can be a wireless communication chip, a wireless sensor or a wireless communication terminal, etc., and can also be called a user, user equipment (UE), an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. STA can be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, an Internet of Things device, a wearable device, a terminal device in a 5G network, a terminal device in a future 6G network or a terminal device in a PLMN, etc., and the embodiments of the present application are not limited to this. STA can be a device that supports the WLAN standard. For example, the STA may support one or more standards of the IEEE 802.11 family, such as 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac, 802.11ax, 802.11be, 802.11ad, and 802.11ay.

[0105] For example, STA can be a mobile phone, tablet computer, set-top box, smart TV, smart wearable device, vehicle communication equipment, computer, Internet of Things (IoT) node, sensor, smart home such as smart camera, smart remote control, smart water meter, smart electricity meter, and sensors in smart city.

[0106] The above-mentioned AP or STA may include a transmitter, a receiver, a memory, a processor, etc., wherein the transmitter and the receiver are respectively used for sending and receiving packet structures, the memory is used to store signaling information and store preset values ​​agreed in advance, etc., and the processor is used to parse signaling information, process related data, etc.

[0107] It should be understood that Figure 1 This is only an example and should not limit the network architecture of the wireless local area network to which the present application is applicable. For example, the network architecture may also include more BSSs, each BSS may also include more STAs, or an area where multiple BSSs overlap may also include more STAs, etc. The embodiments of the present application are not limited here.

[0108] WLAN sensing is a very promising technology that uses commonly deployed WLAN devices and specific WLAN signals to perform sensing tasks. WLAN signals can be reflected, refracted or penetrated on the surface of objects during propagation. By receiving WLAN signal echoes and performing appropriate signal processing through certain algorithms, the received WLAN signals can be used to perceive the surrounding environment, detect obstacles or monitor moving targets.

[0109] The IEEE 802.11bf protocol defines a unified WLAN Sensing process, which enables devices to obtain channel state information (CSI) between two or more devices, thereby realizing the perception of environmental information. IEEE 802.11bf covers the identified sensing scenarios by introducing different roles to the devices involved in sensing, which can be summarized as follows: Sensing initiator is the device that initiates WLAN Sensing; Sensing responder is the device that responds to WLAN Sensing initiated by the Sensing initiator; Sensing transmitter is the device that transmits null data packet (NDP); Sensing receiver is the device that receives NDP sent by the Sensing transmitter and performs sensing measurements based on NDP.

[0110] Figure 2This is a schematic diagram of the WLAN Sensing process defined by IEEE 802.11bf. In the sensing capabilities exchange phase, the sensing capabilities information of the devices are exchanged; in the sensing measurement session phase, the sensing initiator and the sensing responder negotiate the operation information of WLAN Sensing through request / response frames; in the sensing measurement exchange phase, the sensing transmitter and the sensing receiver perform sensing measurements through NDP frames; in the sensing measurement termination phase, the corresponding WLAN Sensing settings are terminated. In this case, the sensing measurement exchange is divided into trigger-based (TB) sensing measurement exchange (TB sensing measurement exchange) and non-triggered sensing measurement instance (Non-TB sensing measurement exchange). In this case, TB sensing measurement exchange is an AP-centric mechanism, with the AP acting as the sensing initiator and one or more STAs acting as the sensing responders.

[0111] Figure 3This is a schematic diagram of the triggered sensing measurement exchange process. The process includes a polling phase, a null data packet announcement (NDPA) sounding phase, a trigger frame (TF) sounding phase, and a reporting phase. It should be noted that the triggered sensing measurement exchange should not consist of only a reporting phase, nor should it consist of only an NDPA sounding phase, and should not consist of only a polling phase and a reporting phase. The process is described below. In the polling phase, the AP first sends a sensing polling trigger frame to one or more STAs that are expected to participate in the sensing measurement. The STA responds with a reflexive clear to send (CTS) (CTS-to-self) frame to confirm participation in subsequent sensing measurements. After polling, the AP will initiate NDPA sounding and / or TF sounding according to the role negotiated in the sensing measurement session. In the NDPA sounding phase, the AP acts as a sensing transmitter and sends a Sensing NDPA frame. After a short interframe space (SIFS) interval, the AP sends a SI2SR NDP frame. The STA acts as a sensing receiver and receives the SI2SR NDP frame for sensing measurement. In the TF sounding phase, the AP acts as a sensing receiver and sends a Sensing SR2SI Sounding Trigger frame to trigger one or more STAs that act as sensing transmitters to send SR2SI NDP frames to the AP so that the AP can perform sensing measurement. After the Sounding phase ends, the AP triggers the STA to return the sensing measurement results through the Sensing Report Trigger frame.

[0112] Figure 4 This is a schematic diagram of the TB Sensing measurement exchange between AP and STA. In the sensing window, AP and STA need to perform N sensing measurement exchange measurements. During this process, as long as the communication link is not disconnected, AP and STA1 will perform N sensing measurement exchange measurements. Then, the sensing measurement report is returned.

[0113] In one possible scenario, when the AP senses a target in the OBSS, it may be interfered by other devices in the space, such as co-frequency or adjacent frequency interference, and because the sensed target is at the edge of the BSS, the perception performance is poor, which will lead to large errors in the measurement results. However, during the Sensing measurement exchange process, as long as the communication link is not interrupted, the Sensing measurement exchange will continue. Only after obtaining the perception measurement report and performing signal processing through a certain algorithm can it be known that there is a large error in the perception measurement result. At this time, there will be multiple Sensing measurement exchange results that cannot be used, resulting in the abandonment of the measurement results, causing the perception task to fail.

[0114] Figure 5 This is a flow chart of SBP. SBP refers to the process of allowing STA to request AP to perform sensing measurements on its behalf. First, STA1, as the SBP initiator, requests AP, as the SBP responder, to perform SBP through the SBP Request frame, and AP replies to STA1's request through the SBP Response frame. After accepting STA1's SBP request, AP, as the Sensinginitiator, searches for a suitable STA in the BSS to complete WLAN Sensing. After AP completes WLAN Sensing, it returns the measurement results to STA1 through the SBP Report frame.

[0115] Therefore, multiple APs can perform joint perception of the same target, and when the perception result of a certain AP is unavailable, the perception results of other APs can be used. However, the existing SBP does not support AP requesting AP proxy perception, that is, multi-AP joint perception cannot be established based on the existing SBP.

[0116] In view of this, the present application proposes a sensing method that can realize multi-AP joint sensing. When the sensing result of a certain AP is not available, the sensing results of other APs can be used. Figure 6 The method proposed in this application is introduced in detail.

[0117] Figure 6 is a schematic flow chart of a perception method provided by the present application. The method comprises the following steps.

[0118] S601, a first AP sends first request frames corresponding to N APs to N APs respectively, the first request frames are used by the AP to initiate a multi-AP joint proxy perception request, N is a positive integer. Correspondingly, the N APs receive the first request frames from the first AP respectively.

[0119] For ease of description, the present application may refer to multi-AP joint proxy sensing as coordinated sensing by proxy (Co-SBP).

[0120] It should be noted that the multi-AP joint proxy perception in this scheme may be multiple APs jointly perceiving the same target, or the multi-AP joint proxy perception may be respectively perceiving different parts of the same target, and the first AP may obtain the perception result of the entire target based on the perception results of different APs, or the multi-AP joint proxy perception may be a joint perception of the environment. This application does not specifically limit the perception target of the multi-AP joint perception.

[0121] Optionally, since the first AP needs to perform multi-AP joint perception with multiple APs, the first AP in this application can select M (M is greater than or equal to N) APs in the multi-AP cooperation set based on its own needs or other conditions, and send a first request frame to the M APs respectively. The N APs in this application can be regarded as the APs that ultimately participate in the multi-AP joint perception. It should be noted that any AP in the multi-AP cooperation set can obtain relevant information of all APs in the multi-AP cooperation set.

[0122] Optionally, the first request frame includes first information, and the first information indicates that the first request frame is a request frame for the AP to initiate multi-AP joint proxy perception, that is, for a device that receives the first request frame, it can be determined based on the first information in the first request frame that the device type of the device that initiates the Co-SBP request is an AP.

[0123] Optionally, the first request frame includes second information, the second information includes parameters required for the second AP to perform multi-AP joint proxy perception, and the second AP is the AP that receives the first request frame. For example, the parameters required for the second AP to perform multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP cooperative transmission type, trigger-based detection phase type, required number of perception response STAs, and whether the number of perception response STAs is required. The meaning of each parameter will be combined with Figure 7 A detailed explanation is given and will not be described here.

[0124] Optionally, the first request frame may also include information about the type of the perception measurement result of the second AP, and the second AP obtains the corresponding measurement result based on the type information, and the second AP is the AP that receives the first request frame. For example, the first request frame may include one or more types of information. For example, the type of the perception measurement result may be a CSI matrix.

[0125] S602, N APs send their respective first response frames to the first AP, where the first response frames are used to indicate acceptance of the multi-AP joint proxy perception request. Correspondingly, the first AP receives the first response frames from the N APs respectively.

[0126] For example, N APs can respectively determine whether they can accept the Co-SBP request of the first AP based on their own capabilities and the capabilities of the associated STAs, and directly reply to the first AP in the first response frame. For example, AP#1 among the N APs determines that it can accept the Co-SBP request of the first AP, and then sends a first response frame to the first AP. The first response frame indicates that AP#1 receives the Co-SBP request of the first AP, and then AP#1 establishes a sensing measurement session. It can be understood that the establishment of a sensing session here refers to AP#1 establishing a sensing session with its associated STA to prepare for AP#1 to perform joint sensing measurements later. For example, AP#1 can send a sensing measurement request (Sensing MeasurementRequest) frame to the associated STA#1, and STA#1 sends a sensing measurement response (Sensing Measurement Response) frame to AP#1 to indicate whether the sensing session is successfully established.

[0127] For example, AP#1 among the N APs may also first try to establish a perception measurement session, and then reply to the first AP according to the result of establishing the session.

[0128] This application does not impose any restrictions on the order in which AP#1 establishes the perception measurement session and replies to the first response frame. The interval between the first request frame and the first response frame does not exceed 20ms.

[0129] Optionally, the first response frame includes third information, where the third information indicates that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP.

[0130] Optionally, the embodiment of the present application can be applied to the following two scenarios. The processes of the two scenarios are briefly described below.

[0131] Scenario 1: The first AP can proactively initiate a Co-SBP request to N APs based on its own needs. For ease of description, the first AP in this scenario is referred to as a Co-sensing initiator, and the N APs are referred to as Co-sensing responders.

[0132] Scenario 2: The first STA can actively initiate a Co-SBP request to the first AP based on its own needs, and the first AP passively initiates Co-SBP requests to N APs based on the request of the first STA. It can be seen that two Co-SBP requests are initiated in Scenario 2. To facilitate the distinction of descriptions, this application refers to the device that initiates the first Co-SBP request in this scenario (i.e., the first STA) as the Co-SBP initiator, and the first AP that responds to the Co-SBP request of the first STA as the Co-SBP responder. Afterwards, the first AP will initiate a second Co-SBP request to N APs. Therefore, this application refers to the device that initiates the second Co-SBP request (i.e., the first AP) as the Co-sensing initiator, and the N APs that respond to the Co-SBP request of the first AP as Co-sensing responders.

[0133] It should be understood that S601 and S602 can be regarded as the process corresponding to the Co-SBP request in scenario 1 or the process corresponding to the second Co-SBP request in scenario 2. Optionally, if the corresponding scenario is scenario 2, the first STA also needs to initiate the first Co-SBP request before the first AP initiates the second Co-SBP request. For the process of the first STA initiating the first Co-SBP request, refer to the description in S603 and S604, which will not be described here.

[0134] Figure 7 : is a possible frame structure diagram of the first request frame proposed in this application. The first request frame can be regarded as a SBP Request frame for AP to request multi-AP joint perception, which is redesigned on the basis of the existing SBP Request frame. The existing SBP Request frame cannot support the scenario of multi-AP joint perception of this application, and cannot realize the indication of multi-AP joint perception parameters. Figure 7 The first request frame given in the present application can support the scenario of multi-AP joint sensing and realize the function of allocating joint sensing parameters to each AP. For example, the first request frame can be referred to as a Co-sensing request frame in the present application.

[0135] It should be understood that the number of bits occupied by each field in the request frame and response frame given in the drawings of the embodiments of the present application is only an example and should not constitute a limitation on the frame structure or frame length of the request frame and response frame proposed in the present application.

[0136] It should also be understood that the names of the request frames and response frames in the drawings of the embodiments of the present application and the names of the fields included therein are merely examples and should not constitute limitations on the request frames and response frames proposed in the present application.

[0137] like Figure 7As shown, the first request frame includes a Category field, a Public Action / Protected Dual of Public Action field, a Dialog Token field, a Measurement Session ID Indication field, a Co-Sensing Parameters Element field, a Sensing Measurement Parameters Element field, and a Responding STA (RSTA) Available Window Element field. The following describes some fields in the first request frame that are relevant to the present application.

[0138] (1) The first request frame adds a new frame type to the existing SBP Request frame, indicating that the first request frame is an SBP Request frame used by the AP to initiate a multi-AP joint perception request, and indicating that this frame will allocate joint perception parameters to the AP receiving the frame. Exemplarily, the present application extends a frame type in the Public Action / Protected Dual of Public Action field of the existing SBP Request frame to indicate that the frame is the first request frame. Exemplarily, as shown in Table 1, when the value of the Public Action / Protected Dual of Public Action field is 62 (i.e., an example of the first information), it indicates that the current SBP Request frame is the first request frame.

[0139] Table 1

[0140] Public Action Field Value meaning 51 Perception measurement request 52 Perceptual measurement response 53 Perception Measurement Report …… …… 59 SBP Report 60 Co-SBP Request 61 Co-SBP response 62 Co-Sensing Request 63 Co-Sensing Response

[0141] (2) The Measurement Session ID Indication field in the first request frame indicates the Measurement Session ID, which identifies the perception measurement parameters to be used in the corresponding perception measurement exchange. The existing field is directly reused here and will not be described in detail.

[0142] (3) The RSTA Availability Window element field in the first request frame is the specific time and period allocated by the first AP to N APs for multi-AP joint sensing, that is, the available time window. Multi-AP joint sensing needs to be performed within this allocated time window.

[0143] (4) In the first request frame, the Sensing Measurement Parameters Element field indicates the specific sensing parameters allocated to AP#1 receiving the first request frame. For example, this field includes a bandwidth (BW) field, a maximum (Max) transmission (TX) space-time stream (STS) and a Max reception (RX) STS field, a number of receiving antennas (Number of RX Antennas) field, etc., wherein the BW field is used to indicate the sensing measurement bandwidth, the Max TX STS and Max RX STS fields are used to indicate the maximum space-time stream, and the Number of RX Antennas field is used to indicate the number of antennas used by the sensing receiver. In a possible implementation, this field may be designed in the same manner as the Sensing Measurement Parameters Element field in the existing SBP Request frame.

[0144] (5) A new Co-Sensing Parameter element field is defined in the first request frame.

[0145] It should be noted that the naming of the newly added fields in the first request frame is only an example for the convenience of description. If the information carried and the functions implemented in a field are the same as the information carried and the functions implemented by the newly added fields given in this application, then the field can be considered to be the same field as the newly added fields given in this application. The specific names given for the newly added fields in the first request frame or other frames later are also examples, and the related places will not be repeated one by one in the following text.

[0146] It should also be noted that the length of the newly added field in the first request frame is only an example for the convenience of description, and the length of this field should not constitute a limitation to the present invention. The specific length of the newly added field in the first request frame or other frames later is also an example, and the relevant parts will not be repeated one by one in the following text.

[0147] like Figure 7As shown, the Co-sensing Parameter element field includes an element identification (Element ID) field, a length (Length) field, an element identification extension (Element ID Extension) field, a joint sensing parameter control (Co-Sensing Parameters Control) field, a sensing responder address (Sensing ResponderAddresses) field and a sensing responder identification field (Sensing Responder IDs) field. The following describes some fields in the Co-sensing Parameter element field that are related to this application.

[0148] 1) The Element ID field and the Element ID Extension field in the Co-sensing Parameter element field are used to jointly indicate the type and usage scenario of the corresponding element. This application extends the Element ID Extension to indicate that this element carries the joint sensing parameters allocated to AP#1 that receives the first request frame. In this application, the Element ID, Length, and Element ID Extension follow the design of IEEE 802.11bf. For example, as shown in Table 2, an element type is extended on the Element ID. When the value of the Element ID Extension is<Lastassigned+18> , it is considered that the element carries the joint perception parameters allocated to AP#1 that receives the first request frame.

[0149] Table 2

[0150]

[0151] 2) The Co-Sensing Parameters Control field in the Co-sensing Parameter element field is used to carry the second information. For example, Figure 8It is a schematic diagram of the structure of the Co-Sensing Parameters Control field. The Co-Sensing Parameters Control field includes a joint sensing request (Co-Sensing Request) field, a joint sensing procedure expiry index (Co-Sensing Procedure Expiry Exponent) field, a multi-AP transmission type (MAP Transmission Model) field, a detection phase type (Sounding Phase Model) field, a sensing responder number (Number of Sensing Responder field), whether the number of sensing responders is required (mandatory or mandatory) (Mandatory Number of Responder) field, a recommended responder list (Preferred Responder List), a recommended responder number (Number of Preferred Responders), whether the recommended number of responders is required (Mandatory Preferred Responder) and a sensing responder to sensing responder (sensing responder to sensing responder, SR2SR) sensing request (SR2SR Sounding Request). The following specifically describes the meaning of each field in the Co-Sensing Parameters Control field and which parameters in the second information are specifically carried.

[0152] The Co-Sensing Request field is used to indicate in which frame the Co-Sensing Parameters element is carried. Exemplarily, the Co-Sensing Request field is set to "1" to indicate that the Co-Sensing Parameters element is carried in a request frame for multi-AP joint perception initiated by the AP, and is set to "0" to indicate that the Co-Sensing Parameters element is carried in a response frame for multi-AP joint perception initiated in response to the AP. It should be noted that since the first request frame is a request frame for multi-AP joint perception initiated by the AP, the value of this field in the first request frame is 1. In addition, this field is also included in the first response frame (see Fig. 9), since the first response frame is a response frame for multi-AP joint perception initiated in response to the AP, the value of this field in the first response frame is 0. Since the Public Action / Protected Dual of Public Action field in the first request frame already indicates that the first request frame is a request frame for multi-AP joint perception initiated by the AP, this field in the first request frame may be an optional field.

[0153] The Co-Sensing Procedure Expiry Exponent field is used to obtain the AP of this field to determine whether to terminate multi-AP joint perception (i.e., the expiration time of multi-AP joint perception carrying the second information in this field). Co-Sensing Procedure Expiry Exponent contains an unsigned integer, which can indicate the length of time. Within the time window agreed upon by multi-AP joint perception, the AP that obtains this field starts counting down the length of time indicated by this field after listening to the frame in the channel. When the countdown ends, there is still no frame interaction in the channel, and the AP considers that the current multi-AP joint perception process is over. Exemplary, the value of this field can be 2 (Co-SBP Procedure Expiry Exponent+8) millisecond.

[0154] The MAP Transmission Model field indicates the multi-AP collaborative transmission type to support multiple APs to coordinate the transmission of frames in the perception measurement process. For example, this field can indicate different transmission types through 2 bits. For example, when the MAP Transmission Model field is 00 (i.e., the value is 0), it indicates that the multi-AP collaborative transmission type is coordinated beamforming (CBF), and N APs can send frames in the perception measurement process based on CBF. The present application is not limited to CBF. In the future, multi-AP collaborative transmission methods suitable for the present application can be indicated by other values ​​in the MAP Transmission Model field.

[0155] The Sounding Phase Model field indicates the type of TB Sounding Phase established by the AP receiving the first request frame. For example, this field can indicate different TB sounding phases through 2 bits. For example, when the Sounding Phase Model field is 00 (i.e., the value is 0), AP#1 receiving the first request frame can only choose to establish the NDPA sounding phase; when the Sounding Phase Model field is 01 (i.e., the value is 1), AP#1 receiving the first request frame can only choose to establish the TF sounding phase; when the Sounding Phase Model field is 10 (i.e., the value is 2), AP#1 can choose between the NDPA sounding phase and the TF sounding phase.

[0156] It is understood that the above method of indicating the sounding phase type through the Sounding Phase Model field is only an example, and the present application does not exclude other methods that can achieve the indication of the sounding phase type. For example, the present application can also indicate the sounding phase type by assigning transmitter / receiver roles to different Sensing Responders through the "Sensing Responder Role Bitmap" field in the existing SBP, and the present application does not limit this.

[0157] The Number of Sensing Responder field indicates how many Sensing Responders the AP#1 receiving the first request frame needs to establish sensing (ie, the number of sensing responder STAs required to carry the second information in this field).

[0158] The Mandatory Number of Responder field indicates whether the number of Sensing Responders indicated in the above-mentioned Number of Sensing Responder field is mandatory. Exemplarily, this field can be indicated by 1 bit. When the Mandatory Number of Responder field is "0", it means that the number of STAs indicated in the Number of Sensing Responder field is not mandatory, and the number of STAs can be regarded as a reference quantity, which can be met as much as possible; on the contrary, when the Mandatory Number of Responder field is "1", it means that the number of STAs indicated in the Number of Sensing Responder field must meet the requirements.

[0159] The Preferred Responder List field indicates whether to provide a recommended Sensing Responder list for AP#1 that receives the first request frame. Exemplarily, if the Preferred Responder List field is "1", it means that a recommended Sensing Responder list is provided for AP#1, and the address information of the recommended Sensing Responder is carried in the Co-sensing Parameter element in the first request frame (carried in the Sensing Responder Addresses field of the first request frame), and AP#1 needs to find a STA in the recommended Sensing Responder list to initiate a sensing request; if the Preferred Responder List field is "0", it means that no Sensing Responder is recommended for AP#1, and AP#1 looks for a suitable STA in its own BSS to initiate a sensing request.

[0160] The Number of Preferred Responders field indicates the number of Sensing Responders recommended for AP#1 to receive the first request frame. That is, if the Preferred Responder List field is "1", the Number of Preferred Responders field indicates how many media access control (MAC) addresses of the recommended Sensing Responders are contained in the Sensing Responder Addresses field. If the Preferred Responder List field is "0", the field is reserved. For example, the characters can be all set to 0, and AP#1 does not read the field.

[0161] The Mandatory Preferred Responder field indicates whether the Sensing Responder recommended for AP#1 receiving the first request frame is mandatory. Exemplarily, this field can be indicated by 1 bit. When the Mandatory Preferred Responder field is "0", it means that the recommended Sensing Responder is not mandatory. The recommended Sensing Responder can be regarded as a reference, and the Sensing Responder that ultimately participates in sensing should be found among the recommended Sensing Responders as much as possible; on the contrary, when the Mandatory Preferred Responder field is "1", it means that the Sensing Responder that ultimately participates in sensing must be found among the recommended Sensing Responders.

[0162] The SR2SR Sounding Request field indicates whether SR2SR awareness needs to be established. For example, if the SR2SR Sounding Request field is "0", it means it is not needed, and if it is "1", it means it is needed.

[0163] 3) The Sensing Responder Addresses field in the Co-sensing Parameter element field carries the address information of the Sensing Responder recommended for AP#1 receiving the first request frame. It can be understood that the Sensing Responder Addresses field will only exist in the first request frame when the Preferred Responder List field indicates that the Sensing Responder is recommended for AP#1. At this time, the Sensing Responder Addresses field contains one or more MAC addresses, which indicate the MAC addresses of the STAs sensed by AP#1.

[0164] 4) The Sensing Responder IDs field in the Co-sensing Parameter element field occupies 0 bits.

[0165] The above Figure 7 A possible first request frame is described in detail, for example, as follows Fig. 9 A possible frame structure of a first response frame is described.

[0166] Fig. 9 : is a schematic diagram of a possible frame structure of a first response frame proposed in this application. For example, in this application, the first request frame may be referred to as a Co-sensing response (Reponse) frame. Fig. 9 As shown, the frame structure of the first response frame is basically the same as that of the first request frame. Specifically, the first response frame includes a Category field, a Public Action / Protected Dual of Public Action field, a Dialog Token field, a Measurement Session ID Indication field, a Status Code field, a Co-Sensing Parameters Element field, and a Sensing Measurement Parameters Element. Only the fields that carry different information between the first response frame and the first request frame are described here.

[0167] (1) The first response frame extends a frame type in the Public Action / Protected Dual of Public Action field to indicate that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP. Exemplary, as shown in Table 1, when the value of the Public Action / Protected Dual of Public Action field is "63" (ie, an example of the first information), it indicates that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP.

[0168] (2) The Status Code field in the first response frame indicates whether AP#1 receiving the first request frame receives the request of the first request frame. For example, if AP#1 receives the request, the Status Code field is set to SUCCESS; if AP#1 rejects the request, the Status Code field is set to REQUEST_DECLINED or REJECTED_WITH_SUGGESTED_CHANGES (which is exactly the same as the existing Status Code field in 11bf).

[0169] (3) A new Co-Sensing Parameter element field is defined in the first response frame. The Co-Sensing Parameter element field of the first response frame is designed the same as the Co-Sensing Parameter element field of the first request frame, and only the meanings of some fields are different. Only the fields with different meanings are described below.

[0170] 1) If the Co-Sensing Request field in the Co-SensingParameter Control field of the Co-Sensing Parameters Element field of the first response frame exists, exemplarily, the value of the Co-SensingRequest field is 1, indicating that the Co-Sensing Parameters element is carried in the request frame of multi-AP joint perception initiated by the AP, and the value is 0, indicating that the Co-Sensing Parameters element is carried in the response frame of multi-AP joint perception initiated in response to the AP, then the value of this field in the first response frame needs to be set to 0, indicating that the Co-SensingParameters element is carried in the first response frame. Since the Public Action / Protected Dual of Public Action field in the first response frame already indicates that the first response frame is a response frame for multi-AP joint perception initiated in response to the AP, this field in the first response frame can be an optional field. 2) The Co-Sensing ProcedureExpiry Exponent field, the MAP Transmission Model field, the Sounding Phase Model field, the Mandatory Number of Responder field, the Mandatory Preferred Responder field, and the SR2SRSounding Request field are reserved in the first response frame. For example, when the character is reserved, all the fields may be set to 0, and the first AP may not read these fields.

[0171] 3) The Number of Sensing Responder field has different meanings depending on the Status Code field. For example, if the Status Code field of the first response frame is equal to SUCCESS, the Number of Sensing Responder field is used to indicate how many Sensing Responders are actually established by AP#1 that receives the first request frame. If the Status Code field of the first response frame is equal to REJECTED_WITH_SUGGESTED_CHANGES, the Number of Sensing Responder field is used to recommend the value of this field carried in the first request frame when the first AP initiates multi-AP joint perception next time.

[0172] 4) The Preferred Responder List field indicates the Sensing Responder included in the perception established by AP#1 that receives the first request frame. Specifically, this field is used to indicate whether the Sensing Responder Addresses field and the Sensing Responder IDs field exist. Exemplarily, if the Preferred Responder List field is "1", it means that the Sensing Responder Addresses field and the Sensing Responder IDs field exist, and contain the address and ID of the Sensing Responder included in the perception established by AP#1 that receives the first request frame; if the Preferred Responder List field is "0", it means that the Sensing Responder Addresses field and the Sensing Responder IDs field do not exist.

[0173] 5) The Number of Preferred Responders field indicates the number of MAC addresses contained in the Sensing Responder Addresses field. For example, if the Preferred Responder List field is "1", the Number of Preferred Responders field indicates the number of MAC addresses of the Sensing Responder contained in the Sensing Responder Addresses field. If the Preferred Responder List field is "0", this field is reserved.

[0174] (4) The Sensing Responder Addresses field carries the address information of the Sensing Responder that AP#1, which receives the first request frame, uses to satisfy the first AP request. It can be understood that the Sensing Responder Addresses field appears only when the Preferred Responder List field is set to "1". At this time, the Sensing Responder Addresses field contains one or more MAC addresses that indicate the STA selected by AP#1 to satisfy the first AP request.

[0175] (5) The Sensing Responder IDs field exists only when the Preferred Responder List field is set to "1" and the Status Code field is equal to SUCCESS. The Sensing Responder IDs field is used to carry the ID information of the Sensing Responder used by AP#1 that receives the first request frame to satisfy the request of the first AP, such as the association identification (AID) / unassociated STA identifier (USID), and the order of the AID / USID should be the same as the order of the MAC addresses in the Sensing Responder Addresses field.

[0176] In the above technical solution, the first AP can initiate a Co-SBP request to other APs, so that the first AP can use multiple sensing results at the same time, thereby avoiding the situation where the sensing task fails due to unavailable sensing results when the first AP senses alone.

[0177] From the above, it can be seen that if the corresponding scenario is scenario 2, the first STA also needs to initiate the first Co-SBP request before the first AP initiates the second Co-SBP request. Then, optionally, before S602, the method also includes S603 and S604.

[0178] S603, the first STA sends a second request frame to the first AP, where the second request frame is used by the STA to initiate a multi-AP joint proxy awareness request. Correspondingly, the first AP receives the second request frame from the first STA.

[0179] It should be understood that the first request frame sent by the first AP to the N APs in S601 is determined and sent based on the received second request frame.

[0180] For example, the second request frame may carry an identifier of an AP recommended by the first STA to the first AP for participating in multi-AP joint perception. The AP recommended by the first STA includes the N APs in S601, and the N APs are the APs among the recommended APs that ultimately participate in multi-AP joint perception.

[0181] For example, if the first STA does not recommend an AP to participate in multi-AP joint perception to the first AP, the first AP can select M (M is greater than or equal to N) APs in the multi-AP collaboration set to initiate multi-AP joint perception. The N APs in S601 are the APs among the M APs that ultimately participate in multi-AP joint perception.

[0182] Optionally, the second request frame includes fourth information, and the fourth information indicates that the second request frame is a request frame for STA to initiate multi-AP joint proxy perception, that is, for a device that receives the second request frame, the device type of the device that initiates the Co-SBP request can be determined based on the fourth information in the second request frame as STA.

[0183] Optionally, the second request frame includes fifth information, and the fifth information includes parameters required for multi-AP joint proxy perception. For example, the parameters required for multi-AP joint proxy perception include one or more of the following parameters: multi-AP cooperative transmission type, trigger-based detection phase type, the number of APs required to establish multi-AP joint proxy perception, whether the required number of APs is mandatory, whether the AP receiving the second request frame needs to perform perception measurement, the number of required perception response STAs, whether the number of perception response STAs is mandatory, whether the AP receiving the second request frame recommends the AP for joint proxy perception, whether different multi-AP joint proxy perception parameters are provided for the recommended AP, and whether the first STA needs to participate in the perception measurement.

[0184] For example, when the fifth information indicates that different perception parameters are provided for the recommended AP, the second request frame includes the sixth information, and the sixth information includes the perception parameters assigned to each AP in the recommended AP. For example, the sixth information includes one or more of the following parameters assigned to each recommended AP: measurement parameters for perception, the number of required perception response STAs, whether the number of perception response STAs is required, and the type of detection phase based on triggering. The meaning of each parameter will be described below. Fig. 9 A detailed explanation is given and will not be described here.

[0185] It should be understood that when different perception parameters are provided for the recommended AP in the second request frame, the perception parameters in the first request frame sent by the first AP to AP#1 in the recommended AP are determined based on the perception parameters of AP#1 carried in the second request frame. For example, if the second request frame indicates that the type of detection phase that AP#1 needs to establish is NDPA sounding phase, and the number of perception response STAs required for the perception measurement of AP#1 is 5 and the number 5 is a condition that must be met, then the first request frame sent by the first AP to AP#1 also needs to indicate that the type of detection phase that AP#1 needs to establish is NDPA sounding phase, and the number of perception response STAs required for the perception measurement of AP#1 is 5 and the number 5 is a condition that must be met.

[0186] Optionally, the second request frame may further include information about the type of the perception measurement result. It should be noted that the type information in the first request frame is the same as the type information in the second request frame.

[0187] S604: The first AP sends a second response frame to the first STA, where the second response frame indicates acceptance of the multi-AP joint proxy perception request.

[0188] For example, the first AP can determine whether the multi-AP joint perception request of the first STA is feasible through the multi-AP cooperation set information, and reply to the second response frame according to the judgment result. If the second response frame indicates that the request of the first STA is accepted, the first AP establishes multi-AP joint perception with the N APs. For the process of establishing multi-AP joint perception with the first AP and the N APs, refer to the description in S601 and S602, which will not be repeated here.

[0189] For example, the first AP may first establish perception with M APs recommended or determined by the first STA, and then reply with a second response frame to the first STA based on the perception establishment result. For the process of the first AP establishing perception with the M APs recommended or determined by the first STA, please refer to the description in S601 and S602, which will not be repeated here.

[0190] The present application does not impose any restriction on the order in which the first AP establishes perception with the M APs and replies to the second response frame, as long as the interval between the second request frame and the second response frame does not exceed 20ms.

[0191] Optionally, the second response frame includes seventh information, and the seventh information indicates that the second response frame is a response frame for responding to a multi-AP joint proxy awareness request initiated by a STA.

[0192] Fig.10 This is a schematic diagram of a possible frame structure of a second request frame proposed in this application. The second request frame can be regarded as a SBP Request frame redesigned on the basis of the existing SBP Request frame for STA to request multi-AP joint perception. For example, the second request frame can be referred to as a Co-SBP Request frame in this application.

[0193] like Fig.10As shown, the second request frame includes a Category field, a Public Action / Protected Dual of Public Action field, a DialogToken field, a Co-SBP Parameters Element field, a Sensing Measurement Parameters Element field, and an Availability Window element field for an initiating STA (ISTA). The following describes some of the fields in the second request frame that are relevant to the present application.

[0194] (1) The second request frame adds a new frame type to the existing SBP Request frame, indicating that the first request frame is an SBP Request frame used by the STA to initiate a multi-AP joint perception request, and indicating that this frame will carry multi-AP joint perception parameters. Exemplarily, the present application extends a frame type in the Public Action / Protected Dual of Public Action field of the existing SBP Request frame to indicate that the frame is a second request frame. Exemplarily, as shown in Table 1, when the value of the Public Action / Protected Dual of Public Action field is "60" (i.e., an example of the fourth information), it indicates that the current SBP Request frame is a second request frame.

[0195] (2) The ISTA Availability Window element field in the second request frame is used by the first STA to inform the first AP of the period of time during which it is idle. The first AP needs to allocate the time and cycle for multi-AP joint sensing during this idle time. This is the same as the design of the existing SBP and is reused here.

[0196] (3) In the second request frame, the Sensing Measurement Parameters Element indicates the specific sensing parameters allocated to the first AP receiving the second request frame, such as the BW field, the Max TX STS and Max RXSTS fields, the Number of RX Antennas field, etc. For the meaning of each field, refer to the description of the corresponding field in the Sensing Measurement Parameters Element field in the first request frame, which will not be repeated here. In a possible implementation, the design of this field can be the same as that of the Sensing Measurement Parameters Element field in the existing SBP Request frame.

[0197] (4) A Co-SBP Parameter element field is newly designed in the second request frame.

[0198] like Fig.10 As shown, the Co-SBP Parameter element field includes an element identification (Element ID) field, a length (Length) field, an element identification extension (Element ID Extension) field and a joint proxy sensing parameter control (Co-SBP Parameters Control) field, a multi-AP parameter control (MAP Parameters Control) field, a sensing responder address (Sensing Responder Addresses) field and a sensing responder identification field (Sensing Responder IDs) field. The following describes some fields in the Co-SBP Parameter element field that are related to this application.

[0199] 1) The Element ID field and the Element ID Extension field in the Co-SBP Parameter element field are used to indicate the type and usage scenario of the corresponding element. This application extends the Element ID Extension to indicate that this element carries multi-AP joint perception parameters. The Element ID, Length, and Element ID Extension in this application follow the design of IEEE 802.11bf. For example, as shown in Table 2, an element type is extended on the Element ID. When the value of the Element ID Extension is<Last assigned+17> , it is considered that the corresponding element carries the multi-AP joint perception parameters.

[0200] 2) The Co-SBP Parameters Control field in the Co-SBP Parameter element field is used to carry the fifth information. For example, Fig.11It is a schematic diagram of the structure of the Co-SBP Parameters Control field. The Co-SBP Parameters Control field includes a joint proxy perception request (Co-SBP Request) field, a joint proxy perception procedure expiration index (Co-SBP Procedure Expiry Exponent) field, a multi-AP transmission type (MAP Transmission Model) field, a detection phase type (Sounding Phase Model) field, an AP number (Number of AP) field, an AP number must (Mandatory Number of AP) field, a joint proxy perception initiator (Co-SBP Initiator) field, a sensing responder number (Number of Sensing Responder) field and a sensing responder number must (Mandatory Number of Responder) field, a recommended AP list (Preferred AP List) field, a recommended AP number (Number of Preferrd AP) field, a different sensing element of the recommended AP (Different Sensing element of Preferred AP) field, a sensing responder (Sensing Responder) field, a recommended responder list (Preferred Responder List), and a recommended responder number (Number of Preferred Responders), whether the number of recommended responders is required (Mandatory Preferred Responder) and SR2SR Sounding Request (SR2SR Sounding Request). The following specifically describes the meaning of each field in the Co-SBP Parameters Control field and which parameters in the fifth information are specifically carried.

[0201] The Co-SBP Request field is used to indicate in which frame the Co-SBP Parameters element is carried. Exemplarily, the Co-SBP Request field is set to "1" to indicate that the Co-SBP Parameters element is carried in the request frame for multi-AP joint perception initiated by the STA, and is set to "0" to indicate that the Co-SBP Parameters element is carried in the response frame for multi-AP joint perception initiated in response to the STA. It should be noted that since the second request frame is a request frame for multi-AP joint perception initiated by the STA, the value of this field in the second request frame is 1. In addition, this field is also included in the second response frame (see Fig.13 ), since the second response frame is a response frame for multi-AP joint perception initiated in response to the STA, the value of this field in the second response frame is 0. Since the Public Action / Protected Dual of PublicAction field in the second request frame already indicates that the second request frame is a request frame for multi-AP joint perception initiated by the STA, this field in the second request frame may be an optional field.

[0202] For descriptions of the Co-SBP Procedure Expiry Exponent field, the MAP Transmission Model field, and the Sounding Phase Model field, refer to the descriptions of the corresponding fields in the first request frame, which will not be repeated here.

[0203] However, it should be noted that the value of the Co-Sensing Procedure Expiry Exponent field in the first request frame should be the same as the value of the Co-SBP Procedure Expiry Exponent in the second request frame, that is, the first AP and the N APs determine whether the multi-AP joint perception process is completed based on the same parameter value. Within the agreed time window of multi-AP joint perception, the first STA and the first AP that obtain this field start counting down the duration indicated by this field after listening to the frame in the channel. When the countdown ends, there is still no frame interaction in the channel, and the first STA and the first AP consider that the current multi-AP joint perception process is completed.

[0204] It should be noted that the value of the MAP Transmission Model field in the first request frame should be the same as the value of the MAP Transmission Model field in the second request frame.

[0205] The Number of AP field indicates how many APs need to be included in the multi-AP joint perception, that is, the first STA can use the Number of AP field to indicate to the first AP how many APs are included in the multi-AP joint perception.

[0206] The Mandatory Number of AP field indicates whether the number of APs indicated in the above-mentioned Number of AP field is mandatory. For example, when the Mandatory Number of AP field is "0", it means that the number of APs indicated in Number of AP is not mandatory. At this time, the number of APs indicated in Number of AP is a reference quantity and should be met as much as possible; on the contrary, when the Mandatory Number of AP field is "1", it means that the number of APs indicated in Number of AP is mandatory.

[0207] The Co-Sensing Initiator field indicates whether the first AP requested by the first STA to establish multi-AP joint sensing needs to perform sensing measurements. Exemplarily, the Co-SBP Initiator field is "0" for not requiring, and "1" for requiring.

[0208] The Number of Sensing Responder field indicates how many Sensing Responders the first AP needs to establish a sense of. It should be noted that this field only exists when the Co-Sensing Initiator field is "1".

[0209] The Mandatory Number of Responder field indicates whether the number of Sensing Responders indicated in the above-mentioned Number of Sensing Responder field is mandatory.

[0210] The Preferred AP List field indicates whether to provide a recommended AP list for the first AP. Exemplarily, if the Preferred AP List field is "1", it means that a recommended AP list is provided for the first AP, and the MAC address of the recommended AP is carried in the MAP Parameters in the second request frame. The AP needs to find an AP in the recommended AP list to initiate a second Co-SBP request; if the Preferred AP List field is "0", it means that an AP list is not recommended for the first AP, and the first AP looks for a suitable AP among all APs participating in multi-AP collaboration to initiate a second Co-SBP request.

[0211] The Number of Preferred AP field indicates the number of recommended APs provided for the first AP. That is, if the Preferred AP List field is "1", the Number of Preferred AP field indicates how many MAP Parameters Control fields the Co-SBP ParametersElement field contains, where each MAP ParametersControl field corresponds to a recommended AP. If the Preferred Responder List field is "0", the field is reserved.

[0212] The Different Sensing element of Preferred AP field indicates whether different sensing parameters are provided for the recommended AP. It should be noted that the Different Sensing element of Preferred AP field is only meaningful when the Preferred AP List is "1". For example, the Different Sensing element of Preferred AP field is "1", which means that different parameters are assigned to the recommended AP; the Different Sensing element of Preferred AP field is "0", which means that the recommended AP uses the same parameters, and is the same as the parameters provided to the first AP.

[0213] It should be noted that, if the first STA does not recommend an AP for the first AP, the AP participating in multi-AP joint sensing found by the first AP itself uses the same parameters, which are the same as the parameters sent by the first STA to the first AP.

[0214] It can be understood that if the Different Sensing element of Preferred AP field is "0", when the first AP needs to send a first request frame to AP#1 in the recommended AP, the first AP generates a first request frame to be sent to AP#1 based on the information obtained in the second request frame. For example, the frame structure of the first request frame is as follows: Figure 7As shown, then, the Sensing Measurement Parameters field in the Sensing Measurement Parameters element field of the first request frame carries the information carried in the Sensing Measurement Parameters field of the Sensing Measurement Parameters element field in the second request frame, and the Number of Sensing Responders field, Mandatory Number of Sensing Responders field, and Sounding Phase Model field of the Co-SBP Parameters Control field of the first request frame respectively carry the information carried in the Number of Sensing Responders field, Mandatory Number of Sensing Responders field, and Sounding Phase Model field of the Co-SBP Parameters Control field of the second request frame.

[0215] The Sensing Responder field indicates whether the first STA participates in the multi-AP joint sensing process as a sensing responder. Exemplarily, the Sensing Responder field is "0" for non-participation and "1" for participation. It can be understood that when the Sensing Responder field indicates that the first STA participates in the multi-AP joint sensing measurement, the Co-SensingInitiator field should indicate that the first AP needs to sense.

[0216] For the description of the Preferred Responder List field, the Number of Preferred Responders field, the Mandatory Preferred Responder field, and the SR2SR Sounding Request field, please refer to the description of the corresponding fields in the first request frame, which will not be repeated here. It should be noted that these four fields are parameters allocated to the first AP, that is, these four fields are only meaningful when the Co-Sensing Initiator field indicates that the first AP needs to perform perception measurements, otherwise they are retained.

[0217] 3) The MAP Parameters Control field in the Co-SBP Parameter element field is used to carry the sixth information. For example, Fig.12 It is a schematic diagram of the structure of the MAP Parameters Control field. The MAP Parameters Control field includes the Preferred AP Addresses field, the Preferred AP Identifier (Preferred APIDs) field, the Sensing Measurement Parameters field, the Number of Sensing Responders field, the Mandatory Number of Sensing Responders field, the Sounding Phase Model field, the Preferred Responder List field, the Number of Preferred Responders field, the Mandatory Preferred Responder field, and the SR2SR Sounding Request field, the Sensing Responder Addresses field, and the Sensing Responder IDs field. The meaning of each field in this field and which parameters in the sixth information are specifically carried are explained in detail below.

[0218] The Preferred AP Addresses field is used to carry the address information of the recommended AP. It is understood that the MAP ParametersControl field will only exist in the second request frame when the Preferred AP List field is set to the recommended AP. At this time, the Preferred AP Addresses field in the MAP Parameters Control field contains a MAC address, which indicates the MAC address of the recommended AP. It is understood that each Preferred AP Addresses field in the MAP ParametersControl field corresponds to a different recommended AP.

[0219] It should be noted that the Preferred AP IDs field in the second request frame occupies 0 bits.

[0220] The Sensing Measurement Parameters field is used to allocate sensing parameters to different APs. For example, the field includes the BW field, the Max TX STS and Max RX STS fields, the number of receiving antennas (Number of RXAntennas) field, etc. For the meaning of each field, refer to the description of the corresponding field in the Sensing Measurement Parameters Element field in the first request frame, which will not be repeated here. In a possible implementation, the design of this field can be the same as that of the Sensing Measurement Parameters field in the Sensing Measurement Parameters Element in the existing SBP Request frame.

[0221] The Number of Sensing Responders field indicates how many Sensing Responders (i.e., sensing response STAs) should be included in different recommended APs to establish sensing.

[0222] The Mandatory Number of Sensing Responders field indicates whether the number of Sensing Responders indicated in the Number of Sensing Responders field is mandatory.

[0223] The Sounding Phase Model field indicates the TBSounding Phase type that the AP of the corresponding AID needs to establish in the perception phase. The design concept of this field is the same as that of the Sounding PhaseModel field of the Co-SBP Parameters Control field, except that the objects indicated are different.

[0224] For the description of the Preferred Responder List field, the Number of Preferred Responders field, the Mandatory Preferred Responder field, the SR2SR Sounding Request field, the Sensing Responder Addresses field, and the Sensing Responder IDs field, please refer to the description of the corresponding fields in the first request frame, which will not be repeated here. It should be noted that these four fields are parameters allocated to the second AP, that is, these four fields are only meaningful when the Different Sensing element of Preferred AP field indicates that different sensing parameters are provided for the recommended AP, otherwise they are retained.

[0225] It can be understood that if the first STA assigns different perception parameters to different recommended APs through the MAP Parameters Control field in the second request frame, when the first AP needs to send the first request frame to AP#1 in the recommended AP, the first AP needs to obtain the information carried by AP#1 in the MAP Parameters Control field in the recommended AP, and then generate the first request frame to be sent to AP#1 based on the information. For example, the frame structure of the first request frame is as follows: Figure 7As shown, then, the Sensing MeasurementParameters field in the Sensing Measurement Parameters element field of the first request frame carries the sensing parameters allocated to AP#1 by the Sensing MeasurementParameters field in the MAP Parameters Control field, and the Number of Sensing Responders field, the Mandatory Number of SensingResponders field, and the Sounding Phase Model field in the Co-Sensing ParametersControl field of the first request frame carry the sensing parameters allocated to AP#1 by the Number of Sensing Responders field, the Mandatory Number of Sensing Responders field, and the Sounding Phase Model field in the MAP Parameters Control field, respectively. 4) The Sensing Responder Addresses field in the Co-SBP Parameter element field carries the address information of the Sensing Responder recommended for the first AP. It can be understood that the Sensing Responder Addresses field will exist in the second request frame only when the Preferred Responder List field is set to recommend the Sensing Responder and the Co-Sensing Initiator field indicates that the first AP needs to perform sensing measurement. At this time, the Sensing Responder Addresses field contains one or more MAC addresses, which indicate the MAC addresses of the STAs with which the first AP establishes sensing.

[0226] 5) The Sensing Responder IDs field in the Co-SBP Parameter element field occupies 0 bits.

[0227] The above Fig.10 A possible second request frame is described in detail, for example, as follows Fig.13 A possible frame structure of the second response frame is described.

[0228] Fig.13: is a schematic diagram of a possible second response frame proposed in this application. For example, in this application, the second request frame may be referred to as a Co-SBP response (Reponse) frame. Fig.13 As shown, the frame structure of the second response frame is basically the same as that of the second request frame. Specifically, the second response frame includes a Category field, a Public Action / Protected Dual of Public Action field, a Dialog Token field, a Status Code field, an AID / USID field, a Co-SBP Parameters Element field, a Sensing Measurement Parameters Element field, and an RSTA Availability Window element field. Only the fields that carry different information between the second response frame and the second request frame are described here.

[0229] (1) The second response frame extends a frame type in the Public Action / Protected Dual of Public Action field to indicate that the second response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by a STA. Exemplary, as shown in Table 1, when the value of the Public Action / Protected Dual of Public Action field is 61 (ie, an example of the seventh information), it indicates that the second response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by a STA.

[0230] (2) The Status Code field in the second response frame indicates whether the first AP receives the request of the second request frame. For an example of this field, please refer to the above description and will not be repeated here.

[0231] It should be noted here that if the Status Code field is equal to SUCCESS and the first STA is associated with the first AP, the AID / USID field is set to the AID of the first STA; if the Status Code field is equal to SUCCESS and the first STA is not associated with the first AP, the AID / USID field is set to the USID of the first STA.

[0232] (3) A new Co-SBP Parameter element field is defined in the second response frame. The Co-SBP Parameter element field of the second response frame is designed the same as the Co-SBP Parameter element field of the second request frame, and only the meanings of some fields are different. Only the fields with different meanings are described below.

[0233] 1) If the Co-SBP Request field of the Co-SBP ParameterControl field of the Co-SBP Parameters Element field of the second response frame exists, exemplarily, the value of the Co-SBP Request field is 1, indicating that the Co-Sensing Parameters element is carried in the request frame of multi-AP joint perception initiated by the STA, and the value is 0, indicating that the Co-Sensing Parameters element is carried in the response frame of multi-AP joint perception initiated in response to the STA, then the value of this field in the second response frame needs to be set to 0, indicating that the Co-SBP Parameters element is carried in the second response frame. Since the Public Action / Protected Dual of Public Action field in the second response frame already indicates that the second response frame is a response frame for multi-AP joint perception initiated in response to the AP, this field in the second response frame can be an optional field.

[0234] 2) The Co-SBP Procedure Expiry Exponent field, MAP Transmission Model field, Sounding Phase Model field, Mandatory Number of AP field, Co-Sensing Initiator field, Mandatory Number of Responder field, Sensing Responder field, Mandatory Preferred Responder field, SR2SR Sounding Request field, and Different Sensing element of Preferred AP field are retained in the second response frame.

[0235] 3) Number of AP has different meanings depending on the Status Code field. For example, if the Status Code field of the second response frame is equal to SUCCESS, the Number of AP field is used to indicate how many APs the AP receiving the second request frame actually established to form a multi-AP joint perception. If the Status Code field of the second response frame is equal to REJECTED_WITH_SUGGESTED_CHANGES, the Number of AP field is used to recommend the value of this field carried in the second request frame when the first STA initiates multi-AP joint perception next time.

[0236] 4) The Number of Sensing Responder field has different meanings depending on the Status Code field. For example, if the Status Code field of the second response frame is equal to SUCCESS, the Number of Sensing Responder field is used to indicate how many Sensing Responders the AP receiving the second request frame has actually established. If the Status Code field of the second response frame is equal to REJECTED_WITH_SUGGESTED_CHANGES, the Number of Sensing Responder field is used to recommend the value of this field carried in the second request frame the next time the first STA initiates multi-AP joint perception. It should be noted that this field will only exist in the second response frame if it exists in the second request frame.

[0237] 5) The Preferred AP List field indicates whether the MAP Parameters Control field carries the AID of the AP included in the perception established by the first AP or the MAC address of the AP recommended by the first AP for STA4. That is, this field is used to indicate whether the MAP Parameters Control field exists. Exemplarily, the Preferred Responder List field is "1" to indicate that the MAP Parameters Control field exists; the Preferred Responder List field is "0" to indicate that the MAP Parameters Control field does not exist. In a possible implementation, this field can be designed the same as the Preferred Responder List field in the existing SBPResponse frame.

[0238] 6) The Number of Preferred AP field indicates how many MAP Parameters Control fields are included. For example, if the Preferred AP List field is "1", the Number of Preferred AP field indicates how many MAP Parameters Control fields are included, and one MAP Parameters Control field corresponds to one recommended AP. If the Preferred Responder List field is "0", the field is reserved.

[0239] 7) The Number of Preferred Responders field indicates the number of MAC addresses contained in the Sensing Responder Addresses field. For example, if the Preferred Responder List field is "1", the Number of Preferred Responders field indicates how many MAC addresses of Sensing Responders are contained in the Sensing Responder Addresses field. If the Preferred Responder List field is "0", this field is reserved.

[0240] (4) A new MAP Parameters Control field is defined in the second response frame. The MAP Parameters Control field of the second response frame is designed the same as the MAP Parameters Control field of the second request frame, with only some fields having different meanings. Only the fields with different meanings are described below.

[0241] 1) The Preferred AP Addresses field carries the address information of the second AP used by the first AP to satisfy the request of the first STA. It is understood that the Preferred AP Addresses field will only exist in the second response frame when the Preferred AP List field is set to "1". At this time, the Preferred AP Addresses field contains a MAC address, which indicates the MAC address of the second AP. It is understood that the Preferred AP Addresses field in each MAP Parameters Control field corresponds to a different second AP.

[0242] 2) The Preferred AP IDs field only exists when the Preferred AP List field is set to "1" and the Status Code field is equal to SUCCESS. The Preferred AP IDs field is used to carry the ID information of the second AP used by the first AP to satisfy the request of the first STA, such as AID / USID. The AID / USID can be a 12-bit ID negotiated between APs, or generated based on the MAC address of the AP. This application does not limit the method of obtaining the AID / USID. It only needs to be obtained through existing technologies and can indicate the corresponding AP. It should be noted that the AID / USID in the same MAP Parameters Control field should indicate the same second AP as the MAC address in the Preferred AP Addresses field.

[0243] (5) The Sensing Responder Addresses field carries the address information of the Sensing Responder that the first AP uses to satisfy the request of the first STA. It can be understood that the Sensing Responder Addresses field appears only when the Co-Sensing Initiator field is set to "1" and the Preferred Responder List field is set to "1". At this time, the Sensing Responder Addresses field contains one or more MAC addresses that indicate the Sensing Responder selected by the first AP to satisfy the request of the first STA.

[0244] (6) The Sensing Responder IDs field exists only when the Co-Sensing Initiator field is set to "1", the Preferred Responder List field is set to "1", and the Status Code field is equal to SUCCESS. The Sensing Responder IDs field is used to carry the ID information of the Sensing Responder used by the first AP to satisfy the request of the first STA, such as the AID / USID, and the order of the AID / USID should be the same as the order of the MAC addresses in the Sensing Responder Addresses field.

[0245] It should be noted that in scenario 2, the time window for multi-AP joint perception allocated by the first AP in the first request frame should be the same as the information of the multi-AP joint perception time window carried in the second response frame replied by the first AP to the first STA. For example, the information of the multi-AP joint perception time window can be carried in Fig.13 In the RSTA Availability Window element field in the second response frame shown.

[0246] It can be understood that in scenario 1, S601 and S602 can be referred to as the multi-AP joint perception establishment phase in the scenario, and in scenario 2, S601 to S604 can be referred to as the multi-AP joint perception establishment phase in the scenario. The following illustrates the frame interaction process of the multi-AP joint perception establishment phase in the two scenarios with reference to the accompanying drawings.

[0247] Fig.14 Schematic diagram of the multi-AP joint perception process corresponding to scenario one. Fig.14It includes a multi-AP joint perception establishment phase, a multi-AP joint perception measurement phase and a multi-AP joint perception report feedback phase of scenario one, wherein AP1 can be regarded as the first AP, and AP2 and AP3 can be regarded as APs among N APs. In this scenario, AP1, as a Co-Sensing Initiator, sends a Co-Sensing Request frame (i.e., an example of the first request frame) to AP2 to initiate a multi-AP joint perception request. AP2, as a Co-Sensing Responder, sends a Co-Sensing Response frame (i.e., an example of the first response frame) to AP1 to indicate that the multi-AP joint perception request initiated by AP1 is accepted. After that, AP1, as a Co-Sensing Initiator, continues to send Co-Sensing Request frames (i.e., an example of the first request frame) to AP3 to initiate a multi-AP joint perception request. AP3, as a Co-Sensing Responder, sends a Co-Sensing Response frame (i.e., an example of the first response frame) to AP1 to indicate that the multi-AP joint perception request initiated by AP1 is received. Finally, AP1, AP2, and AP3 send SensingMeasurement Request frames to their associated STA1, STA2, and STA3, respectively, to establish a perception session to prepare for the subsequent multi-AP perception measurement. STA1, STA2, and STA3 send Sensing Measurement Response frames to AP1, AP2, and AP3, respectively, to indicate that the perception session establishment is complete. Afterwards, the APs participating in multi-AP joint perception can continue to complete corresponding frame interactions in the multi-AP joint perception measurement phase and the multi-AP joint perception report feedback phase. The specific processes of these two phases will be described in detail in S605 to S607 and will not be described here.

[0248] Fig.15 Schematic diagram of the multi-AP joint perception process corresponding to scenario 2. Fig.15It includes the multi-AP joint perception establishment phase, the multi-AP joint perception measurement phase and the multi-AP joint perception report feedback phase of scenario 2, wherein ST4 can be regarded as the first STA, AP1 can be regarded as the first AP, and AP2 and AP3 can be regarded as APs among N APs. The multi-AP joint perception measurement phase and the multi-AP joint perception report feedback phase will be introduced in detail in S605 to S607, and will not be described here for the time being. In this scenario, STA4, as a Co-SBP Initiator, sends a Co-SBP Request frame (i.e., an example of the second request frame) to AP1 to initiate a multi-AP joint perception request, and AP1, as a Co-SBP Responder, sends a Co-SBP Response frame (i.e., an example of the second response frame) to STA4 to indicate that the multi-AP joint perception request initiated by STA4 is accepted. Then, AP1, as a Co-Sensing Initiator, sends a Co-Sensing Request frame (i.e., an example of the first request frame) to AP2 to initiate a multi-AP joint perception request, and AP2, as a Co-Sensing Responder, sends a Co-Sensing Response frame (i.e., an example of the first response frame) to AP1 to indicate that the multi-AP joint perception request initiated by AP1 is accepted. After that, AP1, as a Co-Sensing Initiator, continues to send Co-Sensing Request frames (i.e., an example of the first request frame) to AP3 to initiate a multi-AP joint perception request, and AP3, as a Co-Sensing Responder, sends Co-Sensing Response frames to AP1 to indicate that the multi-AP joint perception request initiated by AP1 is accepted. The Response frame (i.e., an example of the first response frame) indicates the reception of the multi-AP joint perception request initiated by AP1. Finally, AP1, AP2, and AP3 send Sensing Measurement Request frames to their associated STA1, STA2, and STA3, respectively, to establish a perception session. STA1, STA2, and STA3 send Sensing Measurement Response frames to AP1, AP2, and AP3, respectively, to indicate that the perception session establishment is complete. After that, the APs participating in the multi-AP joint perception can continue to complete the corresponding frame interaction in the multi-AP joint perception measurement phase and the multi-AP joint perception report feedback phase. The specific process of the multi-AP joint perception measurement phase will be described in detail in S605, and the specific process of the multi-AP joint perception report feedback phase will be described in detail in S605 to S608, which will not be described here.

[0249] Optionally, after the N APs successfully establish awareness sessions with the associated STAs, the method further includes:

[0250] S605: The first AP triggers N APs to perform multi-AP joint sensing measurement. Two implementation methods of the first AP triggering N APs to perform sensing measurement are given below.

[0251] In implementation method one, the first AP may trigger N APs in sequence to perform perception measurements. For example, if the second AP among the N APs is not the last AP among the N APs to be triggered to perform perception measurements, the first AP triggers the N APs to perform multi-AP joint perception measurements, including: the first AP determines that the second AP completes the perception measurement; the first AP sends a first inquiry trigger frame to a third AP among the N APs, the first inquiry trigger frame is used to trigger the third AP to perform perception measurements, the third AP is any AP among the N APs that has not been triggered to perform perception measurements; the first AP receives a first inquiry response frame from the third AP. Optionally, the ninth information in the first inquiry trigger frame is used to trigger the AP that receives the first inquiry trigger frame to perform multi-AP joint perception measurements.

[0252] Optionally, the first inquiry trigger frame includes tenth information, and the tenth information instructs the third AP to start performing perception measurement.

[0253] The following examples illustrate how the first AP in this implementation method determines that a certain AP (taking the third AP as an example) among N APs completes the perception measurement. Example 1: The first inquiry trigger frame includes information #1. Information #1 includes the duration of the third AP's perception measurement. When the first AP allocates a duration to the third AP, the third AP needs to complete the perception measurement within the allocated duration. After the duration allocated to the third AP expires, the first AP continues to trigger the next AP to perform the perception measurement. Example 2: The first inquiry trigger frame does not include the duration of the third AP's perception measurement. After the first AP triggers the third AP's perception measurement, the third AP can complete the perception measurement with the corresponding STA. The first AP will continue to monitor the channel. When the channel is idle, the first AP considers that the third AP has completed the perception measurement and continues to trigger the next AP to perform the perception measurement.

[0254] In the second implementation, the first AP can allocate a perception measurement start time and duration for each of the N APs to perform perception measurement, and the N APs perform perception measurement based on their own perception measurement start time and duration. For example, the first AP triggers N APs to perform multi-AP joint perception measurement, including: the first AP sends a second inquiry trigger frame to the N APs, the second inquiry trigger frame is used to trigger the N APs to perform perception measurement based on their respective corresponding perception measurement start time and duration; the first AP receives the second inquiry response frame of the N APs, the second inquiry response frame indicates that the AP confirms to perform perception measurement based on the corresponding perception measurement start time and duration.

[0255] Optionally, the second inquiry trigger frame includes eighth information, and the eighth information includes the start time and duration of the perception measurement performed by the N APs.

[0256] Optionally, the eleventh information in the second inquiry trigger frame is used to trigger N APs to perform multi-AP joint perception measurement.

[0257] Optionally, the second inquiry trigger frame includes twelfth information, and the twelfth information indicates that the N APs perform perception measurement based on their respective corresponding perception measurement start time and duration.

[0258] The current SBP does not support the SBP initiator to control the perception process. Even if the first AP can initiate a multi-AP joint request, it cannot guarantee that multiple perception results can be used in combination. However, based on the method given in S605, the first AP can control the perception measurements of multiple APs so that multiple APs can complete the perception of the target in a shorter period of time. At this time, the perception results of each AP can be considered to be soft-synchronized, ensuring that multiple perception results can be used in combination. Then, when the perception results of the first AP are unavailable due to interference or too weak signal strength at the edge of the BSS, the perception results of N APs at the "same moment" can be used to avoid the failure of the perception task.

[0259] For example, the above inquiry trigger frame for triggering multi-AP joint perception, such as the first inquiry trigger frame or the second inquiry trigger frame, may be referred to as a Co-SBP Polling Trigger frame in the present application.

[0260] Combine the following Fig.16 and Fig.17 The above implementation method 1 and implementation method 2 are illustrated with examples.

[0261] Fig.16 FIG. 1 is a schematic diagram of multiple APs performing joint sensing based on implementation method 1. Among them, AP1 can be regarded as the first AP, and AP2 and AP3 can be regarded as APs among N APs. Fig.16 As shown, AP1 first performs perception measurement. After AP1 completes the perception measurement, it sends a Co-SBP Polling Trigger frame to AP2 to trigger AP2 to perform measurement perception. AP2 sends a CTS-to-self frame response to AP1. Then, AP2 starts the perception measurement. After AP1 determines that AP2 has completed the perception measurement, it sends a Co-SBPPolling Trigger frame to AP3 to trigger AP3 to perform measurement perception. AP3 sends a CTS-to-self frame response to AP1. Then, AP3 starts the perception measurement until all APs participating in the multi-AP perception measurement complete the perception measurement based on the Co-SBP Polling Trigger frame sent by AP1.

[0262] Fig.17 FIG. 1 is a schematic diagram of multiple APs performing joint sensing based on implementation mode 2. Among them, AP1 can be regarded as the first AP, and AP2 and AP3 can be regarded as APs among N APs. Fig.17 As shown, AP1 sends a Co-SBP PollingTrigger frame to AP2 and AP3 to trigger AP2 and AP3 to perform measurement perception. The Co-SBP Polling Trigger frame includes the start time and duration of AP2's perception measurement and the start time and duration of AP3's perception measurement. AP2 and AP3 send a CTS-to-self frame response to AP1. AP1, AP2 and AP3 perform perception measurement in turn based on their respective start time and duration of perception measurement.

[0263] Fig.18 This is a schematic diagram of the frame structure of a possible inquiry trigger frame (hereinafter referred to as Co-SBP Polling Trigger frame) for triggering multi-AP joint perception proposed in this application. The inquiry trigger frame for triggering multi-AP joint perception can be regarded as a PollingTrigger frame for multi-AP joint perception redesigned on the basis of the existing Trigger frame. The existing Trigger frame cannot support the function of triggering the perception measurement of multiple APs at the same time in this application, and Fig.18 The inquiry trigger frame given in can support the scenario of multi-AP joint perception in this application. This application only makes modifications to the trigger-based common information (Trigger Dependent CommentInfo) field and the User Info field in the common information (Common Info) field of the existing Trigger frame.

[0264] like Fig.18 As shown, the Co-SBP Polling Trigger frame includes fields such as a common information field and a user information list field, wherein the common information field contains common information that all STAs associated with the AP need to read, and the user information list field contains multiple user information fields, each of which corresponds to information that a STA needs to read. The following describes some fields in the Co-SBP Polling Trigger frame that are relevant to this application.

[0265] (1) The Co-SBP Polling Trigger frame adds a new frame type to the existing trigger frame, indicating that the Co-SBP Polling Trigger frame is an inquiry trigger frame used to trigger multi-AP joint perception. Exemplarily, the present application extends a frame type in the Sensing Trigger Subtype field of the Trigger Dependent Common Info field of the Common Info field of the existing trigger frame to indicate that the trigger frame is a Co-SBP Polling Trigger frame. Exemplarily, as shown in Table 3, when the value of the Sensing Trigger Subtype field is 5 (i.e., an example of the ninth information or an example of the eleventh information), it indicates that the current trigger frame is a Co-SBP Polling Trigger frame, and the AP that receives this frame needs to return a CTS-to-self frame in response.

[0266] Table 3

[0267] Value of the Perception Trigger Subtype field meaning …… …… 3 Sensing Report 4 SR2SI Sounding 5 Co-SBP Polling 6 Co-SBP Report 7-15 Reserve

[0268] (2) The site information (Trigger Dependent User Info) field based on the trigger frame type in the User Info List field of the Co-SBP Polling Trigger frame is used to carry the parameters required for the sensing measurement allocated to different APs, and the parameters include the eighth information. Exemplarily, when the value of the Sensing Trigger Subtype field in the trigger frame is 5, the trigger frame is considered to be a Co-SBP Polling Trigger frame, and the UserInfo List field of the Co-SBP Polling Trigger frame carries the Trigger Dependent User Info field. Exemplarily, Fig.19 It is a structural diagram of the User Info List field. The User Info List field includes multiple User Info fields. Each User Info field includes an AID12 field and a Trigger Dependent User Info field. The AID12 field represents an association identifier of an AP. The Trigger Dependent User Info field indicates the number of HE-LTF repetitions of the NDP frame sent by the AP indicated by the AID12 field in the Sounding Phase, and the start time and duration of the perception measurement of the AP indicated by the AID12 field.

[0269] like Fig.19 As shown, the Trigger Dependent User Info field includes a Co-SBP repetition count (Co-SBPRep) field, a start time (Start Time) field, and a duration (Duration) field. The following specifically describes the meaning of each field in the Trigger Dependent User Info field and the parameters it carries.

[0270] The Co-SBP Rep field is used to indicate the number of HE-LTF repetitions of the NDP frame sent by the AP corresponding to AID12 in the Sounding Phase.

[0271] The Start Time field is used to indicate a first duration, which is used to determine the expected start time for the AP corresponding to AID 12 to perform perception measurement. For example, the expected start time may be the time corresponding to the first duration after the Co-SBP Polling Trigger frame is received.

[0272] The Duration field is used to indicate the duration of the Sounding of the AP corresponding to AID12. If this field is configured, each AP should complete the Sounding within this duration. Duration can be a specified duration in units of 32μs. For example, if the value of this field in the corresponding Co-SBP Polling Trigger frame in implementation method 1 can be set to all 0s.

[0273] Optionally, the AP that receives the Co-SBP Polling Trigger frame can determine whether to perform perception measurements based on implementation method one or implementation method two based on the number of User Info fields carried in the Co-SBP Polling Trigger frame. Specifically, if it is implementation method one, the Co-SBP Polling Trigger frame only carries one User Info field (i.e., the User Info of the triggered AP), and if it is implementation method two, the Co-SBP Polling Trigger frame will carry multiple User Info fields (i.e., the User Info of all triggered APs). Therefore, the AP can determine whether to perform subsequent perception measurements based on implementation method one or implementation method two based on the number of User Info fields contained in the Co-SBP Polling Trigger frame.

[0274] Optionally, the Trigger Dependent User Info field may also include a type (Model) field, which is used to indicate that the AP corresponding to AID12 performs perception measurement based on implementation method 1 or implementation method 2. For example, this field is indicated by 1 bit. When the value of this field is 0, it indicates that the AP starts to perform perception measurement (ie, implementation method 1). When the value of this field is 1, it indicates that the AP performs perception measurement based on the corresponding perception measurement start time and duration (ie, implementation method 2).

[0275] For example, when AP#1 among N APs determines to perform measurement based on implementation mode 1 based on the first inquiry trigger frame, AP#1 may not read the Start Time field in the first inquiry trigger frame. When AP#1 determines to perform measurement based on implementation mode 2 based on the second inquiry trigger frame, AP#1 needs to read the values ​​of the Start Time field and the Duration field of the User Info field containing its own AID in the second inquiry trigger frame.

[0276] For example, when the first AP triggers AP#1 to perform measurements based on implementation method one by querying trigger frame #1, and the first AP does not indicate the duration of perception measurement to AP#1, the Duration field in the first trigger frame can be set to all 0s.

[0277] It can be understood that S605 in the present application may be referred to as a multi-AP joint sensing stage.

[0278] Optionally, after the N APs' sensing measurements are completed, if the multi-AP joint sensing scenario is scenario one, the method further includes S606 and S607; if the multi-AP joint sensing scenario is scenario two, the method further includes S606 to S608:

[0279] S606: The first AP sends a first report trigger frame to N APs, where the first report trigger frame is used to trigger the N APs to report measurement results of multi-AP joint perception.

[0280] Optionally, the thirteenth information in the first report trigger frame is used to trigger the AP that receives the first report trigger frame to report the measurement result of multi-AP joint perception.

[0281] Optionally, the first report trigger frame includes type information of the perception measurement result, where the type information includes one or more types in the first request frame, and N APs report corresponding measurement results based on the type information.

[0282] For example, the first report trigger frame in the present application can be called a Co-SBP Report Trigger frame.

[0283] Optionally, the Co-SBP Report Trigger frame can reuse the existing Sensing Report Trigger frame, and only a new trigger frame type needs to be added to the Sensing Report Trigger frame, indicating that the Co-SBP ReportTrigger frame is a trigger frame used to trigger the reporting of joint perception results of multiple APs, and at the same time indicates that the AP that receives this frame needs to return the SBP report frame uplink at the same time after a SIFS time interval. Exemplarily, the present application extends a frame type in the SensingTrigger Subtype field of the Trigger Dependent Comment Info field of the Common Info field of the existing Sensing ReportTrigger frame to indicate that the trigger frame is a Co-SBP Report Trigger frame. For example, as shown in Table 3, when the value of the Sensing Trigger Subtype field is 6 (i.e., an example of the thirteenth information), it indicates that the current trigger frame is a Co-SBP Report Trigger frame.

[0284] S607, the N APs send measurement results to the first AP respectively. Correspondingly, the first AP receives measurement results from the N APs.

[0285] S608: The first AP sends measurement results of N APs to the first STA. Correspondingly, the first STA receives the perception measurement results of N APs from the first AP.

[0286] It can be understood that S605 to S608 in the present application may be referred to as a multi-AP joint perception report feedback stage.

[0287] It should be understood that the sequence numbers of the above processes do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0288] It should also be understood that in the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their internal logical relationships.

[0289] It should also be understood that in some of the above embodiments, the devices in the existing network architecture are mainly used as examples for exemplary description, and it should be understood that the embodiments of the present application do not limit the specific form of the devices. For example, devices that can achieve the same function in the future are applicable to the embodiments of the present application.

[0290] It can be understood that in the above-mentioned method embodiments, the methods and operations implemented by the device (such as the Co-Sensing responder, Co-Sensing initiator, etc.) can also be implemented by components of the device (such as chips or circuits).

[0291] Above, combined Figures 1 to 19 The method provided by the embodiment of the present application is described in detail. The above method is mainly introduced from the perspective of the interaction between the Co-Sensing initiator and the Co-Sensing responder. It can be understood that the Co-Sensing initiator and the Co-Sensing responder, in order to achieve the above functions, include hardware structures and / or software modules corresponding to the execution of each function.

[0292] Those skilled in the art should be aware that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0293] The following, combined Fig. 20 and Fig.21 The communication device provided in the embodiment of the present application is described in detail. It should be understood that the description of the device embodiment corresponds to the description of the method embodiment. Therefore, the content not described in detail can refer to the method embodiment above. For the sake of brevity, some contents are not repeated. The embodiment of the present application can divide the functional modules of the Co-Sensing initiator or the Co-Sensing responder according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above-mentioned integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic, which is only a logical functional division. There may be other division methods in actual implementation. The following is an example of dividing each functional module corresponding to each function.

[0294] The above describes in detail the method for data transmission provided by the present application. The following describes the communication device provided by the present application. In one possible implementation, the device is used to implement the steps or processes corresponding to the Co-Sensing responder in the above method embodiment. In another possible implementation, the device is used to implement the steps or processes corresponding to the Co-Sensing initiator in the above method embodiment.

[0295] Fig. 20 is a schematic block diagram of a communication device 200 provided in an embodiment of the present application. Fig. 20 As shown, the device 200 may include a communication unit 210 and a processing unit 220. The communication unit 210 may communicate with the outside, and the processing unit 220 is used for data processing. The communication unit 210 may also be called a communication interface or a transceiver unit.

[0296] In one possible design, the device 200 can implement steps or processes corresponding to those performed by the Co-Sensing initiator in the above method embodiment, wherein the processing unit 220 is used to perform processing-related operations of the Co-Sensing initiator in the above method embodiment, and the communication unit 210 is used to perform sending-related operations of the Co-Sensing initiator in the above method embodiment.

[0297] In another possible design, the device 200 may implement steps or processes corresponding to those performed by the Co-Sensing responder in the above method embodiment, wherein the communication unit 210 is used to perform reception-related operations of the Co-Sensing responder in the above method embodiment, and the processing unit 220 is used to perform processing-related operations of the Co-Sensing responder in the above method embodiment.

[0298] It should be understood that the device 200 here is embodied in the form of a functional unit. The term "unit" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a merged logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art may understand that the device 200 may be specifically the Co-Sensing initiator in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the Co-Sensing initiator in the above-mentioned method embodiment, or the device 200 may be specifically the Co-Sensing responder in the above-mentioned embodiment, and may be used to execute the various processes and / or steps corresponding to the Co-Sensing responder in the above-mentioned method embodiment. To avoid repetition, it will not be repeated here.

[0299] The device 200 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the Co-Sensing initiator in the above-mentioned method, or the device 200 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the Co-Sensing responder in the above-mentioned method. The function can be implemented by hardware, or the corresponding software can be implemented by hardware. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the communication unit can be replaced by a transceiver (for example, the sending unit in the communication unit can be replaced by a transmitter, and the receiving unit in the communication unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor to respectively perform the sending and receiving operations and related processing operations in each method embodiment.

[0300] In addition, the communication unit may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing unit may be a processing circuit. Fig. 20 The device in the embodiment may be the Co-Sensing responder or the Co-Sensing initiator in the aforementioned embodiment, or may be a chip or a chip system, for example, a system on chip (SoC). The communication unit may be an input / output circuit or a communication interface; the processing unit may be a processor or a microprocessor or an integrated circuit integrated on the chip. This is not limited here.

[0301] Fig.21 A schematic block diagram of a communication device 300 provided in an embodiment of the present application. The device 300 includes a processor 310 and a transceiver 320. The processor 310 and the transceiver 320 communicate with each other through an internal connection path, and the processor 310 is used to execute instructions to control the transceiver 320 to send signals and / or receive signals.

[0302] Optionally, the device 300 may also include a memory 330, which communicates with the processor 310 and the transceiver 320 through an internal connection path. The memory 330 is used to store instructions, and the processor 310 can execute the instructions stored in the memory 330. In one possible implementation, the device 300 is used to implement the various processes and steps corresponding to the Co-Sensing initiator in the above method embodiment. In another possible implementation, the device 300 is used to implement the various processes and steps corresponding to the Co-Sensing responder in the above method embodiment.

[0303] It should be understood that the device 300 may be specifically the Co-Sensing initiator or Co-Sensing responder in the above-mentioned embodiment, or it may be a chip or a chip system. Correspondingly, the transceiver 320 may be the transceiver circuit of the chip, which is not limited here. Specifically, the device 300 may be used to execute the various steps and / or processes corresponding to the Co-Sensing initiator or Co-Sensing responder in the above-mentioned method embodiment. Optionally, the memory 330 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory. For example, the memory may also store information about the device type. The processor 310 may be used to execute instructions stored in the memory, and when the processor 310 executes instructions stored in the memory, the processor 310 is used to execute the various steps and / or processes of the above-mentioned method embodiments corresponding to the Co-Sensing initiator or Co-Sensing responder.

[0304] In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here.

[0305] It should be noted that the processor in the embodiment of the present application can be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method embodiment can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general-purpose processor, digital signal processing (digital signal processing, DSP), ASIC, field-programmable gate array (field-programmable gate array, FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The processor in the embodiment of the present application can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to execute, or the hardware and software modules in the decoding processor can be combined and executed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0306] It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0307] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0308] In addition, the present application also provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the operations and / or processes performed by the Co-Sensing initiator or the Co-Sensing responder in each method embodiment of the present application are executed.

[0309] The present application also provides a computer program product, which includes computer program code or instructions. When the computer program code or instructions are run on a computer, the operations and / or processes performed by the Co-Sensing initiator or the Co-Sensing responder in the various method embodiments of the present application are executed.

[0310] In addition, the present application also provides a chip, the chip including a processor. A memory for storing a computer program is provided independently of the chip, and the processor is used to execute the computer program stored in the memory, so that the operation and / or processing performed by the Co-Sensing initiator or the Co-Sensing responder in any one of the method embodiments is executed.

[0311] Furthermore, the chip may further include a communication interface. The communication interface may be an input / output interface, or an interface circuit, etc. Furthermore, the chip may further include a memory.

[0312] In addition, the present application also provides a communication system, including the Co-Sensing initiator and the Co-Sensing responder in the embodiment of the present application.

[0313] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0314] It can be appreciated by a person skilled in the art that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or in combination with computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application. It can be clearly understood by a person skilled in the art that for the convenience and simplicity of description, the specific working process of the system, device and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. In several embodiments provided in this application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the unit is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point, the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms. The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0315] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.

[0316] It should be understood that the "embodiment" mentioned throughout the specification means that the specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, the various embodiments in the entire specification do not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner.

[0317] It should also be understood that the ordinal numbers such as "first" and "second" mentioned in the embodiments of the present application are used to distinguish multiple objects, and are not used to limit the size, content, order, timing, priority or importance of multiple objects.

[0318] It should also be understood that in the present application, "when", "if" and "if" all mean that the network element will take corresponding actions under certain objective circumstances, and do not limit the time, nor do they require the network element to have a judgment action when implementing it, nor do they mean that there are other limitations.

[0319] It should also be understood that in this application, "at least one" means one or more, and "more than one" means two or more. "At least one item" or similar expressions means one or more items, that is, any combination of these items, including any combination of single items or plural items. For example, at least one item of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c.

[0320] It should also be understood that the meaning of expressions similar to "the project includes one or more of the following: A, B, and C" in this application, unless otherwise specified, generally means that the project can be any of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A and A; A, A and B; A, A and C, A, B and B; A, C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B and C. The above is an example of three elements, A, B and C, to illustrate the optional items of the project. When it is expressed as "the project includes at least one of the following: A, B, ..., and X", that is, when there are more elements in the expression, then the items that can be applied to the project can also be obtained according to the above rules.

[0321] It should also be understood that the term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, including A and B, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. For example, A / B means: A or B.

[0322] It should also be understood that in each embodiment of the present application, "A corresponds to B" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0323] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method of sensing, characterized in that: include: The first access point AP sends first request frames corresponding to the N APs to the N APs respectively, where the first request frame is used for the AP to initiate a multi-AP joint proxy perception request, where N is a positive integer; The first AP receives first response frames from the N APs respectively, where the first response frames are used to indicate acceptance of a multi-AP joint proxy perception request.

2. The method according to claim 1, characterized in that The first request frame includes first information, wherein the first information indicates that the first request frame is a request frame for AP to initiate multi-AP joint proxy perception, and the first information is carried in the public function / protected dual public function Public Action / Protected Dualof Public Action field included in the first request frame.

3. The method according to claim 1 or 2, characterized in that: The first request frame includes second information, where the second information includes parameters required for a second AP to perform multi-AP joint proxy perception, and the second AP is an AP that receives the first request frame.

4. The method according to claim 3, characterized in that The parameters required for the second AP to perform multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP collaborative transmission type, trigger-based detection phase type, the required number of perception response sites STA, and whether the number of perception response STAs is required.

5. The method according to any one of claims 1 to 4, characterized in that The first response frame includes third information, the third information indicating that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP, and the third information is carried in the first response frame. The public function / protected dual public function PublicAction / Protected Dual of Public Action field.

6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: The first AP receives a second request frame from the first station STA, where the second request frame is used by the STA to initiate a multi-AP joint proxy perception request; The first AP sends a second response frame to the first STA, where the second response frame indicates acceptance of the multi-AP joint proxy awareness request.

7. The method according to claim 6, characterized in that The second request frame includes fourth information, the fourth information indicating that the second request frame is a request frame for STA to initiate multi-AP joint proxy perception, and the fourth information is carried in the public function / protected dual public function Public Action / Protected Dual of Public Action field included in the second request frame.

8. The method according to claim 6 or 7, characterized in that: The second request frame includes fifth information, and the fifth information includes parameters required for multi-AP joint proxy perception.

9. The method according to claim 8, characterized in that The parameters required for the multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP collaborative transmission type, trigger-based detection phase type, the number of APs required to establish multi-AP joint proxy perception, the required number of APs is required, whether the AP receiving the second request frame needs to perform perception measurement, the required number of perception response STAs, the number of perception response STAs is required, whether the AP receiving the second request frame is recommended for joint proxy perception, whether different multi-AP joint proxy perception parameters are provided for the recommended AP, and whether the first STA needs to participate in the perception measurement.

10. The method according to claim 9, characterized in that When the fifth information indicates that different perception parameters are provided for the recommended APs, the second request frame includes sixth information, and the sixth information includes the perception parameter allocated to each of the recommended APs.

11. The method according to claim 10, characterized in that The sixth information includes one or more of the following parameters allocated to each AP: measurement parameters for sensing, the number of required sensing response STAs, whether the number of sensing response STAs is mandatory, and a trigger-based detection phase type.

12. The method according to any one of claims 6 to 11, characterized in that The second response frame includes seventh information, the seventh information indicating that the second response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by a STA, and the seventh information is carried in the second response frame. The public function / protected dual public function Public Action / Protected Dual of Public Action field.

13. The method according to any one of claims 1 to 12, characterized in that The method further comprises: The first AP triggers the N APs to perform multi-AP joint perception measurement.

14. The method according to claim 13, characterized in that If a second AP among the N APs is not the last AP among the N APs to be triggered to perform perception measurement, the first AP triggers the N APs to perform multi-AP joint perception measurement, including: The first AP determines that the second AP completes the sensing measurement; The first AP sends a first inquiry trigger frame to a third AP among the N APs, where the first inquiry trigger frame is used to trigger the third AP to perform perception measurement, and the third AP is any AP among the N APs that has not been triggered to perform perception measurement; The first AP receives a first inquiry response frame from the third AP.

15. The method according to claim 13, characterized in that The first AP triggers the N APs to perform multi-AP joint perception measurement, including: The first AP sends a second inquiry trigger frame to the N APs, where the second inquiry trigger frame is used to trigger the N APs to perform perception measurement based on their respective corresponding perception measurement start time and duration; The first AP receives second inquiry response frames from the N APs, where the second inquiry response frames indicate that the AP confirms to perform perception measurement based on the corresponding perception measurement start time and duration.

16. The method according to claim 15, characterized in that The second inquiry trigger frame includes eighth information, and the eighth information includes the start time and duration of the perception measurement performed by the N APs.

17. The method according to claim 14, characterized in that The ninth information in the first inquiry trigger frame is used to trigger the AP receiving the first inquiry trigger frame to perform multi-AP joint perception measurement, and the ninth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based public information Trigger Dependent CommentInfo field of the common information field included in the first inquiry trigger frame.

18. The method according to claim 14 or 17, characterized in that The first inquiry trigger frame includes tenth information, and the tenth information instructs the third AP to start performing perception measurement.

19. The method according to claim 15 or 16, characterized in that The eleventh information in the second inquiry trigger frame is used to trigger the N APs to perform multi-AP joint perception measurement, and the eleventh information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the second inquiry trigger frame.

20. The method according to any one of claims 15, 16 and 19, characterized in that: The second inquiry trigger frame includes twelfth information, where the twelfth information instructs the N APs to perform perception measurement based on their respective corresponding perception measurement start time and duration.

21. The method according to any one of claims 6 to 20, characterized in that The method further comprises: The first AP sends a first report trigger frame to the N APs, where the first report trigger frame is used to trigger the N APs to report measurement results of multi-AP joint perception; The first AP receives measurement results from the N APs.

22. The method according to claim 21, characterized in that The method further comprises: The first AP sends the measurement results of the N APs to the first STA.

23. The method according to claim 21 or 22, characterized in that The thirteenth information in the first report trigger frame is used to trigger the AP receiving the first report trigger frame to report the measurement results of multi-AP joint perception, and the thirteenth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based public information TriggerDependent Comment Info field of the common information field included in the first report trigger frame.

24. A method of sensing, characterized in that include: The second access point AP receives a first request frame from the first AP, where the first request frame is used for the AP to initiate a multi-AP joint proxy perception request, and the second AP is any AP among the N APs for which the first AP requests multi-AP joint proxy perception, where N is an integer; The second AP sends a first response frame to the first AP, where the first response frame is used to indicate acceptance of the multi-AP joint proxy perception request.

25. The method according to claim 24, characterized in that The first request frame includes first information, wherein the first information indicates that the first request frame is a request frame for AP to initiate multi-AP joint proxy perception, and the first information is carried in the public function / protected dual public function Public Action / Protected Dual of Public Action field included in the first request frame.

26. The method according to claim 24 or 25, characterized in that The first request frame includes second information, and the second information includes parameters required for the second AP to perform multi-AP joint proxy perception.

27. The method according to claim 26, characterized in that The parameters required for the second AP to perform multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP collaborative transmission type, trigger-based detection phase type, the required number of perception response sites STA, and whether the number of perception response STAs is required.

28. The method according to any one of claims 24 to 27, characterized in that The first response frame includes third information, the third information indicating that the first response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by the AP, and the third information is carried in the first response frame. The public function / protected dual public function Public Action / Protected Dual of Public Action field.

29. The method according to any one of claims 24 to 28, characterized in that The method further comprises: The second AP performs multi-AP joint perception measurement under the triggering of the first AP.

30. The method according to claim 29, characterized in that The second AP performs multi-AP joint sensing measurement under the triggering of the first AP, including: The second AP receives a third inquiry trigger frame from the first AP, where the third inquiry trigger frame is used to trigger the second AP to perform perception measurement; The second AP sends a third inquiry response frame to the first AP.

31. The method according to claim 29, characterized in that The first AP triggers the N APs to perform multi-AP joint perception measurement, including: The second AP receives a second inquiry trigger frame from the first AP, where the second inquiry trigger frame is used to trigger the N APs to perform perception measurements based on their respective corresponding perception measurement start time and duration; The second AP sends a second inquiry response frame to the first AP, where the second inquiry response frame indicates that the second AP confirms to perform the perception measurement based on the corresponding perception measurement start time and duration.

32. The method according to claim 31, characterized in that The second inquiry trigger frame includes eighth information, and the eighth information includes the start time and duration of the perception measurement performed by the N APs.

33. The method according to claim 30, characterized in that The fourteenth information in the third inquiry trigger frame is used to trigger the second AP to perform multi-AP joint perception measurement, and the fourteenth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the first inquiry trigger frame.

34. The method according to claim 30 or 33, characterized in that The third inquiry trigger frame includes fifteenth information, and the fifteenth information instructs the second AP to start performing perception measurement.

35. The method according to claim 31 or 32, characterized in that The eleventh information in the second inquiry trigger frame is used to trigger the N APs to perform multi-AP joint perception measurement, and the eleventh information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based common information Trigger Dependent Comment Info field of the common information field included in the second inquiry trigger frame.

36. The method according to any one of claims 31, 32 and 35, characterized in that: The second inquiry trigger frame includes twelfth information, and the twelfth information indicates that the AP receiving the second inquiry trigger frame performs perception measurement based on the corresponding perception measurement start time and duration.

37. The method according to any one of claims 24 to 36, characterized in that The method further comprises: The second AP receives a first report trigger frame from the first AP, where the first report trigger frame is used to trigger the second AP to report a measurement result of multi-AP joint perception; The second AP sends the measurement result to the first AP.

38. The method according to claim 37, characterized in that The thirteenth information in the first report trigger frame is used to trigger the reception of the second AP to report the measurement result of the multi-AP joint perception, and the thirteenth information is carried in the perception trigger subtype Sensing Trigger Subtype field of the trigger-based public information Trigger Dependent Comment Info field of the common information field included in the first report trigger frame.

39. A method of sensing, characterized in that include: The first station STA sends a second request frame to the first access point AP, where the second request frame is used by the STA to initiate a multi-AP joint proxy perception request; The first STA receives a second response frame from the first AP, where the second response frame indicates acceptance of the multi-AP joint proxy awareness request.

40. The method according to claim 39, characterized in that The second request frame includes fourth information, the fourth information indicating that the second request frame is a request frame for STA to initiate multi-AP joint proxy perception, and the fourth information is carried in the public function / protected dual public function Public Action / Protected Dual of Public Action field included in the second request frame.

41. The method according to claim 39 or 40, characterized in that The second request frame includes fifth information, and the fifth information includes parameters required for multi-AP joint proxy perception.

42. The method according to claim 41, characterized in that The parameters required for the multi-AP joint proxy perception include one or more of the following parameters: expiration time of multi-AP joint perception, multi-AP collaborative transmission type, trigger-based detection phase type, the number of APs required to establish multi-AP joint proxy perception, the required number of APs is required, whether the AP receiving the second request frame needs to perform perception measurement, the required number of perception response STAs, the number of perception response STAs is required, whether the AP receiving the second request frame is recommended for joint proxy perception, whether different multi-AP joint proxy perception parameters are provided for the recommended AP, and whether the first STA needs to participate in the perception measurement.

43. The method according to claim 42, characterized in that When the fifth information indicates that different perception parameters are provided for the recommended APs, the second request frame includes sixth information, and the sixth information includes the perception parameter allocated to each of the recommended APs.

44. The method according to claim 43, characterized in that The sixth information includes one or more of the following parameters allocated to each AP: measurement parameters for sensing, the number of required sensing response STAs, whether the number of sensing response STAs is mandatory, and a trigger-based detection phase type.

45. The method according to any one of claims 39 to 44, characterized in that The second response frame includes seventh information, the seventh information indicating that the second response frame is a response frame for responding to a multi-AP joint proxy perception request initiated by a STA, and the seventh information is carried in the second response frame. The public function / protected dual public function Public Action / Protected Dual of Public Action field.

46. ​​The method according to any one of claims 39 to 45, characterized in that The method further comprises: The first STA receives a measurement result of multi-AP joint perception from the first AP.

47. A communication device, characterized in that: A method comprising a module or unit for executing any one of claims 1 to 23, or a module or unit for executing any one of claims 24 to 38, or a module or unit for executing any one of claims 39 to 46.

48. A communication device, characterized in that: The device comprises at least one processor and a communication interface, wherein the communication interface is used to input and / or output signals, and the at least one processor is used to execute a computer program stored in a memory so that the communication device implements the method as described in any one of claims 1 to 23, or implements the method as described in any one of claims 24 to 38, or implements the method as described in any one of claims 39 to 46.

49. A processing device, characterized in that The device comprises a processor configured to execute a computer program stored in a memory so that the device implements the method according to any one of claims 1 to 23, or implements the method according to any one of claims 24 to 38, or implements the method according to any one of claims 39 to 46.

50. A processing device, characterized in that include: Memory for storing computer programs; A processor, configured to call and run the computer program from the memory so that the apparatus implements the method as claimed in any one of claims 1 to 23, or implements the method as claimed in any one of claims 24 to 38, or implements the method as claimed in any one of claims 39 to 46.

51. A computer readable medium, characterized in that The method comprises a computer program, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 38, or the method according to any one of claims 39 to 46.

52. A computer program product, comprising a computer program, which, when executed on a computer, enables the computer to execute the method according to any one of claims 1 to 23, or the method according to any one of claims 24 to 38, or the method according to any one of claims 39 to 46.

Images