The Udm to Udr NF tab is part of the SBI Protocol Stack for 5G and is available on the Service Based Nodal test case when Test UDR (Nudr), From UDM (N35) is enabled.
Per 3GPP TS 23.501, 23.502 and 29.5xx. About the 5G Application.
NF Consumer (Service Based Nodal - UDM-UDR )
|
|
Operator Specific Data |
|
|
|
Nudr Version (29.505) |
Select the Nudr Version. Available when Test UDR (Nudr), From UDM (N35) is selected on Service Based Nodal test case on Interface UDM-UDR. Options: 15.4.0/Jun2019, 15.5.0/Sep2019 Tcl Parameter: N35NudrSbiVersion |
||||||||||||
Select “Use Access Token” option to support OAuth2 authorization for NF Consumer. Support for Nnrf_AccessToken Service to the Service Base Nodal /Node NRF per spec TS 29.510 V16.3.0 section 5.4.2.2.1. Select to enter Access Token. Enter up to 1023 characters Tcl Parameter: N35NudrUseAccTokEn Tcl Parameter: N35NudrAccTokEn Tcl Parameter: N35NudrAccTok |
|||||||||||||
Select to include the Custom Http headers for Origination Timestamp and Max Response Time.
Nudr_DR_sm-data Request (get sm-data) and Nudr_DR_SmfRegistrations (smf registration) Request generated via the N35 (UDM-UDR) interface on Service Based Nodal test case will include these fields in the header. Enter Max response Time in milliseconds. Range : 1 to 60000 Default : 1 Tcl Parameter: N35Nudr3gppSbiOrigTimestampEn Tcl Parameter: N35Nudr3gppSbiOrigTimestamp |
|||||||||||||
DNN with Starting SUPI Mode via TDF |
Select "DNN with Starting SUPI Mode via TDF" to allocate the SUPI from the DNN entry in the TDF file. Each Row (Multiplier Label) is a different DNN. SBI Node can support up to 1500 unique DNNs. The SUPI values will be allocated based on the STARTING_SUPI and its range of each DNN entry from this TDF file. The available columns of TDF file is:
STARTING_SUPI shall be numeric, at most 15 digts. SUPI_RANGE shall be numeric, in range 1..2147483647. SUB_INDEX shall be numeric, in range 1..6. NSSAI has format as ([0-9][0-9]*)(-)([0-9a-f][0-9a-f])* or ([0-9][0-9])*, the first part is SST which value is from 0 to 255, the second part is SD which value is from 1 to 6 Hex characters, the two parts are combined with '-', and the first part shall be mandatory, the second part can be optional. DNN_NAME contains up to 63 characters, at least one character.
SUB_CFG_1_NSSAI and SUB_CFG_2_NSSAI have the same format as NSSAI. SUB_CFG_1_DNN and SUB_CFG_2_DNN have the same format as DNN_NAME.
Tcl Parameter: N35NudrSubSmDnnSupiCfgFileEn Tcl Parameter: N35NudrSubSmDnnSupiCfgFile |
||||||||||||
Subscription Data |
Enter the Subscription Data Count. Available when Test UDR (Nudr), From UDM (N35) is selected on Service Based Nodal test case on Interface UDM-UDR. The Subscription Data Count decides how many subscriptions that the UDM can subscribe to UDR. The message flow exposes the subscription index. If a subscription isn't unsubscribed and you create a new one on the subscription index, the old subscription ID on this index will be overwritten by the new subscription ID. See createUeSDMSubscriptionReq in SBI Message Flow . Range : 1 to 6 Default : 1 Tcl Parameter: N35NudrSubsDataSubCount
Subscription Data Settings Table Information:
|
||||||||||||
Enable Operator Specific Data |
Select Enable Operator Specific Data to add up to 3 Operator Specific Data sets. You have the option to create an operator specific data set for String, Boolean, Integer and Number elements. Available when Test UDR (Nudr), From UDM (N35) is selected on Service Based Nodal test case on Interface UDM-UDR. The # of Operator Specific Data Count decides how many Operator Specific Data Sets are configured (up to 3). Range : 1 to 3 Default : 1 Tcl Parameter: N35NudrOpSpecDataEn Tcl Parameter: N35NudrOpSpecDataIdx Operator Specific Data Settings Table Information:
|