Message

The following guide describes the message section from Thing Events.

Event Message is the last column of Event logs and probably the most important source of information about the call flow. This provides detailed information on Thing logs.

Message-Type

Description

Core-Type

Message

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.

"Initial UE Message, Attach Request, PDN Connectivity Request","protocol":"S1AP","node":"MME","direction":"Sent","enodeb-ue-s1ap-id":2,"serving-network-mcc":"425","serving-network-mnc":"99","imsi":"315010006700038"

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

{"destination-type":"KIBANA-EVENTS","msg-type":"Uplink NAS Transport, ESM Information Response","protocol":"S1AP","node":"MME","direction":"Received","seq-no":1,"apn":"data.mono","apn-length":10,"enodeb-ue-s1ap-id":393,"imsi":"315010006700038"}

Ue Attach Complete

This describes the successful response as attach procedure is completed. The eNodeB transports Attach Complete from UE to MME and Activate Defaut Bearer.

"Uplink NAS Transport, Attach Complete","protocol":"S1AP","node":"MME","direction":"Received","reason":"This message is not supported by MME.","enodeb-ue-s1ap-id":2,"imsi":"315010006700038"

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

"Downlink NAS Transport Attach Reject","protocol":"S1AP","node":"MME","direction":"Sent","mme-ue-s1ap-id":95,"enodeb-ue-s1ap-id":529,"cause":"emmCause_ue_id_not_derived_by_network","imsi":"315010006700038"

Ue Detach Request

UE initiates a detach request for de-registering from the Network. This message is sent by UE to MME

"Uplink NAS Transport, Detach Request (UE Originating Detach)","protocol":"S1AP","node":"MME","direction":"Received","seq-no":1,"enodeb-ue-s1ap-id":816,"imsi":"315010006700038"

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.

"Authentication Information Request","protocol":"S6a","node":"MME","direction":"Sent","session-id":"edge22.edge.monogoto.io:1756743050:718:4","dst-host":"drafr1.monogoto.io","dst-realm":"monogoto.io","imsi":"315010006700038","serving-network-mcc":"425","serving-network-mnc":"99"

Edge Trunk Authentication Answer

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.

"Authentication Information Answer","protocol":"S6a","node":"MME","direction":"Received","session-id":"edge22.edge.monogoto.io:1756743050:718:4","dst-host":"drafr1.monogoto.io","dst-realm":"monogoto.io","imsi":"315010006700038"

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.

"Update Location Request","protocol":"S6a","node":"MME","direction":"Sent","session-id":"edge22.edge.monogoto.io:1756743050:168:4","dst-host":"drafr1.monogoto.io","dst-realm":"monogoto.io","imsi":"315010006700038"

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

"Update Location Answer","protocol":"S6a","node":"MME","direction":"Received","session-id":"edge22.edge.monogoto.io:1756743050:168:4","dst-host":"drafr1.monogoto.io","dst-realm":"monogoto.io","imsi":"315010006700038","apn-profiles":[{"apn":"data.mono","apn_length":9}]

Edge Trunk Purge 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

"Purge Request","protocol":"S6a","node":"MME","direction":"Sent","session-id":"edge22.edge.monogoto.io:1756471690:872:102","dst-host":"drafr1.monogoto.io","dst-realm":"monogoto.io","imsi":"315010006700038"

Edge Trunk Purge Answer

This describes the successful deletion of IMSI (user session) from the HSS.This message is sent by HSS to MME

"Purge Answer","protocol":"S6a","node":"MME","direction":"Received","session-id":"edge22.edge.monogoto.io:1756471690:872:102","imsi":"315010006700038"

Edge Trunk 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.

"Cancel Location Request","protocol":"S6a","node":"MME","direction":"Received","imsi":"240075870544561"

Edge Trunk Cancel Location Answer

The forceful deletion due to subscription withdrawal is completed successfully for the particular IMSI. This is an acknowledgment sent from MME to HSS

"Cancel Location Answer","protocol":"S6a","node":"MME","direction":"Sent","imsi":"240075870544561"

Create 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

"Create Session Request","protocol":"GTPv2","node":"MME","direction":"Sent","imsi":"315010006700038","apn":"data.mono","apn-length":9,"ambr-uplink":210000,"ambr-downlink":210000,"serving-network-mcc":"425","serving-network-mnc":"99"

