Overview
What this challenge is about.
Receive the current transport architecture (P4-programmable switches, ONOS controller cluster), the 3 customer-class SLAs (consumer: best-effort 50 Mbps; enterprise IoT: 5 Mbps guaranteed; manufacturing: 100 Mbps + <2ms one-way latency), and 2 weeks of traffic captures. Design an SDN slicing policy using flow rules + queue assignment + meter tables. Build a Mininet topology (8 switches + 12 hosts) with the real ONOS controller, implement the slicing app, and run a contention experiment: saturate the link with consumer traffic and prove the manufacturing slice still meets latency. Deliver the ONOS application code (Java), the Mininet topology script, the contention-experiment report, and a 5-page policy memo for the transport-engineering director.
The Brief
What you'll do, and what you'll demonstrate.
Design and prototype SDN-based network slicing that enforces 3 distinct customer SLAs under contention on an ONOS-controlled transport network.
Earning criteria — what you'll demonstrate
- Implement an SDN application against a real controller's northbound API
- Translate customer SLAs into concrete flow rules + meter configurations
- Validate slice isolation under contention with reproducible experiments
- Communicate slicing trade-offs to a network-engineering audience
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.