PCMD record IEs

The MAG-c supports PCMD record IEs including header IEs, session IEs, and PCMD heartbeat message IEs.

Header record IEs

The MAG-c supports Common Header, Report Header2, and Sending Node IP container IEs.

Common Header IEs

Table 1. Common Header IEs
Information element Description
PCMDVersion

Version of the PCMD feature 1
RecordType

Type of record:

  • 3 – session2
  • 4 – heartbeat
RecordLength

Total record length in bytes
1 The current value of PCMDVersion is 6. The version changes whenever there is a modification in the Header structure or some non-compatible change in the structure of the containers.

Report Header2 IEs

Table 2. Report Header2 IEs
Information element Description
RecordOpeningTime

Time the record generation started

  • First 4 bytes – time since 1970-01-01 00:00:00 UTC, in seconds

  • Second 4 bytes – precision of the procedure start time, in nanoseconds
RecordSequenceNumber

Unique sequence identifier for the record type per card and per record type

Each card generates the RecordSequenceNumber for each record type it transmits.

Resets to 1 if:

  • maximum reached
  • MSCP-group or MG-Group failover
  • switchover to a new active card or VM
GwId

Mobile gateway ID

Range: 1 to 8
MscpGroupId

MSCP group ID

Range: 1 to 15
SendingNodeType

Type of node that sends the PCMD record:

  • 9 – combined SGW-C + PGW-C
  • 14 – SMF
UEid

User equipment ID:

  • IMSI – for combined SGW-C + PGW-C session, encoded in TBCD form
  • SUPI – for 5G PDU session reporting SUPI for 5G PDU session reporting
  • 0 – no IMSI or SUPI available, for example, an emergency attach with just the IMEI
SendingNodeIpV6

Sending node IP address type:

  • 1 – SendingNodeIP contains an IPv6 address
  • 0 – SendingNodeIP contains an IPv4 address, stored in the first 4 bytes

Sending Node IP container IEs

Table 3. Sending Node IP IEs
Information element Description
SendingNodeIP

IP address of the sending node, corresponding to the system interface of the base router

IP address version used on the network layer, if both IPv4 and IPv6 are configured

Session record information elements

The MAG-c supports session PCMD record IEs.

Session Decoding container IEs

Table 4. Session Decoding container IEs
Information element Description
MessageNum

Number of message containers

Range: 0 to 40
ProcNum

Number of procedure containers

Range: 1 to 3
PeerNum

Number of peers containers

Range: 0 to 15
Table 5. SessionFlags2 IEs
Information element Description
SnssaiFlag Presence of the SNSSAI container
UliTypeFlag

Type of ULI in the Session Extended container

See the ULI IE description in Session extended container IEs
Table 6. SessionFlagsV2 IEs
Information element Description
BrNum

Number of Bearer containers, or the number of QoS Flow containers for 5G sessions

Range: 0 to 11
ApnFlag

Presence of the APN or DNN container
ExtendedFlag

Extended report type flag

The report type is extended when set to 1
ImeiFlag

Presence of the IMEI or PEI for 5G Session container
MsisdnFlag

Presence of the MSISDN or GPSI for 5G Session container

Session3 container IEs

Table 7. Session3 container IEs
Information element Description
RatType

Radio access technology:

  • 0 – reserved
  • 6 – EUTRAN (WB-E-UTRAN)
  • 14 – NR
DT

Direct tunnel indication:

  • 0 – undefined (when UE is idle)
  • 1 – S1-U
BLC

Bearer level charging or sessions flag:

  • 0 – Session level charging is used
  • 1 – Bearer level charging is used

GCID is reported for every bearer

5G sessions only support PDU session-level charging.
CI

Charging indication for the session:

  • 0 – no charging
  • 1 – charging enabled

Accounts for online and offline charging as configured or imposed by PCF
PDNType

PDN type:

  • 0 – UE IP container is not present, for example in UE level procedures (see UE-level procedures)
  • 1 – IPv4
  • 2 – IPv6
  • 3 – Dual stack
IwkI

Interworking indication for 4G-attached sessions (from the MME) or 5G-attached sessions (from the AMF):

  • 0 – reserved
  • 1 – no interworking
  • 2 – N26 interworking
  • 3 – no N26 interworking
UPSelection

