L Use Cases for Setting SBI Message Priority

This section describes the use cases supported by the Setting SBI Message Priority feature. The use cases illustrate how the 3gpp-Sbi-Message-Priority header is determined and applied based on configuration and incoming request characteristics.

Use Case Types: The Setting SBI Message Priority feature supports the following use case types:

Notes

The common points for use cases are defined to capture the baseline behavior and rules that apply consistently across all use case scenarios:
  • The discovery response corresponding to the SLF response will follow the rules defined for NRF acting as a server for the NFDiscover service operation.
  • For certain use cases, such as forwarding and roaming, NRF sends requests to a peer NF. If an error occurs within NRF while it is acting as an NF and sending the message to the peer, the response generated toward the client NF will follow NRF standalone server rules. In such scenarios, the Back-to-Back server rules defined for forwarding and roaming cases will not be applied.
  • Header names in incoming requests are matched in a case-insensitive manner with the configuration.
  • Headers in both generated requests and responses from NRF will always be in lowercase.
  • When rule values are incremented or decremented, the final value is restricted to the range of 0–31. Values below 0 are set to 0, and values above 31 are capped at 31.
  • Whenever NRF functions as either a server or a client, a rule must be defined for the configured default value; otherwise, the header will not be included in outgoing requests or generated responses for the default case.
  • If the feature is disabled, NRF will not add the header to either requests or responses, even if the header is present in the incoming request or response.
  • Rule matching follows this order: exact match, range-based match, and finally the default match (*).
  • For received requests, ocnrf_smp_parsing_error_total metric is pegged using the service operation handled in server mode. For received responses, the metric is pegged using the service operation handled in client mode.
  • The 3gpp-Sbi-Message-Priority header applies only to API and method combinations defined for NRF. If an invalid combination is used, the header will not be added to generated requests or responses.
  • When NRF sends a request to a peer NRF (for example, in forwarding or roaming scenarios), the 3gpp-Sbi-Message-Priority header received in the response is considered for response mapping only if the corresponding header was included in the outbound request through a valid initiatedRequestPriorityRule mapping. If the header is not included in the outbound request due to a missing or unmatched request mapping, any 3gpp-Sbi-Message-Priority returned in the response is not recognized as an SMP-specific header and is therefore ignored for propagated response mapping. In such cases, NRF uses the defaultPriority configured in the applicable response rules for the corresponding scenario and applies the configured responsePriorityRule to determine the response priority.
.

L.1 Standalone Server Role

NRF is receiving a request from Consumer NFs and returning a response towards consumer NFs (without sending messages to any peer NFs).

In standalone server role, the priority value is derived from the incoming request and applied to the response using the configured responsePriorityRule.

Service Operations and Corresponding Configuration for Standalone Server

The following table lists the service operations and corresponding sbiServiceOperation configurations used for standalone server role.

Table L-1 Service Operations and Corresponding Configuration for Standalone Server Role

Service Operations API HTTP Method sbiServiceOperation Configuration

NF Register

NF Update Complete Replacement

 /nnrf-nfm/v1/nf-instances/<nfInstanceID> PUT Nnrf_NFManagement_NFRegister_FullUpdate

NF Update Partial

NF Heartbeat

 /nnrf-nfm/v1/nf-instances/<nfInstanceID> PATCH Nnrf_NFManagement_NFHeartBeat_NFPartialUpdate
NF Deregister /nnrf-nfm/v1/nf-instances/<nfInstanceID> DELETE Nnrf_NFManagement_NFDeregister
NF OPTIONS /nnrf-nfm/v1/nf-instances/ OPTIONS Nnrf_NFManagement_Options
NF LIST RETRIEVAL /nnrf-nfm/v1/nf-instances/ GET Nnrf_NFManagement_NFListRetrieval
NF INSTANCE RETRIEVAL /nnrf-nfm/v1/nf-instances/<nfInstanceID> GET Nnrf_NFManagement_NFProfileRetrieval
NF Status Subscribe /nnrf-nfm/v1/subscriptions POST Nnrf_NFManagement_NFStatusSubscribe
NF Status Subscribe Update /nnrf-nfm/v1/subscriptions/<subscriptionID> PATCH Nnrf_NFManagement_NFStatusSubscribeUpdate
NF Status Unsubscribe /nnrf-nfm/v1/subscriptions/<subscriptionID> DELETE Nnrf_NFManagement_NFStatusUnSubscribe
NF Discover /nnrf-disc/v1/nf-instances GET Nnrf_NFDiscovery_Request
NF Access Token /oauth2/token POST Nnrf_AccessToken_Get
CDS Response

/nrfcache-data/v1/nf-instances/nrfset-data/v1/nf-subscriptions

 GET Nnrf_CacheData_Response

Use Case Scenarios for Standalone Server

The following table describes the use case scenarios for standalone server role, including the applicable conditions and the corresponding behavior of the Setting SBI Message Priority feature.

Table L-2 Use Case Scenarios For Standalone Server Role

Use Case Description Use Case Type Incoming Header Request SMP Feature Configuration Response and Observability

SBI message priority feature - ENABLED

SBI Message Priority header in incoming service operation - VALID

Corresponding sbiServiceOperation - Configured

responsePriorityRule - Configured

rule corresponding to SBI Message Priority header value is configured with range and default match (that is,. *) and range is not matching

 Header is present in the Request and configured in requestsmpheaders configuration "3gpp-Sbi-Message-Priority"="12"

