02 01 Rn33022en10gla00 Cs Call Setup

Radio Access Network Signalling
CS Call Setup
Nokia Siemens Networks
RN33022EN10GLA00 CS Call Setup
Objectives
Understand step-by-step CS service establishment.
Describe important parameters in the RRC connection, Service
Request and RAB setup phases.
Understand transport network layer setup to support CS service.
Content
Overview of CS Call Setup.

RRC Connection Phase
Transport Network Layer Setup.
Example of Transport Network Layer Setup Signalling
Iu-CS Call Setup
Link of Signalling Messages
Overview of CS Call Setup
Overview of CS Call Setup
Mobile Terminated Call (MTC)
Mobile Originated Call
Paging
RRC
Connection
Service
Request
Radio
Access
Bearer
L3 Call Setup
In case of a mobile terminated call (MTC), the process starts with paging. Paging is the
procedure by which a mobile network attempts to locate the UE within its location area
before any other network-initiated procedure can take place.
If the UE originates the call, paging is not needed and the UE directly requests RRC
connection setup.
After having established an RRC connection, the UE starts setting up a signalling
connection to the CN. For that, a new radio link is needed.
Finally, the radio access bearer setup procedure builds a radio access bearer service
between the UE and the core network (CN), and the call is established.
Paging
UE in idle mode is only known by CN
RLC
RLC: :TM
TM
Logical
LogicalChannel:
Channel:PCCH
PCCH
UTRAN
UE
based on last location update.

CS core page UE within a location
area (LA). This is a paging type 1.
Paging message is delivered to UE by
RRC.
PAGING TYPE 1
RRC
RRC
UE IE
Other IE (optional)
Paging record
CN identity
Paging cause:
CN domain Identity:
CN paged UE Identity:
i.e. BCCH modification info
This procedure is used to transmit paging information to selected UEs in idle mode using
the paging control channel (PCCH). Upper layers in the network may request paging, to
e.g. establish a signalling connection. In addition, UTRAN may initiate paging to trigger
reading of updated system information.
For CN originated paging, UTRAN should set the IE "Paging cause" to the cause for
paging received from upper layers. If no cause for paging is received from upper layers,
UTRAN should set the value "Terminating cause unknown".
When the UE receives a PAGING TYPE 1 message, it shall compare the IE "UE identity"
with all of its allocated CN UE identities. When they are match, UE must indicate
reception of paging and forward the IE "CN domain identity", the IE "UE identity" and the
IE "Paging cause" to the upper layers. Otherwise, UE may ignore the paging.
RRC Connection Establishment

To establish signalling connection between UE and RAN.
UTRAN
UE
RRC CONNECTION REQUEST

RRC
RRC
RRC CONNECTION SETUP

RRC
RRC
RRC CONNECTION SETUP COMPLETE

RRC
RRC
Successful operation of RRC connection

establishment
The UE shall initiate the procedure when upper layers in the UE requests the
establishment of a signalling connection and the UE is in idle mode (no RRC connection
exists).
Both entities, UE and UTRAN, need to set certain timers during this procedure to
determine retransmission needed or initiate failure case.
Service Request
Request a service from CN
UE
CN
UE
L3
L3
CM SERVICE REQUEST
CM SERVICE REQUEST
L3
CN
L3
Authentication and Ciphering Procedure
CM SERVICE ACCEPT
L3
L3
Explicit operation
10
L3 Call Setup Procedure
Implicit operation
Call Setup
Common call setup signalling flow for GSM and 3G.
RAB assignment in RAN is done after CALL PROCEEDING
message.
CN
UE
SETUP ( )
L3
L3
CALL PROCEEDING
ALERTING
L3
CONNECT
L3
L3
11
CONNECT ACKNOWLEDGE
L3
L3
L3
L3
L3
RAB Assignment
The CN may request the RNC to:
Establish
Modify*
Release
One or several RABs with one RAB
ASSIGNMENT REQUEST message.
CN
RNC
RAB ASSIGNMENT REQUEST
RANAP
RANAP
RAB ASSIGNMENT RESPONSE

RANAP
RANAP
RAB ASSIGNMENT RESPONSE**

RANAP
RANAP
Successful operation
**RU10
RU10support
supportRAB
RABmodification
modificationfor
forPS
PSNRT
NRTRAB
RAB
****There
may
be
several
responses
There may be several responses
12
RRC Connection Phase
13
RRC CONNECTION REQUEST Message

UE
RRC
RRC CONNECTION REQUEST (CCCH on RACH)
UE IEs
Initial UE identity
Measurement IEs
Establishment cause
Protocol error
indicator
Originating
OriginatingConversational
ConversationalCall,
Call,
Originating
OriginatingBackground
BackgroundCall,
Call,
Terminating
TerminatingStreaming
StreamingCall,
Call,
Emergency
EmergencyCall,
Call,
Inter-RAT
cell
reselection,
Inter-RAT cell reselection,
Registration,
Registration,
Detach,
Detach,
Originating
OriginatingHigh
HighPriority
PrioritySignalling,
Signalling,
Call
reestablishment,
Call reestablishment,
Terminating
Low
Priority
Signalling,
Terminating Low Priority Signalling,
14
RNC
Node B
MSS/MGW
RRC
CHOICE
IMSI
TMSI & LAI
P-TMSI & RAI
IMEI
SRNC
Admission Control
Select Transport
Channel
Allocate RNTI
The UE initiates set-up of an RRC connection by sending RRC message Connection Request on
CCCH.
Important parameters: Initial UE Identity, Establishment cause, Measured CPICH Ec/N0.
UL-CCCH-Message
message
rrcConnectionRequest
initialUE-Identity
imsi
Digit: 5
Digit: 2
Digit: 0
Digit: 0
Digit: 5
Digit: 1
Digit: 0
Digit: 0
Digit: 0
Digit: 0
Digit: 0
Digit: 0
Digit: 0
Digit: 1
Digit: 8
establishmentCause: originatingConversationalCall
protocolErrorIndicator: noError
measuredResultsOnRACH
currentCell
modeSpecificInfo
fdd
measurementQuantity
cpich-Ec-N0: 44
RADIO LINK SETUP REQUEST Message

