Content for  TS 26.512  Word version:  18.2.1

The 5GMS AF configures Server Certificate resources in the 5GMS AS using the procedures defined in this clause such that they remain synchronised with the Server Certificates provisioned at reference point M1 using the procedures defined in clause 4.3.6. Each Server Certificate resource at reference point M3 is represented by a PEM-formatted X.509 certificate bundle.

This procedure is used by the 5GMS AF to determine the configuration state of the Server Certificates collection in a running 5GMS AS instance. The HTTP GET method shall be used for this purpose. The request URL shall be that of the Server Certificates collection on the 5GMS AS instance. If the operation is successful, the 5GMS AS shall return an HTTP 200 (OK) response. The resource body shall be a JSON array of Server Certificate resource identifiers. The array shall be empty if no Server Certificate resources currently exist in the collection.

This procedure is used by the 5GMS AF to create a new Server Certificate resource in the target 5GMS AS instance. The HTTP POST method shall be used for this purpose. The 5GMS AF shall nominate the resource identifier to be used to identify the new resource in the Server Certificates collection as part of the request URL. A representation of the resource, in the form of a PEM-formatted X.509 certificate bundle that includes the private key, shall be provided as the request body. If the operation is successful, the 5GMS AS shall return an HTTP 201 (Created) response with an empty response body. The content of the Location header may differ from the request URL if the request was satisfied by a different 5GMS AS instance. If a Server Certificate resource already exists at the request URL an HTTP 409 (Conflict) error response shall be returned by the 5GMS AS. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571. If a Server Certificate resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMS AS. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

Retrieval of individual Server Certificate resources from the 5GMS AS is not permitted at reference point M3.

This procedure is used by the 5GMS AF to replace a Server Certificate resource in the target 5GMS AS instance. The HTTP PUT method shall be used for this purpose. The target resource shall be indicated in the request URL. The replacement resource representation, in the form of a PEM-formatted X.509 certificate bundle that includes the private key, shall be provided as the request body. If the operation is successful, the 5GMS AS shall return an HTTP 200 (OK) response with an empty response body. If the replacement PEM bundle is identical to the current resource representation the 5GMS AS shall return an HTTP 204 (No Content) response with an empty response body to indicate a "no-op". If a Server Certificate resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMS AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMS AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

This procedure is used by the 5GMS AF to destroy a Server Certificate resource in the target 5GMS AS instance. The HTTP DELETE method shall be used for this purpose. The target resource shall be indicated in the request URL. The request body shall be empty. If the operation is successful, the 5GMS AS shall return an HTTP 204 (No Content) response with an empty response body. Any subsequent attempt to recreate a Server Certificate resource with the same resource identifier shall fail as specified in clause 4.5.2.3. If the target Server Certificate resource is still referenced by a Content Hosting Configuration or Content Publishing Configuration, an HTTP 409 (Conflict) error response shall be returned by the 5GMS AS. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571 If a Server Certificate resource previously existed at the request URL and was destroyed using this procedure an HTTP 410 (Gone) error response should be returned by the 5GMS AS. If no server certificate resource has ever existed at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMS AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

The 5GMS AF shall configure Content Preparation Template resources in the 5GMS AS using the procedures defined in this clause such that they remain synchronised with the Content Preparation Templates provisioned at reference point M1 using the procedures defined in clause 4.3.5. The format of the Content Preparation Template resource representation is not specified in the present document.

This procedure is used by the 5GMS AF to determine the configuration state of the Content Preparation Templates collection in a running 5GMS AS instance. The HTTP GET method shall be used for this purpose. The request URL shall be that of the Content Preparation Templates collection on the 5GMS AS instance. If the operation is successful, the 5GMS AS shall return an HTTP 200 (OK) response. The resource body shall be a JSON array of Content Preparation Template resource identifiers. The array shall be empty if no Content Preparation Template resources currently exist in the collection.

