1 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Establishment
2 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Part IRadio Resource Control
3 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Procedures
Node B
UTRANRRC Procedures
UE
RNC
Measurement Procedures• Measurement Control• Measurement Report• etc.
RRC Connection Mobility Procedures
• Cell and URA update• UTRAN mobility information• Active set update• Hard handover• Inter-RAT cell reselection to
UTRAN• etc.
RRC Connection ManagementProcedures
• Broadcast of system information• Paging• RRC connection establishment• UE capability inquiry• Security mode control• Inter-RAT handover information
transfer• etc.
Radio Bearer ControlProcedures
• Radio bearer establishment• Transport channel reconfiguration• Physical channel reconfiguration• etc.
TS 25.331
4 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Message Structure
Node B
UTRANRRC Message
UE
RNCCN IEs
UTRAN Mobility Management IEs
UE IEs
Radio Bearer IEs
Transport Channel IEs
Physical Channel IEs
Measurement IEs
Other IEs
5 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Establishment
Node BUE RNC
[RACH] RRC Connection Request
[DCH] RRC Connection Setup Complete
[FACH] RRC Connection Setup
Radio Link Setup
L1 Synchronisation
accepted
[RACH] RRC Connection Request
[FACH] RRC Connection Reject
UE RNC
rejected
6 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Part IIRRC Connection Request
7 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Establishment
UERNC
RRC Connection Request ( )
UE IEs
Measurement IEs
Initial UE identity
Establishment cause
Protocol errorindicator
IMSI
TMSI & LAI
P-TMSI & RAI
IMEI
CHOICE
TRUE / FALSE(default: FALSE)
Originating Conversational Call,Originating Background Call,Terminating Streaming Call,
Emergency Call,Inter-RAT cell reselection,
Registration,Detach,
Originating High Priority Signalling,
Call reestablishment,Terminating Low Priority
Signalling,
e.g.
8 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Part IIIRRC Connection Setup
9 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Establishment
UERNC
RRC Connection Request ( )
UE IEs
Measurement IEsMeasurement
results forcurrent cell
Measurementresults for
monitored cells
if FDD: measurement quantity(CPICH Ec/No / CPICH RSCP/Pathloss)
up to 8
SFN – SFN observed
time difference
if FDD
P-CPICH info
Measurementquantity
Primaryscramblingcode0..511
Measured Resultson the RACH
10 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message
UERNC
RRC Connection Setup ( )
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DL
11 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: UE IEs
UERNC
RRC Connection Setup ( )
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DL
Initial UE ID
RRC Transaction ID
Activation Time
New U-RNTI
New C-RNTI
UTRAN DRX cycle length coefficient
RRC State Indicator
Capability updaterequirement
IMSI / TMSI and LAI / P-TMSI and RAI / IMEI
0..3
absolute CFN (0..255); default: now
CELL_DCH/CELL_FACH/CELL_PCH/URA_PCH
3..9
UE radio access FDD: TRUE/FALSEUE radio access TDD: TRUE/FALSEenumerated: GSM (optional)
= S-RNTI + RNC-ID
(optional)
(default)
12 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Nokia Parameters Related to Capability Update RequirementThe Nokia default setting for the IE Capability Update Requirement derivates
from the default values in the UMTS standard:
• UE radio access FDD cap. - Boolean value = TRUE • UE radio access TDD cap. - Boolean value = FALSE• System specific capability update requirement list (not used in RAN1, in
RAN1.5 system specific capability update requirement is always required from GSM system)
• System specific capability update requirement (not used in RAN1, used in RAN1.5): - static value = GSM
13 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message
UERNC
RRC Connection Setup ( )
RRC layer
PHY
MAC
RLC
PDCP BMC
Radio Bearer
LogCH
TrCH
PhyCH
NAS Signalling user plane
PhyChconfiguratio
n
TrCHconfiguratio
n
RBconfiguratio
n
14 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: RB IEs
UERNC
RRC Connection Setup ( )
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DL
15 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message and RBs
UERNC
RRC Connection Setup ( )
RRCconfiguration
Radio Bearer
LogCH
Radio Link Control• Transfer of user data• Segmentation and reassembly. • Concatenation and padding• Sequence number check• In-sequence delivery of upper layer PDUs• Duplicate detection• Error correction• Flow control• Ciphering• Protocol error detection and recovery
(adopted from TS 25.322 V3.12.0)
16 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RLC Modes of Operation
Transparent Mode (TrM)
• data transfer• segmentation &
reassembly
Unacknowledged Mode (UM)
• data transfer• segmentation &
reassembly• sequence control• ciphering• SDU discard
AcknowledgedMode (AM)
• data transfer• segmentation &
reassembly• sequence control• ciphering• SDU discard• error correction• flow control• in-sequence delivery
RLC
Radio Bearer
AM
UM
TrM
BCCH
PCCH
CCCH
UL
DL
CTCH
DCCH
DTCH
Common LogCH Dedicated LogCH
17 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Signalling Radio Bearers
RNC
Radio Bearer
LogCH
NAS Signalling
RRC layer
MAC
RLCUL: TrMDL: UM
RB1
CCCH
RLCUL & DL
UM
RB2
DCCH
RLCUL & DL
AM
RB3
DCCH
RLCUL & DL
AM
RB4
DCCH
RB0
RLCUL & DL
AM
DCCH
optional
UE
RRC Connection Setup ( )
18 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: RB IEs
UERNC
RRC Connection Setup ( )
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DL
Signalling RBinformationto setup list
Signalling RBInformation
to setup
3 / 4
RB identity
CHOICE RLC info type
RLC info
Same as RB
RB mapping info
1..32values 1..4for signallingbearers only
Uplink anddownlink RLCmode
RB (LogCH) inTrCH mappingdescription
19 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: TrCH IEs
UERNC
RRC Connection Setup ( )
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DL
20 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Medium Access Control (MAC) Tasks
UERNC
RRC Connection Setup ( )
TrCHs
MA
C t
asks
• Mapping between TrCHs and LogCHs• Transport Format (TF) selection• Priority handling between data flows
of one UE and between Ues (= dyn. scheduling)• UE identification on common TrCHs• TrCH type switching• De-/multiplexing between LogCHs and TrCHs• Traffic volume measurements• Ciphering (transparent mode)• ASC selection for RACH and CPCH
LogCHs
RRCconfiguration
21 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RLC
RB5
DCCH
RLC
RB7
DTCH
RLC
DTCH
RB3
0 1 0 1 0 1
MAC
Medium Access Control (MAC) Tasks
Radio Bearer
LogCH
RLC
RB5
DCCH
RLC
RB7
DTCH
RLC
DTCH
RB3
0 1 0 1 0 1
MAC
TrCH
MAC PDU
MAC Header
RLC PDU
Example:
Defined by TFS
22 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
IE: Transport Format Set (FDD mode) for dedicated TrCHs
• TTI• Channel Coding• CRC size• Rate matching
• RLC Size • Number of Transport Blocks
Transport Format SetSemi-Static Part
Dynamic TF Information
• RLC Size • Number of Transport Blocks• RLC Size
• Number of Transport Blocks• RLC Size • Number of Transport Blocks• RLC Size
• Number of Transport Blocks
allowed TFson this dedicatedTrCH MAC
TrC
H
• All• Configured
(see IE RB mapping info, if present)• Explicit List
- RB Identity (1..32)- LogicalChannel (0..1)
Logical Channel combination optionsRB ID
RLC
RB ID
LogCH
RLC
LogCH
0 1 0 1
23 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: TrCH IEs
UE
RRC Connection Setup ( )
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DL
Added or ReconfiguredTrCH information list
UL Transport channelinformation common forall transport channels
Added or ReconfiguredUL TrCH information
uplink
1 to maxTrCH (32)(max. allowed TrCHsin one direction)
• UL TrCH type (DCH)• UL TrCH identity• TFS
RNC
PRACH TFCS
TFC subset
UL DCH TFCS
CHOICE FDD
(should not be usedsince TS25.331 V3.7.0)
(OP)
Minimum allowed TFC index /Allowed TFC list /Restricted TrCH information /Full TFC set (= default)
Indicates allowed combinations of already defined TFs and their TFCI values
24 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: TrCH IEs
UE
RRC Connection Setup ( )
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DL
Added or ReconfiguredTrCH information list
DL Transport channelinformation common forall transport channels
Added or ReconfiguredDL TrCH information
downlink
RNC
SCCPCH TFCS
Explicit
SameAsUL
CHOICE FDD
(should not be usedsince TS25.331 V3.8.0)
(OP)
DL DCH TFCS
(no data)
1 to maxTrCH (32)(max. allowed TrCHsin one direction)
• DL TrCH type (DCH)• DL TrCH identity• TFS• DCH quality target
(BLER quality value on a log10 scale: -6.3..0, step size: 0.1)
25 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: PhyCH IEs
UERNC
RRC Connection Setup ( )
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DL optional:UARFCN uplink and downlinkdefault: operating band
Frequency Info
UL radio resources
DL radio resources
26 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Physical Layer Tasks
UERNC
RRC Connection Setup ( )
RRCconfiguration
TrCHs
PhyCHs
Ph
ysic
al Layer
TasksFor TrCHs:
• Error detection• FEC encoding/decoding• De-/multiplexing of CCTrCHs and PhyCHs
WCDMA related tasks:• Frequency and time synchronisation• Radio measurements• Inner - loop PC• De-/modulation and de-/spreading of PhyCHs
• Mapping of CCTrCHs in PhyCHs• Rate matching of CCTrCHs in PhyCHs
• Power weighting and PhyCHs combining• Macrodiversity and SHO
27 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: PhyCH IEs for UL
UERNC
RRC Connection Setup ( )
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DL Frequency Info
UL radio resources
DL radio resources
Maximum allowedUL TX power
CHOICE channel requirement
Uplink DPCH info CPCH SET info
-50..33 dBm(default: existing max. UL TX power)
(OP)
28 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: Uplink DPCH info
Uplink DPCH info
Uplink DPCHpower control info
TFCI existence
Spreading factor
Number of DPDCH
Scrambling codenumber
Scrambling codetype
Puncturing Limit
Number of FBI bits
CHOICE FDDlong / short
1.. maxDPDCH (=6)(default: 1)
4, 8, 16, 32, 64, 128, 256
0 .. 16,777,215
TRUE / FALSE(default: TRUE)
1 / 2 bits
0.40 .. 1(step size: 0.04)
OP
-164 .. –6 dB(step size: 2dB)
0 .. 7 frames
0 .. 7 frames
algorithm 1 / algorithm 2
1 dB / 2 dB(if algorithm 1)
DPCCHpower offset
PC Preamble
SRB Delay
TPC step size
Power ControlAlgorithm
if FDD
29 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: PhyCH IEs for DL
UERNC
RRC Connection Setup ( )
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DL Frequency Info
UL radio resources
DL radio resources
Downlink informationcommon for all
radio links
Downlink infor-mation for each
radio link
1..MaxRL (8)Downlink information
per radio link list
(OP)
30 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: PhyCH IEs for DLDownlink information
common for allradio links
Uplink DPCH infocommon for all RL
SSDT information
TX Diversity Mode
DPCH compressedmode info
CHOICE FDD
Downlink DPCH infocommon for all RL
Timing Indication
CFN-targetSFN frame offset
Downlink DPCH powercontrol information
CHOICE FDD
Fixed or Flexible Position
Downlink rate matchingrestriction information
Power offset PPilot-DPDCH
Spreading factor
TFCI existence
CHOICE SF
Number of bits for Pilot bits- if SF = 256: 2 / 4 / 8- if SF = 128: 4 / 8
Single TPC (DPC_Mode = 0) /TPC triplet in soft (DPC_Mode =1)
Initialise / Maintain
0..255
0..6 dB, step size 0.25
4..512
TRUE / FALSE
Fixed / Flexible
Lists TFI of DCHs & DSCHs, which have DL rate matching restrictions;rate matching should be done onTFCs of „DL TFCS with no restrictedTransport Channel“
requiredfor HO
31 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: PhyCH IEs for DLDownlink infor-mation for each
radio link
Downlink DPCH infofor each RL
Primary CPICH info
PDSCH withSHO DCH Info
CHOICE FDD
PDSCH code mapping
SCCPCH Informationfor FACH
Downlink DPCH infofor each RL
Primary CPICH usagefor channel estimation
DPCH frame offset
Secondary CPICH info
DL channelisation code
SSDT Cell Identity
Closed loop timingadjustment mode
Secondaryscrambling code
Spreading factor
Code number
Scrambling codechange
TPC combination index
(OP)Downlink DPCH infofor each RL
PCPICH may be used /shall not be used
0..38144 (step size 256; = DPCH,n)
1 to maxDPCH-DLchan (8)
4..512
0..SF-1
code change / no code change
(alternative scrambling codefor compressed mode with SF/2?)
1..15 (Secondary scrambling code)0..255 (Channelisation code)
0..511(primary scrambling code)
(MP)
32 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup message: PhyCH IEs for DLDownlink infor-mation for each
radio link
Downlink DPCH infofor each RL
Primary CPICH info
PDSCH withSHO DCH Info
CHOICE FDD
PDSCH code mapping
SCCPCH Informationfor FACH
Downlink DPCH infofor each RL
Secondary scramblingcode
STTD indicator
Spreading Factor
Code number
Timing offset
Fixed or FlexiblePosition
Pilot symbol existence
1 to maxFACHPCH (8)(max of FACHs and PCHsmapped on one S-CCPCH)
1 to maxSIB-FACH (8)(max number of referencesto SIB on one FACH)
Secondary CCPCH info
TFCS
FACH/PCH information
TFS
Transport channelidentity
CHOICE FDD
References to systeminformation blocks
Schedulinginformation
SIB typeSIBs only
CTCH indicator
SCCPCH Informationfor FACH
33 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Nokia Aspects Related to the Physical Layer• The IE „Maximum allowed UL TX power is not used in RAN1. In RAN1, the same value of
the UL TX power is used as is conveyed in the system information. That is why this value is not conveyed in this message.
• The DSCH does not exist in RAN1 and RAN1.5
34 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Part IVRRC Connection Setup Complete
35 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup Complete message
UERNC
RRC Connection Setup Complete ( )
UE IEs
Other IEsRRC Transaction ID
START list
CN domainidentity
START
UE radio accesscapability
UE radio accesscapability extension
• Release 99• Capabilities: PDCP, RLC, TrCH,
FDD RF, TDD RF, PhyCH, UE multi-mode/multi-RAT,security, UE positioning, measurement
0..3
1..maxCNdomains (4)
CS domain / PS domain
used to initialise the 20 MSBs of all hyperframe numbers
OP
UE system specificcapability
Inter-RAT UEradio access
capability
1 to InterSysMessages (4)
GSM MS Classmark 2 /GSM MS Classmark 3
OP
36 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Nokia Aspects Related to RRC Connection Setup CompleteThe UE can return its capabilities to the S-RNC with the IE Radio Access Capability, which
contains• Transport channel capability: is distributed to the resource manager and to the admission
control entity• RF capability: the RF capability is distributed to the resource manager, the power control
entity and to the handover control entity• Physical channel entity: is distributed to resource manager• UE multi-mode/multi-RAT capability: in RAN1 not distributed• Security capability: in RAN1 not distributed• LCS capability: in RAN1 not distributed• Measurement capability: is distributed to the handover control entity. Presence is
mandatory if IE Multi-mode capability has the value "FDD" or "FDD/TDD" and a FDD capability update has been requested in a previous message. Otherwise this field is not needed in the message.
Among the optional other information elements, we find the Inter_RAT UE access capability, which is also not used in RAN1. The RNC shall extract the inter-system message from the UE CAPABILITY INFORMATION message and transfer it to the handover control entity.
37 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Part VRRC Connection Setup Timer
38 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Establishment Timing
RRC Connection Request transmissionV300 = 1; T300 started
RRC Connection Setupmessage received withinitial UE identity
RRC Connection Request transmissionV300 = V300 + 1; T300 started
T300 expiry orcell reselection
V300 N300
no
no
noyes
RRC Connection Setup Completetransmission
RRC connection establishmentaborted, UE enters RRC idle mode
T300: default value = 1000 msN300: default value = 3
39 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection ReleaseUE RNC
RRC Connection Release [RLC-UM, DCCH]
[RLC-UM, DCCH] RRC Connection Release Complete
[RLC-UM, DCCH] RRC Connection Release Complete
UE RNC
RRC Connection Release [RLC-UM, DCCH]
[RLC-AM, DCCH] RRC Connection Release Complete
UE RNC
RRC Connection Release [RLC-UM, CCCH]
CELL_DCH state
N308 times inT308 time intervals
CELL_FACH state;
DCCH available
CELL_FACH state;DCCH
unavailable
40 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RRC Connection Setup Timer• RNC: T300
The RRC Connection Request retransmission timer (MS timer). This parameter is part of SIB 1.[100, 200, 400, 600, 800, 1000, 1200, 1400, 1600, 1800, 2000, 3000, 4000, 6000, 8000] ms; default: 3000 ms.
• RNC: N300The RRC Connection Request retransmission counter (MS counter). This parameter is part of SIB 1.[0 ... 7]; default: 3.
• RNC: T308The RRC Connection Release Complete retransmission timer. This parameter is part of SIB 1.[40, 80, 160, 320]ms; default: 160ms.
• RNC: N308This counter is used to define the maximum number of retransmissions of the RRC CONNECTION RELEASE COMPLETE message by the MS when the MS is in CELL_DCH state.[1 ... 8]; default: 2.
41 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Part VIRB Control Procedures
42 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Physical Channel Reconfiguration
MAC
PHY
RRC
configura
tion
PhyCHs
RLC
PDCP/BMC
UE RNCPhysical Channel Reconfiguration [RLC-AM/UM, DCCH]
Physical Channel Reconfiguration Complete [RLC-AM, DCCH]
UE RNCPhysical Channel Reconfiguration [RLC-AM/UM, DCCH]
Physical Channel Reconfiguration Failure [RLC-AM, DCCH]
on existingRBs
43 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
Transport Channel Reconfiguration
MAC
PHY
RRC
configura
tion
PhyCHs
RLC
PDCP/BMC
UE RNCTransport Channel Reconfiguration [RLC-UM/AM, DCCH]
Transport Channel Reconfiguration Complete [RLC-AM, DCCH]
UE RNCTransport Channel Reconfiguration [RLC-UM/AM, DCCH]
Transport Channel Reconfiguration Failure [RLC-AM, DCCH]
on existingRBs
TrCHs
44 © NOKIA topic: RRC Connection Establishment/ July 2003 /Markus Wimmer
RB Setup, Reconfiguration, and Release
MAC
PHY
RRC
configura
tion
PhyCHs
RLC
PDCP/BMC
UE RNCRadio Bearer Setup [RLC-AM/UM, DCCH]
UE RNCRadio Bearer Reconfiguration [RLC-AM/UM, DCCH]
TrCHs
RB
• Radio Bearer Setup Complete [RLC-AM, DCCH]
• Radio Bearer Setup Failure [RLC-AM, DCCH]
• Radio Bearer Reconfiguration Complete [RLC-AM, DCCH]
• Radio Bearer Reconfiguraiton Failure [RLC-AM, DCCH]
UE RNCRadio Bearer Release [RLC-UM/AM, PCCH]
• Radio Bearer Release Complete [RLC-AM, DCCH]• Radio Bearer Release Failure [RLC-AM, DCCH]