Long Term Evolution

Home Top Ad

ESM Information Response Time : 11:41:41.491 Vendor Header Length : 37 Log Code (Hex) : 0xB0E3 HW Timestamp : (70928885.00 ms) 19:42:08.8...

ESM Information Response

ESM Information Response

Time : 11:41:41.491
Vendor Header
Length : 37
Log Code (Hex) : 0xB0E3
HW Timestamp : (70928885.00 ms) 19:42:08.885
1.25 ms fraction : 0.00
CFN : 120
1.25 ms counter : 805512103108
Protocol discriminator : (2) EPS session management messages
EPS Bearer Identity : 0
Procedure Transaction Identity : 12
Message type : 218
Access point name
Access point name value : broadband

ESM Information Request Time : 11:41:41.491 Vendor Header Length : 19 Log Code (Hex) : 0xB0E2 HW Timestamp : (70928885.00 ms) 19:42:08...

ESM Information Request

ESM Information Request

Time : 11:41:41.491
Vendor Header
Length : 19
Log Code (Hex) : 0xB0E2
HW Timestamp : (70928885.00 ms) 19:42:08.885
1.25 ms fraction : 0.00
CFN : 76
1.25 ms counter : 805512103108
Protocol discriminator : (2) EPS session management messages
EPS Bearer Identity : 0
Procedure Transaction Identity : 12
Message type : 217

Identity Response Time : 11:41:41.086 Vendor Header Length : 33 Log Code (Hex) : 0xB0ED HW Timestamp : (70928535.00 ms) 19:42:08.535 1...

Identity Response

Identity Response

Time : 11:41:41.086
Vendor Header
Length : 33
Log Code (Hex) : 0xB0ED
HW Timestamp : (70928535.00 ms) 19:42:08.535
1.25 ms fraction : 0.00
CFN : 24
1.25 ms counter : 805512102828
Protocol discriminator : (7) EPS mobility management messages
Security Header Type : 0
Message type : 86
Mobile identity
Odd/even indication : (1) Odd number of digits
Type of identity : (1) IMSI
Identity digits (BCD) : 310980300013567

Identity Request Time : 11:41:41.086 Vendor Header Length : 19 Log Code (Hex) : 0xB0EC HW Timestamp : (70928533.75 ms) 19:42:08.534 ...

Identity Request

Identity Request

Time : 11:41:41.086
Vendor Header
Length : 19
Log Code (Hex) : 0xB0EC
HW Timestamp : (70928533.75 ms) 19:42:08.534
1.25 ms fraction : 0.00
CFN : 188
1.25 ms counter : 805512102827
Protocol discriminator : (7) EPS mobility management messages
Security Header Type : 0
Message type : 85
Identity type 2
Type of identity : (1) IMSI

Attach Accept Time : 11:41:42.131 Vendor Header Length : 152 Log Code (Hex) : 0xB0EC HW Timestamp : (70929508.75 ms) 19:42:09.509 ...

Attach Accept

Attach Accept

Time : 11:41:42.131
Vendor Header
Length : 152
Log Code (Hex) : 0xB0EC
HW Timestamp : (70929508.75 ms) 19:42:09.509
1.25 ms fraction : 0.00
CFN : 64
1.25 ms counter : 805512103607
Protocol discriminator : (7) EPS mobility management messages
Security Header Type : 0
Message type : 66
EPS Attach Result
spare : 0
EPS Attach Result Value : (2) Combined EPS/IMSI attach
GPRS timer
Unit : (1) Value is incremented in multiples of 1 minute
Value : (30) 30 minutes
Tracking area identity list
Length : 6
spare : 0
Type Of List : (0) list of TACs belonging to one PLMN, with non-consecutive TAC values
Number Of Elements : 1 Elements
TrackingAreaIdentity
plmn
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
TAC : 64257
TACValues :
NASMessageContainer
Protocol discriminator : 2 (ESM)
MessageType : Activate Default EPS Bearer Context Request
Message Contents : 52 0C C1 01 08 1D 09 62 72 6F 61 64 62 61 6E 64 06 6D 6E 63 39 38 30 06 6D 63 63 33 31 30 04 67 70 72 73 05 01 0A 5D 0A 1F 5D 01 00 30 10 14 92 1F 73 96 FE FE 73 2A FF FF 00 81 00 54 00 32 05 82 34 01 08 5E 04 FE FE 81 54 27 15 80 80 21 0A 02 00 00 0A 83 06 AC 1A 26 02 00 0D 04 AC 1A 26 01
GUTI
Length : 11
Odd/even indication : (0) Even number of digits
Type of identity : (6) Reserved
plmn
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
MMEGroupID : 65520
MMECode : 1
M_TMSI : 3490051258
Location Area Identification
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
Location area code (LAC) : 49000 (Hex 0xBF68)
Mobile identity
Odd/even indication : (0) Even number of digits
Type of identity : (4) TMSI/P-TMSI
TMSI/P-TMSI : Hex 0x0110F0EA

Attach Request Time : 11:41:41.070 Vendor Header Length : 119 Log Code (Hex) : 0xB0ED HW Timestamp : (70928378.75 ms) 19:42:08.379 ...

Attach Request

Attach Request

Time : 11:41:41.070
Vendor Header
Length : 119
Log Code (Hex) : 0xB0ED
HW Timestamp : (70928378.75 ms) 19:42:08.379
1.25 ms fraction : 0.00
CFN : 80
1.25 ms counter : 805512102703
Protocol discriminator : (7) EPS mobility management messages
Security Header Type : 0
Message type : 65
NAS Key Set Identifier
TSC : (0) native security context
Key : 0
EPS Attach Type
EPS Attach Type Value : (2) combined EPS/IMSI attach
Old GUTI or IMSI
Length : 11
Odd/even indication : (0) Even number of digits
Type of identity : (6) Reserved
plmn
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
MMEGroupID : 9500
MMECode : 2
M_TMSI : 3758224433
UE Network Capability
Length : 4
128EEA0 : (1) supported
128EEA1 : (1) supported
128EEA2 : (1) supported
EEA3 : (0) not supported
EEA4 : (0) not supported
EEA5 : (0) not supported
EEA6 : (0) not supported
EEA7 : (0) not supported
128EIA1 : (1) supported
128EIA2 : (1) supported
EIA3 : (0) not supported
EIA4 : (0) not supported
EIA5 : (0) not supported
EIA6 : (0) not supported
EIA7 : (0) not supported
UEA0 : (1) supported
UEA1 : (1) supported
UEA2 : (0) not supported
UEA3 : (0) not supported
UEA4 : (0) not supported
UEA5 : (0) not supported
UEA6 : (0) not supported
UEA7 : 0
UCS2 : The UE has a preference for the default alphabet (defined in 3GPP TS 23.038 [3]) over UCS2 (see ISO/IEC 10646 [29]).
UIA1 : (1) supported
UIA2 : (0) not supported
UIA3 : (0) not supported
UIA4 : (0) not supported
UIA5 : (0) not supported
UIA6 : (0) not supported
UIA7 : (0) not supported
SpareArray :
NASMessageContainer
Protocol discriminator : 2 (ESM)
MessageType : PDN Connectivity Request
Message Contents : 02 0C D0 11 D1 27 1A 80 80 21 10 01 00 00 10 81 06 00 00 00 00 83 06 00 00 00 00 00 0D 00 00 0A 00
Old P-TMSI signature
Value : 59200 (Hex 0x00E740)
Additional GUTI
Length : 11
Odd/even indication : (0) Even number of digits
Type of identity : (6) Reserved
plmn
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
MMEGroupID : 65520
MMECode : 5
M_TMSI : 4026791086
Last visited registered TAI
plmn
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
TAC : 64257
DRX parameter
Split PG cycle code : (10) Value: 10
CN Specific DRX cycle length coefficient : (0) CN Specific DRX cycle length coefficient not specified
Split on CCCH : (0) Split pg cycle on CCCH is not supported by the MS.
Non-DRX timer : (2) Max 2 sec non-DRX mode after transfer state.
MS Network Capability
GEA/1 : (1) Encryption algorithm GEA/1 available
SM capabilities via dedicated channels : (1) MS supports mobile terminated point to point SMS via dedicated signalling channels.
SM capabilities via GPRS channels : (1) MS supports mobile terminated point to point SMS via GPRS packet data channels.
UCS2 support : (0) The ME has a preference for the default alphabet (defined in GSM 03.38) over UCS2.
SS Screening Indicator : 1, Defined in 24.080
SoLSA Capability : (0) The ME does not support SoLSA.
Revision level indicator : (1) The ME is Release '99 onwards
PFC feature mode : (1) Mobile station does support BSS packet flow procedures
Extended GEA bits
GEA/2 : (1) Encryption algorithm GEA/2 available
GEA/3 : (1) Encryption algorithm GEA/3 available
GEA/4 : (0) Encryption algorithm GEA/4 not available
GEA/5 : (0) Encryption algorithm GEA/5 not available
GEA/6 : (0) Encryption algorithm GEA/6 not available
GEA/7 : (0) Encryption algorithm GEA/7 not available
LCS VA capability : (0) Location request notification via PS domain not supported
PS inter-RAT HO to UTRAN Iu mode capability : (0) PS inter-RAT HO to UTRAN Iu mode not supported
Old LAI
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
Location area code (LAC) : 9500 (Hex 0x251C)
Mobile Station Classmark 2
Revision level : (2) Mobile station supporting R99 or later versions of the protocol
ES IND : (1) "Controlled Early Classmark Sending" option is implemented in the MS
A5/1 : (0) Encryption algorithm A5/1 available
RF Power Capability : (3) class 4
PS capability (pseudo-synchronization capability) : (1) PS capability present
SS Screening Indicator (defined in TS 24.080) : 1
SM capability (MT SMS pt to pt capability) : (1) Mobile station supports mobile terminated point to point SMS
VBS notification reception : (0) No VBS capability or no notifications wanted
VGCS notification reception : (0) No VGCS capability or no notifications wanted
FC Frequency Capability : (1) (GSM900 only:) The MS supports E-GSM or R-GSM
CM3 : (1) The MS supports options that are indicated in classmark 3 IE
LCS VA capability : (1) LCS value added location request notification capability supported
UCS2 : (0) The ME has a preference for the default alphabet (defined in GSM 03.38) over UCS2.
SoLSA : (0) The ME does not support SoLSA.
CMSP: CM Service Prompt : (1) "Network initiated MO CM connection request" supported for at least one CM protocol.
A5/3 : (1) Encryption algorithm A5/3 available
A5/2 : (0) Encryption algorithm A5/2 not available