This procedure is used by the 5GMS AF to create a new Content Preparation Template resource in the target 5GMS AS instance. The HTTP POST method shall be used for this purpose. The 5GMS AF shall nominate the resource identifier to be used to identify the new resource in the Content Preparation Templates collection as part of the request URL. A representation of the resource shall be provided as the request body. If the operation is successful, the 5GMS AS shall return an HTTP 201 (Created) response with an empty response body. The content of the Location header may differ from the request URL if the request was satisfied by a different 5GMS AS instance. If a Content Preparation Template resource already exists at the request URL an HTTP 409 (Conflict) error response shall be returned by the 5GMS AS. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571. If a Content Preparation Template resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMS AS. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

Retrieval of individual Content Preparation Template resources is not permitted at reference point M3.

This procedure is used by the 5GMS AF to replace a Content Preparation Template resource in the target 5GMS AS instance. The HTTP PUT method shall be used for this purpose. The target resource shall be indicated in the request URL. The replacement resource representation shall be provided as the request body. If the operation is successful, the 5GMS AS shall return an HTTP 200 (OK) response with an empty response body. If the replacement Content Preparation Template is identical to the current resource representation the 5GMS AS shall return an HTTP 204 (No Content) response with an empty response body to indicate a "no-op". If the Media AS does not support modification of the Content Preparation Template, the update operation shall fail with a 403 (Forbidden) HTTP response that includes a ProblemDetails error message body as specified in clause 5.2.4.1 of TS 29.571. If a Content Preparation Template resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMS AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMS AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

This procedure is used by the 5GMS AF to destroy a Content Preparation Template resource in the target 5GMS AS instance. The HTTP DELETE method shall be used for this purpose. The target resource shall be indicated in the request URL. The request body shall be empty. If the operation is successful, the 5GMS AS shall return an HTTP 204 (No Content) response with an empty response body. Any subsequent attempt to recreate a Content Preparation Template resource with the same resource identifier shall fail as specified in clause 4.5.3.3. If the target Content Preparation Template resource is still referenced by a Content Hosting Configuration or Content Publishing Configuration, an HTTP 409 (Conflict) error response shall be returned by the 5GMS AS. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571 If a Content Preparation Template resource previously existed at the request URL and was destroyed using this procedure an HTTP 410 (Gone) error response should be returned by the 5GMS AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMS AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

The 5GMSd AF shall configure Content Hosting Configuration resources in the 5GMSd AS using the procedures defined in this clause such that they remain synchronised with the Content Hosting Configurations provisioned at reference point M1 using the procedures defined in clause 4.3.3. The format of the Content Hosting Configuration resource representation is as specified in clause 8.8.3.1 of TS 26.510.

This procedure is used by the 5GMSd AF to determine the configuration state of the Content Hosting Configurations collection in a running 5GMSd AS instance. The HTTP GET method shall be used for this purpose. The request URL shall be that of the Content Hosting Configuration collection on the 5GMSd AS instance. If the operation is successful, the 5GMSd AS shall return an HTTP 200 (OK) response. The resource body shall be a JSON array of Content Hosting Configuration resource identifiers. The array shall be empty if no Content Hosting Configuration resources currently exist in the collection.

This procedure is used by the 5GMSd AF to create a new Content Hosting Configuration resource in the target 5GMSd AS instance. The HTTP POST method shall be used for this purpose. The 5GMSd AF shall nominate the resource identifier to be used to identify the new resource in the Content Hosting Configurations collection as part of the request URL. A representation of the resource shall be provided as the request body. If the operation is successful, the 5GMSd AS shall return an HTTP 201 (Created) response with an empty response body. The content of the Location header may differ from the request URL if the request was satisfied by a different 5GMSd AS instance. If a Content Hosting Configuration resource already exists at the request URL an HTTP 409 (Conflict) error response shall be returned by the 5GMSd AS. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571. If any resources referenced by the supplied Content Hosting Configuration resource representation are invalid, the create operation shall fail with an HTTP response status code of 400 (Bad Request). The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571. In this case, the Content Hosting Configuration resource shall remain in an uncreated state in the target 5GMSd AS instance. If a Content Hosting Configuration resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMSd AS. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

