5.2 Usage of HTTP

29.5123GPP5G SystemRelease 18Session Management Policy Control ServiceStage 3TS

5.2.1 General

HTTP/2, IETF RFC 7540 [8], shall be used as specified in clause 5 of 3GPP TS 29.500 [4].

HTTP/2, shall be transported as specified in clause 5.3 of 3GPP TS 29.500 [4].

An OpenAPI [10] specification of HTTP messages and content bodies for the Npcf_SMPolicyControl is contained in Annex A.

5.2.2 HTTP standard headers

5.2.2.1 General

See clause 5.2.2 of 3GPP TS 29.500 [4] for the usage of HTTP standard headers.

5.2.2.2 Content type

JSON, IETF RFC 8259 [9], shall be used as content type of the HTTP bodies specified in the present specification as specified in clause 5.4 of 3GPP TS 29.500 [4]. The use of the JSON format shall be signalled by the content type "application/json".

"Problem Details" JSON object shall be used to indicate additional details of the error in a HTTP response body and shall be signalled by the content type "application/problem+json", as defined in IETF RFC 7807 [31].

5.2.3 HTTP custom headers

5.2.3.1 General

The Npcf_SMPolicyControl API shall support HTTP custom header fields specified in clause 5.2.3.2 of 3GPP TS 29.500 [4] and may support HTTP custom header fields specified in clause 5.2.3.3 of 3GPP TS 29.500 [4].

5.2.3.2 3gpp-Sbi-Origination-Timestamp

The header contains the date and time (with a millisecond granularity) when the originating entity initiated the request as specified in clause 6.1.2.3.2 of 3GPP TS 29.502 [22].