You are on page 1of 135

3G RANOP 1

Module 3 – Signalling Flows

For internal use
1 © Nokia Siemens Networks Presentation / Author / Date

3G RAN Optimization
• Cluster health checks • 3G<>2G Cell
• Parameter consistency reselection
Cluster check Inter-System • Neighbour Planning
• Neighbour list Working and • Handover Process and
Preparati verification Optimisation compressed mode
on • Uplink interference as • 3G ISHO service
a problem indicator analysis (AMR and PS)
• GSM ISHO Optimisation
• RF optimisation
RF • New Site Integration • Use of Parameters to
Optimisation • Neighbour plan Paramete optimise network
and Neighbour
Verification
optimisation r performance
Optimisati
• RRC Establishment on
Signalling • RAB Establishment • HSDPA Air Interface
Flows • SHO HSDPA Capacity
• ISHO

Optimisati • HSDPA Drive Test KPIs and
HSDPA Parameter Optimisation
on
• Drive Survey Analysis
Drive Test • System Performance
Analysis (RRC and RAB phases)

For internal use
2 © Nokia Siemens Networks Presentation / Author / Date

Module 3 – Signalling Flows

Objectives
After this module the delegate shall be able to:-
• Describe the signalling flows for AMR calls, PS calls, HSDPA
calls, ISHO, SHO and SRNC relocation procedures
• Understand the key pieces of information contained in the
messages
• Understand the protocols and transport mechanisms used
for the various messages

For internal use
3 © Nokia Siemens Networks Presentation / Author / Date

UMTS Bearer Services Radio Access Stratum Access Non- Bearers Signalling connection RR RRC Iu C connection connectio n Stratum Access Radio bearer service Iu bearer service : SAP UE Uu RAN Iu CN For internal use 4 © Nokia Siemens Networks Presentation / Author / Date .

Protocol Stacks • Communication between the UE.c A s • Protocol stacks include both user and control planes • The control plane of one protocol stack may make use of the user plane of another protocol stack e. RNC and circuit switched core network (CN) makes use of • Uu interface protocol stack • Iub interface protocol stack • Iu-CS interface protocol stack • A interface protocol stack BTS RNC Multimedia 3G Gateway MSC Uu Iub Iu.g. RRC messages which form the control plane of the radio interface protocol are communicated to and from the BTS using the user plane of the Iub protocol stack For internal use 5 © Nokia Siemens Networks Presentation / Author / Date .

cs UP Iu. reconfiguring and releasing radio bearers • The 3G MSC provides connectivity to the circuit switched core and PSTN • The multimedia gateway provides transcoding for • Speech calls: between AMR and A Law PCM • Video calls: no transcoding is required i.CS Radio Interface Protocol (RIP) User Plane • Radio Interface Protocol is responsible for setting up. vocoder RNC vocoder A Law A Law RLC-U RLC-U PCM. vocoder appears only in the UE • Transparent mode RLC is used between the UE and RNC • AAL2 based ATM is used to transfer user plane data across the Iub and Iu.g.g.e. Iu.cs interfaces UE Multimedia GW 3G MSC e. e.cs A For internal use 6 © Nokia Siemens Networks Presentation / Author / Date .cs UP etc etc MAC Node B MAC PSTN FP FP AAL2 AAL2 AAL2 AAL2 Link Link ATM ATM ATM ATM Layer Layer WCDMA WCDMA L1 L1 Phy Phy Phy Phy Phy Phy Phy Uu Iub Iu. PCM.

CS Radio Interface Protocol (RIP) Control Plane • The radio interface protocol control plane allows RRC signalling between the RNC and UE • RRC signalling is communicated across the Iub using the Iub user plane protocol stack i.e. using Frame protocol and AAL2 based ATM • Acknowledged or unacknowledged mode RLC is used between the UE and RNC UE RNC RRC RRC RLC-C RLC-C MAC Node B MAC FP FP AAL2 AAL2 ATM ATM WCDMA WCDMA L1 L1 Phy Phy Uu Iub For internal use 7 © Nokia Siemens Networks Presentation / Author / Date .

2150.1 Q.2 • ATM Adaptation Layer 5 (AAL5) SSCF-UNI SSCF-UNI is used for the control planes SSCOP SSCOP whereas AAL2 is used for the AAL5 AAL5 AAL2 user plane ATM Physical Layer For internal use 8 © Nokia Siemens Networks Presentation / Author / Date .2630.Iub Protocol Stack • The Iub protocol stack has three planes • The radio network control plane uses the NBAP protocol and completes tasks such as configuring a radio link at a BTS • The transport network control plane uses ALCAP and is responsible for setting up and tearing down user plane transport bearers Radio Network Transport User Plane Control Plane Network Control Plane • The user plane uses Frame NBAP Frame Protocol Protocol and is responsible for encapsulating all data to and from the UE ALCAP Q.

1 • ATM Adaptation Layer 5 (AAL5) SCCP Q.2630.1 is used for the control planes MTP3b MTP3b whereas AAL2 is used for the SSCF-NNI SSCF-NNI user plane SSCOP SSCOP AAL5 AAL5 AAL2 ATM Physical Layer For internal use 9 © Nokia Siemens Networks Presentation / Author / Date .2150.Iu-CS Protocol Stack • The Iu-CS protocol stack has three planes • The radio network control plane uses the RANAP protocol and completes tasks such as configuring a RAB or assigning Iu-CS resources • The transport network control plane is responsible for setting up/tearing down Iu transport bearers Radio Network Transport User Plane Control Plane Network Control Plane Iu User Plane • The user plane is responsible RANAP Protocol for encapsulating all data to and from the UE Q.

Signalling Flows AMR Mobile Originating Voice Call For internal use 10 © Nokia Siemens Networks Presentation / Author / Date .Module 3 .

RAB Setup 5. BCCHS C C decoding & RACH access 2.AMR CS Call Phases UE WBT DRN SRN CN 1. Service Established 6. Cell search. Service Released For internal use 11 © Nokia Siemens Networks Presentation / Author / Date . UE <--> CS-CN signalling 5. UE <--> CS-CN signalling 4. RRC connection set-up 3. Branch addition/deletion & Active set update 7.