Retrieval of individual Content Hosting Configuration resources is not permitted at reference point M3.

This procedure is used by the 5GMSd AF to replace a Content Hosting Configuration resource in the target 5GMSd AS instance. The HTTP PUT method shall be used for this purpose. The target resource shall be indicated in the request URL. The replacement resource representation shall be provided as the request body. If the operation is successful, the 5GMSd AS shall return an HTTP 200 (OK) response with an empty response body. If the replacement Content Hosting Configuration is identical to the current resource representation the 5GMSd AS shall return an HTTP 204 (No Content) response with an empty response body to indicate a "no-op". If any resources referenced by the replacement Content Hosting Configuration resource representation are invalid, the update operation shall fail with an HTTP response status code of 400 (Bad Request). The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571. In this case, the target Content Hosting Configuration resource shall remain in the state immediately prior to the update operation. If a Content Hosting Configuration resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMSd AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMSd AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

This procedure is used by the 5GMSd AF to destroy a Content Hosting Configuration resource in the target 5GMSd AS instance. The HTTP DELETE method shall be used for this purpose. The target resource shall be indicated in the request URL. The request body shall be empty. If the operation is successful, the 5GMSd AS shall return an HTTP 204 (No Content) response with an empty response body. Any subsequent attempt to recreate a Content Hosting Configuration resource with the same resource identifier shall fail as specified in clause 4.5.4.3. If a Content Hosting Configuration resource previously existed at the request URL and was destroyed using this procedure an HTTP 410 (Gone) error response should be returned by the 5GMSd AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMSd AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

This procedure is used by the 5GMSd AF to activate or deactivate a Content Hosting Configuration resource in the target 5GMSd AS instance. The HTTP POST method shall be used for this purpose. The target resource shall be identified in the request URL. The request body shall be a single JSON boolean indicating the desired state of the target resource: true for active and false for inactive. If the Content Hosting Configuration can be (de)activated immediately by the 5GMSd AS, or if it is already in the desired state indicated in the request, the HTTP 204 (No Content) response shall be returned by the 5GMSd AS with an empty response body. If the activation request is otherwise acceptable to the 5GMSd AS, but the Content Hosting Configuration cannot be (de)activated immediately, the HTTP 202 (Accepted) response shall be returned by the 5GMSd AS with an empty response body to indicate that (de)activation is in progress. The state of the Content Hosting Configuration may then be polled using the procedure specified in clause 4.5.4.8. If a Content Hosting Configuration resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMSd AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMSd AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

This procedure is used by the 5GMSd AF to interrogate the current state of a Content Hosting Configuration resource in the target 5GMSd AS instance. The HTTP GET method shall be used for this purpose. The target resource shall be indicated in the request URL. The request body shall be empty. If the Content Hosting Configuration is known to the 5GMSd AS, the HTTP 200 (OK) response shall be returned with an indication of its current state provided in the response body as a JSON object of type boolean with the value true for active and false for inactive. If a Content Hosting Configuration resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMS AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMS AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

This procedure is used by the 5GMSd AF to purge one or more content items from the 5GMSd AS cache associated with a Content Hosting Configuration resource in the target 5GMSd AS instance. The HTTP POST method shall be used for this purpose. A Content Hosting Configuration resource shall be indicated in the request URL. The request body shall be a single key-value pair encoded per the application/x-www-form-urlencoded MIME content type. The key shall be the string pattern and the value shall be a regular expression [5] identifying the media resource URL(s) to be purged from the associated content cache. If the operation is successful, the 5GMSd AS shall return an HTTP 200 (OK) response. The resource body should indicate the total number of cache entries purged encoded as a positive JSON integer. If the purge request is otherwise acceptable to the 5GMSd AS, but no cache entries were purged because none matched the supplied regular expression, the HTTP 204 (No Content) response shall instead be returned by the 5GMSd AS with an empty response body. If the request message body - or the regular expression contained in it - are found by the 5GMSd AS to be syntactically malformed the HTTP 400 (Bad Request) error response shall be returned. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571. If a Content Hosting Configuration resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMSd AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMSd AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