/nf-common-component/v1/global-configuration/sbiserviceoperations

"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"

and

/nf-common-component/v1/global-configuration/prioritymappingrules

"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-15",
                    "used": "14" }, "received":
                    "*", "used": "11"
                    }] }]"

and

/nf-common-component/v1/global-configuration/requestsmpheaders

"["3gpp-Sbi-Message-Priority"]"

NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected.

If a range-based value match rule is configured but not matching, then the rule is applied. The mapped value is sent for the SBI message priority header in the response.

"3gpp-Sbi-Message-Priority"="11"

Observability: None

SBI message priority feature - ENABLED

SBI Message Priority header in incoming Service operation - VALID

Corresponding sbiServiceOperation - Configured

responsePriorityRule - Configured

rule corresponding to SBI Message Priority header value is configured range value match only.

 Header is present in Request and configured in requestsmpheaders Configuration "3gpp-Sbi-Message-Priority"="12"

/nf-common-component/v1/global-configuration/sbiserviceoperations

"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"

and

/nf-common-component/v1/global-configuration/prioritymappingrules

"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12-16",
                    "used": "11" }] }]"

and

/nf-common-component/v1/global-configuration/requestsmpheaders

"["3gpp-Sbi-Message-Priority"]"

NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected,

range based value match rule is selected and the mapped value is sent for Sbi Message Priority Header in the response.

"3gpp-Sbi-Message-Priority"="17"

Observability: None

SBI message priority feature - ENABLED

SBI Message Priority header in incoming Service operation - VALID

Corresponding sbiServiceOperation - Configured

responsePriorityRule - Configured

Matching rule for incoming header value - Not Configured

 Header Present in Request and configured in requestsmpheaders Configuration "3gpp-Sbi-Message-Priority"="12"

/nf-common-component/v1/global-configuration/sbiserviceoperations

"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"

and

/nf-common-component/v1/global-configuration/prioritymappingrules

"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "11" }] }]"

and

/nf-common-component/v1/global-configuration/requestsmpheaders

"["3gpp-Sbi-Message-Priority"]"

NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected,

No Rule Found for Value 12. No SMP header will go in the response

Observability: None

SBI message priority feature - DISABLED

SBI Message Priority header in incoming Service operation - VALID

Corresponding sbiServiceOperation - Configured

responsePriorityRule - Configured

rule corresponding to SBI Message Priority header value is configured with exact value match, range and default match (that is,. *)

 Header Present in Request and configured in requestsmpheaders Configuration "3gpp-Sbi-Message-Priority"="12"

/nf-common-component/v1/global-configuration/sbiserviceoperations

"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"

and

/nf-common-component/v1/global-configuration/prioritymappingrules

"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"

and

/nf-common-component/v1/global-configuration/requestsmpheaders

"["3gpp-Sbi-Message-Priority"]"

Feature is disabled. No header will go in the response even they are present in request.

Observability: None

SBI message priority feature - ENABLED

SBI Message Priority header in incoming Service operation - INVALID

Corresponding sbiServiceOperation - Configured

responsePriorityRule - Configured

rule corresponding to SBI Message Priority header value is configured with range and default match (that is,. *)

 Header Present in Request and configured in requestsmpheaders Configuration "3gpp-Sbi-Message-Priority"="35"

/nf-common-component/v1/global-configuration/sbiserviceoperations

"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"
and

/nf-common-component/v1/global-configuration/prioritymappingrules

"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "15-20",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"

and

/nf-common-component/v1/global-configuration/requestsmpheaders

"["3gpp-Sbi-Message-Priority"]"

Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected,range based value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.

"3gpp-Sbi-Message-Priority"="14"

Observability: None

SBI message priority feature - ENABLED

SBI Message Priority header in incoming Service operation - INVALID

Corresponding sbiServiceOperation - Configured

responsePriorityRule - Configured

rule corresponding to SBI Message Priority header value is configured with default match (that is,. *) only

 Header Present in Request and configured in requestsmpheaders Configuration "3gpp-Sbi-Message-Priority"="35"

/nf-common-component/v1/global-configuration/sbiserviceoperations

"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"

and

/nf-common-component/v1/global-configuration/prioritymappingrules

"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "*",
                    "used": "16" }] }]"

and

/nf-common-component/v1/global-configuration/requestsmpheaders

"["3gpp-Sbi-Message-Priority"]"

Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected,default value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.

"3gpp-Sbi-Message-Priority"="16"

Observability: None

SBI message priority feature - ENABLED

SBI Message Priority header in incoming Service operation - INVALID

Corresponding sbiServiceOperation - Configured

responsePriorityRule - Configured

rule corresponding to SBI Message Priority header value is configured with range match only

 Header Present in Request and configured in requestsmpheaders Configuration "3gpp-Sbi-Message-Priority"="35"

/nf-common-component/v1/global-configuration/sbiserviceoperations

"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"

and

/nf-common-component/v1/global-configuration/prioritymappingrules

"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "16-20",
                    "used": "18" }] }]"

and

/nf-common-component/v1/global-configuration/requestsmpheaders

"["3gpp-Sbi-Message-Priority"]"

Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected,range based value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.

"3gpp-Sbi-Message-Priority"="18"

Observability: None

SBI message priority feature - ENABLED