(SFN modulo 2)=0 2)=1 The Primary CCPCH is detected using the 10 ms identified p-scrambling code  system and cell specific BCH information can be read For internal use 12 © Nokia Siemens Networks Presentation / Author / Date . 1 Cell Search Procedure Slot synchronisation to a cell Primary SCH Frame synchronisation and identification of the cell code group Secondary SCH Determination of the exact primary scrambling code used by the found cell CPICH P-CCPCH. (SFN modulo P-CCPCH.

1 Random Access Procedure Information on BCCH: • Preamble scrambling code • Message Length (10 or 20 ms) • Available signatures and RACH sub- channels • Power Ramp Step (P0) / / BCH • Preamble Retransmission Max (B CCH m a tion • Power Offset (P ) r p-m m Info • Set of Transport Format Parameters : S yste RRC PCH) PCC RACH P l e (P 1) eamble 1. dication Conne e In : R RC e s sag C HM 4.RR / PR A C C H (RA )) P P 2+ p -m For internal use (P 3= 13 © Nokia Siemens Networks Presentation / Author / Date . eamb H Pr P r C PRA ) ition P is UE 2. = P 1+ 0 : A cqu qu est P e ( AICH on R WBTS 2 cti 3.

2 RRC Connection Set-up Signalling Flow UE WBTS RNC RRC: RRC CONNECTION REQUEST (RACH) Admission Control NBAP: RADIO LINK SETUP REQUEST NBAP: RADIO LINK SETUP RESPONSE ALCAP: ERQ ALCAP: ECF FP Downlink Sync FP Uplink Sync RRC: RRC CONNECTION SETUP (FACH) L1 Sync NBAP: SYNCH INDICATION RRC: CONNECTION SETUP COMPLETE (DCH) For internal use 14 © Nokia Siemens Networks Presentation / Author / Date .

IMSI. CPICH Ec/Io of current cell and mobile identity (in terms of PTMSI. TMSI. LAI) • RRC Connection Request message is sent from the BTS across the Iub using Frame Protocol to encapsulate the transport blocks and send UE identity here given by TMSI and LAI them via AAL2 based ATM (transparent mode) • The BTS measures the one Establishment Cause way propagation delay in chips (resolution is 3 chips) and inserts into message CPICH Ec/Io of measured cell For internal use 15 © Nokia Siemens Networks Presentation / Author / Date . 2 RRC Connection Request • UE initiates the RRC establishment process by sending the RRC Connection Request message to the RNC (either in response to a paging request from the network or initiated by high layer request in the UE) • RRC Connection Request message is sent using unacknowledged mode RLC on the RACH • Contains info such as establishment cause (e. OriginatingConversationalCall).g. RAI.

040 0.020 0.080 Mot A835. 616 0.040 Nokia 7600 NEC 606. A920.060 0.020 0.080 NEC 313.020 0.160 0.160 0.040 0.5 -2. 616 0.030 Mot C975.060 Mot A1000 0.5 -25 -21 -19 -17 -13 -11 -8.030 0.5 -2.5 EcNo EcNo NEC RRC Connection Request EcNo PDF Nokia RRC Connection Request EcNo PDF 0. A925 0.120 0.5 -8.020 0.090 0.5 -2.5 -2.000 0. 8138.070 0.080 0. E1000 0.5 -25 -21 -19 -15 -13 -8.050 LG 8130. 808 0.5 -25 -21 -19 -15 -13 -6.100 Mot A835 0.000 -23 -21 -15 -11 -8.090 0.5 -0.080 0.040 LG U8110.5 -4.120 0.5 -25 -19 -17 -13 -6. 6680 PDF PDF 0.5 -4.060 0.5 -23 -17 -11 For internal use 16 © Nokia Siemens Networks EcNo/ Author / Date Presentation EcNo .000 -23 -15 -6.000 0. V975 0.010 0. 8330 PDF PDF 0.070 0. 8120 Mot C975.5 -0.140 0.060 0.5 -23 -17 -11 -6.050 Nokia 6630. 8180.140 0.010 0.Differences in EcNo estimation at RRC 2 Connection Request • Measurement made in a UK network in 2005 LG RRC Connection Request EcNo PDF Motorola RRC Connection Request EcNo PDF 0.5 -0. 338. 323.5 -4.5 -0.5 -4.100 NEC 313.

It does not include Iub communication • The Common NBAP: Radio Link Setup Request is sent using AAL5 based ATM within the radio network control plane belonging to the Iub protocol stack • The BTS acknowledges the Common NBAP: Radio Link Setup Request message with a Common NBAP: Radio Link Setup Response message • The Common NBAP: Radio Link Setup Response is sent using AAL5 based ATM within the radio network control plane belonging to the Iub protocol For internal use Example NetHawk Iub Log stack 17 © Nokia Siemens Networks Presentation / Author / Date . 2 NBAP Radio Link Setup • Once the RNC has received the RRC Connection Request message it sends a Common NBAP: Radio Link Setup Request to the BTS • The Common NBAP: Radio Link Setup Request includes uplink and downlink configuration data for the radio link that the BTS is being requested to support (see next slide) • The radio link refers only to the communication link between the BTS and UE.

This is equal to the value that the BTS measured from reception of the PRACH RRC Connection Request message • The initial downlink transmit power is –18. DL frames are expected to arrive before this time. Downlink data frames are expected to arrive after this time. 2 NBAP Radio Link Setup • The Iub time of arrival window start point (toAWS) is 15 ms.0 dBm (actual value = IE/10) For internal use 18 © Nokia Siemens Networks • The maximum DL transmit power is –7.1 dBm (actual value = Presentation / Author / Date . • The downlink transport format set is defined by being able to transmit 0 or 1 transport blocks of size 148 bits • The downlink TTI is 40 ms and rate 1/3 convolutional coding is used with a rate matching attribute of 1 and a 16 CRC • The uplink transport format set is defined by being able to transmit 0 or 1 transport blocks of size 148 bits • The uplink TTI is 40 ms and rate 1/3 Convolutional coding is used with a rate matching attribute of 1 and a 16 CRC • The cell ID is specified to be ID = 60791 • This radio link is the first radio link to be configured for this UE • The propagation delay from the UE to the BTS is specified to be 6 chips (actual value = IE*3). The DL Iub time of arrival window endpoint (toAWE) is 5 ms prior to the LTOA.

the BTS acknowledges by sending an ALCAP: Establish Confirm For internal use message 19 © Nokia Siemens Networks Presentation / Author / Date • The ALCAP: Establish Confirm is sent using AAL5 based ATM . 2 ALCAP Establishment • On receiving the Common NBAP: Radio Link Setup Response message indicating that the BTS has accepted the request for a radio link. RNC sends an ALCAP: Establish Request message to request Iub resources. • AAL type 2 Link Characteristics (ALC) (fixed length 12 octet data field) which specifies the maximum and average bit rates and SDU size to be used • Destination and Originating Signalling Association Identifiers (DSAID) and (OSAID) are defined. These are used for routing across ATM switches • The Connection Element Identifier (CEID) (5 octets. fixed length) which includes: Channel ID (CID) being established and path identifier as 107001 • The Network Service Access Point (NSAP) address is specified using a fixed length 20 octets • Once the BTS has received the ALCAP: Establish Request message signalling the requirement for an AAL2 ATM link. • The ALCAP: Establish Request is sent using AAL5 based ATM within the radio network control plane belonging to the Iub protocol stack • Message contains.

the RNC corrects itself to ensure subsequent TOAs are within the window defined by the NBAP: Radio Link Setup message For internal use 20 © Nokia Siemens Networks Presentation / Author / Date . 2 DCH Synchronisation on Iub • Used to achieve or restore the synchronisation of the DCH data stream in the downlink direction – as well as a keep alive procedure in order to maintain activity on the Iub transport bearer • The procedure is initiated by the SRNC by sending a DL SYNCHRONISATION frame protocol control frame towards BTS. the BTS immediately responds with an uplink SYNCHRONISATION control frame indicating the ToA for the DL SYNCHRONISATION control frame as well as the CFN indicated in that control frame • Depending on the received value of ToA. This is done over the newly created ATM connection • The DL SYNCHRONISATION frame protocol control frame indicates the target CFN • Upon reception of the DL SYNCHRONISATION control frame.

2nd-3rd time gap 1100ms) For internal use 21 © Nokia Siemens Networks Presentation / Author / Date . 1st-2nd time gap 100ms. • Signalling Radio Bearers (SRBs) configuration to be used • Configuration information on uplink and downlink transport CH’s • TTI used. 2 RRC Connection Setup • RNC replies to the UE’s original RRC Connection Request message with an RRC Connection Setup message which is sent via the BTS using FP to encapsulate the transport blocks across the Iub via AAL2 based ATM • The RRC Connection Setup message is sent to UE on FACH (S-CCPCH) using UM RLC • This message echos the UE identity in terms of the (P)TMSI and the RAI/LAI (The UE is assigned a new U-RNTI which is used by UTRAN to address the UE) • Message contains information such as. RLC PDU size • Convolutional coding rate to be used and CRC size • DPCCH power offset used for the uplink open loop power control • Downlink BLER target for outer loop power control • Power control algorithm and step size to be used • Downlink primary CPICH scrambling code • RNC can send the RRC Connection Setup message multiple times on the Layer 3 (FACH) depending on whether it receives the RRC Setup Complete message from the UE within a certain time period (Nokia sends up to 3 RRC Connection Setup messages. SRB TBS size.

The RRC Connection Setup message also provides timing information so the UE has some knowledge of when to expect the startUEof the downlink frame andNode slotB structure RNC RRC: RRC Connection Request (RACH) NBAP: Radio Link Setup Request NBAP: Radio Link Setup Response ALCAP: Establish Request ALCAP: Establish Confirm FP: Downlink Sync FP: Uplink Sync RRC: RRC Connection Setup (FACH) For internal use L1 Synchronisation 22 © Nokia Siemens Networks Presentation / Author / Date . 2 Layer 1 Synchronisation I • Once the BTS has relayed the RRC Connection Setup message it starts to transmit the downlink DPCCH on the radio link which has been configured by the NBAP: Radio Link Setup Request message • The transmit power has been computed by Admission Control (AC) and instructed within the NBAP: Radio Link Setup Request message • The UE uses the information within the RRC Connection Setup message to indicate which scrambling code and which channelisation code to search for.

e. If T312 expires then the UE considers the DPCH establishment attempt as a failure For internal use 23 © Nokia Siemens Networks Presentation / Author / Date . 2 Layer 1 Synchronisation II • Once UE has identified the precise timing of the downlink DPCCH it evaluates the quality over the first 40 ms. If the UE judges the quality to be greater than Qin it sends an CPHY-Sync-IND primitive to higher layers • After the first 40 ms have been judged the UE evaluates the DPCCH quality every 10 ms but based upon the previous 40 ms of DPCCH frames (sliding window) • Layer 3 of the UE uses to timer T312 (6s) and counter threshold N312 (1) to determine whether or not the L1 synchronisation has succeeded. Both T312 and N312 were broadcast to the UE in SIB 1 • T312 was started when UE initiated the establishment of the DPCH i. when the RRC Connection Request message was sent • Layer 3 of the UE must count N312 CPHY-Sync-IND primitives before T312 expires to consider the DPCH as established.

Both these parameters are specified within the RRC Connection Setup message • While the UE has been transmitting these DPCCH radio frames the BTS has been attempting to achieve uplink synchronisation • L1 of the BTS generates in-sync primitives whenever it judges itself to have successfully received a DPCCH frame. • Layer 1 of the UE continues to compare the downlink DPCCH quality against Qin for 160 ms after achieving the DPCH establishment. After the 160 ms period L1 of the UE is able to report both CPHY-Sync-IND and CPHY-Out-of-Sync-IND primitives based upon Qin and Qout respectively. The transmit power is then given by (Offset – CPICH RSCP) as measured by the UE • The UE transmits pc-Preamble DPCCH radio frames followed by a further SRB-delay DPCCH radio frames. CRC indications are also used throughout this phase • The initial transmit power for the UE is calculated from the offset provided in the RRC Connection Setup message. 2 Layer 1 Synchronisation III • Assuming that N312 CPHY-Sync-IND primitives are received prior to T312 expiring then the UE starts to transmit its UL DPCCH. During this phase the DPCCH quality is evaluated every 10 ms but over the previous 160 ms rather than the previous 40 ms. If the BTS receives NInSynchInd successive (not necessarily consecutive) in-sync primitives it sends a Synchronisation Indication message to the RNC to indicate that the DPCH has been established and that the BTS has moved from the initial state to the in-sync state For internal use 24 © Nokia Siemens Networks Presentation / Author / Date .

2 RRC Connection Setup Complete • Having transmitted the DPCCH during (pc- Preamble + SRB-delay) 14 radio frames the UE transmits the RRC Connection Setup Complete message using SRB 2 on the newly established DCH • DCCH contains the RRC Connection Setup Complete message • Message is sent using Acknowledged mode RLC • The message contains the UE radio access capability For internal use 25 © Nokia Siemens Networks Presentation / Author / Date .

3
UE<–> CS_CN signalling

• Location
Update
• Authentication
• Security Mode
e
• Setup
Paging a tio n U pdat
curity
o c Se
1. L quest n and
• Call Setup R e
n ticat
i o
t he p
2. Au de Setu ate
Mo
i o n Upd
ca t
3. Lo cept
Ac
P ag ing MSC /
4. VLR
p
a l l Setu
5. C
U
E

RN MG
C W
WB
For internal use
26 © Nokia Siemens Networks Presentation / Author / Date
TS

3
UE<–> CS_CN signalling
UE RNC CN
RRC Connection Establishment

INITIAL DIRECT TRANSFER (CM Service SCCP: Connection Request
Request)
SCCP: Connection Confirm

Location reporting Control

RANAP: COMMON ID

Security Mode Command

1
Security Mode Complete
OR

2
CM Service Accept

UPLINK DIRECT TRANSFER (Setup, mobile
originated side)

DIRECT TRANSFER (Call
Proceeding)

For internal use
27 © Nokia Siemens Networks Presentation / Author / Date

3
CM Service Request
• Having established the RRC connection the UE is able to send a NAS message
to the CS core
• DCCH contains the RRC: Initial Direct Transfer message (DCCH ->DCH ->
DPCH)
• Message is sent using acknowledged mode RLC
• The RRC: Initial Direct Transfer message is received by the RNC and forwarded
to the CS core, across the Iu-CS, using a RANAP: Initial UE Message
• The NAS message (TS 24.008) is not read by the RNC but is forwarded to the
multimedia gateway
• Since the RANAP message is a RANAP: Initial UE Message means, the SCCP
layer includes a SCCP: Connection Request message which is used to establish
a connection orientated signalling link (this does not reserve any resources for
the AMR call itself)
• The SCCP layer of theNode
UE Iu-CS
B protocol stack responds
RNC to the Connection Request
MGW
message with a Connection Confirm message
RRC Connection Establishment

Initial Direct Transfer (CM Service Request) SCCP: Connection Request

For internal use
28 © Nokia Siemens Networks Presentation / Author / Date

3 Location Report Control • The CS core sends a RANAP: Location Reporting Control message to the RNC • This allows the core network to request information regarding the location of a particular UE • The CS core will expect a RANAP: Location Report message in response to this control message (following call establishment) • The RANAP: Location Reporting Control message requests the RNC to provide a location report whenever the UE changes service area UE Node B RNC MGW RRC Connection Establishment Initial Direct Transfer (CM Service Request) SCCP: Connection Request SCCP: Connection Confirm Location Reporting Control For internal use 29 © Nokia Siemens Networks Presentation / Author / Date .

• The CS core does not expect a response to the RANAP: Common ID message UE Node B RNC MGW RRC Connection Establishment Initial Direct Transfer (CM Service Request) SCCP: Connection Request SCCP: Connection Confirm Location Reporting Control Common ID For internal use 30 © Nokia Siemens Networks Presentation / Author / Date . the IMSI. This is used by the RNC to create a reference between the permanent NAS identity and the RRC connection.e. 3 Common ID • The CS core sends a RANAP: Common ID message to the RNC • This informs the RNC of the UE’s permanent NAS identity i.

ciphering and integrity protection are initialised for the four SRBs belonging to the UE • The UE responds to the Security Mode Command message with a Security Mode Complete message UE Node B RNC MGW RRC Connection Establishment Initial Direct Transfer (CM Service Request) SCCP: Connection Request SCCP: Connection Confirm Location Reporting Control Common ID Security Mode Command Security Mode Complete For internal use 31 © Nokia Siemens Networks Presentation / Author / Date . for the radio bearers of one core network domain and for all signalling bearers • The general structure and contents of the Security Mode Command message are the same as those used for IMSI attach i. 3 Security Mode • The CS core then sends a Security Mode Command message to the UE • The purpose of this procedure is to trigger the start or stop of ciphering or to command the restart of the ciphering with a new ciphering configuration.e.

(as stated in 24. 3 CM Service Accept • The CM Service Accept message is only sent if the security mode procedure is not used • If the security mode procedure is used then completion of that procedure is used as an alternative indication of CM service acceptance.008) • The CM Service Accept message serves only as an acknowledgement and contains no additional information UE Node B RNC MGW RRC Connection Establishment Initial Direct Transfer (CM Service Request) SCCP: Connection Request SCCP: Connection Confirm Location Reporting Control Common ID Security Mode Command Security Mode Complete OR CM Service Accept For internal use 32 © Nokia Siemens Networks Presentation / Author / Date .

3 Setup • UE sends a NAS Setup message to the CS core which includes the number being dialled by the UE • The NAS message is sent to the RNC using an RRC: Uplink Direct Transfer message and forwarded to the CS Core using a RANAP: Direct Transfer message • The structure of the NAS message is specified by 24.008 (see below) 03 45 04 03 20 02 80 5E 03 81 06 F2 15 02 03 01 Call Control Capabilities 4 Octets (3 + IEI) 1 bearer supported PCP support DTMF support 1 speech bearer supported Called Party BCD Number Message Type 5 Octets 1 Octet Unknown type of number 0100 0101 => Setup Message Telephone numbering plan Number: 602 Protocol discriminator Example ½ Octet Bearer Capability structure of NAS 0011 => Call Control Message 5 Octets set-up message GSM full rate speech versions 1 and 2 Transaction Identifier GSM standardised coding is used ½ Octet Transfer mode is circuit switched 0000 => message flow 0 Information transfer capability is speech For internal use 33 © Nokia Siemens Networks Presentation / Author / Date .

3 Call Proceeding • Having received the NAS Setup message the CS core sends the NAS Call Proceeding message to the UE • The NAS message is a simple acknowledgement and contains no further information • In some scenarios it is possible that the NAS message contains more information • The NAS message can be interpreted using the message structure definition in TS 24.008 MGW UE Node B RNC • The Call Proceeding message is sent to the UE using a RANAP: Downlink Direct RRC Connection Establishment Transfer message Initial Direct Transfer (CM Service Request) SCCP: Connection Request SCCP: Connection Confirm Location Reporting Control Common ID Security Mode Command Security Mode Complete Setup Call Proceeding For internal use 34 © Nokia Siemens Networks Presentation / Author / Date .

The supplementary service to be invoked and its associated parameters are specified within the NAS Facility message UE Node B RNC MGW RRC Connection Establishment Initial Direct Transfer (CM Service Request) SCCP: Connection Request SCCP: Connection Confirm Location Reporting Control Common ID Security Mode Command Security Mode Complete Setup Call Proceeding Facility For internal use 35 © Nokia Siemens Networks Presentation / Author / Date . 3 Facility • Facility message is used to indicate to the UE that a supplementary service is active.

4 RAB Setup UE Node B RNC MGW RRC Connection Establishment Initial Direct Transfer (CM Service Request) SCCP: Connection Request SCCP: Connection Confirm Location Reporting Control Common ID Security Mode Command Security Mode Complete Setup Call Proceeding Facility RAB Assignment Request Admission Control Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF FP: Downlink Sync FP: Uplink Sync AAL2SIG:ERQ AAL2SIG:ECF Radio Link Reconfiguration Commit Radio Bearer Setup Radio Bearer Setup Complete RAB Assignment Response For internal use 36 © Nokia Siemens Networks Presentation / Author / Date .

streaming etc. B and C bits) • On receipt of the RANAP: RAB Assignment Request Admission Control (AC) will decide whether the RAB can be admitted For internal use 37 © Nokia Siemens Networks Presentation / Author / Date .) • Maximum and guaranteed bit rates • Maximum SDU size (used with TTI to define bit rates) • information of RAB sub flows (SRB and AMR RAB sub flows for Class A.e. • traffic class (i. conversational. 4 RANAP: RAB Assignment Request • The CS core initiates the RAB Establishment procedure by sending the RANAP: RAB Assignment Request message to the RNC • The RANAP: RAB Assignment Request message requests the RNC to establish a RAB with a specified set of QoS parameters • The CS core requests these QoS parameters based upon the UE subscription and the service being requested • Information in the RAB Assignment request message includes.

4 NBAP: Radio Link Reconfiguration • If admission control (AC) procedure within the RNC decides to accept the RAB request it prepares to reconfigure the radio link at the BTS by sending the NBAP: Radio Link Reconfigure Prepare message • This message contains similar information as that specified in the Common NBAP: Radio Link Set-up message • Provides information on the calculated TFC (cTFC) based on the individual transport channels defined as well as information on each transport channel • The NBAP: Radio Link Reconfigure Prepare message has not changed the uplink SIR target nor has it changed the downlink DPCCH / DPDCH power offsets • The BTS responds to the NBAP: Radio Link Reconfigure Prepare message with a NBAP: Radio Link Reconfigure Ready message UE Node B RNC MGW RAB Assignment Request Radio Link Reconfigure Prepare Radio Link Reconfigure Ready For internal use 38 © Nokia Siemens Networks Presentation / Author / Date .

fixed length): • The SRB and AMR make use of separate CID • The path identifier is the same identifier as that used to configure the SRB Iub resources • The request for AMR Iub resources is acknowledged using the ALCAP: Establish MGW Confirm UE message Node B RNC RAB Assignment Request Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF For internal use 39 © Nokia Siemens Networks Presentation / Author / Date . 4 ALCAP: Establish Request/Confirm (ERQ/ECF) • Having received acknowledgement that the radio link has been prepared for reconfiguration the RNC assigns additional Iub resources for the speech transport blocks • Iub resources are in addition to those that have already been assigned for the SRB transport blocks • The Destination Signalling Association Identifier (DSAID) is set to the same identifier as that used to configure the SRB Iub resources • The Connection Element Identifier (CEID) includes (5 octets.

DCH synchronisation is achieved by sending downlink and uplink frame protocol control frames (in the same way as described in the RRC connection set-up procedure) • This ensures the AMR transport blocks arrive at the BTS within the window start and end points UE Node B RNC MGW RAB Assignment Request Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF FP: Downlink Sync FP: Uplink Sync For internal use 40 © Nokia Siemens Networks Presentation / Author / Date . 4 DCH Synchronisation on Iub • Once the Iub resources have been allocated for the AMR transport blocks.

the RNC sends a request to assign transmission resources on the Iu-CS • This is done using the transport network control plane of the Iu-CS protocol stack • The request for AMR Iu-CS resources is acknowledged using the ALCAP: Establish Confirm message • Once the transmission resource allocations have been configured the RNC sends a NBAP: Radio Link Reconfiguration Commit message to the BTS UE Node B RNC MGW RAB Assignment Request Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF FP: Downlink Sync FP: Uplink Sync AAL2SIG:ERQ AAL2SIG:ECF For internal use 41 © Nokia Siemens Networks Presentation / Author / Date . 4 Iu-CS ALCAP: Establish Request/Confirm • Having allocated transmission resources on the Iub.

UL scrambling codes. puncturing limits. This is the same CFN as recorded in the NBAP: Radio Link Reconfiguration Commit message • The message provides information for mapping the new radio bearers to the transport channels • The calculated transport format combinations (cTFC) are signalled to the UE. This is the time at which the radio bearer setup shall become applicable. power offsets) and radio link (e.g. DL BLER for SRB and AMR RAB sub flow Class A bits. B and C bits) • This message also provides information on the configuration of the transport channels (e.RRC: Radio Bearer Setup & RAB Assignment 4 Response • Once the NBAP: Radio Link Reconfiguration Commit message has been sent to the BTS the RNC sends a RRC: Radio Bearer Setup message to the UE • The activation time is specified in terms of CFN. downlink primary scrambling code) • The UE acknowledges the RRC: Radio Bearer Setup message with a RRC: Radio Bearer Setup Complete message • Once the radio bearer establishment has been acknowledged. the RNC indicates to the CS core that the RAB has been established using the RANAP: RAB Assignment Response message For internal use 42 © Nokia Siemens Networks Presentation / Author / Date . These are the same cTFC as signalled to the BTS in the NBAP: Radio Link Reconfigure Prepare message • The four transport channels are configured in an identical fashion as was done at the BTS with the NBAP: Radio Link Reconfigure Prepare message (An AMR Voice call comprises 1 SRB and 3 RAB sub flows for Class A. spreading factors.g.

id: 52 .criticality: reject outcome RAB-AssignmentResponse protocolIEs .rAB-ID: '00000001'B For internal use 43 © Nokia Siemens Networks Presentation / Author / Date .criticality: ignore RAB-SetupOrModifiedItem .criticality: ignore RAB-SetupOrModifiedList .RRC: Radio Bearer Setup & RAB Assignment 4 Response This acknowledgment specifies that RAB 1 has been successfully established RANAP-PDU outcome .procedureCode: 0 .id: 51 .

5 UE-CN signalling UE Node B RNC MGW RRC Connection Establishment Initial Direct Transfer (CM Service Request) SCCP: Connection Request SCCP: Connection Confirm Location Reporting Control Common ID Security Mode Command Security Mode Complete Setup Call Proceeding Facility RAB Assignment Request Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF FP: Downlink Sync FP: Uplink Sync AAL2SIG:ERQ AAL2SIG:ECF Radio Link Reconfiguration Commit Radio Bearer Setup Radio Bearer Setup Complete RAB Assignment Response Alerting Connect Connect Acknowledge Call Established Location Report Measurement Control For internal use 44 © Nokia Siemens Networks Presentation / Author / Date .

5 Alerting • Having received the RANAP: RAB Assignment Response message. • The Alerting message is sent to the UE using a RANAP: Direct Transfer message • The structure of the NAS Alerting message is specified by 24.008 UE Node B RNC MGW RAB Assignment Response Alerting For internal use 45 © Nokia Siemens Networks Presentation / Author / Date . CS core sends NAS Alerting message to the UE • This message is sent to indicate that the called user alerting has been initiated.

008 • The UE acknowledges the NAS Connect message with the NAS Connect Acknowledge message • At UE this point the call Node has B been successfully RNC established MGW RAB Assignment Response Alerting Connect Connect Acknowledge For internal use 46 © Nokia Siemens Networks Presentation / Author / Date . 5 Connect/Connect Acknowledge • Having received the Alerting message. the CS core sends the NAS Connect message to the UE • This message is sent to indicate call acceptance by the called user • The Connect message is sent to the UE using a RANAP: Direct Transfer message • The structure of the NAS Connect message is specified by 24.

5 Location Report • The RNC replies to the earlier RANAP: Location Reporting Control message with the RANAP: Location Report message • The RANAP: Location Report message is sent to the UE using a RANAP: Direct Transfer message • The location report specifies that the service area identity based upon the PLMN ID. LAC and SAC UE Node B RNC MGW RAB Assignment Response Alerting Connect Connect Acknowledge Call Established Location Report For internal use 47 © Nokia Siemens Networks Presentation / Author / Date .

if two neighbours are assigned the same cell ID then one will overwrite the other • Each neighbour has its scrambling code specified as well as an indication that the SFN should be read and whether or not transmit diversity is being used • The Layer 3 UE filter coefficient is also specified • Specifies measurement quantity to be used for Intra-frequency measurements (e. acknowledged mode RLC) • Specifies whether measurement reports should be event or periodically triggered For internal use 48 © Nokia Siemens Networks Presentation / Author / Date .g. Ec/Io) • Specifies which cells UE should report on Active + Monitored • Criteria for reporting events 1a. • The neighbour list to be used by the UE • Intra-frequency neighbour with cell ID 0 is always the serving cell • Intra-frequency neighbours with cell IDs other than 0 are then specified.e.g. 1b and 1c are specified • Informs UE on the transfer mode to be used for Measurement Reports (e. 5 Measurement Control • Once the call has been established the RNC sends an RRC: Measurement Control message • Prior to receiving this message. the UE uses the measurement control information from the SIBs • This message is used to specify. The UE uses the cell ID as a pointer to the location within its neighbour register where the information is stored i.

6 Branch Addition / Active Set update UE Node B1 Node B2 RNC MGW Call Established Measurement Control Measurement Report Admission Control NBAP: Radio Link Addition Request Cell starts receiving NBAP: Radio Link Addition Response ALCAP: Establish Request ALCAP: Establish Confirm Required when Event 1a FP: Downlink Sync is for a soft handover FP: Uplink Sync rather than softer handover Cell starts transmitting Active Set Update If softer handover then only L1 SYNC a single set of transport Active Set Update Complete blocks are forwarded across the Iub Measurement Control For internal use 49 © Nokia Siemens Networks Presentation / Author / Date .

synchronisation information and CPICH Ec/Io.e. The scrambling code is used to identify the active set cells • Monitored set cell measurements are provided as specified within the measurement control message i. UE Node B1 Node B2 RNC MGW • The event 1a is specified to have been triggered by a monitored set cell Call Established Measurement Control Measurement Report For internal use 50 © Nokia Siemens Networks Presentation / Author / Date . synchronisation information and CPICH Ec/Io. This is done using the RRC: Measurement Report message • The UE reports all active set cells plus up to N monitored set cells within the measurement report. 6 RRC: Measurement Report (Event 1a) • Once the UE determines that an event 1a (add) has occurred it sends a measurement report to the RNC.e. (As specified in the RRC: Measurement Control message) • The measurement identity reflects that provided within the measurement control message • Active set cell measurements are provided as specified within the measurement control message i.

BTS 2) in the case of soft handover (For softer handover RNC uses the NBAP: Radio Link Addition Request • If the event 1a corresponds to a softer handover then the Iub resources are already configured and synchronisation already achieved. • Once the BTS has received the NBAP: Radio Link Addition Request message it starts to receive using the appropriate uplink configuration UE Node B1Node B2 RNC MGW Call Established Measurement Control Measurement Report NBAP: Radio Link Addition Request For internal use 51 © Nokia Siemens Networks Presentation / Author / Date . RL Setup for Soft HO 6 NBAP: RL Setup/Addition Request RL Addition for Softer • Assuming the RNC admission control admits the new radio link then it sends an NBAP: Radio Link Setup Request message to the appropriate BTS (i. The BTS will also already have knowledge of the uplink and downlink physical layer configuration.e.

The cell then starts transmitting the same transport blocks as the original cell Call Established Measurement Control Measurement Report NBAP: Radio Link Addition Request Cell starts receiving NBAP: Radio Link Addition Response ALCAP: Establish Request ALCAP: Establish Confirm Required when Event 1a FP: Downlink Sync is for a soft handover FP: Uplink Sync rather than softer handover For internal use Cell starts 52 © Nokia Siemens Networks Presentation / Author / Date transmitting . 6 NBAP: RL Setup/Addition Request • BTS responds to the NBAP: Radio Link Addition Request with an NBAP: Radio Link Addition Response • If the event 1a corresponds to a soft handover then Iub resources must be configured. If the BTS receives NInSynchInd (8) successive (not necessarily consecutive) in-sync primitives then it sends a Synchronisation Indication message to the RNC to indicate that the DPCH has been established and that the BTS has moved from the initial state to the in-sync state • In the case that the event 1a is for soft handover then Iub resources must be reserved using the ALCAP: Establish Request and ALCAP: Establish Confirm messages. synchronisation achieved and the BTS informed of the physical layer configuration • L1 of the BTS generates in-sync primitives whenever it judges itself to have successfully received a DPCCH frame. Synchronisation UE must also be Nodeachieved B1 Node B2 using the FP: Downlink RNC Sync and FP: Uplink MGW Sync messages.

then that neighbour is over written • The scrambling code of each neighbour to be added is specified and an indication is made that the SFN of each should be read when measurements are made. These neighbours are referenced using a cell ID. If a neighbour already exists with the same cell ID. 6 RRC: Active Set Update/Complete • The RRC: Active Set Update message is then transmitted from both cells • UE confirms to RNC that the AS has been updated by sending an RRC: Active Set Update Complete message • Once the RNC has received the RRC: Active Set Update Complete message it updates the neighbour list used by the UE using an RRC: Measurement Control message • A list of neighbours to be removed from the neighbour list is specified (referenced using their cell ID within the neighbour list) • A list of neighbours to be added to the neighbour list is specified. • Once the UE has entered soft handover then reporting events 6f and 6g become applicable • These reporting events are configured using a separate measurement control message For internal use 53 © Nokia Siemens Networks Presentation / Author / Date .

7 Release of AMR Speech Call UE Node B RNC MGW Call Established Direct Transfer (Disconnect) Direct Transfer (Release) Direct Transfer (Release Complete) Iu Release Command Iu Release Complete RRC Connection Release RRC Connection Release Complete RRC Connection Release Complete RRC Connection Release Complete Radio Link Deletion Request Radio Link Deletion Response ALCAP: Release Request ALCAP: Release Response ALCAP: Release Request ALCAP: Release Response Call Released • In this example the UE initiates the call release by sending the Disconnect message to the CS core • The network acknowledges the Disconnect message with a Release message • The core network initiates the release of the Iu resources using the Iu Release Command message For internal use 54 © Nokia Siemens Networks Presentation / Author / Date .

Module 3 .Signalling Flows CS Video call setup For internal use 55 © Nokia Siemens Networks Presentation / Author / Date .

For internal use 56 © Nokia Siemens Networks Presentation / Author / Date .CS Video Telephony • The bearer of CS Video Telephony (UDI) is set up on a CS 64kbps data RAB • 3G-324M is the 3GPP version of ITU H-324 • 3G-324M data flow is transparent to the network: no transcoding/decoding.

324 Signalling TerminalCapabilitySet • 4 phases in Video Handshaking TerminalCapabilityAck TerminalCapabilitySet • TerminalCapabilitySet message: terminals exchange TerminalCapabilityAck information about their own terminal system capabilities MasterSlaveDetermination MasterSlaveDeterminationAck • MasterSlaveDetermination: MasterSlaveDetermination terminals exchange random numbers. Video. Data] For internal use 57 © Nokia Siemens Networks Presentation / Author / Date . Terminal A Terminal B H. to determine the master MasterSlaveDeterminationAck and slave terminals OpenLogicalChannel • VideoIndicateReadyToActivate: OpenLogicalChannelAck [optional procedure]. OpenLogicalChannelAck • OpenLogicalChannel: logical channels are opened for information streams [Audio. wait for video transmission until both UEs OpenLogicalChannel are ready to send.

Module 3 .Signalling Flows Location Update Procedure For internal use 58 © Nokia Siemens Networks Presentation / Author / Date .

Location Update and Security Mode Setup UE WBTS RNC CN INITIAL DIRECT TRANSFER (Location Update Request) Authentication Request Authentication Response Security Mode Command Security Mode Complete Identity Request Identity Response DIRECT TRANSFER (Location Update Accept) DIRECT TRANSFER (TMSI Reallocaiton Complete) Iu Release Command Iu Release Complete SCCP: Release SCCP: Release RRC: Connection Complete Release RRC: Connection Release Complete RRC: Connection Release Complete RRC: Connection Release Complete NBAP: Radio Link Deletion Request NBAP: Radio Link Deletion Response ALCAP: Release Request ALCAP: Release Confirm For internal use 59 © Nokia Siemens Networks Presentation / Author / Date .

Location Update and Security Mode Setup Location Update Process For internal use 60 © Nokia Siemens Networks Presentation / Author / Date .

Location Update Request • Once the UE has established a dedicated communication link with UTRAN via RRC Connection Establishment. These identify the Node Bactual location of the UE RNC rather than the location MGW stored in the UE’s SIM RRC Connection Request (RACH) RRC Connection Setup (FACH) RRC Connection Setup Complete (DCH) Location Updating Request (DCH) SCCP: Connection Request For internal use 61 © Nokia Siemens Networks Presentation / Author / Date . it is in a position to initiate the Location Update procedure • The UE uses an uplink RRC: Initial Direct Transfer message to encapsulate and send a Location Updating Request message to the RNC • The BTS extracts the RRC: Initial Direct Transfer message and encapsulates it within a DCH Frame Protocol frame • The RNC extracts the Location Updating Request message and encapsulates it within a RANAP: Initial UE Message prior to forwarding it to the multimedia gateway (CN) • The header to this message informs the CS core of the LAI. SAI and the global RNC UE ID.

Location update request across Iu-CS • The SCCP layer of the Iu-CS protocol stack adds a header to the RANAP message which includes a Connection Request message • The Connection Request message initiates the establishment of a connection orientated connection between RNC and MGW • The SCCP layer of the Iu-cs protocol stack responds to the Connection Request message with a Connection Confirm message UE Node B RNC MGW RRC Connection Request (RACH) RRC Connection Setup (FACH) RRC Connection Setup Complete (DCH) Location Updating Request (DCH) SCCP: Connection Request SCCP: Connection Confirm For internal use 62 © Nokia Siemens Networks Presentation / Author / Date .

Authentication Request • Having received the Location Updating Request message the CS core responds with an NAS Authentication Request message • The Authentication Request message is sent to the RNC encapsulated within a RANAP Direct Transfer message • The RNC extracts the Authentication Request message and encapsulates it within an RRC Downlink Direct Transfer message • The RNC then encapsulates the RRC Downlink Direct Transfer message within a downlink Frame Protocol data frame prior to forwarding it to the BTS • The BTS extracts the RRC Downlink Direct Transfer message and forwards it to the UE • Message is sent using Acknowledged mode RLC For internal use 63 © Nokia Siemens Networks Presentation / Author / Date .

Authentication Response • Having received the Authentication Request message the UE responds with an Authentication Response message • The Authentication Response message is sent to the BTS encapsulated within an RRC Uplink Direct Transfer message • The BTS encapsulates the RRC Uplink Direct Transfer message within an uplink Frame Protocol data frame prior to forwarding it to the RNC • The RNC extracts the Authentication Response message and encapsulates it within a RANAP Direct Transfer message prior to forwarding it to the CS core UE Node B RNC MGW RRC Connection Request (RACH) RRC Connection Setup (FACH) RRC Connection Setup Complete (DCH) Location Updating Request (DCH) SCCP: Connection Request SCCP: Connection Confirm (DCH) Authentication Request Authentication Response (DCH) For internal use 64 © Nokia Siemens Networks Presentation / Author / Date .

it is not a RANAP: Direct Transfer message . It is generated by the RNC from the RRC: Security Mode Complete message For internal use 65 © Nokia Siemens Networks Presentation / Author / Date . for the radio bearers of one core network domain and for all signalling bearers • It is also used to start integrity protection or to modify the integrity protection configuration for all signalling radio bearers • The security mode command is sent to the RNC using the Security Mode Command message of the RANAP protocol • This message does not include a NAS PDU • The RNC receives the RANAP: Security Mode Command and subsequently generates an RRC: Security Mode Command • Message is sent using Acknowledged mode RLC • The UE responds to the Security Mode Command message with a Security Mode Complete message • Message is sent using Acknowledged mode RLC • The RANAP: Security Mode Complete message is not a simple encapsulation of the message from the UE i.Security Command/Complete • The CS core sends a Security Mode Command message to the UE • The purpose of this procedure is to trigger the start or stop of ciphering or to command the restart of the ciphering with a new ciphering configuration.e.

Identity Request/Response
• CS core may request the UE to provide its identity. This is done using the Identity Request
message
• CS core sends the Identity Request message encapsulated within a RANAP: Direct
Transfer message
• RNC sends the Identity Request message encapsulated within a RRC: Downlink Direct
Transfer msg
• UEUE
sends the Identity Response
Node B
message encapsulated within
RNC
a RRC: Uplink Direct MGW
Transfer message
• RNCRRC
sends theRequest
Connection Identity
(RACH)Response message encapsulated within a RANAP: Direct Transfer

message RRC Connection Setup (FACH)
RRC Connection Setup Complete (DCH)
Location Updating Request (DCH) SCCP: Connection Request

SCCP: Connection Confirm

(DCH) Authentication Request

Authenication Response (DCH)

(DCH) Security Mode Command

Secuirty Mode Complete (DCH)

(DCH) Identity Request

Identity Response (DCH)
For internal use
66 © Nokia Siemens Networks Presentation / Author / Date

Location Update Accept
• CS core responds to the Location Updating Request with a Location Updating
Accept message
• The Location Updating Accept is sent to the RNC encapsulated within a RANAP:
Direct Transfer message
• RNC extracts the Location Updating Accept message and encapsulates it within
an RRC: Downlink Direct Transfer message. Message is sent using
Acknowledged
UE mode RLC Node B RNC MGW
RRC Connection Request (RACH)
RRC Connection Setup (FACH)
RRC Connection Setup Complete (DCH)
Location Updating Request (DCH) SCCP: Connection Request

SCCP: Connection Confirm

(DCH) Authentication Request

Authenication Response (DCH)

(DCH) Security Mode Command

Secuirty Mode Complete (DCH)

(DCH) Identity Request

Identity Response (DCH)

(DCH) Location Updating Accept
For internal use
67 © Nokia Siemens Networks Presentation / Author / Date

Release
• Having sent the Location Updating Accept message the CS core initiates the release of the
Iu-cs connection by sending a RANAP: Iu Release Command message to the RNC
• The RANAP message includes only the cause for the release which in this case is a normal
release
• The RNC replies to the RANAP: Iu Release Command message with a RANAP: Iu Release
Complete message
• The RANAP: Iu Release Complete message is relatively empty because it is only clearing a
RANAP signalling connection rather than a RAB connection
• Having released the Iu-cs connection at the RANAP layer, the SCCP layer releases the
underlying connection orientated link
• The SCCP: Released message specifies both the RNC and CS core local references
• Having sent the Iu Release Command Complete message the RNC initiates the release of
the RRC connection by sending an RRC Connection Release message to the UE
• Network instructs the UE to release the RRC connection
• Message is sent using unacknowledged mode RLC
• The UE responds by sending (n308+2) RRC Connection Release Complete messages to the
RNC
• UE informs the network that it is releasing the RRC connection
• Message is sent using unacknowledged mode RLC

For internal use
68 © Nokia Siemens Networks Presentation / Author / Date

Radio Link Deletion • The Dedicated NBAP: Radio Link Deletion Request is used to remove a radio link at a BTS • The Dedicated NBAP: Radio Link Deletion Request specifies the: • BTS communication context (specifies the UE to which the radio link deletion refers) • CRNC communication context (specifies the UE to which the RL deletion refers) • RL ID for the RL to be deleted (each UE may have multiple radio links at a BTS) • The Dedicated NBAP: Radio Link Deletion Response is used to remove a radio link at a BTS For internal use 69 © Nokia Siemens Networks Presentation / Author / Date .

ALCAP Iub Deletion • Having deleted the radio link. the ALCAP protocol is used to release the Iub resources • The ACLAP: Release Request is used to release the Iub resources • The RNC replies to the ACLAP: Release Request message with a ACLAP: Release Confirm message For internal use 70 © Nokia Siemens Networks Presentation / Author / Date .

Signalling Flows Inter System Handover (ISHO) – CS call For internal use 71 © Nokia Siemens Networks Presentation / Author / Date .Module 3 .

ISHO AMR Call UE WBTS RNC CN RCC: Measurement Control RCC: Measurement Report NBAP: RL Reconfigure Prepare Reporting Event NBAP: RL Reconfigure Ready Triggered NBAP: RL Reconfigure Commit RCC: Physical Channel Reconfiguration RCC: Physical Channel Reconfiguration Complete NBAP: Compressed Mode Command RCC: Measurement Control Handover Decision : RCC: Measurement Report BSIC verification (GSM RSSI) NBAP: Compressed Mode required Command RCC: Measurement Control RCC: Measurement Report (BSIC verified) RANAP: Relocation Required RANAP: Relocation Command RCC: Handover From UTRAN Command RANAP: Iu Release Command RANAP: Iu Release Complete NBAP: Radio Link Deletion Request NBAP: Radio Link Deletion Response For internal use 72 © Nokia Siemens Networks Presentation / Author / Date .

Ec/Io) has exceeded the relevant threshold (< -15dB).g. Event 1F.Measurement Report • Once UE identifies that one of the trigger mechanisms for ISHO (e. it sends an RRC: Measurement Report to the RNC For internal use 73 © Nokia Siemens Networks Presentation / Author / Date .

Radio Link Reconfiguration • On receiving the RRC: Measurement Report the RNC uses the NBAP: RL Reconfiguration Prepare message to inform the BTS of how its existing radio link will need to be reconfigured to support the compressed mode operation • The NBAP: RL Reconfiguration Prepare message informs the BTS about the compressed mode method to be used together with the various timing parameters. the position of the compressed mode transmission gap within a radio frame. This message informs the UE of the necessary changes to the existing radio links as well as informing the UE of the CM pattern that will be used (e. At this point the BTS has not implemented the changes • RNC sends the NBAP: RL Reconfiguration Commit message to the BTS informing it of the connection frame number (CFN) during which it must apply the new radio link configuration • Having reconfigured the radio link at the BTS.g. duration of the transmission gap and frequency of transmission gaps (Different parameters can be configured depending on the compressed mode purpose. e. e.g.g. Transmission Gap Pattern Sequence Indicator) For internal use 74 © Nokia Siemens Networks Presentation / Author / Date . RSSI measurements or BSIC verification) • The BTS through uses the NBAP: RL Reconfiguration Ready message to inform the RNC that it received the necessary changes. the RNC sends an RRC: Physical Channel Reconfiguration message to the UE.

Physical Channel Reconfiguration • Having prepared the BTS for the radio link reconfiguration. For internal use 75 © Nokia Siemens Networks Presentation / Author / Date . • Once the new configuration has become active (at the appropriate CFN) the UE responds with an RRC: Physical Channel Reconfiguration Complete message to the RNC. the RNC sends an RRC: Physical Channel Reconfiguration message to the UE. This message informs the UE of the CFN when it should be ready to start compressed mode measurements together with the compressed mode method and parameters.

representing the 2G cells which the UE should measure during compressed mode • During compressed mode operation the UE informs the RNC of the 2G measurements it makes using RRC: Measurement Report messages which are typically sent periodically.Compressed Mode Measurements • The RNC informs the BTS of which compressed mode pattern to activate at the appropriate CFN using the NBAP: Compressed Mode Command (i. GSM RSSI Measurements) • The UE is informed of the CFN in the RRC: Measurement Control message sent by the RNC following the NBAP: Compressed Mode Command. For internal use 76 © Nokia Siemens Networks Presentation / Author / Date .e. The RRC: Measurement Control message also contains the 2G neighbour list. The RNC uses these measurements to determine whether the UE should move to the 2G network • If the 2G cell with the highest RSSI is on a shared RF carrier the UE is required to complete the BSIC verification part of the process. The RNC informs the BTS of this requirement using a second set of NBAP: Compressed Mode Command and RRC: Measurement Control messages.

Compressed Mode Measurements (GSM RSSI) For internal use 77 © Nokia Siemens Networks Presentation / Author / Date .

Compressed Mode Measurements (BSIC Verification) For internal use 78 © Nokia Siemens Networks Presentation / Author / Date .

• The RNC instructs the UE to move to the 2G cell using the RRC: Handover Command from UTRAN message.Handover to 2G Network • Once the UE has verified the BSIC measurement using the RRC: Measurement Report the RNC sends a RANAP: Relocation Required message to the CS-CN and CS-CN responds with a RANAP: Relocation Command message. Information on 2G target cell For internal use 79 © Nokia Siemens Networks Presentation / Author / Date .

• The CN then instructs the RNC to clear the Iu resources using the RANAP: Iu Release Command. which then proceeds to delete the radio link at the Node B and the Iu signalling connection.Release of 3G resources • Once the UE has handed over to the 2G network the previously reserved UTRAN resources must be cleared down • It is common for the BTS to send the RNC a Radio Link Failure message before the UTRAN resources are cleared. AAL2 signalling is used to clear the Iub resources for both the user plane and signalling radio bearer. For internal use 80 © Nokia Siemens Networks Presentation / Author / Date . This message is acknowledged by the RNC in the RANAP: Iu Release Complete. (This is because the UE has moved to 2G and the BTS no longer has an uplink signal to maintain synchronisation with).

Signalling Flows PS Call For internal use 81 © Nokia Siemens Networks Presentation / Author / Date .Module 3 .

GPRS Attach 4. PS Data Session Released For internal use 82 © Nokia Siemens Networks Presentation / Author / Date . RB Reconfiguration 7. RAB set-up 5.PS Call Phases UE WBTS DRNC SRNC CN 1. PS Data Session Established 8. Branch addition/deletion & Active set update 10. UE <--> PS-CN Signalling (PDP Context Activation Accept) 6. RRC connection setup 3. Cell search. BCCH decoding & RACH access Same as for AMR call 2. State Transitions 9.

GPRS Attach • UE performs cell search and RRC Connection Establishment in the same way as for an AMR call • The UE registers with the PS-CN through the GPRS Attach procedure UE Node B RNC SGSN RRC Connection Initial Direct Transfer: GPRS Attach Request (DCH) SCCP: Connection Request Initial UE message : GPRS Attach Request SCCP: Connection Confirm Downlink Direct Transfer: Authentication and Ciphering Request (DCH) Direct Transfer: Authentication and Ciphering Request Uplink Direct Transfer: Authenication and Ciphering Response (DCH) Direct Transfer: Authentication and Ciphering Response Security Mode Command (DCH) Security Mode Command Secuirty Mode Complete (DCH) Common ID Downlink Direct Transfer: Common ID (DCH) Direct Transfer: Identity Request Uplink Direct Transfer: Identity Response (DCH) Direct Transfer: Identity Response Downlink Direct Transfer: Location Attach Accept (DCH) Direct Transfer: Attach Accept Uplink Direct Transfer: Attach Complete (DCH) Direct Transfer: Attach Complete For internal use 83 © Nokia Siemens Networks Presentation / Author / Date .

GPRS Attach Request • The UE has now established a dedicated communication link with UTRAN and is in a position to send a message to the core network (PS core in this case) • The UE uses an uplink RRC: Initial Direct Transfer message to encapsulate and send a GPRS MM : Attach Request message to the RNC • The BTS extracts the RRC: Initial Direct Transfer message and encapsulates it within a DCH Frame Protocol frame • The RNC extracts the Attach Request message and encapsulates it within a RANAP: Initial UE Message prior to forwarding it to the SGSN • The SCCP layer of the Iu-PS protocol stack responds to the Connection Request message with a Connection Confirm message UE Node B RNC SGSN RRC Connection Request (RACH) RRC Connection Setup (FACH) RRC Connection Setup Complete (DCH) Initial Direct Transfer: GPRS Attach Request (DCH) SCCP: Connection Request Initial UE message : GPRS Attach Request SCCP: Connection Confirm For internal use 84 © Nokia Siemens Networks Presentation / Author / Date .

Authentication and Ciphering Request • Having received the Attach Request message the PS core responds with an Authentication and Ciphering Request message • The Authentication and Ciphering Request message is sent to the RNC encapsulated within a RANAP Direct Transfer message • The RNC extracts the Authentication and Ciphering Request message and encapsulates it within an RRC Downlink Direct Transfer message • The RNC then encapsulates the RRC Downlink Direct Transfer message within a downlink Frame Protocol data frame prior to forwarding it to the Node B • The BTS extracts the RRC Downlink Direct Transfer message and forwards it to UE the UE Node B RNC SGSN RRC Connection Request (RACH) RRC Connection Setup (FACH) RRC Connection Setup Complete (DCH) Initial Direct Transfer: GPRS Attach Request (DCH) SCCP: Connection Request Initial UE message : GPRS Attach Request SCCP: Connection Confirm Downlink Direct Transfer: Authentication and Ciphering Request (DCH) Direct Transfer: Authentication and Ciphering Request For internal use 85 © Nokia Siemens Networks Presentation / Author / Date .

Authentication and Ciphering Response • Having received the Authentication and Ciphering Request message the UE responds with an Authentication and Ciphering Response message • The Authentication and Ciphering Response message is sent to the BTS encapsulated within an RRC Uplink Direct Transfer message • The BTS encapsulates the RRC Uplink Direct Transfer message within an uplink Frame Protocol data frame prior to forwarding it to the RNC • The RNC extracts the Authentication and Ciphering Response message and encapsulates it within a RANAP Direct Transfer message prior to forwarding it to the PS core UE Node B RNC SGSN RRC Connection Request (RACH) RRC Connection Setup (FACH) RRC Connection Setup Complete (DCH) Initial Direct Transfer: GPRS Attach Request (DCH) SCCP: Connection Request Initial UE message : GPRS Attach Request SCCP: Connection Confirm Downlink Direct Transfer: Authentication and Ciphering Request (DCH) Direct Transfer: Authentication and Ciphering Request Uplink Direct Transfer: Authenication and Ciphering Response (DCH) Direct Transfer: Authentication and Ciphering Response For internal use 86 © Nokia Siemens Networks Presentation / Author / Date .

it is not a RANAP: Direct Transfer message .e. It is generated by the RNC from the RRC: Security Mode Complete message For internal use 87 © Nokia Siemens Networks Presentation / Author / Date . for the radio bearers of one core network domain and for all signalling bearers • It is also used to start integrity protection or to modify the integrity protection configuration for all signalling radio bearers • The security mode command is sent to the RNC using the Security Mode Command message of the RANAP protocol • The RNC receives the RANAP: Security Mode Command and subsequently generates an RRC: Security Mode Command.Security Mode Command • The CS core sends a Security Mode Command message to the UE • The purpose of this procedure is to trigger the start or stop of ciphering or to command the restart of the ciphering with a new ciphering configuration. The message is sent using Acknowledged mode RLC • The UE responds to the Security Mode Command message with a Security Mode Complete message • The RANAP: Security Mode Complete message is not a simple encapsulation of the message from the UE i.

e. to create a reference between the permanent NAS UE identity of the user and the RRC connection of that user for UTRAN paging co-ordination UE Node B RNC SGSN RRC Connection Request (RACH) RRC Connection Setup (FACH) RRC Connection Setup Complete (DCH) Initial Direct Transfer: GPRS Attach Request (DCH) SCCP: Connection Request Initial UE message : GPRS Attach Request SCCP: Connection Confirm Downlink Direct Transfer: Authentication and Ciphering Request (DCH) Direct Transfer: Authentication and Ciphering Request Uplink Direct Transfer: Authenication and Ciphering Response (DCH) Direct Transfer: Authentication and Ciphering Response Security Mode Command (DCH) Security Mode Command Secuirty Mode Complete (DCH) Common ID For internal use 88 © Nokia Siemens Networks Presentation / Author / Date .Common ID • The purpose of the Common ID procedure is to inform the RNC about the permanent NAS UE Identity (i. IMSI) of a user • This is used by the RNC e.g.

Identity Request/ Response • PS Core may request the UE to provide its identity using the Identity Request message • PS Core sends the Identity Request message encapsulated within a RANAP: Direct Transfer message • RNC sends the Identity Request message encapsulated within a RRC: Downlink Direct Transfer message • UE sends the Identity Response message encapsulated within a RRC: Uplink Direct Transfer message UE Node B RNC SGSN • RNC sends the Identity Response message encapsulated within a RANAP: Direct Transfer message RRC Connection Request (RACH) RRC Connection Setup (FACH) RRC Connection Setup Complete (DCH) Initial Direct Transfer: GPRS Attach Request (DCH) SCCP: Connection Request Initial UE message : GPRS Attach Request SCCP: Connection Confirm Downlink Direct Transfer: Authentication and Ciphering Request (DCH) Direct Transfer: Authentication and Ciphering Request Uplink Direct Transfer: Authenication and Ciphering Response (DCH) Direct Transfer: Authentication and Ciphering Response Security Mode Command (DCH) Security Mode Command Secuirty Mode Complete (DCH) Common ID Downlink Direct Transfer: Common ID (DCH) Direct Transfer: Identity Request Uplink Direct Transfer: Identity Response (DCH) Direct Transfer: Identity Response For internal use 89 © Nokia Siemens Networks Presentation / Author / Date .

Attach Accept • The PS core responds to the Attach Request with a Attach Accept message • The Attach Accept is sent to the RNC encapsulated within a RANAP: Direct Transfer message • The RNC extracts the Attach Accept message and encapsulates it within an RRC: Downlink Direct Transfer message UE Node B RNC SGSN RRC Connection Request (RACH) RRC Connection Setup (FACH) RRC Connection Setup Complete (DCH) Initial Direct Transfer: GPRS Attach Request (DCH) SCCP: Connection Request Initial UE message : GPRS Attach Request SCCP: Connection Confirm Downlink Direct Transfer: Authentication and Ciphering Request (DCH) Direct Transfer: Authentication and Ciphering Request Uplink Direct Transfer: Authenication and Ciphering Response (DCH) Direct Transfer: Authentication and Ciphering Response Security Mode Command (DCH) Security Mode Command Secuirty Mode Complete (DCH) Common ID Downlink Direct Transfer: Common ID (DCH) Direct Transfer: Identity Request Uplink Direct Transfer: Identity Response (DCH) Direct Transfer: Identity Response Downlink Direct Transfer: Location Attach Accept (DCH) Direct Transfer: Attach Accept For internal use 90 © Nokia Siemens Networks Presentation / Author / Date .

g. PDP context Activation) UE Node B RNC SGSN RRC Connection Request (RACH) RRC Connection Setup (FACH) RRC Connection Setup Complete (DCH) Initial Direct Transfer: GPRS Attach Request (DCH) SCCP: Connection Request Initial UE message : GPRS Attach Request SCCP: Connection Confirm Downlink Direct Transfer: Authentication and Ciphering Request (DCH) Direct Transfer: Authentication and Ciphering Request Uplink Direct Transfer: Authenication and Ciphering Response (DCH) Direct Transfer: Authentication and Ciphering Response Security Mode Command (DCH) Security Mode Command Secuirty Mode Complete (DCH) Common ID Downlink Direct Transfer: Common ID (DCH) Direct Transfer: Identity Request Uplink Direct Transfer: Identity Response (DCH) Direct Transfer: Identity Response Downlink Direct Transfer: Location Attach Accept (DCH) Direct Transfer: Attach Accept Uplink Direct Transfer: Attach Complete (DCH) For internal use Direct Transfer: Attach Complete 91 © Nokia Siemens Networks Presentation / Author / Date .Attach Complete • The UE core responds to the Attach Accept with a Attach Complete message • The RNC extracts the Attach Complete message and encapsulates it within a RANAP: Direct Transfer message • The Attach Complete is sent to the RNC encapsulated within RRC: Uplink Direct Transfer message • There is no Iu release as PS-CN is waiting for additional signalling using the same RRC (e.

PDP Context (PS call) UE Node B RNC SGSN GPRS Attach Uplink Direct Transfer : Activate PDP context request (DCH) Direct Transfer : Activate PDP context request RANAP: RAB Assignment Request RRC: Radio Bearer Setup Radio Bearer Setup Complete RAB Assignment Response Measurement Control Measurement Control Downlink Direct Transfer : Activate PDP Context Accept (DCH) Direct Transfer: Activate PDP Context Accept Call Established For internal use 92 © Nokia Siemens Networks Presentation / Author / Date .

PDP Context Activation Request • DCCH contains the RRC: Uplink Direct Transfer message • Message is sent using acknowledged mode RLC • The RRC: Uplink Direct Transfer message is received by the RNC and forwarded to the PS core using a RANAP: Direct Transfer Message • The most important part in Activate PDP Context Request message are the requested QoS fields • Typically the UE requests all of the QoS parameters ‘Subscribed’ which means that the network uses HLR QoS profile to set-up the QoS UE Node B RNC SGSN GPRS Attach Uplink Direct Transfer : Activate PDP context request (DCH) Direct Transfer : Activate PDP context request For internal use 93 © Nokia Siemens Networks Presentation / Author / Date .

Delivery of erroneous SDUs: Subscribed .Residual BER: Subscribed .Guaranteed bit rate for downlink: Subscribed (MS only) be dynamic.Reliab.Configuration protocol: IP PDP type Password Authentic.Precedence class: Subscribed • As can be seen the UE is requesting all of . Options . Access point Id • The most important part in Activate PDP .length: 23 (17h) .Mean throughput: Best effort the QoS parameters ‘Subscribed’ which . Access Point Id .PDP Context Activation Request ACT.PDP type number: IPv4 Access Point Name 0A 73 74 61 74 64 79 6E 68 6C 72 03 63 . class: Subscribed (MS only) requested QoS fields .Maximum bit rate for uplink: Subscribed (MS only) . based on IETF allocated Packet Data Protocol Address .Guaranteed bit rate for uplink: Subscribed (MS only) .Dynamic PDP addressing is applied .length: 33 (21h) .Delivery order: Subscribed means that the network uses HLR QoS .Maximum bit rate for downlink: Subscribed (MS only) • Mean throughput is set to ‘best .PDP type organisation: IETF allocated address • Access Point is : 07 67 33 67 67 73 6E 31 .Delay class: Subscribed .length: 11 (0Bh) .Peak throughput: Subscribed . PDP CONTEXT REQUEST (GPRS SM) .value 6F 6D which corresponds to the APN set 07 67 33 67 67 73 6E 31 0A 73 74 61 74 64 79 6E 68 6C 72 03 63 6F 6D in the UE Protocol Conf.Traffic handling priority: Subscribed • The requested IP address is requested to .Maximum SDU size: Subscribed maximum SDU size profile to set-up the QoS .SDU error ratio: Subscribed effort’ .Traffic class: Subscribed . Protocol (PAP) For internal use Contents: 01 15 00 0A 04 64 65 6D 6F 00 94 © Nokia Siemens Networks Presentation / Author / Date Internet Protocol Control Protocol (IPCP) Contents: 01 05 00 10 81 06 00 00 00 00 83 06 00 00 00 00 .Transaction identifier: 00h Network Serv.Transfer delay: Subscribed (MS only) .NSAPI 5 LLC Serv.SAPI 3 Quality of Service Context Request message are the .Length: 2 (02h) addresses and IPv4 .

RAB Assignment Request • Having received the Activate PDP Context Request message the PS core sends the RANAP: RAB Assignment Request message to the RNC • The RANAP: RAB Assignment Request message requests the RNC to establish a RAB with a specified set of QoS parameters • The PS core requests these QoS parameters based upon the subscription and the service being requested (as seen from Activate PDP Context Request message the QoS is based entirely on the subscription) UE Node B RNC SGSN GPRS Attach Uplink Direct Transfer : Activate PDP context request (DCH) Direct Transfer : Activate PDP context request RAB Assignment Request For internal use 95 © Nokia Siemens Networks Presentation / Author / Date .

Radio Bearer Setup/Complete & RAB Assignment Response • Once the RANAP: RAB Assignment Request message has been received from PS CN and RNC has resources to setup the 0/0 kbps RB the RNC sends a RRC: Radio Bearer Setup message to the UE • The UE acknowledges the RRC: Radio Bearer Setup message with a RRC: Radio Bearer Setup Complete message • Once the radio bearer establishment has been acknowledged. the RNC indicates to the PS core that the RAB has been established using the RANAP: RAB Assignment Response message UE Node B RNC SGSN GPRS Attach Uplink Direct Transfer : Activate PDP context request (DCH) Direct Transfer : Activate PDP context request RANAP: RAB Assignment Request RRC: Radio Bearer Setup Radio Bearer Setup Complete RAB Assignment Response For internal use 96 © Nokia Siemens Networks Presentation / Author / Date .

the UE uses the measurement control information from the SIBs (inter and intra freq. Measurement Control • Once the RAB has been established the RNC sends a measurement control messages • For traffic volume measurements (UE internal) • For intra and inter frequency measurements • Prior to receiving this message. Measurements – traffic volume measurements are not performed prior to measurement control) • Measurement control defines the reporting thresholds also for traffic volume UE measurements which are used for the UL capacityRNC Node B requests SGSN GPRS Attach Uplink Direct Transfer : Activate PDP context request (DCH) Direct Transfer : Activate PDP context request RANAP: RAB Assignment Request RRC: Radio Bearer Setup Radio Bearer Setup Complete RAB Assignment Response Measurement Control Measurement Control For internal use 97 © Nokia Siemens Networks Presentation / Author / Date .

(measurement control messages can be sent before or after the Activate PDP Context Accept) the PS CN indicates to the UE that the PDP Context Activation has been successfully established using the RANAP: Activate PDP Context Accept message • RNC receives the Direct Transfer : Activate PDP Context Accept message and forwards it as Downlink Direct Transfer : Activate PDP Context Accept message to the UE UE Node B RNC SGSN GPRS Attach Uplink Direct Transfer : Activate PDP context request (DCH) Direct Transfer : Activate PDP context request RANAP: RAB Assignment Request RRC: Radio Bearer Setup Radio Bearer Setup Complete RAB Assignment Response Measurement Control Measurement Control Downlink Direct Transfer : Activate PDP Context Accept (DCH) Direct Transfer: Activate PDP Context Accept Call Established For internal use 98 © Nokia Siemens Networks Presentation / Author / Date .Activate PDP Context Accept • Once the radio access bearer establishment has been acknowledged.

Radio Bearer Reconfiguration UE Node B RNC SGSN GPRS Attach Uplink Direct Transfer : Activate PDP context request (DCH) Direct Transfer : Activate PDP context request RANAP: RAB Assignment Request RRC: Radio Bearer Setup Radio Bearer Setup Complete RAB Assignment Response Measurement Control Measurement Control Downlink Direct Transfer : Activate PDP Context Accept (DCH) Direct Transfer: Activate PDP Context Accept Call Established Measurement Report : e4a NBAP: Radio Link Reconfigure Prepare Admission Control Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF FP: Downlink Sync FP: Uplink Sync Radio Link Reconfiguration Commit RRC: Radio Bearer Reconfiguration (DCH) RRC: Radio Bearer Reconfiguration Complete (DCH) Measurement Control For internal use 99 © Nokia Siemens Networks Presentation / Author / Date .

the UE sends measurement report when the RLC buffer absolute payload exceeds 8B • The measurement identity reflects that provided within the measurement control message UE Node B RNC SGSN GPRS Attach Uplink Direct Transfer : Activate PDP context request (DCH) Direct Transfer : Activate PDP context request RANAP: RAB Assignment Request RRC: Radio Bearer Setup Radio Bearer Setup Complete RAB Assignment Response Measurement Control Measurement Control Downlink Direct Transfer : Activate PDP Context Accept (DCH) Direct Transfer: Activate PDP Context Accept Call Established Measurement Report : e4a For internal use 100 © Nokia Siemens Networks Presentation / Author / Date .Measurement Report e4a • Once the UE determines that an event 4a has occurred it sends a measurement report to the RNC. This is done using the RRC: Measurement Report message • As instructed.

the RNC prepares to reconfigure the radio link at the BTS by sending the NBAP: Radio Link Reconfigure Prepare message • This includes the parameters to reconfigure the existing SRB transport channel and the additional PS transport channel (s) • The radio link refers only to the communication link between the BTS and UE. It does not include Iub communication • The BTS responds to the NBAP: Radio Link Reconfigure Prepare message with a NBAP: Radio Link Reconfigure Ready message UE Node B RNC SGSN Call Established Measurement Report : e4a NBAP: Radio Link Reconfigure Prepare Radio Link Reconfigure Ready For internal use 101 © Nokia Siemens Networks Presentation / Author / Date .Radio Link Reconfigure prepare / ready • Assuming that the admission control procedure within the RNC decides to accept the capacity request from UE.

Iub ALCAP Establish Request/Confirm • Having received acknowledgement that the radio link has been prepared for reconfiguration the RNC assigns additional Iub resources for the PS transport blocks • These Iub resources are in addition to those that have already been assigned for the SRB transport blocks • These additional Iub resources are configured with a new Channel ID (CID) • The request for PS Iub resources is acknowledged using the ALCAP: Establish Confirm message UE Node B RNC SGSN Call Established Measurement Report : e4a NBAP: Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF For internal use 102 © Nokia Siemens Networks Presentation / Author / Date .

Iub DCH Synchronisation • Once the Iub resources have been allocated for the PS transport blocks. DCH synchronisation is achieved by sending downlink and uplink frame protocol control frames • This process has already been described during the RRC connection setup procedure for IMSI attach • The result is timing such that the PS transport blocks arrive at the BTS within the window start and end points • Once the transmission resource allocations have been configured the RNC sends a NBAP: Radio Link Reconfiguration Commit message to the BTS UE Node B RNC SGSN Call Established Measurement Report : e4a NBAP: Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF FP: Downlink Sync FP: Uplink Sync For internal use 103 © Nokia Siemens Networks Presentation / Author / Date .

it follows this up by sending an RRC: Radio Bearer Reconfiguration • The information contained in this message is largely the same as that sent to the BTS in the NBAP: Radio Link Reconfigure Prepare • The UE acknowledges the RRC: Radio Bearer Reconfiguration message with a RRC: Radio Bearer Reconfiguration Complete message • RNC sends RRC: Measurement Control message to the UE to stop the UE traffic volume measurements (as the UL is having max bit rate already) • The required user bit rate connection is now established and data flow between UE client and server is open UE Node B RNC SGSN Call Established Measurement Report : e4a NBAP: Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF FP: Downlink Sync FP: Uplink Sync RRC: Radio Bearer Reconfiguration (DCH) RRC: Radio Bearer Reconfiguration Complete (DCH) For internal use 104 © Nokia Siemens Networks Presentation / Author / Date .Radio Bearer Reconfiguration • Once the RNC has sent the NBAP: Radio Link Reconfiguration Commit message to the BTS.

Module 3 .State Transitions For internal use 105 © Nokia Siemens Networks Presentation / Author / Date .Signalling Flows PS Call .

no capacity requests from UE or RNC the UE is moved to Cell_PCH where the UE only listens PCH • (paging Typical UE power consumptions for channel) UTRAN Connected Mode different states. cell state transition from Cell_DCH to Cell_FACH occurs • In order to save some UE battery power (as in Cell_FACH the UE has to read FACH channel all the time) in case of further inactivity i.RRC State transitions for PS call • When the RNC notices that there is nothing being transmitted between UE and RNC inactivity timers will start to run and in case of expiry of those timers the UE is moved to use common channels i.e. URA_PC CELL_P • Cell_DCH H URA update CH ~200-300mW Inactivity Inactivity Cell timer • Cell_FACH timer update expires expires or or after ~100-200mw after URA Establish DCH cell • URA_PCH/Cell_PCH/Idle <5mw update update CELL_D CELL_FA CH Explicit signalling or CH inactivity timer expiration Release RRC Establish RRC Release RRC ConnectionConnection Connection Idle Mode For internal use 106 © Nokia Siemens Networks Presentation / Author / Date .e.

DCH to FACH Transition UE Node B RNC SGSN GPRS Attach Call Established Measurement Report : e4a NBAP: Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF FP: Downlink Sync FP: Uplink Sync All data is sent and RLC Radio Link Reconfiguration Commit buffer is empty RRC: Radio Bearer Reconfiguration (DCH) RRC: Radio Bearer Reconfiguration Complete (DCH) Inactivity timer expires Measurement Control Data Flow RRC: Radio Bearer Reconfiguration (DCH) RRC: Radio Bearer Reconfiguration Complete (RACH) Measurement Control (FACH) NBAP: Radio Link Deletion Request NBAP: Radio Link Deletion Response ALCAP: Release Request ALCAP: Release Confirm UE in Cell_FACH. PDP Context Active and GPRS Attached For internal use 107 © Nokia Siemens Networks Presentation / Author / Date .

the ALCAP protocol is used to release the Iub resources • The ACLAP: Release Request is used to release the Iub resources • The RNC replies to the ACLAP: Release Request message with a ACLAP: Release Confirm message For internal use 108 © Nokia Siemens Networks Presentation / Author / Date .DCH to FACH transition • In case the RNC decides to move the UE to Cell_FACH state it sends RRC: Radio Bearer Reconfiguration • The UE acknowledges the RRC: Radio Bearer Reconfiguration message with a RRC: Radio Bearer Reconfiguration Complete message on RACH • RNC sends RRC: Measurement Control message to the UE to setup the UE traffic volume measurements for the UE capacity requests (e4a) • RNC sends NBAP: Radio Link Deletion Request message to the BTS to delete the dedicated resources from the BTS for the UE moved to the Cell_FACH • The Dedicated NBAP: Radio Link Deletion Request is used to remove a radio link at a BTS • Having deleted the radio link.

FACH to DCH transition (1/2) UE WBTS RNC-NBAP RNC-RRC RNC-L2 RNC-RRM UE in cell_FACH state UE has data to RNC has data to send send RRC of UE requests MAC requests DL capacity from RRM capacity from RRM Traffic volume measurements DL capacity request RRC: Measurement report (RACH) Channel type selection UL capacity request WBTS provides periodical cell load information to RRM NBAP: Radio Resource Indication RR indication UL and DL packet scheduling For internal use 109 © Nokia Siemens Networks Presentation / Author / Date .

FACH to DCH transition (2/2) UE WBTS RNC. RNC. RNC-L2 RNC-RRM NBAP RRC RL setup (NBAP) and AAL2 transmission setup PS indicates UE about the granted capacity capacity allocation RRC: Radio Bearer Reconfiguration (FACH) L1 Sync NBAP: Synchronisation Indication sync indication L2 configuration RRC: Radio Bearer Reconfiguration complete (DCH) UE in cell_DCH state For internal use 110 © Nokia Siemens Networks Presentation / Author / Date .

RAB and RB setup • UE internal measurements are activated and in case UE has something to send in addition to just activating PDP Context • In case UE sends Measurement Report for event 4a the dedicated resources are setup with radio bearer reconfiguration • This is also reconfiguration from Cell_FACH to Cell_DCH i.e.UE GPRS Attached and PDP Deactivated in Cell_PCH (I) • In case the UE is GPRS Attached and in Cell_PCH state the UE needs to send RRC: Cell Update message indicating UL capacity request after that the PDP Context activation procedure as above where the messaging is as explained earlier • Then PDP Context is activated using common channels. asynchronous For internal use 111 © Nokia Siemens Networks Presentation / Author / Date .

UE GPRS Attached and PDP Deactivated in Cell_PCH (II) UE Node B RNC SGSN GPRS Attach Call Established Data Flow UE in Cell_PCH. GPRS Attached RRC : Cell Update (RACH) RRC : Cell Update Confirm (FACH) RRC : Utran Mobility Information Confirm (RACH) UpLink Direct Transfer : Activate PDP Context Request (RACH) Direct Transfer : Activate PDP Context Request RANAP : RAB Assignment Request RRC : Radio Bearer Setup (FACH) RRC : Radio Bearer Setup Complete (RACH) RANAP : RAB Assignment Response RRC : Measurement Control (FACH) RRC : Measurement Control (FACH) Downlink Direct Transfer : Activate PDP Context Accept (FACH) Direct Transfer : Activate PDP Context Accept RRC : Measurement Report (E4a) (RACH) NBAP : Radio Link Setup NBAP : Radio Link Setup Response RRC: Radio Bearer Reconfiguration (FACH) NBAP : Radio Link Synchronisation RRC: Radio Bearer Reconfiguration Complete (DCH) RRC : Measurement Control (DCH) RRC : Measurement Control (DCH) For internal use 112 © Nokia Siemens Networks Presentation / Author / Date .

UE GPRS Attached and PDP Activated in Idle Mode (I) • In case the UE has PDP Context active but is moved to idle mode (still attached as well) the UE must initiate RRC Connection Setup procedure before it can have any data transmission using the existing PDP Context • The RNC has to re-establish the Iu resources for the UE by CM service request For internal use 113 © Nokia Siemens Networks Presentation / Author / Date .

UE GPRS Attached and PDP Activated in Idle Mode (II) UE Node B RNC SGSN GPRS Attach Call Established Data Flow UE in idle. GPRS Attached. PDP Context Deactive RRC : RRC Connection request (RACH) NBAP : Radio Link Setup NBAP : Radio Link Setup Response RRC : RRC Connection Setup (FACH) NBAP : Radio Link Synchronisation RRC : RRC Connection Setup Complete (DCH) Initial Direct Transfer : GPRS Service Request (DCH) Initial UE Message : GPRS Service Request Security Mode Command Security Mode Complete (DCH) RRC: Uplink Direct Transfer: GPRS Activate PDP Context Request (DCH) RANAP: Direct Transfer: GPRS Activate PDP Context Request RRC: Downlink Direct Transfer : GPRS P-TMSI Reallocation Command (DCH) RANAP: Direct Transfer : GPRS P-TMSI Reallocation Command RRC: Uplink Direct Transfer : GPRS P-TMSI Reallocation Complete (DCH) RANAP: Direct Transfer : GPRS P-TMSI Reallocation Complete RRC: Radio Bearer Setup (DCH) RANAP: RAB Assignment Request RRC : Radio Bearer Setup Complete (DCH) RANAP :RAB Assignment Response RRC: Measurement Control (DCH) RRC: Measurement Control (DCH) RRC: Downlink Direct Transfer : GPRS Activate PDP Context Accept (DCH) RANAP: Direct Transfer : GPRS Activate PDP Context Accept RRC : Measurement Report (e4a) (DCH) NBAP : Radio Link Reconfiguration Prepare NBAP : Radio Link Reconfiguration Ready NBAP : Radio Link Reconfiguration Commit RRC: Radio Bearer Reconfiguration (DCH) RRC : Radio Bearer Reconfiguration Complete (DCH) For internal use Setup 64/64 114 © Nokia Siemens Networks Presentation / Author / Date RRC: Measurement Control (DCH) .

PS Call 115 © 2005 Nokia V1-Filename.Module 3 – Signalling Flows Cell Change Order .ppt / yyyy-mm-dd / Initials .

ISHO PS Call UE WBTS RNC CN RCC: Measurement RCC: Measurement Control Report NBAP: RL Reconfigure Reporting Prepare Event NBAP: RL Reconfigure Triggered Ready NBAP: RL Reconfigure Commit RCC: Physical Channel RCC: Physical Channel Reconfiguration Reconfiguration Complete NBAP: Compressed Mode BSIC Command verification RCC: Measurement not often RCC: Measurement Control required for PS Report RCC: Cell Change Order from UTRAN Command RANAP: SRNC Context UE performs LAU to Request 2G SGSN followed by RANAP: SRNC Context RAU Request Response RANAP: SRNC Data Forwarding Data is forwarded to 2G SGSN (from 3G SGSN) until UE Command location is updated and data is sent directly to 2G SGSN NBAP: Radio Link RANAP: Iu Release Failure Command RANAP: Iu Release NBAP: Radio Link Deletion Complete NBAP: Radio Link Deletion Request Response AAL2: Release Request AAL2: Release Response For internal use 116 © Nokia Siemens Networks Presentation / Author / Date .

Signalling Flows SRNC Relocation Procedure For internal use 117 © Nokia Siemens Networks Presentation / Author / Date .Module 3 .

SRNS Relocation Procedure CN CN CN CN Iu Iu Iu Iu Iu Iu Iu Iu RNC RNC RNC RNC RNC RNC RNC RNC Iur Iur Iur Iur SRNS “SRNS“ Relocation Anchoring For internal use 118 © Nokia Siemens Networks Presentation / Author / Date .

SRNC Relocation for RT Source RNC CN Target RNC MS SRNC Relocation Decision RANAP:Relocation Required • SRNC Relocation starts when all the cells of the x RANAP:Relocation Request active set belong to a different RNC Start RelocPrep timer • In successful case after sending the Relocation Start RelocOverall required message to CN there will be Relocation timer Request sent to target RNC RANAP:Relocation Request Ack x • In case of ACK from target RNC there will be User plane set -up Stop RelocPrep RANAP: Relocation Command sent from CN to timer x RANAP:Relocation Command Source RNC xRNSAP:Relocation Commit • After that the Source RNC sends RANSAP: Start RelocOverall SRNC operation Relocation Commit message over Iur to the timer started Target RNC RANAP:Relocation Detect • When target RNC starts SRNC operation and UP switching RRC:UTRAN Mobility Information detects that the relocation is successful there will be RANAP: Relocation Detect message sent from RRC:UTRAN Mobility Information Confirm target RNC to CN Stop RelocOverall RANAP:Relocation complete timer x • At the same time RRC: UTRAN Mobility RANAP:Iu Release x Stop RelocOverall Information is sent to the UE and after confirm RANAP:Iu Release Complete timer from UE the target RNC informs CN with RANAP: Relocation Complete –message that the User plane release relocation procedure was successful and Iu is released from source RNC For internal use 119 © Nokia Siemens Networks Presentation / Author / Date .

SRNC Relocation for NRT Source RNC CN Target RNC MS SRNC Relocation Decision RANAP:Relocation Required • Procedure is similar with RT but: x Start RelocPrep timer RANAP:Relocation Request • A timer T_Reloc_Inhibit_NRT is Start RelocOverall timer started when the HC of the SRNC RANAP:Relocation Request Ack x has made a decision to initiate a User plane set -up Stop RelocPrep timer SRNC Relocation procedure for RANAP:Relocation Command x the MS using a NRT (only) service Start TDataFwd timer in Cell_DCH state Data tunnel xRNSAP:Relocation Commit • After the reception of the RANAP: Start RelocOverall SRNC operation started Relocation Command message timer RANAP:Relocation Detect from the CN the Source RNC UP switching RRC:UTRAN Mobility Information establishes a unidirectional data RRC:UTRAN Mobility Information Confirm forwarding tunnel with the Stop RelocOverall timer RANAP:Relocation complete Target RNC and it starts x x RANAP:Iu Release TDataFwd timer. Stop RelocOverall RANAP:Iu Release Complete timer User plane release For internal use 120 © Nokia Siemens Networks Presentation / Author / Date .

the SRNC Relocation procedure is started immediately • If the PS receives a DL or UL capacity request during the T_Reloc_Inhibit_NRT.e. If a RAB assignment request is received during T_Reloc_Inhibit_NRT. the SRNC Relocation procedure is started immediately • If a soft handover is executed (i.SRNC Relocation for NRT in DCH . the timer is stopped and the preparation for SRNC Relocation is terminated • The handover measurements from the MS using a NRT (only) service are handled normally.Decision • New RAB assignment requests received from the CN(s) during the SRNC Relocation procedure (including the inhibition period) are rejected with a cause value "Relocation Triggered". a soft handover branch is setup in the SRNC or a different neighboring RNC than the current DRNC) before expiration of the timer T_Reloc_Inhibit_NRT. and thus the SHO in this stage is possible • There is defined a failure counter for cancellations of SRNC Relocation procedures due to inactivity of NRT (only) services during the relocation signaling • The exact value of timer T_Reloc_Inhibit_NRT could be set in accordance with a success rate of the (NRT) relocation procedures For internal use 121 © Nokia Siemens Networks Presentation / Author / Date .

UL message ] RRC makes relocation started in the SRNC The MS selects a cell controlled decision (SRNC by the target RNC and initiates relocation is supported a RRC:Cell/URA Update by the DRNC and CN) when an RRC:Cell/URA procedure via the BTS2 RANAP:Relocation Required Update message is RANAP:Relocation Request received from the MS via RANAP:Relocation Request Acknowledge [May include addresses for DL PDUs towards a target RNC and the target RNC] User plane establishment through the RANAP:Relocation Command RNSAP:UPLINK [May include addresses for DL PDUs which the source RNC may forward to the target RNC] SIGNALLING TRANSFER Data Forwarding (if addresses received from CN) INDICATION message . D-RNTI. SRNC-ID. the SRNC RRC:Cell/URA Update [ Cell/URA Update Cause. RNSAP:Relocation Commit RRC:Cell/URA Update Confirm [ D-RNTI . new S-RNTI. Resource For internal use releasing 122 © Nokia Siemens Networks Presentation / Author / Date . CELL_PCH or URA_PCH state • If the state of the MS is The MS moves to the CELL_FACH state (if CELL_FACH. (new C-RNTI) ] RANAP:Relocation Detect RRC:UTRAN Mobility Information Confirm RANAP:Relocation Complete MS is in CELL_FACH .5 the target RRC state RANAP:Iu Release Command of the MS is decided based on the RRC state information RANAP:Iu Release Complete received from the source RNC. U-RNTI ] RNSAP:Uplink Signalling Transfer Indication Relocation procedure is [ new C-RNTI.SRNC Relocation for NRT in FACH / PCH MS BTS1 BTS2 Target RNC Source RNC PS CN MS is in CELL_FACH. CELL_PCH not already there) or(URA_PCH. CELL_PCH or URA_PCH state In RAN1. may include Direct Transfer messages and RAB Context information] [ S-RNTI. new SRNC-ID.

the ongoing relocation procedure is cancelled with a cause value ‘Failure in the Radio Interface Procedure’ and a RRC Connection Release message with a cause value ''Directed Signalling Connection Re-establishment' is sent to the MS. • If there is no response from the CN to the RANAP:RELOCATION REQUIRED message before the RANAP timer TRelocPrep expires. the message with a cause value is ‘RLC unrecoverable error’ is received (during the SRNC relocation procedure) before the RNSAP:RELOCATION COMMIT message has been sent to the target RNC. these messages are ignored by the source RNC and relocation procedure is continued as normally. • If however. The cause value ‘Relocation Desirable for Radio Reasons’ shall be used in RANAP:RELOCATION REQUIRED message sent to the CN. For internal use 123 © Nokia Siemens Networks Presentation / Author / Date . • If repeated Cell/URA Update messages are received from the target RNC during the SRNC relocation procedure.SRNC Relocation for NRT in FACH / PCH • The SRNC Relocation procedure is started when RRC:CELL UPDATE or RRC:URA UPDATE message is received by the source RNC inside RNSAP:UPLINK SIGNALLING TRANSFER INDICATION message. the source RNC cancels the RANAP:Relocation Preparation procedure by initiating the RANAP:Relocation Cancel procedure with a cause value 'TRELOCprep expiry'.’ • After this the source RNC may reinitiate the SRNC relocation procedure. or (preferably) initiate a call re-establishment by sending an RRC:RRC CONNECTION RELEASE message with a cause value ''Directed Signalling Connection Re- establishment' to the MS.

RANAP RANAP cause value Usage Time Critical Relocation Used in all coverage based relocation initiations in RAN1.SRNC Relocation – Relocation Required Source RNC CN Target RNC MS • The RANAP:RELOCATION SRNC Relocation Decision REQUIRED message contains the RANAP:Relocation Required following parameters: RANAP:Relocation Request • Information element Presence Comments • Message Type M. Not used in RAN1.5 For internal use 124 © Nokia Siemens Networks Presentation / Author / Date . RANAP • Cause M. RANAP • Relocation Type M. O&M Intervention The source cell is emptied by a forced HO procedure.5 Resource Optimisation Relocation Used in cases where all RLs in the active set of the MS are located in DRNS Relocation Desirable for Radio Reasons Used in cases where relocation is triggered by a Cell/URA update received over Iur.

Signalling Flows HSDPA Call For internal use 125 © Nokia Siemens Networks Presentation / Author / Date .Module 3 .

measuredResults trafficVolumeMeasuredResultsList : rb-Identity 5. rlc-BuffersPayload pl256 eventResults trafficVolumeEventResults : ul-transportChannelCausingEvent dch : 1. trafficVolumeEventIdentity e4a For internal use 126 © Nokia Siemens Networks Presentation / Author / Date . Setting Up the HS-DSCH Cell DCH – HS-DSCH transaction UE Node B RNC SGSN PDP Established Measurement Report : e4a • UE sends measurement report MEASUREMENT REPORT showing event 4a (buffer levels value UL-DCCH-Message ::= exceed the set threshold) integrityCheckInfo messageAuthenticationCode '00011100 11100101 11111001 01001000' • Buffer payload is 256B rrc-MessageSequenceNumber 3 message measurementReport : measurementIdentity 16.

). UE capability Information (CQI feedback. the RNC prepares to reconfigure the radio link at the BTS by sending the NBAP: Radio Link Reconfigure Prepare message • This includes HSDPA MAC-d flow information.Radio Link Reconfigure prepare / ready • Assuming that the admission control procedure within the RNC decides to accept the capacity request from UE. ACK/NACK. PO etc. Also information from HSDPA return channel is included • The BTS responds to the NBAP: Radio Link Reconfigure Prepare message with a NBAP: Radio Link Reconfigure Ready message UE Node B RNC PDP Established Measurement Report : e4a NBAP: Radio Link Reconfigure Prepare Radio Link Reconfigure Ready For internal use 127 © Nokia Siemens Networks Presentation / Author / Date .

Cell DCH – HS-DSCH transaction

UE Node B RNC

PDP Established
Measurement Report : e4a
NBAP: Radio Link Reconfigure Prepare
Radio Link Reconfigure Ready
AAL2SIG:ERQ
AAL2SIG:ECF
AAL2SIG:ERQ
AAL2SIG:ECF

• First ERQ is the setup of the UL NRT return channel for HSDPA i.e.
64kbps
• BTS WAM/AXC responds back with Establish Confirm if the reservation is ok
also from UL CAC point of view
• Second ERQ is for HS-DSCH
• BTS WAM/AXC responds back with Establish Confirm if the reservation is ok
also from UL CAC point of view

For internal use
128 © Nokia Siemens Networks Presentation / Author / Date

Setting Up the HS-DSCH

Cell DCH – HS-DSCH transaction
UE Node B RNC

PDP Established
Measurement Report : e4a
RADIO LINK RECONFIGURATION COMMIT
NBAP: Radio Link Reconfigure Prepare
NBAP-PDU
Radio Link Reconfigure Ready initiatingMessage
AAL2SIG:ERQ procedureID
- procedureCode: 30
AAL2SIG:ECF
- ddMode: common
AAL2SIG:ERQ - criticality: ignore
AAL2SIG:ECF - messageDiscriminator:
FP: Downlink Sync dedicated
transactionID
FP: Uplink Sync - longTransActionId: 66
FP: Downlink Sync initiatingMessage
FP: Uplink Sync RadioLinkReconfigurationCommit

Radio Link Reconfiguration Commit protocolIEs
- id: 143
- criticality: ignore
NodeB-CommunicationContextID:
160001
- id: 24
• After receiving NBAP: RL Reconfiguration Ready - criticality: ignore

message from BTS and successful AAL2 setup the
CFN: 40

RNC can order the BTS to commit the modification
and the exact time for modifications : CFN = 40

For internal use
129 © Nokia Siemens Networks Presentation / Author / Date

Setting Up the HS-DSCH

Cell DCH – HS-DSCH transaction
UE Node B RNC

PDP Established
Measurement Report : e4a
RADIO BEARER RECONFIGURATION [DCCH] 1
NBAP: Radio Link Reconfigure Prepare
value DL-DCCH-Message ::=
Radio Link Reconfigure Ready integrityCheckInfo
AAL2SIG:ERQ messageAuthenticationCode '11000110
10000101 10011001 10000000'B,
AAL2SIG:ECF
rrc-MessageSequenceNumber 4
AAL2SIG:ERQ message radioBearerReconfiguration :
AAL2SIG:ECF later-than-r3 :
rrc-TransactionIdentifier 0,
FP: Downlink Sync
criticalExtensions criticalExtensions : r5 :
FP: Uplink Sync radioBearerReconfiguration-r5
FP: Downlink Sync activationTime 40,

FP: Uplink Sync new-H-RNTI '00000000 00000001'B,
rrc-StateIndicator cell-DCH,
Radio Link Reconfiguration Commit
specificationMode complete :
RRC: Radio Bearer Reconfiguration (DCH)
rb-InformationReconfigList
rb-Identity 5,

• RRC: RADIO BEARER RECONFIGURATION message rlc-Info
ul-RLC-Mode ul-AM-RLC-Mode :

is used to deliver same setup information to the Retransmissions :
transmissionRLC-Discard maxDAT-

UE that was given to BTS in NBAP: RL maxDAT dat6,
timerMRW te300,
RECONFIGURATION PREPARE message maxMRW mm12
transmissionWindowSize tw128,

• The H-RNTI given to UE is the same as given to timerRST tr250,
max-RST rst12,
BTS i.e. 00000000 00000001 B pollingInfo
timerPollProhibit tpp100,

• Activation time for new configuration is CFN 40 timerPoll tp240,
poll-SDU sdu1,
(just like given to the BTS) lastTransmissionPDU-Poll TRUE,
lastRetransmissionPDU-Poll TRUE,
For internal use
130 © Nokia Siemens Networks Presentation / Author / Date pollWindow pw50

Setting Up the HS-DSCH Cell DCH – HS-DSCH transaction • The HS-DSCH Capacity request procedure provides means for the RNC to request HS-DSCH capacity from the BTS. UE Node B RNC PDP Established Measurement Report : e4a NBAP: Radio Link Reconfigure Prepare ATM Conn:10 VPI:1 VCI:120 CID:14 Line:1 CT:0 Radio Link Reconfigure Ready 524 11:26:28.604285 AAL2SIG:ERQ AAL 2 UUI: 26 (1Ah) AAL2SIG:ECF SSSAR-PDU: 7F 0A 0F 00 2A AAL2SIG:ERQ HS-DSCH CAPACITY REQUEST AAL2SIG:ECF Control Frame CRC : 63 (3Fh) FP: Downlink Sync Control Frame Type : 10 (0Ah) CmCH-PI : 15 (Fh) FP: Uplink Sync User Buffer Size : 42 (002Ah) octets FP: Downlink Sync FP: Uplink Sync Radio Link Reconfiguration Commit RRC: Radio Bearer Reconfiguration (DCH) RRC: Radio Bearer Reconfiguration Complete (DCH) For internal use HS-DSCH: Capacity Request 131 © Nokia Siemens Networks Presentation / Author / Date . by indicating the users buffer size in the RNC for a given priority level (CmCh-PI) • The RNC is allowed to reissue the HS-DSCH capacity Request if from the BS no Capacity Allocation has been received with an appropriate time threshold • Trigger: No capacity available for the data waiting in RLC buffers.

So the Node B may use this message to modify the traffic flow at any time by indicating its capacity to deliver PDU UE Node B RNC PDP Established Measurement Report : e4a NBAP: Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF AAL2SIG:ERQ AAL2SIG:ECF FP: Downlink Sync FP: Uplink Sync FP: Downlink Sync FP: Uplink Sync Radio Link Reconfiguration Commit RRC: Radio Bearer Reconfiguration (DCH) RRC: Radio Bearer Reconfiguration Complete (DCH) HS-DSCH: Capacity Request HS-DSCH: Capacity Allocation For internal use 132 © Nokia Siemens Networks Presentation / Author / Date . The Node-B does know the status of the buffers in the RNC by the capacity request and by every further data frame .Cell DCH – HS-DSCH transaction • HS-DSCH Capacity Allocation is generated either in response to a HS-DSCH Capacity Request or at any other time • The flow control is mainly controlled by the Node-B sending capacity allocation messages.

Setting Up the HS-DSCH Cell DCH – HS-DSCH transaction UE Node B RNC SGSN PDP Established Measurement Report : e4a NBAP: Radio Link Reconfigure Prepare Radio Link Reconfigure Ready AAL2SIG:ERQ AAL2SIG:ECF AAL2SIG:ERQ AAL2SIG:ECF FP: Downlink Sync FP: Uplink Sync FP: Downlink Sync FP: Uplink Sync Radio Link Reconfiguration Commit RRC: Radio Bearer Reconfiguration (DCH) RRC: Radio Bearer Reconfiguration Complete (DCH) Measurement Control HS-DSCH: Capacity Request HS-DSCH: Capacity Allocation HSDPA Traffic For internal use 133 © Nokia Siemens Networks Presentation / Author / Date .

Module 3 – Signalling Flows Summary • An understanding of the various signalling flows together with the information contained in different messages is an essential element in the optimisation engineers’ toolbox For internal use 134 © Nokia Siemens Networks Presentation / Author / Date .

2007 HSDPA signalling added. Steve Hunt. 04. Gareth Davies.0 24.Version control Version Date Status Owner RAN04 2006 Base version Mike Roche. added some signalling flows Checked for RAS051 level For internal use 135 © Nokia Siemens Networks Presentation / Author / Date . Video call Kirsi Teravainen signalling. Pekka Ranta RAS051_v1.