11 Supported 3GPP Headers
The following table lists the headers supported by SCP:
Table 11-1 Supported 3GPP Custom Headers
| Custom Header Name | Description |
|---|---|
| 3gpp-Sbi-Message-Priority | This header is used to specify the HTTP/2 message priority for 3GPP service based interfaces. |
| 3gpp-Sbi-Callback | The header is used to identify a particular type of callback, for example, notification. |
| 3gpp-Sbi-Target-apiRoot | The header contains the apiRoot of the target URI in a
message request sent to an SCP instance when using indirect
communication such as Model C and Model D. SCP uses this header to
indicate the apiRoot of the target URI if a new HTTP server is selected
or reselected and if there is no location header in the message
response.
SCP adds this header to message responses when:
|
| 3gpp-Sbi-Routing-Binding | This header is used in a service request to signal binding information to direct the service request to an HTTP server that has the targeted NF service resource context. |
| 3gpp-Sbi-Binding | This header is used to signal binding information related to an NF service resource to a future consumer, such as an HTTP client, of that resource. |
| 3gpp-Sbi-Discovery-* | This header, which begins with the prefix 3gpp-Sbi-Discovery, is used in indirect communication mode for discovery and selection of a suitable producer by the SCP. Such headers can be included in any SBI message and include information allowing an SCP to find a suitable producer based on the consumer's included delegated discovery parameters. |
| 3gpp-Sbi-Oci | This header is utilized by overloaded SCPs, SEPPs, consumer NFs, and producer NFs to transmit Overload Control Information (OCI) within message requests and responses to peers. The OCI includes attributes such as Overload Timestamp, Overload-Reduction-Metric, Period-of-Validity, and Scope within the 3gpp-Sbi-Oci header. |
| 3gpp-Sbi-Producer-Id | This header contains Instance ID of the producer NF. In
case of producer selection or reselection (i.e. alternate routing) in
indirect communication modes such as Model C or Model D, this header is
used in a message response from SCP to the consumer NF to identify the
producer NF.
SCP adds this header to message responses when:
|
| 3gpp-Sbi-Lci | This header is used by a producer NF to send Load Control Information (LCI) to the consumer NF. |
| 3gpp-Sbi-Client-Credentials | This header is used by a consumer NF to send a Client Credential Assertion (CCA) to the NRF or to the producer NF. |
| 3gpp-Sbi-Target-Nf-Id | This header is used in a 307 Temporary Redirect or 308 Permanent Redirect response to identify the target NF service instance towards which the request is redirected. |
| 3gpp-Sbi-Access-Scope | This header is used in a service request for indirect communication to indicate the access scope of the service request for NF service access authorization. |
| 3gpp-Sbi-Access-Token | This header is used in a service response forwarded by the SCP to an NF service consumer to provide an access token for possible reuse in subsequent service requests. |
| 3gpp-Sbi-Correlation-Info | This header may be used to contain correlation information, for example, UE identity, that may be used by an operator in various offline network management, performance analysis and troubleshooting tools/applications to identify messages (requests, responses, subscriptions, notifications) related to a particular subscriber. |
SCP also supports the HTTP standard headers. For more information, see 3GPP TS 29.500 V16.10.0, Table 5.2.2.2-1.