SBI Message Priority header in incoming Service operation - INVALID

Corresponding sbiServiceOperation - Configured

responsePriorityRule - Configured

Matching rule for default configured value - NA

 Header Present in Request and configured in requestsmpheaders Configuration "3gpp-Sbi-Message-Priority"="-1"

/nf-common-component/v1/global-configuration/sbiserviceoperations

"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"

and

/nf-common-component/v1/global-configuration/prioritymappingrules

"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"

and

/nf-common-component/v1/global-configuration/requestsmpheaders

"["3gpp-Sbi-Message-Priority"]"

Rule is not configured for defaultPriority. No SMP header will go in the response.

Observability: Metric will be pegged with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - INVALID

                                    
Corresponding sbiServiceOperation - Not Configured

                                    
responsePriorityRule - NA

                                    
Matching rule for incoming header value - NA

                                 		
                                 Header Present in Request and configured in requestsmpheaders Configuration
                                  "3gpp-Sbi-Message-Priority"="-1"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Request", "defaultPriority": 18, "preferReceivedPriority": true }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
SBI Service operation is not configured for the incoming request. No SMP header will go in the response.

                                    
Observability: Metric will be pegged with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - DISABLED

                                    
SBI Message Priority header in incoming Service operation - INVALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with exact value match, range and default match (that is,. *)

                                 		
                                 Header Present in Request and configured in requestsmpheaders Configuration
                                  "3gpp-Sbi-Message-Priority"="-2"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Feature is disabled. No header will go in the response even they are present in request.

                                    
Observability: None

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation -NOT PRESENT/CANNOT BE USED

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with range and default match (that is,. *)

                                 		
                                 
                                    
Header Present in Request and not configured in requestsmpheaders configuration 

                                    
Header Not Present in Request but configured in requestsmpheaders configuration 

                                    
Header Not Present in Request and not configured in requestsmpheaders configuration

                                 		
                                 -
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule", "initiatedRequestPriorityRule": "" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "15-20",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority", "Custom-SMP-Header"]"		
                                 
                                    
Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected,range based value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.
"3gpp-Sbi-Message-Priority"="14"
Observability: None

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation -NOT PRESENT/CANNOT BE USED

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with default match (that is,. *) only

                                 		
                                 
                                    
Header Present in Request and not configured in requestsmpheaders configuration 

                                    
Header Not Present in Request but configured in requestsmpheaders configuration 

                                    
Header Not Present in Request and not configured in requestsmpheaders configuration

                                 		
                                 -
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "*",
                    "used": "16" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected,default value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.
"3gpp-Sbi-Message-Priority"="16"
Observability: None.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation -NOT PRESENT/CANNOT BE USED

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with range match only

                                 		
                                 
                                    
Header Present in Request and not configured in requestsmpheaders configuration 

                                    
Header Not Present in Request but configured in requestsmpheaders configuration 

                                    
Header Not Present in Request and not configured in requestsmpheaders configuration

                                 		
                                 -
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "16-20",
                    "used": "18" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected,range based value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response. 
"3gpp-Sbi-Message-Priority"="18"
Observability: None

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation -NOT PRESENT/CANNOT BE USED

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
Matching rule for default configured value - NA

                                 		
                                 
                                    
Header Present in Request and not configured in requestsmpheaders configuration. 

                                    
Header Not Present in Request but configured in requestsmpheaders configuration.

                                    
Header Not Present in Request and not configured in requestsmpheaders configuration,

                                 		
                                 -
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Rule is not configured for defaultPriority. The SMP header will not go in the response.

                                    
Observability: Metric will be pegged with reason.

                                 		
                              

                              

                                 
                                    
    
                                       
  • SBI message priority feature - DISABLED
    • 
                                       
  • SBI Message Priority header in incoming Service operation -NOT PRESENT or CANNOT BE USED
    • 
                                       
  • Corresponding sbiServiceOperation - Configured
    • 
                                       
  • responsePriorityRule - Configured
    • 
                                       
  • rule corresponding to SBI Message Priority header value is configured with exact value match, range and default match (that is,. *)
    • 
                                    

                                 		
                                 
                                    
Header Present in Request and not configured in requestsmpheaders configuration 

                                    
Header Not Present in Request but configured in requestsmpheaders configuration 

                                    
Header Not Present in Request and not configured in requestsmpheaders configuration

                                 		
                                 -
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFRegister_FullUpdate", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Rule" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Feature is disabled. The SMP header will not go in the response even they are present in the request.

                                    
Observability: None.

                                 		
                              

                           
                        

                     

                  

               

            

            
L.2 Standalone Client Role
               

               

                  
In this role, NRF is generating a request of its own without getting any request from Consumer NF.

                  
In this role, NRF initiates requests and determines the 3gpp-Sbi-Message-Priority header value based on the configured service operation behavior and priority mapping rules.
                  

                  

                     
Service Operations and Corresponding Configuration for Standalone Client

                     
The following table lists the service operations and corresponding sbiServiceOperation configurations used for standalone client role.
                     

                     

                        
Table L-3 Service Operations and Corresponding sbiServiceOperation Configuration for Standalone Client Role

                        

                           
                              

                                 Service Operation
                                 API
                                 HTTP Method
                                 sbiServiceOperation
                              

                           
                           
                              

                                 NF Status Notify
                                 Will be generated internally by NRF
                                 POST
                                 Nnrf_NFManagement_NFStatusNotify
                              

                              

                                 CDS Request Generated
                                 
                                    
