LTE attach Procedure

-

In this series of Log Analysis, we are explaining about the LTE attach procedure, below is the detailed summary :

Step
Direction
Channel
Message
1
UE <---- NW
BCCH -> BCH,
No MAC Header, RLC TM, No PDCP
MIB

[0xB0C1] LTE MIB Message Log Packet
Version = 2
Physical cell ID = 378
FREQ = 1276
SFN = 320
Number of TX Antennas = 2
DL Bandwidth = 5 MHz (25)

Step
Direction
Channel
Message
2
UE <---- NW
BCCH -> DL SCH,
No MAC Header, RLC TM, No PDCP
SIBs

0xB0C0  LTE RRC OTA Packet  --  BCCH_DL_SCH / System Information
value BCCH-DL-SCH-Message ::
{ message c1 : systemInformation :
      { criticalExtensions systemInformation-r8 :
          { sib-TypeAndInfo
            { sib2 :
                { radioResourceConfigCommon
                  { rach-ConfigCommon
                    { preambleInfo
                      { numberOfRA-Preambles n52
                      
Step
Direction
Channel
Message
3
UE ----> NW
PRACH -> RACH,
No MAC Header, No RLC, No PDCP
PRACH Preamble
4
UE <---- NW
RACH -> DL SCH,
No MAC Header, No RLC, No PDCP
RACH Response

[0xB166] LTE PRACH Configuration
Version = 3
Logical Root Seq Index = 38
PRACH Config = 4
Preamble Format = 0
Duplex Mode = FDD
High Speed Flag = 0
PRACH Frequency Offset = 3
Max Transmissions MSG3 = 4
Cyclic Shift Zone Length = 12
RA Response Window Size = 10

Step
Direction
Channel
Message
5
UE ----> NW
UL SCH -> UL CCCH
MAC Header, No RLC, No PDCP
RRC Connection Request

[0xB0C0/012/014/002] | OTA LOG | UL_CCCH / RRC Connection Request
value UL-CCCH-Message ::=
{ message c1 : rrcConnectionRequest :
{ criticalExtensions rrcConnectionRequest-r8 :
{ ue-Identity randomValue : '11110001 11001000 10111110 10100000 01010101'B, establishmentCause mo-Signalling,

Step
Direction
Channel
Message
6
UE <---- NW
DL CCCH -> DL SCH
MAC Header, No RLC, No PDCP
RRC Connection Setup

[0xB0C0/012/012/004] | OTA LOG |  DL_CCCH / RRC Connection Setup
value DL-CCCH-Message ::=
{ message c1 : rrcConnectionSetup :
      { rrc-TransactionIdentifier 0,
criticalExtensions c1:rrcConnectionSetup-r8
            
Step
Direction
Channel
Message
7
UE ----> NW
UL SCH -> UL DCCH
MAC Header, RLC AM, PDCP
RRC : RRC Connection Setup Complete +
NAS : Attach Request (ESM:PDN Connectivity Request)

[0xB0C0/012/015/005] | OTA LOG | 11:26:11.146 | UL_DCCH / RRC Connection Setup Complete 
value UL-DCCH-Message ::=
{ message c1 : rrcConnectionSetupComplete :
      { rrc-TransactionIdentifier 0,
        criticalExtensions c1 : rrcConnectionSetupComplete-r8 :
            { selectedPLMN-Identity 1,
              registeredMM

[0xB0ED] | OTA LOG | LTE NAS EMM Plain OTA Outgoing Message | Attach request Msg
prot_disc = 7 (0x7) (EPS mobility management messages)
msg_type = 65 (0x41) (Attach request)
lte_emm_msg
emm_attach_request
tsc = 0 (0x0) (cached sec context)
nas_key_set_id = 4 (0x4)
att_type = 2 (0x2) (combined EPS/IMSI attach)
eps_mob_id
id_type = 6 (0x6) (GUTI)
odd_even_ind = 0 (0x0)
Guti_1111 = 15 (0xf)
MME_group_id = 36865 (0x9001)
MME_code = 3 (0x3)
m_tmsi = 3230808976 (0xc0923b90)
[0xB0E3] | OTA LOG | 11:26:11.965 | LTE NAS ESM Plain OTA Outgoing Message | PDN connectivity request 
msg_type = 208 (0xd0) (PDN connectivity request)
lte_esm_msg
pdn_connectivity_req
pdn_type = 3 (0x3) (Ipv4v6)
req_type = 1 (0x1) (initial request)
info_trans_flag_incl = 0 (0x0)
access_pt_name_incl = 1 (0x1)

Step
Direction
Channel
Message
8
UE <---- NW
DL DCCH -> DL SCH
MAC Header, RLC AM, PDCP
RRC : DL Information Transfer
EMM : Authentication Request

[0xB0C0/012/013/002] | OTA LOG |DL_DCCH / DL Information Transfer
value DL-DCCH-Message ::=
{ message c1 : dlInformationTransfer :
{ rrc-TransactionIdentifier 0,
criticalExtensions c1 : dlInformationTransfer-r8 :
{ dedicatedInfoType dedicatedInfoNAS : '27490DB1B54768E44A'H

0xB0EC  LTE NAS EMM Plain OTA Incoming Message -- Authentication request
prot_disc = 7 (0x7) (EPS mobility management messages)
msg_type = 82 (0x52) (Authentication request)
lte_emm_msg
  emm_auth_req
    tsc = 0 (0x0) (cached sec context)
    nas_key_set_id = 0 (0x0)
auth_param_RAND

Step
Direction
Channel
Message
9
UE ----> NW
UL SCH -> UL DCCH
MAC Header, RLC AM, PDCP
RRC : UL Information Transfer
EMM : Authentication Response

[0xB0C0/012/015/010] | OTA LOG |UL_DCCH / UL Information Transfer
value UL-DCCH-Message ::=
{ message c1 : ulInformationTransfer :
{ CriticalExtensions c1 : ulInformationTransfer-r8 :
{ dedicatedInfoType dedicatedInfoNAS :

0xB0ED  LTE NAS EMM Plain OTA Outgoing Message -- Authentication response Msg
prot_disc = 7 (0x7) (EPS mobility management messages)
msg_type = 83 (0x53) (Authentication response)
lte_emm_msg,  
emm_auth_resp,    auth_resp_param

Step
Direction
Channel
Message
10
UE <---- NW
DL DCCH -> DL SCH
MAC Header, RLC AM, PDCP
RRC : Security Mode Command

[0xB0C0/012/013/007] | OTA LOG | DL_DCCH / Security Mode Command
value DL-DCCH-Message ::=
{ message c1 : securityModeCommand :
{ rrc-TransactionIdentifier 0,
 criticalExtensions c1 : securityModeCommand-r8 :
{ securityConfigSMC
{ securityAlgorithmConfig
{ cipheringAlgorithm eea1,
integrityProtAlgorithm eia2

Step
Direction
Channel
Message
11
UE ----> NW
UL SCH -> UL DCCH
MAC Header, RLC AM, PDCP
RRC : Security Mode Complete

[0xB0C0/012/015/006] | OTA LOG|UL_DCCH / Security Mode Complete 
value UL-DCCH-Message ::=
{ message c1 : securityModeComplete :
{ rrc-TransactionIdentifier 0,
criticalExtensions securityModeComplete-r8 :

[0xB0C0/012/013/008] | OTA LOG | 11:26:11.407 | DL_DCCH / UE Capability Enquiry
value DL-DCCH-Message ::=
 { message c1 : ueCapabilityEnquiry :
{ rrc-TransactionIdentifier 0,
     criticalExtensions c1 : ueCapabilityEnquiry-r8 :
{ue-CapabilityRequest
{ eutra,
 utra,
 geran-cs
}

[0xB0C0/012/015/008] | OTA LOG | 11:26:11.417 | UL_DCCH / UE Capability Information 
value UL-DCCH-Message ::=
{ message c1 : ueCapabilityInformation :
{ rrc-TransactionIdentifier 0,
 criticalExtensions c1 : ueCapabilityInformation-r8 :
{ ue-CapabilityRAT-ContainerList

  
Step
Direction
Channel
Message
12
UE <---- NW
DL DCCH -> DL SCH
MAC Header, RLC AM, PDCP
RRC : RRC Connection Reconfiguration
EMM : Attach Accept
ESM : Activate Default EPS Bearer Context Request

[0xB0EC] | OTA LOG | 11:26:11.468 | LTE NAS EMM Plain OTA Incoming Message | Attach accept 
lte_emm_msg
emm_attach_accept
attach_result = 2 (0x2) (comb EPS/IMSI attach)

[0xB0E2] | OTA LOG | 11:26:11.469 | LTE NAS ESM Plain OTA Incoming Message | Activate default EPS bearer context request
msg_type = 193 (0xc1) (Activate default EPS bearer context request)
lte_esm_msg
act_def_eps_bearer_context_req

[0xB0C0/012/013/005] | OTA LOG | 11:26:11.464 | DL_DCCH / RRC Connection Reconfiguration 
value DL-DCCH-Message ::=
{ message c1 : rrcConnectionReconfiguration :
{ rrc-TransactionIdentifier 0,
criticalExtensions c1 : rrcConnectionReconfiguration-r8 :
{ measConfig
{ measObjectToAddModList
{ measObjectId 1,
 measObject measObjectEUTRA :

Step
Direction
Channel
Message
13
UE ----> NW
UL SCH -> UL DCCH
MAC Header, RLC AM, PDCP
RRC : RRC Connection Reconfiguration Complete

[0xB0C0/012/015/003] | OTA LOG | 11:26:11.468 | UL_DCCH / RRC Connection Reconfiguration Complete
value UL-DCCH-Message ::=
{ message c1 : rrcConnectionReconfigurationComplete :
  { rrc-TransactionIdentifier 0,
     criticalExtensions
  rrcConnectionReconfigurationComplete-r8 :
  

Step
Direction
Channel
Message
14
UE ----> NW
UL SCH -> UL DCCH
MAC Header, RLC AM, PDCP
EMM : Attach Complete
ESM : Activate Default EPS Bearer Context Accept

[0xB0ED] | OTA LOG | 11:26:11.492 | LTE NAS EMM Plain OTA Outgoing Message | Attach complete 
lte_emm_msg
emm_attach_complete
esm_msg_container
eps_bearer_id_or_skip_id = 5 (0x5)
prot_disc = 2 (0x2) (EPS session management messages)
trans_id = 0 (0x0)

[0xB0E3] | OTA LOG | 11:26:11.876 | LTE NAS ESM Plain OTA Outgoing Message | Activate default EPS bearer context accept  
msg_type = 194 (0xc2) (Activate default EPS bearer context accept)
lte_esm_msg
act_def_eps_bearer_context_accept
prot_config_incl = 0 (0x0)
ext_prot_config_incl = 0 (0x0)


Step
Direction
Channel
Message
15
UE <---- NW
DL DCCH -> DL SCH
MAC Header, RLC AM, PDCP
RRC : RRC Connection Release

[0xB0C0/012/013/006] | OTA LOG | 09:10:21.428 | DL_DCCH / RRC Connection Release 
value DL-DCCH-Message ::=
{ message c1 : rrcConnectionRelease :
{ rrc-TransactionIdentifier 0,
criticalExtensions c1 : rrcConnectionRelease-r8 :
{ releaseCause other,

Comments

Post a Comment

Popular posts from this blog

MAP Protocol Error codes and Supplementary Service codes

-
MAP Protocol Error codes and Supple Service codes  MAP Protocol Error Codes  Generic errors     34 System failure     35 Data Missing     36 Unexpected Data Value     21 Facility Not Supported     28 Incompatible Terminal     51 Resource Limitation  Identification and Numbering Errors     01 Unknown Subscriber     144 Number Changed     03 Unknown MSC     05 Unidentified Subscriber     07 Unknown Equipment  Subscription Errors     08 Roaming Not Allowed     09 Illegal Subscriber     12 Illegal Equipment     10 Bearer Service Not Provisioned     11 Teleservice Not Provision...
Read more

Cause Codes From Network

-
C AUSE CODES   FROM   NETWORK   Reference : 3GPP TS 24.008 10.5.3.6 and Annex G. Cause  No  1  :    “unassigned (unallocated) number” (UMTS specific cause values for call control) This cause indicates that the destination requested by the mobile station cannot be   reached  because, although the number is in a valid format, it is not currently assigned (allocated). Cause value = 2  : IMSI unknown in HLR (Causes related to MS identification) This cause is sent to the MS if the MS is not known (registered) in the HLR. This cause code  does not affect operation of the GPRS service, although is may be used by a GMM procedure. Cause value = 3  :   Illegal MS (Causes related to MS identification)   This cause is sent to the MS when the network refuses service to the MS either because an  identity of the MS is not acceptable to the network or because the MS does not pass the authenticat...
Read more

MCC-MNC Codes for India

-
S. No. MCC-MNC OPERATOR Circle 1 INA 00 404-00 SISTEMA SHYAM Rajasthan 2 INA 01 404-01 Vodafone Haryana 3 INA 02 404-02 Airtel Punjab 4 INA 03 404-03 Airtel Himachal Pradesh 5 INA 04 404-04 Idea Delhi 6 INA 05 404-05 Vodafone Gujarat 7 INA 07 404-07 Idea Andhra Pradesh 8 INA 09 404-09 Reliance Telecom Assam 9 INA 10 404-10 Airtel Delhi 10 INA 11 404-11 Vodafone Delhi 11 INA 12 404-12 Idea Haryana 12 INA 13 404-13 Vodafone Andhra Pradesh 13 INA 14 404-14 SPICE Punjab 14 INA 15 404-15 Vodafone Uttar Pradesh (East) 15 INA 16 404-16 Airtel North East 16 INA 17 404-17 Aircel West Bengal 17 INA 18 404-18 Reliance Telecom Himachal Pradesh 18 INA 19 404-19 IDEA Kerala 19 INA 20 404-20 Vodafone Mumbai 20 INA 21 404-21 LOOP Mumbai 21 INA 22 404-22 IDEA Maharashtra 22 INA 24 404-24 IDEA Gujarat 23 INA 25 404-25 Aircel Bihar 24 INA 27 404-27 Vodafone Maharashtra 25 INA 28 404-28 Aircel Orissa 26 INA 29 404-29 Aircel Assam 27 INA 30 404-30 Vodafone Kolkata 28 INA 31...
Read more

WCDMA Attach Procedure

-
WCDMA Attach Procedure WCDMA initial attach to the network, step by step messages from Network <=> MS 1. [0x412F/004/007] OTA LOG  BCCH-BCH DL/Complete SIB List [0x412F] WCDMA Signaling Messages Channel Type = DL_BCCH_BCH , Radio Bearer ID = 40, Uarfcn = 10807, Psc = 404, Message Length = 31 Interpreted PDU: value BCCH-BCH-Message ::= { message { sfn-Prime 106, payload completeSIB-List : { sib-Type systemInformationBlockType1, sib-Data-variable '11100110 00110011 11100001 00001000 010 ...'B } 2. [0x412F/254/001] OTA LOG BCCH-BCH DL/System Information Block Type 1 [0x412F] WCDMA Signaling Messages Channel Type = Complete SIB (254)  , Radio Bearer ID = 40, Uarfcn = N/A, Psc = N/A, Message Length = 20 Interpreted PDU: value SysInfoType1 ::= { cn-CommonGSM-MAP-NAS-SysInfo '8CF8'H, cn-DomainSysInfoList { { cn-DomainIdentity cs-domain, cn-Type gsm-MAP : '0A01'H, cn-DRX-CycleLengthCoeff 6 }, ...
Read more

GSM Device and Network Error Codes

-
GSM Device  and Network Error Codes     ERROR's (GSM Device  related codes)    ERROR: 0 Phone failure    ERROR: 1 No connection to phone    ERROR: 2 Phone adapter link reserved    ERROR: 3 Operation not allowed    ERROR: 4 Operation not supported    ERROR: 5 PH_SIM PIN required    ERROR: 6 PH_FSIM PIN required    ERROR: 7 PH_FSIM PUK required    ERROR: 10 SIM not inserted    ERROR: 11 SIM PIN required    ERROR: 12 SIM PUK required    ERROR: 13 SIM failure    ERROR: 14 SIM busy    ERROR: 15 SIM wrong    ERROR: 16 Incorrect password    ERROR: 17 SIM PIN2 required    ERROR: 18 SIM PUK2 required    ERROR: 20 Memory full    ERROR: 21 Invalid index    ERROR: 22 Not found    ERROR: 23 Memory failure ...
Read more

GSM Attach Procedure

-
GSM Attach Procedure GSM initial attach to the network, step by step messages from Network <=> MS 1. [0x5B2F/002/129] | OTA LOG | 07:21:52.178 | GSM DSDS RR Signaling Message Channel Type = RACH (2) Direction = Uplink Message Type = Open Loop CMD ACK (129) Message Length in bytes = 24 L3 Message in Hex:   17 49 06 1B 3E 46 04 F4 94 00 2A C8 00 0A 14 65 4A B8 00 00 81 00 05 9B Decoded Message: prot_disc = 7 (0x7) (GSM_EPS_MOB_MANAGEMENT) msg_type = 73 (0x49) 2.0 0x5B2F/002/129] | OTA LOG | 07:21:52.178 | GSM DSDS RR Signaling Message Channel Type = BCCH (1) Direction = Uplink Message Type = System Information Type 9 (4) Message Length in bytes = 19 L3 Message in Hex:   12 06 15 AB EB 7E 00 00 00 00 00 00 00 00 00 00 00 00 00 Decoded Message: prot_disc = 6 (0x6) (GSM_RR_MANAGEMENT) msg_type = 21 (0x15) MEASUREMENT_REPORT BA_USED = 1 (0x1) DTX_USED = 0 (0x0) RXLEV_FULL_SERVING_CELL = 43 (0x2b) 3G_BA_USED = 1 (0x1) ME...
Read more

LTE IMS MO Call

-
LTE IMS MO Call 0x1832  IMS Registration Version = 1 Registration Type = Initial Call Id Length = 59 Call Id = 3512047382_2335928920@2405:204:6c09:13b:ed63:680a:633:8ab7 Request Uri Length = 38 Request Uri = sip:ims.mnc861.mcc405.3gppnetwork.org To Length = 56 To = <sip:405861002372445@ims.mnc861.mcc405.3gppnetwork.org> Result = OK 0x156E  IMS SIP Message  --  IMS_SIP_REGISTER/INFORMAL_RESPONSE Version = 1 Direction = UE_TO_NETWORK SDP Presence = 0 SIP Call ID Length = 59 SIP Message Length = 2506 SIP Message Logged Bytes = 2507 Message ID = IMS_SIP_REGISTER Response Code = INFORMAL_RESPONSE (0) CM Call ID = 255 SIP Call ID = 3512047382_2335928920@2405:204:6c09:13b:ed63:680a:633:8ab7 Sip Message = REGISTER  sip:ims.mnc861.mcc405.3gppnetwork.org SIP/2.0 0x156E   IMS SIP Message  --  IMS_SIP_REGISTER/OK Version = 1 Direction = NETWORK_TO_UE SDP Presence = 0 SIP Call ID Length = 59 ...
Read more

SIP Response Codes

-
List of SIP response codes The Session Initiation Protocol (SIP) is a signalling protocol used for controlling communication sessions such as Voice over IP telephone calls. SIP is based around request/response transactions, in a similar manner to the Hypertext Transfer Protocol (HTTP). Each transaction consists of a SIP request (which will be one of several request methods), and at least one response. Contents 11xx—Provisional Responses 22xx—Successful Responses 33xx—Redirection Responses 44xx—Client Failure Responses 55xx—Server Failure Responses 66xx—Global Failure Responses 1xx—Provisional Responses 100 Trying Extended search being performed may take a significant time so a forking proxy must send a 100 Trying response. 180 Ringing Destination user agent received INVITE, and is alerting user of call. 181 Call is Being Forwarded Servers can optionally send this response to indicate a call is being forwarded. 182 Queued Indicates that the destination was temporarily unavai...
Read more