MME Node - Provisioning TDF

The MME Node test case allows you use customized Test Data File per UE and per Bearer. You may provision the three Test Data Files in the MME Node Test Case: NAS Protocol TDF, Bearer Context TDF, and S1-AP TDF. These three TDFs are linked together and share a common IMSI Index column located in the NAS Protocol TDF. Hence, the NAS Protocol TDF is required to define the IMSIs Index column for the other TDFs even if you do not define the NAS Protocol options per UE.

The sections below provides an example of the TDFs, their contents and how their data may be linked.

Test Data File	Location on the UI
NAS Protocol TDF	MME Node \| S1-MME \| NAS tab
Bearer Context TDF	MME Node \| S1-MME \| NAS tab
S1-AP TDF	MME Node \| S1-MME \| S1-AP tab

Learn more about:

NAS Protocol TDF

The NAS protocol TDF contains the IMSI index used for all three TDFs . This index is only specified in the NAS Protocol TDF and it applies to all 3 TDFs (NAS Protocol TDF, Bearer Context TDF, and S1-AP TDF). The four valid columns in the NAS Protocol TDF are as follows:

IMSI	The IMSI index for a given UE. If an incoming UE matches this index then the corresponding rows for all 3 TDFs will be used by that IMSI as described in this document.
Perform Security	0 if the UE is to not perform security, 1 of it is.
Integrity Algorithm	0 = Reserved, 1 = EIA1 Snow3G, 2 = EIA2-AES
Ciphering Algorithm	0 = Null, 1 = EEA1-Snow3G, 2 = EEA2-AES

Example NAS Protocol TDF

IMSI	Perform Security	Integrity Algorithm	Ciphering Algorithm
123400000000001	0	0	0
123400000000002	1	1	1
123400000000009	1	2	2

NOTES:

If the MME Test Case is configured for 100 UEs and the TDF contains 3 Rows (3 Unique IMSIs), then the 3 UEs that match the IMSIs will use the values from the TDFs while the other 97 will use the default settings from the UI.
The TDF operate in an override fashion. At the initialization of the test case, all the values are first configured in the Database based upon the default values from the UI. The TDFs are then read in and OVERWRITE the default values BUT ONLY for the fields that actually exist in the TDFs. Therefore, If a parameter is not defined in the TDF, the default values from the UI are used.

^ Back to Top

Bearer Context TDF

The Bearer Context TDF is used to specify unique per bearer/per IMSI configuration information. It does not have an index column, it uses the IMSI Index column from the NAS Protocol TDF.

Each Row represents a Bearer set consisting of a Default Bearer and 1 or more Dedicated Bearers. For example, if you require a UE to create 3 Default Bearers, then in Bearer Context TDF, specify 3 rows (one for each Default Bearer set) corresponding to the given IMSI in the NAS Protocol TDF.

IMPORTANT: The order of the rows is important as they and map to the order of IMSI in the NAS protocol file as follows.

Number of IMSI = Number of IMSI rows in the NAS Protocol TDF

Defining Bearer Context TDF

Define the rows to represent the Default Bearers to map the IMSIs in the NAS Protocol TDF.

For configuring one Default Bearer and any number of Dedicated Bearers

Define values in rows for Default Bearer 0 (db0):

The first row in the Bearer Context TDF is Default Bearer 0 (db0) associated with the first IMSI row in the NAS protocol TDF.
The second row in the Bearer Context File is Default Bearer 0 associated with the second row IMSI in the NAS protocol TDF.
The third row in the Bearer Context File is Default Bearer 0 associated with the third row IMSI in the NAS protocol TDF.

NOTES:

Repeat the above sequence until the number of db0 rows in the Bearer Context TDF matches the number of IMSI rows in the NAS protocol TDF.
You may also define lesser number of rows in the Bearer Context TDF than the number of IMSI rows in the NAS Protocol TDF.

In this case, the IMSIs without Bearer Context entries in the Bearer Context TDF uses the default values form the UI for db0 and associated dedicated bearers.