/nrfcache-data/v1/nf-instances

                                    
/nrfset-data/v1/nf-subscriptions

                                 		
                                 GET
                                 Nnrf_CacheData_Request
                              

                              

                                 CDS Periodic Request
                                 /nrfset-data/v1/nf-instances?
                                 GET
                                 Nnrf_CacheData_PeriodicRequest
                              

                              

                                 CDS Request Generated by NRF Configuration
                                 
                                    
/nrfcache-data/v1/nf-instances

                                    
/nrfset-data/v1/nf-subscriptions

                                 		
                                 GET
                                 Nnrf_Configuration_CacheData_Request
                              

                           
                        

                     

                  

                  

                     
Use Case Scenarios for Standalone Client Role

                     
The following table describes the use case scenarios for standalone client role, including the applicable conditions and the corresponding behavior of the Setting SBI Message Priority feature.

                     

                     

                        
Table L-4 Use Case Scenarios for Standalone Client Role

                        

                           
                              

                                 Use Case Description
                                 Use Case Type
                                 Incoming Header Request
                                 SMP Feature Configuration
                                 Response and Observability
                              

                           
                           
                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule- Configured

                                    
rules - Configured as range matching for default value

                                 		
                                 NA
                                 NA
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations

                                    

"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFStatusNotify",
 "defaultPriority": 18,
 "preferReceivedPriority": true,
 "initiatedRequestPriorityRule": "NRF_As_Client_Notification" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules

"[{ "name": "NRF_As_Client_Notification", 
    "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority",
     "rules":
            [{ "received": "15-20",
               "used": "14" }, "received":
               "*", "used": "16"
              }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders

                                    
"["3gpp-Sbi-Message-Priority"]"

                                 		
                                 
                                    
NRF_As_Client_Notification corresponding to initiatedRequestPriorityRule rule is selected,

                                    
Header Name comes from defaultSmpHeaderName

                                    
And value comes from defaultPriority.

                                    
Range based rule is matched and hence corresponding value will go in the request "3gpp-Sbi-Message-Priority"="14"

                                    
Observability: None.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule- Not Configured

                                 		
                                 NA
                                 NA
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations

                                    
"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFStatusNotify", "defaultPriority": 18, "preferReceivedPriority": true }]"

                                    
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Notification", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders

                                    
"["3gpp-Sbi-Message-Priority"]"

                                 		
                                 
                                    
initiatedRequestPriorityRule rule is not configured.

                                    
The header name comes from defaultSmpHeaderName, and the header and rules are not configured. So, the header will not go.

                                    
Observability: Metric will peg with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
Corresponding sbiServiceOperation - Not Configured

                                    
initiatedRequestPriorityRule- Not Configured

                                 		
                                 NA
                                 NA
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations

                                    
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Request", "defaultPriority": 18, "preferReceivedPriority": true }]"
 

                                    
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Notification", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders

                                    
"["3gpp-Sbi-Message-Priority"]"

                                 		
                                 
                                    
initiatedRequestPriorityRule rule is not configured, SBI operation is not configured

                                    
The header name comes from defaultSmpHeaderName, and rules are not configured. So, the header will not go.

                                    
Observability: Metric will peg with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - DISABLED

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule- Configured

                                    
rules configured - Does not matter as client

                                 		
                                 NA
                                 NA
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations

                                    
"[{ "sbiServiceOperation": "Nnrf_NFManagement_NFStatusNotify", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "", "initiatedRequestPriorityRule": "NRF_As_Client_Notification" }]"

                                    
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Notification", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders

                                    
"["3gpp-Sbi-Message-Priority"]"

                                 		
                                 
                                    
Feature is disabled. No header will go in request.

                                    
Observability: None.

                                 		
                              

                           
                        

                     

                  

               

            

            
L.3 Back-to-Back Agent Client Role
               

               

                  
In this role, NRF receives a request from Consumer NF and sends the request to peer NF.

                  
In this role, NRF forwards requests to target network functions (for example, AMF, SMF, PCF) and determines the 3gpp-Sbi-Message-Priority header value based on the configured service operation behavior and priority mapping rules.
                  

                  

                     
Service Operations and Corresponding Configuration for Back-to-Back Agent Client Role

                     
This table is used to determine the applicable configuration for deriving and applying the priority value when forwarding requests.

                     
The following table lists the service operations and corresponding sbiServiceOperation configurations used for back-to-back agent client role.
                     

                     

                        
Table L-5 Service Operations and Corresponding sbiServiceOperation Configuration

                        

                           
                              

                                 Service Operation
                                 API
                                 HTTP Method
                                 sbiServiceOperation
                              

                           
                           
                              

                                 NF Profile Retrieval Forwarding Request
                                 /nnrf-nfm/v1/nf-instances/<nfInstanceID>
                                 GET
                                 Nnrf_NFManagement_NFProfileRetrieval_Forward_Request
                              

                              

                                 NF Status Subscribe Create Forwarding Request
                                 /nnrf-nfm/v1/subscriptions
                                 POST
                                 Nnrf_NFManagement_NFStatusSubscribe_Forward_Request
                              

                              

                                 NF Status Subscribe Create Roaming Request
                                 /nnrf-nfm/v1/subscriptions
                                 POST
                                 Nnrf_NFManagement_NFStatusSubscribe_Roaming_Request
                              

                              

                                 NF Status Subscribe Update Forwarding Request
                                 /nnrf-nfm/v1/subscriptions
                                 PATCH
                                 Nnrf_NFManagement_NFStatusSubscribeUpdate_Forward_Request
                              

                              

                                 NF Status Subscribe Update Roaming Request
                                 /nnrf-nfm/v1/subscriptions
                                 PATCH
                                 Nnrf_NFManagement_NFStatusSubscribeUpdate_Roaming_Request
                              

                              

                                 NF Status UnSubscribe Forwarding Request
                                 /nnrf-nfm/v1/subscriptions
                                 DELETE
                                 Nnrf_NFManagement_NFStatusUnSubscribe_Forward_Request
                              

                              

                                 NF Status UnSubscribe Roaming Request
                                 /nnrf-nfm/v1/subscriptions
                                 DELETE
                                 Nnrf_NFManagement_NFStatusUnSubscribe_Roaming_Request
                              

                              

                                 NF Discover Forwarding Request
                                 /nnrf-disc/v1/nf-instances
                                 GET
                                 Nnrf_NFDiscovery_Forward_Request
                              

                              

                                 NF Discover Roaming Request
                                 /nnrf-disc/v1/nf-instances
                                 GET
                                 Nnrf_NFDiscovery_Roaming_Request
                              

                              

                                 SLF Request
                                 /nudr-group-id-map/v1/nf-group-ids
                                 GET
                                 Nnrf_NFDiscovery_SLF
                              

                              

                                 NF Access Token Forwarding Request
                                 /oauth2/token
                                 POST
                                 Nnrf_AccessToken_Forward_Request
                              

                              

                                 NF Access Token Roaming Request
                                 /oauth2/token
                                 POST
                                 Nnrf_AccessToken_Roaming_Request 
                              

                           
                        

                     

                  

                  

                     
