The UL-CCCH-Message class is the set of 48-bits RRC messages that may be sent from the UE to the

Network on the uplink CCCH logical channel

-- ASN1START
-- TAG-UL-CCCH-MESSAGE-START

UL-CCCH-Message ::= SEQUENCE {

message UL-CCCH-MessageType
}

UL-CCCH-MessageType ::= CHOICE {

c1 CHOICE {
rrcSetupRequest RRCSetupRequest,
rrcResumeRequest RRCResumeRequest,
rrcReestablishmentRequest RRCReestablishmentRequest,
rrcSystemInfoRequest RRCSystemInfoRequest
},
messageClassExtension SEQUENCE {}
}

-- TAG-UL-CCCH-MESSAGE-STOP
-- ASN1STOP

RRCSetupRequest
The RRCSetupRequest message is used to request the establishment of an RRC connection.
Signalling radio bearer: SRB0

RLC-SAP: TM

Logical channel: CCCH

Direction: UE to Network

RRCSetupRequest message
-- ASN1START
-- TAG-RRCSETUPREQUEST-START

RRCSetupRequest ::= SEQUENCE {

rrcSetupRequest RRCSetupRequest-IEs
}

RRCSetupRequest-IEs ::= SEQUENCE {

ue-Identity InitialUE-Identity,
establishmentCause EstablishmentCause,
spare BIT STRING (SIZE (1))
}

InitialUE-Identity ::= CHOICE {

ng-5G-S-TMSI-Part1 BIT STRING (SIZE (39)),
randomValue BIT STRING (SIZE (39))
}

EstablishmentCause ::= ENUMERATED {

emergency, highPriorityAccess, mt-Access, mo-Signalling,
mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS,
mps-PriorityAccess, mcs-PriorityAccess }

-- TAG-RRCSETUPREQUEST-STOP
-- ASN1STOP
 RRCSetup
The RRCSetup message is used to establish SRB1.
Signalling radio bearer: SRB0

RLC-SAP: TM

Logical channel: CCCH

Direction: Network to UE

RRCSetup message
-- ASN1START
-- TAG-RRCSETUP-START

RRCSetup ::= SEQUENCE {

rrc-TransactionIdentifier RRC-TransactionIdentifier,
criticalExtensions CHOICE {
rrcSetup RRCSetup-IEs,
criticalExtensionsFuture SEQUENCE {}
}
}

RRCSetup-IEs ::= SEQUENCE {

radioBearerConfig RadioBearerConfig,
masterCellGroup OCTET STRING (CONTAINING CellGroupConfig),

lateNonCriticalExtension OCTET STRING

OPTIONAL,
nonCriticalExtension SEQUENCE{}
OPTIONAL
}

-- TAG-RRCSETUP-STOP
-- ASN1STOP

RRCSetup-IEs field descriptions

masterCellGroup
The network configures only the RLC bearer for the SRB1, mac-CellGroupConfig, physicalCellGroupConfig and spCellConfig.
radioBearerConfig
Only SRB1 can be configured in RRC setup.

– RRCSetupComplete
The RRCSetupComplete message is used to confirm the successful completion of an RRC connection
establishment.
Signalling radio bearer: SRB1

RLC-SAP: AM

Logical channel: DCCH

Direction: UE to Network

RRCSetupComplete message
-- ASN1START
-- TAG-RRCSETUPCOMPLETE-START

RRCSetupComplete ::= SEQUENCE {

rrc-TransactionIdentifier RRC-TransactionIdentifier,
criticalExtensions CHOICE {
rrcSetupComplete RRCSetupComplete-IEs,
criticalExtensionsFuture SEQUENCE {}
 }
}

RRCSetupComplete-IEs ::= SEQUENCE {

selectedPLMN-Identity INTEGER (1..maxPLMN),
registeredAMF RegisteredAMF OPTIONAL,
guami-Type ENUMERATED {native, mapped} OPTIONAL,
s-NSSAI-List SEQUENCE (SIZE (1..maxNrofS-NSSAI)) OF S-NSSAI OPTIONAL,
dedicatedNAS-Message DedicatedNAS-Message,
ng-5G-S-TMSI-Value CHOICE {
ng-5G-S-TMSI NG-5G-S-TMSI,
ng-5G-S-TMSI-Part2 BIT STRING (SIZE (9))
} OPTIONAL,
lateNonCriticalExtension OCTET STRING OPTIONAL,
nonCriticalExtension SEQUENCE{} OPTIONAL
}