UE
RRC
RNC
Node B
NBAP
Message Type
Transaction ID
CRNC Communication
Context ID
DL DPCH
Information IEs
DL DPCH
Information IEs
15
RRC
RADIO LINK SETUP REQUEST
Message Discriminator
MSS/MGW
NBAP
DCH Information
DSCH Information
TFCI2 bearer
information IEs
RL Information IEs
Transmission Gap
Pattern Sequence
Information
Active Pattern
Sequence Info
The SRNC decides to use a DCH for this RRC connection, allocates RNTI and radio
resources for the RRC connection. When a DCH is to be set-up, RADIO LINK SETUP
REQUEST message is sent to Node B.
Parameters: Cell id, Transport Format Set, Transport Format Combination Set, frequency,
UL scrambling code, Power control information.
RADIO LINK SETUP RESPONSE Message

UE
RRC
RNC
Node B
NBAP
NBAP

RADIO LINK SETUP RESPONSE
MSS/MGW
RRC
NBAP
NBAP
CRNC Communication Context ID

NodeB Communication Context ID
Radio Link Information List
Radio Link Information Item
DCH List RL Setup Response
16
Node B allocates resources, starts PHY reception, and responses with NBAP message
Radio Link Setup Response.
Parameters: Signalling link termination, Transport layer addressing information (AAL2
address, AAL2 Binding Identity) for the Iub Data Transport Bearer.
ERQ and ECF Messages

UE
RRC
RNC
Node B
NBAP
NBAP

MSS/MGW
RRC
NBAP
NBAP
ERQ
ALCAP
ALCAP
ALCAP
ECF
ALCAP
ERQ
ERQ==Establishment
EstablishmentRequest
Request
ECF
ECF==Establishment
EstablishmentConfirm
Confirm
17
SRNC initiates set-up of Iub Data Transport bearer using ALCAP protocol. This request
contains the AAL2 Binding Identity to bind the Iub Data Transport Bearer to the DCH. The
request for set-up of Iub Data Transport bearer is acknowledged by Node B.
The Node B and SRNC establish synchronism for the Iub and Iur Data Transport Bearer
by means of exchange of the appropriate DCH Frame Protocol frames Downlink
Synchronisation and Uplink Synchronisation. Then Node B starts DL transmission.
DL and UL SYNCHRONISATION Messages

UE
RNC
Node B
RRC
RRC
NBAP
NBAP

NBAP
NBAP
ERQ
ALCAP
ALCAP
ALCAP
ECF
ALCAP
DL SYCH
DCH-FP
DCH-FP
Start
StartTx
Tx
18
DCH-FP
UL SYNCH
DCH-FP
MSS/MGW
RRC CONNECTION SETUP Message

UE
RRC
RNC
Node B
NBAP
NBAP

MSS/MGW
RRC
NBAP
NBAP
ERQ
ALCAP
ALCAP
DCH-FP
DCH-FP
RRC
19
ALCAP
ECF
DL SYCH
UL SYNCH
RRC CONNECTION SETUP (CCCH on FACH)
ALCAP
DCH-FP
DCH-FP
RRC
Message RRC Connection Setup is sent on CCCH from SRNC to UE.

Parameters: Initial UE Identity, RNTI, Capability update Requirement, Transport Format
Set, Transport Format Combination Set, frequency, DL scrambling code (FDD only), Time
Slots (TDD only), User Codes (TDD only), Power control information.
Let us assume, that the S-RNC accepts the UEs RRC Connection Establishment
request. It starts an interaction with the Node B to establish a radio link connection over
the interface Iub. This interaction is also used to inform the Node B about the radio link
configuration parameters for uplink and downlink transmission via the interface Uu. In
other words, the Node B is fully prepared to serve as intermediate mode between the
mobile phone and the RNC.
The UE gets the radio link configuration parameters with the RRC Connection Setup
message, which is transmitted in the transport channel FACH. This message is used to
establish signalling radio bearers between the UE and the RNC. The message itself holds
4 information elements groups:
UE information elements to identify the UE.
Radio bearer information elements, which specify the properties of the signalling
bearers, which are established with this RRC message.
Transport channel information elements to define the transport channel
characteristics, in other words the TFCS.
Physical Channel information elements, which specify parameters relevant for the
PHY layer to make the physical channels available.

UE
RNC
Node B
RRC
UE IEs
Initial UE ID
RB IEs
RRC Transaction ID
MSS/MGW
RRC
IMSI / TMSI and LAI /
P-TMSI and RAI/ IMEI
0..3
TrCH IEs: UL/DL

PhyCH IEs: UL/DL
Signalling RB
information
to setup list
Activation Time
New U-RNTI
absolute CFN (0..255); default: now

