6.2.2 Usage of HTTP

29.5623GPP5G SystemHome Subscriber Server (HSS) servicesRelease 18Stage 3TS

6.2.2.1 General

HTTP/2, as defined in 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].

HTTP messages and bodies for the Nhss_imsSubscriberDataManagement service shall comply with the OpenAPI [9] specification contained in Annex A.3.

6.2.2.2 HTTP standard headers

6.2.2.2.1 General

The usage of HTTP standard headers shall be supported as specified in clause 5.2.2 of 3GPP TS 29.500 [4].

6.2.2.2.2 Content type

The following content types shall be supported:

– JSON, as defined in IETF RFC 8259 [10], signalled by the content type "application/json".

– The Problem Details JSON Object (IETF RFC 7807 [11] signalled by the content type "application/problem+json"

– JSON Patch, as defined in IETF RFC 6902 [12], signalled by the content type "application/json-patch+json"

6.2.2.3 HTTP custom headers

6.2.2.3.1 General

The usage of HTTP custom headers shall be supported as specified in clause 5.2.3 of 3GPP TS 29.500 [4].