Ned call-setup-and-release

85
Call Setup and Release DN03471581 Issue 5-0 en 30/05/2007 # Nokia Siemens Networks 1 (85) RNC3267 Nokia WCDMA RAN, Rel. RAS06, System Library, v. 1

description

Call setup and release in 3G

Transcript of Ned call-setup-and-release

Page 1: Ned call-setup-and-release

Call Setup and Release

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 1 (85)

RNC3267Nokia WCDMA RAN, Rel. RAS06, SystemLibrary, v. 1

Page 2: Ned call-setup-and-release

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2007. All rights reserved.

2 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 3: Ned call-setup-and-release

Contents

Contents 3

List of tables 5

List of figures 6

Summary of changes 9

1 Call setup and release 11

2 Real-time and non-real time services 15

3 RRC state 25

4 Paging 334.1 Paging the UE in idle mode 344.2 Paging the UE in connected mode 344.2.1 UE-dedicated paging procedure 354.2.2 Connected mode paging procedure 354.3 RNC-originated paging 36

5 RRC connection setup and release 395.1 RRC connection setup 395.2 RRC connection release 40

6 Signalling connection setup and release 436.1 Direct transfer 436.2 Signalling connection release 44

7 Radio link setup, reconfiguration and deletion 477.1 Radio link setup 477.2 Radio link reconfiguration 497.3 Radio link deletion 51

8 Radio access bearer setup, reconfiguration and release 538.1 Radio access bearer setup 538.2 Radio access bearer release 55

9 Ciphering and integrity protection setup 57

10 Location updates 6310.1 Cell update 63

11 Transcoder Free Operation (TrFO) and Tandem Free Operation(TFO) 65

11.1 TrFO and TFO with multimode AMR 6711.2 RNC TrFO and TFO functions 6711.3 RNC parameters 73

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 3 (85)

Contents

Page 4: Ned call-setup-and-release

11.4 Definitions 73

12 Flexible Iu 7512.1 Pool-Area 7512.2 Network Resource Identification 7612.3 Load Balancing 7712.4 RNC Parameters 7812.5 Definitions 79

13 Call setup and release statistics 81

Related Topics 83

4 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 5: Ned call-setup-and-release

List of tables

Table 1. UE cell states 26

Table 2. RNC parameter 73

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 5 (85)

List of tables

Page 6: Ned call-setup-and-release

List of figures

Figure 1. Signalling protocols 12

Figure 2. Overview of setting up a call 13

Figure 3. Mobile-originated call (CS), 1/2 16

Figure 4. Mobile-originated call (CS), 2/2 17

Figure 5. Mobile-terminated call (CS), 1/2 18

Figure 6. Mobile-terminated call (CS), 2/2 19

Figure 7. Mobile-originated call (PS), 1/2 20

Figure 8. Mobile-originated call (PS), 2/2 21

Figure 9. Mobile-terminated call (PS), 1/2 22

Figure 10. Mobile-terminated call (PS), 2/2 23

Figure 11. RRC states and state transitions 26

Figure 12. CELL_DCH to CELL_FACH state transition using radio bearerreconfiguration 29

Figure 13. CELL_FACH to CELL_DCH UL state transition 30

Figure 14. CELL_FACH to CELL_DCH DL state transition 31

Figure 15. Cell update due to UL data transmission 32

Figure 16. Paging the UE in idle mode 34

Figure 17. Paging the UE in connected mode (CELL_FACH or CELL_DCH state) 35

Figure 18. Paging the UE in connected mode (CELL_PCH state) 36

Figure 19. RNC-originated paging 37

Figure 20. Setting up an RRC connection 39

Figure 21. RRC connection setup failure and retry 40

Figure 22. RRC connection release in CELL_DCH state 41

Figure 23. Signalling connection setup 44

Figure 24. Signalling connection release requested by the CN 45

Figure 25. Signalling connection release requested by the UE (all flows are notreleased) 46

Figure 26. Radio link setup 48

Figure 27. Radio link setup failure 48

6 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 7: Ned call-setup-and-release

Figure 28. Synchronised radio link reconfiguration 50

Figure 29. Radio link reconfiguration failure 51

Figure 30. Radio link deletion 52

Figure 31. Radio access bearer establishment procedure (DCH to DCH) 54

Figure 32. Failure in radio access bearer establishment 55

Figure 33. Radio access bearer release 56

Figure 34. Ciphering and integrity procedure overview 60

Figure 35. Setting up ciphering and integrity protection 61

Figure 36. Cell update due to periodic update 64

Figure 37. Basic architecture for UMTS to UMTS TrFO connection 66

Figure 38. RAB Assignment procedure 68

Figure 39. Filtering Frequent Iu UP Rate Control procedures 72

Figure 40. Pool area example 76

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 7 (85)

List of figures

Page 8: Ned call-setup-and-release

8 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 9: Ned call-setup-and-release

Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes between issues 3-1 and 4-0

A new chapter has been added: Flexible Iu

Changes between issues 3-0 and 3-1

Editorial corrections. No changes in the technical content.

Changes between issues 2-0 and 3-0

Chapter Transcoder Free Operation (TrFO) and Tandem Free Operation(TFO)

. A new section has been added.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 9 (85)

Summary of changes

Page 10: Ned call-setup-and-release

10 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 11: Ned call-setup-and-release

1 Call setup and release

Call setup and release refers to setting up or releasing a speech or dataconnection between the end-user user equipment (UE) and the corenetwork (CN). When the UE is in the idle state, it has no radio resourcecontrol connection (RRC connection) to the radio access network. RRC isused to optimise the capability of the UE in sending and receiving signalsover the air interface. Only one RRC connection is used at any one timebetween the UE and the network, regardless of the number of radioaccess bearers (RABs) and services used.

The RRC connection is always initiated by the UE, and its establishmentand release is handled by the RRC protocol. Once the RRC connection isestablished, it is possible to take into use various radio bearers (RB) andsignalling radio bearers (SRB). The role of this radio bearer service is tocover all the aspects of the radio interface transport. These radio bearerscan make use of both dedicated RRC channels and common channels.On common channels, RACH is used in uplink and FACH in downlink. Theradio access bearer service handles circuit-switched speech calls, circuit-switched data calls as well as packet-switched data calls.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 11 (85)

Call setup and release

Page 12: Ned call-setup-and-release

Figure 1. Signalling protocols

RANAP layer

The RANAP layer includes all the RANAP signalling entities of the RNCand the related application for RANAP signalling entity management.

A RANAP signalling entity is a serving RNC functionality responsible forthe RANAP connection-specific signalling and information managementbetween the RNC and core network for the UE.

RNSAP layer

The RNSAP layer includes all the RNSAP signalling entities of the RNCand the related application for RNSAP signalling entity management.

A RNSAP signalling entity is an RNC functionality responsible for RNSAP-connection-specific signalling and information management between twoRNCs for the UE.

NBAP layer

The NBAP layer includes all common and dedicated NBAP signallingentities of the RNC or the BTS and the related application for the NBAPsignalling entity management.

8.6.00

NBAP

Iub

DRNC

RNSAP

Iur

Iub Iu

SRNC

RANAP

CN

12 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 13: Ned call-setup-and-release

A common NBAP signalling entity is a BTS or a controlling RNCfunctionality responsible for the logical resource management, BCHmanagement, and communication context creation for one BTS.

A dedicated NBAP signalling entity is a BTS or a controlling RNCfunctionality responsible for the radio link management for a group of UEs.

RRC layer

The RRC layer includes all the RRC signalling entities of the RNC and therelated application for RRC signalling entity management.

The RRC signalling entity is a serving RNC functionality responsible forthe RRC connection-specific signalling and information management forthe UE.

Overview of setting up a call

The procedure of setting up a call depends on whether the call is mobile-originated or mobile-terminated.

Figure 2. Overview of setting up a call

In case of a mobile-terminated call (MTC), the process starts with paging.Paging is the procedure by which a mobile network attempts to locate theUE within its location area before any other network-initiated procedurecan take place.

Mobile-terminated call (MTC)

Mobile-originated call (MOC)

Paging Radio linksSignallingconnection

RRCconnection

Radio accessbearer

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 13 (85)

Call setup and release

Page 14: Ned call-setup-and-release

If the UE originates the call, paging is not needed and the UE directlyrequests RRC connection setup.

After having established an RRC connection, the UE starts setting up asignalling connection to the CN. For that, a new radio link is needed.

Finally, the radio access bearer setup procedure builds a radio accessbearer service between the UE and the core network (CN), and the call isestablished.

14 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 15: Ned call-setup-and-release

2 Real-time and non-real time services

Real-time (RT) services involve mobile-originated and mobile-terminatedspeech and data calls, as well as real time packet-switched (PS) datatransmissions.

Non-real time (NRT) handles only packet-switched transmissions.Individual procedures presented in the figures are described in Call setupand release.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 15 (85)

Real-time and non-real time services

Page 16: Ned call-setup-and-release

Figure 3. Mobile-originated call (CS), 1/2

