B.3 DataSetId Enhancements
As per 3GPP TS 29.510 v17.7, NRF supports the following enumeration (ENUM) values within DataSetId enumeration.
Table B-2 Additional DataSetId Enumerations
| ENUM Value | Description |
|---|---|
| "A_PFD" | ApplicationData subset: Packet Flow Descriptions |
| "A_AFTI" | ApplicationData subset: AF Traffic Influence Data |
| "A_IPTV" | ApplicationData subset: IPTV Config Data |
| "A_BDT" | ApplicationData subset: Background Data Transfer |
| "A_SPD" | ApplicationData subset: Service Parameter Data |
| "A_EASD" | ApplicationData subset: EAS Deployment Information |
| "A_AMI" | ApplicationData subset: AM Influence Data |
| "P_UE" | PolicyData subset: UE Specific Data |
| "P_SCD" | PolicyData subset: Sponsored Connectivity Data |
| "P_BDT" | PolicyData subset: Background Data Transfer |
| "P_PLMNUE" | PolicyData subset: PLMN-specific UE policy data |
| "P_NSSCD" | PolicyData subset: Network Slice Specific Control Data |
| "P_MBSCD" | PolicyData subset: MBS Session Policy Control Data |
NRF supports the additional ENUM values added in the
DataSetId attribute in the following service operations as per the
3GPP TS 29.510 v17 standards:
- NFRegister
- NFProfileRetrieval
- NFUpdate (Partial/Complete)
- NFStatusNotify
- NFDiscover
If UDR registers with
DataSetId attribute, only the following enums are
allowed:
- SUBSCRIPTION
- POLICY
- EXPOSURE
- APPLICATION
- A_PFD
- A_AFTI
- A_IPTV
- A_BDT
- A_SPD
- A_EASD
- A_AMI
- P_UE
- P_SCD
- P_BDT
- P_PLMNUE
- P_NSSCD
- P_MBSCD
However, in case of NFRegister service operation, the following validations are not supported:
- If UDR registers with
DataSetIdattribute with "APPLICATION", it is required to register with all A_*** enumerations in addition. - If UDR registers with all the above defined A_*** enumerations, it should register with "APPLICATION" enumeration in addition.
- If UDR registers with
DataSetIdattribute with "POLICY", it is required to register with all P_*** enumerations in addition. - If UDR registers with all the above defined P_*** enumerations, it should register with "POLICY" enumeration in addition.
For more information about the attribute, see NRF Compliance Matrix.
Note:
The DataSetId parameter is ignored in the following scenarios for the NF Profiles (if the discovery query contains the DataSetId parameter):- supportedDataSets attribute is missing: If the UdrInfo profile does not contain the supportedDataSets attribute, the data-set parameter in the discovery request should be ignored.
- UdrInfo JSON object is empty: If the UdrInfo JSON object is provided and it is empty, the data-set parameter should be ignored.
- UdrInfo JSON object is missing: If the entire UdrInfo JSON object is not included in the request, the data-set parameter should be ignored.