Professional Documents
Culture Documents
Field Descriptions:
Consists of MCC and MNC. The first listed one is the Primary
PLMN-Identity
PLMN
Value applicable for the cell. If absent the UE applies the
maximum power according to the UE capability. If eNB
p-Max configures the value more than the value supported by the UE
then UE will set the max value aupported by the UE capability.
Example UE Catagory 3 supports max 23 db
cellReservedForOperatorUse As defined by operator (Reserved/Not_reserved)
trackingAreaCode TAC which is common to the PLMN Identities
cellIdentity Identifies a cell within the PLMN
cellBarred If Barred then UE is not allowed to camp on the cell
If enabled, UE will be able to perform Cell-reselection to
intraFreqReselection
INTRA-frequency cells
q_RxLevMin Minimum required RX level in the cell
Actual value Qrxlevminoffset = IE value * 2 [dB]. only applied
when a cell is evaluated for cell selection as a result of a
periodic search for a higher priority PLMN while camped
normally in a VPLMN [5]. During this periodic search for
q_RxLevMinOffset
higher priority PLMN the UE may check the S criteria of a cell
using parameter values stored from a different cell of this
higher priority PLMN. Affects the minimum required Rx level
in the cell.
freqBandIndicator indicates the E-UTRA operating band
information regarding the presence of SIB type; other than
schedulingInfoList
SIB1
Periodicity of the SI-message in radio frames (SI will be
si_Periodicity
transmitted within the specified radio frame)
carries the List of the SIBs mapped. SIB2 is always present in
sib_MappingInfo
the first element of schedulingInfoList
specifies that a SIB should be transmitted somewhere within
the specified window length. Value is in ms. This window
si_WindowLength starts at the starting sub-frame of the mentioned si_periodicity.
SIBs can be received in any of the sub-frame as mentioned in
the WindowLength.
indicates if a change has occurred in the SI messages. UEs may
use systemInfoValueTag, e.g. upon return from out of
coverage, to verify if the previously stored SI messages are still
valid.
systemInfoValueTag Additionally, the UE considers stored system information to be
invalid after 3 hours from the moment it was successfully
confirmed as valid, unless specified otherwise.
Common for all SIBs other than MIB, SIB1, SIB10, SIB11 and
SIB12.
SIB2 in LTE
SIB-2: an IMPORTANT SIB
The IE SystemInformationBlockType2 contains radio resource configuration information that is common for all
UEs.
It carries Common and shared channel configuration, RACH related configuration, Timers, UL Power controls.
SIB2 is not specifically included in the scheduling information in SIB1 but it is always mapped to the SI message
that corresponds to the first entry in the list of SI messages in schedulingInfoList in SIB1
Field Descriptions:
ac-BarringInfo Access Class Barring configuration
used to specify common radio resource configurations
radioResourceConfig in the system information and in the mobility control
information
numberOfRA_Preambles Number of non-dedicated random access preambles
powerRampingParameters
powerRampingStep Power ramping factor
preambleInitialReceivedTargetPower Initial preamble power
ra_SupervisionInfo
preambleTransMax Maximum number of preamble transmission
Duration of the RA response window. Value in
ra_ResponseWindowSize
subframes. Value sf2 corresponds to 2 subframes
Timer for contention resolution. Value in subframes.
mac_ContentionResolutionTimer
Value sf8 corresponds to 8 subframes
Maximum number of Msg3 HARQ transmissions, used
maxHARQ_Msg3Tx 4
for contention based random access
bcch_Config
Actual modification period, expressed in number of
radio
modificationPeriodCoeff
frames= modificationPeriodCoeff * defaultPagingCycle.
n2 corresponds to value 2
pcch_Config
Default paging cycle, used to derive ‘T’. Value rf32
defaultPagingCycle
corresponds to 32 radio frames
is used as one of parameters to derive the Paging Frame
nB
and Paging Occasion
used to specify the PRACH configuration in the system
prach_Config
information and in the mobility control information
RA preambles are generated from Zadoff Chu
sequence which consists of series of root sequences.
rootSequenceIndex Each root sequence can be cyclic shifted to obtain
preamble sequence. Range of rootSequenceIndex is 0 to
837.
mentions the:
Preamble format: 0-4 (For frame structure 1 preamble
format is 0-3 and for frame structure 2 it is 0-4)
prach_ConfigIndex SFN: whether it will be EVEN no. frame OR any frame
subframe number: carrier the subframe no. within the
SFN
(Look for the table in TS36.211 - Table 5.7.1-2)
SIB3 in LTE
SIB3: Cell-reselection parameters for INTRA-Frequency, INTER-Frequency and Inter-RAT
contains Cell re-selection information common for intra-frequency, inter-frequency and inter-RAT cell re-selection
(i.e. applicable for more than one type of cell re-selection but not necessarily all)
intra-frequency cell re-selection information other than neighbouring cell related
Signalling radio bearer: N/A
RLC-Mode: TM
Logical channel: BCCH
Direction: E-UTRAN to UE
SIB4 in LTE
SIB4: Cell-reselection parameters for Neighbouring INTRA-Frequency
contains neighbouring cell related information relevant only for intra-frequency cell re-selection
includes cells with specific re-selection parameters as well as blacklisted cells
All the contents of SIB4 are optional because UE's can automatically detect and complete neighbour
INTRA_frequency cells
Signalling radio bearer: N/A
RLC-Mode: TM
Logical channel: BCCH
Direction: E-UTRAN to UE
Field Descriptions:
intraFreqNeighCellList List of intra-frequency neighbouring cells with specific cell
[1-16 instances] re-selection parameters
IntraFreqNeighCellInfo
physCellId Physical CellID of the neighbour cell
specifies the offset between the two cells. Value -24 -
q-OffsetCell
+24dB
intraFreqBlackCellList List of blacklisted intra-frequency neighbouring cells. These
[1-16 instances] type of cells are not considered for cell re-selection
Set of physical cell identities reserved for CSG cells on the
frequency on which this field was received. The received
csg-PhysCellIdRange applies if less than 24 hours has
csg_PhysCellIdRange
elapsed since it was received and it was received in the same
primary PLMN. This field is Optional (mandatory for CSG
cell)
SIB5 in LTE
SIB5: Cell-reselection parameters for INTER-Frequency
contains information relevant only for inter-frequency cell re-selection i.e. information
about other E-UTRA frequencies and inter-frequency neighbouring cells relevant for cell re-selection
includes cell re-selection parameters common for a frequency as well as cell specific re-
selection parameters
SIB6 in LTE
SIB6: Cell-reselection parameters INTER RAT Frequency
contains information relevant only for inter-RAT cell re-selection (information about UTRA frequencies and UTRA
neighbouring cells relevant for cell re-selection.
includes cell re-selection parameters common for a frequency
Signalling radio bearer: N/A
RLC-Mode: TMLogical channel: BCCH
Direction: E-UTRAN to UE
carrierFreqListUTRA_FDD/TDD
carrierFreq
cellReselectionPriority
threshX_High
threshX_Low
q_RxLevMin
p_Max
q_QualMin
t_ReselectionUTRA
t_ReselectionUTRA_SF
SF_Medium
SF_High
Field Descriptions:
Information specified for up to 16 instances of RF carriers for
carrierFreqListUTRA_FDD/TDD
FDD or TDD
carrierFreq carrier frequency helps the UE to seach
defines the absolute priority of the UMTS. Value 0-7, 0 is the
cellReselectionPriority
lowest priority
# Threshold (in dB) used by UE for cell re-selection to a
HIGHER priority UMTS frequency
threshX_High
# The Srxlev of the candiate cell is greater then threshX_High
# Value 0 to 31 dB. Actual value= Signaled value * 2
# Threshold (in dB) used by UE for cell re-selection to a
LOWER priority UMTS frequency
# Cell re-selection is allowed only when Srxlev of the candiate
threshX_Low
cell is greater then threshX_Low and RSR of serving cell is less
than the value of ThreshServingLow singalled within SIB3
# Value 0 to 31 dB. Actual value= Signaled value * 2
minimum RSCP requirement for candiate UMTS cell. Value -60
q_RxLevMin
to -13 dB. Actual value= Signaled value * 2 +1
Value applicable for the intra-frequency neighbouring E-UTRA
p_Max cells. If absent the UE applies the maximum power according to
the UE capability
# minimum Ec/Io requirement for candiate UMTS cell.
q_QualMin Value -24 to 0 dB
# applicable for FDD only
# defines the time to trigger cell re-selection
t_ReselectionUTRA
# value 0 - 7 seconds
# defines the time to trigger cell re-selection
# value 0 - 7 seconds
# Scaling factors used for Medium and High mobility
t_ReselectionUTRA_SF
# Scaling Factors value 0.25, 0.5, 0.75, 1.0. These values
decrease the value of T_reselection which allows more rapid cell
re-selections
SIB7 in LTE
SIB7: Cell-reselection parameters INTER RAT Frequency (GERAN)
contains information relevant only for inter-RAT (GERAN) cell re-selection
Signalling radio bearer: N/A
RLC-Mode: TM
Logical channel: BCCH
Direction: E-UTRAN to UE
SIB9 in LTE
SIB9: Home eNB name
contains a home eNB name (HeNB Name)
HeNB provie services to Closed Subscriber Groups. The HeNB name helps the user to select the correct CSG
Identity when performing a manual selection
Signalling radio bearer: N/A
RLC-Mode: TM
Logical channel: BCCH
Direction: E-UTRAN to UE
SIB10 in LTE
SIB10: ETWS primary notification
contains an ETWS primary notification
Field Descriptions:
Identifies the source and type of ETWS notification (earthquake,
messageIdentifier
tsunami warning, any emergency or test message)
Identifies variations of an ETWS notification.
-uses various mechanisms to alert the user (display message,
serialNumber play a tone or vibrate, location where the message is applicable,
also contains an update number which specifies whether a
change is in the message content or not)
# Identifies the warning type of the ETWS primary notification
warningType (earthquake, tsunami, etc.) and
# provides information on emergency user alert and UE popup
# is optional, only applied when security is applied
warningSecurityInfo
# Provides security information for the ETWS notification
SIB11 in LTE
SIB11: ETWS secondary notification
contains an ETWS secondary notification
Field Descriptions:
Identifies the source and type of ETWS
messageIdentifier notification (earthquake, tsunami warning, any
emergency or test message)
Identifies variations of an ETWS notification.
-uses various mechanisms to alert the user
(display message, play a tone or vibrate,
serialNumber location where the message is applicable, also
contains an update number which specifies
whether a change is in the message content or
not)
Indicates whether the included ETWS warning
warningMessageSegmentType
message segment is the last segment of the
[last/not last]
complete segment or not
# allows oedering of the message segments
# Segment number of the ETWS warning
message segment contained in the SIB. A
warningMessageSegmentNumber
segment number of zero corresponds to the first
segment, one corresponds to the second
segment, and so on
warningMessageSegment carries actual segment of the message
Identifies the alphabet/coding and the language
dataCodingScheme
applied variations of an ETWS notification
SIB12 in LTE
SIB12: CMAS notification
contains a CMAS notification
CMAS notifications carry high emerygency situations and is defined for three catagories:
-Presiential Alerts (President of a geographical location can send alerts)
-Threat Alerts (Tornado/Hurricane alerts)
-AMBER Alerts (Child abduction, endangered situation)
introduced in Release9
Signalling radio bearer: N/A
RLC-Mode: TMLogical channel: BCCH
Direction: E-UTRAN to UE
Field Descriptions:
Identifies the source and type of CMAS
messageIdentifier
notification
serialNumber Identifies variations of a CMAS notification
Indicates whether the included CMAS warning
warningMessageSegmentType
message segment is the last segment or not
Segment number of the CMAS warning message
segment contained in the SIB. A segment number
warningMessageSegmentNumber
of zero corresponds to the first segment, one
corresponds to the second segment, and so on
SIB13 in LTE
SIB13: MBMS control information
contains the information required to acquire the MBMS control information associated with one or more MBSFN
areas
introduced in Release9
Signalling radio bearer: N/A
RLC-Mode: TM
Logical channel: BCCH
Direction: E-UTRAN to UE
Query_4: Minimum of how many SIBs are required for the UE to initiate Attach procedure?
In LTE, for a UE to access the eNB, at the most minimum 2 SIBs are required (SIB1 and SIB2).
Information regarding SIB2-SIB13 are carried in SI messages and are included in schedulingInfoList which is part of SIB1.
Scheduling of SIBs:
SIB1 uses a fixed schedule with a periodicity of 80 ms and repetitions made within 80 ms.
The first transmission of SIB1 is scheduled in subframe #5 of radio frames for which the SFN mod 8 = 0, and
Repetitions are scheduled in subframe #5 of all other radio frames for which SFN mod 2 = 0.
Scheduling of other SIB's i.e. SIB-2 to SIB-9 is defined by si-Periodicity and si-WindowLength. Both these IEs are
explained below. For the rest of the SIBs, Paging is received by UE in RRC_IDLE or RRC_CONNECTED mode for
notification of an in-coming SI message.
There are two IE's which help the UE to calculate when to read SI messages. They are:
a. schedulingInfoList
b. si-WindowLengthd
schedulingInfoList informs the UE regarding the presence of SIB type; other than SIB1. It carriers two more parameters:
i. si_Periodicity
ii. sib_MappingInfo
si_Periodicity tells about the period in terms of radio frames which helps the UE to read the required SIB. The value of this
parameter is used for calculating the Radio frame where SI will be received.
sib_MappingInfo carries the type of SIBs mapped
si-WindowLength specifies that a SIB should be transmitted somewhere within the specified window length. Value is in
ms. This window starts at the starting sub-frame of the mentioned si_periodicity. SIBs can be received in any of the sub-
frame as mentioned in the WindowLength.
Example:
SIB1 is received by UE with the following information:
schedulingInfoList[0] SchedulingInfo
si_Periodicity SchedulingInfosi_Periodicity_rf16
sib_MappingInfo[0] SIB_TypeSIB_Type_sibType3
schedulingInfoList[1] SchedulingInfo
si_Periodicity SchedulingInfosi_Periodicity_rf32
sib_MappingInfo[0] SIB_TypeSIB_Type_sibType4
schedulingInfoList[2] SchedulingInfo
si_Periodicity SchedulingInfosi_Periodicity_rf64
sib_MappingInfo[0] SIB_TypeSIB_Type_sibType5
si_WindowLength ms20
(To look for the complete IE contents and explanation of SIB1 click here)
b. on which sub-frame will the SI window start. To determine the start of the SI window at sub-frame, the formula is:
a = x mod 10
x = (n – 1)*w
where,
X Integer value
a number which corrosponds to the order of entry in schedulingInfoList.For sib3 n is
1,
N
for sib4 n is 2 and
for sib5 n is 3
W si-WindowLength
T si-Periodicity of the concerned SI message
Let's start calulating the Radio frame and SI starting sub frame for SIB3, SIB4 and SIB5
x = (n –
For 1)*w a = x mod 10
The SI Window will start at sub frame 0 of the Radio frame where SI will be
SIB- x=(2 - a= 20 mod 10
acquired
4 1)*20 a=0
x=20
x = (n –
For 1)*w a = x mod 10
The SI Window will start at sub frame 0 of the Radio frame where SI will be
SIB- x=(3 - a= 40 mod 10
acquired
5 1)*20 a=0
x=40
SIBs and their JOBS: (click on each of the SIB to know more about them)
SIB-1 Cell access related parameters and scheduling of other SIBs
Common and shared channel configuration, RACH related configuration are
SIB-2
present
Parameters required for intra-frequency, inter-frequency and I-RAT cell re-
SIB-3
selections
SIB-4 Information regarding INTRA-frequency neighboring cells (E-UTRA)
SIB-5 Information regarding INTER-frequency neighboring cells (E-UTRA)
SIB-6 Information for re-selection to INTER-RAT (UTRAN cells)
SIB-7 Information for re-selection to INTER-RAT (GERAN cells)
SIB-8 Information for re-selection to INTER-RAT (CDMA2000)
SIB-9 Information related to Home eNodeB (FEMTOCELL)
ETWS (Earthquake and Tsunami Warning System) information (Primary
SIB-10
notification)
ETWS (Earthquake and Tsunami Warning System) information (Secondary
SIB-11
notification)
SIB-12 Commercial Mobile Alert Service (CMAS) information.
Contains the information required to acquire the MBMS control information
SIB-13
associated with one or more MBSFN areas.
SIB Scheduling
In LTE, MIB, SIB1, SIB2 is mandated to be transmitted for any cells. Since many of the SIB are
transmitted, it should be transmitted in such a way that the location (subframe) where a SIB is
transmitted should not be the same subframe where another SIB is transmitted.
You may notice that LTE SIB1 is very similar to WCDMA MIB.
Especially at initial test case development, you have to be very careful about item v). If you set this value
incorrectly, all the other SIBs will not be decoded by UE. And as a result, UE would not recognize the cell
and show "No Service" message.
According to 36.331 section 6.2.2 Message definitions - MasterInformationBlock field descriptions, the
System Frame Number in MIB is specified as follows :
Defines the 8 most significant bits of the SFN. As indicated in TS 36.211 [21, 6.6.1], the 2 least
significant bits of the SFN are acquired implicitly in the P-BCH decoding, i.e. timing of 40ms P-BCH
TTI indicates 2 least significant bits(within 40ms P-BCH TTI, the first radio frame: 00, the second
radio frame: 01, the third radio frame: 10, the last radio frame: 11). One value applies for all
serving cells (the associated functionality is common i.e. not performed independently for each
cell).
This means that even though SIB1 periodicity is 80 ms, different copies (Redudancy version : RV) of the
SIB1 is transmitted every 20ms. Meaning that at L3 you will see the SIB1 every 80 ms, but at PHY layer
you will see it every 20ms. For the detailed RV assignment for each transmission, refer to 36.321 section
5.3.1 (the last part of the section)
The transmission cycles for other SIBs are determined by schedulingInfoList in SIB1 as shown in the
following example (This example is the case where SIB2 and 3 are being transmitted).
One thing you would notice that sib-MappingInfo IE in the first node is not specified, but the first entity of
schedulingInfoList should always be for SIB2 as specified in the 36.331 as follows (See 36.331
SystemInformationBlockType1 field description).
List of the SIBs mapped to this SystemInformation message.There is no mapping information of SIB2; it is
always
present in the first SystemInformation message listed in the schedulingInfoList list.
Understanding overall cycle in the unit of Subframe number is pretty straightforward to understand. But
understanding exactly at which subframe a SIB should be transmitted is not that straightforward as you
might think. It is related to 'si-WindowLength'. si-WindowLength tells that a SIB should be transmitted
somewhere within the window length starting at the SFN specified by si-Periodicity. But this parameter
does not specify the exact subframe number for the transmission.
The subframe for a specific SIB transmission is determined by a algorithm defined in 36.331 5.2.3
Acquisition of an SI message as follows.
Following is a SIBs captured from a live network. Go through the capture and check if it matches your
understanding.