SBI Message Priority Mechanism
The primary usage of SBI Message Priority (SMP) is to provide guidance to 5GC NF acting as HTTP/2 clients or servers while making throttling decisions related to overload control. You can use the priority information for routing in the proxies. Eventually a server uses the priority information to process higher-priority requests before lower-priority requests. The SMP mechanism uses the "3gpp-Sbi-Message-Priority" custom HTTP header to set and carry the message priority between the client and the server. The custom HTTP header enforces the message priority end to end between the client and the server through one or more proxies.
Note | Stream Priority mechanism is not supported. |
The header contains the HTTP/2 message priority value: The encoding of the header follows the ABNF as defined in IETF RFC 7230 [12].
3gpp-Sbi-Message-Priority = "3gpp-Sbi-Message-Priority" ":" (DIGIT / %x31-32 DIGIT / "3" %x30-31)
A message with 3gpp-Sbi-Message-Priority "0"
has the highest priority.Example:
3gpp-Sbi-Message-Priority: 10