Use Case Scenarios for Back-to-Back Agent – Client Role

                     
The following table describes the use case scenarios for back-to-back agent – client role, including the applicable conditions and the corresponding behavior of the Setting SBI Message Priority feature.

                     

                        
Table L-6 Use Case Scenarios for Back-to-Back Agent – Client Role

                        

                           
                              

                                 Use Case Description
                                 Use Case Type
                                 Incoming Header Request
                                 SMP Feature Configuration
                                 Request behavior and Observability
                              

                           
                           
                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule- Configured

                                    
rule corresponding to SBI Message Priority header value is configured with range and default match (that is, *)

                                 		
                                 
                                    
Header Present in Request and configured in requestsmpheaders configuration

                                 		
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true, "initiatedRequestPriorityRule": "NRF_As_Client_Forwarding_Request" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
NRF_As_Client_Forwarding_Request corresponding to

                                    
initiatedRequestPriorityRule rule is selected, range value match rule is selected, and the mapped value is sent for Sbi Message Priority Header in the request. 
"3gpp-Sbi-Message-Priority"="14"
Observability:
                    None

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule- Configured

                                    
rule corresponding to SBI Message Priority header value is configured with default match (that is, *)

                                 		
                                 
                                    
Header Present in Request and configured in requestsmpheaders configuration

                                 		
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true, "initiatedRequestPriorityRule": "NRF_As_Client_Forwarding_Request" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "*",
                    "used": "16" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
NRF_As_Client_Forwarding_Request corresponding to

                                    
initiatedRequestPriorityRule rule is selected,

                                    
* match rule is selected and mapped value is sent for Sbi Message Priority Header in the request.
"3gpp-Sbi-Message-Priority"="16"
Observability:
                    None

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule- Configured

                                    
rule corresponding to SBI Message Priority header value is configured with range match only

                                 		
                                 
                                    
Header Present in Request and configured in requestsmpheaders configuration

                                 		
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true, "initiatedRequestPriorityRule": "NRF_As_Client_Forwarding_Request" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12-15",
                    "used": "14" } }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
NRF_As_Client_Forwarding_Request corresponding to

                                    
initiatedRequestPriorityRule rule is selected,

                                    
range based value match rule is selected

                                    
and mapped value is sent for Sbi Message Priority Header in the request.
"3gpp-Sbi-Message-Priority"="14"
Observability:
                    None

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule- Configured

                                    
rule corresponding to SBI Message Priority header value - Not configured

                                 		
                                 
                                    
Header Present in Request and configured in requestsmpheaders configuration

                                 		
                                  "3gpp-Sbi-Message-Priority"="10"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true, "initiatedRequestPriorityRule": "NRF_As_Client_Forwarding_Request" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "11-15",
                    "used": "14" } }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
NRF_As_Client_Forwarding_Request corresponding to

                                    
initiatedRequestPriorityRule rule is selected,

                                    
But no rules for matching value as incoming request.

                                    
No header will be sent out in the request.

                                    
Observability:
                        Metric pegged with Reason

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule- Not Configured

                                    
rule corresponding to SBI Message Priority header value - Not configured

                                 		
                                 
                                    
Header Present in Request and configured in requestsmpheaders configuration

                                 		
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "11-15",
                    "used": "14"} }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
