Tutorial Note From Mas Bian HArdiyanto RNO engineer from Central Java

Huawei LTE Signalling measurement Point based on Omstar R012:

1. RRC Setup Reject:
Analyse UU Trace, just include message of "RRC_CONN_REQ" and "RRC_CONN_REJ".
2. RRC Setup NoReply:
Analyse UU Trace, just include message of "RRC_CONN_REQ" and "RRC_CONN_SETUP".
3. S1 Sig ConnEst Fail:
Analyse S1 Trace include message of "S1AP_INITIAL_UE_MSG" and next message of "S
1AP_INITIAL_UE_MSG" is not "S1AP_INI
TIAL_CONTEXT_SETUP_REQ" or "S1AP_DL_NAS_TRANS" or "S1AP_UE_CONTEXT_REL_CMD".
4. ERAB Setup Fail due to MME Initial Context Setup timeout:
Analyse S1 trace, satisfy the condition: (1) Not include message of "S1AP_INITAI
L_CONTEXT_SETUP_FAIL"; (2) Include me
ssage of "S1AP_INITIAL_CONTEXT_SETUP_REQ" and "S1AP_UE_CONTEXT_REL_CMD"; (3) Not
include message of "S1AP_UE_CONTEXT
_REL_REQ" and "S1AP_INITIAL_CONTEXT_SETUP_RSP".
5. ERAB Setup Fail Non MME Initial Context Setup timeout:
Analyse S1 Trance, (S1 Trace include message of "S1AP_INITIAL_CONTEXT_SETUP_FAIL
") or (S1 trace include message of "
S1AP_S1_UE_CONTEXT_REL_REQ" and "S1AP_UE_CONTEXT_REL_REQ" and not include "S1AP_
INITIAL_CONTEXT_SETUP_RSP") or (trace
include message of "S1AP_ERAB_SETUP_REQ" and "S1AP_ERAB_SETUP_RSP" and the Relea
se cause of "S1AP_ERAB_SETUP_RSP" is
not null).
6. NAS Procedure Failure:
Analyse S1 Trace, Include message of "S1AP_INITIAL_UE_MSG" and "S1AP_DL_NAS_TRAN
S"; Not include message of "S1AP_INI
TIAL_CONTEXT_SETUP_REQ"; Release cause is not "Normal_Release", " Detach", "User
Inactivity", "cs fallback triggered"
,"UE Not Available For PS Service", "Inter-RAT redirection" in "S1AP_UE_CONTEXT_
REL_CMD" or "S1AP_DL_NAS_TRANS" with
eMM-cause or "S1AP_UL_NAS_TRANS" with eMM-cause.
7. Call Drop:
The eNodeB sends an E-RAB RELEASE INDICATION message to the MME and the release
cause is not "Normal Release","Detach
", "User Inactivity", "CS Fallback triggered", "UE Not Available For PS Service"
, "Inter-RAT Redirection","Successful
Handover";. The eNodeB sends a UE CONTEXT RELEASE REQUEST message to the MME and
the cause is not "Normal Release",
"Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available For PS S
ervice", "Inter-RAT Redirection","
Time Critical Handover", "Successful Handover".
8. Call Drop with MME:
An E-RAB release procedure initiated by the MME, the eNodeB receives an E-RAB RE
LEASE COMMAND message from the MME
and the release cause is not "Normal Release", "Detach", "User Inactivity","CS F
allback triggered","UE Not Available
For PS Service", "Inter-RAT Redirection", "Successful Handover";A UE context rel
ease procedure initiated by the MME,
the eNodeB receives a UE CONTEXT RELEASE COMMAND message from the MME and the re

lease cause is not "Normal Release",

"Detach", "User Inactivity", "CS Fallback triggered", "UE Not Available For PS S
ervice", "Inter-RAT Redirection",
"Successful Handover".
9. IRAT handover out preparation fail:
(1).IRAT Handover (Include E2W/E2T/E2G); The next message after HANDOVER REQUIRE
D (the handover typeis lte to utran)
sent by ENODEB on the S1 interface is not HANDOVER COMMAND,HANDOVER PREPARATION
FAILURE or HANDOVER CANCEL sent from
on the interface,source ENODEB.(2).IRAT Handover(Include E2W/E2T/E2G):After ENOD
EB asent the HANDVOER REQUIRED mess
age S1 the MME sends HANDOVER PREPARATION FAILURE.(3).IRAT Handover(Include E2W/
E2T/E2G):The next message after HAN
DOVER REQUIRED(the handover type is lte to utran) sent by ENODEB on the S1 inter
face is UE CONTEXT RELEASE COMMAND
sent by MME.
10. IRAT handover out execution fail:
After source ENODEB sends the RRC_MOBIL_FROM_EUTRA_CMD message, if the next mess
age received by source ENODEB is not
UE CONTEXT RELEASE COMMAND nor RRC reestablish request, the HO attempt fails.If
the next message is either UE CONTEXT
RELEASE COMMAND or RRC reestablish request, the HO attempt succeeds.?