3gpp-Sbi-Target-apiRoot Header

While sending notification to peer NF, the SMF replaces the "api root" of the "target api" with the "scp api root" and includes the "target api root" in the "3gpp-sbi-target-apiRoot" header.

For example, if the SMF sends the notification "POST https://scp.com/a/b/c/notification" to the SCP, with the "3gpp-sbi-target-apiRoot" header set to "https://example.com", then the SCP sends the request "POST https://example.com/a/b/c/notification" to the NF Service Producer, without the "3gpp-sbi-target-apiRoot" header.

Note

SMF doesn't support the SCP "apiPrefix".

The SMF doesn't include the "3gpp-sbi-target-apiRoot" header in the initial request to the peer NF for a specific session. SMF extracts the "target api" prefix of the resource from the "location" header of the response. Then, SMF includes this prefix in the "3gpp-sbi-target-apiRoot" header in a subsequent message to the peer NF for the same session.

For example, When the SMF receives the following "location" header in the N7 Create Response:

http://209.165.200.230:9082/npcf-smpolicycontrol/v1/sm-policies/ism.14.imsi-310260157090153.1660028704.43993.7129768994171956185

Then, the SMF sends the following SMPolicy Update message:

http://scpIP:port/npcf-smpolicycontrol/v1/sm-policies/

ism.14.imsi-310260157090153.1660028704.43993.7129768994171956185

Where

"authority header" is "scpIP"

"3gpp-sbi-target-apiRoot" is 209.165.200.230:9082

Note

SMF also includes "3gpp-sbi-target-apiRoot" header in the messages that are intended to operate on a resource that the peer has already created. For example, when the SMF sends the N10 Deregistration message to UDM, the SMF uses the "location" header that the SMF receives in N10 Registration response to populate the "3gpp-sbi-target-apiRoot" header.