| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hi Rojan, I want to elaborate on your concerns:
Responses 1. We need it for several reasons, the first one being to control a non-collocated AMP Energizer via BLE or UART connections. 2. In relation to the 802.11 [IEEE P802.11-REVmf/D2.0, February 2026]: The Vendor Specific element is defined in 9.4.2.24 The Vendor Specific element is used to carry information not defined in this standard so that interoperability is achieved in the presence of nonstandard information. The example below shows how this element is used in an IoT hub to communicate using 802.11 protocol on one side and non-802.11 protocols on the other side (UART, BLE, Zigbee, etc.). The general flow is as follows: 802.11 Action Frame (Vendor IE) An IoT hub is a multi-protocol gateway that:
In this case, the hub is the bridge that makes this work: 802.11 Action Frame (Vendor IE) An example of the products where this approach can be deployed:
These are the kinds of payloads that make sense given:
Used for Parameter Updates / Tuning What is delivered: Operational parameters Example payloadTYPE=CONFIGID=sensor_123THRESHOLD=75INTERVAL=10Best Regards, Solomon Trainin +972547885738 To unsubscribe from the STDS-802-11-TGBP list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-11-TGBP&A=1 |