Release v1.2.3 - 5GMS Application Server

This is a minor bug-fix release.

In this release

1. The Application Server will now look for the mime.types file on the system in the normal OpenResty location and normal nginx location and use whichever it finds. (issue #83)
2. The OpenResty proxy handler will check nginx binaries it finds to make sure they are built with the Lua module before using them. If the binary is not found on the normal $PATH then the handler will subsequently check the default OpenResty installation location. If OpenResty is not found then the Application Server will abort with an error. (issue #89)

What's Changed

• Documentation Updates - Development by @jordijoangimenez in #86
• Bug fixes: Find mime.types file location and automatically find Openresty path by @davidjwbbc in #90
• Minor restructuring of the README.md. Move the Open Resty installatio… by @dsilhavy in #91

Full Changelog: rt-5gms-application-server-1.2.2...rt-5gms-application-server-1.2.3

Release v1.2.2 - 5GMS Application Server

This is a bug-fix and compatibility release.

In this release

1. Fix a compatibility issue with the latest version of pydantic. The pydantic Python module is pulled in as a dependency of fastapi and affects data types presented to the application from its M3 server interface.
2. Bring the return code for the M3 cache purge operation in line with the new TS 26.512 v17.7.0. The code returned when the regular expression for matching cache entries cannot be compiled has changed from 422 to 400.

What's Changed

• Bug-fix: Handle changes to OpenAPI models when pydantic v2 is installed by @davidjwbbc in #82
• Feature: TS 26.512 v17.7.0 uplift by @davidjwbbc in #85

Full Changelog: rt-5gms-application-server-1.2.1...rt-5gms-application-server-1.2.2

Release v1.2.1 - 5GMS Application Server

In This Release

This is a bug-fix release of the 5GMS Application Server. This release fixes two issues:

• Use SNI on TLS connections to media ingest servers (#78)
  • Media fetches failed if the ingest server required SNI in order to serve media content correctly.
  • The configuration is now changed to use SNI for upstream TLS connections.
• The dynamic redirection failed on some versions of OpenResty (#80)
  • The configuration was ambiguous with redirection cache entries.
  • Cache keys are now unique between the original redirected request and the fetch request for redirected paths.

What's Changed

• Bug-fix: Use SNI with media origin by @davidjwbbc in #78
• Bug-fix: Redirections fail with recent versions of OpenResty by @davidjwbbc in #80

Full Changelog: rt-5gms-application-server-1.2.0...rt-5gms-application-server-1.2.1

Release v1.2.0 - 5GMS Application Server

Release v1.2.0 - Reference Tools 5GMS Application Server

In this release

This release contains a change to the 5GMS Application Server to allow it to handle redirects from configured media origins (via the interface at reference point M2). A redirect will now be learned and an appropriate local redirect issued to the UE via the interface at reference point M4. This is done so that the UE will continue to use the designated 5GMS Application Server for media retrieval, but allows the 5GMS Application Server to track when the request needs to be redirected to another media origin or path.

In order to accomplish this the 5GMS Application Server now needs to use some runtime language features (Lua script) that exists in the OpenResty release of nginx. Therefore the default web proxy server used is now OpenResty instead of the plain nginx package. Please follow the instructions in the README.md for installing OpenResty and ensuring that the OpenResty nginx process is the first found in the executable path.

This release also includes some minor bug fixes, operational improvements and documentation improvements.

What's Changed

• Fix: Various small fixes by @davidjwbbc in #64
• Fix: nginx configuration not merged correctly by @davidjwbbc in #67
• Fix: Force access mode when creating directories. by @davidjwbbc in #69
• Documentation update by @jordijoangimenez in #74
• Documentation update by @jordijoangimenez in #73
• Upstream redirects (Issue #70) by @davidjwbbc in #77

Full Changelog: rt-5gms-application-server-1.1.2...rt-5gms-application-server-1.2.0

Release v1.1.2 - 5GMS Application Server

Release v1.1.2

This is a bug fix release to correct problems found while deploying the new 5GMS Application Function v1.3.0.

Major changes in this release:

• Fixed issue where distribution points with the same domainNameAlias defined were not being merged into the same virtual server configuration in the Nginx configuration.
• Updated documentation to explain the need to have nginx installed before running the AS.

What's Changed

• Fix: nginx configuration not merged correctly (v1.1.x backport) by @davidjwbbc in #68

Full Changelog: rt-5gms-application-server-1.1.1...rt-5gms-application-server-1.1.2

Release v1.1.1 - 5GMS Application Server

Release v1.1.1

This release to fixes an issue caused by the tightening of rules in an upstream component, the Python fastapi module (version 0.95.0 and above). This causes a run-time issue with the v1.1.0 release of the Reference Tools 5GMS Application Server. This is visible as an error about the Path() function not allowing a default value when the Application Server is started, causing the Application Server to immediately abort.

What's Changed

• Fix: fastapi 0.95.0 compatibility by @davidjwbbc in #63

Full Changelog: rt-5gms-application-server-1.1.0...rt-5gms-application-server-1.1.1

Release v1.1.0 - 5GMS Application Server

Release v1.1.0

This Release marks the move of the Application Server away from the minimum viable products (MVP#1 & MVP#2) and becoming a managed service of the Application Function. This is achieved by implementing a configuration and control interface at reference point M3 (see 3GPP TS 26.501). This also means that this release of the Application Server will require an M3 client, such as the 5GMS Application Function (v1.1.0 or above), to configure it at run-time.

What's Changed

• Add Certificate handling for HTTPS distrubution. by @davidjwbbc in #37
• Only use keyword arguments for asyncio.create_task that are understood. by @davidjwbbc in #42
• Documentation of "development" updated according to "main" by @jordijoangimenez in #48
• Feature: Add M3 interface by @davidjwbbc in #50
• Feature: Uplift to TS 26.512 v17.3.0 by @davidjwbbc in #51
• Fix: Report 422 for bad purge regex by @davidjwbbc in #53
• Improve documentation from feedback and change to M3 cache purge responses by @davidjwbbc in #55
• Update documentation to reflect the need for an M3 client. by @davidjwbbc in #58
• Improve testing documentation. by @davidjwbbc in #61

Full Changelog: rt-5gms-application-server-1.0.1...rt-5gms-application-server-1.1.0

Release v1.0.1

This release is just an update to the documentation to make it clearer for those wanting to try-out or develop the 5G-MAG Reference Tools 5GMS Application Server.

What's Changed

• Updates to documentation in "main" by @jordijoangimenez in #44

Full Changelog: rt-5gms-application-server-1.0.0...rt-5gms-application-server-1.0.1

Release v1.0.0

This Release

This is the first release of the 5G-MAG Reference Tools 5GMS Application Server. This release provides a simple 5GMSd Application Server which uses nginx to process requests. The media to be served by nginx is obtained from a pull-ingest described by a ContentHostingConfiguration JSON file.

This represents a partial implementation of the 3GPP TS 26.501 and TS 26.512 specifications for a 5G Media Streaming Downlink Application Server.

What's Changed

• Fix startup of nginx software (issue #15). by @davidjwbbc in #16
• Add instructions for API regeneration (issue #17) by @davidjwbbc in #19
• Add source file metadata by @davidjwbbc in #21
• Move the example ContentHostingConfiguration to the shared repository by @davidjwbbc in #22
• Change the proxy modules loading to use importlib by @davidjwbbc in #25
• Add link to developer docs and placeholder commands for TODO sections. by @davidjwbbc in #24
• Generate OpenAPI Python modules by @davidjwbbc in #23
• Add an application configuration file by @davidjwbbc in #26
• Validate ContentHostingConfiguration rewriteRule by @davidjwbbc in #27
• Update docs and configuration to add provisioning-session-id UUID. by @davidjwbbc in #29
• Add lifecycle management for web proxy daemon by @davidjwbbc in #32
• Resync rt-common-shared submodule by @davidjwbbc in #33
• Rework OpenAPI bindings generator script by @davidjwbbc in #35
• Add ATTIBUTION_NOTICE and update README by @davidjwbbc in #36
• Add a hint to the documentation to checkout the correct branch for fe… by @dsilhavy in #38

New Contributors

• @dsilhavy made their first contribution in #38

Full Changelog: https://github.com/5G-MAG/rt-5gms-application-server/commits/rt-5gms-application-server-1.0.0