How to Integrate Release 2 Extensions

This guide explains how to incorporate Release 2 features from WINNF-TS-3002 (Extensions to SAS-CBSD Interface) into a CBSD implementation that already supports Release 1 (WINNF-TS-0016).

Overview

Release 2 introduces optional enhancements for more advanced deployments, including:

• Feature capability exchange
• Enhanced grouping handling
• Group configuration from SAS
• Additional measurement and reporting options
• Improved error handling and response objects

These are backward compatible—Release 1 CBSDs can still operate with Release 2 SASs.

Prerequisites

• Working Release 1 implementation (registration, inquiry, grant, heartbeat, etc.)
• CBSD firmware capable of declaring new capabilities
• SAS that supports Release 2 (e.g., Key Bridge SAS)

Step 1: Declare Release 2 Feature Support

During registration, include the featureCapability parameter (new in Release 2) in registrationRequest.

Supported Values (partial list from WINNF-TS-3002)

Example in RegistrationRequest

{
  "registrationRequest": [
    {
      "userId": "user@example.com",
      "fccId": "ABC123",
      "cbsdSerialNumber": "SN456789",
      "measCapability": [
        "RECEIVED_POWER_WITHOUT_GRANT",
        "RECEIVED_POWER_WITH_GRANT"
      ],
      "featureCapability": [
        "ENHANCED_GROUP_HANDLING",
        "GROUP_CONFIG_RESPONSE"
      ],
      "installationParam": {
        // ... installation details
      }
    }
  ]
}

Tip: Only declare features your CBSD fully implements to avoid SAS expecting unsupported behavior.

Step 2: Handle Group Configuration from SAS

If you declared ENHANCED_GROUP_HANDLING or GROUP_CONFIG_RESPONSE, SAS may return groupConfig array in registrationResponse or heartbeatResponse.

Example Response Fragment

{
  "registrationResponse": [
    {
      "cbsdId": "SAS123/CBSD-001",
      "groupConfig": [
        {
          "groupType": "INTERFERENCE_COORDINATION",
          "groupId": "MyNetwork-SiteA-Cluster1",
          "groupConfigInfo": {
            // SAS-provided configuration (type-specific)
          }
        }
      ],
      "response": {
        "responseCode": 0
      }
    }
  ]
}

Implementation Steps

• Parse groupConfig array
• Apply any SAS-provided rules (e.g., intra-group power coordination)
• Acknowledge in next heartbeat (if required)

Step 3: Use Enhanced Grouping Parameters

Release 2 allows more detailed groupingParam objects and better SAS validation.

• Include multiple groups per CBSD
• Add GroupInfo object where defined (e.g., for PRINCIPAL_SUBORDINATE_SFG)

Example

"groupingParam": [
  {
    "groupType": "PRINCIPAL_SUBORDINATE_SFG",
    "groupId": "SFG-Cluster-001",
    "groupInfo": {
      "cbssType": "PRINCIPAL"
    }
  }
]

Best Practices & Tips

• Start by declaring only one new feature (e.g., ENHANCED_GROUP_HANDLING) and test thoroughly
• Log all received groupConfig objects for debugging
• If SAS returns unexpected groupConfig, fall back gracefully (ignore unsupported fields)
• Combine with measurement reporting—Release 2 SASs often use both to optimize grants
• Re-register after firmware update to advertise new capabilities

Common Issues & Troubleshooting

Next Steps

• Test with Key Bridge SAS sandbox (contact support)
• Monitor grant improvements (higher EIRP, more channels) after enabling
• Consider adding Release 2-only measurements if your hardware supports