This release introduces the Metrics Reporting feature and contains some documentation updates and bug fixes.
In this release
New Feature: Metrics Reporting
Provisioning for metrics reporting has been added to the interface at reference point M1 and metrics report client configuration and collection has been added to the interface at reference point M5.
Enhancement: Improved OpenAPI code generation
The templates for code generation from OpenAPI YAML have been improved to add some new data type handling and error reporting.
Architecture: Move of Python tools
The Python tools and module for interacting with the M1 API interface have been moved to the rt-5gms-application-provider repository.
What's Changed
- Enhancement: Use new branches and common areas in 5G-MAG/open5gs and 5G-MAG/rt-common-shared by @davidjwbbc in #136
- Use new paths for Open5GS OpenAPI generator script and templates by @davidjwbbc in #138
- Location header included for creation of Metrics Configuration by @stojkovicv in #142
- Moving M1 python tools and classes to rt-5gms-application-provider by @davidjwbbc in #141
- M5 | Metrics Reporting API by @stojkovicv in #143
- Bug-fix: Add range checking for parameters in MetricsReportingConfiguration by @davidjwbbc in #148
- Various memory leaks and bug fixes found during metrics provisioning testing by @davidjwbbc in #150
- QoE Metrics Reporting | Handling of missing scheme value by @stojkovicv in #152
- Fixed parsing client id value from QoE metrics by @stojkovicv in #155
- Bug-fix: Response message for activateConsumptionReporting operation at M1 by @davidjwbbc in #160
- Documentation updates by @jordijoangimenez in #161
New Contributors
- @stojkovicv made their first contribution in #142
Full Changelog: rt-5gms-application-function-v1.4.0...rt-5gms-application-function-v1.4.1