UE BTS RNC MSC

AAL2 Setup

RRC:RRC CONNECTION SETUP

RANAP:INITIAL UE MESSAGE

NBAP:RADIO LINK RESTORE INDICATION

RRC:CONNECTION SETUP COMPLETE

RRC:INITIAL DIRECT TRANSFER

NBAP:RADIO LINK SETUP REQUEST

RRC:RRC CONNECTION REQUEST

NBAP:RADIO LINK SETUP RESPONSE

RANAP:COMMON ID

UE-CN signalling

RANAP:SECURITY MODE COMMAND

RRC:SECURITY MODE COMMAND

RRC:SECURITY MODE COMPLETE

RANAP:SECURITY MODE COMPLETE

L1 synchronisation

16 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 17: Ned call-setup-and-release

Figure 4. Mobile-originated call (CS), 2/2

The following figure illustrates the mobile-terminated circuit-switched (CS)call. The only difference between a mobile-originated and mobile-terminated call is that only mobile-terminated calls include paging the UE.

MS BTS RNCUE

AAL2 Setup

RANAP:RAB ASSIGNMENT REQUEST

NBAP:RADIO LINK RECONFIGURATION PREPARE

NBAP:RADIO LINK RECONFIGURATION READY

AAL2 Setup

Connection established

NBAP:RADIO LINK RECONFIGURATION COMMIT

RRC:RADIO BEARER SETUP

RRC:RADIO BEARER SETUP COMPLETE

RANAP:RAB ASSIGNMENT RESPONSE

MSC

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 17 (85)

Real-time and non-real time services

Page 18: Ned call-setup-and-release

Figure 5. Mobile-terminated call (CS), 1/2

UE BTS RNC MSC

AAL2 Setup

RRC:RRC CONNECTION SETUP

RANAP:INITIAL UE MESSAGE

RRC:CONNECTION SETUP COMPLETE

RRC:INITIAL DIRECT TRANSFER

NBAP:RADIO LINK SETUP REQUEST

RRC:RRC CONNECTION REQUEST

NBAP:RADIO LINK SETUP RESPONSE

RANAP:COMMON ID

UE-CN signalling

RANAP:SECURITY MODE COMMAND

RRC:SECURITY MODE COMMAND

RRC:SECURITY MODE COMPLETE

RANAP:SECURITY MODE COMPLETE

RRC: PAGING TYPE 1

RANAP: PAGING

L1 synchronisation

NBAP:RADIO LINK RESTORE INDICATION

18 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 19: Ned call-setup-and-release

Figure 6. Mobile-terminated call (CS), 2/2

Non-real time services only involve packet-switched data calls. For non-real time services, the radio access bearer is created without immediatelyreserving radio resources. The resources are allocated on demand byusing the signalling link between the UE and the RNC. The followingfigures illustrate the process of establishing a packet-switched call.

MS BTS RNCUE

AAL2 Setup

RANAP:RAB ASSIGNMENT REQUEST

NBAP:RADIO LINK RECONFIGURATION PREPARE

NBAP:RADIO LINK RECONFIGURATION READY

AAL2 Setup

Connection established

NBAP:RADIO LINK RECONFIGURATION COMMIT

RRC:RADIO BEARER SETUP

RRC:RADIO BEARER SETUP COMPLETE

RANAP:RAB ASSIGNMENT RESPONSE

MSC

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 19 (85)

Real-time and non-real time services

Page 20: Ned call-setup-and-release

Figure 7. Mobile-originated call (PS), 1/2

UE BTS RNC SGSN

AAL2 Setup

RRC:RRC CONNECTION SETUP

RANAP:INITIAL UE MESSAGE

RRC:CONNECTION SETUP COMPLETE

RRC:INITIAL DIRECT TRANSFER

NBAP:RADIO LINK SETUP REQUEST

RRC:RRC CONNECTION REQUEST

NBAP:RADIO LINK SETUP RESPONSE

RANAP:COMMON ID

UE-CN signalling

RANAP:SECURITY MODE COMMAND

RRC:SECURITY MODE COMMAND

RRC:SECURITY MODE COMPLETE

RANAP:SECURITY MODE COMPLETE

L1 synchronisation

NBAP:RADIO LINK RESTORE INDICATION

20 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 21: Ned call-setup-and-release

Figure 8. Mobile-originated call (PS), 2/2

The following figure illustrates the mobile-terminated packet-switched call.The only difference between mobile-originated and mobile-terminatedcalls is that only mobile-terminated calls include paging the UE.

MS BTS RNCUE

RANAP:RAB ASSIGNMENT REQUEST

GTP Tunnel setup

Connection established (CELL_DCH state)

RRC:RADIO BEARER SETUP

RRC:RADIO BEARER SETUP COMPLETE

RANAP:RAB ASSIGNMENT RESPONSE

SGSN

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 21 (85)

Real-time and non-real time services

Page 22: Ned call-setup-and-release

Figure 9. Mobile-terminated call (PS), 1/2

UE BTS RNC SGSN

AAL2 Setup

RRC:RRC CONNECTION SETUP

RANAP:INITIAL UE MESSAGE

RRC:CONNECTION SETUP COMPLETE

RRC:INITIAL DIRECT TRANSFER

NBAP:RADIO LINK SETUP REQUEST

RRC:RRC CONNECTION REQUEST

NBAP:RADIO LINK SETUP RESPONSE

RANAP:COMMON ID

UE-CN signalling

RANAP:SECURITY MODE COMMAND

RRC:SECURITY MODE COMMAND

RRC:SECURITY MODE COMPLETE

RANAP:SECURITY MODE COMPLETE

RRC:PAGING TYPE 1

RANAP: PAGING

L1 synchronisation

NBAP:RADIO LINK RESTORE INDICATION

22 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 23: Ned call-setup-and-release

Figure 10. Mobile-terminated call (PS), 2/2

MS BTS RNCUE

RANAP:RAB ASSIGNMENT REQUEST

GTP Tunnel setup

Connection established (CELL_DCH state)

RRC:RADIO BEARER SETUP

RRC:RADIO BEARER SETUP COMPLETE

RANAP:RAB ASSIGNMENT RESPONSE

SGSN

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 23 (85)

Real-time and non-real time services

Page 24: Ned call-setup-and-release

24 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 25: Ned call-setup-and-release

3 RRC state

Radio resource control (RRC) state is also called packet data transferstate.

The description of the packet data transfer states given here is based onthe 3GPP RRC protocol specification. The Figure RRC states and statetransitions shows the supported RRC states and state transitions.

The RRC handles the control plane signalling of layer 3 between the UEsand RAN. RRC allows a dialogue between the RAN and the UE and alsobetween the core network and the UE. An RRC connection is a logicalconnection between the UE and the RAN used by two peer entities tosupport the upper layer exchange of information flows. There can only beone RRC connection per UE. Several upper layer entities use the sameRRC connection.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 25 (85)

RRC state

Page 26: Ned call-setup-and-release

Figure 11. RRC states and state transitions

When a signalling connection exists, there is an RRC connection and theUE is in UTRAN connected mode. In UTRAN connected mode, theposition of the UE is known on cell level. The UE leaves the UTRANconnected mode and returns to idle mode when the RRC connection isreleased or at RRC connection failure. When the UE position is known oncell level, it is either in CELL_FACH, CELL_DCH or CELL_PCH state. TheRRC connection mobility is then handled by handover procedures and cellupdates.

Table 1. UE cell states

UE cell state Description

CELL_DCH UE receives and transmits on the dedicated trafficchannel (DCH).

The location of the UE is known on the cell level.

CELL_FACH UE receives on the forward access channel (FACH)and transmits on the random access channel (RACH).

The location of the UE is known on the cell level.

UTRAN Connected Mode

Establish RCCConnection

Release RRCConnection

Release RRCConnection

CELL_PCH

CELL_DCH

Idle Mode

URA_PCH

CELL_FACH

26 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 27: Ned call-setup-and-release

Table 1. UE cell states (cont.)

UE cell state Description

CELL_PCH UE receives on the paging channel (PCH).

The location of the UE is known on the cell level.

If the UE has something to transmit, it transfers toCELL_FACH state.

CELL_DCH

The CELL_DCH state is characterised by the allocation of a dedicatedtransport channel to the UE. The UE is transferred from idle mode to theCELL_DCH substate through the setup of an RRC connection, or byestablishing a dedicated channel (DCH) from the CELL_FACH state.Transition from CELL_DCH state to idle mode is realised through therelease of the RRC connection. Transition from CELL_DCH substate toCELL_FACH substate is performed when the last active NRT DCH isreleased and the RT RABs do not exist.

CELL_FACH

