# US 12,016,081 B2 · Method of reporting received signal strength on per frame basis in Wi-Fi network > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,016,081 B2 - Document ID: US12016081B2 - Status: Granted - Kind: B2 - Application number: 18/077,437 - Filed: 2022-12-08 - Published: 2023-04-06 - Granted: 2024-06-18 - Earliest claimed: 2020-06-08 - Assignees: ARRIS Enterprises LLC - Applicants: ARRIS Enterprises LLC - Inventors: Kurt Alan Lumbatis; Mark Hamilton - Web page: https://patentgrep.com/patent/US12016081B2 ## CPC - H04L 1/1614: {using bitmaps} - H04W 8/24: Transfer of terminal data - H04B 17/336: Signal-to-interference ratio [SIR] or carrier-to-interference ratio [CIR] - H04L 1/0008: {by supplementing frame payload, e.g. with padding bits} - H04L 1/0026: {Transmission of channel quality indication} - H04L 1/0028: {Formatting} - H04L 1/1607: Details of the supervisory signal - H04L 5/0044: {Allocation of payload; Allocation of data channels, e.g. PDSCH or PUSCH} - H04L 5/0055: {Physical resource allocation for ACK/NACK (for physical mapping arrangements in ARQ protocols H04L1/1861)} - H04L 69/22: Parsing or analysis of headers - H04W 24/10: Scheduling measurement reports {; Arrangements for measurement reports} - H04W 76/10: Connection setup - H04W 84/12: WLAN [Wireless Local Area Networks] - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04B: TRANSMISSION ## Abstract Aspects of the present disclosure are drawn to a client device for use with an access point device. The client device includes: a memory; and a processor configured to execute instructions stored on the memory to cause the client device to: obtain a value associated with a capability of the client device, create a response including a header and a payload, the header including a reserved field including a bit reporting that the payload of the response includes the value associated with the capability, and transmit the response to the APD. ## Claims ### Claim 1 An access point device for determining that a client device supports one or more capabilities, the access point device comprising: a memory; and a processor configured to execute one or more instructions stored on the memory to cause said client device to: generate an Add Block Ack (ADDBA) request frame, wherein the ADDBA request frame comprises an ADDBA capabilities field; transmit the ADDBA request frame to the client device to establish a Block Ack session; receive an ADDBA response frame from the client device based on the ADDBA request frame, wherein the ADDBA response frame comprises a value associated with a capability of the client device; and determine that the client device supports the one or more capabilities based on the ADDBA response frame, wherein at least one of the one or more capabilities indicate that the client device is capable of reporting channel condition. ### Claim 2 (depends on 1) The access point device of claim 1, wherein the ADDBA request frame comprises an ADDBA extension element that includes the ADDBA capabilities field. ### Claim 3 (depends on 1) The access point device of claim 1, wherein the ADDBA extension element comprises an element identifier describing a type of element, a length of the ADDBA capabilities field, and the ADDBA capabilities field. ### Claim 4 (depends on 1) The access point device of claim 1, wherein the ADDBA capabilities field specifies whether the client device is capable of reporting one or more channel power measurements. ### Claim 5 (depends on 1) The access point device of claim 1, wherein the ADDBA response frame includes a Block Ack header and a Block Ack payload, wherein the value associated with the capability of the client device resides in a Block Ack information field of the Block Ack payload. ### Claim 6 (depends on 5) The access point device of claim 5, wherein the processor is further configured to execute the one or more instructions stored on the memory to additionally cause the access point device to: obtain as the value of the capability of the client device in the Block Ack information field of the Block Ack payload a received channel power indicator indicative of radio frequency power received on a channel by the client device. ### Claim 7 (depends on 5) The access point device of claim 5, wherein the processor is further configured to execute the one or more instructions stored on the memory to additionally cause the access point device to: obtain as the value of the capability of the client device in the Block Ack information field of the Block Ack payload a received signal-to-noise indicator indicative of noise received on a channel by the client device. ### Claim 8 A method for an access point device to determine that a client device supports one or more capabilities, the method comprising: generating an Add Block Ack (ADDBA) request frame, wherein the ADDBA request frame comprises an ADDBA capabilities field; transmitting the ADDBA request frame to the client device to establish a Block Ack session; receiving an ADDBA response frame from the client device based on the ADDBA request frame, wherein the ADDBA response frame comprises a value associated with a capability of the client device; and determining that the client device supports the one or more capabilities based on the ADDBA response frame, wherein at least one of the one or more capabilities indicate that the client device is capable of reporting channel condition. ### Claim 9 (depends on 8) The method of claim 8, wherein the ADDBA request frame comprises an ADDBA extension element that includes the ADDBA capabilities field. ### Claim 10 (depends on 8) The method of claim 8, wherein the ADDBA extension element comprises an element identifier describing a type of element, a length of the ADDBA capabilities field, and the ADDBA capabilities field. ### Claim 11 (depends on 8) The method of claim 8, wherein the ADDBA capabilities field specifies whether the client device is capable of reporting one or more channel power measurements. ### Claim 12 (depends on 8) The method of claim 8, wherein the ADDBA response frame includes a Block Ack header and a Block Ack payload, wherein the value associated with the capability of the client device resides in a Block Ack information field of the Block Ack payload. ### Claim 13 (depends on 12) The method of claim 12, the method further comprising: obtaining as the value of the capability of the client device in the Block Ack information field of the Block Ack payload a received channel power indicator indicative of radio frequency power received on a channel by the client device. ### Claim 14 (depends on 12) The method of claim 12, the method further comprising: obtaining as the value of the capability of the client device in the Block Ack information field of the Block Ack payload a received signal-to-noise indicator indicative of noise received on a channel by the client device. ### Claim 15 A non-transitory computer-readable medium of an access point device storing one or more instructions for determining that a client device supports one or more capabilities, which when executed by a processor of the access point device, cause the access point device to perform one or more operations comprising: generating an Add Block Ack (ADDBA) request frame, wherein the ADDBA request frame comprises an ADDBA capabilities field; transmitting the ADDBA request frame to the client device to establish a Block Ack session; receiving an ADDBA response frame from the client device based on the ADDBA request frame, wherein the ADDBA response frame comprises a value associated with a capability of the client device; and determining that the client device supports the one or more capabilities based on the ADDBA response frame, wherein at least one of the one or more capabilities indicate that the client device is capable of reporting channel condition. ### Claim 16 (depends on 15) The non-transitory, computer-readable medium of claim 15, wherein at least one of: the ADDBA request frame comprises an ADDBA extension element that includes the ADDBA capabilities field; and the ADDBA extension element comprises an element identifier describing a type of element, a length of the ADDBA capabilities field, and the ADDBA capabilities field. ### Claim 17 (depends on 15) The non-transitory, computer-readable medium of claim 15, wherein the ADDBA capabilities field specifies whether the client device is capable of reporting one or more channel power measurements. ### Claim 18 (depends on 15) The non-transitory, computer-readable medium of claim 15, wherein the ADDBA response frame includes a Block Ack header and a Block Ack payload, wherein the value associated with the capability of the client device resides in a Block Ack information field of the Block Ack payload. ### Claim 19 (depends on 18) The non-transitory, computer-readable medium of claim 18, wherein the one or more instructions when executed by the processor further cause the access point device to further perform the one or more operations comprising: obtaining as the value of the capability of the client device in the Block Ack information field of the Block Ack payload a received channel power indicator indicative of radio frequency power received on a channel by the client device. ### Claim 20 (depends on 18) The non-transitory, computer-readable medium of claim 18, wherein the one or more instructions when executed by the processor further cause the access point device to further perform the one or more operations comprising: obtaining as the value of the capability of the client device in the Block Ack information field of the Block Ack payload a received signal-to-noise indicator indicative of noise received on a channel by the client device.