RRC Connection Release (DL-DCCH) Time : 11:41:40.821 Vendor Header Length : 27 Log Code (Hex) : 0xB0C0 HW Timestamp : (70928246.25 ms) 1...

RRC Connection Release

RRC Connection Release (DL-DCCH)

Time : 11:41:40.821
Vendor Header
Length : 27
Log Code (Hex) : 0xB0C0
HW Timestamp : (70928246.25 ms) 19:42:08.246
1.25 ms fraction : 0.00
CFN : 68
1.25 ms counter : 805512102597
RRC Signaling Header
Log Packet Version : 2
RRC Release Number : 9.3.0
Radio Bearer Id : 1
Physical Cell Id : 270
E-ARFCN : 5780
System Frame Number
System frame number : N/A
Sub frame number : N/A
Message Type : DcchDownlink
Message Length : 2
rrc-TransactionIdentifier : 0
criticalExtensions : c1
c1 : rrcConnectionRelease-r8
rrcConnectionRelease-r8
releaseCause : other

Tracking Area Update Reject Time : 11:41:40.290 Vendor Header Length : 19 Log Code (Hex) : 0xB0EC HW Timestamp : (70927743.75 ms) 19:4...

Tracking Area Update Reject

Tracking Area Update Reject

Time : 11:41:40.290
Vendor Header
Length : 19
Log Code (Hex) : 0xB0EC
HW Timestamp : (70927743.75 ms) 19:42:07.744
1.25 ms fraction : 0.00
CFN : 96
1.25 ms counter : 805512102195
Protocol discriminator : (7) EPS mobility management messages
Security Header Type : 0
Message type : 75
EMM Cause
Value : (10) Implicitly detached

Security Mode Complete Time : 11:41:40.259 Vendor Header Length : 35 Log Code (Hex) : 0xB0ED HW Timestamp : (70927635.00 ms) 19:42:07....

Security Mode Complete

Security Mode Complete

Time : 11:41:40.259
Vendor Header
Length : 35
Log Code (Hex) : 0xB0ED
HW Timestamp : (70927635.00 ms) 19:42:07.635
1.25 ms fraction : 0.00
CFN : 16
1.25 ms counter : 805512102108
Protocol discriminator : (7) EPS mobility management messages
Security Header Type : 0
Message type : 94
Mobile identity
Odd/even indication : (0) Even number of digits
Type of identity : (3) IMEISV
Identity digits (BCD) : 3562980400435303

Security Mode Command Time : 11:41:40.259 Vendor Header Length : 27 Log Code (Hex) : 0xB0EC HW Timestamp : (70927633.75 ms) 19:42:07.6...

Security Mode Command

Security Mode Command

Time : 11:41:40.259
Vendor Header
Length : 27
Log Code (Hex) : 0xB0EC
HW Timestamp : (70927633.75 ms) 19:42:07.634
1.25 ms fraction : 0.00
CFN : 36
1.25 ms counter : 805512102107
Protocol discriminator : (7) EPS mobility management messages
Security Header Type : 0
Message type : 93
Selected NAS security algorithms
Type Of Ciphering Algorithm : (2) EPS encryption algorithm 128-EEA2
Type Of Integrity Protection Algorithm : (2) EPS integrity algorithm 128-EIA2
NAS Key Set Identifier
TSC : (0) native security context
Key : 0
UE Network Capability
Length : 5
128EEA0 : (1) supported
128EEA1 : (1) supported
128EEA2 : (1) supported
EEA3 : (0) not supported
EEA4 : (0) not supported
EEA5 : (0) not supported
EEA6 : (0) not supported
EEA7 : (0) not supported
128EIA1 : (1) supported
128EIA2 : (1) supported
EIA3 : (0) not supported
EIA4 : (0) not supported
EIA5 : (0) not supported
EIA6 : (0) not supported
EIA7 : (0) not supported
UEA0 : (1) supported
UEA1 : (1) supported
UEA2 : (0) not supported
UEA3 : (0) not supported
UEA4 : (0) not supported
UEA5 : (0) not supported
UEA6 : (0) not supported
UEA7 : 0
UIA1 : (1) supported
UIA2 : (0) not supported
UIA3 : (0) not supported
UIA4 : (0) not supported
UIA5 : (0) not supported
UIA6 : (0) not supported
UIA7 : (0) not supported
GEA1 : (1) supported
GEA2 : (1) supported
GEA3 : (1) supported
GEA4 : (0) not supported
GEA5 : (0) not supported
GEA6 : (0) not supported
GEA7 : (0) not supported
IMEISV request
IMEISV request value : (1) IMEISV requested