In the CELL_FACH substate the UE monitors a forward access channel(FACH). In this state, the UE is able to transmit uplink control signals andmay be able to transmit small data packets on the random access channel(RACH). A transition from CELL_FACH to CELL_DCH state occurs, whena dedicated transport channel is established through explicit signalling.While in the CELL_FACH substate, the UE monitors the FACHcontinuously and therefore it should be moved to the CELL_PCH substatewhen the data service has been inactive for a while, as defined by theelapse of an inactivity timer. When the timer expires, the UE is transferredto the CELL_PCH state in order to decrease UE power consumption. Also,when the UE is moved from the CELL_PCH state to the CELL_FACH stateto perform a cell update procedure, the UE state is changed back toCELL_PCH state if neither the UE nor the network has any data to transmitafter the procedure has been performed. When the RRC connection isreleased, the UE is moved to idle mode.

CELL_PCH

In the CELL_PCH substate the UE listens to the PCH transport channel.The dedicated control channel (DCCH) logical channel cannot be used inthis substate. If the network wants to initiate any activity, it needs to make apaging request on the PCCH logical channel in the known cell to initiateany downlink activity. The UE initiates a cell update procedure when itselects a new cell. The only overhead in keeping a UE in the PCH substate

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 27 (85)

RRC state

Page 28: Ned call-setup-and-release

is the potential possibility of cell updating, when the UE moves to othercells. To reduce this overhead, the UE is moved to the URA_PCH statewhen low activity is observed. This can be controlled with an inactivitytimer, and optionally, with a counter that counts the number of cell updates.When the number of cell updates has exceeded certain limits, the UEchanges to the URA_PCH state. The UE is transferred from CELL_PCH toCELL_FACH state either by a packet paging command from RAN orthrough any uplink access.

To conserve resources, the packet data transfer allocates the resourceswhen they are needed. When the RNC detects inactivity in either uplink ordownlink, it starts an inactivity timer in that direction. If the timer in bothdirections expires and the inactivity continues, the RNC releases thededicated resources and starts the transition of the UE from CELL_DCH toCELL_FACH state. The transition is usually done with the radio bearerreconfiguration procedure.

The radio bearer reconfiguration procedure is used if the radio link control(RLC) parameters of the NRT RB need to be reconfigured when the DCHof the NRT RB is released.

The physical channel reconfiguration procedure is used when the UE ismoved from CELL_FACH to CELL_PCH state.

The radio bearer release procedure is used when an NRT RAB and an RTRAB are simultaneously used for the same UE, and the NRT RAB hasbeen inactive (the inactivity timer has expired) when the CN releases theRT RAB.

The following figure illustrates the state transition using radio bearerreconfiguration.

28 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 29: Ned call-setup-and-release

Figure 12. CELL_DCH to CELL_FACH state transition using radio bearerreconfiguration

The transition from CELL_FACH state to CELL_DCH state is started whenthe RNC has user or control data waiting for transmission in downlinkdirection or when the UE requests capacity for user data in uplinkdirection. The RNC's resource manager (RM) checks that there are logicalresources available and allocates the requested resources. Specificallythe RM also performs code allocation to achieve the requested bit rate forthe signal by giving it an appropriate spreading code. The RM alsorequests a radio link setup procedure (for more information, see Radio linksetup).

Once a radio link is set up, the transition is done with the radio bearerreconfiguration procedure.

UE is in CELL_DCH state

Inactivity timer expires

RRC:RADIO BEARER RECONFIGURATION

RRC:RADIO BEARER RECONFIGURATION COMPLETE

UE is in CELL_FACH state

NBAP: RADIO LINK DELETION REQUEST

NBAP: RADIO LINK DELETION RESPONSE

RNCUE BTS

CELL UPDATE CONFIRM

CELL UPDATE

If another cellthan assignedone selectedby the UE

RRC: UTRAN Mobility Information Confirm

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 29 (85)

RRC state

Page 30: Ned call-setup-and-release

The radio bearer reconfiguration procedure is used, if the radio link control(RLC) parameters of the NRT RB need to be reconfigured.

The radio bearer setup procedure is used, if an NRT RAB already existsand a new RT RAB must be established.

The following figure illustrates the state transition from CELL_FACH toCELL_DCH.

Figure 13. CELL_FACH to CELL_DCH UL state transition

RNCUE BTS

UE is in CELL_FACH state

RRC: RADIO BEARER RECONFIGURATION

RRC: RADIO BEARER RECONFIGURATION COMPLETE

NBAP Radio Link Setup

RRC:MEASUREMENT REPORT

UE is in CELL_DCH state

30 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 31: Ned call-setup-and-release

Figure 14. CELL_FACH to CELL_DCH DL state transition

Uplink data transmission can cause a cell update as illustrated in the figurebelow.

RNCUE BTS

UE is in CELL_FACH state

RRC: RADIO BEARER RECONFIGURATION

RRC: RADIO BEARER RECONFIGURATION COMPLETE

NBAP Radio Link Setup

UE is in CELL_DCH state

DL capacity need detected

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 31 (85)

RRC state

Page 32: Ned call-setup-and-release

Figure 15. Cell update due to UL data transmission

RNCUE BTS

UL capacity need is detected by MAC

UE moves to CELL_FACH state

UE is in CELL_PCH state

RRC:CELL UPDATE CONFIRM

RRC:CELL UPDATE

RRC:UTRAN MOBILITY INFORMATION CONFIRM

UE is in CELL_FACH state

32 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 33: Ned call-setup-and-release

4 Paging

Paging is necessary in order for the CN to know to which BTS and cell aspecific UE is currently linked. In idle mode, paging is always initiated bythe CN. In CS paging, the CN and further the RNC broadcast pagingmessages through base stations of the location area in which the UE issituated. In PS paging, the CN and further the RNC broadcast pagingmessages through base stations of the routing area in which the UE issituated.

To save on power consumption, the UE can use discontinuous reception(DRX). This means that the network pages the UE according to a presetsequence of frames during specific intervals. This preset frame sequenceinterval is called a DRX cycle. DRX cycles can vary in length, and in casethe UE is connected to two different CN domains with different DRX cyclelengths, the UE uses the shortest DRX cycle. The UE can store eachdomain-specific DRX cycle of each CN it is currently attached to.

If the CN sends a specific DRX cycle length coefficient, the RAN uses it inthe paging message. If there is no CN-specific coefficient, the RAN usesthe default value for CN-specific DRX cycle length coefficient in the radionetwork database.

The RNC sends paging requests to all WCDMA BTSs which belong to thepaging area where the UE is currently registered. The cells in a single BTScan belong to different paging areas.

Each paging message on the Iu interface involves only the UE andtherefore, the RNC has to pack the pages into the relevant radio interfacepaging message.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 33 (85)

Paging

Page 34: Ned call-setup-and-release

4.1 Paging the UE in idle mode

The RNC checks whether the paged UE is engaged in an ongoing radioresource control (RRC) connection. If there is no connection, the RNCstarts the idle mode paging procedure. As a result, the UE starts the RRCconnection setup procedure.

The procedure using the PAGING TYPE 1 message is referred to aspaging procedure in the 3GPP RRC specification.

Figure 16. Paging the UE in idle mode

4.2 Paging the UE in connected mode

The RNC checks whether the paged UE already has an RRC connection.

If it does not, the idle mode paging procedure using RRC:PAGING TYPE 1message is applied. The CN is responsible for making repetitions for thispaging procedure.

If the UE is in UTRA RRC connected mode, also the RRC state of the UEis checked. Depending on the current RRC state, the RNC initiates a UE-dedicated paging procedure or a connected mode paging procedure.

CNUE BTS

PAGING TYPE 1

RANAP:PAGING

UE has no RRC connection

RRC connection establishment

Paging response

RNC

34 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 35: Ned call-setup-and-release

4.2.1 UE-dedicated paging procedure

If the UE is in CELL_DCH or CELL_FACH state, there is a dedicatedsignalling link allocated for the UE in the Uu interface. The RNC sends apaging message (RRC:PAGING TYPE 2) to an RRC-connected UEthrough the existing RRC connection.

The procedure using the PAGING TYPE 2 message is referred to as UE-dedicated paging procedure in the 3GPP RRC specification.

Figure 17. Paging the UE in connected mode (CELL_FACH or CELL_DCHstate)

4.2.2 Connected mode paging procedure

If the UE is in CELL_PCH or URA_PCH state, the RNC originates thepaging procedure (RRC:PAGING TYPE1). The paging procedure can betriggered due to an idle mode paging received from the CS CN or due todownlink data (or signalling) received from the PS CN. If there is noresponse received from the UE, the RNC repeats the paging procedure ina predefined interval.

CN 2UE BTS RNC CN 1

UE has signalling connection to CN1

UE is in CELL_FACH or CELL_DCH state

Paging response to CN 2

RRC:PAGING TYPE 2

RANAP:PAGING

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 35 (85)

Paging

Page 36: Ned call-setup-and-release

Figure 18. Paging the UE in connected mode (CELL_PCH state)

4.3 RNC-originated paging

To save its battery, the UE can reside on common channels (the pagingchannel) while still maintaining the RRC connection to the RNC. In such acase, the RNC needs to page the UE when there is downlink user data ora downlink signalling message addressed to the UE. This is because inCELL_PCH state, the DCCH logical channel cannot be used. Therefore,the RNC transmits a paging request on the PCCH logical channel in theknown cell where the UE is located. The RNC's RRC signalling entitystarts the paging procedure. As a response, the UE moves to theCELL_FACH state and starts the cell update procedure with the causepaging response.

