search

camaraproject / QualityOnDemand

Repository to describe, develop, document and test the QualityOnDemand API family
https://wiki.camaraproject.org/x/zwOeAQ
Apache License 2.0
42 stars 59 forks source link

Is enum the best choice for qos_profile ? #11

Closed patrice-conil closed 2 years ago

patrice-conil commented 2 years ago

What if a client needs a QoS profile with LOW_LATENCY and THROUGHPUT_L? To be able to compose these profiles, we would need to add an enum key that represents this combination and also a new key for all other relevant ones. Instead, we could associate each profile with values ​​based on the power of two (1, 2, 4, 8, 16...) and compose them via an OR operation. What do you think of this?

Marcin-Jarzab commented 2 years ago

IMO, those QoS profiles are "flavours" similar to instances types known from Public Cloud providers. In production deployment there could be defined several only based on subscription fee and specific use-case applicability. 5G System QoS framework and configuration might differ among operators and we might expect that RAN will support some limited configuration. Example AWS provider and instance types : https://aws.amazon.com/ec2/instance-types/

IMO in production deployment such "multiplicity" could be possible and QoS mapping table which is defined in CAMARA QoD API can be extended and even defined based on AWS blueprint concept.

Nevertheless as for now in the CAMARA QoD the "profiles mapping table" should fit most use cases.

Marcin-Jarzab commented 2 years ago

Agreed to close and agree on current solution during the meeting : 04.22.2022.