Supported X-Header Information

Out of all the configurable X-header information, some information requires SMF to send the corresponding values to the UPF. The following table lists the information that is sent from the SMF to the UPF for X-header insertion.

X-header Information
Xheader FieldDescriptionPresent in Session Establishment Modified in Session Modification
String ConstantInserts the configured string in xheader
Charging IDPer Flow or Bearer Charging IdYes
IMEIIMEI for the callYes
IMSIIMSI for the callYes
Rat-TypeRAT type for the UE sessionYesYes
s-mcc-mncMCC or MNC of the SGW or AMFYes
Sgsn-addressAMF or SGW addressYesYes
ULIUser Location InfoYesYes
GGSN-AddressN4 or or S5 endpoint of SMFYesYes
Radius-station-IDMSISDN of the UE
Sn-rulebaseRulebase for a callYesYes
Subscriber-ip-addressIP address allocated to UE
Msisdn-no-ccObtained from MSISDNYesNo

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

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.