UL Information Transfer (UL-DCCH) Time : 11:41:40.087 Vendor Header Length : 45 Log Code (Hex) : 0xB0C0 HW Timestamp : (70927558.75 ms...

UL Information Transfer

UL Information Transfer (UL-DCCH)

Time : 11:41:40.087
Vendor Header
Length : 45
Log Code (Hex) : 0xB0C0
HW Timestamp : (70927558.75 ms) 19:42:07.559
1.25 ms fraction : 0.00
CFN : 148
1.25 ms counter : 805512102047
RRC Signaling Header
Log Packet Version : 2
RRC Release Number : 9.3.0
Radio Bearer Id : 1
Physical Cell Id : 270
E-ARFCN : 5780
System Frame Number
System frame number : N/A
Sub frame number : N/A
Message Type : DcchUplink
Message Length : 20
criticalExtensions : c1
c1 : ulInformationTransfer-r8
ulInformationTransfer-r8
dedicatedInfoType : dedicatedInfoNAS
dedicatedInfoNAS
Protocol discriminator : 7 (EMM)
MessageType : Authentication Response
Message Contents : 17 E5 60 83 93 06 07 53 08 E0 18 12 00 A9 08 FB CB

Authentication Response Time : 11:41:40.087 Vendor Header Length : 33 Log Code (Hex) : 0xB0ED HW Timestamp : (70927558.75 ms) 19:42:07...

Authentication Response

Authentication Response

Time : 11:41:40.087
Vendor Header
Length : 33
Log Code (Hex) : 0xB0ED
HW Timestamp : (70927558.75 ms) 19:42:07.559
1.25 ms fraction : 0.00
CFN : 68
1.25 ms counter : 805512102047
Protocol discriminator : (7) EPS mobility management messages
Security Header Type : 0
Message type : 83
Authentication Response Parameter
Length : 8
RESArray :
[0 ] : 224
[1 ] : 24
[2 ] : 18
[3 ] : 0
[4 ] : 169
[5 ] : 8
[6 ] : 251
[7 ] : 203

Authentication Request Time : 11:41:40.072 Vendor Header Length : 52 Log Code (Hex) : 0xB0EC HW Timestamp : (70927500.00 ms) 19:42:07....

Authentication Request

Authentication Request

Time : 11:41:40.072
Vendor Header
Length : 52
Log Code (Hex) : 0xB0EC
HW Timestamp : (70927500.00 ms) 19:42:07.500
1.25 ms fraction : 0.00
CFN : 0
1.25 ms counter : 805512102000
Protocol discriminator : (7) EPS mobility management messages
Security Header Type : 0
Message type : 82
NAS Key Set Identifier
TSC : (0) native security context
Key : 0
Authentication parameter RAND
Rand value (Hex) :
[0 ] : 0x3A
[1 ] : 0x6A
[2 ] : 0x41
[3 ] : 0x84
[4 ] : 0xBC
[5 ] : 0xD9
[6 ] : 0x15
[7 ] : 0xD9
[8 ] : 0xBD
[9 ] : 0x55
[10] : 0x61
[11] : 0xFB
[12] : 0xE3
[13] : 0xD6
[14] : 0x81
[15] : 0x03
Authentication parameter AUTN
AUTN (Hex) :
[0 ] : 0xDD
[1 ] : 0x66
[2 ] : 0x80
[3 ] : 0x39
[4 ] : 0xE6
[5 ] : 0x3C
[6 ] : 0x80
[7 ] : 0x01
[8 ] : 0x44
[9 ] : 0xB7
[10] : 0xEC
[11] : 0xF3
[12] : 0xC5
[13] : 0xF3
[14] : 0xFC
[15] : 0x4C

DL Information Transfer (DL-DCCH) Time : 11:41:40.072 Vendor Header Length : 64 Log Code (Hex) : 0xB0C0 HW Timestamp : (70927498.75 m...

DL Information Transfer

DL Information Transfer (DL-DCCH)

Time : 11:41:40.072
Vendor Header
Length : 64
Log Code (Hex) : 0xB0C0
HW Timestamp : (70927498.75 ms) 19:42:07.499
1.25 ms fraction : 0.00
CFN : 140
1.25 ms counter : 805512101999
RRC Signaling Header
Log Packet Version : 2
RRC Release Number : 9.3.0
Radio Bearer Id : 1
Physical Cell Id : 270
E-ARFCN : 5780
System Frame Number
System frame number : N/A
Sub frame number : N/A
Message Type : DcchDownlink
Message Length : 39
rrc-TransactionIdentifier : 0
criticalExtensions : c1
c1 : dlInformationTransfer-r8
dlInformationTransfer-r8
dedicatedInfoType : dedicatedInfoNAS
dedicatedInfoNAS
Protocol discriminator : 7 (EMM)
MessageType : Authentication Request
Message Contents : 07 52 00 3A 6A 41 84 BC D9 15 D9 BD 55 61 FB E3 D6 81 03 10 DD 66 80 39 E6 3C 80 01 44 B7 EC F3 C5 F3 FC 4C

RRC Connection Setup Complete (UL-DCCH) Time : 11:41:40.056 Vendor Header Length : 108 Log Code (Hex) : 0xB0C0 HW Timestamp : (70927347....

RRC Connection Setup Complete

RRC Connection Setup Complete (UL-DCCH)

Time : 11:41:40.056
Vendor Header
Length : 108
Log Code (Hex) : 0xB0C0
HW Timestamp : (70927347.50 ms) 19:42:07.348
1.25 ms fraction : 0.00
CFN : 88
1.25 ms counter : 805512101878
RRC Signaling Header
Log Packet Version : 2
RRC Release Number : 9.3.0
Radio Bearer Id : 1
Physical Cell Id : 270
E-ARFCN : 5780
System Frame Number
System frame number : N/A
Sub frame number : N/A
Message Type : DcchUplink
Message Length : 83
rrc-TransactionIdentifier : 0
criticalExtensions : c1
c1 : rrcConnectionSetupComplete-r8
rrcConnectionSetupComplete-r8
selectedPLMN-Identity : 1
dedicatedInfoNAS
Protocol discriminator : 7 (EMM)
MessageType : Tracking Area Update Request
Message Contents : 17 1C E2 82 0F 05 07 48 02 0B F6 13 00 89 25 1C 02 E0 01 F4 31 80 19 00 E7 40 50 0B F6 13 00 89 FF F0 05 F0 03 F4 AE 55 A5 FA 46 16 58 04 E0 E0 C0 40 52 13 00 89 FB 01 5C 0A 02 A1 57 02 20 00 31 03 E5 E0 24 13 13 00 89 25 1C 11 03 53 59 A6

RRC Connection Setup (DL-CCCH) Time : 11:41:40.056 Vendor Header Length : 51 Log Code (Hex) : 0xB0C0 HW Timestamp : (70927345.00 ms) 19:...

RRC Connection Setup

RRC Connection Setup (DL-CCCH)

Time : 11:41:40.056
Vendor Header
Length : 51
Log Code (Hex) : 0xB0C0
HW Timestamp : (70927345.00 ms) 19:42:07.345
1.25 ms fraction : 0.00
CFN : 92
1.25 ms counter : 805512101876
RRC Signaling Header
Log Packet Version : 2
RRC Release Number : 9.3.0
Radio Bearer Id : 0
Physical Cell Id : 270
E-ARFCN : 5780
System Frame Number
System frame number : N/A
Sub frame number : N/A
Message Type : CcchDownlink
Message Length : 26
rrc-TransactionIdentifier : 0
criticalExtensions : c1
c1 : rrcConnectionSetup-r8
rrcConnectionSetup-r8
radioResourceConfigDedicated
srb-ToAddModList
SRB-ToAddModList :
[0 ] :
srb-Identity : 1
rlc-Config : explicitValue
explicitValue
RLC-Config : am
ul-AM-RLC
t-PollRetransmit : ms45
pollPDU : pInfinity
pollByte : kBinfinity
maxRetxThreshold : t32
dl-AM-RLC
t-Reordering : ms35
t-StatusProhibit : ms0
logicalChannelConfig : explicitValue
explicitValue
priority : 1
prioritisedBitRate : infinity
bucketSizeDuration : ms50
logicalChannelGroup : 0
mac-MainConfig : explicitValue
explicitValue
maxHARQ-Tx : n4
periodicBSR-Timer : sf5
retxBSR-Timer : sf320
ttiBundling : False
timeAlignmentTimerDedicated : sf5120
phr-Config : setup
periodicPHR-Timer : sf200
prohibitPHR-Timer : sf200
dl-PathlossChange : dB3
physicalConfigDedicated
pdsch-ConfigDedicated
p-a : dB-3
pusch-ConfigDedicated
betaOffset-ACK-Index : 10
betaOffset-RI-Index : 9
betaOffset-CQI-Index : 10
cqi-ReportConfig
cqi-ReportModeAperiodic : rm30
nomPDSCH-RS-EPRE-Offset : 0
cqi-ReportPeriodic
CQI-ReportPeriodic : setup
cqi-PUCCH-ResourceIndex : 0
cqi-pmi-ConfigIndex : 37
cqi-FormatIndicatorPeriodic : widebandCQI
ri-ConfigIndex : 322
simultaneousAckNackAndCQI : False
antennaInfo : explicitValue
explicitValue
transmissionMode : tm3
codebookSubsetRestriction : n2TxAntenna-tm3
n2TxAntenna-tm3 : 11
[0 ] : 1
[1 ] : 1
ue-TransmitAntennaSelection : release
schedulingRequestConfig
SchedulingRequestConfig : setup
sr-PUCCH-ResourceIndex : 0
sr-ConfigIndex : 14
dsr-TransMax : n64

RRC Connection Request (UL-CCCH) Time : 11:41:39.869 Vendor Header Length : 31 Log Code (Hex) : 0xB0C0 HW Timestamp : (70927302.50 ms) 1...

RRC Connection Request

RRC Connection Request (UL-CCCH)

Time : 11:41:39.869
Vendor Header
Length : 31
Log Code (Hex) : 0xB0C0
HW Timestamp : (70927302.50 ms) 19:42:07.302
1.25 ms fraction : 0.00
CFN : 184
1.25 ms counter : 805512101842
RRC Signaling Header
Log Packet Version : 2
RRC Release Number : 9.3.0
Radio Bearer Id : 0
Physical Cell Id : 270
E-ARFCN : 5780
System Frame Number
System frame number : N/A
Sub frame number : N/A
Message Type : CcchUplink
Message Length : 6
criticalExtensions : rrcConnectionRequest-r8
rrcConnectionRequest-r8
ue-Identity
InitialUE-Identity : s-TMSI
s-TMSI
mmec
mmec : (0x5) : 5
m-TMSI : (0xF003F4AE) : 4026791086
establishmentCause : mo-Signalling
spare : 0
[0 ] : 0

Tracking Area Update Request Time : 11:41:39.869 Vendor Header Length : 96 Log Code (Hex) : 0xB0ED HW Timestamp : (70927302.50 ms) 19:...

Tracking Area Update Request

Tracking Area Update Request

Time : 11:41:39.869
Vendor Header
Length : 96
Log Code (Hex) : 0xB0ED
HW Timestamp : (70927302.50 ms) 19:42:07.302
1.25 ms fraction : 0.00
CFN : 100
1.25 ms counter : 805512101842
Protocol discriminator : (7) EPS mobility management messages
Security Header Type : 0
Message type : 72
NAS Key Set Identifier
TSC : (0) native security context
Key : 0
EPS Update Type
Active Flag : (0) No bearer establishment requested
EPS update type Value : (2) combined TA/LA updating with IMSI attach
GUTI
Length : 11
Odd/even indication : (0) Even number of digits
Type of identity : (6) Reserved
plmn
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
MMEGroupID : 9500
MMECode : 2
M_TMSI : 3758224433
Ciphering key sequence number
Key sequence : (0) 0
P-TMSI signature
Value : 59200 (Hex 0x00E740)
GUTI
Length : 11
Odd/even indication : (0) Even number of digits
Type of identity : (6) Reserved
plmn
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
MMEGroupID : 65520
MMECode : 5
M_TMSI : 4026791086
NonceUE
NonceValue : 2784642582
UE Network Capability
Length : 4
128EEA0 : (1) supported
128EEA1 : (1) supported
128EEA2 : (1) supported
EEA3 : (0) not supported
EEA4 : (0) not supported
EEA5 : (0) not supported
EEA6 : (0) not supported
EEA7 : (0) not supported
128EIA1 : (1) supported
128EIA2 : (1) supported
EIA3 : (0) not supported
EIA4 : (0) not supported
EIA5 : (0) not supported
EIA6 : (0) not supported
EIA7 : (0) not supported
UEA0 : (1) supported
UEA1 : (1) supported
UEA2 : (0) not supported
UEA3 : (0) not supported
UEA4 : (0) not supported
UEA5 : (0) not supported
UEA6 : (0) not supported
UEA7 : 0
UCS2 : The UE has a preference for the default alphabet (defined in 3GPP TS 23.038 [3]) over UCS2 (see ISO/IEC 10646 [29]).
UIA1 : (1) supported
UIA2 : (0) not supported
UIA3 : (0) not supported
UIA4 : (0) not supported
UIA5 : (0) not supported
UIA6 : (0) not supported
UIA7 : (0) not supported
SpareArray :
TrackingAreaIdentity
plmn
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
TAC : 64257
DRX parameter
Split PG cycle code : (10) Value: 10
CN Specific DRX cycle length coefficient : (0) CN Specific DRX cycle length coefficient not specified
Split on CCCH : (0) Split pg cycle on CCCH is not supported by the MS.
Non-DRX timer : (2) Max 2 sec non-DRX mode after transfer state.
UE Radio Capability Information Update Needed
spare : 0
URC upd : (1) UE radio capability information update needed
EPS Bearer Context Status
EBI5 : Active
EBI6 : Inactive
EBI7 : Inactive
EBI8 : Inactive
EBI9 : Inactive
EBI10 : Inactive
EBI11 : Inactive
EBI12 : Inactive
EBI13 : Inactive
EBI14 : Inactive
EBI15 : Inactive
MS Network Capability
GEA/1 : (1) Encryption algorithm GEA/1 available
SM capabilities via dedicated channels : (1) MS supports mobile terminated point to point SMS via dedicated signalling channels.
SM capabilities via GPRS channels : (1) MS supports mobile terminated point to point SMS via GPRS packet data channels.
UCS2 support : (0) The ME has a preference for the default alphabet (defined in GSM 03.38) over UCS2.
SS Screening Indicator : 1, Defined in 24.080
SoLSA Capability : (0) The ME does not support SoLSA.
Revision level indicator : (1) The ME is Release '99 onwards
PFC feature mode : (1) Mobile station does support BSS packet flow procedures
Extended GEA bits
GEA/2 : (1) Encryption algorithm GEA/2 available
GEA/3 : (1) Encryption algorithm GEA/3 available
GEA/4 : (0) Encryption algorithm GEA/4 not available
GEA/5 : (0) Encryption algorithm GEA/5 not available
GEA/6 : (0) Encryption algorithm GEA/6 not available
GEA/7 : (0) Encryption algorithm GEA/7 not available
LCS VA capability : (0) Location request notification via PS domain not supported
PS inter-RAT HO to UTRAN Iu mode capability : (0) PS inter-RAT HO to UTRAN Iu mode not supported
Location Area Identification
Mobile country code (MCC) : 310
Mobile network code (MNC) : 980
Location area code (LAC) : 9500 (Hex 0x251C)
Mobile Station Classmark 2
Revision level : (2) Mobile station supporting R99 or later versions of the protocol
ES IND : (1) "Controlled Early Classmark Sending" option is implemented in the MS
A5/1 : (0) Encryption algorithm A5/1 available
RF Power Capability : (3) class 4
PS capability (pseudo-synchronization capability) : (1) PS capability present
SS Screening Indicator (defined in TS 24.080) : 1
SM capability (MT SMS pt to pt capability) : (1) Mobile station supports mobile terminated point to point SMS
VBS notification reception : (0) No VBS capability or no notifications wanted
VGCS notification reception : (0) No VGCS capability or no notifications wanted
FC Frequency Capability : (1) (GSM900 only:) The MS supports E-GSM or R-GSM
CM3 : (1) The MS supports options that are indicated in classmark 3 IE
LCS VA capability : (1) LCS value added location request notification capability supported
UCS2 : (0) The ME has a preference for the default alphabet (defined in GSM 03.38) over UCS2.
SoLSA : (0) The ME does not support SoLSA.
CMSP: CM Service Prompt : (1) "Network initiated MO CM connection request" supported for at least one CM protocol.
A5/3 : (1) Encryption algorithm A5/3 available
A5/2 : (0) Encryption algorithm A5/2 not available

System Information Block Type1 (DL-BCCH-SCH) Time : 11:41:39.853 Vendor Header Length : 47 Log Code (Hex) : 0xB0C0 HW Timestamp : (709272...

System Information Block Type1 (DL-BCCH-SCH)

System Information Block Type1 (DL-BCCH-SCH)

Time : 11:41:39.853
Vendor Header
Length : 47
Log Code (Hex) : 0xB0C0
HW Timestamp : (70927288.75 ms) 19:42:07.289
1.25 ms fraction : 0.00
CFN : 104
1.25 ms counter : 805512101831
RRC Signaling Header
Log Packet Version : 2
RRC Release Number : 9.3.0
Radio Bearer Id : 0
Physical Cell Id : 270
E-ARFCN : 5780
System Frame Number
System frame number : N/A
Sub frame number : N/A
Message Type : BcchSchDownlink
Message Length : 22
plmn-IdentityList
PLMN-IdentityList :
[0 ] :
plmn-Identity
mcc
MCC :
[0 ] : 3
[1 ] : 1
[2 ] : 0
mnc
MNC :
[0 ] : 9
[1 ] : 8
[2 ] : 0
cellReservedForOperatorUse : notReserved
trackingAreaCode : 64257 (0xFB01)
cellIdentity : 256000346 (0xF42415A)
cellBarred : notBarred
intraFreqReselection : allowed
csg-Indication : False
q-RxLevMin : -60
p-Max : 23
freqBandIndicator : 17
schedulingInfoList
SchedulingInfoList :
[0 ] :
si-Periodicity : rf8
sib-MappingInfo
SIB-MappingInfo :
[0 ] :
extensionBit0 : 0
item : sibType3
[1 ] :
si-Periodicity : rf64
sib-MappingInfo
SIB-MappingInfo :
[0 ] :
extensionBit0 : 0
item : sibType5
[2 ] :
si-Periodicity : rf64
sib-MappingInfo
SIB-MappingInfo :
[0 ] :
extensionBit0 : 0
item : sibType6
[3 ] :
si-Periodicity : rf64
sib-MappingInfo
SIB-MappingInfo :
[0 ] :
extensionBit0 : 0
item : sibType7
si-WindowLength : ms10
systemInfoValueTag : 0

What is RB or Resource Block? A Resource Block (RB) is a time- and frequency resource that occupies 12 subcarriers (12x15 kHz = 180 kHz) and...

What is a resource block

What is RB or Resource Block?

A Resource Block (RB) is a time- and frequency resource
that occupies 12 subcarriers (12x15 kHz = 180 kHz) and one slot (=0.5 ms).

RBs are allocated in pairs by the scheduler (then referred to as Scheduling Blocks).

Each OFDM symbol contains, if 64-QAM is used, 6 bits per subcarrier (15kHz). There are, if normal CP is used, 7 OFDM symbols per slot. This ...

Calculate the maximum theoretical physical peak data rate in LTE radio interface

Each OFDM symbol contains, if 64-QAM is used, 6 bits per subcarrier (15kHz). There are, if normal CP is used, 7 OFDM symbols per slot. This ends up with 6*7 = 42 bits per slot.

One slot is 0.5 ms which gives us 42/0.5ms = 84kbps per sub-carrier.
If the full bandwidth, 20MHz, is used, there are
20MHz/15kHz=1333 sub-carriers.

However, only 1200 of these are used for user data. This
corresponds to 100 resource blocks.

1200*84kbps = 100,8 Mbps.
With four MIMO layers, we should be able to achieve 403,2 Mbps
of raw data rate in the physical layer.
What about the user data rate? The data rates used for L1/L2
signaling, reference signals, PBCH, SCH, layer 3 signaling and protocol headers has to be subtracted from this figure.

Then we end up with approximately 320 Mbps of user data rate on RLC level??
In UL we have approximately the same calculation, except that the gain from MIMO cannot be included, since no SU-MIMO is used in UL. Hence, approximately 80-100 Mbps of theoretical bitrate should be possible to reach.

Self-Healing Self-healing is a function that mitigates the faults automatically by triggering appropriate recovery actions. From the point o...

LTE SON on Self-Healing

Self-Healing

Self-healing is a function that mitigates the faults automatically by triggering appropriate recovery
actions.

From the point of view of fault management, for each detected fault appropriate alarms are be generated by the faulty network entity, regardless of whether it is an automatically detected and automatically cleared fault, or an automatically detected and manually cleared fault.

The self-healing functionality monitors the alarms, and gathers necessary correlated information (e.g. measurements, testing result, etc.) and does deep analysis, and triggers appropriate recovery actions to solve the fault.

It also monitors the execution of the recovery actions and decides the next step accordingly. When self-healing iteration ends, the self-healing functionality generates
appropriate notifications to inform the Integration Reference Point (IRP) Manager of all the changes
performed.

This concludes the section on the new radio access network for LTE, and the following chapters cover the new Core Network entities required to support this new technology.

Self-Optimization Based on the actual location of equipment, the optimization of the initial neighbour list is required, (e.g. radio measu...

LTE SON on Self-Optimization

Self-Optimization

Based on the actual location of equipment, the optimization of the initial neighbour list is required,
(e.g. radio measurements of eNodeBs are required to solve the call drops or handover problems).

For this approach, RRC connections and their accompanying measurements can be used to gather
the needed information about their neighbours.

Known neighbours can be checked if they are really
appropriate concerning real RF conditions; new ones can be included based on information about detected cells in the UEs. Neighbour related parameters include:

Location of the neighbours (distance)

UE measurement reporting or eNodeB radio scanning for neighbours

Field strength information

Event measurements such as cell specific call drops or handover failures

Network Management System(EMS)/Element Management

System(NMS) configuration data

Planning tool data

Self-Configuration Self-configuration is the process that is executed automatically after the physical installation of the eNB. An IP addres...

LTE SON on Self-Configuration

Self-Configuration

Self-configuration is the process that is executed automatically after the physical installation of the
eNB.

An IP address is allocated to the new eNB.

The eNB connects to the OAM system for authentication, software download and configuration data download. The initial radio configuration and transport parameters configuration are completed, and the software is downloaded into the eNB.

The eNB connects to the OAM system for configuration data or normal network management.

The S1-links and X2-links are established and dependent nodes such as MMEs and eNBs are updated with new configuration data.

The inventory system in the OAM is informed that a new eNB is ready to perform the next required operation.

LTE MIMO MIMO, (Multiple-input and Multiple-output), refers to the use of multiple antennas at both the transmitter and receiver to improve ...

What is MIMO in LTE

LTE MIMO

MIMO, (Multiple-input and Multiple-output), refers to the use of multiple antennas at both the
transmitter and receiver to improve communication performance. It is one of several forms of smart
antenna technology.

MIMO offers significant increases in data throughput and link range without additional bandwidth or
transmit power. This is achieved due to a higher spectral efficiency, (more bits per second per hertz
of bandwidth), and link reliability or diversity (reduced fading).

LTE supports Multi-Mode Adaptive MIMO for Downlink and Uplink, which accommodates both higher
data rate and wider coverage:

Single User MIMO for peak user data rate improvement.

Multi User MIMO for average data rate enhancement.

Collaborative/Network MIMO for cell edge user data rate boost.

Self Organizing Network - SON SON in LTE SON is a certain set of features defined as use cases in 3GPP and applied for LTE. The feature sets...

What is SON

Self Organizing Network - SON

SON in LTE

SON is a certain set of features defined as use cases in 3GPP and applied for LTE.

The feature sets, dependent on 3GPP releases (e.g. 8 or 9) are expected to benefit Operators by transforming possible network management operations into automatic executable software procedures, hence resulting in substantial savings in OPEX.

Automation is not a new concept for wireless networks, although with LTE this will prove to be more efficient, enabling the extensive use of automated processes. Thus, the appearance of SON algorithms represents a continuation of the natural evolution of wireless networks, where automated processes are simply extending their scope deeper
into the network.

SON features are distributed to eNB and EPC, and include Self Configuration, Self Optimization and
Self Healing features.

LTE stands for Long Term Evolution.LTE is a standard for 4th generation (4G) mobile broadband which is aimed to be the successor to the 3...

What is LTE

LTE stands for Long Term Evolution.LTE is a standard for 4th generation (4G) mobile broadband which is aimed to be the successor to the 3G technologies GSM/UMTS.

LTE is already implemented in many countries but still in the early stage.

LTE is also considered the competitor to WiMAX.

LTE promises to provide theoretical peak download rates of up 100Mbps (rates with varies based on environment etc) and peak upload rates of up to 50Mbps.

LTE is a better technology than wimax becauste LTE will make people free from the burden of having to find a WiFi hotspot (Wimax) when they are on the road.

As long as you have an LTE modem, LTE subscribers can connect to the internet anywhere in the service provider's coverage area!

LTE User Equipment UE Cateogory

LTE User Equipment Categories

LTE User Equipment UE Cateogory



Introduction to LTE n Broadband access with LTE n Architecture terminology n LTE development and design goals n LTE standards developmen...

LTE Training Course

Introduction to LTE
n Broadband access with LTE
n Architecture terminology
n LTE development and design goals
n LTE standards development
n LTE key technologies
n Access networks and the eNB (evolved Node B)
n X2 interface
n The EPC (Evolved Packet Core)
n S1 interface
n Evolved packet core ‘S’ interfaces
n Data rates and services
n E-UTRA protocols


UE Bearers and Connectivity
n The EPS as an IP-CAN
n EPS bearer QoS class identifiers
n Allocation and retention priority (ARP)
n QoS levels
n EPS bearer composition and establishment
n EPS area and subscriber identities
n LTE state management and EPS service concepts
n EPS initial attach and IMS registration
n Tracking area update and paging
n Service requests
n IMS connection establishment
n CS fallback call setup
n CS service provision via a GANC
n S1 interfaces for HeNBs (Home eNB)


OFDM Principles
n Defining radio carrier orthogonality
n Resilience to time dispersion and multipath fading
n Principles of QAM
n The Fourier Transform
n The OFDM transmitter and receiver
n The cyclic prefix
n Scalability in OFDM
n OFDMA resource allocation strategies
n Channel adaptation and Turbo coding
n OFDM peak to average power ratio
n SC-FDMA principles of operation
n MIMO concept and benefits
n Multi-user MIMO


Physical Layer Structure
n Channel bandwidths and subcarriers
n Frequency bands and radio channel organization
n OFDMA parameter summary
n Modulation and error protection
n Physical channels
n The physical layer timing unit
n Type 1 and Type 2 frame structure
n Resource blocks
n Downlink cell and UE-specific reference signals
n Uplink demodulation reference signals
n Uplink sounding reference signals
n Synchronization signals
n PBCH transmission
n Downlink control channels and resources
n Resource allocation options
n PUCCH resource allocation
n Resource allocation for PUSCH and PRACH


Layer 2 Protocols
n L2/L1 channel mapping
n PDCP architecture and PDU formats
n PDCP sequence numbers in handover
n PDCP message integrity protection
n PDCP ciphering
n RLC general functions and modes
n RLC UM and AM frame structures
n RLC retransmission and resegmentation
n MAC general architecture and PDU structure
n Scheduling functions and prioritized bit rates
n RACH procedure for MAC
n RNTI types
n Downlink HARQ principles and operation
n Management of DRX for connected mode


Radio Resource Control
n RRC functions and states
n RRC I-RAT state transitions
n Signalling radio bearers
n System information broadcasting and paging
n RRC connection establishment
n UE capability enquiry
n Security mode setting
n Data radio bearer establishment
n Measurement configuration
n Intra-LTE handover
n Handover from LTE (IRAT)
n NAS information transfer


Lower Layer Procedures
n Cell search procedure
n PLMN selection
n Idle mode
n Cell selection
n Cell reselection
n DRX operation
n E-UTRA radio measurements
n Measurements for RRC connected mode
n Measurement gaps
n Trigger events for E-UTRA
n Uplink power control
n Timing advance
n CQI reporting and reporting options
n MIMO options for LTE

Timer Start Stop At expiry T300 Transmission of RRCConnectionRequest Reception of RRCConnectionSetup or RRCConnectionReject messag...

LTE Timers

Timer Start Stop At expiry
T300 Transmission of RRCConnectionRequest Reception of RRCConnectionSetup or RRCConnectionReject message, cell re-selection and upon abortion of connection establishment by upper layers Perform the actions
T301 Transmission of RRCConnectionReestabilshmentRequest Reception of RRCConnectionReestablishment or RRCConnectionReestablishmentReject message as well as when the selected cell becomes unsuitable Go to RRC_IDLE
T303 Access barred while performing RRC connection establishment for mobile originating calls Upon entering RRC_CONNECTED and upon cell re-selection Inform upper layers about barring alleviation as specified
T304 Reception of RRCConnectionReconfiguration message including the MobilityControl Info or reception of MobilityFromEUTRACommand message including CellChangeOrder Criterion for successful completion of handover to EUTRA or cell change order is met (the criterion is specified in the target RAT in case of inter-RAT) In case of cell change order from E-UTRA or intra E-UTRA handover, initiate the RRC connection re-establishment procedure; In case of handover to E-UTRA, perform the actions defined in the specifications applicable for the source RAT.
T305 Access barred while performing RRC connection establishment for mobile originating signalling Upon entering RRC_CONNECTED and upon cell re-selection Inform upper layers about barring alleviation as specified
T310 Upon detecting physical layer problems i.e. upon receiving N310 consecutive out-of-sync indications from lower layers Upon receiving N311 consecutive in-sync indications from lower layers, upon triggering the handover procedure and upon initiating the connection re-establishment procedure If security is not activated: go to RRC_IDLE else: initiate the connection re-establishment procedure
T311 Upon initiating the RRC connection re-establishment procedure Selection of a suitable E-UTRA cell or a cell using another RAT. Enter RRC_IDLE
T320 Upon receiving t320 or upon cell (re)selection to E-UTRA from another RAT with validity time configured for dedicated priorities (in which case the remaining validity time is applied). Upon entering RRC_CONNECTED, when PLMN selection is performed on request by NAS, or upon cell (re)selection to another RAT (in which case the timer is carried on to the other RAT). Discard the cell reselection priority information provided by dedicated signalling.
T321 Upon receiving measConfig including a reportConfig with the purpose set to reportCGI Upon acquiring the information needed to set all fields of globalCellId for the requested cell, upon receiving measConfig that includes removal of the reportConfig with the purpose set to reportCGI Initiate the measurement reporting procedure, stop performing the related measurements and remove the corresponding measId

eNode B is the RAN node in the EPS architecture that is responsible for radio transmission to and reception from UEs in one or more cells. ...

What is the eNode B functionality


eNode B is the RAN node in the EPS architecture that is responsible for radio transmission to and reception from UEs in one or more cells.

 The eNode B is connected to EPC nodes by means of an S1 interface. The eNode B may also be connected to its neighbour eNode Bs by means of the X2 interface.

Some significant changes have been made to the eNode B functional allocation compared to UTRAN. Most Rel-6 RNC functionality has been
moved to the E-UTRAN eNode B.

Below follows a description of the functionality provided by eNode B.

Cell control and MME pool support
eNode B owns and controls the radio resources of its own cells. Cell resources are requested by and granted to MMEs in an ordered fashion. This arrangement supports the MME pooling concept. S-GW pooling is managed by the MMEs and is not really seen in the eNode B.

Mobility control
The eNode B is responsible for controlling the mobility for terminals in active state. This is done by ordering the UE to perform measurement and then performing handover when necessary.


• Control and User Plane security
The ciphering of user plane data over the radio interface is terminated in the eNode B.
Also the ciphering and integrity protection of RRC signalling is terminated in the eNode B.

Shared Channel handling
Since eNode B owns the cell resources, eNode B also handles the shared and random access channels used for signalling and initial access.

Segmentation/Concatenation 
Radio Link Control (RLC) Service Data Units (SDUs) received from the Packet Data convergence

Protocol (PDCP) layer in the AGW consist of whole IP packets may be larger than the transport block size provided by the physical layer. Thus, the RLC layer must support segmentation and concatenation to adapt the payload to the transport block size.

HARQ
A Medium Access Control (MAC) Hybrid Automatic Repeat reQuest (HARQ) layer with fast feedback provides a means for quickly correcting most errors from the radio channel. To achieve low delay and efficient use of radio resources, the HARQ operates with a native error rate which is sufficient only for services with moderate error rate requirements such as for instance VoIP. Lower error rates are achieved by letting an outer Automatic Repeat reQuest (ARQ) layer in the eNode B handle the HARQ errors.

Scheduling
A scheduler with support for the QoS model provides efficient scheduling of UP and CP data.

Multiplexing and Mapping
The eNode B performs mapping of logical channels onto transport channels.

Physical layer functionality
The eNode B handles the physical layer such as scrambling, Tx diversity, beamforming processing, and OFDM modulation. The eNode B also handles L1 functions like link adaptation and power control.

Measurements and reporting
eNode B provides functions for configuring and making measurements on the radio environment and eNode B-internal variables and conditions. The collected data is used internally for RRM but can be reported for the purpose of multi-cell RRM.

What is the functionality of the MME node ? The EPS architecture defines an MME node, which contains CN control functionality. Although...

MME node functionality


What is the functionality of the MME node ?

The EPS architecture defines an MME node, which contains CN control functionality.

Although the functionality is not entirely the same, the MME conceptually constitutes a CP SGSN node.

The CP terminal protocols terminate at the MME which also manages the mobility contexts of the UEs. The same MME remains in control of a UE as long as the UE move within an MME pool area.

Below follows descriptions of the functions performed by the MME.

The MME handles the mobility and session management functions listed below:

UE attach/detach handling - This allows UE to register/de-register to the network.

Security – AAA
The Access Gateway (AGW) implements functions for Authentication, Authorization and Accounting (AAA) to verify users’ identities and grant access to the network and track users’ activities. In addition, the MME performs ciphering and integrity protection of NAS message signalling.

EPS Bearer Handling
The MME manages the setting up, modification and tearing down of EPS Bearers. It is assumed that a UE in E-UTRAN will always have one default EPS Bearer established at the time of attachment to the network.

Mobility Anchor – IP Point of Presence
The AGW acts as a mobility anchor point which hides UE mobility from the fixed network. When a UE attaches to the network it is assigned an IP address from an AGW which then also assumes the role of mobility anchor to the UE. While the control of a UE may be transferred to another AGW because of a HO, the UEs IP Point of Presence (PoP) will remain at the mobility anchor AGW. Thus, the mobility of UEs is transparent to the fixed network.

Mobility Management for Idle Mode UEs
The MME manages mobility of idle mode UEs. Idle mode UEs are tracked with the
granularity of Tracking Area (TA).

S5/S8 - This is the interface between the S-GW and P-GW. In principle S5 and S8 is the same interface, the difference being that S8 is used...

S5/S8 Interface


S5/S8 - This is the interface between the S-GW and P-GW. In principle S5 and S8 is the same interface, the difference being that S8 is used when roaming between different operators while S5 is network internal.

The S5 / S8 interface will exist in two flavours one based on Gn/GTP (SGSN-GGSN) and the other will use the IETF specified Proxy Mobile IP (PMIP) for mobility control with additional mechanism to handle QoS.

The motivation for the PMIP flavour of S5/S8 has mainly come from WiMAX/CDMA2000 operators and vendors interested in inter-working with E-UTRAN, GERAN or UTRAN, or re-using the 3GPP EPS specified mechanism also for intra WiMAX / CDMA2000 mobility.

It has been agreed in 3GPP that the usage of PMIP or GTP on S5 and S8 should not impact RAN behaviour or impact the terminals.

The usage of PMIP or GTP on S5/S8 will not be visible over the S1 interface or in the terminal. In the non roaming case, the S-GW and P-GW functions can be performed in one physical node.

S5/S8 is a many-to-many interface.

LTE S5/S8 Interface

S10 - This is a control interface between the MMEs which will be very similar to the S3 interface between the SGSN and MME. The interface i...

S10 Interface


S10 - This is a control interface between the MMEs which will be very similar to the S3 interface between the SGSN and MME. The interface is based on Gn/GTP-C (SGSNSGSN) with additional functionality.

S10 is a many-to-many interface.

LTE S10 Interface

X2 - This is the interface between eNode Bs. The interface is mainly used to support active mode UE mobility. This interface may also be ...

X2 Interface


X2 - This is the interface between eNode Bs. The interface is mainly used to support active mode UE mobility.

This interface may also be used for multi-cell Radio Resource Management (RRM) functions. The X2-CP interface will consist of a signalling protocol called X2-AP on top of SCTP.

The X2-UP interface is based on GTP-U.

The X2-UP interface will be used to support loss-less mobility (packet forwarding).

The X2 interface is a many-to-many interface.

LTE X2 Interface

S11 - This is the interface between the MME and S-GW. The interface is based on Gn/GTP-Control (GTP-C) (interface between SGSN-GGSN) with s...

S11 Interface


S11 - This is the interface between the MME and S-GW. The interface is based on Gn/GTP-Control (GTP-C) (interface between SGSN-GGSN) with some additional functions for paging coordination, mobility compared to the legacy Gn/GTP-C (SGSN-GGSN) interface.

S11 is a many-to-many interface.

LTE S11 Interface

S4 - This is the interface between the P-GW and 2G/3G SGSNs. The interface is based on Gn/GTP (SGSN-GGSN). The user plane interface is base...

S4 Interface


S4 - This is the interface between the P-GW and 2G/3G SGSNs. The interface is based on Gn/GTP (SGSN-GGSN). The user plane interface is based on GTP-U (same as S1-UP and Iu-UP) and the control plane is based on GTP-C (similar to S11).

S4 is a many-to-many interface and is backwards compatible with the Gn interface.

S3 - This is a control interface between the MME and 2G/3G SGSNs. The interface is based on Gn/GTP-C (SGSN-SGSN), possibly with some new fu...

S3 Interface


S3 - This is a control interface between the MME and 2G/3G SGSNs. The interface is based on Gn/GTP-C (SGSN-SGSN), possibly with some new functionality to support signalling free idle mode mobility between E-UTRAN and UTRAN/GERAN.

S3 will not support packet forwarding; instead this will be supported on the S4 interface.

S3 is a many-to-many interface and is backwards compatible with the Gn interface.

The S3 interface will be similar to the S10 interface between MMEs which will be used for intra-LTE mobility between two MME pool areas.

LTE S3 Interface

S1 - This is the interface between eNode Bs and MME and S-GW. In the user plane this interface will be based on GTP User Data Tunnelling (G...

S1 Interface


S1 - This is the interface between eNode Bs and MME and S-GW. In the user plane this interface will be based on GTP User Data Tunnelling (GTP-U) (similar to today’s Iu and Gn interface).

In the control plane, the interface is more similar to Radio Access Network Application Part (RANAP), with some simplifications and changes due to the different functional split and mobility within EPS.

It has been agreed to split the S1 interface into a S1-CP (control) and S1-UP part (user plane). The signalling transport on S1-CP will be based on SCTP. The signalling protocol for S1 is called S1-AP.

S1 is a many-to-many interface.

LTE S1 Interface

Gi - This is the interface to external packet data networks (e.g., Internet) and contains the end-user’s IP point of presence. All user- an...

Gi Interface


Gi - This is the interface to external packet data networks (e.g., Internet) and contains the end-user’s IP point of presence. All user- and control-plane functions that use the Gi interface are handled above the end-user’s IP layer. All terminal mobility within 3GPP will be handled below the Gi interface.

LTE Gi Interface

Below is a simplified picture of the EPS architecture. The EPS system is made up of the Evolved Packet Core (EPC) and the E-UTRAN. Th...

What is EPS


Below is a simplified picture of the EPS architecture.



The EPS system is made up of the Evolved Packet Core (EPC) and the E-UTRAN. The EPC provides access to external data networks (e.g., Internet, Corporate Networks) and operator services (e.g., MMS,
MBMS).

It also performs functions related to security (authentication, key agreement), subscriber information, charging and inter-access mobility (GERAN/UTRAN/E-UTRAN/ I-WLAN/CDMA2000 etc.). The CN also tracks the mobility of inactive terminals (i.e., terminals in power saving state).

E-UTRAN performs all radio related functions for active terminals (i.e. terminals sending data).

Between the EPC and E-UTRAN there is an interface called S1.

An E-UTRA capable terminal is connected directly to E-UTRAN. However some parts of  the terminal control-plane protocol stack is also terminated in the EPC.

The transmission of an Internet Protocol (IP) packet with 0 byte payload should experience a one-way UP latency of less than 5 ms. For FDD ...

What is User Plane Latency


The transmission of an Internet Protocol (IP) packet with 0 byte payload should experience a one-way UP latency of less than 5 ms. For FDD it was concluded that for a typical case with an initial Hybrid Automatic Repeat Request (HARQ) error rate of 0.3, a total average UP latency of 4ms + S1-U transfer delay can be achieved.

For TDD frame structure type 2, the requirements on UP delay can be reached for a 4- DL/3-UL configuration and no re-transmission assumed for the first transmission.

In general, the latency in TDD is larger than in FDD, because of the finite delay between the switching points. In particular, since the number of switching points per frame is limited due to efficiency reasons, the delay increases. The main contributor to the longer delay is the increased HARQ Round Trip Time (RTT).

CP latency that allows for a transition from a camped state to an active state is less than 100 ms, e.g. from MME-IDLE to MME-CONNECTED

What is Control Plane Latency


CP latency that allows for a transition from a camped state to an active state is less than
100 ms, e.g. from MME-IDLE to MME-CONNECTED

For both FDD and TDD, the DL transmission scheme is based on OFDMA. Each 10 ms radio frame is divided into 10 equally sized sub-frames. Cha...

LTE DL transmission scheme


For both FDD and TDD, the DL transmission scheme is based on OFDMA. Each 10 ms radio frame is divided into 10 equally sized sub-frames. Channel-dependent scheduling and link adaptation can operate on a sub-frame level.

Supported downlink data-modulation schemes are QPSK, 16QAM, and 64QAM.

For both FDD and TDD, the basic uplink transmission scheme is based on low-peak-toaverage power ratio (low-PAPR) single-carrier transmissio...

LTE UL Transmission scheme


For both FDD and TDD, the basic uplink transmission scheme is based on low-peak-toaverage power ratio (low-PAPR) single-carrier transmission (SC-FDMA) with cyclic prefix to achieve uplink inter-user orthogonality and to enable efficient frequency-domain equalization at the receiver side. Each 10 ms radio frame is divided into 10 equally sized sub-frames.

Each sub-frame is then divided into two equally sized time slots. Scheduling can operate on a sub-frame level.

Supported uplink data-modulation schemes are QPSK, 16QAM, and 64QAM.

The LTE standard specifies two different duplex modes; FDD and TDD. In Frequency Division Multiplex (FDD) mode the uplink and downlink are ...

What is the difference between FDD and TDD mode in LTE


The LTE standard specifies two different duplex modes; FDD and TDD. In Frequency Division Multiplex (FDD) mode the uplink and downlink are using separate frequencies. In Time Division Multiplex (TDD) mode the uplink and downlink use the same frequency but are separated in time.

These two modes have been harmonized in 3GPP to a large extent enabling vendors to use same HW platforms for eNode B and to develop terminals supporting both modes of operation.

Due to the commonalities between LTE FDD&TDD modes, their performance is similar in many aspects, such as spectrum efficiency. The fundamental characteristics of FDD and

TDD however also lead to differences:

  • TDD has a 3 to 6 dB weaker link budget compared to FDD, depending on UL:DL allocation
  • LTE TDD requires high accuracy synchronization within the network and also towards other TDD systems for efficient co-existence
  • LTE TDD has potentially more flexibility in applying beamforming schemes (due to thefact that eNode B has more knowledge on channel conditions in absence of UE report)

TD-LTE, FD-LTE, FDD-LTE,TDD-LTE

Latency or round trip time involves not only the radio but also the core network and the user equipment. The 3GPP target is to reach 10 m...

What is the LTE latency?


Latency or round trip time involves not only the radio but also the core network and the user equipment.

The 3GPP target is to reach 10 ms in a fully evolved SAE-LTE system.

The exact capability in terms of capacity and cell coverage varies depending on a number of factors such as the amount of available spectru...

What is LTE bitrates


The exact capability in terms of capacity and cell coverage varies depending on a number of factors such as the amount of available spectrum, the size of the radio channels, urban or rural areas, the number of subscribers sharing the capacity in the cell, interference from neighbouring cells, LOS, NLOS, NLOS indoor etc.

The 3GPP target of LTE is to provide mobile subscribers with a data channel of at least 100 Mbps in the downlink and 50 Mbps in the uplink with the use of a 20 MHz FDD carrier.

With  4x4 MIMO LTE with can go over 300 Mbps.

LTE is a complement to DSL and other fixed broadband technologies, not a replacement. A fibre based fixed network provides an almost unli...

Will LTE replace fixed broadband


LTE is a complement to DSL and other fixed broadband technologies, not a replacement.

A fibre based fixed network provides an almost unlimited bandwidth and is very suitable for HDTV distribution and similar applications requiring extremely high and continuous bitrates. For distribution of HDTV to large size screens in homes the requirement is often to support hundreds of channels and three simultaneous programs. This requires streaming of 20-60 Mbps and is, except for in some rural cases, best supported by cable and satellite TV networks.

However LTE offers support for bandwidth demanding applications such as interactive TV, POD TV to laptops and handheld terminals as well as most other type of broadband services. The services of fixed and mobile broadband systems are converged and the advantages of both technologies are combined to create new and even more attractive services.

Can GSM and WCDMA/HSPA work seamlessly with LTE ? LTE is an evolution of GSM-WCDMA and seamless mobility between these radio technologies...

Can GSM and WCDMA/HSPA work together with LTE


Can GSM and WCDMA/HSPA work seamlessly with LTE?

LTE is an evolution of GSM-WCDMA and seamless mobility between these radio technologies is therefore built in to the 3GPP standard. It should however be noted that LTE is only operating in packet data mode, i.e. there is no circuit switch part for voice service etc.

A wide variety of user equipment is foreseen to be available with many supporting LTE and HSPA as well as EDGE thereby providing global coverage from day one.

LTE is the radio part of the 3G evolution and SAE (System Architecture Evolution) is the part handling the packet core network. The goals...

What is SAE


LTE is the radio part of the 3G evolution and SAE (System Architecture Evolution) is the part handling the packet core network.

The goals of SAE are to provide a simplification of the packet core with a flat architecture, improvement in latency and optimization for IP services.

LTE Spectrum


LTE Architecture Overview

The LTE standard specifies these physical channels:  • Physical broadcast channel (PBCH)  o The coded BCH transport block is mapped to fo...

LTE Physical Channels

The LTE standard specifies these physical channels:

 • Physical broadcast channel (PBCH)
 o The coded BCH transport block is mapped to four subframes within a 40 ms interval
 o 40 ms timing is blindly detected, i.e. there is no explicit signaling indicating 40 ms timing o Each subframe is assumed to be self-decodable, i.e. the BCH can be decoded from a single reception, assuming sufficiently good channel conditions

 • Physical control format indicator channel (PCFICH)
 o Informs the UE about the number of OFDM symbols used for the PDCCHs
 o Transmitted in every subframe

 • Physical downlink control channel (PDCCH)
 o Informs the UE about the resource allocation of PCH and DL-SCH, and Hybrid ARQ information related to DL-SCH
 o Carries the uplink scheduling grant

 • Physical Hybrid ARQ Indicator Channel (PHICH): Carries Hybrid ARQ ACK/NAKs in response to uplink transmissions.

 • Physical downlink shared channel (PDSCH): Carries the DL-SCH and PCH

 • Physical multicast channel (PMCH): Carries the MCH

 • Physical uplink control channel (PUCCH)
 o Carries Hybrid ARQ ACK/NAKs in response to downlink transmission
 o Carries Scheduling Request (SR) o Carries CQI reports

 • Physical uplink shared channel (PUSCH): Carries the UL-SCH

 • Physical random access channel (PRACH): Carries the random access preamble

Download Long Term Evolution Protocol Overview

Download Long Term Evolution Protocol Overview

Download Long Term Evolution Protocol Overview

Download Overview of the 3GPP Long Term Evolution Physical Layer

Download Overview of the 3GPP Long Term Evolution Physical Layer

Download Overview of the 3GPP Long Term Evolution Physical Layer

Download The LTE Link-Layer Design

Download The LTE Link-Layer Design

Download The LTE Link-Layer Design

Download Journal LTE: The Evolution of Mobile Broadband

Download Journal LTE: The Evolution of Mobile Broadband

Download Journal LTE: The Evolution of Mobile Broadband

Event B2 (Serving becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2) The UE shall: 1> for UTRA and ...

LTE Event B2

Event B2 (Serving becomes worse than threshold1 and inter RAT neighbour becomes better than threshold2)

The UE shall:

1> for UTRA and CDMA2000, only trigger the event for cells included in the corresponding measurement object;
1> consider the entering condition for this event to be satisfied when both condition B2-1 and condition B2-2, as
specified below, are fulfilled;

1> consider the leaving condition for this event to be satisfied when condition B2-3 or condition B2-4, i.e. at least one of the two, as specified below, is fulfilled;

Inequality B2-1 (Entering condition 1)
Ms + Hys < Thresh1
Inequality B2-2 (Entering condition 2)
Mn+Ofn-Hys > Thresh2
Inequality B2-3 (Leaving condition 1)
Ms - Hys > Thresh1
Inequality B2-4 (Leaving condition 2)
Mn + Ofn +Hys < Thresh2

The variables in the formula are defined as follows:

Ms is the measurement result of the serving cell, not taking into account any offsets.
Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.
Ofn is the frequency specific offset of the frequency of the inter-RAT neighbour cell (i.e. offsetFreq as defined
within the measObject corresponding to the frequency of the inter-RAT neighbour cell).
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).
Thresh1 is the threshold parameter for this event (i.e. b2-Threshold1 as defined within reportConfigInterRAT for
this event).
Thresh2 is the threshold parameter for this event (i.e. b2-Threshold2 as defined within reportConfigInterRAT for
this event).
Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Mn is expressed in dBm or dB, depending on the measurement quantity of the inter-RAT neighbour cell.
Ofn, Hys are expressed in dB.
Thresh1 is expressed in the same unit as Ms.
Thresh2 is expressed in the same unit as Mn.

Event B1 (Inter RAT neighbour becomes better than threshold) The UE shall: 1> for UTRA and CDMA2000, only trigger the event for cells inc...

LTE Event B1

Event B1 (Inter RAT neighbour becomes better than threshold)

The UE shall:
1> for UTRA and CDMA2000, only trigger the event for cells included in the corresponding measurement object;
1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled;

Inequality B1-1 (Entering condition)
Mn + Ofn - Hys > Thresh

Inequality B1-2 (Leaving condition)
Mn + Ofn + Hys < Thresh

The variables in the formula are defined as follows:
Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets.
Ofn is the frequency specific offset of the frequency of the inter-RAT neighbour cell (i.e. offsetFreq as defined
within the measObject corresponding to the frequency of the neighbour inter-RAT cell).

Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event).

Event A5 (Serving becomes worse than threshold1 and neighbour becomes better than threshold2) The UE shall: 1> consider the entering cond...

LTE RRC Event A5

Event A5 (Serving becomes worse than threshold1 and neighbour becomes better than threshold2)

The UE shall:
1> consider the entering condition for this event to be satisfied when both conditions A5-1 and condition A5-2, as
specified below, are fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A5-3 or condition A5-4, i.e. at least
one of the two, as specified below, is fulfilled;

Inequality A5-1 (Entering condition 1)
Ms + Hys < Thresh1

Inequality A5-2 (Entering condition 2)
Mn + Ofn+ Ocn - Hys > Thresh2

Inequality A5-3 (Leaving condition 1)
Ms - Hys >Thresh1

Inequality A5-4 (Leaving condition 2)
Mn+Ofn+Ocn+Hys < Thresh2

The variables in the formula are defined as follows:
Ms is the measurement result of the serving cell, not taking into account any offsets.
Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within
measObjectEUTRA corresponding to the frequency of the neighbour cell).

Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA
corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).
Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigEUTRA for this event).

Thresh2 is the threshold parameter for this event (i.e. a5-Threshold2 as defined within reportConfigEUTRA for this event).

Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Ofn, Ocn, Hys are expressed in dB.
Thresh1 is expressed in the same unit as Ms.
Thresh2 is expressed in the same unit as Mn.

Event A4 (Neighbour becomes better than threshold) The UE shall: 1> consider the entering condition for this event to be satisfied when c...

LTE RRC Event A4

Event A4 (Neighbour becomes better than threshold)

The UE shall:
1> consider the entering condition for this event to be satisfied when condition A4-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled;

Inequality A4-1 (Entering condition)
Mn + Ofn + Ocn - Hys > Thresh

Inequality A4-2 (Leaving condition)
Mn + Ofn + Ocn + Hys > Thresh

The variables in the formula are defined as follows:

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).
Thresh is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigEUTRA for this event).
Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Ofn, Ocn, Hys are expressed in dB.
Thresh is expressed in the same unit as Ms.

