This documentation is currently under development and subject to change. It reflects outcomes elaborated by 5G-MAG members. If you are interested in becoming a member of the 5G-MAG and actively participating in shaping this work, please contact the Project Office

Using CAMARA APIs (and Network Services) for Content Production & Contribution

This is a list of CAMARA APIs suitable to be used in the context of Connectivity Quality Management: Network API Initiatives under analysis.

Their mapping to the context of Content Production & Contribution is done below answering the following requirements:

How to book QoS before being at or at the location?

First step is the ability to discover QoS profiles available at a given location and time. This step requires:

  • Mechanism to obtain available QoS profiles
  • Indication of a service area and/or time/duration
Mechanism to obtain available QoS profiles
By means of the QoS Profiles API the QoS profile parameters available in the network can be retrieved. No information about the service area is linked to such request.
By means of the Dedicated Networks - Network Profiles API it is possible to obtain the list of available Network Profiles which link the QoS Profile with additional information on the aggregated UL/DL throughput for a maximum number of devices.

There are some limitations as the information on the name of the QoS profile need to be known beforehand. It is understood that the name of the profiles would be communicated by the network operator via the Network API Platform.

Identification of a service area and/or time/duration
In general the available profiles are listed for the network, not for a specific location or time/duration. It is only when booking the resources for the specific area and duration when information about the success will be available.

There are some limitations as the information on the availability of QoS is only available at booking time and not beforehand. The Connectivity Insights APIs are also not practical as they can only be invoked at the given location. Potential remedy: Create/Adapt an API so that information on the QoS profile availability for a given location can be retrieved.

With the information in the previous step, it should be possible to book QoS (to reserve network resources) for a given application or device for the intended service area and/or time/duration. This step requires:

  • Mechanism to create a booking linking a profile to a service area and time/duration.
  • The previous mechanism including already information about the application server and/or device.
Mechanism to create a booking linking a profile to a service area and time/duration
By means of the Dedicated Networks - Network Profiles API it is possible to request the creation of a dedicated network linking a QoS profile with a service area and time/duration. Therefore, this would comprise the booking of resources for a specific QoS Profile, a maximum number of devices which can make use of it, the service area and the time/duration.
By means of the Network Slice Booking API it is possible to request the creation of a session with the expected service time, service area, and QoS profile. The number of devices can be specified in the QoS profile.
By means of the QoS Booking & Assignment - QoS Booking API it is possible to request the creation of a QoS booking specifying the QoS profile, number of devices, service area and time/duration.

The Quality on Demand API lacks information about the service area. Potential remedy: add information about the service area.

The previous mechanism including already information about the application server and/or device
By means of the QoS Booking API it is possible to request the creation of a QoS booking specifying the QoS profile, application server details, device details, service area and time/duration.
By means of the QoS Provisioning API it is possible to request the creation of a QoS booking specifying the QoS profile and the device. No information about the service area nor time/duration are provided.
By means of the Quality on Demand API it is possible to request the creation of a QoS booking specifying the QoS profile, application server details, device details, and time/duration. No information about the service area is provided.

There are some limitations as the information on the exact device and application server may not be known beforehand or may change in the course between making the booking and using the network resources. The mechanisms defined in Dedicated Networks API and QoS Booking and Assignment are more appropriate for this case.

How to book QoS once already at the location?

All the mechanisms described above would allow the booking of QoS when already at the location. However, the QoS Provisioning API and Quality on Demand API are particularly targetted to this scenario given it is not possible to define the service area in which they are applicable beforehand. If the booking is done at the location it is also assumed that the exact devices are known, therefore any of the mechanisms described above would be suitable.

How to book QoS for a known device?

All the mechanisms described above would allow to exploit network resources for any device. However, the QoS Booking API, QoS Provisioning API and Quality on Demand API would imply knowledge of the devices for which the booking is requested.

How to book QoS for unknown devices?

All the mechanisms described above would allow to exploit network resources for any device. However, if devices are not known yet at the time of booking, it is possible to use the Dedicated Networks - Network Profiles API, Network Slice Booking API and QoS Booking & Assignment - QoS Booking API to request the booking of resources without committing to use a particular device.

How to use the network resources?

First step is to have booked the network resources either for any device, a given number of devices or a concrete device. This implies following one of the steps below:

  • Assingment and management of the booked network resources to a device
  • Direct usage of the network resources when a device just connects to the network
Assingment of the booked network resources to a particular device
By means of the QoS Booking and Assignment - Device Assignment API it is possible to assign a device to an existing QoS booking.
By means of the Dedicated Network - Accesses API it is possible to assign a device to an existing network profile

The mechanisms which detach the booking of network resources from a particular device add flexibility.

Direct usage of the network resources when a device just connects to the network
By means of the Network Slice Booking API it is possible to use the network resources when a device connects to the network.
By means of the QoS Booking API it is possible to use the network resources when a device connects to the network.
By means of the QoS Provisioning API it is possible to use the network resources when a device connects to the network.
By means of the Quality on Demand API it is possible to use the network resources when a device connects to the network.

For some of these mechanisms it is unclear how the network capabilities would be exploited by a device. It may be impractical when a device need to be exchanged.

How to exchange devices during runtime?

In the event that a device need to be exchanged or the booked resources should be assing to a different device, the following alternatives exist:

  • Creating a new booking for a new device before releasing the current device
  • Separation of the QoS booking w.r.t. to the device, enabling re-assignment of QoS booking.
Creating a new booking for a new device before releasing the current device
By means of the QoS Booking API a new booking for a specific device should be created.
By means of the QoS Provisioning API a new booking for a specific device should be created.
By means of the Quality on Demand API a new booking for a specific device should be created.

With the previous mechanisms there is no guarantee that new resources are available. Releasing the previous device will also imply no guarantee that those will remain available for a new booking.

Separation of the QoS booking w.r.t. to the device, enabling re-assignment of QoS booking
By means of the Dedicated Network - Accesses API it is possible to request the assignment or release of a device to an existing network profile
By means of the Network Slice Booking API it is possible to bring a new device which will exploit the booked network resources.
By means of the QoS Booking & Assignment - Device Assignment API it is possible to request the assignment or release of devide to an existing QoS booking.

The mechanisms which detach the booking of network resources from a particular device add flexibility.

How to obtain notifications about the ability of a network to support the requirements of an application?

These are different alternatives, including reception of a one-shot notification (e.g. for checking whether the network is able to meet certain requirements at a given instant of time) and a subcription to receive notifications (more useful during runtime).

A one-shot notification

The pre-requisite is to create an Application Profile by invoking the Application Profiles API with a series of user-defined network quality thresholds. Following this step, the Connectivity Insights API can be invoked which reply contains a message about the confidence of the network in meeting the network quality thresholds.

Subscribing to regular notifications

The pre-requisite is to create an Application Profile by invoking the Application Profiles API with a series of user-defined network quality thresholds. Following this step, the Connectivity Insights Subscriptions API can be invoked to receive regular notifications (up to a defined limit) about the confidence of the network in meeting the network quality thresholds.

A new application profile needs to be created where tracking notifications for the original QoS Profile which many other APIs use would be more coherent. In general, one would expect that notifications/logs can be requested for any API once the network resources are being used.

Back to top

Copyright © 5G-MAG - The Media Connectivity Association