How to Integrate Release 2 Extensions (WINNF-TS-3002)

This guide explains how to upgrade from Release 1 (WINNF-TS-0016) to Release 2 features defined in WINNF-TS-3002.

Overview

Release 2 introduces optional enhancements for better efficiency, advanced grouping, and future-proofing:

• Enhanced CBSD Group Handling (mandatory for new groupings)
• Feature capability exchange
• Additional optional parameters and objects

Key Bridge SAS Support: We fully support Release 2. Existing Release 1 implementations continue to work, but enabling Release 2 features can improve grant approval rates and coordination.

Prerequisites

• Working Release 1 implementation (registration → grant → heartbeat)
• Review WINNF-TS-3002 and WINNF-SSC-0010 (updated grouping)

Step 1: Declare Release 2 Capabilities (Optional but Recommended)

Add cbsdCategory and featureCapability in RegistrationRequest.

Example

{
  "registrationRequest": [
    {
      "cbsdId": "...",  // omit for first registration
      "cbsdCategory": "B",  // "A" or "B"
      "featureCapability": [
        "ENHANCED_GROUP_HANDLING"
      ],
      // ... existing params
      "groupingParam": [ /* enhanced groups */ ]
    }
  ]
}

Step 2: Use Enhanced Grouping (Primary Benefit)

Release 2 formalizes grouping with GroupConfig response and error handling.

• Use same groupingParam as before
• SAS may return GroupConfig in RegistrationResponse or HeartbeatResponse with configuration details

Example GroupConfig Response

{
  "groupConfig": [
    {
      "groupType": "INTERFERENCE_COORDINATION",
      "groupId": "MyNetwork-Site1",
      "groupConfigInfo": { /* SAS-specific config */ }
    }
  ]
}

Tip: Enhanced grouping + measurements often yields higher aggregate EIRP in dense deployments.

Step 3: Handle New Optional Objects

• clientCapability: Declare additional features (future use)
• groupInfoResponseCode: Better error feedback on grouping issues
• Updated measReportConfig handling

Migration Strategy

1. Continue Release 1 Flow: Your existing code works unchanged
2. Add cbsdCategory: Required for some Release 2 features
3. Enable featureCapability: Start with "ENHANCED_GROUP_HANDLING"
4. Update Grouping: Use consistent groupType/groupId across all devices
5. Test: Use sandbox → verify GroupConfig returns and improved grants

Best Practices & Tips

• Enable Release 2 gradually (per site or cluster)
• Combine with measurements for maximum benefit
• Monitor for GroupConfig — may include SAS-specific optimization hints
• No need to change endpoints or TLS — same v1.2 API
• Key Bridge SAS: Release 2 users often see 10-30% better spectrum utilization in coordinated networks

Common Issues & Troubleshooting

Next Steps

• Update firmware to declare Release 2 capabilities
• Test in sandbox with grouping + measurements enabled
• Monitor grant maxEirp improvements