msg-type

The following guide describes the msg-type column from Edge Events.

The msg-type column provides information on the exact messages exchanged between UE, ENB, MME, SPGWC & HSS

msg-type	Description
Radio Setup Request	eNodeB initiates the procedure by sending S1 (Radio Trunk) Setup Request message including the appropriate data to the MME. This message contains TAC ,eNodeB name ,eNodeB IP and its PLMN. This message is sent by eNodeB to MME
Radio Setup Response	MME responds with S1 (Radio Trunk) Setup Response message including the appropriate data. When this procedure is finished, the S1 (Radio Trunk) interface is operational and other S1 messages can be exchanged. This message is send by MME to eNodeB.
Radio Setup Failure Response	This indicates the failure of the S1 setup (Radio Trunk) with MME. This message is sent by the MME to eNodeB to indicate the S1 (Radio Trunk) Setup failure.
Ue Attach Request	The event shows the attach request from UE to MME. Attach message is sent in the Initial UE message to the MME over the S1AP interface. The "Attach Request" is embedded in the Initial UE Message. The message also includes the PDN Connectivity Request message. The Tracking Area Identify (TAI) and E-UTRAN Cell Global Identifier (ECGI) are also included. The eNodeB uses the eNB-UE-S1AP ID to uniquely identify the UE.
Edge Trunk Authentication Request	MME sends a S6A diameter (Edge Trunk) message called Authentication Information Request (AIR) from the MME to the HSS and sends the corresponding mobile identity. This message includes IMSI ,PLMN & destination host & realm name.
Edge Trunk Authentication Response	Event showing successful Authentication Information Answer (AIA) from HSS to MME, which contains the authentication information which includes a random byte array denoted by RAND, the expected response from the UE to the MME denoted by XRES, the authentication response denoted by AUTN, and a shared key called the Key Access.
Edge Trunk Authentication Failure Response	Event showing unsuccessful Authentication Information Answer (AIA) from HSS to MME with mme cause: Unknown s6a Cause. This cause code describes that authentication is not successful as HSS doesn't have its authentication Data.
Ue Attach Failure	This describes the failure of the attach request. By sending this message MME informs UE that attach is not successful. Cause: UE identity cannot be derived by the network describes that attach rejected due to authentication failure.This message is sent by MME to UE
Data Session Request	MME initiates the default route establishment by asking the SPGWC to create a GTP tunnel. The source is identified by the fully qualified endpoint identifier with the Tunnel Endpoint Identifier (TEID) and the MME IP Address.This message is sent by MME to SPGWC
Data Session Response	Event showing a successful acknowledgment message from SPGWC to the MME that indicates the establishment of GPRS Tunneling Protocol for control (GTP-C) tunnel. The IP Address assigned to the UE is also included along with the downlink and uplink maximum data rates allowed at the APN level. The TAI and ECGI (E-UTRAN Cell Group Identifier) information identify the current location of the user.
Data Session Failure Response	This is an acknowledgment message from SPGWC to the MME that indicates the failure of the the data session with cause GTPV2C_CAUSE_MISSING_UNKNOWN_APN. This cause describes that apn is missing/unknown in SPGWC.
Ue Attach Failure	This describes the failure of the attach request. By sending this message MME informs UE that attach is not successful. Cause: mme Cause_network_failure describes that attach rejected due to some network error.This message is sent by MME to UE
Ue Attach Complete	This describes the successful response as attach procedure is completed. The eNodeB transports Attach Complete from UE to MME and Activate Default Bearer Accept.
Ue Detach Request	UE initiates a detach request for deletion of IMSI from the edge/MME. This message is sent by UE to MME
Data Session Request	This describes the initiation of deletion of IMSI (user session) from the Edge. A Delete Session Request message is sent by the MME to the SPGWC as part of the procedures: EUTRAN Initial Attach UE, HSS, or MME Initiated Detach UE or MME Requested PDN Disconnection
Data Session Response	Successful deletion of IMSI (user session) from the Edge. A Delete Session Response message is sent by the SPGWC to the MME as part of the procedures: EUTRAN Initial Attach UE, HSS, or MME Initiated Detach UE or MME Requested PDN Disconnection
UE Detach Response	This is an acknowledgment of the message of the UE deletion request. This message is sent by MME to UE to inform that UE is deleted from MME.
Edge Cdr	This describes that post-data consumption CDRs are generated based on the used volume threshold.This provides information about IMSI,eNodeB IP ,APN ,UE IP, Volume consumed and cause for CDR generation.CDR are generated in SPGWC.
Edge Trunk Delete UE Request	MME sends a Purge Request to HSS to notify that the subscriber is inactive & remove the data of a subscriber from its (temporary) storage.MME deletes data sent by HSS from its end and notifies the same to HSS.This message provides IMSI and Destination host & realm information
Edge Trunk Delete UE Response	This describes the successful deletion of IMSI (user session) from the HSS.This message is sent by HSS to MME
Edge Trunk Delete UE Failure Response	This describes an unsuccessful deletion of UE from HSS.Cause in Purge Answer defines the reason of failure.This message is sent by HSS to MME
UE Cancel Location Request	The subscription is withdrawn from HSS for a user (IMSI). It causes forceful deletion of IMSI (user session) from the Edge. This message is sent by HSS to MME.
UE Cancel Location Response	The forceful deletion due to subscription withdrawal is completed successfully for the particular IMSI. This is an acknowledgment sent from MME to HSS
Radio Trunk Disconnect	The S1 (Radio Trunk ) connection between the radio and the private network's edge is down. eNodeB sent this message to MME
Edge Trunk Disconnect	Edge Trunk (S6a connection between the edge to HSS host ) is down. We support two HSS host Cloud and Local. This message is sent from HSS to MME
Service Request Failure	The event shows that the service requested is rejected due to some failure on the network side .MME sends this message to UE
TAU Failure	This event describes failure of Tracking area update request.This message is sent by MME to UE in the response of Tracking area Update request.
Initial Context Setup Request	This message is sent by MME to eNB .Once received , eNB shall attempt to execute the requested E-RAB configuration. eNB store the UE Aggregate Maximum Bit Rate ,Handover Restriction List ,UE Radio Capability in the UE context and use them cor concerned UEs.
Edge Trunk Update Location Request	The Update Location Procedure shall be used between the MME and the HSS to update location information in the HSS. The procedure shall be invoked by the MME to inform the HSS about the identity of the MME currently serving the user & to update MME with user subscription data.
Edge Trunk Update Location Answer	This is sent by HSS in response to ULR .When receiving an Update Location request the HSS will check whether the IMSI is known.If it is known HSS will provide subscription profile & apn details in ULA
ESM Information Request	MME sends this message to UE to retrieve ESM information, i.e. protocol configuration options, APN, or both from the UE during the attach procedure if the UE has indicated (in the PDN CONNECTIVITY REQUEST) that it has ESM information that needs to be sent security protected.
ESM Information Response	After receiving the ESM INFORMATION REQUEST message, the UE shall send an ESM INFORMATION RESPONSE message to the network. .The UE shall include all the protocol configuration options that need to be transferred security protected, and APN if required, to the network in the ESM INFORMATION RESPONSE
PDN Connectivity Request	UE sent this message to MME to establish additional PDNs This is called a stand-alone PDN CONNECTIVITY REQUEST. The UE wishes to connect to a second PDN. The APN for the second PDN is included in the NAS message received from the UE.
E-RAB Setup Request	This message is sent by the MME to eNB and is used to request the eNB to assign resources on Uu and S1 for one or several ERABs.The MME accepts the second PDN connectivity requests and initiates the establishment of the Default EPS Bearer for the second PDN
E-RAB Setup Response	This message is sent by the eNB to MME and is used to report the outcome of the request from the E-RAB SETUP REQUEST message. The eNodeB responds with details about the RAB establishment for the new RAB (eRAB id 6)
Activate Default EPS Bearer Context Accept	This message is sent by UE to MME. UE responds with the establishment of the Default EPS Bearer for the second PDN.
PDN Disconnect Request	This message is sent by UE to MME. Successful completion of this procedure means that all EPS bearer contexts established towards this PDN, including the default EPS bearer context, are released.