If the UE in CELL_PCH state needs to transmit anything to the RAN, itmoves to the CELL_FACH state and executes a cell update procedurewith the cause UL data transmission.

CN 2UE BTS RNC CN 1

UE has signalling connection to CN1

UE is in CELL_PCH state

Paging response to CN 2

RANAP:PAGING

RRC:PAGING TYPE 1

UE performs a cell update with the cause "paging response"

UE is in CELL_FACH state

36 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 37: Ned call-setup-and-release

Figure 19. RNC-originated paging

UE BTS RNC

UE is in CELL_PCH state

RRC: PAGING TYPE 1

DL data or DL signalling messages

UE makes a transition from CELL_PCH to CELL_FACH

UE performs a cell update with the cause "paging response"

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 37 (85)

Paging

Page 38: Ned call-setup-and-release

38 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 39: Ned call-setup-and-release

5 RRC connection setup and release

5.1 RRC connection setup

The radio resource control (RRC) connection is always started by the UE.The UE sends a message to the RNC requesting RRC connection setup.The RNC sets up a radio link and sends the UE the physical channelinformation. After the UE has synchronised itself to the WCDMA BTS, ittransmits an acknowledgement to the RNC.

Once the UE has set up the RRC connection, it can send higher-layermessages, for instance, a call setup message.

Figure 20. Setting up an RRC connection

RNCUE BTS

RRC: RRC CONNECTION SETUP

L1 synchronisation

Radio link setup

RRC: RRC CONNECTION REQUEST

RRC: RRC CONNECTION SETUP COMPLETE

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 39 (85)

RRC connection setup and release

Page 40: Ned call-setup-and-release

The following figure illustrates an example of an RRC connection failure.The RNC can fail in its attempt to set up a radio link due to hardwareblocking, for instance. Also, admission control can reject the setupattempt. In an error situation, the RNC transmits an RRC connection setupreject message, and the UE initiates an RRC connection setup retry timer.When the timer expires, the UE can attempt to set up the RRC connectionagain.

Figure 21. RRC connection setup failure and retry

Directed RRC connection setup

Directed RRC connection setup provides an efficient way to balance theload between two (or more) carrier frequencies (cells having equalcoverage areas) within one BS. The RNC balances the load byestablishing an RNC connection on the carrier frequency (cell) which hasless load. The admission control of the RNC makes a decision on whetherto perform the directed RRC connection setup procedure. Directed RRCconnection setup is controlled with RNP parameters.

5.2 RRC connection release

The RRC connection is released when the UE no longer has an activesignalling connection to any core network (CN) node. The UE and the CNnegotiate about the release, and after that, the CN sends a releasecommand. The UE in CELL_DCH state sends a layer 3 acknowledgementmessage in unacknowledged mode of RLC to the radio access network. Ifthe UE receives the release message while in CELL_FACH state, itresponds to the RAN using an acknowledged mode of RLC.

UE BTS RNC

RRC: RRC CONNECTION REJECT

RRC: RRC CONNECTION SETUP REQUEST

RRC: RRC CONNECTION REQUEST

40 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 41: Ned call-setup-and-release

After the UE response, the RNC starts the radio link release proceduretowards the BTS, releases transport bearers on the Iub interface andsends an acknowledgement to the core network. The RNC can delete theRRC entity of the UE at the same time with the radio link releaseprocedures.

Figure 22. RRC connection release in CELL_DCH state

UE BTS RNC CN

UE has signalling connection to one CN

Radio link deletion procedure

RANAP: IU RELEASE COMMAND

RRC: RRC CONNECTION RELEASE

RANAP: IU RELEASE COMPLETE

RRC: RRC CONNECTION RELEASE COMPLETE

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 41 (85)

RRC connection setup and release

Page 42: Ned call-setup-and-release

42 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 43: Ned call-setup-and-release

6 Signalling connection setup and release

6.1 Direct transfer

After having established an RRC connection, the UE starts setting up asignalling connection to the core network (CN). The UE sends a messageto the RNC which generates a different message to the CN, depending onwhether or not there is an active signalling connection to the CN domain.

The UE initiates signalling connection establishment to the CN after havingestablished an RRC connection with an RRC:INITIAL DIRECTTRANSFER message. This message triggers the upper layers to initiate asignalling connection to the core network and to transfer a non-accessstratum (NAS) message. The RNC establishes a signalling connection andforwards the (NAS) message of the RRC:INITIAL DIRECT TRANSFERmessage to the CN using a RANAP:INITIAL UE MESSAGE message.

If the RNC fails in transferring the message to the UE, the CN does not getan indication of the failure. Higher layers are used to repeat the message.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 43 (85)

Signalling connection setup and release

Page 44: Ned call-setup-and-release

Figure 23. Signalling connection setup

6.2 Signalling connection release

Signalling connection release can be requested by the CN or by the UE.The UE can have an ongoing signalling connection to one circuit-switchedand one packet-switched core network simultaneously. If one network thenrequests the release of the signalling connection by running the Iu releaseprocedure, the RNC detects that there is still another signalling connectionusing the current RRC connection. The RRC connection is not releasedbut the UE is informed that one of the signalling connections is released.

UE BTS RNC CN

RRC: INITIAL DIRECT TRANSFER

RANAP: INITIAL UE MESSAGE

RANAP: DIRECT TRANSFER

RRC: DOWNLINK DIRECT TRANSFER

RRC: UPLINK DIRECT TRANSFER

RANAP: DIRECT TRANSFER

44 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 45: Ned call-setup-and-release

Figure 24. Signalling connection release requested by the CN

When the UE requests the release of a signalling connection, either thesignalling connection release or the RRC connection release procedure isrun. The number of current signalling connections determines which ofthese release procedures is run. If the UE has two signalling connections,the signalling connection release procedure is run (as in the figure) and theUE continues to have a signalling connection to one core network. If theUE has only one signalling connection from before, the RRC connectionrelease procedure is run after which the UE no longer is connected to anycore network.

RNC CN 1 CN 2BTSUE

UE-CN 1 signalling connection

UE-CN 2 signalling connection

UE-CN 1 signalling connection

RANAP:IU RELEASE COMMAND

RANAP:IU RELEASE COMPLETE

RRC:SIGNALLING CONNECTION RELEASE

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 45 (85)

Signalling connection setup and release

Page 46: Ned call-setup-and-release

Figure 25. Signalling connection release requested by the UE (all flows are notreleased)

RNC CN 1 CN 2BTSUE

RANAP:IU RELEASE REQUEST

RANAP:IU RELEASE COMPLETE

RRC:SIGNALLING CONNECTION RELEASE INDICATION

RANAP:IU RELEASE COMMAND

UE-CN 1 signalling connection

UE-CN 2 signalling connection

UE-CN 1 signalling connection

Release of one signalling flow

46 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 47: Ned call-setup-and-release

7 Radio link setup, reconfiguration anddeletion

7.1 Radio link setup

Radio link setup procedure is started when a new radio link is needed, forinstance, when a new signalling link is set up or when a handover isperformed. The RNC determines the radio link parameters and requestsradio link activation at the BTS. In the first radio link setup, the BTS selectsthe traffic termination point for the communication context and sends theidentification of the associated NBAP signalling link to the RNC. The radiolink allocation is valid at the BTS until the RNC orders radio link deletion.

The procedure also starts the creation or modification of a communicationcontext. Communication context contains information about all activity inone traffic termination point concerning the UE. It is used to associate a setof radio links together at the BTS.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 47 (85)

Radio link setup, reconfiguration and deletion

Page 48: Ned call-setup-and-release

Figure 26. Radio link setup

Error situations that can occur during radio link setup are illustrated in thefollowing figure. Radio link setup can fail, for example, because resourcesare not available or the controlling RNC communication context is alreadyin use. If radio link setup fails, the BTS sends a failure message to theRNC indicating the cause value. The BTS's L3 Common NBAP signallingentity sends the message to the RNC's L3 Common NBAP signallingentity.

Figure 27. Radio link setup failure

NBAP:RADIO LINK SETUP RESPONSE

AAL2 Setup

NBAP:RADIO LINK SETUP REQUEST

RRC:Assignment to UE

L1 synchronisation

UE RNCBTS

NBAP:RADIO LINK RESTORE INDICATION

UE

NBAP:RADIO LINK SETUP FAILURE

NBAP:RADIO LINK SETUP REQUEST

BTS RNC

48 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 49: Ned call-setup-and-release

7.2 Radio link reconfiguration

Synchronised radio link reconfiguration is used to add, delete or modify adedicated channel (DCH) or to modify the radio links belonging to thesame communication context. The resource manager of the RNC initiatesthe reconfiguration procedure.

The situations that can trigger the radio link reconfiguration procedure are:

. radio access bearer setup (AAL2 setup)

. radio access bearer negotiation (possible AAL2 setup, switching,and release)

