Supported X-Header Information

Out of all the configurable X-header information, some information requires control plane (SMF) to send the corresponding values to the user plane (UPF). The following table lists the information that is sent from the SMF to the UPF for X-header Insertion support.

Xheader FieldDescriptionPresent in Session Establishment Modified in Session Modification
String ConstantInserts the configured string in xheaderN/AN/A
Charging IDPer Flow/Bearer Charging IdYesN/A
IMEIIMEI for the callYesN/A
IMSIIMSI for the callYesN/A
Rat-TypeRAT type for the UE sessionYesYes
s-mcc-mncMCC/MNC of the SGW/AMFYesN/A
Sgsn-addressAMF/SGW addressYesYes
ULIUser Location InfoYesYes
GGSN-AddressN4/S5 endpoint of SMFYesYes
Radius-station-IDMSISDN of the UEN/AN/A
Sn-rulebaseRulebase for a callYesYes
Subscriber-ip-addressIP address allocated to UEN/AN/A
Msisdn-no-ccObtained from MSISDNYesNo

The subscriber-specific fields—IMSI, MSIDN, and IMEI—are encoded in the "User ID" standard IE. See, 3GPP 29.244, Section 8.2.101 for more information.

Rest of the fields are sent in the "Subscriber Parameters" proprietary AVP. Some fields, such as the "Rulebase" and "UE IP address", are sent as a part of the created PDRs.

Note
  • All the parameters are always sent from the SMF to the UPF irrespective of whether X-header configuration is available. These parameters ensure that any change in configuration after session creation is immediately applied on the UPF.

  • The SMF supports X-header Insertion-related configurations. The SMF does not require these configurations for its functionality. These configurations are sent to the UPF through the RCM.