SbiPriority

3gpp-Sbi-Message-Priority (SMP) custom header is used to specify the HTTP/2 message priority for 3GPP service-based interfaces.

As per 3GPP TS 29.500, the primary usage of SBI Message Priority (SMP) is to provide guidance to 5GC NF acting as HTTP/2 clients or servers and HTTP/2 proxies when making throttling decisions related to overload control. The priority information may also be used for routing in proxies. Eventually a server may use the priority information to process higher-priority requests before lower-priority requests.

5G-EIR shall support processing of 3gpp-Sbi-Message-Priority (SMP) header received in the N5g-eir_EquipmentIdentityCheck Get service request from AMF. On receiving the SMP header in the request, EIR shall propagate appropriate ldap qos information to OneNDS/SDL in ldap query/update message so that the downstream call legs are also prioritized according to the SMP.

N5g-eir_EquipmentIdentityCheck Get service response also shall carry the 3gpp-Sbi-Message-Priority (SMP) header with appropriate value to ensure the response is processed by the consumer NF.

Additionally, 5G-EIR shall support sending the same priority value in the N5g-eir_EquipmentIdentityCheck Get service response for defined list of priority values. This requirement is a stretch object.

Note: SBI traffic throttling based on SMP is out of scope in step1. It will be handled in future releases.

Nokia 5G-EIR currently does not support processing of the SMP header received in the N5g-eir_EquipmentIdentityCheck_Get service request from AMF.

The feature requirement is for Nokia 5G-EIR to support the processing of 3gpp-Sbi-Message-Priority (SMP) custom header received in the N5g-eir_EquipmentIdentityCheck_Get service request from AMF.