Event A4 (Neighbour becomes better than threshold) The UE shall: 1> consider the entering condition for this event to be satisfied when c...

LTE RRC Event A4

Event A4 (Neighbour becomes better than threshold)

The UE shall:
1> consider the entering condition for this event to be satisfied when condition A4-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A4-2, as specified below, is fulfilled;

Inequality A4-1 (Entering condition)
Mn + Ofn + Ocn - Hys > Thresh

Inequality A4-2 (Leaving condition)
Mn + Ofn + Ocn + Hys > Thresh

The variables in the formula are defined as follows:

Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).
Thresh is the threshold parameter for this event (i.e. a4-Threshold as defined within reportConfigEUTRA for this event).
Mn is expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Ofn, Ocn, Hys are expressed in dB.
Thresh is expressed in the same unit as Ms.

Event A3 (Neighbour becomes offset better than serving) The UE shall: 1> consider the entering condition for this event to be satisfied w...

LTE RRC Event A3

Event A3 (Neighbour becomes offset better than serving)

The UE shall:
1> consider the entering condition for this event to be satisfied when condition A3-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A3-2, as specified below, is fulfilled;

Inequality A3-1 (Entering condition)
Mn+Ofn+Ocn - Hys > Ms + Ofs + Ocs + Off

Inequality A3-2 (Leaving condition)
Mn+Ofn+Ocn + Hys > Ms + Ofs + Ocs + Off