NRF_As_Client_Forwarding_Request

                                    
corresponding to initiatedRequestPriorityRule not configured.

                                    
No header will be sent out in request.

                                    
Observability:
                        Metric pegged with Reason

                                 		
                              

                              

                                 
                                    
SBI message priority feature - Disabled

                                    
SBI Message Priority header in incoming Service operation - VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule- Configured

                                    
rule corresponding to SBI Message Priority header value is configured with exact value match, range and default match (that is, *)

                                 		
                                 
                                    
Header Present in request and configured in requestsmpheaders configuration

                                 		
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true "initiatedRequestPriorityRule": "NRF_As_Client_Forwarding_Request" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
The feature is disabled. The header will not go in the generated request even if it is present in the request.

                                    
Observability:
                      None

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - INVALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule - Configured

                                    
rules - Configured

                                 		
                                 
                                    
Header  is present in request and configured in requestsmpheaders configuration

                                 		
                                  "3gpp-Sbi-Message-Priority"="36"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true, "initiatedRequestPriorityRule": "NRF_As_Client_Forwarding_Request" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "15-20",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
NRF_As_Client_Forwarding_Request corresponding to initiatedRequestPriorityRule rule is selected, the Header Name comes from defaultSmpHeaderName and value comes from defaultPriority and then rule is applied for default value.

                                    
"3gpp-Sbi-Message-Priority"="14"
Observability:
                    None

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - INVALID

                                    
Corresponding sbiServiceOperation - Not Configured

                                    
initiatedRequestPriorityRule -

                                    
Not present

                                    
rules configured - Doesn't matter as client

                                 		
                                 
                                    
Header  is present in request and configured in requestsmpheaders configuration

                                 		
                                  "3gpp-Sbi-Message-Priority"="36"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_AccessToken_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Service operation is not configured. The default header name CANNOT be determined. The header will not go.

                                    
Observability:
                      Metric pegged with Reason

                                 		
                              

                              

                                 
                                    
SBI message priority feature - DISABLED

                                    
SBI Message Priority header in incoming Service operation - INVALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule - Configured

                                    
rules configured - Doesn't matter as client

                                 		
                                 
                                    
Header  is present in request and configured in requestsmpheaders configuration

                                 		
                                  "3gpp-Sbi-Message-Priority"="36"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true, "initiatedRequestPriorityRule": "NRF_As_Client_Forwarding_Request" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 The feature is disabled. The header will not go in the request generated by NRF.
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - Not Present/Valid header CANNOT be used

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule -

                                    
Configured

                                    
rules configured - Configured

                                 		
                                 
                                    
Header is present in request and not configured in requestsmpheaders configuration.

                                    
Header is not present in request but configured in requestsmpheaders configuration 

                                    
Header is not present in request and not configured in requestsmpheaders configuration 

                                 		
                                 NA
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true, "initiatedRequestPriorityRule": "NRF_As_Client_Forwarding_Request" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "15-20",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
NRF_As_Client_Forwarding_Request corresponding to initiatedRequestPriorityRule rule is selected, Header Name comes from defaultSmpHeaderName and value comes from defaultPriority

                                    
Rules configured as range-based and *, but range matched and corresponding value will go in header.

                                    
 
"3gpp-Sbi-Message-Priority"="14"		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - Not Present/Valid header CANNOT be used

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule -

                                    
Not Present

                                    
rules configured - Doesn't matter as client

                                 		
                                 
                                    
Header is present in request and not configured in requestsmpheaders configuration 

                                    
Header is not present in request but configured in requestsmpheaders configuration 

                                    
Header is not present in request and not configured in requestsmpheaders configuration 

                                 		
                                 NA
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
NRF_As_Client_Forwarding_Request corresponding to initiatedRequestPriorityRule rule is not configured, header will not go in the request.

                                    
Observability:
                      Metric pegged with Reason

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming Service operation - Not Present/Valid header CANNOT be used

                                    
Corresponding sbiServiceOperation - Not Configured

                                    
initiatedRequestPriorityRule -

                                    
Not Present

                                    
rules configured - Doesn't matter as client

                                 		
                                 
                                    
Header is present in request and not configured in requestsmpheaders configuration 

                                    
Header is not present in request but configured in requestsmpheaders configuration 

                                    
Header is not present in request and not configured in requestsmpheaders configuration 

                                 		
                                 NA
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
SBI Service operation not configured. The header will not go in the request.

                                    
Observability:
                      Metric pegged with Reason

                                 		
                              

                              

                                 
                                    