RNC-ID , S-RNTI
(optional)
RB identity
Signalling RB
Information
to setup
New C-RNTI
RRC State Indicator
UTRAN DRX cycle
length coefficient
CHOICE RLC
info type
Capability update
requirement
RLC info
Same as RB
CELL_DCH/CELL_FACH/
CELL_PCH/URA_PCH
3..9
UE radio access FDD: TRUE/FALSE
UE radio access TDD: TRUE/FALSE
enumerated: GSM (optional)
RB mapping info
20
Initial UE ID: The common transport channel FACH is used to send the RRC Connection
Setup message from the RNC to the UE. All UEs listening to the same FACH bearing SCCPCH must be capable to detect, whether the RRC message is for them. For UE
identification, the IMSI or TMSI and LAI can be used.
RRC Transaction ID: Several RRC transactions can run in parallel. This number
associates the message to one transaction.
Activation Time: The transmission of transport channel frames has to be
synchronised between the UE and the S-RNC. This is also called L2 synchronisation.
The Connection Frame Number (CFN) is an element of the L2 synchronisation. The
network has to make sure, that the UE gets a radio frame with a specific CFN
(approximately) To = 1024 chips before is starts to send a radio frame with the same
CFN. The Activation Time indicates, when the UE can expect the transmission to
start.
New U-RNTI and New C-RNTI: Common transport channels are shared resources,
which can be used by several UEs. The MAC-layer will add the required addressing
information U-RNTI and C-RNTI. UE, SRNC, C-RNC and Node B identify each other
by called Radio Network Temporary Identifiers (RNTI). The S-RNC allocates a SRNTI to the UE to address the UE. When the UE accesses a new cell, the C-RNC
allocates a C-RNTI to the UE, with which it addresses the UE. The U-RNTI is a
concatenation of the SRNTI and the S-RNCs RNC-ID. The U-RNTI is unique
worldwide, and is used by the S-RNC to address the UE on common radio channels,
during paging, etc.
RRC State Indicator: This indicator tells the UE, in which internal RRC connected
sub-state is has to move to.

UE
RNC
Node B
RRC
MSS/MGW
RRC
UE IEs
UL/DL Transport channel
information common for
all transport channels
RB IEs
TrCH IEs: UL/DL
Added or Reconfigured
TrCH information list
PhyCH IEs: UL/DL
Added or Reconfigured
UL/DL TrCH information
Frequency Info
UL radio resources
optional:
UARFCN uplink and downlink
default: operating band
DL radio resources
21
Capability Update Requirement:

The Nokia Siemens Networks 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
Each RB set between a UE and UTRAN has a unique number. Each of them can be
mapped on one or two logical channels. This was part of the RB setup information. The
information carried on radio bearers must be mapped on transport channels. But on which
transport channels can the higher layer information be transmitted? How can higher layer
information be segmented? This is described with the information elements for TrCH
UL/DL. This information is used by the RRC to configure the RLC-, MAC, and PHY layer.
A very important IE is the Transport Format Set. The Transport Format Set information
element describes the the allowed TFs, which can be transmitted via this TrCH. A TF and
TFS definition can be found in the first module of the course. This information element
also describes, which logical channels (und with them which radio bearers) are mapped
on this TrCH.
The Physical Channel information elements deliver relevant information for the PHY layer
to configure the physical channels. One of the PhyCH IEs is the carrier frequency band,
where the signalling connection is established. As can be seen, a UE can be immediately
re-directed to another frequency band for the signalling bearer setup. Also the available
UL and DL radio resources have to be described.
RRC CONNECTION SETUP COMPLETE Message

UE
RRC
RNC
Node B
NBAP
NBAP

MSS/MGW
RRC
NBAP
NBAP
ERQ
ALCAP
ALCAP
DCH-FP
DCH-FP
RRC
RRC
22
ALCAP
ECF
DL SYCH
UL SYNCH

RRC CONNECTION SETUP COMPLETE (DCCH on DCH)
ALCAP
DCH-FP
DCH-FP
RRC
RRC
Message RRC Connection Setup Complete is sent on DCCH from UE to SRNC.

Parameters: Integrity information, ciphering information.
RRC CONNECTION SETUP COMPLETE Message

UE
RNC
Node B
RRC CONNECTION SETUP COMPLETE (DCCH on DCH)
RRC
UE IEs
RRC Transaction ID
Other IEs
START list
OP
Inter-RAT UE
radio access
capability
1..maxCNdomains (4)
CS domain / PS domain
used to initialise the 20 MSBs of
all hyperframe numbers
START
UE radio access
capability
UE radio access
capability extension
RRC
0..3
CN domain
identity
UE system specific
capability
MSS/MGW
OP
Release 99
Capabilities: PDCP, RLC, TrCH,
FDD RF, TDD RF, PhyCH,
UE multi-mode/multi-RAT,
security, UE positioning,
measurement
1 to InterSysMessages (4)
GSM MS Classmark 2 /
GSM MS Classmark 3
23
The UE has received the RRC Connection Setup message and returns the RRC
Connection Setup Complete message to the S-RNC. This message is transmitted via the
logical channel DCCH on the radio signalling bearer, which offers acknowledged mode of
operation (RB2). The information elements in the RRC Connection Setup Complete
message can be grouped into
UE information elements and
Other information elements.
The UE IEs RRC transaction identifier and the START list elements are mandatory.
The remaining IEs are optional. With the UE radio access capability IE, the UE can
transmit its capabilities, ranging from its layer and channel capabilities to its
measurements and multi-mode capabilities. The optional IE Inter-RAT UE radio access
capability can be use to inform the S-RNC about the UEs cdma2000 and GSM MS
classmarks. If these optional IE can not be use by either the UE or UTRAN, their content
can also be transmitted with the RRC message UE Capability Information.
Transport Network Layer Setup
24
Transport Network Layer Setup

Node-B
UE
NBAP
RNC
Radio Link Setup Response
NBAP
Binding ID
Channel IDs organise the AAL type 2

minipacket flow in the VCC:
CID: 0 ... 7 reserved
CID: 8 ... 255 for external use
Transport Layer Address
ALCAP
Establish Request (ERQ)
ALCAP
Path ID
Channel Identifier (CID)
NSEA-Dest. NSAP Serv. Endpoint Addr.
Signalling Association Identifier
Binding ID
AAL type 2 path ID
ALCAP
Establish Confirm (ECF)
has to be identical at
both ends of a VCC
DAID-Dest. sign. assoc. ident
25
ALCAP
CN
Establish Request
Node-B
UE
Signalling association id that will
generated in the BS .In the
establish request is always 0.
ALCAP
RNC
CN
ALCAP
DAID-Dest. sig. assoc. identifier.
Connection element identifier

