Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uplift to TS 26.512 v17.4.0: Update M3 interface with new ContentHostingConfiguration structure #62

Closed
davidjwbbc opened this issue Mar 14, 2023 · 1 comment · Fixed by #64
Assignees
Labels
enhancement New feature or request

Comments

@davidjwbbc
Copy link
Contributor

Context

3GPP SA4 has agreed CR0032r1 [S4-230267] to update TS 26.512 Rel-17. This will hopefully be approved at SA#99 Plenary as part of the CR Pack SP-230253.

One part of these changes is the introduction of multiple entry point paths, up to one per distributionConfiguration, instead of just a single entryPointPath in the ContentHostingConfiguration. This is a compatibility breaking change in the specification which affects the interface at reference point M1.

The new OpenAPI YAML for TS26512_M1_ContentHostingProvisioning.yaml removes entryPointPath at the top level on the ContentHostingConfiguration object and introduces a new optional distributionConfigurations[].entryPoint object. This new entryPoint object has 3 properties:

  • relativePath - This is a mandatory property which is the per distributionConfiguration equivalent to the old entryPointPath from the top level.
  • contentType - This describes the MIME type for the relativePath and is also mandatory.
  • profiles - An optional array of media profile URIs which describe the media profiles used by this entry point.

The interface at reference point M3 refers to the ContentHostingConfiguration object structure from TS26512_M1_ContentHostingProvisioning.yaml and will therefore be updated by these changes.

Changes to the Application Server

Although the ContentHostingConfiguration structure is changing, the parts that are changing do not directly affect the Application Server. Therefore this ticket is more about checking that the 5GMS Application Server and M3 test client still work with the new structures. It is not expected that there will be any code changes necessary.

Related issues

This requires 5G-MAG/rt-common-shared#22 and 5G-MAG/rt-5gms-application-function#51 to be implemented first.

@davidjwbbc
Copy link
Contributor Author

Updated the AS to include the new rt-common-shared and so far there are no issues (as we anticipated there wouldn't be) with the multiple media entry points.

@davidjwbbc davidjwbbc moved this from In Progress to Ready To Review in 5GMS: TS 26.512 V17.4.0 uplift Apr 5, 2023
@davidjwbbc davidjwbbc linked a pull request Apr 6, 2023 that will close this issue
@davidjwbbc davidjwbbc moved this from Ready To Review to Done in 5GMS: TS 26.512 V17.4.0 uplift Apr 6, 2023
@rjb1000 rjb1000 moved this from Backlog to Done in 5GMS: M3 link (AF to AS RESTful OpenAPI) Apr 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

1 participant