You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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 singleentryPointPath
in theContentHostingConfiguration
. 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
removesentryPointPath
at the top level on theContentHostingConfiguration
object and introduces a new optionaldistributionConfigurations[].entryPoint
object. This newentryPoint
object has 3 properties:relativePath
- This is a mandatory property which is the per distributionConfiguration equivalent to the oldentryPointPath
from the top level.contentType
- This describes the MIME type for therelativePath
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 fromTS26512_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.
The text was updated successfully, but these errors were encountered: