Prior to configuring content hosting, dynamic policies, or reporting, the 5GMS Application Provider shall create a new Provisioning Session. The following CRUD operations are used to manage a provisioning session.

This procedure is used by the 5GMS Application Provider to create a new Provisioning Session. The 5GMS Application Provider shall use the HTTP POST method to create a new Provisioning Session. Upon successful creation, the 5GMS AF shall respond with a 201 (Created) response message that includes the resource identifier of the newly created Provisioning Session in the body of the reply and the URL of the resource, including its resource identifier, shall be returned as part of the HTTP Location header field.

This procedure is used by the 5GMS Application Provider to obtain the properties of the Provisioning Session from the 5GMS AF. The 5GMS Application Provider uses the GET method for this purpose.

The Update operation is not allowed on Provisioning Sessions.

This procedure is used by the 5GMS Application Provider to destroy a Provisioning Session. The 5GMS AF will release any associated resources, purge any cached data, delete all QoS and reporting configurations associated with this Provisioning Session. The 5GMS AF shall use the HTTP DELETE method for this purpose.

These procedures are used by the 5GMSd Application Provider and the 5GMSd AF on M1d to provision the content hosting feature for downlink streaming.

This procedure is used by the 5GMSd Application Provider to create a new Content Hosting Configuration. The 5GMSd Application Provider shall use the HTTP POST method for this purpose and the request message body shall include a ContentHostingConfiguration resource, as specified in clause 7.6.3.1.

• If the Content Hosting Configuration uses the Pull-based content ingest method, i.e. the pull attribute is set to True, then the IngestConfiguration.baseURL property shall be nominated by the 5GMSd Application Provider in the request message body.
• If the Content Hosting Configuration uses the Push-based content ingest method, i.e. the pull attribute is set to False, then the IngestConfiguration.baseURL property shall be nominated by the 5GMSd AF and returned in the response message body. It shall not be set by the 5GMSd Application Provider in the request message body.

In all cases, the DistributionConfiguration.baseURL property is read-only: it shall be omitted from the creation request and shall be assigned by the 5GMSd AF, allowing the value to be inspected by the 5GMSd Application Provider in the returned ContentHostingConfiguration resource representation, or by using the procedure specified in clause 4.3.3.3 below. If the procedure is successful, the 5GMSd AF shall generate a resource identifier representing the new Content Hosting Configuration. In this case, the 5GMSd AF shall respond with a 201 (Created) HTTP response message and shall provide the URL to the newly created resource in the Location header field. The response message body may include a ContentHostingConfiguration resource (see clause 7.6.3.1) that represents the current state of the Content Hosting Configuration, including any fields set by the 5GMSd AF. If the procedure is not successful, the 5GMSd AF shall provide a response code as defined in clause 6.3.

This procedure is used by the 5GMSd Application Provider to obtain the properties of an existing Content Hosting Configuration resource from the 5GMSd AF. The HTTP GET method shall be used for this purpose. If the procedure is successful, the 5GMSd AF shall respond with a 200 (OK) response message that includes the ContentHostingConfiguration resource in the response message body. If the procedure is not successful, the 5GMSd AF shall provide a response code as defined in clause 6.3.

The update operation is invoked by the 5GMSd Application Provider to modify the properties of an existing ContentHostingConfiguration resource. All writeable properties except domainNameAlias may be updated. The HTTP PATCH or HTTP PUT methods shall be used for the update operation. If the procedure is successful, the 5GMSd AF shall respond with a 200 (OK) and provide the content of the resource in the response, confirming the successful update operation. If the procedure is not successful, the 5GMSd AF shall provide a response code as defined in clause 6.3.

This operation is used by the 5GMS Application Provider to destroy a Content Hosting Configuration resource and to terminate the related distribution. The HTTP DELETE method shall be used for this purpose. As a result, the 5GMS AF will release any associated network resources, purge any cached content, and delete any corresponding configurations. If the procedure is successful, the 5GMSd AF shall respond with a 200 (OK) response message. If the procedure is not successful, the 5GMSd AF shall provide a response code as defined in clause 6.3.

The set of downlink content ingest or uplink content egest protocols supported by the 5GMS AS at interface M2 is described by the ContentProtocols resource at M1, as specified in clause 7.5.3.1.

The Create operation is not permitted for the ContentProtocols resource.

This procedure is used by the 5GMS Application Provider to retrieve a list of content ingest protocols supported by the 5GMS AS. The HTTP GET method shall be used for this purpose. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) response that includes a ContentProtocols resource in the response message body, as specified in clause 7.5.3.1. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

The Update operation is not permitted for the ContentProtocols resource.

The Delete operation is not permitted for the ContentProtocols resource.

For downlink media streaming, the 5GMSd AS may be required to process content ingested at interface M2d before serving it on interface M4d. For uplink media streaming, the 5GMSu AS may be required to process content it receives from the 5GMSu Client before passing it to the 5GMSu Application Provider on the egest interface M2u. The content processing operations are specified in a Content Preparation Template resource, as specified in clause 7.4.2.

This procedure is used by the 5GMS Application Provider to register a new Content Preparation Template with a Provisioning Session. The 5GMS Application Provider shall use the HTTP POST method to upload a new Content Preparation Template resource. The MIME content type of the Content Preparation Template shall be supplied in the Content-Type HTTP request header. Upon successful creation, the 5GMS AF shall respond with a 201 (Created) response message and the URL of the newly created resource, including its resource identifier, shall be returned as part of the HTTP Location header field. If the MIME content type indicated in Content-Type is not understood by the 5GMS AF, the creation of the Content Preparation Template resource shall fail with HTTP error response status code 422 (Unprocessable entity). If the 5GMS AF is unable to provision the resources indicated in the supplied Content Preparation Template, the creation operation shall fail with an HTTP response status code of 503 (Service Unavailable). If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

This procedure is used by the 5GMS Application Provider to download a copy of a Content Preparation Template resource from the 5GMS AF. The 5GMS Application Provider shall use the GET method for this purpose. If the procedure is successful, the 5GMS AF shall respond with 200 (OK) and shall provide the requested resource in the HTTP message response body. The Content-Type response header shall have the same value as that supplied when the Content Preparation Template resource was created. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

The update procedure is used by the 5GMS Application Provider to modify or replace an existing Content Preparation Template resource. The HTTP PATCH or HTTP PUT methods shall be used for the update operation. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) and provide the content of the resource in the response, reflecting the successful update operation. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

This operation is used by the 5GMS Application Provider to destroy a Content Preparation Template resource. The HTTP DELETE method shall be used for this purpose. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) response message. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3. If the Content Preparation Template is in use as part of a Content Hosting Configuration, the procedure shall fail with HTTP error response status code 409 (Conflict).

Each X.509 server certificate [8] presented by the 5GMSd AS at reference point M4d or at reference point xMB-U is represented by a Server Certificate resource at M1d. The Server Certificates Provisioning API as specified in clause 7.3 enables a Server Certificate resource to be created within the scope of a Provisioning Session, and subsequently referenced by a Content Hosting Configuration created in the scope of the same Provisioning Session. That API supports two alternative provisioning methods for Server Certificate resources: one in which a certificate is generated by the 5GMS System operator on behalf of the 5GMSd Application Provider; the other in which a certificate is generated by the 5GMSd Application Provider from a Certificate Signing Request solicited from the 5GMSd AF. Both methods shall be supported by implementations of the 5GMSd AF.

This procedure is used by the 5GMSd Application Provider to request that the 5GMS System generates a new X.509 certificate on its behalf within the scope of a Provisioning Session. In this case, the certificate's Common Name (CN) is assigned in a domain under the control of the 5GMSd System operator. The 5GMSd Application Provider shall use the HTTP POST method to create a new Server Certificate resource. Upon successful creation, the 5GMSd AF shall respond with a 201 (Created) response message and the URL of the resource, including its resource identifier, shall be returned in the HTTP Location header. The response message body may optionally include a copy of the X.509 certificate corresponding to the newly created Server Certificate resource, as specified in clause 7.3.3.2. If the procedure is not successful, the 5GMSd AF shall provide a response code as defined in clause 6.3.