The 5GMSu AF shall configure Content Publishing Configuration resources in the 5GMSu AS using the procedures defined in this clause such that they remain synchronised with the Content Publishing Configurations provisioned at reference point M1 using the procedures defined in clause 4.3.3. The format of the Content Publishing Configuration resource representation is as specified in clause 8.9.3.1 of TS 26.510.

This procedure is used by the 5GMSu AF to determine the configuration state of a running 5GMSu AS instance. The HTTP GET method shall be used for this purpose. The request URL shall be that of the Content Publishing Configuration collection on the 5GMSu AS instance. If the operation is successful, the 5GMSu AS shall return an HTTP 200 (OK) response. The resource body shall be a JSON array of Content Publishing Configuration resource identifiers. The array shall be empty if no Content Publishing Configuration resources currently exist in the collection.

This procedure is used by the 5GMSu AF to create a new Content Publishing Configuration resource in the target 5GMSu AS instance. The HTTP POST method shall be used for this purpose. The 5GMSu AF shall nominate the resource identifier to be used to identify the new resource in the Content Publishing Configurations collection as part of the request URL. A representation of the resource shall be provided as the request body. If the operation is successful, the 5GMSu AS shall return an HTTP 201 (Created) response with an empty response body. The content of the Location header may differ from the request URL if the request was satisfied by a different 5GMSu AS instance. If a Content Publishing Configuration resource already exists at the request URL an HTTP 409 (Conflict) error response shall be returned by the 5GMSu AS. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571. If any resources referenced by the supplied Content Publishing Configuration resource representation are invalid, the create operation shall fail with an HTTP response status code of 400 (Bad Request). The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571. In this case, the Content Publishing Configuration resource shall remain in an uncreated state in the target 5GMSu AS instance. If a Content Publishing Configuration resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMSu AS. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

Retrieval of individual Content Publishing Configuration resources is not permitted at reference point M3.

This procedure is used by the 5GMSu AF to replace a Content Publishing Configuration resource in the target 5GMSu AS instance. The HTTP PUT method shall be used for this purpose. The target resource shall be indicated in the request URL. The replacement resource representation shall be provided as the request body. If the operation is successful, the 5GMSu AS shall return an HTTP 200 (OK) response with an empty response body. If the replacement Content Publishing Configuration is identical to the current resource representation the 5GMSu AS shall return an HTTP 204 (No Content) response with an empty response body to indicate a "no-op". If any resources referenced by the replacement Content Publishing Configuration resource representation are invalid, the update operation shall fail with an HTTP response status code of 400 (Bad Request). The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571. In this case, the target Content Publishing Configuration resource shall remain in the state immediately prior to the update operation. If a Content Publishing Configuration resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMSu AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMSu AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

This procedure is used by the 5GMSu AF to destroy a Content Publishing Configuration resource in the target 5GMSu AS instance. The HTTP DELETE method shall be used for this purpose. The target resource shall be indicated in the request URL. The request body shall be empty. If the operation is successful, the 5GMSu AS shall return an HTTP 204 (No Content) response with an empty response body. Any subsequent attempt to recreate a Content Publishing Configuration resource with the same resource identifier shall fail as specified in clause 4.5.3.3. If a Content Publishing Configuration resource previously existed at the request URL and was destroyed using this procedure an HTTP 410 (Gone) error response should be returned by the 5GMSu AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMSu AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

