How to Use Grouping Parameters

This guide explains how to implement grouping parameters in CBRS deployments as defined in WINNF-TS-0016 and WINNF-SSC-0010.

Overview

Grouping parameters allow a CBSD to inform the SAS that it belongs to a logical group of devices. This enables the SAS (or the group itself) to apply coordinated interference management, potentially improving spectrum availability, EIRP limits, or channel stability.

Key benefits:

• Better protection/coordination within your own network
• Potential for higher power or more reliable channels
• Support for advanced topologies (e.g., single-frequency networks, spectrum reuse)

Grouping is declared during registration and can be updated if needed.

Important Note for Key Bridge SAS Users:

Measurement reporting is always requested by our SAS (via measReportConfig), but sending measurements remains optional. We strongly encourage it because accurate received power reports help us:

• Allocate better spectrum (higher EIRP, more channels)
• Diagnose and mitigate interference issues faster
• Improve overall network performance for you and nearby users

Prerequisites

• Review recognized grouping types in WINNF-SSC-0010
• Decide which group type fits your deployment
• Ensure all CBSDs in the same group use identical groupType and groupId

Step 1: Choose a Grouping Type

Common recognized types (as of WINNF-SSC-0010 v4.2.0):

Tip: Start with INTERFERENCE_COORDINATION if unsure — it's flexible and widely supported.

Step 2: Include groupingParam in RegistrationRequest

Add the groupingParam array (one or more groups per CBSD).

Example: Interference Coordination Group

{
  "registrationRequest": [
    {
      "userId": "user@example.com",
      "fccId": "ABC123",
      "cbsdSerialNumber": "SN456789",
      "measCapability": [
        "RECEIVED_POWER_WITHOUT_GRANT",
        "RECEIVED_POWER_WITH_GRANT"
      ],
      "installationParam": {
        // ... installation details
      },
      "groupingParam": [
        {
          "groupType": "INTERFERENCE_COORDINATION",
          "groupId": "MyNetwork-SiteA-Cluster1"
        }
      ]
    }
  ]
}

Example: Multiple Groups (e.g., Spectrum Reuse + Passive DAS)

"groupingParam": [
  {
    "groupType": "SPECTRUM_REUSE",
    "groupId": "Enterprise-Campus-ReuseGroup-01"
  },
  {
    "groupType": "PASSIVE_DAS",
    "groupId": "ABC123:SN456789:Chain-1"
  }
]

Step 3: Handle SAS Response

SAS may return group configuration or error codes in GroupConfig (Release 2) or via response codes.

With Key Bridge SAS:

• We accept all valid recognized grouping types
• Grouping often unlocks higher EIRP or more stable channels
• Combined with optional measurement reports, grouping gives us the best data to optimize your deployment

Best Practices & Tips

• Use meaningful, unique groupId values (include site, cluster, or customer identifiers)
• Apply the same group parameters to all CBSDs in the logical group
• Combine grouping with measurement reporting for maximum benefit
• For large deployments, coordinate groupIds with your SAS administrator in advance
• Re-register if group membership changes (SAS may require it)

Common Issues & Troubleshooting

Next Steps

• Test grouping in a small cluster first
• Monitor grant maxEirp and channel stability after enabling
• Contact support if you want recommendations for your specific topology