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 interfaces at reference points M1 and M5.
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 TS26512_M5_ServiceAccessInformation.yaml OpenAPI YAML remove the old single mediaPlayerEntry and replaces it with a new entryPoints array. Each entry in the array is an object with 3 properties:
locator - This is mandatory and contains an absolute URL pointing to a path on the interface at reference point M2d where the media entry point can be found.
contentType - This describes the MIME type for the locator and is also mandatory.
profiles - An optional array of media profile URIs which describe the media profiles used by this entry point.
The M3 interface definition references the ContentHostingConfiguration schema from TS26512_M1_ContentHostingProvisioning.yaml. The M3 interface OpenAPI YAML should increment its version number to indicate the inclusion of the new ContentHostingConfiguration.
Changes
Install the v17.4.0 TS26512_M1_ContentHostingProvisioning.yaml in 5gms/5G_APIs-overrides
Install the v17.4.0 TS26512_M5_ServiceAccessInformation.yaml in 5gms/5G_APIs-overrides
Install the v17.4.0 TS26512_CommonData.yaml in 5gms/5G_APIs-overrides
Update the version number in 5gms/5G_APIs-overrides/M3_ContentHostingProvisioning.yaml to indicate the inclusion of the new structure, i.e. change the version number to 0.1.0.
Related issues
This is a prerequisite for 5G-MAG/rt-5gms-application-function#51 and 5G-MAG/rt-5gms-application-server#??.
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 singleentryPointPathin theContentHostingConfiguration. This is a compatibility breaking change in the specification which affects the interfaces at reference points M1 and M5.The new OpenAPI YAML for
TS26512_M1_ContentHostingProvisioning.yamlremovesentryPointPathat the top level on theContentHostingConfigurationobject and introduces a new optionaldistributionConfigurations[].entryPointobject. This newentryPointobject has 3 properties:relativePath- This is a mandatory property which is the per distributionConfiguration equivalent to the oldentryPointPathfrom the top level.contentType- This describes the MIME type for therelativePathand is also mandatory.profiles- An optional array of media profile URIs which describe the media profiles used by this entry point.The
TS26512_M5_ServiceAccessInformation.yamlOpenAPI YAML remove the old singlemediaPlayerEntryand replaces it with a newentryPointsarray. Each entry in the array is an object with 3 properties:locator- This is mandatory and contains an absolute URL pointing to a path on the interface at reference point M2d where the media entry point can be found.contentType- This describes the MIME type for thelocatorand is also mandatory.profiles- An optional array of media profile URIs which describe the media profiles used by this entry point.The M3 interface definition references the
ContentHostingConfigurationschema fromTS26512_M1_ContentHostingProvisioning.yaml. The M3 interface OpenAPI YAML should increment its version number to indicate the inclusion of the newContentHostingConfiguration.Changes
TS26512_M1_ContentHostingProvisioning.yamlin5gms/5G_APIs-overridesTS26512_M5_ServiceAccessInformation.yamlin5gms/5G_APIs-overridesTS26512_CommonData.yamlin5gms/5G_APIs-overrides5gms/5G_APIs-overrides/M3_ContentHostingProvisioning.yamlto indicate the inclusion of the new structure, i.e. change the version number to 0.1.0.Related issues
This is a prerequisite for 5G-MAG/rt-5gms-application-function#51 and 5G-MAG/rt-5gms-application-server#??.