Create Session Request

SPGWC receives the default route establishment from MME 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 received by SPGWC from MME.

"Create Session Request","protocol":"GTPv2","node":"SPGWC","direction":"Received","msg-type-no":32,"msg-length":228,"seq-no":1919,"teid":"0","imsi":"315010006700038","msisdn":508182221433,"apn":"data.mono","f-teid":[{"intfc-type":"S11 MME GTP-C interface","teid":"a","ip-addr":"10.52.103.175"}]

Create 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.

"Create Session Response","protocol":"GTPv2","node":"SPGWC","direction":"Sent","msg-type-no":33,"msg-length":143,"seq-no":1919,"teid":"a","imsi":"315010006700038","pdn-type":"IPV4","pdn-addr":"192.168.100.247"

Create Session Response

"Create Session Response","protocol":"GTPv2","node":"MME","direction":"Received","imsi":"315010006700038","teid":"a","pdn-addr":"192.168.100.247","f-teid":[{"intfc-name":"S11 / S4 SGW GTP-C Interface","teid":"c10016","ip-addr":"10.52.103.172"}],"bearer-ctxt":{"f-teid":[{"intfc-name":"S1-U SGW GTP-U Interface","teid":"f0c10016","ip-addr":"192.168.200.3"}],"mbr-uplink":1650000,"mbr-downlink":1650000}

Delete UE 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

"Delete Sesssion Request","protocol":"GTPv2","node":"SPGWC","direction":"Received","msg-type-no":36,"msg-length":23,"seq-no":1729,"teid":"c10009","imsi":"315010006700038","eps-bearer-id":5

Delete UE Request

This describes the initiation of deletion of IMSI (user session) from the Edge. A Delete Session Request message is received by the SPGWC from the MME as part of the procedures: EUTRAN Initial Attach UE, HSS, or MME Initiated Detach UE or MME Requested PDN Disconnection

"Delete Sesssion Request","protocol":"GTPv2","node":"MME","direction":"Sent","imsi":"315010006700038","eps-bearer-id":5

Delete UE Response

Successful deletion of IMSI (user session) from the Edge. A Delete Session Response message is received by the MME from the SPGWC as part of the procedures: EUTRAN Initial Attach UE, HSS, or MME Initiated Detach UE or MME Requested PDN Disconnection

"Delete Session Response","protocol":"GTPv2","node":"MME","direction":"Received","imsi":"315010006700038"

Delete UE 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

"Delete Session Response","protocol":"GTPv2","node":"SPGWC","direction":"Sent","msg-type-no":37,"msg-length":14,"seq-no":1729,"teid":"8","imsi":"315010006700038"

Pfcp Session Establishment Request

A PFCP Session Establishment Request is a message sent by a SPGWC to UPF to create a new PFCP session context.

"Pfcp Session Establishment Request","protocol":"PFCP","node":"SPGWC","direction":"Sent","msg-type-no":50,"msg-length":542,"seq-no":17252,"sess-id":"0","imsi":"315010006700038","node-addr":"10.52.103.172","f-seid":[{"sess-id":"c100165","ip-addr":"10.52.103.172"}],"pdn-type":"IPV4"

Pfcp Session Establishment Response

A PFCP Session Establishment Response is a message sent by a UPF to SPGWC after a PFCP Session Establishment Request is received, acknowledging the request and providing necessary information such as the allocated User Plane TEID (Tunnel Endpoint Identifier) and other forwarding rules to establish the PDU session

"Pfcp Session Establishment Response","protocol":"PFCP","node":"SPGWC","direction":"Received","msg-type-no":51,"msg-length":43,"seq-no":17252,"sess-id":"c100165","imsi":"315010006700038","node-addr":"192.168.85.21","f-seid":[{"sess-id":"5886bc5185426342","ip-addr":"10.52.103.183"}]

Pfcp Session Modification Request

A PFCP Session Modification Request is a message from SPGW to UPF to update parameters for an existing PFCP session or request usage information (counters).

"Pfcp Session Modification Request","protocol":"PFCP","node":"SPGWC","direction":"Sent","msg-type-no":52,"msg-length":69,"seq-no":19053,"sess-id":"5886bc5185426342","imsi":"315010006700038","f-teid":[{"sess-id":"c100165","ip-addr":"10.52.103.172"}]