SBI message priority feature - Disabled

                                    
SBI Message Priority header in incoming Service operation - Configured

                                    
Corresponding sbiServiceOperation - Configured

                                    
initiatedRequestPriorityRule -Present

                                    
rules configured

                                 		
                                 
                                    
Header is present in request and not configured in requestsmpheaders configuration 

                                    
Header is not present in request but configured in requestsmpheaders configuration 

                                    
Header is not present in request and not configured in requestsmpheaders configuration 

                                 		
                                 NA
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_AccessToken_Forward_Request", "defaultPriority": 18, "preferReceivedPriority": true, "initiatedRequestPriorityRule": "NRF_As_Client_Forwarding_Request"}]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Client_Forwarding_Request", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 Feature is disabled. The header will not go in the request.
                              

                           
                        

                     

                  

               

            

            
L.4 Back-to-Back Agent Server Role
               

               

                  
In this role, NRF receives response from peer NF and sends back response to Consumer NF.

                  
In this role, NRF processes responses received from target network functions and determines the 3gpp-Sbi-Message-Priority header value based on the configured service operation behavior and priority mapping rules.
                  

                  

                     
Service Operations and Corresponding Configuration for Back-to-Back Agent  Server Role

                     
The following table lists the service operations and corresponding sbiServiceOperation configurations used for back-to-back agent server role. This is used to determine the applicable configuration for evaluating and updating the priority value in responses before sending them to the originating network function.
                     

                     

                        
Table L-7 Service Operations and Corresponding sbiServiceOperation Configuration

                        

                           
                              

                                 Service Operation
                                 API
                                 HTTP Method
                                 sbiServiceOperation
                              

                           
                           
                              

                                 NF Profile Retrieval Forwarding Response
                                 /nnrf-nfm/v1/nf-instances/<nfInstanceID>
                                 GET
                                 Nnrf_NFManagement_NFProfileRetrieval_Forward_Response
                              

                              

                                 NF Status Subscribe Creation Forwarding Response
                                 /nnrf-nfm/v1/subscriptions
                                 POST
                                 Nnrf_NFManagement_NFStatusSubscribe_Forward_Response
                              

                              

                                 NF Status Subscribe Creation Roaming Response
                                 /nnrf-nfm/v1/subscriptions
                                 POST
                                 Nnrf_NFManagement_NFStatusSubscribe_Roaming_Response
                              

                              

                                 NF Status Subscribe Update Forwarding Response
                                 /nnrf-nfm/v1/subscriptions
                                 PATCH
                                 Nnrf_NFManagement_NFStatusSubscribeUpdate_Forward_Response
                              

                              

                                 NF Status Subscribe Update Roaming Response
                                 /nnrf-nfm/v1/subscriptions
                                 PATCH
                                 Nnrf_NFManagement_NFStatusSubscribeUpdate_Roaming_Response
                              

                              

                                 NF Status UnSubscribe Creation Forwarding Response
                                 /nnrf-nfm/v1/subscriptions
                                 DELETE
                                 Nnrf_NFManagement_NFStatusUnSubscribe_Forward_Response
                              

                              

                                 NF Status UnSubscribe Creation Roaming Response
                                 /nnrf-nfm/v1/subscriptions
                                 DELETE
                                 Nnrf_NFManagement_NFStatusUnSubscribe_Roaming_Response
                              

                              

                                 NF Discover Forwarding Response
                                 /nnrf-disc/v1/nf-instances?
                                 GET
                                 Nnrf_NFDiscovery_Forward_Response
                              

                              

                                 NF Discover Roaming Response
                                 /nnrf-disc/v1/nf-instances?
                                 GET
                                 Nnrf_NFDiscovery_Roaming_Response
                              

                              

                                 NF Access Token Forwarding Response
                                 /oauth2/token
                                 POST
                                 Nnrf_AccessToken_Forward_Response
                              

                              

                                 NF Access Token Roaming Response
                                 /oauth2/token
                                 POST
                                 Nnrf_AccessToken_Roaming_Response
                              

                           
                        

                     

                  

                  

                     
Use Case Scenarios for Back-to-Back Agent – Server Role

                     
The following table describes the use case scenarios for Back-to-Back Agent – Server Role, including the applicable conditions and the corresponding behavior of the Setting SBI Message Priority feature.

                     

                        
Table L-8 Use Case Scenarios for Back-to-Back Agent – Server Role

                        

                           
                              

                                 Use Case Description
                                 Use Case Type
                                 Incoming Header Request
                                 Response and Observability
                                 Response and Observability
                              

                           
                           
                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response - VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with range and default match (that is, *)

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
NRF_As_Server_Forwarding_Response

                                    
corresponding to the responsePriorityRule rule is selected,

                                    
The range-based value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.
"3gpp-Sbi-Message-Priority"="14"
Observability:
                    None

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response - VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with default match (that is, *) only

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "*",
                    "used": "16" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
NRF_As_Server_Forwarding_Response
corresponding to responsePriorityRule rule is selected,

                                    
default value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.
"3gpp-Sbi-Message-Priority"="16"
Observability:
                    None

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response - VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured range value match only.

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
NRF_As_Server_Forwarding_Response corresponding to responsePriorityRule rule is selected, range based value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.
"3gpp-Sbi-Message-Priority"="17"
Observability:
                    None

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response - VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
Matching rule for incoming header value - Not Configured

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
NRF_As_Server_Forwarding_Response
corresponding to responsePriorityRule rule is selected,

                                    
No Rule Found for Value 12. No SMP header will go in the response.

                                    
Observability:
                      Metric will be pegged with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response- VALID

                                    
Corresponding sbiServiceOperation -  Not Configured

                                    
responsePriorityRule - NA

                                    
Matching rule for incoming header value - NA

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Request", "defaultPriority": 18, "preferReceivedPriority": true }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
 

                                    
sbiServiceOperation is not present in the configuration for the incoming response. No SMP header will go in the response.

                                    
Observability:
                        Metric will be pegged with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - DISABLED

                                    
SBI Message Priority header in incoming response- VALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with exact value match, range and default match (that is, *)

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="12"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Feature is disabled. No header will go in the response even they are present in request.

                                    
Observability:
                      None.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response- INVALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with range and default match (that is, *)

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="35"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "15-20",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected, range based value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.
"3gpp-Sbi-Message-Priority"="14"
Observability:
                    None.

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response - INVALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with default match (that is, *) only

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="35"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "*",
                    "used": "16" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected, default value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.