Container for UPSelectionAttributes and UPSelectionPeer; see the table User Plane Selection IEs
SSC-Mode

Session and service continuity mode:

  • 0 – undefined
  • 1 – SSC Mode 1
  • 2 – SSC Mode 2
  • 3 – SSC Mode 3
PduSessionId

PDU session ID for the UE

Range: 0 to 15
Table 8. User Plane Selection IEs
Information element Description
UPSelectionAttributes

0 – UPSelection not relevant

0 in the current version
UPSelectionPeer

Present when UPSelectionAttributes is not 0

Procedure container IEs

Table 9. Procedure container IEs
Information element Description
ProcedureID

ID of the procedure

See ProcedureIDs for possible values and meanings.
ProcedureResult

Indicates the outcome of the procedure:

  • 1 – success
  • 2 – failure
ProcedureCause

ProcedureCause associated with the ProcedureResult

See Causes for possible values and meanings.

0 when no value is reported

Cause code matches GTPv2, HTTP2, or PFCP external message causes
ProcedureDetailedCause

ProcedureDetailedCause associated with the current procedure.

See Detailed causes for possible values and meanings.

Set to 0 when no value is reported

Cause code matches internal status events
ProcedureDuration

Elapsed time since start of the procedure, in hundredths of seconds

IMEI container IEs

Table 10. IMEI container IEs
Information element Description
IMEI

IMEI or PEI (14 decimal digits plus a check digit) or IMEI/SV (16 digits) for the UE

IMEI/SV structure specified in 3GPP TS 23.003

Includes device origin, model, and serial number

Non-zero if available

Encoded in telephony binary-coded decimal (TBCD)

MSISDN container IEs

Table 11. MSISDN container IEs
Information element Description
MSISDN

MSISDN or GPSI identifying the subscription

Non-zero if available

Encoded in TBCD

Peers container IEs

Table 12. PeerNTypeV2 container IEs
Information element Description
PeerNId

ID of the nth peer

IPv4, IPv6, or UUID depending on peerIdType value
PeerIdType

Type of ID used in PeerNId:

  • 10 – IPv6
  • 00 – IPv4
  • 01 – UUID
PeerType

Indicates the type of the involved Peer:

  • 2 – MME
  • 16 – combined SGW-U + PGW-U
  • 20 – UPF
  • 21 – Nsmf_PDUSession consumer
  • 23 – Namf_Communication service
  • 25 – Nudm_SubscriberDataManagement service
  • 26 – Nudm_UEContextManagement service
  • 27 – Npcf_SMPolicyControl service
  • 28 – Nchf_ConvergedCharging service

APN container IEs

Table 13. APN container IEs
Information element Description
ApnLength

Length of the APN in bytes
APN

Access point name
Note: APN is not reported in the UE level procedures (see UE-level procedures).

Session extended container IEs

The Session extended container presence is indicated by the ExtendedFlag.

Table 14. Session extended container IEs
Information element Description
UliLength

Length of the ULI
ULI

If the UliTypeFlag is not set (0), the ULI format is as specified in 3GPP TS 29.274, section 8.21.

Bytes defined in the specification from 5 onward are present in this field; the first 4 bytes (type, length, spare, instance) are omitted from the PCMD ULI field.

If the UliTypeFlag is set (1), the ULI format is as specified in 3GPP TS 29.061, section 16.4.7.2 set.

Bytes defined in the specification from 3 onward are present in this field; the first 2 bytes (containing 3GPP type and length) are omitted from the PCMD ULI field.

This format is used for 5G ULI.

Only the following types are reported:
  • 137 NrLocation – 5GS TAI and NCGI
  • 130 EutraLocation – 5GS TAI and ECGI
From 3GPP TS 29.571 (5.4.4.3-5):
  • TAI = PLMN-ID + 5GS TAC
  • ECGI = PLMN-ID + eutraCellId
  • NCGI = PLMN-ID + nrCellId
  • TAC, eutraCellId, and nrCellId encoded as per section 5.4.2 of 3GPP TS 29.571

MCC and MNC encoded per 3GPP TS 29.274 for the PLMN-ID part
Note: In 5G, the TAC part of TAI can be a 2- or 3-octet string, however in 2G, 3G, and 4G, it is always 2 octets.

Message container IEs