contains PATH id & CID number
selected by the RNC.
CEID-Connection element identifier

NSEA Dest NSAPe.g.
service end point add.
AAL2 TP in the WAM of the BS
CPS-SDU bit rate/size
Parameter that define the Max.

and Average bit rate/size of the
CPS in forward & backwards
OSAID-Origin. Sig. Assoc. identifier

SUGR-Served user gen. reference

generated in the RNC .
The field of SUGR reports the
binding ID generated in the BS
and forwarded to the RNC
through the Radio link set up
Response .
ALCAP
DAID-Dest. sig. assoc. identifier.

OSAID-Origin. Sig. Assoc. identifier
RNC & BS
Transport Network is Ready
26
RNC
Collects parameters to
configure the UE
ALCAP
Signalling association identifier
generated in the BS
generated in the RNC .
Binding ID
Binding Identifier (Binding ID) is used to initialise the linkage
between ALCAP and Application Part (RANAP, RNSAP, NBAP)
identifiers.
Binding Identifier can be used both in Radio Network Control plane
Application Part protocols and in Transport Network Control
Plane's ALCAP protocol.
Binding ID binds the Radio and Transport Network Control plane
identifiers together.
27
To ensure maximal independence of those two planes, the Binding ID should be used
only when necessary:
Binding ID shall thus be used only in Radio Network Control plane Application Part
messages in which a new association between the planes is created and in ALCAP
messages creating new transport bearers.
Binding ID for each transport bearer shall be allocated before the setup of that transport
bearer.
The Binding ID is sent on one direction using the Application Part protocol and is returned
in the other direction by the ALCAP protocol.
When an Application Part procedure with an allocated Binding ID is applied for modifying
an existing Radio Network User Plane connection, the decision to use the Binding ID (and
the ALCAP procedures) shall be done by that end of the reference point that decides
whether to use the existing transport bearer or to set up a new transport bearer.
The Binding ID shall already be assigned and tied to a radio application procedure when
the first ALCAP message is received in a node.
The association between the connection Id in the Application Part protocol (e.g. identifying
a RAB) and the corresponding connection Id in the ALCAP protocol (e.g. identifying the
AAL2 channel for that RAB) that was created with the help of Binding ID shall be
memorised by both peers of each reference point for the lifetime of the corresponding
transport bearer.
The Binding ID may be released and re-used as soon as both the Application Part
procedure and the ALCAP procedure that used it are completed in both peers of the
reference point.
Binding ID
Radio Network Control Plane Setup (Response)
AP-1
AP-2
Node1 Transport Address Binding ID
Step 1
ALCAP-1
ALCAP-2
AP-1
Node 1
Step 2
address
Binding ID
ALCAP-1
AP-1
ALCAP Establish request
ALCAP-1
ALCAP-2
AP-2
Step 3
28
AP-2
Transport
Node1 Transport Address Binding ID
ALCAP-2
Step 1: Application Part AP-1 assigns the Binding Identifier and sends a Radio Network
Control Plane Set-up (Response) message (which of the two messages depends on the
involved interface - Iu/Iur or Iub). The message contains the originating node Transport
layer address and the Binding Identifier.
Step 2: As reception of the Radio Network Control Plane Set-up message, the peer entity
AP-2 requests ALCAP-2 to establish a transport bearer. The Binding Identifier is passed
to ALCAP-2.
Step 3: ALCAP-2 sends an ALCAP Establish Request to the peer entity ALCAP-1. The
message contains the Binding Identifier. The Binding Identifier allows correlating the
incoming transport connection with the Application Part transaction in step 1.
AAL2UP without AAL2 Multiplexing

49
BTSID 0WAM0
00123
020
BTSID 0WAM1
123 021
Transport Layer Address Format (A2EA)

1 x AAL2 VCC: 49 + WBTS Identifier + AAL2UPTPId
N x AAL2 VCC: 49 + WBTSId + WAMId + 0
FlexiBTS: 49 + WBTSId + 000
Associate AAL2SIG terminate in same WAM

29
Digit analyses are created by the system for the Iub interface when creating the Routing
and Digit analysis for the AAL2 connections (COCO object creation/modification or WBTS
creation/modification). It is also possible to give the numbering manually.
The system automatically adds the used AFI (authority and format identifier) to the
beginning of the digit sequence when the numbering generation option is used.
One AAL2 VCC for WAM RAN1.5.2ED2 level A2EA generation rule:
"49" (AFI) + 5 digits (WBTS Identifier) + 3 digits (AAL2UPTPId)
The address is generated from the corresponding WBTS id and AAL2 user plane TP id.
For example, the A2EA for the WBTS id 144 with AAL2 tp id 5 would be 4900144005.
Several AAL2 VCCs for WAM RAN04 level A2EA generation rule:
"49" (AFI) + 5 digits (WBTSId) + 2 digits (WAMId) + 1 digit "0" (filler)
The address is generated from the corresponding WBTS id and WAM id. For example,
the A2EA for the WBTS id 12448 with WAM id 3 would be 4912448030.
One A2EA for BTS (Flexi BTS) generation rule:
"49" (AFI) + 5 digits (WBTSId) + 3 digits "0" (filler)
The address is generated from the corresponding WBTS id. For example, the A2EA for
the WBTS id 1244 would be 4901244000.
The length of the digit sequence will be 40 in the system. The additional characters at the
end of the digit sequence are filled with 0xF when the digit is stored to the system.
AAL2UP with AAL2 Multiplexing

BTSID 00AAL2SIG TPID
123 001
30
AAL2UP without AAL2 Multiplexing