"3gpp-Sbi-Message-Priority"="16"
Observability:
                    None.

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response - INVALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with range match only

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="35"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "16-20",
                    "used": "18" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected, range based value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.

                                    
"3gpp-Sbi-Message-Priority"="18"

                                    
Observability: None.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response - INVALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
Matching rule for default configured value - No

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="-1"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Rule is not configured for defaultPriority

                                    
No SMP header will go in the response.

                                    
Observability:
                        Metric will be pegged with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response- INVALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule -  Not Configured

                                    
Matching rule for incoming header value - NA

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="40"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
responsePriorityRule is not configured. 

                                    
No SMP header will go in the response.

                                    
Observability:
                        Metric will be pegged with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response - INVALID

                                    
Corresponding sbiServiceOperation - Not Configured

                                    
responsePriorityRule - NA

                                    
Matching rule for incoming header value - NA

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="-1"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Request", "defaultPriority": 18, "preferReceivedPriority": true }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
SBI Service operation is not configured for the incoming response. 

                                    
No SMP header will go in the response.

                                    
Observability:
                        Metric will be pegged with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - DISABLED

                                    
SBI Message Priority header in incoming response- INVALID

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with exact value match, range and default match (that is, *)

                                 		
                                 The header is present in the response which was sent in the request.
                                  "3gpp-Sbi-Message-Priority"="-2"
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Feature is disabled. No header will go in the response even they are present in request.

                                    
Observability:
                      None.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response -Not present/Cannot be used

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with range and default match (that is, *)

                                 		
                                 The header is not present in the response which was sent in the request.
                                 _
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "15-20",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected, range based value match rule is selected, and mapped value is sent for Sbi Message Priority Header in the response.

                                    
"3gpp-Sbi-Message-Priority"="14"

                                    
Observability: None.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response -Not present/Cannot be used

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with default match (that is, *) only

                                 		
                                 The header is not present in the response which was sent in the request.
                                 -
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "*",
                    "used": "16" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected, default value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.
"3gpp-Sbi-Message-Priority"="16"
Observability:
                    None.

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response-Not present/Cannot be used

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with range match only

                                 		
                                 The header is not present in the response which was sent in the request.
                                 -
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "16-20",
                    "used": "18" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Default Priority from SBIservice operation is used and header from NRF_As_Server_Rule corresponding to responsePriorityRule rule is selected, range based value match rule is selected and mapped value is sent for Sbi Message Priority Header in the response.
"3gpp-Sbi-Message-Priority"="18"
Observability:
                    None.

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response -Not present/Cannot be used

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
Matching rule for default configured value - NA

                                 		
                                 The header is not present in the response which was sent in the request.
                                 -
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Rule is not configured for defaultPriority. No SMP header will go in the response.

                                    
Observability:
                        Metric will be pegged with
                  reason.

                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response -Not present/Cannot be used

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Not Configured

                                    
Matching rule for incoming header value - NA

                                 		
                                 The header is not present in the response which was sent in the request.
                                 _
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true}]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
responsePriorityRule is not configured. 

                                    
No SMP header will go in the response.

                                    
Observability:
                        Metric will be pegged with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - ENABLED

                                    
SBI Message Priority header in incoming response-Not present/Cannot be used

                                    
Corresponding sbiServiceOperation - Not Configured

                                    
responsePriorityRule - NA

                                    
Matching rule for incoming header value - NA

                                 		
                                 The header is not present in the response which was sent in the request.
                                 _
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Request", "defaultPriority": 18, "preferReceivedPriority": true }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Rule", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "13-16",
                    "used": "17" }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
SBI Service operation is not configured for the incoming response. 

                                    
No SMP header will go in the response.

                                    
Observability:
                        Metric will be pegged with reason.

                                 		
                              

                              

                                 
                                    
SBI message priority feature - DISABLED

                                    
SBI Message Priority header in incoming response -Not present/Cannot be used

                                    
Corresponding sbiServiceOperation - Configured

                                    
responsePriorityRule - Configured

                                    
rule corresponding to SBI Message Priority header value is configured with exact value match, range and default match (that is, *)

                                 		
                                 The header is not present in the response which was sent in the request.
                                 _
                                 
                                    
/nf-common-component/v1/global-configuration/sbiserviceoperations
"[{ "sbiServiceOperation": "Nnrf_NFDiscovery_Forward_Response", "defaultPriority": 18, "preferReceivedPriority": true, "responsePriorityRule": "NRF_As_Server_Forwarding_Response" }]"
and

                                    
/nf-common-component/v1/global-configuration/prioritymappingrules
"[{ "name": "NRF_As_Server_Forwarding_Response", "defaultSmpHeaderName": "3gpp-Sbi-Message-Priority", "rules":
                      [{ "received": "12", "used": "10"
                      }, "received": "12-15",
                    "used": "14" }, "received":
                    "*", "used": "16"
                    }] }]"
and

                                    
/nf-common-component/v1/global-configuration/requestsmpheaders
"["3gpp-Sbi-Message-Priority"]"		
                                 
                                    
Feature is disabled. No header will go in the response even they are present in request.

                                    
Observability:
                      None.