There are 0 to 40 message containers in the Session PCMD record.

Table 15. Message container IEs
Information element Description
MessageMarker_n

Code defining a specific procedure message when any message is received or sent during the associated procedure.

See Message marker IDs and SBI service operation messages for possible values and meanings.
ReferencePoint_n

Specifies the reference point where the message is received or sent

See Reference point and SBI services IDs for possible values and meanings
Direction_n

Specifies the direction of the message

See Direction_n IDs for possible values and meanings
TimestampMM_n

Time elapsed since the start of the procedure, in hundredths of seconds

MessageAI container IEs

There are 0 to 40 MessageAI containers in the Session PCMD record.

Table 16. MessageAI container IEs
Information element Description
MessageCauseCode Message cause or reason code

Bearer and QoS Flow container IEs

There are 0 to 11 bearer containers in the session PCMD record.

Table 17. Bearer and QoS Flow container IEs
Information element Description
BearerID

ID of the bearer
LBI

Identifier for the bearer

0 in the default bearer record

Unknown in 5GC QoS flow reporting if N26 interface is not used

LBI is not a unique identifier of a QoS flow; multiple QoS flows may share the same LBI
BearerResult

Bearer result value

See Results for possible values and their meanings.
BearerCause

Bearer cause value

See Causes for possible values and their meanings.

0 if no value reported

Identical to GTPv2 – external causes associated with detailed cause (internal status events)
BearerDetailedCause

Bearer detailed cause value

See Detailed causes for possible values and their meanings.

0 if no value reported

Identical cause code to internal status events
BearerQCI

Bearer QoS class ID

5QI value of the QoS flow for 5G sessions
PVI

Bearer pre-emption vulnerability indicator
PCI

Bearer pre-emption capability indicator
PL

Bearer priority level
FTeidUIpV4BrIdRef

4G – four-bit indicator:

  • 0x0 – absence of an IPv4 address
    Note: No FTEID IP address and no TEID containers are present if FTeidUIpV4BrIdRef and FTeidUIpV6BrIdRef are both 0x0.
  • equal to BearerId – reports an IPv4 address in the FTEID IP container immediately after the TEID container
  • X in range 0x5 to 0xF and not equal to the BearerId value – reports an IPv4 address of the bearer FTEID in the same session record with bearer X, serving as a reference to the bearer X FTEID IP (uses the same IP address)

5G – ignored if Tun5GIpv4 is set
FTeidUIpV6BrIdRef
4G – four-bit indicator:
  • 0x0 – absence of an IPv6 address
    Note: No FTEID IP address or TEID containers are present if FTeidUIpV4BrIdRef and FTeidUIpV6BrIdRef are both 0x0.
  • equal to BearerId – reports an IPv6 address in the FTEID IP container immediately after the TEID container or the IPv4 FTEID IP container
  • X in range 0x5 to 0xF and not equal to the BearerId value – reports the IPv6 address of the bearer FTEID in the same session record with bearer X, using the IP address as a reference to the bearer X FTEID IP (uses the same IP address)

5G – ignored if Tun5GIpv6 set

For an explicitly reported IPv6 address, the FTEID address reporting follows:

  • immediately after the IPv6 FTEID IP container, if present
  • immediately after the TEID container
QosFlag5G
  • 0 – reported container for an EPS bearer
  • 1 – reported container for a 5G QoS flow (5G QoS container is present)
Tun5GIpv4 Uses an IPv4 address for the 5G UP tunnel

If this or the Tun5GIpv6 flag is set, reports only one FTEID and ignores TeidUIpV4BrIdRef and TeidUIpV6BrIdRef IEs
Tun5GIpv6

Uses an IPv6 address for the 5G UP tunnel.

If this or the Tun5GIpv4 flag is set, reports only one FTEID and ignores TeidUIpV4BrIdRef and TeidUIpV6BrIdRef IEs

When explicitly reported, the IPv6 FTEID IP follows:
  • immediately after the IPv4 FTEID IP, if present
  • immediately after the TEID container

No FTEID IP address or TEID containers are present for this QoS flow if the following are 0:

  • Tun5GIpv4
  • Tun5GIPv6
  • QoSFlag5G

Reports FTEID only for the first QoS flow in the PCMD record

TEID container IEs

Table 18. TEID container IEs
Information element Description
TeidU