ZRII;
ZRII;
TREE=1
TREE=1 ATYPE=N
ATYPE=N
DIGITS
DIGITS
4900123020
4900123020
4900123040
4900123040
4900123060
4900123060
AL
AL NBR
NBR
00
22
00
33
00
44
RT
RT CT
CT SP
SP NL
NL RC
RC
ROU
NGC
0
ROU NGC 0 00 APR
APR
ROU
ROU NGC
NGC 00 00 APR
APR
ROU
NGC
ROU NGC 00 00 APR
APR
DEST
DEST
33
66
88
SDEST
SDEST
33
55
66
TREE=2
TREE=2 ATYPE=N
ATYPE=N
DIGITS
DIGITS
456618190111
456618190111
AL
AL NBR
NBR
00 100
100
RT
RT CT
CT SP
SP NL
NL RC
RC
ROU
NGC
0
ROU NGC
0 00 APR
APR
DEST
DEST
10
10
SDEST
SDEST
44
COMMAND
COMMAND EXECUTED
EXECUTED
31
OSAID and DSAID
32
Cause (CAU)
Gives the reason of an operational error
Describes the reason for the release of connection
Indicates the reason why connection could not established
Connection element identifier (CEID)
It consists of AAL type 2 path identifier and Channel identifier (CID).
AAL type 2 path identifier has field size of 4 octets. A value of 0 in all octets indicates
Null.
Channel identifier has field size of 1 octet. It can have value in the range of 8 to 255.
A value of 0 indicates Null.
AAL type 2 service endpoint address (A2EA)
It carries end point address of the destination.
It can have E.164 or NSAP format.
Transport Layer Setup IP Option

UE
RNC
Node B
RRC
NBAP
NBAP

RRC
NBAP
NBAP
Binding ID
BTS Transport IP Address
No ALCAP
RRC
33
RRC
MSS/MGW
RADIO LINK SETUP RESPONSE IP Option
BTS Info:
bts_id
iub_dig_tree = 0 (non existent)
crnc_cc_id
node_b_cc_id
transport_layer_addr [20 bytes]

prefix 35 00 01
IP address 0A 3C 18 4A
10 . 60 . 24 . 74
34
Example of Transport Network Layer Setup

Signalling
35
Review of Transport Network Layer Setup

UE
Node-B
NBAP
RNC
NBAP
Binding ID
ALCAP
ALCAP
Path ID
NSEA-Dest. NSAP Serv. Endpoint Addr.
Signalling Association Identifier
Binding ID
ALCAP
DAID-Dest. sign. assoc. ident

36
ALCAP
CN
RADIO LINK SETUP RESPONSE Message

NBAP-PDU
successfulOutcome
- procedureCode: 9
- criticality: reject
- messageDiscriminator: common
successfulOutcome
RadioLinkSetupResponse
protocolIEs
- id: 43
- criticality: ignore
CRNC-CommunicationContextID: 1033
- id: 73
NodeB-CommunicationContextID: 160010
- id: 111
RadioLinkInformationList-RL-SetupRsp
- id: 101
RadioLinkInformationItem-RL-SetupRsp
- rL-ID: 1
- diversityIndication: mdc-is-done-at-rnc
dCH-Information-RL-SetupRsp
- id: 52
DCH-List-RL-SetupRsp
DCH-List-Item-RL-SetupRsp
- dCH-ID: 24
- bindingID: '00000003'H
transportLayerAddress
- non-extended:
'4900123020FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF'H
- id: 142
Binding ID and
Transport Layer
TrafficTP-ID: 1
Address
37
ESTABLISHMENT REQUEST (ERQ) Message

ERQ - ESTABLISH REQUEST
DAID-Dest. sign. assoc. ident.: 00 00
00 00
- Message's Compatibility: 00h
Pass-on not possible:
- Do not send notification
- Pass on message or parameter
General action:
CEID-Connection element ident.
- Parameter's Compatibility: 00h
General action:
Parameter length: 5 (05h)
- Path identifier: 1001 (3E9h)
- Channel identifier: 12 (Ch)
Path ID and CID
38
NSEA-Dest. NSAP serv. endpoint addr.

- Discard parameter
General action:
Transport Layer
Address
- Address: 49 00 12 30 20 FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF
LC-Link Charactreristics
General action:
Link QoS
Parameter length: 12 (0Ch)
- Maximum forward CPS-SDU bit rate: 312 (138h)
- Maximum backwards CPS-SDU bit rate: 334 (14Eh)
- Average forward CPS-SDU bit rate: 300 (12Ch)
- Average backwards CPS-SDU bit rate: 325 (145h)
- Maximum forward CPS-SDU size: 24 (18h)
- Maximum backwards CPS-SDU size: 26 (1Ah)
- Average forward CPS-SDU size: 24 (18h)
- Average backwards CPS-SDU size: 26 (1Ah)
OSAID-Orig. sign. assoc. ident.

General action:
OSAID
- Signalling association identifier: 45
10 1A 00
SUGR-Served user gen. reference
General action:
- Field: 00 00 00 03
Binding
ID
ESTABLISHMENT CONFIRM (ECF) Message

ECF - ESTABLISH CONFIRM
DAID-Dest. sign. assoc. ident.: 45 10 1A 00
- Message's Compatibility: 00h
General action:
OSAID-Orig. sign. assoc. ident.
General action:
- Signalling association identifier: 00 00 00 09
39
Signalling and Counters (Reference)
40
The following topic discuss the relation between KPI counters and signalling flow as a
reference only.
KPI analysis or optimization will not discuss in this training
RRC Connection Sub-phases (1/2)
Paging
RRC
Connection
Setup Access
41
Radio
Access
Bearer
Service
Request
Active
To evaluate the RRC performance, it is divided into sub phases as shown in the slide. They are:
RRC setup phase
RRC Access phase
RRC Active phase
RRC Connection Sub-phases (2/2)

UE
RRC
RNC
Node B
RRC
RRC_CONN_STP_ATT = N + 1
Setup
RRC
RRC CONNECTION SETUP
RRC
RRC_CONN_STP_COMP = N + 1
Access
RRC
RRC CONNECTION SETUP COMPLETE
RRC
Active
42
RRC Setup Phase