The variables in the formula are defined as follows:
Mn is the measurement result of the neighbouring cell, not taking into account any offsets.
Ofn is the frequency specific offset of the frequency of the neighbour cell (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell).
Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell.
Ms is the measurement result of the serving cell, not taking into account any offsets.


Ofs is the frequency specific offset of the serving frequency (i.e. offsetFreq as defined within measObjectEUTRA corresponding to the serving frequency).
Ocs is the cell specific offset of the serving cell (i.e. cellIndividualOffset as defined within measObjectEUTRA corresponding to the serving frequency), and is set to zero if not configured for the serving cell.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).
Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigEUTRA for this event).
Mn, Ms are expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Ofn, Ocn, Ofs, Ocs, Hys, Off are expressed in dB.

Event A2 (Serving becomes worse than threshold) The UE shall: 1> consider the entering condition for this event to be satisfied when cond...

LTE RRC Event A2

Event A2 (Serving becomes worse than threshold)

The UE shall:
1> consider the entering condition for this event to be satisfied when condition A2-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A2-2, as specified below, is fulfilled;

Inequality A2-1 (Entering condition)
Ms + Hys < Thresh
Inequality A2-2 (Leaving condition)
Ms - Hys < Thresh

The variables in the formula are defined as follows:
Ms is the measurement result of the serving cell, not taking into account any offsets.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).
Thresh is the threshold parameter for this event (i.e. a2-Threshold as defined within reportConfigEUTRA for this event).
Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

