B.2 nrfSupportedFeatures
As per 3GPP TS 29.510, nrfSupportedFeatures attribute
indicates the features supported by NRF for the NFDiscovery service. This attribute
is included in the discovery response if at least one feature is supported by NRF.
From release 23.4.0, the value of this attribute is 172 (in hexadecimal and
101110010 in binary), by reading the bits from left to right it indicates that it
supports the 2, 5, 6, 7, and 9 Feature Number as per the following table:
Table B-1 Features of nrfSupportedFeatures attribute used by Nnrf_NFDiscovery service
| Feature Number | Feature | Mandatory/Optional | Description |
|---|---|---|---|
| 1 | Complex-Query | O |
Support of Complex Query expression (see clause 6.2.3.2.3.1) |
| 2 | Query-Params-Ext1 | O |
Support of the following query parameters: - limit - max-payload-size - required-features - pdu-session-types |
| 3 | Query-Param-Analytics | O |
Support of the query parameters for Analytics identifier: - event-id-list - nwdaf-event-list |
| 4 | MAPDU | O | This feature indicates whether the NRF supports selection of UPF with Access Traffic Steering, Switching and Splitting (ATSSS) capability. |
| 5 | Query-Params-Ext2 | O |
Support of the following query parameters: - requester-nf-instance-id - upf-ue-ip-addr-ind - pfd-data - target-snpn - af-ee-data - w-agf-info - tngf-info - twif-info - target-nf-set-id - target-nf-service-set-id - preferred-tai - nef-id - preferred-nf-instances - notification-type - serving-scope - internal-group-identity - preferred-api-versions - v2x-support-ind - redundant-gtpu - redundant-transport - lmf-id - an-node-type - rat-type - ipups - scp-domain-list - address-domain - ipv4-addr - ipv6-prefix - served-nf-set-id - remote-plmn-id - data-forwarding - preferred-full-plmn - requester-snpn-list - max-payload-size-ext |
| 6 | Service-Map | M | This feature indicates whether it is supported to identify the list of NF Service Instances as a map (that is, the "nfServiceList" attribute of NFProfile is supported). |
| 7 | Query-Params-Ext3 | O |
Support of the following query parameters: - ims-private-identity - ims-public-identity - msisdn - requester-plmn-specific-snssai-list - n1-msg-class - n2-info-class |
| 8 | Query-Params-Ext4 | O |
Support of the following query parameters: - realm-id - storage-id |
| 9 | Query-Param-vSmf-Capability | O |
Support of the query parameters for V-SMF capability: -vsmf-support-ind |
The value of nrfSupportedFeatures attribute in the
discovery response varies based on the value of the
requester-features attribute sent by the Consumer NF. The
requester-features attribute indicates the features that are
supported by the Consumer NF.
The value of the nrfSupportedFeatures attribute is calculated based
on the following scenarios:
- value of
nrfSupportedFeaturesattribute when there are common supported features between consumer NF and NRFIf the
requester-featuresattribute has the value of 12 (this is hexadecimal value) in the discovery search query, the corresponding binary value is 00010010. It indicates that the 2nd and 5th bit are enabled and Consumer NF supports the Feature Number 2 and 5. As per the current support at NRF, the common supported features between Consumer NF and NRF are 2 and 5. Hence, the value ofnrfSupportedFeaturesattribute in the discovery response is 12. - value of
nrfSupportedFeaturesattribute when there are partial common supported features between consumer NF and NRFIf the
requester-featuresattribute has the value of 6 (this is hexadecimal value) in the discovery search query, the corresponding binary value is 0110. It indicates that the 2nd and 3rd bit are enabled and Consumer NF supports Feature Number 2 and 3. As per the current support at NRF, the common supported feature between Consumer NF and NRF is 2. Hence, the value of thenrfSupportedFeaturesattribute in the discovery response is 2. - value of
nrfSupportedFeaturesattribute when there is no common supported features between consumer NF and NRFIf the
requester-featuresattribute has the value of 8 (this is hexadecimal value) in the discovery search query, the corresponding binary value is 1000. It indicates that no common features are available between the Consumer NF and NRF. Hence, the value of thenrfSupportedFeaturesattribute in the discovery response is 0. - value of
nrfSupportedFeaturesattribute is 172When the
requester-featuresattribute is unavailable in the discovery search query of Consumer NF, the value of thenrfSupportedFeaturesattribute in the discovery response is 172.