. radio access bearer release (AAL2 release)

. NRT radio access bearer scheduling (AAL2 setup, possible AAL2switching, AAL2 release).

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 49 (85)

Radio link setup, reconfiguration and deletion

Page 50: Ned call-setup-and-release

Figure 28. Synchronised radio link reconfiguration

Radio link reconfiguration can fail because of a BTS capability failure orbecause there are not enough resources, for example. The BTS respondswith a failure message to the RNC's prepare message. The failuremessage indicates the failed radio links and the cause value for the failure.

UE BTS RNC

NBAP:RADIO LINK RECONFIGURATION READY

RRC:Assignment to UE

NBAP:RADIO LINK RECONFIGURATION COMMIT

NBAP:RADIO LINK RECONFIGURATION PREPARE

AAL2 Release if needed

AAL2 Switching if needed

AAL2 Setup if needed

50 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 51: Ned call-setup-and-release

Figure 29. Radio link reconfiguration failure

7.3 Radio link deletion

The RNC starts the radio link deletion procedure to release one or moreradio links in a communication context. Active set updates, RRCconnection releases and also resets and other error situations such as theBTS and UE being unsynchronised can trigger this procedure.

If the RNC does not receive a response from the BTS before a timerexpires, it sends the deletion message again three times. After that, if thereis still no answer, the resource manager in the RNC starts recoveryactions.

UE BTS RNC

NBAP:RADIO LINK RECONFIGURATION FAILURE

NBAP:RADIO LINK RECONFIGURATION PREPARE

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 51 (85)

Radio link setup, reconfiguration and deletion

Page 52: Ned call-setup-and-release

Figure 30. Radio link deletion

UE BTS RNC

AAL2 Release

NBAP:RADIO LINK DELETION REQUEST

NBAP:RADIO LINK DELETION RESPONSE

52 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 53: Ned call-setup-and-release

8 Radio access bearer setup,reconfiguration and release

8.1 Radio access bearer setup

The radio access bearer setup procedure builds a radio access bearerservice between the UE and the core network (CN). The service isnegotiated between the UE and CN through the signalling link between theUE and radio access network (RAN) and through the signalling connectionbetween RAN and CN.

Once the CN has all the necessary information, it forwards it to the RNC.The RNC analyses the parameters for radio access bearer service andchecks whether the resources needed exist. After that, the RNC activatesor modifies the physical uplink and downlink radio channels from theWCDMA BTS and creates the transmission channels at the Iub and Iurinterfaces according to the reserved radio resources.

The RNC then sends the new radio link parameters to the UE on theexisting signalling link. Once the UE informs the RNC that it uses the newradio link parameters, the RNC acknowledges the information to the CNand radio access bearer establishment is then complete.

The same procedure is also used for adding radio access bearers.

For non-real time (NRT) services, the radio access bearers are createdwithout immediate reservation of radio resources. Instead, radio resourcesare allocated on demand by using the signalling link between the UE andthe RNC.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 53 (85)

Radio access bearer setup, reconfiguration and release

Page 54: Ned call-setup-and-release

Figure 31. Radio access bearer establishment procedure (DCH to DCH)

Setting up a radio access bearer can fail, for instance, because the RNCcannot provide the resources requested. If the requested channel type orresource (for example channel rate) indicated in the RANAP:RABASSIGNMENT REQUEST message is not available in the RAN, aRANAP:RAB ASSIGNMENT RESPONSE message is sent to the CN. Themessage contains the appropriate failure cause.

Signalling link established, MM and CC signalling ...

BTS RNC CNUE

AAL2 Setup (real time RAB)

CC continues...

RANAP:RAB Assignment Request

RANAP:RAB Assignment Response

RRC:RB Setup

RRC:RB Setup Complete

Radio link reconfiguration(real time RAB)

AAL2 Setup (CS RAB)

54 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 55: Ned call-setup-and-release

Figure 32. Failure in radio access bearer establishment

8.2 Radio access bearer release

The UE and CN negotiate about releasing the radio access bearerservices. The CN then commands the RAN to release a radio accessbearer service. The RNC sends an indication of the release to the UE andeither releases the radio link or modifies the radio link parameters if allradio access bearers are not released.

The radio links are also released or modified at the WCDMA BTS, andtransmission channels are released both on the Iu and Iub interfaces. AlsoIur branches are released or modified if the UE had branches throughanother (drifting RNC).

The CN can also request releasing the signalling link if all radio accessbearers related to the CN are released. Then the signalling connectionbetween the RNC and CN is released. The signalling link between theRNC and UE is also released if the UE has no active connection to anotherCN.

RNC CN

Required resourcesnot available

RANAP:RAB Assignment Request

RANAP:Assignment Response(cause)

CN may send a new RAB AssignmentRequest to establish a new RAB orIu release Command to release allreserved resources.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 55 (85)

Radio access bearer setup, reconfiguration and release

Page 56: Ned call-setup-and-release

Figure 33. Radio access bearer release

From the Iu interface's point of view, radio access bearer release is alwayssuccessful. The UE can return a release failure message to the RNC. Inthis case, the UE uses the old configuration.

BTS RNC CNUE

AAL2 release

RL Reconfiguration

AAL2 release

RANAB:RAB Assignment Request (release)

RANAP:RAB Assignment Response

RRC:RB Release

RRC:RB Release Complete

56 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 57: Ned call-setup-and-release

9 Ciphering and integrity protection setup

Authentication and ciphering in circuit switched (CS) and packet switched(PS) is used to verify that the users are who they claim to be. There aretwo security modes: ciphering and integrity protection.

Ciphering is used to encrypt signals between the user equipment (UE) andthe Radio Network Controller (RNC). This is done to prevent third partiesfrom listening to transmissions.

Integrity protection is used to prevent third parties from sendingunauthorised signalling messages between the UE and RNC.

Distribution of the ciphering key (CK) and integrity key (IK) is handled bythe authentication and key agreement (AKA).

Authentication procedure

The authentication procedure verifies that the SIM card of the UE is valid.The SIM card contains IMSI/IMUI security keys as well as other subscriberspecific information. The UE sends its MS classmark to the CN. Theciphering capability of the UE is set by the MS classmark which alsoindicates which integrity protection algorithm (UIA) and encyptionalgorithm (UEA) it supports. Through the authentication procedure thenetwork is able to verify that the security keys of the UE are valid andcorrespond to the subscriber information on the network side. If necessary,the network also requests security parameters from the authenticationcentre (AC) of the CN. The CN sends back subscriber specificauthentication vectors (AV) which consist of information based on the SIMcard of the UE. The AV is only valid for one authentication procedurebetween the UE and the CN. The AV consists of the following:

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 57 (85)

Ciphering and integrity protection setup

Page 58: Ned call-setup-and-release

RAND (random number)random number sent to the UE for generating XRES,CK and IK

XRES (expected response)expected response which needs to be comparedwith the RES in order to allow the AKA procedure tobe successful

CK (ciphering key)key consisting of a number of symbols which controlsthe encipherment and decipherment between the UEand RNC

IK (integrity key) data protection key which is used for protecting theintegrity of data items as well as verifying the origin ofsignalling data

The IK is generated together with CK in the securitymode setup procedure.

AUTN (authentication token)information used to authenticate the sender andcontaining the claimant identity and ticket, as well assigned and encrypted secret key exchangemessages transmitting a secret key to be used inciphering operations

In the authentication key agreement, the CN sends the RAND and AUTNto the UE. This random number is sent unprotected. On the basis of theRAND, the UE generates RES, CK, and IK. This RES is sent to the CN,unprotected. RES and XRES are compared by the CN. The authenticationkey agreement is successful if the RES and XRES match. The CK and IKare then established and subsequent messages are encrypted. The onlysignalling which is sent unprotected is the RAND and the RES. To aneavesdropper, the values appear to be random.

Integrity protection procedure

The integrity protection procedure is started by the RNC which selects thefirst UIA and UEA it supports from the CN's algorithm list. If the RNC doesnot succeed in starting the integrity protection procedure with UE, it sendsa rejection message to the CN.

The integrity key is used in order for the CN to identify the UE and the userbehind it. The input parameters of the integrity key algorithm consist of atime-dependent input (COUNT-I) and a random number generated by theCN (FRESH), a direction bit (DIRECTION) and the signalling data(MESSAGE). The SRNC generates a MAC-I and sends it to the UE whichin turn generates an XMAC-I based on the integrity key algorithmparameters. This XMAC-I code is subscriber and RAB-specific. The UE

58 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 59: Ned call-setup-and-release

compares the received MAC-I and the XMAC-I of the UE and verifies theirvalidity, and if they match the UE returns an RRC: SECURITY MODECOMPLETE acknowledged message to the CN. The COUNT-I is simply acounter which is incremented by one for each sent signalling message;due to this the result (MAC-I/XMAC-I) of the algorithm changes for everynew signalling message. If the sent signalling messages are received withthe wrong message authentication, they are discarded.