Pfcp Session Modification Response

A PFCP Session Modification Response is an Acknwledgement message from UPF to SPGWC.

"Pfcp Session Modification Response","protocol":"PFCP","node":"SPGWC","direction":"Received","msg-type-no":53,"msg-length":17,"seq-no":22935,"sess-id":"c100195","imsi":"315010006700038"

Servcie Request

A 4G service request is the process by which a mobile device (UE) or the network initiates a connection to enable data services, moving the UE from an idle to a connected state

{"destination-type":"KIBANA-EVENTS","msg-type":"Initial UE Message, Service Request","protocol":"S1AP","node":"MME","direction":"Sent","enodeb-ue-s1ap-id":5,"serving-network-mcc":"425","serving-network-mnc":"99", "imsi": "315010006700038"}

CDR

CDR- Describes that information is about the Call Data Record generated for UE based on the volume threshold used. CDR records are visible only after downloading events from the Download button. Once downloaded, you can view records from the first date of the month till the requested date.

{"usage-report":"KIBANA-CDR","seq-no":2451886,"edge-id":"Edge15-AccessPark@Union_Town","edge-cid":"edge15","imsi":"314030000010749","imei":"867945040093955","enb-id":"18","enb-ip":"10.200.24.7","plmn":"314030","apn":"default.data.mono","ue-ip-address":"10.200.29.19","volume-consumed":10240000,"cause":"ThresholdReached","start-time":"2025-09-09 12:01:11.575","stop-time":"2025-09-09 12:01:18.018","duration-in-seconds":6.443,"rat":"4G"}

Initial UE Message

The "Initial UE Message" is an NGAP (NG Application Protocol) message sent from the gNB (5G base station) to the AMF (Access and Mobility Function) that carries the UE's initial Registration Request.

{"destination-type":"KIBANA-EVENTS","node":"amf","ran-node-ip":"192.168.200.94","ran-ue-ngap-id":2,"amf-ue-ngap-id":2,"imsi":"295050950007208","secondary-ue-id":"315010cafe0000000001","secondary-ue-id-type":"5G-GUTI","ran-node-name":"NA","ran-node-id":"99974000004","direction":"Received","reg-type":"5GS Initial Registration","msg-type":"Initial UE Message","time":"2025-09-08T06:19:37.205Z"}

Authentication Request

Authentication Request is Initiated by AMFto carry out authentication process by challenging the UE. It carries information like RAND: Random challenge AUTN: Authentication token generated by the UDM

{"destination-type":"KIBANA-EVENTS","node":"amf","ran-node-ip":"192.168.200.94","ran-ue-ngap-id":6,"amf-ue-ngap-id":6,"imsi":"295050950007208","secondary-ue-id":"315010cafe0000000003","secondary-ue-id-type":"5G-GUTI","ran-node-name":"NA","ran-node-id":"99974000004","msg-type":"Authentication Request","direction":"Sent","time":"2025-09-08T07:08:03.780Z"}

Authentication Response

Authentication Response is sent by UE to AMF to Prove that the UE has the correct key and has successfully verified the challenge.

{"destination-type":"KIBANA-EVENTS","node":"amf","imsi":"295050950007208","secondary-ue-id":"315010cafe0000000003","secondary-ue-id-type":"5G-GUTI","ran-node-name":"NA","ran-node-id":"99974000004","ran-node-ip":"192.168.200.94","ran-ue-ngap-id":6,"amf-ue-ngap-id":6,"msg-type":"Authentication Response","direction":"Received","time":"2025-09-08T07:08:03.889Z"}

Authentication Failure Response

Authentication Failure Response message is sent If Authenttication Failed for any reasons (Illegal UE, Wrong Keys etc).

{"destination-type":"KIBANA-EVENTS","node":"amf","ran-node-ip":"192.168.200.94","ran-ue-ngap-id":10,"amf-ue-ngap-id":10,"imsi":"295050950007208","secondary-ue-id":"315010cafe0000000006","secondary-ue-id-type":"5G-GUTI","ran-node-name":"NA","ran-node-id":"99974000004","msg-type":"Authentication Failure Response","direction":"Received","cause":"ngKSI already in use (71)","time":"2025-09-08T07:57:20.798Z"}

Registration Complete