RegisteredAMF ::= SEQUENCE {

plmn-Identity PLMN-Identity OPTIONAL,
amf-Identifier AMF-Identifier
}

-- TAG-RRCSETUPCOMPLETE-STOP
-- ASN1STOP

RRCSetupComplete-IEs field descriptions

guami-Type
This field is used to indicate whether the GUAMI included is native (derived from native 5G-GUTI) or mapped (from EPS, derived from EPS GU
[23].
ng-5G-S-TMSI-Part2
The leftmost 9 bits of 5G-S-TMSI.
registeredAMF
This field is used to transfer the GUAMI of the AMF where the UE is registered, as provided by upper layers, see TS 23.003 [21].
selectedPLMN-Identity
Index of the PLMN selected by the UE from the plmn-IdentityList fields included in SIB1.

Default MAC Cell Group configuration

Parameters
Name Value Semantics description Ver
MAC Cell Group configuration
bsr-Config
>periodicBSR-Timer sf10
>retxBSR-Timer sf80
phr-Config
>phr-PeriodicTimer sf10
>phr-ProhibitTimer sf10
>phr-Tx-PowerFactorChange dB1

The IE BWP-DownlinkDedicated is used to configure the dedicated (UE specific) parameters of a downlink
BWP.
BWP-DownlinkDedicated information element
-- ASN1START
-- TAG-BWP-DOWNLINKDEDICATED-START

BWP-DownlinkDedicated ::= SEQUENCE {

pdcch-Config SetupRelease { PDCCH-Config }
OPTIONAL, -- Need M
pdsch-Config SetupRelease { PDSCH-Config }
OPTIONAL, -- Need M
sps-Config SetupRelease { SPS-Config }
OPTIONAL, -- Need M
radioLinkMonitoringConfig SetupRelease { RadioLinkMonitoringConfig }
OPTIONAL, -- Need M
 ...
}

-- TAG-BWP-DOWNLINKDEDICATED-STOP
-- ASN1STOP

BWP-DownlinkDedicated field descriptions

pdcch-Config
UE specific PDCCH configuration for one BWP.
pdsch-Config
UE specific PDSCH configuration for one BWP.
sps-Config
UE specific SPS (Semi-Persistent Scheduling) configuration for one BWP. Except for reconfiguration with sync, the NW does not
reconfigure sps-Config when there is an active configured downlink assignment (see TS 38.321 [3]). However, the NW may release the
sps-Config at any time.
radioLinkMonitoringConfig
UE specific configuration of radio link monitoring for detecting cell- and beam radio link failure occasions. The maximum number of
failure detection resources should be limited up to 8 for both cell and beam radio link failure detection in Rel-15.

BWP-DownlinkCommon information element

-- ASN1START
-- TAG-BWP-DOWNLINKCOMMON-START

BWP-DownlinkCommon ::= SEQUENCE {

genericParameters BWP,
pdcch-ConfigCommon SetupRelease { PDCCH-ConfigCommon }
OPTIONAL, -- Need M
pdsch-ConfigCommon SetupRelease { PDSCH-ConfigCommon }
OPTIONAL, -- Need M
...
}

-- TAG-BWP-DOWNLINKCOMMON-STOP
-- ASN1STOP

BWP-DownlinkCommon field descriptions

pdcch-ConfigCommon
Cell specific parameters for the PDCCH of this BWP.
pdsch-ConfigCommon
Cell specific parameters for the PDSCH of this BWP.

The IE BWP-Downlink is used to configure an additional downlink bandwidth part (not for the initial BWP).
BWP-Downlink information element
-- ASN1START
-- TAG-BWP-DOWNLINK-START

BWP-Downlink ::= SEQUENCE {

bwp-Id BWP-Id,
bwp-Common BWP-DownlinkCommon
OPTIONAL, -- Cond SetupOtherBWP
bwp-Dedicated BWP-DownlinkDedicated
OPTIONAL, -- Cond SetupOtherBWP
...
}

-- TAG-BWP-DOWNLINK-STOP
-- ASN1STOP
 BWP-Downlink field descriptions
bwp-Id
An identifier for this bandwidth part. Other parts of the RRC configuration use the BWP-Id to associate themselves with a particular bandwidth
part.
The network configures the BWPs with consecutive IDs from 1. The Network does not include the value 0, since value 0 is reserved for the initial
BWP.
For
Suhail For diagrams fig 8 and 7 PDCCH Config part

BWP information element

-- ASN1START
-- TAG-BWP-START

BWP ::= SEQUENCE {

locationAndBandwidth INTEGER (0..37949),
subcarrierSpacing SubcarrierSpacing,
cyclicPrefix ENUMERATED { extended }
OPTIONAL -- Need R
}

5G NR (CORESET, Search Space and BWP)

CORESET, Search Space and BWP

CORESET: Control Resource Set, This is basically the PDCCH
decode region.

In LTE system, PDCCH is span across the complete system

bandwidth in frequency domain and in time domain, PCFICH tells
about the number of OFDM sysmbol. In LTE Control region is
always at the starting of subframe.

But in NR, there are lot flexibility for PDCCH control region also and
it is not necessary to span across the complete system bandwidth as
like LTE.

Network can define common control region and UE specific

control region. Number of CORESET is limited to 3 per BWP
(Bandwidth part) including both common and UE specific
CORESET.

Broad pictorial representation of LTE vs NR CORESET

Fig 1: LTE vs NR CORESET View

Common CORESET- Common CORESET configuration is shared

by muliple UE’s in a cell, so accordingly network take care alignment
with all UE’s for this configuration. Example — PDCCH control
region for RAR/paging/system information.
Fig 2: Common CORESET Configuration

UE specific CORESET — PDCCH control region which is

specifically defined for a UE.

Fig 3: UE specific CORESET configuration

CORESET and search space both are closely associated

with each other.

Search Space: Initially may be you find it little tricky to

understand, so put a careful attention here. By definition — Each
search space is a set of control channel elements at a different
aggregation level(s). In other words, search space tells how many
candidates are there to decode at different aggregation level.

There is mapping between CORESET and search space. A CORESET

may have multiple search space. It is the search space where UE
attempts for the blind decoding.

Fig 4: CORESET has multiple search space at different aggregation level

Now the question is why multiple candidate are defined at
different aggregation level. Answer is same as LTE. One reason
for different aggregation level is to mitigate the situation when UE is
under bad coverage. For a UE which is under bad coverage area, n/w
will choose higher aggregation level so that UE can reliably decode
the PDCCH. Reliable decoding of PDCCH is very important for the
overall performance of the system

Aggregation Level: It basically tells how many bits are used for
PDCCH transmission. If UE is under bad coverage then n/w may go
with high aggregation level candidate so that UE can reliably decode
the PDCCH. Possible aggregation level in NR is — 1,2,4,8,16

Aggregation Level = 6 REG and REG = 12 RE, so one

aggregation level means (72 RE)

Max number of search space per BWP is — 10 including both

common and UE specific.

Fig 5: Search Space (SS ID associated with CORESET ID 1) configuration with one
candidate of aggregation level 16

In Fig 6, It is shown that in a single CORESET, multiple search space

is defined. In this snippet both search space (search space ID 1, 8)
are common search space but a CORESET can be associated with
both UE specific and/or common search space. End of this snippet,
search space for RACH, Paging and SI has been defined.

Fig 6: Multiple Search space defined corresponding to one CORESET (Refer Fig 4 here
again)

Bandwidth Part (BWP):

1. Motivation of BWP: In most cases, NR would operate in

very wideband and there wouldn’t be any issues for the high end
UEs to handle the full operating band, but we cannot expect
every types of UE to be able to work with this kind of wideband.
So we need some mechanism so that narrow band UE can also
operate. So BWP is basically a fraction of spectrum that a UE
only need to care.
Fig 7: Pictorial representation of BWP

Fig 7 shows three BWP (each BWP is associated with a BWP ID),
location and width of BWP is defined by two parameter
locationAndBandwidth and offsetToCarrier as shown in Fig
8, refer TS38.214 for exact calculation.

Fig 8: Important parameters for BWP Configuration

Bandwidth Part (BWP) is defined for both UL/DL, here in this

tutorial, we explained in term of DL BWP so there after BWP is DL
BWP.

Default BWP: Downlink bandwidth part to be used upon expiry of

the BWP inactivity time. When this field is absent then UE use
Initial BWP as the default BWP.

First Active BWP: If configured for an SpCell, this field contains

the ID of the DL BWP to be activated after applying the the RRC
(re-)configuration from the n/w. As our case is for Spcell, so here
first Active BWP ID is — 1.

After expiry of bwp inactivity timer, UE will switch to default

BWP ID. Here default BWP ID field is absent and hence UE switch
to BWP ID — 0 (BWP ID 0 is always associated with initial BWP), so
in short strory here initial BWP and default BWP is same.
Fig 9: Configuration of Default and First Active BWP

Initial BWP & other BWP:

1. Initial BWP is defined under IE -initialDownlinkBWP and

there is no sub-field for BWP ID here, initial BWP ID is always 0,
refer Fig 10.
2. Other BWP’s are defined under IE
— downlinkBWP_ToAddModList with BWP-ID, refer Fig
11.

Fig 10: Initial BWP configuration

Fig 11: Other then Initial BWP

Below are the few numbers about CORESET, BWP &
Search space
1. Number of CORESET is limited to 3 per BWP including both
common and UE specific.
2. Number of BWP per serving cell is — 4 and at a time there is only
one active BWP.
3. So Max number of CORESET per serving cell is — 12
( controlResourceSetId, range is 0 -11)
4. Max number of search space per BWP is — 10.
5. Max search space per serving cell is — number of BWP per serving
cell (4 )* search space per BWP (10) = 40 // so searchspaceID range
is 0–39
6. CORESET ID (controlResourceSetId) is unique among the BWPs
of a ServingCell.
7. Each search space is associated with some CORESET.
How BWP location and bandwidth is specified in RRC ?
 
The location (starting position and the bandwidth of a BWP is specified in RRC parameter called
locationAndBandwidth and this parameter is specified as RIV that can be calculated according
to the following specification.
 
 
< 38.213-12 Bandwidth part operation > states as follows :
a first PRB and a number of contiguous PRBs by higher layer parameter
locationAndBandwidth that is interpreted as RIV according to TS 38.214,

setting  , and the first PRB is a PRB offset relative to the PRB indicated by
higher layer parameters offsetToCarrier and subcarrierSpacing
 
< 38.214-5.1.2.2.2 Downlink resource allocation type 1> defines RIV as follows :

 
Combining the two specification mentioned above, I would come up with some examples as
shown below. All these examples are based on the assumption that RB_start = 0, BWP takes
up the maximum RB for the specified channel bandwidth and subcarrierspacing = 30 Khz, FR1
 
CBW max RB Equation RIV Calculation locationAndBandwidth
20 51 (1) 275*(51-1)+0 13750
40 106 (1) 275*(106-1)+0 28875
50 133 (1) 275*(133-1)+0 36300
275*(275-
60 162 (2) 31624
162+1)+(275-1-0)
275*(275-
80 217 (2) 16499
217+1)+(275-1-0)
275*(275-
100 273 (2) 1099
273+1)+(275-1-0)
 
 
Following is the table that I calculated for subcarrier spacing  = 15 Khz  based on the
assumption that RB_start = 0, BWP takes up the maximum RB for the specified channel
bandwidth

 
 max
CBW Equation RIV Calculation locationAndBandwidth
RB
10 52 (1) 275*(52-1)+0 14025
20 106 (1) 275*(106-1)+0 28875
275*(275-
40 216 (2) 216+1)+(275- 16774
1-0)
275*(275-
50 270 (2) 270+1)+(275- 1924
1-0)
 
 
Following is the table that I calculated for subcarrier spacing  = 120 Khz  based on the
assumption that RB_start = 0, BWP takes up the maximum RB for the specified channel
bandwidth
 
max Equatio RIV locationAndBandwidt
CBW
RB n Calculation h
50 32 (1) 275*(32-1)+0 8525
100 66 (1) 275*(66-1)+0 17875
275*(132-
200 132 (1) 36025
1)+0
275*(275-
400 264 (2) 264+1)+(275 3574
-1-0)