Comparison of QoS Booking, Dedicated Networks, and TMUS Proposal

5G SA, 5G-NSA, 4G, etc (Up for network provider)

(see API Proporal)

4G or 5G

4G or 5G (if slicing is used there is SA capable device dependency)

Operator MAY return whether Slicing is used or not. Since Provisioning is happening later the end user can provision the right devices. So the determination of the technology can happen during provisioning

Two levels:

• Network Profiles (aggregated bandwidth, max number of devices, supported QoS profiles)

• QoSProfiles for device accesses

  • Array of “string”, reference to QOD QoSProfiles (only those, which are part of the Network Profile)

  • QoSProfiles can be used/changed using the QOD API, when the network is activated.

Operator defined only, structure as defined in QoSProfiles

Operator defined only, structure as defined in QoSProfiles

We strongly recommed using QoS profiles defined by the Operators -- we used it in QoD and we recommend standardizing on that. Otherwise, the operator has to find a closest match, and a kind of negotiation protocol needs to happen.  Otherwise there will be mulitple profiles (one for QoD, one for QoS, one for Dedicated Network)  and might confuse the end users

Predefined by the Operator with a label (additional Service Areas can be up for negotiation). The intention is to avoid any length negotiations, e.g. when parts of the requested area is not capable of supporting the requested capabilities.

Note: we can discuss future expansions.

Flexible, define as part of the booking (point, circle, polygon, and area name which is a label operators can predefine.)

Note: we can discuss future expansion supports.

Flexible, define as part of the booking (point, circle, polygon, spec supports future expansion)

Since service area can be anywhere, any shape, any size and anywhere in the world a flexible approach is required. 

Any Future Date and Time

Any Future Date and Time

Any Future Date and Time. 

Yes.

Note, device access is given before and while the reservation is activated.
Note, the technical realization of ‘provisioning’ is up for the CSP.

No. Booking and Provisiong the device needs to happen at the same time

Yes

When the ASP books the service they may not actually know the IP address or MSDN of the devices.  Booking might happen long before.   If the ASP knows the device details and wants to use the device immediatly then the ASP simple book the service and immedialy provison the device(s)

Multiple devices (Max number of devices limited by Operator in Network Profile)

Single device

Multiple devices, number can be requested during booking

Single Device with each device access call. Multiple device accesses, can be issued, using subsequent Accesses API calls. Therefore, there is support for multiple devices.

Note, the technical realization of ‘provisioning’ is up for the CSP.

Single Device

Multiple Devices

In any common  quality of service use case,  multiple devices are generally used. The booking needs to be requested for mulitple devices and those devices should be provisioned at later time. If the ASP wants only one device then N=1; which is straightforward

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

Supported

B2B (initial): Media production, Festival and Enterprise connectivity

The ASP may also use the API for B2B2C offerings. This is currently not supported within the usage scenarios, but discussed as possible future extensions.

B2B2C: Premium connection “ticket”

Device Access

N/A - Booking and Provisioning happening at the same time

Provision

Network Profile (aggregated)

N/A (single device only)

N/A? … parameters within booking request?

QoS Profiles (array with default)

QoS Profile

QoS Profile

Service Area

Service Area

Service Area

Service Time

Service Time

Service Time