Skip to content

Release v1.1.0 - 5GMS Application Function

Compare
Choose a tag to compare
@davidjwbbc davidjwbbc released this 22 Feb 12:08
· 240 commits to main since this release

Release v1.1.0

This marks the first version of the 5GMS Application Function which now directly controls the 5GMS Application Server via the interface at reference point M3 (see 3GPP TS 26.501). This means that the AF now requires an AS listening at the configured AS location (default: localhost TCP port 7777) to be running in order to operate properly and as part of the 5G Media Streaming architecture. Upon start up the AF will now select and configure the AS using the configuration it has been provided.

What's Changed

  • Feature: 5GMS Application Function M3 API by @devbbc in #23
  • Feature: uplift to TS 26.512 v17.3.0 by @devbbc in #26
  • Fix: Use domainNameAlias for the authority in the mediaPlayerEntry when available and improve error logging by the 5GMS AF by @devbbc in #30
  • Enhancement: improved logging around content hosting configuration and certificates configuration files by @davidjwbbc in #32
  • Prepare release candidate for v1.1.0 by @davidjwbbc in #34
  • Documentation and deployment updates for v1.1.0 release candidate by @davidjwbbc in #40
  • Improve examples and logging by @davidjwbbc in #42
  • Fix for lack of relative filenames in msaf.yaml and documentation improvements for release candidate by @davidjwbbc in #44

Full Changelog: rt-5gms-application-function-v1.0.1...rt-5gms-application-function-v1.1.0