The RRC Setup phase begins when the RNC receives the RRC CONNECTION
REQUEST message from the UE. This triggers the first event: increment of Performance
Indicator for attempted RRC connections, named here as RRC_CONN_STP_ATT.The
sum of measurements equals the total number of RRC connection establishment
attempts.
The Setup phase is completed when the RNC sends the RRC CONNECTION SETUP
message to the UE. At this point event 2: increment of PI RRC_CONN_STP_COMP is
triggered.
RRC Access Phase
RRC Access phase starts from the end of a successful Setup phase, i.e. the transmission
of the RRC CONNECTION SETUP message.
The Access phase is completed when the RNC receives the RRC CONNECTION SETUP
COMPLETE message from the UE. At this point, event 3 is triggered as the
CONN_ACC_COMP Performance Indicator is incremented.
RRC Active Phase
The RRC Active phase begins from the reception of the RRC CONNECTION SETUP
COMPLETE message.
The Active phase is successfully completed when a RANAP message IU RELEASE
COMMAND is received, indicating an intentionally terminated RRC connection. If an
unintentional RRC connection release takes place, the PI RRC_CONN_ACT_FAIL is,
indicating an RRC connection drop.
The active RRC connection can fail for various reasons, e.g. failure in the Iu interface,
pre-emption, i.e. release of resources in order to make room for higher priority RAB such
as emergency call, or failure due to air interface or Node B.
RRC Connection Performance Analysis

Setup phase
Access phase
Active phase
Active
Access
complete
Setup
Attempts
complete
complete
Active
Release
Active
Failures
Success
Drop
Access
Failures
Setup Failures
Setups Failures
, Blocking
43
NOTE: Aim of This Slide

is to give example of relation between KPI counters
and signalling flow.
KPI analysis or optimization will not discuss in this
training
RRC Setup Phase

The RRC Setup phase begins when the RNC receives the RRC CONNECTION REQUEST
message from the UE.
This triggers the first event: increment of Performance Indicator for attempted RRC connections,
named here as RRC_CONN_STP_ATT.
The sum of measurements equals the total number of RRC connection establishment attempts.
The Setup phase is completed when the RNC sends the RRC CONNECTION SETUP message to
the UE.
At this point event 2: increment of PI RRC_CONN_STP_COMP is triggered.
RRC Access Phase
RRC Access phase starts from the end of a successful Setup phase, i.e. the transmission of the
RRC CONNECTION SETUP message.
The Access phase is completed when the RNC receives the RRC CONNECTION SETUP
COMPLETE message from the UE.
At this point, event 3 is triggered as the CONN_ACC_COMP Performance Indicator is incremented.
RRC Active Phase
The RRC Active phase begins from the reception of the RRC CONNECTION SETUP COMPLETE
message.
The Active phase is successfully completed when a RANAP message IU RELEASE COMMAND is
received, indicating an intentionally terminated
RRC connection. If an unintentional RRC connection release takes place, the PI
RRC_CONN_ACT_FAIL is, indicating an RRC connection drop.
The active RRC connection can fail for various reasons, e.g. failure in the Iu interface, pre-emption,
i.e.
release of resources in order to make room for higher priority RAB such as emergency call, or
failure due to air interface or Node B.

Node-B
UE
RNC
RRC Connection Request
No
Counter
Name
Explanation
M1001C
0
RRC
CONN
SETUP
ATT
A number of
RRC connection
setup attempts.
RRC
RRC
Counters RRC CONN SETUP ATT ( Attempt for RRC Setup Causes)
No
Attempt Counter Name
No
M1001C22
MOBILE ORIGINATING CONVERSATIONAL CALL ATTEMPTS
M1001C42
Inter-RAT cell re-selection ATTEMPTS
M1001C24
MOBILE ORIGINATING STREAMING CALL ATTEMPTS
M1001C44
Inter-RAT cell change order ATTEMPTS
M1001C26
MOBILE Originating Interactive Call ATTEMPTS
M1001C46
Registration ATTEMPTS
M1001C28
MOBILE Originating Background Call ATTEMPTS
M1001C48
Detach ATTEMPTS
M1001C30
MOBILE Originating Subscribed traffic Call ATTEMPTS
M1001C50
MOBILE Originating High Priority Signalling ATTEMPTS
M1001C32
MOBILE Terminating Conversational Call ATTEMPTS
M1001C52
MOBILE Terminating High Priority Signalling ATTEMPTS
M1001C34
MOBILE Terminating Streaming Call ATTEMPTS
M1001C54
MOBILE Originating Low Priority Signalling ATTEMPTS
M1001C36
MOBILE Terminating Interactive Call ATTEMPTS
M1001C56
MOBILE Terminating Low Priority Signalling ATTEMPTS
M1001C38
MOBILE Terminating Background Call ATTEMPTS
M1001C58
Call re-establishment ATTEMPTS
M1001C40
Emergency Call ATTEMPTS
M1001C60
Terminating cause unknown ATTEMPTS
44
Attempt Counter Name

RNC
Node-B
UE

RRC
RRC
NBAP Radio Link Setup
Counters of RRC Connection

Setup Failures
SETUP
ALCAP Transport Bearer Setup
RRC
RRC Connection Setup
RRC
No
Counter Name
Explanation
Rejection cause in
RRC Connection
Reject message
M1001C2
RRC CONN SETUP FAIL DUE TO HC
A number of RRC connection setup failures caused by HC.
Unspecified
M1001C3
RRC CONN SETUP FAIL DUE TO AC
A number of RRC connection setup failures caused by AC.
Congestion
M1001C4
RRC CONN SETUP FAIL DUE TO BTS
A number of RRC connection setup failures caused by a BTS.When

