5G SBP Use Case - 5G: Quality on demand
- Amit Surana
Use this template to submit Use Cases for submission to the 5G Super Blueprint Use Case & Requirements Advisory Group. All input marked Mandatory is required for the blueprint use case proposal to be deemed ready for review by the Use Case & Requirements Advisory Group.
Use Case Name: | 5G : Quality on demand |
|
|---|---|---|
Use Case Description: |
Quality on Demand offers the application developer the capability to request stable latency (reduced jitter) or minimum throughput for specified application data flows between application clients (within a user device) and Application Servers (backend services) End Users or applications can request specific network quality levels depending on their current activity, enabling optimal performance for diverse scenario. Scenario Examples: Remote control of machines and vehicles (e.g. Automated Guided Vehicles, drones, robotic arms, factory production lines) require stable data throughput and low latency to ensure secure and efficient operations Media and entertainment (e.g. online gamers and viewers of real-time streaming) require a network with a high level of performance to ensure good user experience. Computer vision and remote video processing applications (e.g. sending a continuous video stream to their backends for processing) require stable data throughput and low latency to generate time-sensitive outputs, such as alarms and events for computer vision, or a produced video stream for their audience (Reference: GSMA) |
|
-Epic -Problem Statement | Traditional systems lack the real-time ability to measure and adjust quality metrics effectively. Even though we can monitor basic network health indicators (like latency or throughput), we have no way of dynamically requesting Quality of Service from network dependent on current traffic scenario. |
|
Blueprint Owner | Amit Surana |
|
Users Stories |
|
|
Interaction with other open source projects and components |
|
|
Resources -people | Resources (people) to execute on the blueprint:
|
|
Steps to Realization |
|
|
High-level architecture diagram |  |
|
High level lab topology diagram |
| |
Dependencies - list of any dependencies that rely of future releases of a specfic component. | Yes
or No |
|
High-level timeline |
|
|
Upstreaming Opportunities |
|
|
Blueprint Outputs (Suggested. Not all may apply) | check all that apply: Code repository Configuration files (e.g. Helm charts, etc.) Upstreaming to relevant projects Continuous Integration Test requirements and test results (if applicable) Documentation: Overview and Theory of Operation (i.e., what does it do?) Deployment and setup Videos demo lab setup/behind the scenes other |
|
Links to existing documentation (Build Guide, Slideware, etc), if available. |
| |
Links to existing demo/video, if available. |
| |
Links to existing code/repos, if available. |
|