To prevent the same ciphering keys from being used indefinitely and thusmaking it possible for third parties to monitor the traffic, the UE stores thepreset key time value in the USIM. This key time value is a counter thatdefines the preset number of times the ciphering keys can be used. Theoperator sets the maximum time value for the ciphering keys. Newciphering keys must be generated for subsequent signalling connections.It is also possible to change the ciphering keys in an ongoing RRCconnection if the ciphering keys expire.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 59 (85)

Ciphering and integrity protection setup

Page 60: Ned call-setup-and-release

Figure 34. Ciphering and integrity procedure overview

UE RNC VLR/SGSN HLR/AuC

Comparison of RES and XRES.If match then ciphering

is initialized

MAC-Igenerated

XMAC-I generatedMAC-I and XMAC-ICompared. If match

then returnedacknowledged

Ciphering and integrity protocol established

IMSI/TMSI

AVN

RAND, AUTN

RES

RANAP: SECURITYMODE COMMAND

RRC: SECURITYMODE COMMAND

CK, IK, RESgenerated

RRC: SECURITYMODE COMPLETE

RANAP: SECURITYMODE COMPLETE

60 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 61: Ned call-setup-and-release

Figure 35. Setting up ciphering and integrity protection

UE BTS RNC CN

RANAP:SECURITY MODE COMMAND

RRC:SECURITY MODE COMMAND

RRC:SECURITY MODE COMPLETE

RANAP:SECURITY MODE COMPLETE

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 61 (85)

Ciphering and integrity protection setup

Page 62: Ned call-setup-and-release

62 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 63: Ned call-setup-and-release

10 Location updates

10.1 Cell update

Cell update procedure is mainly used to update the RNC information onthe UE location after a cell reselection. When the UE selects a new cell, itinforms the RNC in a cell update. In other words, cell update is usedinstead of handover. The UE also performs periodic cell updates accordingto system information.

After the UE has switched to a new cell, it sends a cell update message tothe RNC's radio resource control (RRC). The UE message contains thecell update cause, which can be:

. cell reselection

. periodic cell update

. uplink data transmission

. paging response

. re-entering service area

. radio link failure

. RLC unrecoverable error

If the cell update was caused by cell reselection, the RNC updates the UElocation information and resets the CELL_FACH or CELL_PCH statesupervision timer. The RNC's confirmation message to the UE includes aradio network temporary identifier for the cell (C-RNTI) if the UE remains inCELL_FACH state. If the cell update was performed to a cell not residingunder the serving RNC (SRNC), the message also contains the radionetwork temporary identifier for the RAN (U-RNTI) after relocation, in otherwords; if the SRNC changes.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 63 (85)

Location updates

Page 64: Ned call-setup-and-release

If the cause was a periodic cell update, the RNC updates the UE locationinformation and resets the CELL_FACH or CELL_PCH state supervisiontimer.

If the cause was uplink data transmission, the RNC sends a confirmationand a radio network temporary identifier (C-RNTI). The RNTI for RAN (U-RNTI) is sent if the cell update was performed to a cell not residing underthe serving RNC (SRNC) after the relocation. The UE remains inCELL_FACH state.

If the cell update cause was paging response, the RNC updates the UElocation information. The RNC sends a confirmation and a new radionetwork temporary identifier for cell (C-RNTI). The UE remains inCELL_FACH state.

Figure 36. Cell update due to periodic update

RRC:CELL UPDATE

RRC:CELL UPDATE CONFIRM

RNCUE BTS

MS is in CELL_FACH or CELL_PCH state

64 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 65: Ned call-setup-and-release

11 Transcoder Free Operation (TrFO) andTandem Free Operation (TFO)

The Transcoder Free Operation (TrFO) and Tandem Free Operation (TFO)are included in 3GPP specifications from 3GPP Release 4 onwards. TheTrFO and TFO affect the RNC, MSC, and MGW network elements.

In TrFO, the transcoding which is done in 3GPP Release 99 networks inthe MSC, can be avoided when the CN negotiates Out-of-Band (OoB).OoB is the common set of adaptive multi-rate (AMR) codec modes that aresupported by both end UEs. When the UEs support the same codecs,there is no need for transcoding in the core network (CN), and therefore,the speech quality is increased.

Although the main reason for avoiding transcoding in mobile-to-mobilecalls is improving speech quality, another reason is saving bandwidth bythe transmission of compressed information in the CN, and CN to CNinterface of the cellular network.

The difference between the TrFO and TFO is, that in TrFO, the transcoderis not used in the CN while it is used TFO. Also, the bandwidth savings areonly achieved with TrFO.

The basic architecture for the UMTS to UMTS TrFO connection is shownin the following figure.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 65 (85)

Transcoder Free Operation (TrFO) and Tandem Free Operation(TFO)

Page 66: Ned call-setup-and-release

Figure 37. Basic architecture for UMTS to UMTS TrFO connection

From the RAN point of view, TFO and TrFO are similar functions. Theselection between TFO and TrFO is done in the core network, anddepends on the core network capabilities and if transcoding is needed inthe CN.

TFO and TrFO can be used for mobile-to-mobile calls within the WCDMAnetwork or between WCDMA and GSM networks, or between the WCDMAnetwork and an external network, for example, fixed landline network.

In the RNC, the TFO and TrFO features can be switched on and off by thePeriodULRCAMR management parameter. If it is on, that is, its value isbetween 0 and 254, TFO and TrFO is used together with the supportedAMR modes in WCDMA RAN. Therefore, in the Iu user plane protocol (IuUP) support mode for predefined SDU sizes, version 2 is supported in theRNC. If the PeriodULRCAMR is set to value off, that is, it is 255, only the IuUP support mode for predefined SDU sizes version 1 is supported in theRNC.

Transit Network

MGW

End to end connection

MGW RNCRNC

BearerReq

MSC Server MSC Server

OoB Codec Negotiation

BearerReqBearer Req

MGwControl

MGwControl

ME ME

OoB CodecNegotiation

OoB CodecNegotiation

RANAP RANAP

Iu BearerRadioBearerCN BearerIu Bearer

RadioBearer

UserPlane

ControlPlane

66 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 67: Ned call-setup-and-release

11.1 TrFO and TFO with multimode AMR

TFO and TrFO can be used with all the supported AMR codec modes. Ifthe codec mode set includes more than one codec mode, the rate controlbetween the codec modes is supported, thus enabling link adaptation inthe other end. If the codec mode set includes only one codec, the TrFO isused to achieve bandwidth savings in the CN and improved voice qualityin the UE.

In uplink (UL), rate control is based on the maximum rate controlinformation received from the Iu interface. The uplink rate controlinformation is conveyed to the UE with the RRC: TRANSPORT FORMATCOMBINATION CONTROL (TFCC) message on dedicated controlchannel (DCCH) using AM RLC. After that, the UE selects the codec modebased on that information.

In downlink (DL), the RNC controls the allowed maximum rate, and if achange is needed, the RNC sends the Rate Control procedure to the Iuinterface.

When the RNC receives the Iu UP data frames from the Iu interface, theRNC forwards the data to the UE if the codec mode is equal to or belowthe current maximum downlink rate.

11.2 RNC TrFO and TFO functions

When the PeriodULRCAMR RNC management parameter is set to a valuebetween 0 and 254, the RNC supports the following TrFO TFOfunctionalities.

RAB Assignment procedure

The RAB ASSIGNMENT REQUEST message contains Iu user planemode version 2 as an alternative to enable the TrFO functionality in theRNC. The RAB ASSIGNMENT REQUEST message also contains theAMR codec modes that are negotiated Out-of-Band by the CN andsupported by the UEs. Therefore, they are to be initialised in the UserPlane.

The following figure illustrates the RAB assignment procedure.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 67 (85)

Transcoder Free Operation (TrFO) and Tandem Free Operation(TFO)

Page 68: Ned call-setup-and-release

Figure 38. RAB Assignment procedure

1. The RNC receives the RAB ASSIGNMENT REQUEST messagefrom the MSC.

The message contains:. All the AMR codec modes that are negotiated Out-of-Band in

the CN. For more information, see Figure Basic architecturefor UMTS to UMTS TrFO connection.

. The Iu UP mode versions that are allowed for the Iu userplane. For TrFO, version 2 must be included.

2. The RNC establishes the transport bearer for the CS RAB.

3. The RNC sends the IuUP: INITIALISATION control frame to theMGW.

The message contains:. The RFCI values for all the AMR codec modes that have been

received in RAB ASSIGNMENT REQUEST message.. All the Iu UP mode versions supported by the RNC and that

have been among the mode versions included in RABASSIGNMENT REQUEST message.

4. The MGW sends the IuUP: INITIALISATION ACK control frame tothe RNC. The message contains the selected Iu UP mode version.For TrFO, the Iu UP mode version is 2.

RNC MSC MGW

1

RANAP:RAB Assignment Request

AAL2 Setup (CS RAB)2

IuUP: INITIALISATION

IuUP: INITIALISATION ACK4

3

RANAP:RAB Assignment Response

6

RFCI Value Correction5