the BTS rejects an initial RL setup.
Unspecified
M1001C5
RRC CONN SETUP FAIL DUE TO TRANS
A number of RRC connection setup failures caused by a

transmission.
Unspecified
M1001C6
RRC CONN SETUP FAIL DUE TO RNC INTER

REASONS
A number of RRC connection setup failures caused by RNC's

internal reasons. (e.g. parameter mismatch, timer expiry).
Unspecified
M1001C7
RRC CONN SETUP FAIL DUE TO FROZEN BTS
A number of RRC connection setup failures caused by a frozen

BTS. Frozen BTS means that currently no new RRC connections
are allowed.
Unspecified
45

RNC
Node-B
UE

RRC
RRC
SETUP
RRC
RRC
Counters of RRC Connection

Access Failures
Layer 1 Synchronisation
NBAP Synchronisation
Access
RRC Connection Setup Complete

RRC
46
RRC
No
Counter Name
Explanation
M1001C9
RRC CONN ACC FAIL DUE

TO RADIO INT SYNCH
The number of RRC connection access failures caused by a lack of radio interface
synchronisation. The RRC connection access is considered a failure if the UE loses DL
synchronization before sending RRC Connection Setup Complete message to RNC.
M1001C10

TO UU INT
A number of RRC connection access failures caused by the UU interface. When the RNC does
not receive RRC_CONNECTION_COMPLETE from the UE
M1001C11

TO RNC INTER REASONS
A number of RRC connection access failures caused by RNC's internal reasons. (e.g.
parameter mismatch, timer expiry).

RNC
Node-B
UE

RRC
RRC
SETUP
RRC
RRC
Layer 1 Synchronisation
NBAP Synchronisation
Access
RRC
RRC
RRC: Initial Direct Transfer
No
Counter
Name
Explanation
M1001C8
RRC CONN
ACC COMP
A number of RRC
connection access
completions.
No
Counter
Name
Explanation
M1001C12
RRC CONN
ACTIVE
COMP
A number of RRC
connection active
completions.
RRC
RRC
Active
AAL2 Connection Release
47
Iu-CS Call Setup
48
Service Request Phase
Paging
RRC
Connection
Radio
Access
Bearer
Service
Request
L3 Call Setup
49
In case of a mobile terminated call (MTC), the process starts with paging. Paging
is the procedure by which a mobile network attempts to locate the UE within its
location area before any other network-initiated procedure can take place.
If the UE originates the call, paging is not needed and the UE directly requests
RRC connection setup.
Finally, the radio access bearer setup procedure builds a radio access bearer
service between the UE and the core network (CN), and the call is established.
Iu-CS Call Setup (Service Request)

Node-B
UE
CN
RNC
Initial Direct Transfer
RRC
RRC
CM Service Request
RANAP
Initial UE Message
RANAP
CM Service Request
RANAP
Common ID
RANAP
Security Mode Command

RRC
Uplink Direct Transfer (Set up)
RRC
RANAP
RANAP
Direct Transfer (Setup)

Direct Transfer
RANAP
RANAP
( Call Proceeding)
RRC
50
Downlink Direct Transfer (Call Proceeding)
RRC
Common ID
The purpose of the Common ID procedure is to inform the RNC about the permanent NAS UE
identity (IMSI) of a user. This is used by the RNC, for example, to create a reference between
the permanent NAS UE identity of the user and the Radio Resource Control (RRC) connection
of that user for UTRAN paging coordination. The procedure uses connection-oriented
signalling. The figure below describes the Common ID procedure.
Security Mode Command
The purpose of the Security Mode Control procedure is to allow the CN to pass cipher and integrity
mode information to the UTRAN. The UTRAN uses this information to select and load the
encryption device for user and signalling data with the appropriate parameters, and also to
store the appropriate parameters for the integrity algorithm. The procedure uses connectionoriented signalling
CommonID
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length: 00 01
- id: 23
- contents: 00 17
- contents (in bits): 01
- padding: 000000
- opentype length: 09
PermanentNAS-UE-ID
- extension flag: 0
- iMSI: '62029903000040F1'H
- length (in bits): 101
- padding: 0000
- contents: 62 02 99 03 00 00 40 F1
RAB Setup Phase
RRC
Connection
Paging
Service
Request
Radio
Access
Bearer
L3 Call Setup
51
In case of a mobile terminated call (MTC), the process starts with paging. Paging
is the procedure by which a mobile network attempts to locate the UE within its
location area before any other network-initiated procedure can take place.
If the UE originates the call, paging is not needed and the UE directly requests
RRC connection setup.
Finally, the radio access bearer setup procedure builds a radio access bearer
service between the UE and the core network (CN), and the call is established.
Iu-CS Call Setup (RAB Setup)

UE
Node-B
CN
RNC
RRC Connection & Service Request Phase
MEGACO*
RAB Assignment Request
RANAP
RANAP
Radio Link Reconfiguration Prepare
NBAP
NBAP
Radio Link Reconfiguration Ready
NBAP
NBAP
Establish Request/Confirm
AAL2SIG
AAL2SIG
Establish Request/Confirm
AAL2SIG
AAL2SIG
(RNC and MGW)
Radio Link Reconfiguration Commit

NBAP
NBAP
RRC
RRC
52
Radio Bearer Setup

Radio Bearer Setup complete
RRC
RRC
RANAP
RAB Assignment Response
RANAP
* Before RAC Assignment Request start

In Rel5 MSS use MEGACO send message Add Request to MGW and MGW reply by
message Add Reply
RAB ASSIGNMENT REQUEST ATM Option