Event A1 (Serving becomes better than threshold) The UE shall: 1> consider the entering condition for this event to be satisfied when ...

LTE Event A1

Event A1 (Serving becomes better than threshold)

The UE shall:


1> consider the entering condition for this event to be satisfied when condition A1-1, as specified below, is fulfilled;
1> consider the leaving condition for this event to be satisfied when condition A1-2, as specified below, is fulfilled;


Inequality A1-1 (Entering condition)
Ms - Hys > Thresh

Inequality A1-2 (Leaving condition)
Ms + Hys > Thresh

The variables in the formula are defined as follows:

Ms is the measurement result of the serving cell, not taking into account any offsets.
Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigEUTRA for this event).
Thresh is the threshold parameter for this event (i.e. a1-Threshold as defined within reportConfigEUTRA for this event).
Ms is expressed in dBm in case of RSRP, or in dB in case of RSRQ.
Hys is expressed in dB.

Thresh is expressed in the same unit as Ms.

Cell Structure, Configuration and Dimensioning n Initial LTE parameters n Radio channel organization n Carrier frequencies and EARCFNs ...

LTE Parameters and Tuning


Cell Structure, Configuration and Dimensioning
n Initial LTE parameters
n Radio channel organization
n Carrier frequencies and EARCFNs
n Assignment of PCI
n Automatic neighbour relation function
n Type 1and 2 frame structures (FDD/TDD modes)
n TDD mode with MBMS
n The benefits of MIMO
n MIMO concept and options for LTE
n Physical channels and resource blocks
n Reference signal configuration options
n Downlink configured control resource
n Downlink structure with MIMO
n Uplink configured control resource
n PUCCH resource allocation
n RACH procedure for MAC
n Resource allocation for PRACH
n PRACH procedure control

