THE LINUX FOUNDATION PROJECTS

QoS Profiles

API Description
Use Cases

QoS Profiles helps businesses choose and offer the right network experience before they request it through Quality on Demand or the other CAMARA connectivity quality management APIs. Developers don’t use QoS Profiles on its own. They use it as part of an API such as Quality On Demand which names a QoS profile for the level of service it requests.

  • Live Event Broadcasting: A broadcaster checks which high-throughput uplink profiles are available to its camera crews at a venue, so it can plan a live production stable broadcst.
  • Cloud Gaming and VR: A game service checks which low-latency profiles a player’s device can get, and offers a “pro mode” upgrade to players.
  • Telehealth Consultations: A telemedicine app selects a stable-latency profile for video consultations and remote monitoring, so clinicians get consistent quality.
  • Premium Video Calling: A communications platform offers an “HD call” upgrade backed by a profile that prioritizes voice and video traffic, and turns quality into a product it can sell.
  • Enterprise and Industrial Operations: A manufacturer or logistics company matches profiles to each workload, such as stable latency for machine control and high throughput for video inspection.
Benefits
  • One Integration, many Networks: Every operator publishes its profiles describes them with the same characteristics. One application can find the right profile on any operator that supports CAMARA, without network-specific parameters or hard-coded profile names.
  • Faster Time to Market: Teams don’t have to negotiate or learn each operator’s network settings, so quality-enhanced features ship sooner.
  • Predictable Experience as a Product Feature: Clear, named performance levels let businesses package quality into offers, such as “HD streaming mode”, “pro gaming mode” or “priority field operations”.
  • Consistent across CAMARA Quality APIs: An operator’s profiles work with Quality on Demand, QoS Booking, Dedicated Networks and Network Slice Booking, so learning one API carries over to all.

API Portfolio: Communication Quality

Sub Project Wiki: Connectivity Quality Management
(incl. how to meet the team)

API Wiki: Quality on Demand

API Repository: Quality on Demand

API Repository Status: Incubating

API Status: Stable

API Version(s) and Release Date(s):

  • v0.11.1 (18.12.2024), Fall24 meta-release (patch release)
  • v1.0.0 (11.03.2025), Spring25 meta-release
  • v1.1.0 (16.09.2025), Fall25 meta-release

API availability: Information which APIs are available in which country and network, and how to get access can be found on the GSMA public launch status page.

Be part of a collaborative community driving the future of global Telco APIs.

Join Today