This procedure is used by the 5GMSd AF to activate or deactivate a Content Hosting Configuration resource in the target 5GMSd AS instance. The HTTP POST method shall be used for this purpose. The target resource shall be identified in the request URL. The request body shall be a single JSON boolean indicating the desired state of the target resource: true for active and false for inactive. If the Content Hosting Configuration can be (de)activated immediately by the 5GMSd AS, or if it is already in the desired state indicated in the request, the HTTP 204 (No Content) response shall be returned by the 5GMSd AS with an empty response body. If the activation request is otherwise acceptable to the 5GMSd AS, but the Content Hosting Configuration cannot be (de)activated immediately, the HTTP 202 (Accepted) response shall be returned by the 5GMSd AS with an empty response body to indicate that (de)activation is in progress. The state of the Content Hosting Configuration may then be polled using the procedure specified in clause 4.5.4.8. If a Content Hosting Configuration resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMSd AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMSd AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

This procedure is used by the 5GMSd AF to interrogate the current state of a Content Hosting Configuration resource in the target 5GMSd AS instance. The HTTP GET method shall be used for this purpose. The target resource shall be indicated in the request URL. The request body shall be empty. If the Content Hosting Configuration is known to the 5GMSd AS, the HTTP 200 (OK) response shall be returned with an indication of its current state provided in the response body as a JSON object of type boolean with the value true for active and false for inactive. If a Content Hosting Configuration resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMS AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMS AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

This procedure is used by the 5GMSu AF to purge one or more content items from the 5GMSu AS cache associated with a Content Publishing Configuration resource in the target 5GMSu AS instance. The HTTP POST method shall be used for this purpose. A Content Publishing Configuration resource shall be indicated in the request URL. The request body shall be a single key-value pair encoded per the application/x-www-form-urlencoded MIME content type. The key shall be the string pattern and the value shall be a regular expression [5] identifying the media resource URL(s) to be purged from the associated content cache. If the operation is successful, the 5GMSu AS shall return an HTTP 200 (OK) response. The resource body should indicate the total number of cache entries purged encoded as a positive JSON integer. If the purge request is otherwise acceptable to the 5GMSu AS, but no cache entries were purged because none matched the supplied regular expression, the HTTP 204 (No Content) response shall instead be returned by the 5GMSu AS with an empty response body. If the request message body - or the regular expression contained in it - are found by the 5GMSu AS to be syntactically malformed the HTTP 400 (Bad Request) error response shall be returned. The response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571. If a Content Publishing Configuration resource previously existed at the request URL and was destroyed an HTTP 410 (Gone) error response should be returned by the 5GMSu AS. Otherwise, if no resource exists at the request URL an HTTP 404 (Not Found) error response shall be returned by the 5GMSu AS. In either case the response body shall be a ProblemDetails document as specified in clause 5.2.4.1 of TS 29.571.

