I did identify an intermittently elevated noise floor within the CBRS spectrum range of 3555-3600 MHz, which has been causing occasional communication disruptions, including loss of heartbeat events on autonomous vehicles. It does not appear to be another CBSD , but could be, based on what I am seeing on the RAN spectrum analyzer, or perhaps spurious out of band transmissions.
As part of troubleshooting, I attempted to move operations to the upper portion of the CBRS band on the affected eNB. However, the spectrum grants consistently entered IAP suspension status and did not appear to clear, even after several hours. How can I open a support ticket on this issue to determine what the cause is?
Given that the grants remain in IAP Pending for several hours, I’d definitely open a case with the SAS provider rather than continuing to recreate or modify the eNB.
The key information I’d include is the CBSD/eNB ID, grant IDs, exact 3555–3600 MHz frequencies, timestamps, heartbeat responses and responseCode/responseData, especially any 501 SUSPENDED_GRANT: IAP Pending messages. Those details should help the SAS team determine whether the suspension is related to CPAS/DPA protection, interference calculations, or another backend condition.
It may also be worth checking the grant history in the SAS portal and the exact suspension reason. Google’s documentation specifically recommends contacting SAS Support when a grant remains suspended beyond the expected interference-calculation period or remains suspended after CPAS.