Frequency Planning
n Spectrum considerations
n Example global band allocation
n Considerations for spectrum refarming
n Considerations for spectrum sharing
n Multi-frequency and single-frequency networks
n Network simulations for multi- and single frequency plans
n Network throughput simulations
n Simulated performance for fixed and mobile users
n Simulated performance with and without MIMO

Idle Mode Parameters
n RRC states
n RCC inter-RAT state transitions
n LTE state management
n Idle mode function
n Cell selection
n Parameters for initial cell selection

n Cell selection modifications for CSG (femtocells)
n Cell barring at cell selection
n Cell barring for RRC connection establishment
n Idle mode neighbour lists
n Periodic HPLMN searches
n Cell reselection
n Priority in frequency and technology layers
n Measurement rules
n Normal cell reselection criteria
n Reselection and ranking criteria
n Parameters for cell reselection
n Mobility states
n Scaling rules for mobility states
n LTE neighbour lists in UMTS
n UMTS measurement rules without absolute priorities
n UMTS measurement rules with absolute priorities
n UMTS reselection criteria without absolute priorities
n UMTS reselection criteria with absolute priorities
n LTE neighbour lists in GSM/GPRS
n GSM measurement rules with priorities
n GSM reselection criteria with priorities

Connected Mode Parameters
n Measurement configuration
n Measurement configuration settings
n Measurement object definition for LTE
n Measurement object definition for inter-RAT
n Measurement and object summary
n Measurement gaps
n Configuration of LTE reporting criteria
n Event triggers relating to LTE
n Configuration of inter-RAT reporting criteria
n Event triggers relating to inter-RAT measurements
n Behaviour at event trigger points
n Measurement report format – LTE/UMTS
n Measurement report format – GSM/CDMA2000
n Intra-LTE handover
n Handover from LTE (IRAT)
n UMTS measurement configuration
n LTE measurement objects and reporting in UMTS
n UMTS inter-RAT event triggers
n UMTS inter-RAT event flow
n UMTS measurement reporting
n UMTS handover to LTE
n GSM/GPRS measurement configuration
n Key GSM to LTE measurement parameters
n GSM/GPRS measurement reporting
n GPRS packet handover to LTE
n Uplink power control
n Timing advance
n CQI reporting
n CQI reporting options
n Management of DRX for connected mode

Recent Posts