TEID value of the S1-U, for combined SGW + PGW sessions

TEID of the UP tunnel on the N3 UPF side (shared by all QoS flows), for 5G sessions

If multiple UPFs exist, N3 tunnel reporting for all QoS flows

TEID reported only for first QoS flow in the PCMD record

FTEID IP container IEs

Table 19. FTEID IP container IEs
Information element Description
FTeidUIp

IPv4 or IPv6 address

TEID of the UP tunnel on the N3 UPF side (shared by all QoS flows), for 5G sessions

If multiple UPFs exist, same tunnel reported for all UPFs

Bearer extended container IEs

Table 20. Bearer extended container IEs
Information element Description
Uplink APN-AMBR

Uplink aggregate maximum bit rate in kb/s
Downlink APN-AMBR

Downlink aggregate maximum bit rate in kb/s
Uplink MBR

Uplink maximum bit rate in kb/s
Downlink MBR

Downlink maximum bit rate in kb/s
Uplink GBR

Uplink guaranteed bit rate in kb/s
Downlink GBR Downlink guaranteed bit rate in kb/s

5GC QoS container IEs

Table 21. 5G QoS container IEs
Information element Description
QFI

QFI value of the QoS flow (1 to 63) (6 bits)

Mandatory element
RT

Resource type (2 bits):

  • 1 – GBR
  • 2 – non-GBR
  • 3 – delay critical GBR

Mandatory field
PDB

Packet delay budget (5 bits):

  • 0 – undefined
  • 1 – 5 ms
  • 2 – 10 ms
  • 3 – 30 ms
  • 4 – 50 ms
  • 5 – 60 ms
  • 6 – 75 ms
  • 7 – 100 ms
  • 9 – 150 ms
  • 11 – 200 ms
  • 13 – 300 ms
PER

Packet error rate (3 bits):

  • 0 – undefined
  • 1 – 10-6
  • 2 – 10-5
  • 3 – 10-4
  • 4 – 10-3
  • 5 – 10-2
QNC

QoS control status:

  • 0 – disabled
  • 1 – enabled
RQI

Reflective QoS status:

  • 0 – disabled
  • 1 – enabled
AW

Averaging window

Range: 1 to 4095 ms (12 bits)
MBV

Maximum burst volume

Range: 1 to 4095 Bytes (12 bits)

Charging container IEs

There are 1 to 11 Charging containers in the session PCMD record.

Table 22. Charging container IEs
Information element Description
GCID

Session GCID if BLC is 0 (5G records)

Bearer GCID if BLC is 1 (bearer-level charging, one GCID per bearer container)

UE IP container IEs

Table 23. UE IP container IEs
Information element Description
UeIPs

IP addresses allocated to the UE

Present when the PdnType is not 0

Length from 4 to 20 bytes, depending on the PdnType in the report header:

  • PdnType = 1 (IPv4) – UeIPs contain the IPv4 allocated to the UE, length is 4 bytes
  • PdnType = 2 (IPv6) – UeIPs contain the IPv6 allocated to the UE, length is 16 bytes
  • PdnType = 3 (dual stack) – first 4 bytes of the UeIPs contain the IPv4 allocated to the UE; next 16 bytes contain IPv6; length 20 bytes
Note: Because the PdnType is set to 0 for UE-level procedures, the UE IP is not reported; see UE-level procedures for more information.

SNSSAI container IEs

Table 24. SNSSAI container IEs
Information element Description
sst

Slice service type

Range: 0 to 215
sd

3-byte hex string

6-character hex string (0 to 9 and A to F); for example, 0xD143A5

Heartbeat message record IEs

The MAG-c supports Heartbeat container IEs for PCMD.

Table 25. Heartbeat container IE
Information element Description
HBSequenceNumber

Unique sequence identifier for the Heartbeat

Resets to 1:

  • after reaching the maximum value 65535
  • on failover or when PCMD record transmission is enabled
GwId

Mobile gateway ID

Range: 1 to 8
HBTxTime

Time the heartbeat message was transmitted

Seconds since 1970-01-01 00:00:00 UTC
SendingNodeIpV6
  • 1 – SendingNodeIP contains an IPv6 address
  • 0 – SendingNodeIP contains an IPv4 address stored in the first 4 bytes