Service Access Information is the set of parameters and addresses needed by the 5GMSd Client to activate reception of a downlink media streaming session or by a 5GMSu Client to activate an uplink media streaming session for contribution. Service Access Information additionally includes configuration information to allow the Media Session Handler to invoke procedures for dynamic policy (see clause 4.7.3), consumption reporting (clause 4.7.4), metrics reporting (clause 4.7.5) and network assistance (clause 4.7.6). The Media Session Handler may obtain Service Access Information from either the 5GMS-Aware Application (via reference point M6) or from the 5GMS AF (via reference point M5). In the former case, the Service Access Information is initially acquired by the 5GMS-Aware Application from the 5GMS Application Provider via reference point M8. In the latter case, the Media Session Handler shall use the operations specified in clause 5.3.2 of TS 26.510 at reference point M5 to acquire Service Access Information from the 5GMS AF, citing an external service identifier and the Service Access Information is derived by the 5GMS AF from the Provisioning Session established at reference point M1 (see clause 4.3.2) that is tagged with the same external service identifier. Typically, the Service Access Information for media streaming includes a set of Media Entry Points (e.g. a URL to a DASH MPD or a URL to a progressive download file) that can be consumed by the Media Stream Handler (Media Player or Media Streamer). One of these is selected by the Media Session Handler or by the 5GMS-Aware Application and is handed to the Media Player via reference point M11 or M7 respectively. For downlink media streaming exclusively via eMBMS and for hybrid 5GMSd/eMBMS services as defined in clauses 5.10.2 and 5.10.5 respectively of TS 26.501, the Service Access Information indicates that the 5GMSd Client acts as an MBMS-Aware Application. For dynamically provisioned downlink media streaming via eMBMS as defined in clause 5.10.6 of TS 26.501, the 5GMSd AS creates a presentation manifest that is regularly polled by the Media Player for a potential update. When an eMBMS User Service carrying the 5GMSd content is dynamically provisioned or removed by the 5GMSd AF, the 5GMSd AS shall update the presentation manifest with the locations where the updated manifest and the media segments are now available, for example to add or change to the media server in the MBMS Client. For downlink media streaming exclusively via MBS and for hybrid 5GMSd/MBS services as defined in clauses 5.12.2 and 5.12.4 respectively of TS 26.501, the Service Access Information indicates that the 5GMSd Client acts as an MBS-Aware Application. For dynamically provisioned downlink media streaming via MBS as defined in clause 5.12.4 of TS 26.501, the 5GMSd AS creates or hosts a presentation manifest that is regularly polled by the Media Player for a potential update. When an MBS User Service carrying the 5GMSd content is dynamically provisioned or removed by the 5GMSd AF, the 5GMSd AS shall update the presentation manifest with the resource locations where the updated manifest and the media segments are now available, for example to additionally or alternatively point to the Media Server in the MBSTF Client. If an Edge Resources Configuration with client-driven management is provisioned, a Client Edge Resources Configuration is included in the corresponding Service Access Information.

The Media Session Handler shall play the role of 3GPP Service Handler for Service URLs as defined in clause 6 of TS 26.510 by registering itself as the URL handler for the domain name launch.3gppservices.org/ms (e.g., by declaring an intent filter in an Android application manifest). Hence, the Media Session Handler is launched when a 5GMS-Aware Application requests a 5GMS Service URL (e.g., by means of an Android intent filter).

If it needs to retrieve Service Access Information from the 5GMS AF (because a full set of Service Access Information has not been supplied as additional parameters of the 3GPP Service URL) the Media Session Handler shall decompose the 3GPP Service URL into the prefix and suffix, and shall form the M5 request URL for Service Access Information as specified in clause 9.2.2 of TS 26.510.

1. If the 3GPP Service URL carries one or more af-host-address query parameters, the Media Session Handler shall choose one to substitute into {apiRoot} in the above request URL. If the port number is omitted from any af-host-address, port 80 (for HTTP) or 443 (for HTTPS) shall be assumed.
   The party operating the 5GMS AF is responsible for ensuring that the hostname(s) resolve to the correct IP address(es) in the External DN.
   If more than one af-host-address query parameter is supplied in the 3GPP Service URL, the Media Session Handler may use an alternative host endpoint address at reference point M5 if the one it is using fails to respond after some implementation-specific number of retries.
2. If the af-host-address query parameter is omitted from the 3GPP Service URL, the default host name ms.af.3gppservices.org and port number 80 (HTTP) or 443 (HTTPS) shall be used instead.
   The 5G System operator is responsible for supporting resolution of this well-known host name to the correct IP address(es) in the Trusted DN, e.g., by managing appropriate DNS records.
   The 5G System operator is responsible for ensuring that a resilient service is available at this host endpoint address. If the hostname resolves to multiple IP addresses, the Media Session Handler may use a different one at reference point M5 if the one it is using fails to respond after some implementation-specific number of retries.
3. If the 3GPP Service URL includes the optional media-entry-point query parameter, the Media Session Handler issues a request for this URL (thereby chaining the Media Stream Handler), but only after it has successfully retrieved the Service Access Information from the 5GMS AF.

Depending on the success (or otherwise) of retrieving the Service Access Information (and optionally chaining the Media Stream Handler with the media entry point), the Media Session Handler returns an appropriate HTTP status code to the invoking 5GMS-Aware Application.