5G registration complete indicates your mobile device has successfully connected to the 5G network. For data access UE should send PDU session establishment Request.

{"destination-type":"KIBANA-EVENTS","node":"amf","ran-node-id":"99974000004","ran-node-ip":"192.168.200.94","ran-ue-ngap-id":7,"amf-ue-ngap-id":7,"imsi":"295050950007208","secondary-ue-id":"315010cafe0000000005","secondary-ue-id-type":"5G-GUTI","ran-node-name":"NA","msg-type":"Registration Complete","direction":"Received","time":"2025-09-08T07:20:54.793Z"}

Deregistration Request - UE Originated

Deregistration Request - UE Originated message is sent by UE to network to de-regsiter from network.

{"destination-type":"KIBANA-EVENTS","node":"amf","ran-node-name":"NA","ran-node-id":"99974000004","ran-node-ip":"192.168.200.94","ran-ue-ngap-id":35,"amf-ue-ngap-id":1122,"imsi":"999740950006019","secondary-ue-id":"fe000000000b","secondary-ue-id-type":"5G-S-TMSI","msg-type":"Deregistration Request - UE Originated","direction":"Received","ue_ip":"NA","tac":"000200","serving-network-mcc":"999","serving-network-mnc":"74","time":"2025-09-05T11:39:24.655Z"}

PDU Session Establishment Request

PDU Session Establishment Request is sent by UE to AMF to initiate a request for a new data session.

{"destination-type":"KIBANA-EVENTS","node":"amf","amf-ue-ngap-id":2,"imsi":"999740950006019","secondary-ue-id":"315010cafe000000002","secondary-ue-id-type":"5G-GUTI","ran-node-name":"NA","ran-node-id":"99974000004","ran-node-ip":"192.168.200.94","ran-ue-ngapid":3,"direction":"Received","session-id":5,"dnn-name":"data.mono","msg-type":"PDU Session Establishment Request","time":"2025-0901T16:15:07.339Z"}

PDU Session Resource Setup Request - PDU Session Establishment Accept

PDU Session Resource Setup Request - PDU Session Establishment Accept is sent by AMF to gNB to Instructs the gNB to set up the necessary resources (radio and user plane) for the PDU session(s).

{"node":"amf","destination-type":"KIBANA-EVENTS","amf-ue-ngap-id":270,"imsi":"999740950006019","secondary-ue-id":"fe0000000003","econdary-ue-id-type":"5G-S-TMSI","ran-node-name":"NA","ran-node-id":"99974000004","ran-node-ip":"192.168.200.94","ran-ue-ngap-id"35,"s-nssai":{"sd":0,"sst":0},"msg-type":"PDU Session Resource Setup Request - PDU Session Establishment Accept","direction":"Sen","session-id":0,"ue-ip-addr":"","session-ambr":{"downlink":0,"uplink":0},"dnn":"","time":"2025-09-02T09:25:46.984Z"}

PDU Session Resource Setup Response

This message confirms the successful (or failed) setup of user-plane resources (e.g., GTP-U tunnels) for one or more PDU sessions at the RAN (gNB) side.

{"destination-type":"KIBANA-EVENTS","node":"amf","secondary-ue-id":"315010cafe0000000002","secondary-ue-id-type":"5G-GUTI","ran-nde-name":"NA","ran-node-id":"99974000004","ran-node-ip":"192.168.200.94","ran-ue-ngap-id":3,"amf-ue-ngap-id":2,"imsi":"99974095006019","msg-type":"PDU Session Resource Setup Response","direction":"Received","ue_ip":"192.168.120.2","tac":"000002","serving-netork-mcc":"999","serving-network-mnc":"74","time":"2025-09-01T16:15:07.418Z"}

CDR

{"usage-report":"KIBANA-CDR","seq-no":56,"edge-id":"edge22","imsi":"315010006701653","imei":"352739200332598","enb-id":"000004","enb-ip":"192.168.200.94","plmn":"99974","apn":"default.data.mono","ue-ip-address":"192.168.120.133","volume-consumed":0,"cause":"SessionTerminated","start-time":"2025-09-09 09:54:55.264","stop-time":"2025-09-09 09:54:56.342","duration-in-seconds":"1.078","edge-cid":"edge22","rat":"5G"}

PreviousType NextRadio

Last updated 2 days ago

Was this helpful?