This procedure is used by the 5GMSd Application Provider to solicit a Certificate Signing Request from the 5GMSd AF for the purpose of generating an X.509 certificate independently of the 5GMSd System. In this case, the certificate's Common Name (CN) is assigned in a domain under the control of the 5GMSd Application Provider itself, or that of a third party acting on its behalf. The 5GMSd Application Provider shall separately arrange for the FQDN carried in the Common Name of the certificate, or that of a Subject Alternative Name (subjectAltName) extension in the same certificate (see Section 4.2.1.6 of RFC 5280), to resolve to the address of a 5GMSd AS in the target 5GMS System. The 5GMSd Application Provider shall use the HTTP POST method to create a new Server Certificate. Upon successful creation of the resource, the 5GMSd AF shall respond with a 201 (Created) response message and the URL of the resource, including its resource identifier, shall be returned in the HTTP Location header. The Content-Type response header and the body of the HTTP response message shall be as specified in clause 7.3.3.1. If the procedure is not successful, the 5GMSd AF shall provide a response code as defined in clause 6.3.

This procedure is used by the 5GMSd Application Provider to download a Server Certificate resource for inspection. The HTTP GET method shall be used for this purpose. If the requested resource exists and is populated with an X.509 certificate, the 5GMSd AF shall respond with 200 (OK) and shall return the requested Server Certificate in accordance with clause 7.3.3.2. In the case where the X.509 certificate was provisioned by the 5GMSd System on behalf of the 5GMSd Application Provider according to clause 4.3.6.2 above, the HTTP response 503 (Service Unavailable) shall be returned until such time as the X.509 certificate is generated and available for download. The optional HTTP response header Retry-After should be included in such a response, indicating when the certificate is expected to become available for inspection and use. In cases where the X.509 certificate is to be generated by the 5GMSd Application Provider from a Certificate Signing Request obtained according to clause 4.3.6.3 above, the HTTP response 204 (No Content) shall be returned until such time as the X.509 certificate has been uploaded using the procedure specified in clause 4.3.6.5 below.

This procedure is used by a 5GMSd Application Provider to upload an X.509 certificate that it has generated in response to a Certificate Signing Request solicited using the reservation procedure specified in clause 4.3.6.3 above. The HTTP PUT method shall be used for this purpose. The Content-Type request header and the body of the HTTP request message shall be as specified in clause 7.3.3.2. Before accepting the supplied X.509 certificate, the 5GMSd AF shall verify that the party originating the upload is the same party that reserved the Server Certificate resource using the procedure specified in clause 4.3.6.3 above. If there is a mismatch, the HTTP response 403 (Forbidden) shall be returned. Attempting to upload an X.509 certificate to a Server Certificate resource that has not been reserved shall elicit a 404 (Not Found) HTTP response.

Updating a previously uploaded Server Certificate is not permitted for security reasons. Any attempt to do so using the PUT method shall result in the HTTP response 405 (Method Not Allowed). To supply a replacement X.509 certificate, for example when a previously supplied certificate is shortly due to expire, the 5GMSd Application Provider should instead use one of the procedures specified in clause 4.3.6.2 or 4.3.6.3 above to create or reserve a new Server Certificate resource and, once the certificate is available for use, update the Content Hosting Configuration to reference it.

This procedure is used to remove a Server Certificate resource from a Provisioning Session. The HTTP DELETE method shall be used for this purpose. On success, the HTTP response 200 (OK) or 204 (No content) shall be returned and afterwards the identifier of the Service Certificate resource is no longer valid. Only the party that created (see clause 4.3.6.2) or reserved (see clause 4.3.6.3) the Server Certificate resource is permitted to destroy it. Any attempt by another party to destroy a Server Certificate resource shall elicit the HTTP response 405 (Method Not Allowed). The HTTP response 409 (Conflict) shall be returned if an attempt is made to destroy a Server Certificate resource that is currently referenced by a Content Hosting Configuration resource. Attempting to destroy a Server Certificate resource that has been reserved but never uploaded shall elicit a 200 (OK) HTTP response. In this case, the 5GMSd AF should release any resources associated with the reservation. If the procedure is not successful, the 5GMSd AF shall provide a response code as defined in clause 6.3.

