4.13 E-UTRAN Trace Record Content
32.4233GPPRelease 16Subscriber and equipment traceTelecommunication managementTrace data definition and managementTS
For eNB, the Maximum level of detail shall be supported. The trace record is the same for management based activation and for signalling based activation.
Table 4.13.1 : E-UTRAN Trace Record Content
|
Interface (specific messages) |
Format |
Level of details |
Description |
||
|
Min |
Med |
Max |
|||
|
RRC (without rrc dedicated measurements) |
Decoded |
M |
M |
O |
Message name |
|
O |
O |
O |
Record extensions |
||
|
M |
M |
X |
Global eNBID of traced eNB |
||
|
M |
M |
X |
Dedicated IE extracted from RRC messages between the traced eNB and the UE. A subset of IEs as given in the table 4.13.2. is provided. |
||
|
ASN.1 |
X |
X |
M |
Raw Uu Messages: RRC messages between the traced eNB and the UE. The encoded content of the message is provided |
|
|
S1 |
Decoded |
M |
M |
O |
Message name |
|
O |
O |
O |
Record extensions |
||
|
M |
M |
X |
Global eNBID of traced eNB |
||
|
M |
M |
X |
E-RabId + Dedicated IE extracted from S1AP messages between the traced eNB and Core Network. A subset of IEs as given in the table 4.13.2. is provided. |
||
|
ASN.1 |
X |
X |
M |
Raw S1 Messages S1AP: messages between the traced eNB and Core Network The encoded content of the message is provided |
|
|
X2 |
Decoded |
M |
M |
O |
Message name |
|
O |
O |
O |
Record extensions |
||
|
M |
M |
X |
Global eNBID of traced eNB Global gNBID of connected gNB-CU-CP node over X2 (for NSA) |
||
|
M |
M |
X |
Dedicated IE extracted from X2AP messages between the traced eNB and the neighbouring eNB/connected gNB-CU-CP. A subset of IEs as given in the table 4.13.2.is provided |
||
|
ASN.1 |
X |
X |
M |
Raw X2 Messages:X2AP messages between the traced eNB and the neighbouring eNB/connected gNB-CU-CP. The encoded content of the message is provided |
|
|
RRC (only dedicated measurements) |
Decoded |
X |
M |
X |
Uu IEs from RRC measurement reports messages |
|
ASN.1 |
X |
X |
M |
RRC measurement reports messages |
|
NOTE: For the security keys in IEs or part of IEs that are containing security keys used by the eNB (e.g. KeNB), the value 0 shall be written in the trace file.
Definitions:
Global eNBID of traced eNB: The id of the eNB traced, e.g. the eNB which handles the connection of the traced MS, during the Trace Recording Session. The id corresponds to the “Global eNB ID”, as defined in [16] and [17].
Global eNBID of neighbouring eNB: The ids of all Neighbouring eNB involved in the X2 procedures during the Trace Recording Session. The id corresponds to the “Global eNB ID”, as defined in [16] and [17].
Global gNBID of connected gNB-CU-CP node over X2 (for NSA): The ids of all connected NSA nodes involved during the Trace Recording Session. The id corresponds to the “Global gNB ID”, as defined in [16] and [17].
cell Id: The cell Ids of the cells involved in the X2 procedures during the Trace Recording Session. The cell Ids is provided with each X2AP messages for which the cId is relevant.
E-RABId: Specific recorded IE that contains the E-RAB identifier.
Message name: Name of the protocol message
Record extensions: A set of manufacturer specific extensions to the record
Decoded: Some IEs shall be decoded (cf. detailed list in table 4.6.2. depending on trace depth)
ASN.1: Messages in encoded format
Table 4.13.2 : trace record description for minimum and medium trace depth
|
Interface name |
Prot. name |
IE name |
Message name(s) |
Trace depth |
Notes |
|
|---|---|---|---|---|---|---|
|
Min |
Med |
|||||
|
Uu |
RRC |
Cs fallback indicator |
MOBILITY FROM EUTRA COMMAND |
M |
M |
TS 36.331 |
|
CN domain |
PAGING |
O |
O |
TS 36.331 |
||
|
S-TMSI |
PAGING |
O |
O |
TS 36.331 |
||
|
ReestablishmentCause |
RRC CONNECTION REESTABLISHMENT REQUEST |
M |
M |
TS 36.331 |
||
|
Wait time |
RRC CONNECTION REJECT |
CM |
M |
TS 36.331 |
||
|
Release Cause |
RRC CONNECTION RELEASE |
M |
M |
TS 36.331 |
||
|
Redirection Information |
RRC CONNECTION RELEASE |
M |
M |
TS 36.331 |
||
|
Establishment Cause |
RRC CONNECTION REQUEST |
CM |
CM |
TS 36.331 |
||
|
Selected PLMN-Identity |
RRC CONNECTION SETUP COMPLETE |
CM |
CM |
TS 36.331 |
||
|
RegisteredMME |
RRC CONNECTION SETUP COMPLETE |
CM |
CM |
TS 36.331 |
||
|
Rat-Type |
UE CAPABILITY INFORMATION |
M |
M |
TS 36.331 |
||
|
Measured Results |
MEASUREMENT REPORT |
X |
M |
TS 36.331 |
||
|
CDMA2000-Type |
HANDOVER FROM EUTRA PREPARATION REQUEST UL HANDOVER PREPARATION TRANSFER UL INFORMATION TRANSFER |
M |
M |
TS 36.331 |
||
|
Target RAT Type |
MOBILITY FROM EUTRA COMMAND |
M |
M |
TS 36.331 |
||
|
ConnEstFailReport-r11 |
UE INFORMATION RESPONSE |
X |
M |
TS 36.331 |
||
|
RLF-Report-r9 |
UE INFORMATION RESPONSE |
X |
M |
TS 36.331 |
||
|
S1 |
S1AP |
E-RAB ID |
All messages where it is present |
M |
M |
TS 36.413 |
|
E-RAB Level QoS Parameters |
E-RAB SETUP REQUEST E-RAB MODIFY REQUEST INITIAL CONTEXT SETUP REQUEST |
M |
M |
TS 36.413 |
||
|
Cause |
INITIAL CONTEXT SETUP FAILURE UE CONTEXT RELEASE REQUEST UE CONTEXT RELEASE COMMAND UE CONTEXT MODIFICATION FAILURE HANDOVER REQUIRED HANDOVER PREPARATION FAILURE HANDOVER REQUEST HANDOVER FAILURE HANDOVER CANCEL PATH SWITCH REQUEST FAILURE NAS NON DELIVERY INDICATION |
M |
M |
TS 36.413 |
||
|
Handover Type |
HANDOVER REQUIRED HANDOVER COMMAND HANDOVER REQUEST |
M |
M |
TS 36.413 |
||
|
E-UTRAN CGI |
HANDOVER NOTIFY PATH SWITCH REQUEST INITIAL UE MESSAGE UPLINK NAS TRANSPORT |
CM |
CM |
TS 36.413 |
||
|
TAI |
HANDOVER NOTIFY PATH SWITCH REQUEST UPLINK NAS TRANSPORT |
M |
M |
TS 36.413 |
||
|
Target ID |
HANDOVER REQUIRED |
M |
M |
TS 36.413 |
||
|
CDMA2000 HO Status |
DOWNLINK S1 CDMA2000 TUNNELING |
M |
M |
TS 36.413 |
||
|
CDMA2000 RAT Type |
DOWNLINK S1 CDMA2000 TUNNELING UPLINK S1 CDMA2000 TUNNELING |
M |
M |
TS 36.413 |
||
|
CDMA2000 Sector ID |
UPLINK S1 CDMA2000 TUNNELING |
M |
M |
TS 36.413 |
||
|
CDMA2000 HO Required Indication |
UPLINK S1 CDMA2000 TUNNELING |
M |
M |
TS 36.413 |
||
|
X2 |
X2AP |
E-RAB id |
All messages where it is present |
M |
M |
TS 36.423 |
|
E-RAB Level QoS |
HANDOVER REQUEST SGNB ADDITION REQUEST SGNB ADDITION REQUEST ACKNOWLEDGE SGNB MODIFICATION REQUEST SGNB MODIFICATION REQUEST ACKNOWLEDGE SGNB MODIFICATION REQUIRED |
M |
M |
TS 36.423 |
||
|
Cause |
HANDOVER REQUEST HANDOVER PREPARATION FAILURE HANDOVER CANCEL SGNB ADDITION REQUEST REJECT SGNB RECONFIGURATION COMPLETE SGNB MODIFICATION REQUEST SGNB MODIFICATION REQUEST REJECT SGNB MODIFICATION REQUIRED SGNB MODIFICATION REFUSE SGNB RELEASE REQUEST SGNB RELEASE REQUEST REJECT SGNB RELEASE REQUIRED SGNB CHANGE REQUIRED SGNB CHANGE REFUSE |
M |
M |
TS 36.423 |
||
|
Target Cell ID |
HANDOVER REQUEST |
M |
M |
TS 36.423 |
||
|
GUMMEI |
HANDOVER REQUEST |
M |
M |
TS 36.423 |
||
|
UE History Information |
HANDOVER REQUEST |
M |
M |
TS 36.423 |
||
|
UE RLF Report Container |
RLF INDICATION |
X |
M |
TS 36.423 |
||
Constraints:
The condition for capturing the following Information Element is that Cell Traffic Trace is used:
– Wait time from RRC protocol.
– Establishment Cause from RRC protocol.
– Selected PLMN-Identity from RRC protocol.
– RegisteredMME from RRC protocol.
– E-UTRAN CGI from S1 interface from the following messages: Initial UE message, Handover Notify.