68 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 69: Ned call-setup-and-release

5. Depending on the MGW implementation, the MGW can initiate theRFCI Value Correction procedure to change the RFCI values, whichhave been initially allocated by the RNC. The RNC can also receiveRFCI Value Correction after the following step.

6. After a successful Iu UP initialisation, the RNC sends the RABASSIGNMENT RESPONSE message to the MSC.

For more information about Iub and Uu procedures, see Figure Radioaccess bearer establishment procedure (DCH to DCH).

SRNS Relocation procedures

The parameters received in the RAB Assignment procedure aretransferred from the source RNC to the target RNC in RelocationPreparation and Relocation Resource Allocation procedures. During therelocation, the Iu UP protocol entity is created in the target RNC in a similarmanner as during the RAB Assignment procedure in the source RNC.

Iu UP Initialisation procedure

When TrFO is supported, the RNC initiates the Iu UP with all the codecsthat have been included in the RANAP: RAB ASSIGNMENT REQUESTmessage. When the CN includes version 1 and 2 of the UP mode versionsin the RAB Assignment procedure, the RNC allocates the codec modesand if version 2 is enabled by the PeriodULRCAMR parameter, the RNCincludes both versions as preferred versions in the IuUP: INITIALISATIONcontrol frame. Therefore, the RNC delegates the final decision of the usedIu UP version for the MGW. If the RAB ASSIGNMENT REQUESTmessage contains only version 2, the RNC includes only Iu UP version 2as the preferred version if the TrFO feature is supported.

The IuUP INITIALISATION control frame also contains information aboutthe maximum allowed DL rate. The RNC uses IuUP INITIALISATIONframe version 1 (Iu UP Mode Version = 1) if this version has been includedin the RAB Assignment procedure. Therefore, the first RFCI containsinformation about the maximum allowed DL rate in the first frame only, thenall the rates are allowed again. On the other hand, if the RAB Assignmentprocedure contains only Iu UP mode version 2, the RNC uses the IuUPINITIALISATION control frame version 2. In this case, the first RFCIcontains information about the maximum allowed DL rate, which is validuntil RNC sends a Rate Control procedure.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 69 (85)

Transcoder Free Operation (TrFO) and Tandem Free Operation(TFO)

Page 70: Ned call-setup-and-release

RFCI value correction

The RNC allocates and stores the RFCI values for each codec. The samevalues are included in the Iu UP INITIALISATION control frame, which issent to the MGW. When the RNC at the other end allocates RFCI valuesindependently of the first RNC, the allocated RFCI values can be differentin each end. Therefore, the MGW, which is in the middle, can distinguishthe different values and start the RFCI Value Correction procedure towardsthe other end, which replaces the earlier allocated RFCI values with thenew ones.

The RFCI Value Correction procedure is an Iu UP Initialisation procedure,which is initiated by the MGW, and therefore the RNC supports theincoming Iu UP Initialisation procedure. It is also possible that the MGWdoes not start the RFCI Value Correction when the MGW determines thatthe RFCI values are different. In that case the RNC does not receive theincoming Iu UP Initialisation procedure, and the MGW changescontinuously the RFCI values in the user data frames so that they are validfor each RNC.

Maximum Rate Control procedure

The RNC controls the UL and DL maximum rate in its cells. The Iu UPRate Control procedure is used by the RNC when the RNC detects that themaximum allowed DL rate needs to be changed. This can occur, forexample, if the AMR modes set is reduced due to the UE capability in amultiservice configuration.

When the RNC sends the IuUP: RATE CONTROL control frame to theMGW, the TrFO operation has priority, and therefore, the MGW does notstart the transcoding. The MGW then forwards the message, which finallyreaches the other end.

Therefore, in order to support the TrFO, the RNC must also support theincoming IuUP: RATE CONTROL control frames.

When the RNC receives IuUP: RATE CONTROL control frame, the RNCimmediately forwards this information to the UE if the RNC does not detectan overload and no other RRC procedures are running.

70 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 71: Ned call-setup-and-release

Filtering of Frequent IuUP Rate Control frames

In some cases, for example, in GSM link adaptation, the IuUP: RATECONTROL control frames are received frequently. This is called FrequentRate Control, and it needs a special functionality if the overload control ofthe RNC detects a high signalling load. The functionality in the RNC iscalled ‘Filtering’ and it is activated by the PeriodULRCAMR managementparameter.

When the RNC receives the IuUP: RATE CONTROL control framerequests to upgrade the maximum UL AMR mode, the RNC starts waitingas long as it is defined by the PeriodULRCAMR management parameter.During that time, if there are Rate Control requests to even further upgradethe UL AMR mode, or to downgrade it compared to the recently receivedRate Control request, but the Rate Control is still above the currentmaximum UL AMR mode the UE knows, the RNC ‘filters’ the Rate Controlrequests, and does not send the upgrades to the UE.

When the time defined by PeriodULRCAMR expires, the RNC sends theRRC: TRANSPORT FORMAT CONTROL COMMAND to the UE if themost recent Rate Control request was to increase the maximum UL AMRmode that the UE knows.

Every maximum UL AMR mode downgrade request is transferred to theUE without filtering, unless there is another RRC procedure running thatprohibits it.

The RRC: TRANSPORT FORMAT CONTROL COMMAND is sent to theUE in DCCH, which uses the Acknowledge Mode (AM) RLC.

Figure Filtering Frequent Iu UP Rate Control procedures shows anexample scenario for Filtering Frequent Iu UP Rate Control procedures.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 71 (85)

Transcoder Free Operation (TrFO) and Tandem Free Operation(TFO)

Page 72: Ned call-setup-and-release

Figure 39. Filtering Frequent Iu UP Rate Control procedures

1. The RNC receives the IuUP: RATE CONTROL control frame fromthe MGW.

2. The RNC detects a signalling overload and the Rate Control requestis to increase the Maximum UL rate.

3. The RNC does not send the increased Maximum UL rate informationto the UE but sends the IuUP: RATE CONTROL ACK control frameto the MGW.

4. The RNC receives a new frequent IuUP: RATE CONTROL controlframe before the time defined by PeriodULRCAMR parameter haselapsed.

5. The RNC filters the Rate Control and this time, the Rate Controlrequests to reduce the Maximum rate, or the time defined by thePeriodULRCAMR parameter just elapses.

6. The RNC sends the RRC: TRANSPORT FORMAT CONTROLCOMMAND to the UE to reduce the Maximum rate.

7. The RNC sends the IuUP: RATE CONTROL ACK control frame tothe MGW.

UE RNC MGW

IuUP: RATE CONTROL1

Filtering2IuUP:

RATE CONTROL ACK

IuUP: RATE CONTROL3

4

Filtering5

6

7

RRC: TFCCIuUP:

RATE CONTROL ACK

72 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 73: Ned call-setup-and-release

Immediate Rate Control

The maximum UL rate information is not delivered in the SRNS Relocationprocedures (in RANAP), therefore, it is gathered by Immediate RateControl procedure. This also allows the Target RNC to send its maximumDL rate to the other end.

The Immediate Rate Control is done after the SRNS Relocation and Iu UPInitialisation procedures. It is triggered when the Target RNC receives arelocation execution trigger from the UE or from the Iur interface.

If the type of the SRNS relocation is 'UE not involved in relocation ofSRNS', the relocation execution trigger is the RNSAP: RELOCATIONCOMMIT message from the Source RNC. Otherwise, the relocationexecution trigger is the RRC message received from the UE, or theestablished L1 synchronisation between Node B and the UE.

11.3 RNC parameters

Table 2. RNC parameter

Parameter name: Period for CS AMR RRC TFC control requests

Abbreviated name: PeriodULRCAMR

11.4 Definitions

Transcoder Free Operation (TrFO)

The purpose of TrFO is to remove unnecessary speech encodingcompletely from the speech path. This is achieved by Out-of-Bandsignalling that performs the coded negotiation and selection throughoutthe network.

Configuration of a speech or multimedia call for which no transcoderdevice is physically present in the communication path and thus, nocontrol or conversion or other functions can be associated with it.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 73 (85)

Transcoder Free Operation (TrFO) and Tandem Free Operation(TFO)

Page 74: Ned call-setup-and-release

Tandem Free Operation (TFO)

In 2G (GSM), TFO is a base station system (BSS) feature. In 3G(WCDMA), TFO is performed by transcoders located in the core network.The objective of avoiding multiple transcoding is to improve the speechquality in mobile-to-mobile calls.

Configuration of a voice or multimedia call for which transcoders arephysically present in the communication path but transcoding functions aredisabled or partially disabled in order to avoid multiple transcoding.

74 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 75: Ned call-setup-and-release

12 Flexible Iu

Feature RAN834: Flexible Iu is also known as ‘Multipoint Iu’or ‘IntraDomain Connection of RAN Nodes to Multiple CN nodes’.

