PCMD record information elements
The MAG-c supports PCMD record IEs including header IEs, session IEs, and PCMD heartbeat message IEs.
Header information elements
The MAG-c supports Common Header, Report Header 2, and Sending Node IP container IEs.
Common Header IEs
Information element | Description |
---|---|
PCMDVersion |
Version of the PCMD feature Mandatory field 1 |
RecordType |
Type of record:
Mandatory element |
RecordLength |
Total record length in bytes Mandatory element |
Report Header2 IEs
Information element | Description |
---|---|
RecordOpeningTime |
Opening timestamp for the record generation First 4 bytes: seconds, indicating time since 1970-01-01 00:00:00 UTC Second 4 bytes: nanoseconds, precision of the procedure start time Mandatory element |
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. If the maximum is reached, the number is set to 1. If an MSCP-group or MG-Group failover occurs, the number is set to 1. If a switchover occurs to a new active card or VM, the numbering restarts from 1. Mandatory element |
GwId |
Mobile gateway ID Range: 1 to 8 Mandatory element |
MscpGroupId |
MSCP group ID Range: 1 to 15 Mandatory element |
SendingNodeType |
Type of node that sends the PCMD record:
Mandatory element |
UEid |
IMSI of the combined SGW-C + PGW-C session IMSI is encoded in TBCD format. The SUPI is used when the record is reported for a 5G PDU session. The field is set to zero when the IMSI or SUPI is not available; for example, emergency attach with just the IMEI. Mandatory element |
SendingNodeIpV6 |
Sending node IP address type:
|
Sending Node IP container IEs
Information element | Description |
---|---|
SendingNodeIP |
The IP address of the sending node is the IP address of the system interface of the base router. If the system interface is configured with both an IPv4 and an IPv6 address, the SendingNodeIP in the PCMD Header contains the IP address that matches the IP version on the transport layer. Mandatory element |
Session PCMD record information elements
The MAG-c supports session PCMD record IEs.
Session Decoding container IEs
Information element | Description |
---|---|
MessageNum |
Number of message containers Range: 0 to 40 Mandatory element |
ProcNum |
Number of procedure containers Range: 1 to 3 Mandatory element |
PeerNum |
Number of peers containers Range: 0 to 15 Mandatory element |
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. |
Information element | Description |
---|---|
BrNum |
Number of bearer containers, or the number of QoS Flows containers for 5G Sessions Range is 0 to 11 |
ApnFlag |
Presence of the APN or DNN container Mandatory element |
ExtendedFlag |
Extended report type flag The report type is extended when set to 1 Mandatory element |
ImeiFlag |
Presence of the IMEI or PEI for 5G Session container Mandatory element |
MsisdnFlag |
Presence of the MSISDN or GPSI for 5G Session container Mandatory element |
Session3 container IEs
Information element | Description |
---|---|
RatType |
Radio access technology:
Mandatory element |
DT |
Direct tunnel indication:
|
BLC |
Bearer level charging or sessions flag:
GCID is reported for every bearer For 5G sessions, only PDU session-level charging is supported Mandatory element |
CI |
Charging indication:
The charging indication takes into account online and offline charging as configured or imposed by the PCF |
PDNType |
PDN type:
|
IwkI |
Interworking indication, from the AMF for a 5G-attached UE or from the MME for a 4G-attached UE:
|
UPSelection |
Consists of UPSelectionAttributes and UPSelectionPeer; see the following table |
SSC-Mode |
SSC-Mode 1, 2, or 3 are reported Value 0 indicates undefined Mandatory element |
PduSessionId |
PDU session ID for the UE (0-15) Note: 0 for 4G sessions
|
Information element | Description |
---|---|
UPSelectionAttributes |
0 – UPSelection not relevant UPSelectionAttributes is 0 in the current version. Mandatory element |
UPSelectionPeer |
Present when UPSelectionAttributes is not 0. Conditional element |
Procedure container IEs
Information element | Description |
---|---|
ProcedureID |
ID of the procedure See ProcedureIDs for possible values and meanings. Mandatory element |
ProcedureResult |
ProcedureResult associated with the current procedure:
Mandatory element |
ProcedureCause |
ProcedureCause associated with the ProcedureResult for the current procedure. See Causes for possible values and meanings. When no value is reported, this is set to 0. This code is identical to the GTPv2, HTTP2, or PFCP external causes associated with the detailed cause (internal status events). Conditional element |
ProcedureDetailedCause |
ProcedureDetailedCause associated with the ProcedureCause for the current procedure. See Detailed causes for possible values and meanings. When no value is reported, this is set to 0. This code is identical to internal status events. Conditional element |
ProcedureDuration |
Elapsed time since the start of the procedure, in hundredths of seconds. Mandatory element |
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 The structure of the IMEI/SV is specified in 3GPP TS 23.003 and includes information about the origin, model, and serial number of the device. Non-zero if it is available Encoded in telephony binary-coded decimal (TBCD) Mandatory element |
MSISDN container IEs
Information element | Description |
---|---|
MSISDN |
MSISDN or GPSI identifying the subscription Non-zero if available Encoded in TBCD Mandatory element |
Peers container IEs
Information element | Description |
---|---|
PeerNId |
ID of the nth peer It is IPv4, IPv6, or UUID according to the peerIdType value for the specific peer. |
PeerIdType |
|
PeerType |
Indicates whether the PeerIP container is present, and if present, the type of peer node:
Mandatory element |
APN container IEs
Information element | Description |
---|---|
ApnLength |
Length of the APN in bytes Mandatory element |
APN |
Access Point Name Conditional element |
Session extended container IEs
The ULI container presence is indicated by the ExtendedFlag.
Information element | Description |
---|---|
UliLength |
Length of the ULI Optional element |
ULI |
If the UliTypeFlag is not set (0), the ULI format is as specified in 3GPP TS 29.274, section 8.21. Only the bytes from 5 onwards defined in the specification are present in this field (the first 4 bytes containing type, length, spare, and instance are not present in 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. Only the bytes from 3 onwards defined in the specification are present in this field (the first 2 bytes containing 3GPP type and length are not present in the PCMD ULI field). This format is used for 5G ULI. Only the following types are reported:
From 29.571 (5.4.4.3-5):
For the PLMN-ID part, the MCC and MNC are encoded according to 3GPP TS 29.274. Optional – Conditional element |
Message container IEs
There are 0 to 40 message containers in the Session PCMD record.
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. Conditional element |
ReferencePoint_n |
Code specifying the reference point where the message is received or sent. See Reference point and SBI services IDs for the possible values and meanings. Conditional element |
Direction_n |
Code specifying the direction of the message. See Direction_n IDs for the possible values and meanings. Conditional field |
TimestampMM_n |
Time elapsed since the procedure started, in hundredths of seconds. Conditional element |
MessageAI container IEs
There are 0 to 40 MessageAI containers in the Session PCMD record.
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.
Information element | Description |
---|---|
BearerID |
ID of the bearer Conditional element |
LBI |
Set to 0 in the default bearer record For 5GC QoS flow reporting, the BearerId is not known if the N26 interface is not used in the network. Also, the EBI is not a unique identifier of a QoS flow, so multiple QoS flows may be reported with the same EBI. Conditional element |
BearerResult |
Bearer result value See Results for a list of possible values and their meanings. Conditional element |
BearerCause |
Bearer cause value See Causes for a list of possible values and their meanings. When no value is reported, it is set to 0. Identical to GTPv2 – external causes associated with detailed cause (internal status events) Conditional element |
BearerDetailedCause |
Bearer detailed cause value See Detailed causes for a list of possible values and their meanings. When no value is reported, it is set to 0. The code is identical to internal status events. Conditional element |
BearerQCI |
Bearer QoS class ID For a 5G QoS flow, it is the 5QI value of the QoS flow. Conditional element |
PVI |
Bearer pre-emption vulnerability indicator Conditional element |
PCI |
Bearer pre-emption capability indicator Conditional element |
PL |
Bearer priority level Conditional element |
FTeidUIpV4BrIdRef |
Four-bit indicator:
Mandatory element |
FTeidUIpV6BrIdRef |
Four-bit indicator:
When an IPv6 address is explicitly reported, the FTEID IP address container is reported immediately following the IPv4 FTEID IP container (if this is present), or immediately following the TEID container if the IPv4 address is not present. If both FTeidUIpV4BrIdRef and FTeidUIpV6BrIdRef are set to 0x0, no FTEID IP address and no TEID containers are present. Mandatory element |
QosFlag5G |
When the flag is set to 1, a 5G QoS container is present. |
Tun5GIpv4 | When set, the IP address of the 5G UP
tunnel is an IPv4 address. If this flag or the Tun5GIpv6 flag is set, there is only one FTEID being reported and the FTeidUIpV4/V6BrIdRef IEs must be ignored. |
Tun5GIpv6 |
When set, the IP address of the 5G UP tunnel is an IPv6 address. If this flag or the Tun5GIpv4 flag is set, the FTeidUIpV4/V6BrIdRef IEs is ignored. When an IPv6 address is explicitly reported, the FTEID IP address container is reported immediately following the IPv4 FTEID IP container (if this is present) or right after the TEID container, if the IPv4 address is not present. If both Tun5GIpv4 and Tun5GIPv6 and QoSFlag5G are 0, no FTEID IP address and no TEID containers are present for this QoS flow. FTEID is reported only for the first QoS flow in a PCMD record. |
TEID container IEs
Information element | Description |
---|---|
TeidU |
TEID value of the S1-U for the combined SGW + PGW session. For 5G sessions, the TEID is the TEID of the UP tunnel on the N3 UPF side. A single TEID is reported for all the QoS flows. If there are multiple UPFs for some QoS flows, the N3 tunnel is reported for all. The TEID is reported only for the first QoS flow in a PCMD record. |
FTEID IP container IEs
Information element | Description |
---|---|
FTeidUIp |
IPv4 or IPv6 address The TEID for 5G sessions is the TEID of the UP tunnel on the N3 UPF side. A single TEID is reported for all the QoS flows. If there are multiple UPFs for some QoS flows, the N3 tunnel is reported for all the UPFs. |
Bearer extended container IEs
Information element | Description |
---|---|
Uplink APN-AMBR |
Uplink aggregate maximum bit rate in kb/s Conditional-optional element |
Downlink APN-AMBR |
Downlink aggregate maximum bit rate in kb/s Conditional-optional element |
Uplink MBR |
Uplink maximum bit rate in kb/s Conditional-optional element |
Downlink MBR |
Downlink maximum bit rate in kb/s Conditional-optional element |
Uplink GBR |
Uplink guaranteed bit rate in kb/s Conditional-optional element |
Downlink GBR | Downlink guaranteed bit rate in kb/s Conditional-optional element |
5GC 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):
Mandatory field |
PDB |
Packet delay budget (5 bits):
|
PER |
Packet error rate (3 bits):
|
QNC |
QoS control status:
|
RQI |
Reflective QoS status:
|
AW |
Averaging window (1 to 4095 ms) (12 bits) |
MBV |
Maximum burst volume (1 to 4095 Bytes) (12 bits) |
Charging container IEs
There are 1 to 11 Charging containers in the session PCMD record.
Information element | Description |
---|---|
GCID |
Session GCID when BLC is 0 Bearer GCID when BLC is 1, that is, bearer-level charging is used. In this case there are multiple GCID bearers, one per bearer container. Mandatory element |
UE IP container IEs
Information element | Description |
---|---|
UeIPs |
IP addresses allocated to the UE The container is present when the PdnType is not 0. Length is from 4 to 20 bytes, depending on the PdnType in the report header:
Optional element |
SNSSAI container IEs
Information element | Description |
---|---|
sst |
Slice service type Range: 0 to 215 |
sd |
6 byte-string, allowed characters "0" to "9" and "A"to "F"; for example, 0xD143A5 3 bytes, mandatory |
PCMD Heartbeat message IEs
The MAG-c supports Heartbeat container IEs for PCMD.
Information element | Description |
---|---|
HBSequenceNumber |
Unique sequence identifier for the Heartbeat If the maximum value of 65535 is reached, the number is set to 1. Number is reset to 1 on failovers and each time the PCMD record transmission is enabled. Mandatory element |
GwId |
Mobile gateway ID Range: 1 to 8 Mandatory element |
HBTxTime |
Timestamp when the heartbeat message was transmitted Seconds since 1970-01-01 00:00:00 UTC Mandatory element |
SendingNodeIpV6 |
Mandatory element |