These procedures are used by the 5GMS Application Provider to configure the Policy Templates for streaming sessions of a particular Provisioning Session. Figure 4.3.7.1-1 below is a state diagram showing the life-cycle of a Policy Template resource.

Since Policy Templates require 5GMS System operator verification, a Policy Template resource that is newly created cannot be used immediately. Upon creation, a Policy Template resource shall be in the PENDING state. Once all mandatory properties are provided, the 5GMS AF triggers validation. If the Policy Template is not deemed to be valid by the operator of the 5GMS System, it shall move to the INVALID state, from where it can be updated to remedy the defect. Once it has been successfully validated by the 5GMS System operator, a Policy Template resource shall take the READY state, indicating that it may be applied to media streaming sessions. If it is subsequently updated by the 5GMS Application Provider, a Policy Template resource shall return to the PENDING state, awaiting revalidation by the operator of the 5GMS System. Finally, a Policy Template resource may be SUSPENDED by the 5GMS System operator, e.g. in case of a violation of the usage terms or for some other reasons, which renders it unusable. The update of any property moves the state into PENDING and triggers revalidation. A Policy Template resource may be destroyed when it is in any of the abovementioned states. The 5GMS AF shall verify the status of a Policy Template resource prior to allowing a Dynamic Policy Instance to instantiate it. Only a Policy Template resource in the READY state is eligible to be instantiated in this way.

This procedure is used by the 5GMS Application Provider to create a new Policy Template resource. The HTTP POST method shall be used for this purpose. If the procedure is successful, the 5GMS AF shall generate a resource identifier to uniquely identify the newly created Policy Template resource. In that case, it shall respond with a 201 (Created) HTTP response message and provide the URL to the newly created resource in the Location header field. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3. The default state of a newly created Policy Template resource is PENDING. If all mandatory property values have been provided, the Policy Template resource is eligible for validation.

This procedure is used by the 5GMS Application Provider and other 5GMS AFs to query the properties of an existing Policy Template resource from the 5GMS AF. The HTTP GET method shall be used for this purpose. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) response that includes a copy of the Policy Template resource in the response message body. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

The update operation is invoked by the 5GMS Application Provider to modify the properties of an existing Policy Template resource. All available properties except state may be updated. The HTTP PATCH or HTTP PUT methods shall be used for the update operation. Any update to the Policy Template resource will change its state back to PENDING, which makes it temporarily unusable. If all mandatory property values have been provided, the Policy Template is eligible for revalidation. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) response message that includes a copy of the Policy Template resource in the response message body. Modifications to read-only properties, such as changes to the state of a Policy Template, shall be rejected with a 403 (Forbidden) HTTP response. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

This operation is used by the 5GMS Application Provider to destroy a Policy Template resource. The HTTP DELETE method shall be used for this purpose. As a result, the 5GMS AF will remove the Policy Template from any Provisioning Sessions that reference it. Currently active media streaming sessions using the destroyed Policy Template, if any exist, shall be stopped by the removal of the Policy Template. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) response message. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

These procedures are used by the 5GMSd Application Provider to activate and to configure consumption reporting. This clause defines the basic procedures. More details are provided in clause 7.7.

This procedure is used by the 5GMSd Application Provider to activate consumption reporting for a particular Provisioning Session. The 5GMSd Application Provider shall use the HTTP POST method to activate the consumption reporting procedure and to transmit the Consumption Reporting Configuration to the 5GMSd AF. Upon successful operation, the 5GMSd AF shall respond with a 201 (Created) response message and the same resource URL shall be returned in the Location header field. If the procedure is not successful, the 5GMSd AF shall provide a response code as defined in clause 6.3.