The Intra Domain Connection of RAN Nodes to Multiple CN Nodesovercomes the strict hierarchy, which restricts the connection of a RANnode to just one CN node (see also Feature Nokia MORAN). The IntraDomain Connection of RAN Nodes to Multiple CN Nodes introduces arouting mechanism (and other related functionality), which enables theRAN nodes to route information to the different CN nodes within the CS orPS domain.

The Intra Domain Connection of RAN Nodes to Multiple CN Nodesintroduces the concept of ‘Pool Areas’. Within a Pool Area, a UE can roamfreely (in either connected or idle mode) without the need to change theCN serving node.

The usage of this 'Pool Area' concept aims to reduce inter CN nodeupdates, inter CN handovers/relocations and HLR updating signalling.

Simultaneous usage of Flexible Iu and the Nokia-specific Multiple CoreNetworks Support or Nokia Multi-Operator RAN (MORAN) is not possible.

Flexible Iu is an optional feature.

12.1 Pool-Area

Iu Flexible capable RNCs are able to select any CN node within a poolarea. Iu Flexible capable RNCs and CN nodes are able to coexist with pre-release 5 RNCs and pre-release 5 CN nodes. However, Iu Flexiblecapable RNC cannot have both Iu Flexible capable and pre-release 5 CNnodes connected to it.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 75 (85)

Flexible Iu

Page 76: Ned call-setup-and-release

Pool configurations are done in CN nodes. Pool areas itself are not visibleto the RNC. The configuration of the RNC configuration database is doneaccording to the CN pool configurations. CS and PS pool areas areconfigured independently from each other.

Figure 40. Pool area example

12.2 Network Resource Identification

The Network Resource Identifier (NRI) identifies the specific CN node ofthe pool. The UE derives the NRI from the TMSI, P-TMSI, IMSI or IMEI.

Area 1 Area 2 Area 3 Area 4

Area 5 Area 6 Area 7 Area 8

MSC 3

MSC 2

MSC 1

MSC 6

MSC 5

MSC 4

MSC 7

RANnode

RANnode

SGSN 2

SGSN 1

RANnode

RANnode

RANnode

RANnode

SGSN 5

SGSN 4

SGSN 3

RANnode

RANnode

SGSN 6

PS pool-area 1

PS pool-area 2

CS pool-area 1

PS pool-area 2

76 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 77: Ned call-setup-and-release

The UE provides an IDNNS IE in the RRC: INITIAL DIRECT TRANSFERmessage to the RNC. The IDNNS IE contains a routing parameter, whichtransports the NRI value. In addition, the IDNNS IE contains the indicationfrom which identity (TMSI, P-TMSI, IMSI & IMEI) the routing parameter isderived. NAS node selection function in RNC does not use this identityinformation in routing at all. The NRI values are always used in routingregardless of what the identity where the NRI was taken was.

The NAS node selection function is used in the RNC to select the specificCN node (that is, MSS or SGSN) to which initial signalling messages arerouted. The NRI identifies the specific CN node.

The values of the routing parameters (NRI) are configured into the RNCdatabase according to the pool area configurations. There areindependent parameter sets defined for PS and CS pools.

Max 16 NRI values or value ranges can be configured to every CN nodeconnected to the RNC. CS and PS Core pools have the same maximum16 NRI values per CN node. The maximum number of CN nodes perdomain to be connected in one RNC is 32. This limit consists of a CNnodes connected to the RNC in case of overlapping pool areas. Whenoverlapping pool areas are used in the network, in the overlapping area,RNC is connected to all CN nodes operating there, see Figure Pool areaexample.

The NRI length is configured in the RNC for both CN domains. The lengthof the NRI is the same in all the nodes of the domain in one pool-area. Incase of overlapping pool areas, the NRI length must be the same for alloverlapping pools. If the value of the NRI length is 0, it means that the IuFlexible feature is not used (inactive) in network.

12.3 Load Balancing

The NAS node selection function in the RNC balances the load betweenthe available CN nodes. This is performed by an appropriate selection ofthe CN node for a UE, which has no CN node configured for the NRIindicated by the UE. The load balancing is used to choose the appropriateCN node. The default assumption is that the NRI value is always used forrouting in the RNC. If the CN node indicated by the NRI is not available,the CN node is not found with the given NRI, or NRI is the ‘Null NRI’, a loadbalancing is used for routing. Load sharing between the CN nodes can beaffected by parameters.

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 77 (85)

Flexible Iu

Page 78: Ned call-setup-and-release

The method for load balancing is the round robin. Round robin means thatthe resources are evenly spread in the Iu interface. The Iu signalling entitychooses one of the available CN nodes from the list of the Iu items with theconcerned CN domain.

The availability of the CN node is defined with the IuState parameter foreach CN node. Normal Iu state is WO-EX, working. CN nodes in statesBAL-US and BAR-US are not available for load balancing.

BAL-US value is used for barring only from load balancing function whichmeans that old UEs with correct NRI value are allowed to establishconnection to CN node, but new UEs, UEs with unknown NRI, or UEs withNull-NRI are not allowed.

BAR-US value means that the CN Node is totally blocked from allconnection establishments.

12.4 RNC Parameters

This section introduces management parameters that can be used tocontrol the Flexible Iu feature.

The management parameters are described in detail in WCDMA RAS06Parameter Dictionary.

Parameter name: NRI length for PS Core Networks

Abbreviated name: NRILengthForPSCNs

Parameter name: NRI length for CS Core Networks

Abbreviated name: NRILengthForCSCNs

Parameter name: Null NRI value for PS Pool

Abbreviated name: NullNRIForCSPool

Parameter name: Null NRI value for CS Pool

Abbreviated name: NullNRIForCSPool

78 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 79: Ned call-setup-and-release

Parameter name: NRI list for PS Core routing

Abbreviated name: PSCNNRIList

Parameter name: Minimum value of NRI range for PS Corerouting

Abbreviated name: NRIMinForPSCN

Parameter name: Maximum value of NRI range for PS Core

Abbreviated name: NRIMaxForPSCN

Parameter name: NRI list for CS Core routing

Abbreviated name: CSCNNRIList

Parameter name: Minimum value of NRI range for CS Corerouting

Abbreviated name: NRIMinForCSCN

Parameter name: Maximum value of NRI range for CS Core

Abbreviated name: NRIMaxForCSCN

Parameter name: State of Iu interface

Abbreviated name: IuState

12.5 Definitions

Pool Area

It is a collection of one or more MSC or SGSN serving areas, and withinthem a UE can roam without the need to change the serving CN node (thatis, the MSC-server or the SGSN).

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 79 (85)

Flexible Iu

Page 80: Ned call-setup-and-release

A Pool Area is served by one or more CN nodes in parallel. All the cells arecontrolled by a RAN node, that is, (the RNC belongs to the same (or more)pool area(s).

NAS Node Selection Function

A function used to assign specific network resources (that is, the MSC-server or the SGSN) to serve a UE, and subsequently, route the traffic tothe assigned network resource.

Network Resource Identifier, NRI

A specific parameter which is used to identify the CN node assigned toserve a mobile station.

Null-NRI

A 'null-NRI' indicates to an RNC that the NAS Node Selection Functionmust be used for selecting a CN node to receive a message.

80 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 81: Ned call-setup-and-release

13 Call setup and release statistics

The measurement types introduced in the list below are relevant to callsetup and release. For more information, see the reference documentRNC counters - RNW part.

. Service level (RRC and RAB connections)

. Intra-system hard handover

. Inter-system handover

. RRC signalling

. L3 signalling at Iub

. L3 signalling at Iur

. L3 signalling at Iu

. L3 relocation signalling

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 81 (85)

Call setup and release statistics

Page 82: Ned call-setup-and-release

82 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 83: Ned call-setup-and-release

Related Topics

Call setup and release

Reference

Call setup and release statistics

Descriptions

Real-time and non-real time services

RRC state

Paging

RRC connection setup and release

Signalling connection setup and release

Radio link setup, reconfiguration and deletion

Radio access bearer setup, reconfiguration and release

Ciphering and integrity protection setup

Location updates

Transcoder Free Operation (TrFO) and Tandem Free Operation (TFO)

Real-time and non-real time services

Descriptions

Introduction to the packet scheduler functionality

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 83 (85)

Related Topics

Page 84: Ned call-setup-and-release

RRC state

Descriptions

Call setup and release

Radio link setup, reconfiguration and deletion

Introduction to the packet scheduler functionality

Paging

Descriptions

Call setup and release

RRC connection setup and release

Descriptions

Call setup and release

Signalling connection setup and release

Descriptions

Call setup and release

84 (85) # Nokia Siemens Networks DN03471581Issue 5-0 en30/05/2007

Call Setup and Release

Page 85: Ned call-setup-and-release

Radio link setup, reconfiguration and deletion

Descriptions

Call setup and release

Radio access bearer setup, reconfiguration andrelease

Descriptions

Call setup and release

Ciphering and integrity protection setup

Descriptions

Call setup and release

Location updates

Descriptions

Call setup and release

Flexible Iu

Descriptions

Call setup and release

DN03471581Issue 5-0 en30/05/2007

# Nokia Siemens Networks 85 (85)

Related Topics