Professional Documents
Culture Documents
The RRC Services and Functions
The RRC Services and Functions
The major
functions of the RRC protocol include connection establishment and release functions,
broadcast of system information, radio bearer establishment, reconfiguration and release,
RRC connection mobility procedures, paging notification and release and outer loop power
control.By means of the signaling functions, the RRC configures the user and control planes
according to the network status and allows for Radio Resource Management strategies to
be implemented.
The operation of the RRC is guided by a state machine which defines certain specific states
that a UE may be present in. The different RRC states in this state machine have different
amounts of radio resources associated with them and these are the resources that the UE
may use when it is present in a given specific state.
Appart form RRC connected and RRC IDLE state, 5G NR has introduced a new RRC state
names as RRC Inactive state.
NR-RRC CONNECTED
NR-RRC INACTIVE
NR-RRC IDLE
A UE can move to RRC Idle mode from RRC connected or RRC Inactive state.
PLMN selection
Broadcast of system information
Cell re-selection mobility
Paging for mobile terminated data is initiated by 5GC
Paging for mobile terminated data area is managed by 5GC
DRX for CN paging configured by NAS
RRC Inactive Mode Operation:
The RRC States is a solution to the system access, power saving, and mobility optimization.
5G has to support eMBB, URLLC, and Massive IoT services at same cost and energy
dissipation per day per area.
5G system access and requested services have different characteristics => Control of
connectivity for future services need to flexible and programmable. To meet these different
services characteristics it requires new RRC state model.
To support URLLC services which transmits small packets that require ultra-low
latency and/or high reliability
Massive IoT Devices wakes up seldom power saving mode to transmit and receive a
small payload.
Devices need to camp in low activity state, and sporadically transmits UL data and/or
status reports with small payload to the network.
Devices need periodic and/or sporadic DL small packet transmission.
When UE is in the connected state, and sporadically transmit UL data and/or status
reports with small payload to the network.
Smartphones and consumer devices which eMBB UE have periodic and/or sporadic
UL and/or DL small packet transmission and extreme data rates
RRC Reconfiguration is the most important steps in establishing Radio Connection between UE and Network
Radio Bearer
Measurement
Scells or Cell Group
Radio Bearer
o Establish
o Modify
o Release
Measurement
o Setup
o Modify
o Release
Scells or Cell Group
o Add
o Modify
o Release
What should a UE do when it gets RrcReconfiguration message ? The answer is simple. Do whatever the
message tell you to do. I know this is not the answer you want to hear :). Like in LTE, RRCReconfiguration is the
most complicated message in NR. Understanding this message in full detail is like understanding the full
protocol stack of NR. You will see a good framework or starting point of understanding this message in 3GPP
38.331 - 5.3.5.3 Reception of an RRCReconfiguration by the UE. Followings are some of the highest level
IE(Information Elements) that you may start with.
secondaryCellGroup
radioBearerConfig
measConfig
nr-SecondaryCellGroupConfig
spCellConfig->reconfigurationWithSync
Since this message carries too many parameters (Information Elements), you would easily get lost if you try to
go through each and every items from the beginning. I would suggest you to pick up any one of the high level
items from the items listed above and try to understand the overall functionality of the high level item ,and
then move to next item and get an overview and so on. When you have overall understandings on every items
listed above, then move down to next level (one-step down) in each section.
Followings are RRC Reconfiguration Message structure from 38.331. (NOTE : This is not necessarily from the
latest specification. So just get the overal structure from this note and double check with 3GPP document
version that you are specifically interested in).
QuantityConfigNR::= SEQUENCE {
quantityConfigCell QuantityConfigRS,
quantityConfigRS-Index QuantityConfigRS OPTIONAL -- Need M
}
EUTRA-MBSFN-SubframeConfigList ::=
SEQUENCE (SIZE (1..maxMBSFN-Allocations)) OF EUTRA-MBSFN-SubframeConfig
SubcarrierSpacing ::= ENUMERATED {kHz15, kHz30, kHz60, kHz120, kHz240, spare3, spare2, spare1}
absoluteFrequencySSB : Frequency of the SSB to be used for this serving cell. SSB related parameters (e.g. SSB
index) provided for a serving cell refer to this SSB frequency unless mentioned otherwise. The frequency
provided in this field identifies the position of resource element RE=#0 (subcarrier #0) of resource block RB#10
of the SS block. The cell-defining SSB of the PCell is always on the sync raster. Frequencies are considered to be
on the sync raster if they are also identifiable with a GSCN value. If the field is absent, the SSB related
parameters should be absent, e.g. ssb-PositionsInBurst, ssb-periodicityServingCell and subcarrierSpacing in
ServingCellConfigCommon IE. If the field is absent, the UE obtains timing reference from the SpCell. This is only
supported in case the Scell is in the same frequency band as the SpCell
absoluteFrequencyPointA : Absolute frequency position of the reference resource block (Common RB 0). Its
lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined by this
field but rather in the scs-SpecificCarrierList. Corresponds to L1 parameter 'offset-ref-low-scs-ref-PRB' . See this
page for further details.
carrierBandwidth : Width of this carrier in number of PRBs (using the subcarrierSpacing defined for this carrier)
Corresponds to L1 parameter 'BW
offsetToCarrier : Offset in frequency domain between Point A (lowest subcarrier of common RB 0) and the
lowest usable subcarrier on this carrier in number of PRBs (using the subcarrierSpacing defined for this carrier).
The maximum value corresponds to 275*8-1. Corresponds to L1 parameter 'offset-pointA-low-scs'
SubcarrierSpacing : Subcarrier spacing of this carrier. It is used to convert the offsetToCarrier into an actual
frequency. Only the values 15 or 30 kHz (<6GHz), 60 or 120 kHz (>6GHz) are applicable. The network configures
all SCSs of configured BWPs configured in this serving cell. Corresponds to L1 parameter 'ref-scs'
txDirectCurrentLocation : Indicates the downlink Tx Direct Current location for the carrier. A value in the range
0..3299 indicates the subcarrier index within the carrier. The values in the value range 3301..4095 are reserved
and ignored by the UE. If this field is absent, the UE assumes the default value of 3300 (i.e. "Outside the
carrier").
offsetToPointA : The offset in PRB between the Point A and the lowest subcarrier of the lowest PRB of the cell-
defining SSB after floating SSB is resolved. See this page for further details.
Example 01 : spCellConfig.FrequencyInfoDL
IE(Information Element) Example Description
absoluteFrequencySSB 2054962
ssb_SubcarrierOffset Omit
frequencyBandList
frequencyBand[0] 257
absoluteFrequencyPointA 2054170
scs_SpecificCarrierList
scs_SpecificCarrier[0]
offsetToCarrier 0
subcarrierSpacing 120khz
k0 n0
carrierBandwidth 66
subcarrierSpacingCommon : Indicates Subcarrier spacing for SIB1, Msg.2/4 for initial access and SI-messages.
Values 15, and 30 kHz are applicable for carrier frequencies <6GHz;
Values 60 and 120 kHz are applicable for carrier frequencies >6GHz
ssb-subcarrieroffset : The frequency domain offset between SSB and the overall resource block grid in number
of subcarriers. Absence of the field indicates that no offset if applied (offset = 0). See 38.211, 7.4.3.1)
ssb-PositionsInBurst : Indicates the time domain positions of the transmitted SS-blocks in an SS-burst. It
corresponds to L1 parameter 'SSB-Transmitted' (see 38.213, section 4.1)
shortBitmap : bitmap for sub 3 GHz
mediumBitmap : bitmap for 3-6 GHz
longBitmap : bitmap for above 6 GHz
ssb-periodicityServingCell : The SSB periodicity in msec for the rate matching purpose (see 38.211-7.4.3.1)
dmrs-TypeA-Position : Position of (first) DL DM-RS (see 38.211, section 7.4.1.1.1). This field is usually in MIB.
Assuming that the UE does not need to acquire MIB before sending RA to target cell, this parameter should
also be here.
subcarrierSpacingSSB : Subcarrier spacing of SSB. Used only for non-initial access (e.g. SCells, PCell of SCG).
ss-PBCH-BlockPower : TX power that the NW used for SSB transmission. The UE uses it to estimate the RA
preamble TX power
rach-ConfigCommon : Parameters that are also conveyed via system information (SIB1) but which are provided
here to accelerate handover and to avoid that UEs need to read system information from SCells. See rach-
ConfigCommon details in RACH page.
newUE-Identity : This is used as an RNTI assigning a C-RNTI to a UE. 38.331(v15.1)-5.3.5.5.2 states 'apply the
value of the newUE-Identity as the C-RNTI for this cell group'
Example :