How to Prepare for WInnForum Certification Testing

This guide outlines the process to prepare for and pass WInnForum conformance and performance testing for CBSD/DP implementations, as defined in WINNF-TS-0122.

Overview

WInnForum certification (via WINNF-TS-0122) is required for commercial deployment in the CBRS band. It verifies protocol compliance, security, and performance against the SAS-CBSD interface.

Key Bridge SAS Note:

We recommend completing this certification early. Many issues surface during formal testing that are not apparent in sandbox or health endpoint checks.

Prerequisites

Fully implemented Release 1 (or Release 2) SAS-CBSD protocol
Valid CBSD certificates from WInnForum-approved CA
Test environment with certified test harness or accredited test lab
Access to WInnForum test cases (available to members)

Step 1: Self-Test Against WINNF-TS-0122

Review test categories in WINNF-TS-0122:

Category	Focus Areas	Common Pitfalls
Registration	Required/optional params, error codes	Missing installationParam (Cat B)
Spectrum Inquiry	Frequency ranges, measurements	No measReport when configured
Grant / Relinquishment	OperationParam, partial grants	Ignoring reduced maxEirp
Heartbeat	Directives (suspend/terminate), timers	Missing early heartbeat
Deregistration	Clean removal	Not persisting cbsdId
Security	TLS 1.2+, mutual auth, certificate validation	Wrong trust chain
Performance	Latency, throughput, batch handling	Large batches >512 entries
Grouping & Measurements	Release 2 features (if claimed)	Inconsistent groupId

Tip: Use a local SAS simulator (open-source or vendor) to run test cases before formal submission.

Step 2: Set Up Formal Test Environment

Obtain access to accredited test lab (e.g., Intertek, Keysight, or WInnForum-approved)
Use certified test harness (automated scripts)
Provide test CBSD/DP with production-like config

Step 3: Common Test Failure Areas & Fixes

Failure Area	Typical Cause	Fix
Blacklist/Invalid Cert	Wrong CA chain or expired cert	Use fresh WInnForum PKI cert
Missing Parameters	Omitted installationParam or measCapability	Make all required fields mandatory
Ignoring Directives	No immediate power/frequency change	Implement real-time radio adjustment
Batch Size Errors	>512 entries (Key Bridge limit)	Cap at 100–200; split batches
Measurement Non-Compliance	Not sending when configured	Always include measReport when requested
Heartbeat Timeout	No early send, no jitter	Send 5-10s before interval + random jitter

Best Practices & Tips

Run all test cases locally first
Fix errors one category at a time
Log every request/response during testing
Test edge cases: DPA simulation, high interference, batch failures
Keep cbsdId persistent across test runs
Key Bridge SAS: Our sandbox mirrors production limits (e.g., 512 entries, 10 MHz blocks)

Next Steps

Schedule test lab session
Run self-tests against WINNF-TS-0122
Fix all failures before formal submission