RAB-ASSIGNMENT REQUEST
- rAB-ID: '00000001'B
RAB ID
rAB-Parameters
- extension flag: 0
- preamble: 1100100
- trafficClass: conversational
- extension range: 0
- rAB-AsymmetryIndicator: symmetric-bidirectional
maxBitrate
- MaxBitrate: 12200
- contents: 2F A7
guaranteedBitRate
- GuaranteedBitrate: 4750
- padding: 00000
- contents: 12 8E
- deliveryOrder: delivery-order-requested
- maxSDU-Size: 244
- padding: 0000000
RAB QoS
- contents: 00 F4
53
transportLayerInformation
- extension flag: 0
- preamble: 0
- transportLayerAddress:
'010001010000000000000000000000000000000000000110010000
1000010
110001011110000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000'B
- padding: 0000000
- contents
45 00 00 00 00 06 42 16 2F 00 00 00 00 00 00 00 00 00 00 00
iuTransportAssociation
- extension flag: 0
- choice index: 1
- bindingID: '0103054F'H
- padding: 000000
- contents: 01 03 05 4F
Binding ID and
Transport Layer
Address
RAB ASSIGNMENT REQUEST IP Option

RAB-AssignmentRequest
protocolIEs: 1 item
Item 0: id-RAB-SetupOrModifyList
ProtocolIE-Container
id: id-RAB-SetupOrModifyList (54)
criticality: ignore (1)
value
RAB-SetupOrModifyList: 1 item
Item 0
ProtocolIE-ContainerPairList: 1 item
Item 0: id-RAB-SetupOrModifyItem
ProtocolIE-ContainerPair
id: id-RAB-SetupOrModifyItem (53)
firstCriticality: reject (0)
firstValue
RAB-SetupOrModifyItemFirst
rAB-ID: 01 [bit length 8]
rAB-Parameters
trafficClass: conversational (0)
rAB-AsymmetryIndicator: symmetric-bidirectional (0)
maxBitrate: 1 item
Item 0
RAB-Parameter-MaxBitrateList: 12200
guaranteedBitRate: 1 item
Item 0
RAB-Parameter-GuaranteedBitrateList: 4750
deliveryOrder: delivery-order-requested (0)
maxSDU-Size: 244
sDU-Parameters: 3 items
transferDelay: 80
allocationOrRetentionPriority
sourceStatisticsDescriptor: speech (0)
userPlaneInformation
userPlaneMode: support-mode-for-predefined-SDU-sizes (1)
uP-ModeVersions: 0002 [bit length 16]
transportLayerInformation
transportLayerAddress: 3500010A089F9400000000000000000000000000 [bit length 160]
iuTransportAssociation: bindingID (1)
bindingID: 052E0000
secondCriticality: ignore (1)
secondValue
RAB-SetupOrModifyItemSecond
RAB ID
RAB QoS
MGW IP Address
prefix: 35 00 01
IP address: 0A 08 9F 94
10. 8. 159. 148
Binding ID and
Transport Layer
Address
54
55
Node-B
UE
RNC
RRC Connection Setup Request
RRC
CN
RRC
IMSI
RNTI
NBAP
Radio Link Setup Request
NBAP
RNC Communication Context ID
NBAP
RNC Communication Context ID

Node B Communication Context ID
Binding ID
56
NBAP
UE
Node-B
AAL2SIG
RNC
AAL2SIG

OSAID Orig sign assoc idnet.
AAL2SIG
AAL2SIG
OSAID Orig sign assoc idnet.

DAID Dest sign assoc idnet.
RRC
RRC
IMSI
RRC

Data send on CID that allocate on ERQ
57
RRC
CN
CM
SM
MM
Signalling connection
CM
SM
MM
RAB
NAS
AS
RRC connection/ S-RB
RRC
Iu connection
RRC
RANAP
RB
Log Ch
Transp Ch
Phy Ch
WCDMA
Log Ch
Transp Ch
Phy Ch
WCDMA
Log Ch
Transp Ch
Phy Ch
Log Ch
Transp Ch
Phy Ch
Iu-Bearer
NBAP
AAL2SIG
ATM
RANAP
RANAP
AAL2SIG
Iu-cs
RANA
P
MTP3 SL
AAL2SIG
Iu-cs
AAL2UD (Iu-cs)
IPOAUD (Iu-ps)
AAL2 UP
DCH>DCCH
Eg CID 12
UE
58
Martin
Ervens
Nokia Siemens
Networks
WBTS
RACH eg CID 8
FACH eg CID 9
RNC
ATM
CN

02 01 Rn33022en10gla00 Cs Call Setup

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

02 01 Rn33022en10gla00 Cs Call Setup

Transféré par

Droits d'auteur :

Formats disponibles

Radio Access Network Signalling

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

Overview of CS Call Setup.

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

Overview of CS Call Setup

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

Overview of CS Call Setup

Mobile Terminated Call (MTC)

Mobile Originated Call

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

based on last location update.

i.e. BCCH modification info

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

RRC Connection Establishment

RRC CONNECTION REQUEST

RRC CONNECTION SETUP

RRC CONNECTION SETUP COMPLETE

Successful operation of RRC connection

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

L3 Call Setup Procedure

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

RAB ASSIGNMENT RESPONSE

RAB ASSIGNMENT RESPONSE**

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

RRC Connection Phase

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

RRC CONNECTION REQUEST Message

RRC CONNECTION REQUEST (CCCH on RACH)

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

RADIO LINK SETUP REQUEST Message

Nokia Siemens Networks

RADIO LINK SETUP REQUEST

RN33022EN10GLA00 CS Call Setup

RADIO LINK SETUP RESPONSE Message

RADIO LINK SETUP REQUEST

CRNC Communication Context ID

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

ERQ and ECF Messages

RADIO LINK SETUP REQUEST

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

DL and UL SYNCHRONISATION Messages

RADIO LINK SETUP REQUEST

Nokia Siemens Networks

RN33022EN10GLA00 CS Call Setup

RRC CONNECTION SETUP Message

RADIO LINK SETUP REQUEST

Nokia Siemens Networks

RRC CONNECTION SETUP (CCCH on FACH)