02 01 rn33022en10gla00 cs call setup
DESCRIPTION
Cs Call SetupTRANSCRIPT
1 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Radio Access Network SignallingCS Call Setup
4 © 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.
5 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
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
6 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Overview of CS Call Setup
7 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Overview of CS Call Setup
Mobile Terminated Call (MTC)
ServiceRequest
Radio AccessBearer
Paging
Mobile Originated Call
RRCConnection
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 signallingconnection 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.
8 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Paging
• UE in idle mode is only known by CN 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.
UE UTRAN
PAGING TYPE 1RRC RRC
RLC : TMLogical Channel: PCCH
RLC : TMLogical Channel: PCCH
UE IE
Other IE (optional)
i.e. BCCH modification info
Paging recordCN identityPaging cause:CN domain Identity:CN paged UE Identity:
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 theIE "Paging cause" to the upper layers. Otherwise, UE may ignore the paging.
9 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC Connection Establishment
• To establish signalling connection between UE and RAN.
UE UTRAN
RRC CONNECTION REQUESTRRC RRC
RRC CONNECTION SETUPRRC RRC
RRC CONNECTION SETUP COMPLETERRC 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.
10 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Service Request
• Request a service from CN
Explicit operation
UE CN
Authentication and Ciphering Procedure
Implicit operation
L3 Call Setup Procedure
CM SERVICE REQUESTL3 L3
UE CN
CM SERVICE REQUESTL3 L3
CM SERVICE ACCEPTL3 L3
11 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Call Setup
• Common call setup signalling flow for GSM and 3G.• RAB assignment in RAN is done after CALL PROCEEDING
message.
UE CNSETUP ( )
CALL PROCEEDING
ALERTING
CONNECT
CONNECT ACKNOWLEDGE
L3 L3
L3 L3
L3 L3
L3 L3
L3 L3
12 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RAB Assignment
• The CN may request the RNC to:– Establish– Modify*– Release
• One or several RABs with one RAB ASSIGNMENT REQUEST message.
RNC CN
Successful operation
RAB ASSIGNMENT REQUESTRANAP RANAP
RAB ASSIGNMENT RESPONSERANAP RANAP
* RU10 support RAB modification for PS NRT RAB** There may be several responses
* RU10 support RAB modification for PS NRT RAB** There may be several responses
RAB ASSIGNMENT RESPONSE**RANAP RANAP
…
13 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC Connection Phase
14 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC CONNECTION REQUEST Message
UE Node B RNC MSS/MGW
RRC CONNECTION REQUEST (CCCH on RACH)RRC RRC
Allocate RNTI
Select Transport Channel
Admission Control
SRNCUE IEs
Measurement IEs
Initial UE identity
Establishment causeProtocol error
indicator
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,
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,
IMSI
TMSI & LAI
P-TMSI & RAI
IMEI
CHOICE
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.RRC CONNECTION REQUESTUL-CCCH-MessagemessagerrcConnectionRequestinitialUE-IdentityimsiDigit: 5Digit: 2Digit: 0Digit: 0Digit: 5Digit: 1Digit: 0Digit: 0Digit: 0Digit: 0Digit: 0Digit: 0Digit: 0Digit: 1Digit: 8
establishmentCause: originatingConversationalCallprotocolErrorIndicator: noErrormeasuredResultsOnRACHcurrentCellmodeSpecificInfofddmeasurementQuantitycpich-Ec-N0: 44
15 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RADIO LINK SETUP REQUEST Message
UE Node B RNC MSS/MGW
RADIO LINK SETUP REQUESTNBAPNBAP
RRC RRC
Message DiscriminatorMessage TypeTransaction ID
CRNC CommunicationContext IDDL DPCH
Information IEsDL DPCH
Information IEs
DCH InformationDSCH Information
TFCI2 bearer information IEs
RL Information IEsTransmission GapPattern Sequence
InformationActive PatternSequence Info
RRC CONNECTION REQUEST (CCCH on RACH)
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.
16 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RADIO LINK SETUP RESPONSE Message
UE Node B RNC MSS/MGW
RADIO LINK SETUP RESPONSENBAPNBAP
RADIO LINK SETUP REQUESTNBAPNBAP
RRC RRC
DCH List RL Setup Response
Radio Link Information Item
Radio Link Information List
NodeB Communication Context ID
CRNC Communication Context ID
RRC CONNECTION REQUEST (CCCH on RACH)
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.
17 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
ERQ and ECF Messages
UE Node B RNC MSS/MGW
ERQ
ECFALCAPALCAP
ALCAP ALCAP
RADIO LINK SETUP RESPONSENBAPNBAP
RADIO LINK SETUP REQUESTNBAPNBAP
RRC RRC
ERQ = Establishment RequestECF = Establishment Confirm
ERQ = Establishment RequestECF = Establishment Confirm
RRC CONNECTION REQUEST (CCCH on RACH)
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.
18 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
DL and UL SYNCHRONISATION Messages
UE Node B RNC MSS/MGW
ERQ
ECFALCAPALCAP
ALCAP ALCAP
RADIO LINK SETUP RESPONSENBAPNBAP
RADIO LINK SETUP REQUESTNBAPNBAP
RRC RRC
UL SYNCH
DL SYCH
DCH-FP
DCH-FP
DCH-FP
DCH-FP
Start TxStart Tx
19 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC CONNECTION SETUP Message
UE Node B RNC MSS/MGW
RRC CONNECTION SETUP (CCCH on FACH)RRC RRC
ERQ
ECFALCAPALCAP
ALCAP ALCAP
RADIO LINK SETUP RESPONSENBAPNBAP
RADIO LINK SETUP REQUESTNBAPNBAP
RRC RRCRRC CONNECTION REQUEST (CCCH on RACH)
UL SYNCH
DL SYCH
DCH-FP
DCH-FP
DCH-FP
DCH-FP
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 UE‘s 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 signallingbearers, 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.
20 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC CONNECTION SETUP Message
UE Node B RNC MSS/MGW
RRC RRCRRC CONNECTION SETUP (CCCH on FACH)
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)
RNC-ID , S-RNTI
(optional)
Signalling RBinformationto setup list
Signalling RBInformation
to setup RB identityCHOICE RLC info type
RLC info
Same as RB
RB mapping info
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 S-CCPCH 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 S-RNTI 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-RNC‘s 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.
21 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC CONNECTION SETUP Message
UE Node B RNC MSS/MGW
RRC RRCRRC CONNECTION SETUP (CCCH on FACH)
UE IEs
RB IEs
TrCH IEs: UL/DL
PhyCH IEs: UL/DLAdded or Reconfigured
TrCH information list
UL/DL Transport channelinformation common for
all transport channels
Added or ReconfiguredUL/DL TrCH information
optional:UARFCN uplink and downlinkdefault: operating band
Frequency Info
UL radio resources
DL radio resources
• 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 = FALSESystem 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 TrCHUL/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.
22 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC CONNECTION SETUP COMPLETE Message
UE Node B RNC MSS/MGW
ERQ
ECFALCAPALCAP
ALCAP ALCAP
RADIO LINK SETUP RESPONSENBAPNBAP
RADIO LINK SETUP REQUESTNBAPNBAP
RRC RRCRRC CONNECTION REQUEST (CCCH on RACH)
RRC CONNECTION SETUP COMPLETE (DCCH on DCH)RRC RRC
RRC CONNECTION SETUP (CCCH on FACH)RRC RRC
UL SYNCH
DL SYCH
DCH-FP
DCH-FP
DCH-FP
DCH-FP
Message RRC Connection Setup Complete is sent on DCCH from UE to SRNC.
Parameters: Integrity information, ciphering information.
23 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC CONNECTION SETUP COMPLETE Message
UE Node B RNC MSS/MGW
RRC RRCRRC CONNECTION SETUP COMPLETE (DCCH on DCH)
• 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 IEs
Other IEs
RRC Transaction ID
START list
CN domainidentity
START
UE radio accesscapability
UE radio accesscapability extension
UE system specificcapability
Inter-RAT UEradio access
capability
1 to InterSysMessages (4)
GSM MS Classmark 2 /GSM MS Classmark 3
OP
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 Completemessage 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 UE‘s 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.
24 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Transport Network Layer Setup
25 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Transport Layer Address
Binding ID
Transport Network Layer SetupUE Node-B RNC CN
Radio Link Setup ResponseNBAPNBAP
Signalling Association Identifier
NSEA-Dest. NSAP Serv. Endpoint Addr.
Channel Identifier (CID)
Path ID
DAID-Dest. sign. assoc. ident
Binding ID
Establish Request (ERQ)ALCAPALCAP
Establish Confirm (ECF)ALCAPALCAP
Channel IDs organise the AAL type 2 minipacket flow in the VCC:
CID: 0 ... 7 reservedCID: 8 ... 255 for external use
AAL type 2 path IDhas to be identical atboth ends of a VCC
26 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Establish RequestUE Node-B RNC CN
e.g.
DAID-Dest. sig. assoc. identifier.
CEID-Connection element identifier
NSEA Dest NSAP service end point add.
CPS-SDU bit rate/size
OSAID-Origin. Sig. Assoc. identifier
SUGR-Served user gen. reference
Signalling association id that will generated in the BS .In the establish request is always 0.
Connection element identifier contains PATH id & CID number selected by the RNC.
AAL2 TP in the WAM of the BS
Parameter that define the Max. and Average bit rate/size of the CPS in forward & backwards
Signalling association id that will 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 .
DAID-Dest. sig. assoc. identifier.
OSAID-Origin. Sig. Assoc. identifier
Signalling association identifier generated in the BS
Signalling association id that will generated in the RNC .
Transport Network is ReadyRNC & BS
Collects parameters to configure the UE
RNC
Establish Request (ERQ)ALCAPALCAP
Establish Confirm (ECF) ALCAPALCAP
27 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
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.
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.
28 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Binding ID
AP-1
ALCAP-1
AP-1
ALCAP-1
AP-1
ALCAP-1
AP-2
ALCAP-2
AP-2
ALCAP-2
AP-2
ALCAP-2
Step 1
Step 2
Step 3
Radio Network Control Plane Setup (Response)
ALCAP Establish request
Node1 Transport Address Binding ID
Node1 Transport Address Binding ID
Node 1 Transport addressBinding ID
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.
29 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
AAL2UP without AAL2 Multiplexing
49 00123 020BTSID 0WAM0
123 021BTSID 0WAM1
Associate AAL2SIG terminate in same WAM
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
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.
30 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
AAL2UP with AAL2 Multiplexing
123 001BTSID 00AAL2SIG TPID
31 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
AAL2UP without AAL2 Multiplexing
ZRII;
TREE=1 ATYPE=N
DIGITS AL NBR RT CT SP NL RC DEST SDEST
4900123020 0 2 ROU NGC 0 0 APR 3 3
4900123040 0 3 ROU NGC 0 0 APR 6 5
4900123060 0 4 ROU NGC 0 0 APR 8 6
TREE=2 ATYPE=N
DIGITS AL NBR RT CT SP NL RC DEST SDEST
456618190111 0 100 ROU NGC 0 0 APR 10 4
COMMAND EXECUTED
ZRII;
TREE=1 ATYPE=N
DIGITS AL NBR RT CT SP NL RC DEST SDEST
4900123020 0 2 ROU NGC 0 0 APR 3 3
4900123040 0 3 ROU NGC 0 0 APR 6 5
4900123060 0 4 ROU NGC 0 0 APR 8 6
TREE=2 ATYPE=N
DIGITS AL NBR RT CT SP NL RC DEST SDEST
456618190111 0 100 ROU NGC 0 0 APR 10 4
COMMAND EXECUTED
32 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
OSAID and DSAID
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.
33 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Transport Layer Setup – IP Option
UE Node B RNC MSS/MGW
RADIO LINK SETUP RESPONSENBAPNBAP
RADIO LINK SETUP REQUESTNBAPNBAP
RRC RRCRRC CONNECTION REQUEST (CCCH on RACH)
Transport Layer Address
Binding ID
BTS Transport IP Address
RRC RRCRRC CONNECTION SETUP (CCCH on FACH)
No ALCAP
34 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
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
35 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Example of Transport Network Layer Setup Signalling
36 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Review of Transport Network Layer Setup
Transport Layer Address
Binding ID
UE Node-B RNC CN
Radio Link Setup ResponseNBAPNBAP
Signalling Association Identifier
NSEA-Dest. NSAP Serv. Endpoint Addr.
Channel Identifier (CID)
Path ID
DAID-Dest. sign. assoc. ident
Binding ID
Establish Request (ERQ)ALCAPALCAP
Establish Confirm (ECF)ALCAPALCAP
37 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RADIO LINK SETUP RESPONSE Message
RADIO LINK SETUP RESPONSENBAP-PDUsuccessfulOutcome
- procedureCode: 9- criticality: reject- messageDiscriminator: common
successfulOutcomeRadioLinkSetupResponseprotocolIEs
- id: 43- criticality: ignoreCRNC-CommunicationContextID: 1033- id: 73- criticality: ignoreNodeB-CommunicationContextID: 160010- id: 111- criticality: ignore
RadioLinkInformationList-RL-SetupRsp- id: 101- criticality: ignoreRadioLinkInformationItem-RL-SetupRsp- rL-ID: 1- diversityIndication: mdc-is-done-at-rnc
dCH-Information-RL-SetupRsp- id: 52- criticality: ignoreDCH-List-RL-SetupRspDCH-List-Item-RL-SetupRsp- dCH-ID: 24- bindingID: '00000003'H
transportLayerAddress- non-extended:
'4900123020FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF'H- id: 142- criticality: ignore
TrafficTP-ID: 1Binding ID and Transport Layer
Address
38 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
ESTABLISHMENT REQUEST (ERQ) MessageOSAID-Orig. sign. assoc. ident.- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Signalling association identifier: 45 10 1A 00 SUGR-Served user gen. reference- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Field: 00 00 00 03
NSEA-Dest. NSAP serv. endpoint addr.- Parameter's Compatibility: 10hPass-on not possible:- Do not send notification- Discard parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 20 (14h)- Address: 49 00 12 30 20 FF FF FF FF FF FF FF FF FF FF FFFF FF FF FFLC-Link Charactreristics- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter 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)
ERQ - ESTABLISH REQUESTDAID-Dest. sign. assoc. ident.: 00 0000 00- Message's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterCEID-Connection element ident.- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 5 (05h)- Path identifier: 1001 (3E9h)- Channel identifier: 12 (Ch)
Path ID and CID
Transport Layer Address
Link QoS
OSAID
Binding ID
39 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
ESTABLISHMENT CONFIRM (ECF) Message
ECF - ESTABLISH CONFIRMDAID-Dest. sign. assoc. ident.: 45 10 1A 00 - Message's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterOSAID-Orig. sign. assoc. ident.- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Signalling association identifier: 00 00 00 09
40 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Signalling and Counters (Reference)
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
41 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC Connection Sub-phases (1/2)
Mobile Terminated Call (MTC)
ServiceRequest
Radio AccessBearer
Paging
Mobile Originated Call
RRCConnection
Setup ActiveAccess
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
42 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC Connection Sub-phases (2/2)
UE Node B RNC
RRC CONNECTION REQUEST
RRC CONNECTION SETUP
RRC CONNECTION SETUP COMPLETE
RRC RRC
RRC
RRC
RRC
RRC
Setup
Access
Active
RRC_CONN_STP_ATT = N + 1
RRC_CONN_STP_COMP = N + 1
RRC Setup PhaseThe 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.Thesum 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 PhaseRRC 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 PhaseThe 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.
43 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Setup Failures
Setupcomplete
Setup phase
Access Failures
Accesscomplete
Access phase
Active Failures
Active Release
Activecomplete
Active phase
Success
DropAttempts
RRC Connection Performance Analysis
Setups Failures, Blocking
NOTE: Aim of This Slideis to give example of relation between KPI counters and signalling flow.KPI analysis or optimization will not discuss in this training
RRC Setup PhaseThe 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 PhaseRRC 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 PhaseThe 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.
44 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC Connection Performance AnalysisUE Node-B RNC
RRC Connection Request RRC RRC
A number of RRC connection setup attempts.
RRC CONN SETUP
ATT
M1001C0
ExplanationCounter NameNo
MOBILE Originating Low Priority Signalling ATTEMPTSM1001C54MOBILE Terminating Streaming Call ATTEMPTSM1001C34
MOBILE Terminating High Priority Signalling ATTEMPTSM1001C52MOBILE Terminating Conversational Call ATTEMPTSM1001C32
MOBILE Originating High Priority Signalling ATTEMPTSM1001C50MOBILE Originating Subscribed traffic Call ATTEMPTSM1001C30
M1001C60
M1001C58
M1001C56
M1001C48
M1001C46
M1001C44
M1001C42
No
Terminating – cause unknown ATTEMPTS
Call re-establishment ATTEMPTS
MOBILE Terminating Low Priority Signalling ATTEMPTS
Detach ATTEMPTS
Registration ATTEMPTS
Inter-RAT cell change order ATTEMPTS
Inter-RAT cell re-selection ATTEMPTS
Attempt Counter Name
MOBILE Terminating Interactive Call ATTEMPTSM1001C36
MOBILE Originating Background Call ATTEMPTSM1001C28
MOBILE Terminating Background Call ATTEMPTSM1001C38
MOBILE ORIGINATING STREAMING CALL ATTEMPTSM1001C24
MOBILE ORIGINATING CONVERSATIONAL CALL ATTEMPTSM1001C22
MOBILE Originating Interactive Call ATTEMPTSM1001C26
Emergency Call ATTEMPTSM1001C40
Attempt Counter NameNo
Counters RRC CONN SETUP ATT ( Attempt for RRC Setup Causes)
45 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC Connection Performance AnalysisUE Node-B RNC
RRC Connection Request RRC RRC
Counters of RRC Connection Setup Failures
NBAP Radio Link Setup
ALCAP Transport Bearer Setup
RRC Connection Setup RRC RRC
UnspecifiedA number of RRC connection setup failures caused by a transmission.RRC CONN SETUP FAIL DUE TO TRANSM1001C5
UnspecifiedA number of RRC connection setup failures caused by RNC'sinternal reasons. (e.g. parameter mismatch, timer expiry).
RRC CONN SETUP FAIL DUE TO RNC INTER REASONSM1001C6
UnspecifiedA number of RRC connection setup failures caused by a frozen BTS. Frozen BTS means that currently no new RRC connections
are allowed.RRC CONN SETUP FAIL DUE TO FROZEN BTSM1001C7
UnspecifiedA number of RRC connection setup failures caused by a BTS.Whenthe BTS rejects an initial RL setup.RRC CONN SETUP FAIL DUE TO BTSM1001C4
CongestionA number of RRC connection setup failures caused by AC.RRC CONN SETUP FAIL DUE TO ACM1001C3
UnspecifiedA number of RRC connection setup failures caused by HC.RRC CONN SETUP FAIL DUE TO HCM1001C2
Rejection cause in RRC Connection Reject message
ExplanationCounter NameNo
SETUP
46 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC Connection Performance AnalysisUE Node-B RNC
RRC Connection RequestRRC
SETUP
RRC Connection Setup Complete
RRC Connection Setup
RRC
RRC
Layer 1 Synchronisation
NBAP SynchronisationAccess
Counters of RRC Connection Access Failures
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.RRC CONN ACC FAIL DUE
TO RADIO INT SYNCHM1001C9
A number of RRC connection access failures caused by RNC's internal reasons. (e.g. parameter mismatch, timer expiry).
RRC CONN ACC FAIL DUE TO RNC INTER REASONSM1001C11
A number of RRC connection access failures caused by the UU interface. When the RNC does not receive RRC_CONNECTION_COMPLETE from the UE
RRC CONN ACC FAIL DUE TO UU INTM1001C10
ExplanationCounter NameNo
RRC
RRC
RRC
47 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RRC Connection Performance Analysis
A number of RRC connection access
completions.RRC CONN ACC COMPM1001C8
ExplanationCounter NameNo
UE Node-B RNC
RRC Connection RequestRRC
SETUP
RRC Connection Setup Complete
RRC Connection Setup
RRC
RRC
Layer 1 Synchronisation
NBAP SynchronisationAccess
Active
RRCRRC: Initial Direct Transfer
AAL2 Connection Release
A number of RRC connection active
completions.
RRC CONN ACTIVE COMP
M1001C12
ExplanationCounter NameNo
RRC
RRC
RRC
RRC
48 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Iu-CS Call Setup
49 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Service Request Phase
Mobile Terminated Call (MTC)
ServiceRequest
Radio AccessBearer
Paging
Mobile Originated Call
RRCConnection
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.
50 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Iu-CS Call Setup (Service Request)UE RNC CN
RRC Connection Setup
Initial Direct TransferCM Service Request
RRC RRC
Initial UE MessageCM Service Request
RANAPRANAP
Node-B
Common IDRANAPRANAP
Security Mode Command
Uplink Direct Transfer (Set up)RRC RRC
Direct Transfer (Setup) RANAPRANAP
Direct Transfer ( Call Proceeding)
RANAPRANAP
Downlink Direct Transfer (Call Proceeding)RRC RRC
Common IDThe 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 connection-oriented signalling
CommonID- extension flag: 0 - preamble: 0
protocolIEs- padding: 000000 - length: 00 01
- id: 23- contents: 00 17
- criticality: ignore- 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
51 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RAB Setup Phase
Mobile Terminated Call (MTC)
ServiceRequest
Radio AccessBearer
Paging
Mobile Originated Call
RRCConnection
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.
52 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Iu-CS Call Setup (RAB Setup)UE Node-B RNC
RRC Connection & Service Request Phase
RAB Assignment RequestRANAPRANAP
RAB Assignment ResponseRANAPRANAP
MEGACO*
Radio Bearer SetupRRC RRC
Radio Bearer Setup completeRRC RRC
CN
Establish Request/Confirm
(RNC and MGW) AAL2SIGAAL2SIG
Radio Link Reconfiguration PrepareNBAPNBAP
Radio Link Reconfiguration CommitNBAPNBAP
Radio Link Reconfiguration ReadyNBAPNBAP
Establish Request/Confirm AAL2SIGAAL2SIG
* Before RAC Assignment Request start
In Rel’5 MSS use MEGACO send message “Add Request” to MGW and MGW reply by message “ Add Reply”
53 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RAB ASSIGNMENT REQUEST – ATM OptionRAB-ASSIGNMENT REQUEST
- rAB-ID: '00000001'B
rAB-Parameters- extension flag: 0 - preamble: 1100100
- trafficClass: conversational- extension range: 0 - contents (in bits): 00
- rAB-AsymmetryIndicator: symmetric-bidirectional- extension range: 0 - contents (in bits): 00
maxBitrate- length (in bits): 0
- MaxBitrate: 12200- length (in bits): 01 - contents: 2F A7
guaranteedBitRate- length (in bits): 0
- GuaranteedBitrate: 4750- length (in bits): 01 - padding: 00000 - contents: 12 8E
- deliveryOrder: delivery-order-requested- contents (in bits): 0
- maxSDU-Size: 244- padding: 0000000 - contents: 00 F4
transportLayerInformation- extension flag: 0
- preamble: 0 - transportLayerAddress:
'0100010100000000000000000000000000000000000001100100001000010110001011110000000000000000000000000000000000000000000000000000000000000000000000000000000000000000'B
- extension range: 0 - length (in bits): 10011111
- 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 QoS
RAB ID
54 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
RAB ASSIGNMENT REQUEST – IP OptionRAB-AssignmentRequest
protocolIEs: 1 itemItem 0: id-RAB-SetupOrModifyList
ProtocolIE-Containerid: id-RAB-SetupOrModifyList (54)criticality: ignore (1)value
RAB-SetupOrModifyList: 1 itemItem 0
ProtocolIE-ContainerPairList: 1 itemItem 0: id-RAB-SetupOrModifyItem
ProtocolIE-ContainerPairid: id-RAB-SetupOrModifyItem (53)firstCriticality: reject (0)firstValue
RAB-SetupOrModifyItemFirstrAB-ID: 01 [bit length 8]rAB-Parameters
trafficClass: conversational (0)rAB-AsymmetryIndicator: symmetric-bidirectional (0)maxBitrate: 1 item
Item 0RAB-Parameter-MaxBitrateList: 12200
guaranteedBitRate: 1 itemItem 0
RAB-Parameter-GuaranteedBitrateList: 4750deliveryOrder: delivery-order-requested (0)maxSDU-Size: 244sDU-Parameters: 3 itemstransferDelay: 80allocationOrRetentionPrioritysourceStatisticsDescriptor: speech (0)
userPlaneInformationuserPlaneMode: support-mode-for-predefined-SDU-sizes (1)uP-ModeVersions: 0002 [bit length 16]
transportLayerInformationtransportLayerAddress: 3500010A089F9400000000000000000000000000 [bit length 160]iuTransportAssociation: bindingID (1)
bindingID: 052E0000secondCriticality: ignore (1)secondValue
RAB-SetupOrModifyItemSecond
RAB ID
RAB QoS
Binding ID and Transport Layer
Address
MGW IP Address• prefix: 35 00 01• IP address: 0A 08 9F 94
10. 8. 159. 148
55 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Link of Signalling Messages
56 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
UE Node-B RNC CN
RRC Connection Setup Request
Radio Link Setup RequestNBAPNBAP
Radio Link Setup Response NBAPNBAP
RRC RRCIMSI
RNTI
RNC Communication Context ID
Node B Communication Context ID
RNC Communication Context ID
Transport Layer Address
Binding ID
57 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
UE Node-B RNC CN
RRC Connection Setup Complete
RRC Connection Setup
Establish Request (ERQ) AAL2SIGAAL2SIG
Establish Confirm (ECF) AAL2SIGAAL2SIG
RRCRRC
RRC RRC
Transport Layer Address
Channel Identifier (CID)
OSAID Orig sign assoc idnet.
OSAID Orig sign assoc idnet.
DAID Dest sign assoc idnet.
IMSI
Data send on CID that allocate on ERQ
58 © Nokia Siemens Networks RN33022EN10GLA00 CS Call Setup
Link of Signalling Messages
UE WBTS RNC CN
Signalling connection
RAB
Iu connectionRANAP RANA
P
RRC connection/ S-RBRRC RRC
CMSMMM
RB Iu-Bearer
WCDMA
WCDMA
NBAP
AAL2SIG
AAL2 UP
Log ChTransp ChPhy Ch
Log ChTransp ChPhy Ch
Log ChTransp ChPhy Ch
Log ChTransp ChPhy Ch
CMSMMM
MTP3 SLRANAP
AAL2SIGIu-cs
AAL2UD (Iu-cs)IPOAUD (Iu-ps)
RANAP
AAL2SIGIu-cs
ATMRACH eg CID 8FACH eg CID 9
DCH->DCCHEg CID 12
AS
NAS
ATM
Martin Ervens