For configuring 2 Default Bearers and any number of Dedicated Bearers

Define two sets of rows in the Bearer Context TDF as follows.

NOTE: If the second Default Bearer (db1) and Dedicated Bearers use the default values from the UI, then no additional rows are required to be added to the Bearer Context TDF.

For the Default/First Bearer (db0): Specify the first X rows, where X = Number of IMSI in the NAS protocol TDF

For the second Default Bearer (db1): Specify X rows, from X + 1 row, where X = Number of IMSI in the NAS protocol TDF

For example, if X = 3, the Bearer Context TDF values for 2 Default Bearers would be as follows:

Header Row
Row 1 = DB0 for IMSI 1
Row 2 = DB0 for IMSI 2
Row 3 = DB0 for IMSI 3
Row 4 = DB1 for IMSI 1
Row 5 = DB1 for IMSI 2
Row 6 = DB1 for IMSI 3

Bearer Context TDF Values

The following describes some of the values defined in the Bearer Context TDF.

UE Initiated Dedicated

Indicates dedicated Bearers for who are going to be UE initiated or Network Initiated.

0 = Network Initiated; 1 = UE Initiated

EPS QOS Set

Indicates the Bearer to which the previous Columns of QOS values apply:

0 = Default Bearer, 1 = First Dedicated Bearer, 2 = 2nd Dedicated Bearer, etc.

For each Bearer to be specified, the TDF includes the EPS QOS Set column following each set of QOS values (columns) (See illustration below). The set of values (each in their own column) map directly to the corresponding QOS fields from the GUI (See MME Node | SI-MME | NAS tab).

EPS QOS Class Identifier
EPS QOS Max Bit Rate for Uplink
EPS QOS Max Bit Rate for Downlink
EPS QOS Guaranteed Bit Rate Uplink
EPS QOS Guaranteed Bit Rate Downlink
EPS QOS Extended Max Bit Rate for Uplink
EPS QOS Extended Max Bit Rate for Downlink
EPS QOS Extended Guaranteed Bit Rate Uplink
EPS QOS Extended Guaranteed Bit Rate Downlink

NOTE: Selecting USE Bearer Parameters from the UE on the Emulator Configuration tab determines whether the User Initiated Dedicated Bearers use the QOS Settings provided by the Mobile or use the QoS settings defined in MME Node Default and Bearer Context TDF.

Example Bearer Context TDF

The Example Bearer Contest TDF File illustrates definition for 3 IMSIs Each with 2 Default bearers (6 rows total).

Column 1	The first column is the UE Initiated Dedicated Bearer row and indicates whether the dedicated bearers will be UE initiated or Network Initiated.
Columns 2-10	The next 9 columns (columns 2-10) map to the QOS settings for the bearers in the DB0 set. The 11th column indicates to which of the bearers in the db0 set the columns 2-10 are referring.
Column 11	The EPS QOS Set in column 11 is a 0, hence, columns 2-10 refer to the Default Bearer in the db0 set.
Columns 12-20	Defines the next set of QOS values and are mapped based upon the EPS QOS Set value in Column 21. In this case, EPS QOS Set value in Column 21 is a 1 which indicates it maps to the first dedicated bearer.

^ Back to Top

S1-AP TDF

Use the S1-AP TDF to define unique Uplink and Downlink Aggregate Bit Rates per UE. This file contains no index and maps directly to the IMSI index/Rows defined in the NAS Protocol file. Each row maps to 1 UE. When this file is not used, or a given IMSI in not defined in the file (as indexed by NAS protocol TDF), the default values on the S1-AP tab are used by the EPC emulator.

The S1-AP TDF includes only two possible columns:

UE AMBR DL – Aggregate Bit Rate for Downlink
UE AMBR UL – Aggregate Bit Rate for Uplink

Example S1-AP TDF

UE AMBR DL	UE AMBR UL
4000000	3000000
4500000	3500000
4750000	3750000

^ Back to Top