tree 5502440e96547430b0425a07c5768cb2f42dd718
parent ccdad74d78729932f94fccfcc2dd80b288fa831e
author Kai Shi <kaishi@google.com> 1609789496 -0800
committer Kai Shi <kaishi@google.com> 1609790253 -0800

Improve the handling of assoc rejection due to AP's reasons

Some association rejection events happen due to AP's reasons. This includes the following status codes
17: DENIED_NO_MORE_STAS (aka AP_UNABLE_TO_HANDLE_NEW_STA).
30: REFUSED_TEMPORARILY
33: DENIED_INSUFFICIENT_BANDWIDTH

The association rejection due to the above reasons
1) should be counted separately from other reasons for wifi metric report purpose.
2) shouldn't trigger bug report or be counted as abnormal assoc rejection failure in wifi health monitor.

For the simplicity, all above assoc rejection events are flagged as the internal level2 failure reason code AP_UNABLE_TO_HANDLE_NEW_STA so that they are treated in the same way in BssidBlocklistMonitor and WifiScoreCard.

Bug: 176412894
Test: atest com.android.server.wifi
Change-Id: I8068861c731f1b13e43917994ad67e7305f45a27