This procedure is used by the 5GMSd Application Provider to obtain the current Consumption Reporting Configuration from the 5GMSd AF. The 5GMSd Application Provider uses the GET method for this purpose.

The update operation is invoked by the 5GMSd Application Provider to modify the current Consumption Reporting Configuration. All available parameters may be updated. The HTTP PATCH or HTTP PUT methods shall be used for the update operation. If the procedure is successful, the 5GMSd AF shall respond with a 200 (OK) reflecting the successful update operation. If the procedure is not successful, the 5GMSd AF shall provide a response code as defined in clause 6.3.

This operation is used by the 5GMSd Application Provider to terminate the related consumption reporting procedure. The HTTP DELETE method shall be used for this purpose. As a result, the 5GMSd AF will release any associated resources, purge any cached data, and delete any corresponding configurations. If the procedure is successful, the 5GMSd AF shall respond with a 200 (OK) response message. If the procedure is not successful, the 5GMSd AF shall provide a response code as defined in clause 6.3.

These procedures are used by the 5GMS Application Provider to configure QoE metrics reporting functionality associated with downlink or uplink media streaming. This clause defines the basic procedures. More details are provided in clause 7.8.3.1. A given instance of a Metrics Reporting Configuration resource is identified by the metricsReportingConfigurationId property of the MetricsReportingConfiguration resource, The properties of that resource, as described in clause 7.8.3.1, pertain to metrics collection and reporting by the Media Session Handler to the 5GMS AF.

This procedure is used by the 5GMS Application Provider to create a Metrics Reporting Configuration resource for a particular Provisioning Session. The 5GMS Application Provider shall use the HTTP POST method for this purpose and the request message body may include a MetricsReportingConfiguration resource, as specified in clause 7.8.3.1. Upon successful operation, the 5GMS AF shall respond with a 201 (Created) response message and the resource URL for the newly-created Metrics Reporting Configuration resource shall be returned in the Location header field. If the procedure is unsuccessful, the 5GMS AF shall provide a response code as defined in clause 6.3. This procedure may be performed multiple times to provision different Metrics Reporting Configurations in the scope of a particular Provisioning Session. Each such configuration resource is represented by a different value of metricsReportingConfigurationId.

This procedure is used by the 5GMS Application Provider to obtain the properties of an existing Metrics Reporting Configuration resource from the 5GMS AF. The 5GMS Application Provider shall use the GET method for this purpose. If successful, the 5GMS AF shall respond with a 200 (OK) and the requested MetricsReportingConfiguration resource (see clause 7.8.3.1) shall be returned in the body of the HTTP response message. If the procedure is unsuccessful, the 5GMS AF shall provide a response code as defined in clause 6.3.

The update operation is invoked by the 5GMS Application Provider to initially upload the Metrics Reporting Configuration resource, or in the case of an existing Metrics Reporting Configuration resource, to entirely replace or modify certain properties of that resource. All available properties may be updated. The HTTP PATCH or HTTP PUT methods shall be used for the update operation. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) reflecting the successful update operation. If the procedure is unsuccessful, the 5GMS AF shall provide a response code as defined in clause 6.3.

This operation is used by the 5GMS Application Provider to destroy a Metrics Reporting Configuration resource and to terminate the related metrics reporting procedure. The HTTP DELETE method shall be used for this purpose. As a result, the 5GMS AF should release any associated resources, discard any pending metrics reports, and delete any corresponding configurations. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) response message. If the procedure is unsuccessful, the 5GMS AF shall provide a response code as defined in clause 6.3.

These procedures are used by the 5GMS Application Provider and the 5GMS AF at reference point M1d to provision edge resources for downlink streaming.

This procedure is used by the 5GMS Application Provider to create a new Edge Resources Provisioning Configuration. The 5GMS Application Provider shall use the HTTP POST method for this purpose and the request message body shall include an EdgeResourcesConfiguration resource, as specified in clause 7.10.3.1.

