fix(dp): Unregister CBSD on SAS response 105

[xbend]

Fixed an issue where a CBSD state remained "registered" when SAS
returned a response with reponseCode 105.
Response code 105 means the CBSD got unregistered in SAS and should
consider itself "Unregistered".
This PR changes the CBSD state to "unregistered" when any SAS response
is a 105 code.

Signed-off-by: Artur Dębski artur.debski@freedomfi.com

Summary

• Set CBSD state to "Unregistered" on each SAS response that has the responseCode 105.

Additional Information

• This change is backwards-breaking

[github-actions]

Thanks for opening a PR! 💯

A couple initial guidelines

• All commits must be signed off. This is enforced by DCO check.
• All PR titles must follow the semantic commits format. This is enforced by Semantic PR.

Howto

• Reviews. The "Reviewers" listed for this PR are the Magma maintainers who will shepherd it.
• Checks. All required CI checks must pass before merge.
• Merge. Once approved and passing CI checks, use the ready2merge label to indicate the maintainers can merge your PR.

More info

Please take a moment to read through the Magma project's

• Contributing Conventions for norms around contributed code

If this is your first Magma PR, also consider reading

• Developer Onboarding for onboarding as a new Magma developer
• Development Workflow for guidance on your first pull request
• CI Checks for points of contact for failing or flaky CI checks
• GitHub-to-Slack mappings for Magma maintainers for guidance on how to contact maintainers on Slack

[jkmar]

One question:
Does that mean SAS can respond with 105 code on any type of request (not just Deregistration)?
I also wonder if there are any certification tests for that

[xbend]

@jkmar

One question: Does that mean SAS can respond with 105 code on any type of request (not just Deregistration)? I also wonder if there are any certification tests for that

According to WINNF-TS-0016, error codes 1XX are general errors related to the SAS-CBSD protocol. Documentation does not explicitly specify that those errors can occur on any request type, but that's the assumption - as SAS can internally deregister a CBSD at any time. Any CBSD that's communicating with SAS that has some sort of state, can issue any request according to their state machine, and SAS should/will respond exactly with error 105 indicating that the CBSD has been deregistered.

FreedomFi environment got this error initially on a heartbeat response for a CBSD, and then got the same error subsequently on each spectrum inquiry that followed after.

Certification testing documentation WINNF-TS-0122 has only 1 test case WINNF.FT.C.HBT.3 which targets handling of response code 105 for hearbeat requests, however section 6.7.1 about CBSD deregistration process says:

Deregistrations triggered by the SAS in a response message with a responseCode of
105 are covered in other test cases.