\nAre you aware that Google\u00c2\u00b4s Open Source radio protocol on 6LoWPAN will support frequency hopping?
\n<\/span><\/span><\/p>\n
Text out of <\/span><\/span>ETSI ERM TG11 #23 Meeting<\/h3>\nChannel Access Mechanism (CAM)<\/h3>\n
It was decided that TG11 members should now concentrate and prepare contributions on the CAM rather than to continuing influencing the MU formula and it\u00e2\u20ac\u2122s limit.<\/p>\n
Duty cycle for hoppers<\/h3>\n
Changes on the observation time for adaptive systems (from 1s to 40s -> this means 1s for non-hoppers and 40s for hoppers). The observation time should be different to the non-adaptive. The revision of the duty cycle section is to be done offline (by correspondence). The objective is to cover duty cycle and TX-on\/TX-off times in this section. The terms TX-on\/TX-off should not be used.<\/p>\n
Hopping frequency separation<\/h3>\n
Reduce the separation (0.1MHz) in order to make use of the gaps between channels. This is only for adaptive systems.<\/p>\n
Adaptive Frequency Hopping<\/h3>\n
Many questions about how to treat that equipment which falls below the MU threshold. The question is what happens with the adaptive systems when going below the [10%] (should it remain adaptive?). Adaptive Frequency Hopping with DAA (Detect and Avoid),<\/p>\n
Adaptive Frequency Hopping with Blacklisting<\/h3>\n
For further review.<\/p>\n
Source: ![\"\"](\"https:\/\/www.xing.com\/img\/n\/outlink.gif\")
<\/a>https:\/\/mentor.ieee.org\/802.11\/dcn\/10\/11-10-0024-00-0reg-sum…<\/a><\/p>\n
<\/a>https:\/\/mentor.ieee.org\/802.11\/dcn\/10\/11-10-0024-00-0reg-sum…<\/a><\/p>\n