• If the edgeManagmentMode is set to EM_AF_DRIVEN (indicating AF-driven edge resource management), the 5GMS AF is responsible for requesting and managing the required edge resources and for handling EAS relocation in relation to media streaming sessions that fall within the scope of the parent Provisioning Session.
• If the edgeManagementMode is set to EM_CLIENT_DRIVEN (indicating client-driven edge resource management), the 5GMS AF shall only request edge resources based on requests from the EEC instantiated in the Media Session Handler at reference point EDGE-1.

If the procedure is successful, the 5GMS AF shall generate a resource identifier representing the new Edge Resources Provisioning Configuration. In this case, the 5GMS AF shall respond with a 201 (Created) HTTP response message and shall provide the URL to the newly created resource in the Location header field. The response message body may include an EdgeResourcesConfiguration resource (see clause 7.10.3.1) that represents the current state of the Edge Resources Provisioning Configuration, including any fields set by the 5GMS AF. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

This procedure is used by the 5GMS Application Provider to retrieve the current values of the properties of an existing Edge Resources Provisioning Configuration resource from the 5GMS AF. The HTTP GET method shall be used for this purpose. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) response message that includes the EdgeResourcesConfiguration resource in the response message body. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

The update operation is invoked by the 5GMS Application Provider to modify the properties of an existing EdgeResourcesConfiguration resource. All writeable properties except edgeManagementMode may be updated. The HTTP PATCH or HTTP PUT methods shall be used for the update operation. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) and provide the content of the resource in the response, confirming the successful update operation. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

This operation is used by the 5GMS Application Provider to destroy an Edge Resources Provisioning Configuration resource. The HTTP DELETE method shall be used for this purpose. This operation makes the configuration unsuable for future media streaming sessions, but it does not affect any ongoing media streaming sessions. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) response message. If the procedure is not successful, the 5GMS AF shall provide a response code as defined in clause 6.3.

These procedures are used by the 5GMS Application Provider to configure the collection and processing of UE data related to 5G Media Streaming over reference point M1 (as defined in TS 26.531) and to restrict its exposure over reference points R5 and R6 by configuring the Data Collection AF instantiated in the 5GMS AF (as defined in clause 4.7 of TS 26.501) with one or more Event Data Processing Configurations and Data Access Profiles for a particular Event ID. Each instance of a Data Access Profile specifies a set of data processing operations to be performed by the Data Collection AF on its collected UE data in order to synthesize the event data to be exposed to a specific Event service consumer entity. In this release, eligible Event service consumer entities of 5GMS event data are the NWDAF, the Event Consumer AF and the NEF. The Event Data Processing Provisioning API is specified in clause 7.11.

This procedure is used by the 5GMS Application Provider to create a new Event Data Processing Configuration in the form of one or more Data Access Profiles. The 5GMS Application Provider shall use the HTTP POST method for this purpose and the request message body shall include an EventDataProcessingConfiguration resource, as specified in clause 7.11.3. If the procedure is successful, the 5GMS AF shall generate a resource identifier representing the new Event Data Processing Configuration. In this case, the 5GMS AF shall respond with a 201 (Created) response message and shall provide the URL to the newly created resource in the Location header field. If the procedure is unsuccessful, the 5GMS AF shall provide a response code as defined in clause 6.3.

This procedure is used by the 5GMS Application Provider to obtain the properties of an existing Event Data Processing Configuration resource from the 5GMS AF. The HTTP GET method shall be used for this purpose. If the procedure is unsuccessful, the 5GMS AF shall provide a response code as defined in clause 6.3.

This operation is used by the 5GMS Application Provider to destroy an existing Event Data Processing Configuration resource and to terminate the related distribution. The HTTP DELETE method shall be used for this purpose. As a result, the Data Collection AF shall process any reported UE data still outstanding and shall delete any corresponding data collection and reporting client configurations. If the procedure is successful, the 5GMS AF shall respond with a 200 (OK) response message. If the procedure is unsuccessful, the 5GMS AF shall provide a response code as defined in clause 6.3.